“What would you tell us about your team’s strategy?” is a question that catches many EMs off guard. Operational managers can recite this quarter’s deliverables. Strong managers can articulate where the team is going, why, and how the work in progress maps to that vision. The interview probes this for senior+ EM roles directly.
The three-horizon model
Healthy engineering teams have plans across three horizons:
- Now (this quarter): committed work, in flight
- Next (next 1–2 quarters): high confidence, scoped but not started
- Later (3–6 quarters): directional, lower confidence, big bets
Many teams have only “now.” They are reactive and lose strategic capacity over time.
Building a 12-month plan
Your team should be able to answer: “If everything goes well, where will we be in 12 months?” The answer should be a few specific outcomes, not a list of projects.
Examples:
- “Customer time-to-value reduced from 2 weeks to 3 days”
- “All ML models served from a unified inference platform”
- “Mobile crash rate below 0.1%”
- “Onboarding NPS > 50”
Outcomes shape the projects. Project list is the implementation, not the plan.
Connecting strategy to execution
Each quarter’s roadmap should be visibly aligned to the 12-month outcomes. The OKR ritual works for many teams:
- Annual: 3–5 outcomes (the strategy)
- Quarterly OKRs: measurable contributions toward annual outcomes
- Sprint goals: tactical work that delivers OKR progress
Prioritization frameworks
When you have more work than capacity (always), pick a framework:
- RICE: Reach × Impact × Confidence ÷ Effort. Numeric, defensible.
- ICE: Impact × Confidence × Ease. Simpler version.
- Kano: distinguishes basic, performance, and excitement features.
- Cost of Delay: opportunity cost of not doing something.
Frameworks are tools, not oracles. The point is to make tradeoffs explicit.
Saying no
The hardest part of strategy is what you do not do. As an EM:
- Surface the tradeoff in writing — “to take this on, we would defer X and Y”
- Let stakeholders pick — they own priorities, you own delivery
- Document the decisions; revisit when context changes
The vision document
Write a 1–2 page document describing where your team is going. It should answer:
- What problem are we solving?
- For whom?
- Why now?
- What does success look like in 12–24 months?
- What are the biggest risks?
Share with your team, your manager, and key stakeholders. Update twice a year. Use it as the anchor for OKR planning.
Stakeholder alignment
Before quarterly planning, sync with:
- Your manager — what does the org need from your team?
- PM lead — what is the product roadmap?
- Adjacent EMs — what depends on you, what do you depend on?
- Sales / GTM (if applicable) — what does the field need?
Surfacing conflicts early avoids “we missed the deadline because their team did not deliver” later.
The big-bet decision
Once or twice a year, your team will face a meaningful “build X big thing or Y other big thing” decision. Process:
- Write a 2-page proposal for each option
- List assumptions, risks, and required investments
- Discuss with stakeholders
- Make a decision; commit
- Schedule a review at 3 and 6 months — kill the project if the assumptions are not validating
Tech debt as strategic investment
Strategic teams treat tech debt as part of their roadmap, not as a tax. Allocate explicit capacity (10–20%). Tie debt paydown to specific outcomes — “this refactor unlocks the next feature with 50% less effort.”
Frequently Asked Questions
How often should I revisit strategy?
Light review at the start of every quarter; substantial review at the start of the year. More if business context changes materially.
What if my company does not give me a strategy to align with?
Build one. Make it visible. The act of writing forces alignment with your manager and partners. Strategy from below is often a sign of a strong EM.
How do I handle a strategy I disagree with?
Disagree in writing first. Articulate concerns and propose alternatives. If the decision holds, commit publicly. Re-raise concerns only if new information emerges.