Your English is not what's holding you back. Order is. You deliver conclusions the way you write a design doc — context, evidence, reasoning, then the call. Executives decode in the opposite direction and stop listening long before you arrive. This course rewires the order, the hedging, and the room.
Sylvia Ann Hewlett's research asked senior executives what makes someone read as leadership material. The weights are lopsided, and they are not where most engineers spend their effort.
67% · Gravitas
How you act
Composure under fire. Taking a public position before you have certainty. Saying the inconvenient thing to someone senior. Knowing your domain cold. This is the bulk of the score and it is almost entirely about behaviour in the moment, not vocabulary.
28% · Communication
How you speak
Conciseness, command of a room, pacing, the strategic pause, reading the audience. Note what this isn't: grammar, idiom range, or accent. Voice quality matters here; correctness barely registers.
5% · Appearance
How you look
Small, and mostly a threshold effect — it can subtract points, it rarely adds them. Clear it once and stop thinking about it. Most of the anxiety spent here is misallocated from the 67%.
The trap for a strong non-native IC is that both the anxiety and the remediation get aimed at the 5% and at the parts of the 28% that don't count. Six weeks of accent work moves nothing. Six weeks of restructuring how you open a sentence moves everything.
Diagnosis
Three failure modes
Everything in this course traces back to one of these. Learn to hear yourself doing them; that recognition is half the fix.
1 · The Buried Lede
You were trained — by engineering culture and by school — to show your work before your answer. A VP with eleven minutes hears preamble and concludes you don't have a position.
You said
"So, we looked at three options. The first one was to keep the existing pipeline but add a caching layer, which we prototyped, and the latency was better but the cache invalidation got complicated because of the way the upstream service batches its writes, and then we also considered…"「我们看了三个方案。第一个是保留现有管道加一层缓存,我们做了原型,延迟确实好些,但缓存失效因为上游批量写入变得很复杂,然后我们还考虑了……」——讲了四十秒还没到结论。
Say this
"I recommend we rebuild the pipeline rather than cache around it. Three reasons, thirty seconds. Then I'll take questions on any of them."「我建议重建管道,而不是外面套缓存。三个理由,三十秒讲完,然后随便问。」结论在第一句。
Why
The second version buys you the same five minutes — but now they're spent on your reasoning with the room already oriented, instead of on them waiting for you to arrive somewhere.
2 · The Hedge Reflex
In a high-context culture, softeners are politeness infrastructure — they leave the other person room to disagree without either of you losing face. In a low-context US room, the softener is parsed literally: it is read as your actual confidence level.
You said
"I think maybe we could possibly consider moving the deadline, if that's okay? I'm not totally sure but it might be a bit risky."四个软化词叠在一起:think / maybe / possibly / a bit。在中文语境里这是礼貌,在美式会议里是「他没有立场」。
They heard
"He doesn't know. He wants me to decide. I'll ask someone else next time."对方听到的是:「他不知道,他想让我来定。下次我问别人。」
Say this
"We should move the deadline two weeks. The risk is the migration's rollback path is untested — that's the one thing I'm not willing to ship without. If you want to hold the date, tell me and I'll come back with what we'd cut."先给结论(推迟两周),再给唯一的具体风险(回滚路径未测),最后把选择权交回去并附代价。全程零软化词。
3 · The Deference Tax
You defer to the most senior person in the room by default. In a hierarchical culture that reads as competence and respect. In an egalitarian one it reads as having nothing to add — and worse, it quietly transfers ownership of your call to someone with less context than you.
You said
"Whatever you think is best. You have more visibility than me on this."「您看着办,您比我看得全。」在层级文化里是得体,在扁平文化里是弃权。
They heard
"No opinion." (And later, when it goes wrong: "He never flagged it.")「他没有观点。」——而且出事之后会变成「他当时也没提醒过」。
Say this
"You have context I don't on the customer side, so you may land somewhere else. From where I sit, the technical answer is clearly B — A costs us six months of migration debt. If the customer commitment overrides that, I'll take B and make it work."在对方真的更懂的那条轴上让步(客户侧),在你更懂的那条轴上守住(技术侧),并且明确表示服从最终决定。这就是 gravitas 的标准形状。
Why
Both respectful and on record. You've deferred on the axis where they genuinely know more, and held your ground on the axis where you do. That combination is exactly what "gravitas" scores.
Week 0
Baseline
Answer honestly about the last month, not your best day. 1 = never / not true, 5 = consistently true. This takes four minutes and gives you the three numbers to move.
Curriculum
Six weeks
Roughly two hours of study plus five twenty-minute drills each week. Check lessons off as you go — progress is saved in this browser.
Reference
Phrase banks
Not scripts to memorise word-for-word — patterns to internalise until the right shape arrives without translation. Read the left column aloud once, then the right. The difference you hear is the whole course.
Practice
Scenario library
Twelve situations you will actually hit at Staff level. Each has a setup, the trap most people fall into, a script that works, and what to grade yourself on. Run them out loud — reading them silently does nothing.
Habit
The weekly drill rotation
Twenty minutes, five days. The rotation stays the same for all six weeks; only the material you feed it changes. This is where the actual rewiring happens — the lessons just tell you what you're aiming at.
Day
Drill
How
Pass condition
Live reps
Using me as the practice partner
Role-play is the part of the original course you can't get from a page. Paste these into a chat with me and we run it live — I play the counterpart, stay in character, and score you afterwards against the rubric below.
Scoring
Simulation rubric
Score every rep out of 20. Below 12 means run it again immediately — the second attempt is where the learning is. Track the number weekly; the shape of your weak column tells you which week to re-read.