Description: A Strategy on a Page is a single-page summary of an organization's current strategy. It is intended to be easy to create, share, consume, and update. Compared with traditional longer strategy documents created by committee (and then typically rarely referred to), the Strategy on a Page method is meant to encourage active communication about living, changing strategy.
Goals:
Make it easy for teams to have a meaningful strategy discussion without a lengthy or complex document
Typical scenarios include:
A team seeks to share its strategy with its sponsors, customers, partner teams, etc.
Roles: A strategy on a page can be developed in a workshop setting by a facilitator leading a group responsible for an area they wish to describe strategy for. Once published, each strategy should have an owner; other contributors may edit the strategy based on some defined process.
Steps: In a typical initial strategy workshop, a facilitator leads discussion of and records notes on high level drivers and outcomes (defined below). The group may be able to lead initial existing or proposed initiatives toward the outcomes. This information is sufficient for a first draft, which the group can revise in further sessions or collaboratively online.
Artifacts: A basic Strategy on a Page template includes:
The template can be expanded to include items such as:
Improved communication is one of the fundamental goals of this method. Once they are drafted strategies should be kept where they are readily available to team members, peer teams, and stakeholders such as customers, sponsors, or investors. Not only should the document be available, it should be actively shared and referred to in team meetings, planning meetings, project reviews, customer advisory boards, etc.
This method is at the level of strategy. A team can then choose to plan in more detail using:
Capability Maps - Focus on what the organization needs to be able to do to execute its strategy
Architecture Methods > Strategy on a Page |
|
Want to help with this page? Please see the Method Contributor Guide. Stewards for this page:
Other contributors:
|