The skills that got you promoted as an engineer, solving hard problems quickly, are not the ones that are noticed at the next level. There, people want to know which problems are worth solving, what it will cost and what you recommend. The engineers I coach usually have all of that in their heads. The work is in saying it in the language of the business, in a few clear sentences.
01What changes at the next level
A strategic role is less about doing the work and more about deciding which work happens. The questions you answer change:
This doesn’t mean losing your technical depth. It means using it to make better business decisions, and explaining those decisions to people who don’t share your background.
02Translate technical work into business impact
Senior people listen for four things: revenue, cost, risk and speed. Climb the ladder from your technical fact until you reach one of them:
| Step | Example |
|---|---|
| Technical fact | “We added caching to the pricing API.” |
| Effect | “The pricing page now loads in under a second instead of four.” |
| Business outcome | “Fewer people leave the checkout, which protects revenue.” |
| The ask or decision | “I’d like to do the same for search next quarter.” |
Then lead with the top of the ladder, not the bottom:
Keep the technical detail ready for follow-up questions. Engineers in the room will ask for it; executives usually won’t.
03Bring options and a recommendation
Taking a problem to a senior leader without a recommendation hands the work back to them. Use “bottom line up front”, a structure Harvard Business Review describes for email: the recommendation first, the reasons second.
Recommendation
One sentence: what you think should happen.
Options
Two or three, with cost, time and risk.
Trade-off
What you give up with your choice, said openly.
The ask
The decision you need, and by when.
04Prioritise, and say no in business terms
At the strategic level, saying yes to everything is the fastest way to lose trust: the work arrives late and half-finished. Make the cost of each yes visible instead.
- Name the trade-off: “If we take this on, the migration moves to next quarter.”
- Offer a smaller yes: “We can do a first version for the two biggest customers by June.”
- Link it to the goals: “This doesn’t move either of our two goals this year, so I’d leave it.”
- Decide early: a clear no in March is better for everyone than a missed deadline in June.
05Think and speak in a longer time frame
Operators plan in sprints; strategic leaders plan in quarters and years. Show that range when you speak:
- Ask business questions in your one-to-ones: what success looks like this year, what worries them, which customers matter most.
- Describe your roadmap as bets, each with the result you expect: “We’re betting that faster onboarding will reduce churn.”
- Talk about risks before they happen, with a plan: “If usage doubles, the current setup will struggle. Here’s what we’d do.”
06Build relationships beyond engineering
Strategy happens between teams. Spend time with your peers in product, sales, finance and support. A thirty-minute call once a month, asking what they’re worried about, gives you the business context that makes your recommendations land.
It also means you hear about problems early, and they hear your name when decisions are made.
07Phrases for strategic conversations
| Situation | Phrases |
|---|---|
| Leading with the point | “The bottom line is…” · “My recommendation is X, for two reasons.” · “What I need from you today is a decision on…” |
| Business impact | “In business terms, this means…” · “The impact for customers is…” · “This reduces the risk of…” |
| Options and trade-offs | “I see three options.” · “The trade-off is speed against cost.” · “If we choose A, we accept…” |
| Prioritising and saying no | “If we take this on, X moves to next quarter.” · “We can do two of these three well, not all three.” · “I’d rather say no now than deliver late.” |
| Understanding the business | “What does success look like for you this year?” · “Which of these matters most to the business right now?” · “What would make you worried about this plan?” |
| When you don’t have the answer | “I don’t have that number yet. I’ll come back to you by Friday.” · “Let me check and confirm in writing.” |
| Instead of | Try |
|---|---|
| “We refactored the service.” | “The service now costs less to run and fails less often.” |
| “It’s technically complicated.” | “There are two risks you should know about.” |
| “We can’t do that.” | “We can do that if we move X to next quarter.” |
| “I think maybe we could try…” | “I recommend…” |
| “Any questions?” | “Can I go ahead with option A?” |
08Example: a decision email to a VP
An invented example. The whole case fits on one screen, the recommendation comes first, and the ask is impossible to miss.
Decision email
Subject: Decision needed by Friday: reporting service
Recommendation. Pause the export feature for four weeks and fix the reporting service.
Why now. Reports take up to 40 seconds to load. Sales has raised it in three enterprise renewals this quarter, and two customers have asked for a timeline.
Options. A: pause exports, fix reporting (4 weeks, no extra cost). B: hire two contractors (around 8 weeks to be productive, budget needed). C: wait (risk to renewals continues).
Trade-off. Exports move from November to December. I’ve checked with Product; no customer contract depends on the November date.
What I need. Your approval to go ahead with A. I’ll send a short update every Friday until it’s done.
09Before your next leadership conversation
- I can say the business impact in one sentence: revenue, cost, risk or speed.
- I start with my recommendation.
- I have two or three options with their cost and risk.
- I say the trade-off before anyone asks.
- I know the decision I need, and by when.
- I have the technical detail ready, but I don’t lead with it.