Description
Two written artefacts for aligning many teams: a strategy for one challenge (diagnosis, guiding policies, actions) and an aspirational vision for an area, produced through interviews and pre-alignment.
When an organisation outgrows direct oversight, written strategy and vision documents align teams better than meetings. A strategy addresses one challenge with Rumelt's kernel: a diagnosis that honestly names factors and constraints (including organisational ones), guiding policies that state the approach and its trade-offs, and coherent actions that follow. A vision describes a future in which today's trade-offs no longer conflict, written far enough ahead that details illustrate rather than constrain: a one or two sentence statement, a value proposition starting from users, the capabilities needed, constraints solved and remaining, references and a one-page narrative. Reilly's process adds an executive sponsor, a core group of two to four, broad interviews, decisions recorded with trade-offs, rough consensus with a pre-agreed tiebreaker, nemawashi (one-to-one pre-alignment before any meeting) and a memorable story. Drafts are tested on readers until confusion is minimal.
Attributes
- Discipline
- Design & Product Practice
- Loss type
- Active
- Stage
- Strategy
- Data
- Qualitative
- Effort
- Weeks
Steps
- Check that a document is needed; if teams are already aligned, use a lighter artefact.
- Join any existing effort, secure an executive sponsor and form a core group of two to four with a weekly time commitment.
- Agree scope and document type (strategy for a specific challenge, vision for an area) with the sponsor.
- Interview widely, gather ideas without judgement, and write the diagnosis or the vision's value proposition starting from users.
- Identify the few key decisions, decide each with recorded trade-offs, and draft guiding policies and actions (or capabilities and constraints for a vision).
- Pre-align stakeholders one to one (nemawashi), test drafts on several readers, and record unresolved disagreements in the text.
- Launch with executive endorsement and an official home, write a one-page narrative or slogan, and refresh yearly.
Sources
- An Elegant Puzzle (Larson, 2019)
- The Staff Engineer's Path (Reilly, 2022)
Also known as
- Strategy and vision documents (diagnosis, guiding policies, actions; vision components)
- Creating a technical vision or strategy document
- Technical strategy
- Technical vision
- Strategy kernel (diagnosis, guiding policy, coherent actions)
- Nemawashi
Categories
- Design
- Design & Product Practice