A software company announces that larger organisations will become its main growth market. Product begins discussing administration and reporting capabilities, Sales pursues bigger accounts, and Engineering investigates stronger access controls. The existing business still serves smaller customers and provides most of the revenue.
At the next planning meeting, a large prospect requests a custom workflow. Sales sees an opportunity to advance the strategy. Product worries that the work will delay capabilities several prospects need, while Engineering identifies a maintenance commitment the proposed contract does not cover.
The strategic intent gives this discussion a direction. It does not settle the choice. The company needs to decide which customers it intends to serve, what kind of offer it can support, and how this opportunity compares with other uses of its capacity.
Strategic decisions make those commitments specific. Their relationship with intent matters because a series of reasonable local choices can gradually produce a business different from the one leadership described. The response should be to examine the choices and their context, rather than assume every deviation is a failure of commitment.
Making the Intended Direction Specific Enough to Use
An enterprise focus needs more definition before it can guide a contract decision. Larger organisations differ in how they buy, use, and support software. Some need a standard product with additional controls; others require substantial integration or ongoing specialist services.
The company should establish which needs it aims to meet and why it believes the offer can be attractive. That account might identify a particular customer group, a problem the product solves well, and capabilities that distinguish it from alternatives.
The existing business belongs in this account too. Maintaining smaller customers may fund the transition and preserve a useful market. The strategy should explain whether that segment will remain part of the intended model, receive a narrower offer, or eventually move elsewhere.
These choices help interpret the prospect’s request. A custom workflow could provide evidence about a recurring need, or it could take the company towards a service model it does not intend to operate. Deal size alone will not distinguish those possibilities.
Intent remains useful when it gives teams a common basis for judging opportunities. It can leave room for investigation without being so broad that every proposal appears equally consistent with it. Unresolved questions should be visible, with owners and a route to a decision.
Identifying Which Choices Carry Strategic Consequences
A decision becomes strategically important through its effect on the business, its dependencies, or the commitments it creates. A major contract may shape product direction for years. A small technical change can also have lasting consequences if it establishes an interface many customers will depend on.
For the requested workflow, the company needs to consider more than implementation effort. It should examine ongoing maintenance, support, permissions, future compatibility, and whether the capability can become part of a shared product. These obligations affect the value of the deal and the organisation required to serve it.
Not every choice needs executive approval. Teams can handle routine decisions within an agreed scope, using the strategic context and relevant standards. Escalation becomes appropriate when a proposal changes the customer promise, creates a material obligation, or competes with resources beyond the team’s authority.
Clear decision rights should identify who supplies expertise, who can approve the commitment, and which requirements constrain it. A specialist objection needs examination; it should not disappear simply because the opportunity has been labelled strategic.
This makes distributed decisions more coherent without requiring leadership to manage every detail. The organisation can concentrate attention on choices whose consequences reach beyond the local task while keeping ordinary work moving.
Comparing Alternatives Before Approving the Opportunity
The company has several possible responses. It could build a general capability, provide a limited integration, offer a paid service with defined boundaries, revise the contract, or decline the request. The preferred option depends on customer value, strategic fit, cost, and risk.
The assessment should include what happens if the company continues its current roadmap instead. The prospect’s revenue is visible, but the delayed capability may serve several other customers. Opportunity cost needs an account of the displaced work and its expected benefit.
The Green Book’s appraisal guidance provides a structured example of comparing options through costs, benefits, risks, and objectives. A commercial company need not apply public-sector appraisal rules to use the underlying discipline of examining alternatives and assumptions.
Evidence will remain incomplete. Sales may have a strong indication of demand without a signed agreement. Product may suspect the requirement is common without enough customer research to be confident. The proposal should distinguish those positions from established facts.
A limited investigation can help where it could change the decision. The company might validate the need with other suitable customers or test a technically uncertain integration. If the contract must be decided sooner, leadership should record the uncertainty it is accepting and the limits of the commitment.
Reading Budgets and Hiring Plans in Context
Budgets and staffing decisions provide important evidence of commitment. If the company intends to build an enterprise offer, it needs access to the relevant product, technical, commercial, and operating capabilities. A persistent absence of necessary capacity deserves investigation.
The percentage of total spending assigned to a new initiative does not establish sincerity on its own. Existing services may have unavoidable operating costs, and a new opportunity may initially need only a small trial. A modest allocation can be appropriate for the decision stage and the uncertainty involved.
The useful question is whether the approved work has adequate resources and a credible path to the next decision. If the company expects a general enterprise release while funding only a prototype, the mismatch should be made explicit. Leadership can change the scope, resources, or expectation.
Hiring needs similar interpretation. A capability may be developed internally, bought, provided by a partner, or deferred. An unfilled specialist role may indicate a delivery risk without proving that the whole strategy has changed. The plan should explain how the relevant work will be performed in the meantime.
The budget is therefore part of a decision record, alongside commitments, timing, and operating constraints. Reviewing those elements together gives a more reliable picture than treating one ratio as the definitive statement of strategy.
Making Exceptions and Stopping Decisions Explicit
The company may approve the custom workflow as an exception. That can be reasonable if the expected value justifies a bounded commitment. The record should explain why it differs from the standard offer, who owns the obligations, and when its costs will be reviewed.
Exceptions become harder to manage when they accumulate without a shared account. Several individually attractive deals can create an extensive support model that the company never deliberately chose. A periodic review can identify whether the pattern should become a supported offer, be constrained, or stop.
New investment also needs room in the plan. Trade-offs may involve reducing scope, deferring work, obtaining additional capacity, or closing an initiative. Each has transition costs and consequences for people whose expectations were based on the earlier commitment.
Stopping does not automatically release resources immediately. Customer agreements, access, data, and support obligations may remain. A product retirement may require a migration period and a maintained historical service. Those requirements should be assessed before savings are assumed.
A stopping decision also needs an explanation that distinguishes changed priorities from poor performance. Work can have been useful and competently delivered while no longer being the best use of future capacity. That distinction makes the decision more accurate and gives staff a clearer basis for carrying useful knowledge forward.
Reviewing the Pattern Without Freezing the Strategy
Leadership should review a meaningful sample of decisions alongside their outcomes. For the enterprise direction, this could include major contracts, product allocations, capability investments, and exceptions to the standard offer. The aim is to understand whether the commitments reinforce the intended model.
A decision that appeared inconsistent may reflect an operating obligation or a useful opportunity. Repeated divergence may indicate unclear criteria, conflicting incentives, or evidence that the original intent needs revision. The review should investigate those explanations rather than score every departure as noncompliance.
Measures can help, but a percentage of spending labelled strategic is easy to overinterpret. The company should examine what capability became available, how customers used it, what obligations increased, and whether the commercial assumptions held. Investment classification is supporting evidence rather than the outcome itself.
The execution results can legitimately change the direction. Customers may prefer a different purchasing model, or the company may discover that its strongest advantage lies in a narrower segment. Revising intent after that finding can improve coherence.
What matters is that the change becomes an explicit choice. Leaving the old direction in presentations while approving a different business through successive exceptions makes future decisions harder. Staff need a dependable account of what the organisation is now trying to achieve and why.
For this company, strategic intent and strategic decisions do different work together. Intent explains the direction and the reasons for it. Decisions define the customer promises, capabilities, and resource commitments through which that direction is pursued. Review connects both to evidence, giving the organisation a way to remain purposeful without pretending its first assumptions will always hold.
