> ## Content Index
> Fetch the complete content index at: https://www.associateshandbook.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Understand the problem before you touch the data
- URL: https://www.associateshandbook.com/understand-the-problem-before-you-touch-the-data/
- Published: 2026-10-13T09:21:39.000Z
- Updated: 2026-10-13T09:21:38.000Z
- Author: Moritz
- Tags: Problem Solving, Concept

*You can only deliver a good result when you understand the Problem. During the interview, you have been trained to do that. Apply this knowledge now.*

Before you open Excel or start building slides, build a working model of the company you are working for. What exactly is the product or service? How do they make money? What drives cost? What strategic questions are they facing? Who competes with them and what actually differentiates them?

You do not need a perfect view in week one. You need something coherent enough to anchor your thinking. Without it, every analysis you run risks being disconnected from the reality of the business, and you will not notice until somebody senior points it out in a meeting.

**Seven questions** 

**1\.** What is the product or service?

**2\.** Who pays, and why do they pay?

**3\.** Is the revenue recurring?

**4\.** Who holds the pricing power, and how do prices pass through from supplier to company to customer when inflation moves?

**5\.** What drives cost: people, materials, energy?

**6\.** What are the main dependencies: suppliers, politics, regulation, raw materials?

**7\.** What stops a competitor from simply copying this?

At the start of a case you will not have days for this. You might have a few hours, possibly on the train there. Work outward from company to industry to recent developments, and keep the unanswered questions in your pocket for the first free conversation.

AI has made this dramatically cheaper. Build one research prompt covering the seven questions and reuse it on every case. Push the output plus the annual report into NotebookLM and generate an audio summary for the commute, or hold a voice conversation with the model on the way in. An hour of this, done well, means you arrive knowing more about the industry than several people on the team.

If you want to go deeper on what makes a business good rather than merely functional, [Quality Investing ](https://link.amazon/B0cCN9AhJ?ref=associateshandbook.com)by Cunningham, Hargreaves and Eide is the best short summary I know. And if your firm offers it, half a year on commercial due diligences is the fastest training available: you see dozens of companies across industries, stages and dynamics.

**Then understand the task itself**

What do you need to do? Why are you doing it? How does it fit the broader case? What outcome is expected at the end?

The rule of thumb: **understand the context one or two levels above your own task.** If your manager asks you to size a market, know what decision the team is trying to make with that number. If you are asked to analyse costs, know how that will feed a storyline or a recommendation.

This extra level of context removes an enormous amount of misalignment, and it is the difference between an associate who produces the right analysis and one who produces a correct analysis of the wrong thing.

**Look for old work before you build anything**

During ramp-up, hunt for previous case decks, old analyses, and the sources they used. Save the key slides and reuse the formats.

Most consulting output is built on proven logic and templates. Your job is to adapt them to the current problem rather than start from zero out of pride. Copy where you can and update intelligently. The time you save here is the time you spend on the thinking that is actually specific to this client.

**And stop when something does not click**

If something does not make sense to you, stop and think it through. There is always a reason. Maybe you are missing context. Maybe the task was phrased loosely. Maybe your approach is wrong.

Finding that reason is your responsibility, and the fastest route is to go back with a clear question or a proposed interpretation: “Here is how I understand the task, is that right?”

That small habit is most of what separates a reliable problem solver from somebody who executes accurately in the wrong direction. It costs two minutes and it is welcome at any point in the first day.

**START THIS WEEK**

**1\.** Answer the seven questions about your current client. Where you cannot answer, mark it and ask somebody this week.

**2\.** For your current task, write one sentence describing the decision the team will make with your output. If you cannot, that is your next question for your manager.

**3\.** Spend thirty minutes in your firm’s knowledge base looking for a deck from a similar case.

**If you cannot explain how the client makes money, you are not ready to analyse anything about them.**