Skip to main content

PART III: Closing Reflections - From Frameworks to Judgment

You now have a powerful collection of tools for understanding a business and the environment in which it operates. But remember: The objective was never to learn eight frameworks. The objective was to become better at understanding businesses. Each framework gives you a different lens:

  • SWOT helps organise internal and external factors into strategic choices.

  • PESTLE helps you understand the external forces shaping the environment.

  • Porter’s Five Forces helps you understand competitive pressure and industry structure.

  • Value Chain Analysis helps you understand where value is created, lost, and strengthened.

  • VRIO helps you understand capabilities and potential competitive advantage.

  • Business Model Canvas helps you understand how the organisation creates, delivers, and captures value.

  • McKinsey 7S helps you understand whether the organisation is aligned to execute its strategy.

  • Stakeholder Analysis helps you understand the people and groups who influence, and are influenced by, the decision.

The real power comes when you connect these perspectives.

From Environment to Action

Consider how the frameworks can build on one another: PESTLE: What is changing outside the organisation? ↓ Five Forces: How does that change competitive pressure? ↓ Value Chain: Where does the organisation create or lose value? ↓ VRIO: What capabilities can create or protect advantage? ↓ Business Model Canvas: How does the business model need to change? ↓ 7S: What must change inside the organisation to execute? ↓ Stakeholders: Who must support, enable, or respond to the change? ↓ SWOT: How do these insights come together into strategic choices? ↓ Strategy: What should the organisation do?  This is the real purpose of frameworks. Not to produce more analysis. To create a clearer path from understanding to action. Understanding → Insight → Choice → Action. 

The Framework Selection Test

Before using any framework in a case competition, ask five questions:

  1. What question am I trying to answer? If you cannot clearly state the question, you probably are not ready to choose the framework.
  2. Is this the right tool for the question? Don't use a familiar framework simply because you know how to complete it.
  3. What evidence do I have? A framework should be grounded in the case. Don't manufacture inputs simply to fill the boxes.
  4. What insight does it produce? If you cannot identify the insight, the framework probably isn't helping.
  5. How does the insight affect our decision? If the answer does not influence your alternatives, recommendation, or implementation plan, ask whether the analysis is necessary.

This is the difference between doing analysis and using analysis.

The Framework Reflection

Step back from the individual frameworks and consider the progression you have just worked through.

  • External Environment
    • PESTLE: What is changing around the organisation?
  • Industry
    • Five Forces: What competitive pressures shape the organisation's environment?
  • Internal Activities
    • Value Chain: Where is value created, lost, and strengthened?
  • Capabilities
    • VRIO: What can the organisation do better, differently, or more defensibly?
  • Business Model
    • Business Model Canvas: How does the organisation create, deliver, and capture value?
  • Organisation
    • McKinsey 7S: Is the organisation aligned to execute the strategy?
  • Stakeholders
    • Stakeholder Analysis: Who must support, enable, or respond to the strategy?
  • Strategic Synthesis
    • SWOT: How do these insights come together into strategic choices?

The frameworks are different, but they are not isolated. The best case analysis moves between these perspectives, looking for connections, contradictions, gaps, and implications.

From Frameworks to Judgment

Take a step back and consider your own development as a case solver.

  1. Which framework in this section do you find most useful? Why?

  2. Which framework are you most likely to misuse?

  3. Which framework is most useful for understanding the external environment?

  4. Which is most useful for understanding the organisation itself?

  5. Which is most useful for understanding implementation?

  6. How can two frameworks provide different perspectives on the same problem?

  7. When might using a framework actually make your analysis worse?

  8. How do you decide when not to use a framework?

  9. Which framework would you consider first when entering an unfamiliar case? Why?

  10. Which framework would you consider last before making a recommendation? Why?

  11. How do the frameworks complement rather than replace one another?

  12. What evidence would you need before trusting the conclusions generated by a framework?

  13. Think about a case you have previously solved. Which framework might have revealed an insight you missed?

  14. If you had only three analytical tools available during a case competition, which would you choose?

  15. The ultimate MAD Skills question: Are you using the framework because the case needs it, or because you know how to use it?

That last question is worth remembering. Because framework knowledge is relatively easy to acquire. Framework judgment is much harder.

The Frameworks-to-Judgment Test

Complete these sentences:

  • I should use PESTLE when...

  • I should use Five Forces when...

  • I should use Value Chain when...

  • I should use VRIO when...

  • I should use Business Model Canvas when...

  • I should use 7S when...

  • I should use Stakeholder Analysis when...

  • I should use SWOT when...

  • I should not use a framework when...

That final sentence may tell you more about your development as a case solver than all the others combined.

Discover Your MAD Skills Principle

Framework mastery is not knowing how to complete the framework. It is knowing when to use it, what question it should answer, what insight it should produce, and what decision that insight should influence.

Frameworks are not answers. Frameworks are thinking tools.

The MAD Skills Framework Rule

  • Don't ask: "What framework can I use?"
  • Ask: "What do I need to understand?"
  • Then ask: "What tool will help me understand it?"
  • And finally: "What does that understanding allow me to do?"

That is the difference between using frameworks and thinking with frameworks.

Deciphering Case Characteristics

This brings us back to one of the most important ideas in the Discover Your MAD Skills approach:

Every case is different.

  • A growth case may require market and competitive analysis.
  • A turnaround may require financial and operational analysis.
  • A market-entry case may require PESTLE, Five Forces, market sizing, and capability analysis.
  • A transformation case may require Business Model Canvas, 7S, stakeholder analysis, and implementation planning.
  • An innovation case may require customer analysis, creative thinking, business model analysis, and financial feasibility assessment.

There is no universal framework stack. The characteristics of the case should determine the tools you use. That is one of the most important MAD Skills you can develop.

Final Challenge: Audit a Case You Have Already Solved

Take a case you have previously solved. Without looking at your original analysis, answer:

  • What did we actually need to understand?

  • Which frameworks did we use?

  • Which frameworks actually created insight?

  • Which frameworks were unnecessary?

  • What important question did we fail to answer?

  • What did we learn from the analysis that actually changed our thinking?

  • If we solved the case again, which tools would we choose?

  • Which tools would we deliberately leave out?

Then ask yourself the most important question: Did we use frameworks to understand the case, or did we use the case to complete frameworks? Your answer will tell you a great deal about your team's analytical maturity.

Key Takeaway

Frameworks don't win case competitions. Insight does. And insight comes from knowing:

  • What to look for.
    What to question.
    What to connect.
    What matters.

The goal is not to become someone who can complete every framework. The goal is to become someone who can look at an unfamiliar situation, identify what matters, choose the right tools, generate meaningful insight, and turn that insight into a decision. That is the beginning of becoming a more sophisticated case solver. Frameworks are not answers. Frameworks are thinking tools.

No Comments
Back to top