Strategy also means deciding what to leave out.

01Name the constraint

Start with your company’s situation rather than a list of initi­atives. Is demand too low? Do too few enquiries become orders? Can operations reliably fulfil the orders you already have? Or is prof­itab­ility weak despite high util­isation?

These questions lead to different decisions. More enquiries can put extra pressure on an overloaded business. A new system does not auto­matic­ally improve an offer that fails to meet customer needs.

Formulate a hypothesis you can check: “Proposals stall because technical questions are resolved too late.” Look for supporting evidence and counter­examples. If the evidence is weak, a short invest­igation may be more useful than a major change programme.

02Compare options using the same assumptions

For each initiative, describe its expected contri­bution to the constraint, the effort required, prerequis­ites and key uncer­tain­ties. Include improving an existing process or making no change for now.

• Benefit: What should change for customers or operations?
• Evidence: What supports that expect­ation?
• Effort: Which internal people and external costs are required?
• Dependency: What must be clarified or completed first?
• Revers­ibility: How difficult would a correction be?
• Risk: What happens if the assumption is wrong?

A scoring model can structure a discussion. It cannot replace a decision. Two options with the same total can carry very different risks. Record the reasoning and show which assumption would change the order.

03Plan with actual capacity

“The team will do it alongside their normal work” is not yet a resource plan. Ask who will actually do the work and which existing task will be reduced or stopped. People with essential specialist knowledge are often already occupied with daily operations.

Plan a manageable stage, for example the next 90 days. That period is a working choice, not a univer­sally correct rule. What matters is being able to assess an outcome before taking on the next major commitment.

04Agree on success and counterevidence in advance

Completing a work package is not the same as achieving a benefit. A deployed system may be an output; less duplicate data entry would be the intended benefit. Define them separately.

Simplified illus­tration, not a client case: A company believes that resolving technical questions faster will improve proposal handling. It tests a fixed clari­fica­tion meeting with clear ownership. It measures the time until a complete answer and the number of unresolved questions, rather than merely counting meetings.

Record when you will review the results and what would contradict the assumption. A trial can be useful even if it does not produce the hoped-for improve­ment: it can prevent you from continuing to fund an assumption the evidence no longer supports.

05The decision on one page

1. Starting point: Which constraint is supported by evidence, and what remains an assumption?
2. Objective: Which benefit are we pursuing in the next stage?
3. Choice: Which initiative takes priority, and why?
4. Deferral: What are we explicitly not starting yet?
5. Resources: Who will work on it, with which budget and time freed up?
6. Evaluation: Which outputs and benefits will be checked, and when?
7. Recon­sider­ation: What would cause us to change course?

Share the decision with the people affected. They should understand the sequence and be able to raise conflicts. Strategy becomes visible in everyday work when everyone knows how a new idea will be assessed.

Our strategy and management consulting supports the comparison of options. Imple­ment­ation may start with project management or a targeted improve­ment to your organ­isation and processes.