PART III: Build The Case-Solving Architecture

Once you have deciphered the case and understood the organisation, you need a structure for turning that understanding into a decision. Case solving can feel chaotic.

• There is information everywhere.
• There are multiple problems.
• There are competing perspectives.
• There are frameworks to consider.
• There are financial questions.
• There are strategic alternatives.
• There are implementation challenges.
• There is always a clock running.

A strong case-solving architecture gives the team a way to organise that complexity. The architecture in this manual is: Decipher → Analyse → Develop → Decide → Recommend → Implement → Measure → Communicate. This is not a checklist to complete and forget; it is a thinking architecture.

• You may move forward.
• You may move backwards.
• You may revisit earlier decisions.
• You may discover that an assumption was wrong.
• You may eliminate an alternative because the financial analysis doesn't work.
• You may discover a capability constraint that changes your recommendation.

That is not a breakdown of the process; that is good case solving.