Strategy & Vision

Strategy & Vision is the work of connecting engineering effort to business outcomes and direction and, from organisational scope, of shaping the organisation that does the work. Here engineering management turns outward. The team and its work give way to the business and its goals. The domain carries 20% of every examination: 12 questions on EMA-I, 15 on EMP-II and 18 on EME-III. Its six competencies are listed below with the questions each carries at each level, and the Exam Content Outlines give the proficiency indicators.

Each competency in this domain reasons about outcomes in preference to output. Strong managers tie every significant piece of work to why it matters to the business. They speak in the listener's language, make resource trade-offs explicit, measure whether the strategy is working, and treat the organisation's structure as the way the strategy is implemented. The examinations favour the option that links an engineering decision to an outcome, or to a choice a stakeholder really faces, over the option that follows engineering preference. The stronger answer states the trade-off where the weaker one absorbs the ask. It argues the platform in business terms, compares bets on forward-looking arithmetic, trends teams instead of ranking them, and changes the structure instead of blaming the people.

At team scope you translate a strategy you were given into work one team can execute and believe in, and you are the team's interface to its partners. At organisational scope you own a department strategy with a connecting thesis. You negotiate every ask with its trade-off, curate a portfolio with admission criteria, allocate a budget, measure across teams without breaking them, and design team boundaries. At executive scope you author the engineering strategy and argue it to the board. You own the horizon mix and the economics of the whole function, declare how the strategy's success will be judged, and shape the organisation itself. The general pattern is in How Judgment Scales; each unit's scaling note places its own competency on it.

Read SV-1 Engineering strategy first, because everything else serves the strategy. Take SV-3 Roadmapping and SV-4 Engineering economics together: the roadmap is the sequence of bets, and economics decides between them. SV-2 Communicating and partnering across functions is the communication that carries all of it outward, and it is worth reading alongside the trade-off transparency in DE-1 Prioritisation under constraint. SV-5 Engineering metrics and measurement closes the loop by asking whether the strategy is working. Leave SV-6 Organisational design and leading change for last. It is assessed from EMP-II and makes the domain's claim that the organisation is how the strategy gets implemented.

Strategy depends on Delivery & Execution for the mechanics its choices turn into: DE-1 Prioritisation under constraint for the portfolio, DE-2 Estimation, planning, and honest commitments for the commitment and DE-5 Designing how work flows for the flow. It depends on Technical Judgment for the technical strategy, TJ-1 Evaluating architectural decisions and their organisational consequences, and for the AI decisions that now sit inside economics and metrics, TJ-5 AI-assisted engineering. The people the structure is designed around are the subject of PL-6 Leading through leaders. When someone asks for a forecast or a message to be shaded upward, the costly right call is CC-5 Values, integrity, and ethical judgment under pressure.