Sign up
Subscribe
Home / Guide: How to Write an Analytical Report Using McKinsey Principles

Guide: How to Write an Analytical Report Using McKinsey Principles

Guide: How to Write an Analytical Report Using McKinsey Principles

1. The Main Idea

An analytical report is not a retelling of facts. Its purpose is to help a manager, client, or investor make a decision.

That is why the report must answer three questions:

  1. What is happening?
  2. What does it mean?
  3. What should be done?

The main principle:

Start with the conclusion. Then explain. Then provide evidence.

This is called Lead with the answer.

The second principle is the Pyramid Principle: the entire argument is built as a pyramid.

At the top is the main conclusion.
Below it are 3–5 key arguments.
Further below are facts, figures, examples, and calculations that prove each argument.

2. What Is Wrong with a Typical Report

An inexperienced employee often writes like this:

“We studied the market. First, we looked at competitors. Then we analyzed prices. Then we spoke with clients. Then we collected advertising data. As a result, it can be said that there are certain opportunities for growth.”

The problem: the reader spends too much time trying to understand where the text is going.

In McKinsey style, it should be written like this:

“The company should enter Market X within the next 6 months because demand has already formed, competition is fragmented, and the project economics allow payback within 12–15 months.”

After that, you can explain the details.

3. Basic Structure of an Analytical Report

A good report usually consists of 7 parts:

  1. Executive summary — a brief main conclusion.
  2. Context and question — what problem we are solving.
  3. Main answer — what we recommend or claim.
  4. Logic of the argument — why this is true.
  5. Evidence — data, calculations, facts, comparisons.
  6. Risks and limitations — what may go wrong.
  7. Recommendations and next steps — what to do next.

4. Executive Summary: How to Write the Main Conclusion

An executive summary is a short 5–10 line summary. It should be understandable even to someone who will not read the entire document.

Formula:

We recommend / believe that [main conclusion] because [argument 1], [argument 2], [argument 3]. To implement this, it is necessary to [key actions]. The main risks are [risks], but they can be reduced through [mitigation measures].

Example:

We recommend launching an MVP of a review platform for the travel market within 3 months. The opportunity is attractive because most competitors in the local market do not verify reviews, users are not confident that existing tools limit bots from travel agencies, and the business model can be monetized through lead generation and premium placement. At the first stage, it is important to have an effective filter for authorized users, and only after that to build traffic, reviews, and a company database. The main risks are low user engagement and weak activity from travel agencies; they can be reduced through newsworthy content, SEO content, and transparent publication rules.

5. The Lead with the Answer Principle

What It Means

You do not need to begin with a long description of the research process. Start with the answer.

Bad:

“As part of the analysis, we studied 25 companies, reviewed prices, compared traffic, and conducted interviews. The results are presented below.”

Good:

“The market is attractive for entry, but only through a niche MVP: a full-scale launch with broad functionality would create unnecessary costs and would not increase the chances of success.”

Why It Works

A manager does not read a report for the sake of the process. They need to quickly understand:

– what decision is being proposed;
– why it is reasonable;
– what the risks are;
– what should be done next.

That is why the first screen, first page, or first slide must immediately communicate the meaning.

6. Pyramid Principle: How to Build a Pyramid of Arguments

The pyramid looks like this:

Main Conclusion

The company should launch Product X as an MVP within 3 months.

Second-Level Arguments

  1. There is unmet demand in the market.
  2. Competitors do not address the client’s key pain point.
  3. The MVP can be launched quickly and cheaply.
  4. The project economics have payback potential.

Third-Level Evidence:

Each argument needs supporting facts.

1. There Is Unmet Demand

– users search for information on Google;
– there are complaints on social media;
– current solutions do not inspire trust;
– interviews confirm the problem.

2. Competitors Do Not Address the Pain Point

– data is fragmented;
– reviews are difficult to verify;
– there is no comparison of companies.

3. The MVP Can Be Launched Quickly

– basic catalog;
– review form;
– moderation;
– SEO pages;
– traffic analytics.

4. There Is Economic Potential

– monetization through leads;
– paid placement;
– advertising formats;
– partner commissions.

7. The Rule of 3–5 Arguments

You do not need to give 12 reasons. A good report usually rests on 3–5 strong arguments.

Optimal structure:

Main conclusion
→ 3 key arguments
→ 2–4 pieces of evidence for each argument

Example:

We recommend not launching the full product immediately, but starting with an MVP.

Why?

  1. The full product will increase timelines and costs.
  2. The main value lies in the ability to build trust.
  3. The MVP will allow demand to be tested before large investments.

8. The MECE Principle

MECE means:

Mutually Exclusive, Collectively Exhaustive.

In other words:

The points do not overlap, and together they fully cover the issue.

This means that arguments should not duplicate each other, but together they should cover the entire question.

Bad:

  1. We have few clients.
  2. We have weak sales.
  3. We have few leads.

These points overlap.

Better:

  1. The problem is lead generation.
  2. The problem is conversion of leads into sales.
  3. The problem is customer retention after the first purchase.

This structure is cleaner: each block is responsible for a separate part of the problem.

9. How to Write Headings

In an analytical report, a heading should not simply name the topic. It should communicate the conclusion.

Bad:

Market Analysis

Good:

The Market Is Growing, but Entry Should Be Through a Narrow Niche

Bad:

Competitors

Good:

Competitors Are Strong in Distribution but Weak in Personalized Service

Bad:

Financial Model

Good:

The Project Can Reach Operating Break-Even with 300–400 Paying Clients

If you read only the headings, they should form a logical storyline of the report.

10. Structure of a Page or Slide

Each page should answer one question and prove one idea.

Page formula:

1. Conclusion Heading

For example:

The main problem is not the product price, but lack of trust in the supplier.

2. Brief Explanation

2–4 lines explaining the logic.

3. Evidence

Figures, table, chart, examples, client quotes, comparison.

4. Decision Implication

What this means for the business.

Example:

If the barrier is trust, discounts will not solve the problem. The company needs to strengthen case studies, guarantees, reviews, and process transparency.

11. How to Write Arguments

A good argument consists of three parts:

  1. Claim — what we believe.
  2. Evidence — why it is true.
  3. Implication — what follows from it.

Example:

Claim: launching the full product now is premature.
Evidence: the key hypothesis — the existence of demand — has not yet been confirmed through real reviews and organic traffic.
Implication: first, the company should launch an MVP, collect user behavior data, and only then invest in complex functionality.

12. How to Work with Data

Data should not merely be present. It should prove the conclusion.

Bad:

The table below presents market indicators for the past 5 years.

Good:

Data from the past 5 years shows that the market is growing unevenly: two segments drive most of the growth, so the launch should focus specifically on them.

Every number must answer the question:

Why is this number needed for the decision?

If a number does not help make a decision, it is better to remove it or move it to the appendix.

13. Typical Forms of an Analytical Report

Option 1. Report for a “Launch or Do Not Launch” Decision

Structure:

  1. Main recommendation.
  2. Why the question matters now.
  3. Size of the opportunity.
  4. Client pain point.
  5. Competitive situation.
  6. Project economics.
  7. Risks.
  8. Recommendation and launch plan.

Option 2. Report for Diagnosing a Problem

Structure:

  1. Main diagnosis.
  2. Symptoms of the problem.
  3. Root causes.
  4. Evidence for each cause.
  5. Consequences of inaction.
  6. Possible solutions.
  7. Recommended solution.
  8. Implementation plan.

Option 3. Report for Growth Strategy

Structure:

  1. Main growth direction.
  2. Current position of the company.
  3. Where the opportunities are.
  4. Which opportunities are most attractive.
  5. What should be done first.
  6. What resources are needed.
  7. What the risks are.
  8. Roadmap.

Option 4. Report for an Investor

Structure:

  1. Investment thesis.
  2. Market problem.
  3. Solution.
  4. Market size.
  5. Business model.
  6. Competitive advantage.
  7. Financial logic.
  8. Team and plan.
  9. Risks.
  10. Requested decision.

14. Universal Report Template

Title

Briefly state what the report is about and what decision needs to be made.

1. Executive Summary

A brief answer to the entire question.

Formula:

We believe that [conclusion]. This is based on [3 arguments]. Therefore, we recommend [action]. The main risks are [risks], but they are manageable through [measures].

2. Context

What is happening? Why has the question arisen now?

You need to explain:

– the situation;
– the problem;
– the purpose of the analysis;
– who the decision is being prepared for.

3. Key Question

This is formulated as a management question.

Examples:

– Should we launch the product?
– Why are sales falling?
– Which market should we enter first?
– Which acquisition channel should we scale?
– How can operational risks be reduced?

4. Main Answer

One clear thesis.

Example:

The company should launch the product, but only as an MVP and only in one segment, because a broad launch would create high costs before demand is confirmed.

5. Arguments

Usually 3–5 arguments.

Example:

  1. Demand exists, but it is concentrated in a narrow segment.
  2. Competitors do not address the key pain point.
  3. The MVP allows the hypothesis to be tested at low cost.
  4. A full launch now carries a high risk of budget overruns.

6. Evidence

For each argument:

– data;
– calculations;
– interviews;
– comparisons;
– market facts;
– internal metrics;
– client examples.

7. Risks and Limitations

You need to honestly state:

– where the data is incomplete;
– what assumptions were used;
– what could change the conclusion;
– which risks are most dangerous.

8. Recommendations

What exactly should be done?

Recommendations must be practical:

– who does it;
– what they do;
– by when;
– what result is expected.

9. Next Steps

Example:

  1. Within 2 weeks, validate demand through interviews and a landing page.
  2. Within 4 weeks, build the MVP.
  3. Within 8 weeks, launch SEO content and review collection.
  4. After 12 weeks, decide whether to scale.

15. How to Prepare the Report: Work Process

Step 1. Formulate the Question

Bad question:

Analyze the market.

Good question:

Should the company enter Market X in 2026, and if so, with what product and budget?

Step 2. Formulate a Preliminary Answer

Even before the full analysis, you need a hypothesis.

Example:

It is likely worth entering the market, but through an MVP, because the market is interesting but demand has not yet been confirmed.

The hypothesis may change after the analysis. That is normal.

Step 3. Break the Question into Blocks

Example for a product launch:

  1. Does the client have a problem?
  2. Is the client willing to pay?
  3. Who are the competitors?
  4. Can we build the product?
  5. Do the economics work?
  6. What are the risks?

Step 4. Collect Data

Data is not collected “in general,” but for the specific blocks of the pyramid.

Step 5. Check the Logic

Ask yourself:

– Is the main conclusion clear from the first page?
– Do the arguments avoid duplication?
– Is each argument proven?
– Are there weak points?
– Do the recommendations follow from the analysis?

Step 6. Write the Report

Writing order:

– First, the structure.
– Then, the key theses.
– Then, the evidence.
– Then, the executive summary.
– Then, final editing.

The executive summary is often best written at the end, once the full logic is clear.

16. Practical Example

Suppose the question is:

Should the company launch a Telegram channel for a B2B audience?

Bad structure:

  1. What Telegram is.
  2. Telegram statistics.
  3. Examples of channels.
  4. Content plan.
  5. Conclusions.

Good structure:

Main Conclusion

The company should launch a Telegram channel if it is ready to use it not as a news feed, but as a tool for trust-building and lead generation in a narrow B2B niche.

Argument 1

A B2B audience makes decisions slowly, so the channel must regularly build trust.

Evidence:

– long sales cycle;
– high importance of expertise;
– importance of repeated touchpoints.

Argument 2

Monetization will depend not on the number of subscribers, but on the quality of the audience.

Evidence:

– one qualified lead can be more valuable than thousands of random views;
– job titles, industries, and purchasing power of the audience matter.

Argument 3

Content should be built around client problems, not company news.

Evidence:

– people read what helps them solve tasks;
– expert content reduces distrust;
– case studies and breakdowns create practical value.

Recommendation

Launch the channel as a 3-month pilot: 3 posts per week, focus on client pain points, monthly evaluation of leads, engagement, and audience quality.

17. Common Mistakes

Mistake 1. Starting with the Research Story

You do not need to explain in detail how you worked. Show the conclusion.

Mistake 2. Giving Many Facts Without Meaning

Facts without interpretation do not help make a decision.

Mistake 3. Hiding the Recommendation at the End

The manager should understand the recommendation immediately.

Mistake 4. Making Headings Too Generic

A heading should be a conclusion, not the name of a section.

Mistake 5. Mixing Different Levels of Logic

You cannot place a strategic conclusion next to a minor operational detail.

Bad:

  1. We need to enter the Brazilian market.
  2. We need to change the color of the button on the website.
  3. We need to hire a director.

Better:

  1. Entry into the Brazilian market is attractive.
  2. To enter, the company needs local sales, payment infrastructure, and legal adaptation.
  3. Among operational tasks, the first priority is hiring a local director.

Mistake 6. Not Showing Risks

A report without risks looks like advertising, not analysis.

Mistake 7. Giving Recommendations Without an Owner and Deadline

Bad:

Improve marketing.

Good:

Within 30 days, test 3 acquisition channels: SEO, Telegram Ads, and partner publications. Owner — marketing. Success criterion — cost per qualified lead below X.

18. Checklist Before Submitting the Report

Before sending the report, check:

  1. The main conclusion is clear on the first page.
  2. The report answers a specific management question.
  3. There are 3–5 main arguments.
  4. The arguments do not duplicate each other.
  5. Each argument is supported by data or logic.
  6. Page headings are formulated as conclusions.
  7. There are no unnecessary facts that do not help the decision.
  8. Risks and limitations are stated.
  9. Recommendations are specific.
  10. It is clear what to do next, who is responsible, and by when.

19. Mini-Template for an Employee

Before writing the report, fill out this form.

1. What question are we solving?

2. Who will make the decision?

3. What is the main conclusion?

4. What 3–5 arguments support the conclusion?

5. What evidence exists for each argument?

Argument 1:

– …
– …

Argument 2:

– …
– …

Argument 3:

– …
– …

6. What are the risks and limitations?

– …
– …

7. What do we recommend doing?

– …
– …

8. What are the next steps?

20. The Main Rule

A good analytical report is not a long text or a set of beautiful tables.

A good analytical report is clear logic that leads the reader from the question to the decision.

Final formula:

Answer → Arguments → Evidence → Risks → Actions.

If an employee follows this formula, their report will be clear, persuasive, and useful for decision-making.

Comments

Weekly high-risk digest

Regulation, sanctions and payment news across your verticals — once a week, free.

Please check your inbox and click the link to confirm your subscription.

Please enter a valid email address!