A technology investment paper can describe a solution in considerable detail and still leave a board unsure what it is being asked to approve. The essential job of the paper is to connect a defined commitment with a business outcome, credible alternatives and the conditions needed for success.
Directors need enough information to exercise judgement. Management needs a clear mandate it can execute and report against. A good paper serves both purposes.
Make the requested decision explicit
Put the decision near the beginning. State the amount and scope of the proposed commitment, the authority being requested and what approval would allow management to do next.
Distinguish an approval to investigate from an approval to implement. A request to fund a defined first stage should explain what later commitments remain open. If approval creates obligations beyond that stage, make them visible.
Describe the business outcome in terms that can be observed. Faster customer response, more reliable production information or reduced administrative effort can each be worthwhile, but the paper needs to explain who benefits and how the improvement will be established.
The board should be able to trace the requested investment back to that outcome. If it cannot, more technical detail is unlikely to resolve the gap.
Show the alternatives management considered
Explain the credible options, including improving the current arrangement, reducing the ambition or deferring the decision. Describe the consequence of leaving the problem unresolved so that the current position receives the same scrutiny as the proposed change.
Compare options against common criteria: expected business value, remaining cost, operational disruption, delivery capability and important risks. State why management recommends one option and where another might be preferable.
Consider a hypothetical industrial-services company seeking approval for a new scheduling platform. It wants to reduce missed appointments and improve utilisation. The current process also suffers from incomplete job information and late customer changes.
The paper could compare a full replacement with improving data and dispatch practices in the current system, or introducing a narrower scheduling tool for one service line. It should explain which problems each option addresses and which remain the responsibility of the business.
That comparison gives directors a basis for judging whether the proposed commitment is proportionate to the outcome.
Expose the assumptions behind the value
Show how the expected benefit will arise. If the case depends on increased utilisation, explain the operating changes required and who will make them. If it depends on time saved, explain how the released capacity will be used.
Separate measured facts from estimates. State the baseline, the assumptions used and the gaps in the evidence. Consider what happens if adoption is slower, integration costs more or the expected benefit is smaller.
Include the costs beyond the initial purchase: internal effort, data preparation, transition, training, support and ongoing ownership. A supplier quotation covers only the commitments included in that quotation.
For the scheduling example, the value might depend on dispatchers having accurate job durations and authority to change allocations. If those conditions are unresolved, the investment case should show what it takes to establish them. They should not disappear into a general statement about change management.
Explain whether the business is ready
Name the executive accountable for the outcome and the people responsible for delivery and adoption. Show whether the business has the capacity to do the work alongside its existing commitments.
Identify material dependencies. These may include access to suitable data, a shutdown window, supplier capacity or a decision on operating practices. Explain how unresolved dependencies affect timing and the requested commitment.
Summarise the technical issues that affect the decision, with supporting detail available separately. Directors need to understand the consequences of integration complexity, security requirements or a difficult migration. A long inventory of technical components can obscure those consequences.
In an industrial setting, the transition deserves particular attention. Explain how operations will continue, which changes need operational approval and what happens if the new arrangement is not ready when expected.
Agree what the next review will establish
Define the evidence management will bring back and the decisions that evidence will support. Reviews should track business outcomes and readiness as well as delivery activity.
A completed configuration or signed contract can be a useful milestone. It does not establish that the scheduling example has improved service. A later review would need evidence about appointment reliability, utilisation and the effort required to maintain the process.
Where uncertainty is material, consider staged commitments. Explain what can be learnt in the first stage, what it costs and what would justify the next one. Be candid about any commitments that would make changing direction difficult.
Before submitting the paper, ask a colleague outside the project to identify the requested decision, strongest alternative, critical assumption and next review point. If those are hard to find, revise the paper. The board should leave the discussion with a clear choice, and management with a mandate whose limits and success measures are understood.
If an important technology investment needs a clearer decision case, tell us what is being considered. We can discuss whether a Decision Sprint would help assess the options, or Shape would help develop a chosen direction.
Start an enquiry