Episode 27: Some Thoughts on Reading and Resolving the Case

February 12, 2025

Over the past few weekends, I have had the opportunity to judge and mentor at the Haskayne School of Business Digital Innovation Challenge and Innovatank Cross-Continental Case Competition. This week, I will also be starting a series of case-solving workshops at Hong Kong Polytechnic University. As I observed and worked with the participating teams in these competitions and planned the upcoming workshops, two key points have been on my mind: the approach to reading cases and the process that teams can adopt to solve them.

Reading the Case

This topic will be a focus of my upcoming workshop, and it’s also something that received positive feedback in a post shared with the teams at the Cross-Continental Case Competition. Typically, case writers use the introduction to outline the key issue or problem, at least at a high level, along with identifying the client. This introduction often includes key characters, although some may be introduced later, especially if additional characters are essential to the case. From this information, case solvers should be able to start defining the problem statement and determining the positioning they should adopt. They should also clarify what business the client is engaged in.

Next comes the background and history section, which is crucial for understanding not only the client's business but also the corporate culture. This section typically includes the client’s vision, mission, and goals, along with how these have evolved over the company's history. It is also where additional key characters might be introduced, as well as existing strategic plans.

Following this, much of the content focuses on financial details, external perspectives, and further explanations of existing plans. In this section, the author examines the specifics of the client's problem and may offer hints or suggestions for potential solutions. The information provided here should help the case solver better understand the client's business model and revenue generation methods. It’s important to pay attention to the questions presented in this section, as they may not be straightforward inquiries. As I mentioned in earlier discussions, my expectation as a judge is that those questions will have answers.

Next, we have the summary. This section usually addresses key questions that not only need to be answered but should also enhance the case solver's understanding of the problem. It can lead to insights that inform potential solutions, and it may include a paragraph outlining the case solver's specific task.

Lastly, and most importantly, are the appendices. I recommend that my teams review these first, as they contain information that the author deems significant and often holds important clues. In well-structured cases, the appendices can greatly influence the interpretation of the situation. One of my favourite cases, for example, is understood completely differently if the financial statements included in the appendices are not examined before the main text. Neglecting to review them first often leads to missing the root problem.

The Resolution Process

The resolution process can differ among teams, but there are some common elements. I have discussed many of these elements in previous episodes and had the pleasure of speaking to students at Hong Kong Polytechnic University last night about the case-solving process. I also outline this process in a video on my YouTube Channel at https://youtu.be/LmF5SI24Etw.

During my talk last night, the question asked was not about the process itself, but rather about how to foster teamwork.

I addressed this question in two parts. The first part involves organising activities that allow team members to get to know each other on both professional and personal levels. The goal is not only to build familiarity among team members but also to identify each other’s strengths and weaknesses, as well as to find ways to help colleagues manage the stresses that come with case-solving. The second part aims to help the team understand different leadership styles and encourage the rotation of leadership responsibilities as the team works together on case resolutions over time.