Strategy
ストラテジー
A strategy is a coherent set of choices about where to compete, what advantage to pursue, and what not to do. It guides decisions under constraints; it is not a goal, schedule, or task list.
What it means
Strategy connects an intended outcome to a defensible way of achieving it. In an organization, it normally identifies the arena to serve, the problem or opportunity to prioritize, the basis of advantage, the capabilities and resources that must reinforce one another, and the trade-offs that preserve focus. Its boundary matters: a vision describes a desired future, a goal states a result, a plan organizes execution, and tactics are local actions. A strategy sits between aspiration and execution by making consequential choices that remain useful when conditions change.
How to calculate it
Strategy has no universal formula and should not be converted into a fake score. Evaluate it as a decision logic: are the choices explicit, mutually reinforcing, feasible with available capabilities, grounded in evidence, and linked to observable outcomes and review triggers? Quantitative models can test assumptions, but they do not calculate strategy itself.
What counts / what does not
Write the boundary before approving resources so that a broad aspiration does not masquerade as a strategy. Include | chosen customers or arena, priority need, value proposition, advantage logic, required capabilities, major trade-offs, assumptions, and success evidence. Exclude | slogans, revenue targets by themselves, undifferentiated lists of initiatives, detailed calendars, and budgets that do not explain why these choices should work. State uncertainty | name the external conditions and customer beliefs that could invalidate the choices, plus the signal and date that will trigger a review.
| Item | Treatment |
|---|---|
| Include | chosen customers or arena, priority need, value proposition, advantage logic, required capabilities, major trade-offs, assumptions, and success evidence. |
| Exclude | slogans, revenue targets by themselves, undifferentiated lists of initiatives, detailed calendars, and budgets that do not explain why these choices should work. |
| State uncertainty | name the external conditions and customer beliefs that could invalidate the choices, plus the signal and date that will trigger a review. |
What moves the number
Use strategy to resolve competing demands, not to decorate an annual plan. Diagnosis | identify the few customer, competitive, regulatory, or capability facts that shape the decision. Choice | select an arena and advantage, then make exclusions clear enough to stop lower-priority work. Coherence | align product, distribution, pricing, operations, and talent so that one choice strengthens the others. Learning | attach leading indicators and disconfirming evidence, then revise choices when assumptions fail rather than defending sunk cost.
| Driver | Metric impact |
|---|---|
| Diagnosis | identify the few customer, competitive, regulatory, or capability facts that shape the decision. |
| Choice | select an arena and advantage, then make exclusions clear enough to stop lower-priority work. |
| Coherence | align product, distribution, pricing, operations, and talent so that one choice strengthens the others. |
| Learning | attach leading indicators and disconfirming evidence, then revise choices when assumptions fail rather than defending sunk cost. |
When it helps
Resource allocation becomes explainable because teams can connect funding and headcount to a chosen advantage instead of to the loudest request. Product and go-to-market decisions become faster because the target customer, value proposition, and explicit exclusions provide a common filter. Performance reviews become more useful when leaders distinguish flawed execution from a strategic assumption that evidence has disproved.
- Resource allocation becomes explainable because teams can connect funding and headcount to a chosen advantage instead of to the loudest request.
- Product and go-to-market decisions become faster because the target customer, value proposition, and explicit exclusions provide a common filter.
- Performance reviews become more useful when leaders distinguish flawed execution from a strategic assumption that evidence has disproved.
How to use it
- A strategy must contain choices and trade-offs; a collection of desirable outcomes is only an aspiration.
- The strategy should be stable enough to coordinate work but revisable when named assumptions no longer hold.
- Plans and tactics should trace back to the strategy, while the strategy should not collapse into their level of detail.
- Advantage depends on a reinforcing system of activities, not a single feature that competitors can readily copy.
- Good strategic review asks what evidence would change the choice, not merely whether scheduled work was completed.
Decision cautions
Do not call a document approved until owners can name the choice, the exclusion, the evidence, and the review trigger. A vague strategy lets every initiative claim alignment and therefore provides no real prioritization. A rigid strategy can survive after its assumptions fail; schedule periodic reviews without turning them into automatic rewrites. A strategy copied from another organization may import different customers, capabilities, constraints, and economics.
- A vague strategy lets every initiative claim alignment and therefore provides no real prioritization.
- A rigid strategy can survive after its assumptions fail; schedule periodic reviews without turning them into automatic rewrites.
- A strategy copied from another organization may import different customers, capabilities, constraints, and economics.
Example
A workflow software company wants growth in Japan. Its goal is to reach a defined recurring-revenue milestone, but that number is not its strategy. After interviews and win-loss analysis, it chooses operations teams at 50-to-500-person service businesses, promises rapid deployment through Japanese templates and accounting integrations, and declines custom enterprise projects that would slow the product. The supporting plan assigns quarterly integration releases, partner recruitment, onboarding changes, owners, and budgets. Campaign copy and a webinar are tactics. The team tracks activation time, qualified conversion, retention, and requests for excluded custom work. If target accounts do not value fast deployment after two review cycles, leaders revisit the strategic premise rather than merely adding more campaigns.
Compare with
Strategy | establishes where to play, how to create advantage, and which trade-offs protect focus. Plan | translates a direction into sequenced actions, owners, resources, milestones, and contingencies. Tactic | is a specific action used in a local situation, such as a campaign, negotiation move, or release technique. Goal | names the result to achieve; it does not by itself explain the distinctive route or the sacrifices required.
| Metric | Difference |
|---|---|
| Strategy | establishes where to play, how to create advantage, and which trade-offs protect focus. |
| Plan | translates a direction into sequenced actions, owners, resources, milestones, and contingencies. |
| Tactic | is a specific action used in a local situation, such as a campaign, negotiation move, or release technique. |
| Goal | names the result to achieve; it does not by itself explain the distinctive route or the sacrifices required. |
Common mistakes
- Strategy is not a long list of priorities. If everything remains important, the document has avoided the central choice.
- Strategy is not prediction. It makes assumptions about an uncertain future and defines how those assumptions will be tested.
- Strategy is not reserved for executives. Functional teams need choices that support the organization-level direction without inventing a conflicting one.
- Execution quality cannot rescue a strategy whose customer or advantage premise is false, although weak execution can hide whether the premise was sound.
Frequently asked questions
How short can a strategy be?
Length is not the test. A concise strategy is useful if it states the arena, advantage logic, trade-offs, assumptions, and evidence clearly enough to guide real decisions.
Is a roadmap a strategy?
Usually no. A roadmap is a time-oriented plan. It should show how scheduled investments express strategic choices, but the sequence alone does not explain those choices.
How often should strategy change?
Review it on a defined cadence and whenever a material assumption fails. Do not change it for every short-term fluctuation or preserve it despite sustained contrary evidence.
Can a team have its own strategy?
Yes, when its choices support the higher-level strategy, stay within delegated decision rights, and make any cross-team trade-offs explicit.