Skip to main content

PART IV: Analysis: Frameworks Are Optional

PART IV: Analysis: Frameworks Are Optional

One of the most important lessons for developing case-solving judgment is that you don't have to use a framework. Frameworks are tools, not requirements. Sometimes a framework will help you see something that would otherwise be difficult to identify. Sometimes a simple comparison, calculation, customer analysis, or observation from the case will produce a stronger insight than a formal framework. For example, if the case tells you that:

  • sales have declined;

  • prices have remained stable;

  • customer volume has fallen;

  • a major competitor has entered the market.

You may not need to build a SWOT analysis to recognise that competitive pressure and declining customer demand deserve investigation. Likewise, if a financial calculation clearly demonstrates that an initiative produces a negative NPV, you don't need another framework to tell you that the investment destroys value under the assumptions used. The key question is therefore not:not "Whatwhat framework haven't we used?" It is:is "Whatwhat do we still need to understand?" Use a framework when it helps you answer an important question, uncover an insight, compare alternatives, or support your recommendation. Don't use one simply because:

  • it is familiar;

  • it appears in a textbook;

  • another team might use it;

  • you think judges expect it;

  • you want to make the analysis look more sophisticated.

Sometimes the most sophisticated case-solving decision is knowing when not to use a framework.

The MAD Skills Rule

Use the tool that produces the best insight not the tool that looks the most impressive.

Your judges are not awarding points for the number of frameworks you complete. They are evaluating whether you understand the case, identify the important issues, develop meaningful insights, and use those insights to support a strong decision.

Back to top