Every junior analyst has made this slide. Most senior ones still do. It is the "Competitor Update" slide: dense, dutiful, and dead on arrival. This teardown takes one such slide, the kind produced in thousands of CI functions every Monday, and rebuilds it fix by fix. The content is fictional but the sins are drawn from life.

The before slide

Picture it. The title reads: "Competitor Update: Veltrax Flow Systems, Q2 2026."

Below it, three zones fight for attention. Left: six bullet points. "Veltrax announced a distribution agreement with a Texas MRO supplier." "14 field service technician openings posted across Gulf Coast." "New price list shows 6% reduction on mid-range centrifugal pumps." "CEO mentioned aftermarket revenue 4x on earnings call." "Revenue grew 8% YoY in Q1." "New CMO hired from a industrial software company."

Right: a clustered bar chart titled "Veltrax Revenue by Segment, 2022 to 2025," four years, five segments, twenty bars, a legend with five colors, and a source line in 6-point font.

Bottom: a text box labeled "Implications," containing: "Veltrax continues to invest in its service capabilities. We will continue to monitor developments."

Everything on this slide is accurate. Nothing on it is useful. Let us fix it in six moves.

Before and after: the dense Competitor Update slide desaturated on the left, the rebuilt argument slide in full contrast on the right, six numbered pins tagging the fixes.
Before and after: the dense Competitor Update slide desaturated on the left, the rebuilt argument slide in full contrast on the right, six numbered pins tagging the fixes.

Fix 1: The title must be the finding, not the topic

"Competitor Update: Veltrax, Q2 2026" is a filing label, not a message. The MBB convention is the action title: a full sentence stating the one thing this slide proves. If a reader saw only the titles of your deck, they should get the entire argument.

The test: does the title survive as a standalone sentence someone could agree or disagree with? "Competitor Update" cannot be disagreed with. Rewrite:

"Veltrax is pivoting from selling pumps to selling uptime, putting our Gulf Coast aftermarket revenue at risk within 18 months."

Note what happened: the title is an inference, so the slide must now carry its labeling. That is not a burden; that is the point. A title that risks being wrong is a title that says something.

The action title test: the topic label "Competitor Update: Veltrax Q2" struck through, the falsifiable sentence beneath it, captioned "Could a reader disagree with it?"
The action title test: the topic label "Competitor Update: Veltrax Q2" struck through, the falsifiable sentence beneath it, captioned "Could a reader disagree with it?"

Fix 2: One slide, one message; everything else goes

The before slide carries six facts, a five-segment chart, and a vague implication: at least three separate messages. The revenue growth bullet and the CMO hire belong to different stories. The single-message rule is brutal: everything on the slide either supports the title or leaves the slide.

Apply it. The distribution deal, the technician hiring, the price cut, and the earnings language all support the pivot thesis; they stay. Revenue growth of 8% supports nothing specific here; it moves to a backup slide. The CMO hire is a different signal on a different timeline; it gets its own slide or the watch log. Cutting content feels like losing work. It is actually the work.

Fix 3: Kill the chart crime, choose the chart that argues

The twenty-bar segment chart answers a question nobody asked. It exists because the data existed. A chart on an MBB-grade slide is not decoration; it is a witness called to prove the title.

What would prove "pivot to services"? One comparison: service-related signals over time. Rebuild as a single, minimal visual: four converging evidence streams on one timeline, hiring, distribution, pricing, and earnings language, each plotted as a dated marker, all pointing at the same six-week window. One color for evidence, one accent for the inference they converge on. No legend needed if the labels sit on the data. The chart now performs the argument: separate facts, one direction.

The general rule: if your chart needs a legend with five entries, you have not decided what it is for.

The convergence timeline: four dated evidence markers, hiring, distribution, pricing, and earnings language, converging on one labeled inference.
The convergence timeline: four dated evidence markers, hiring, distribution, pricing, and earnings language, converging on one labeled inference.

Fix 4: Structure the body as evidence, not as a feed

Bullets ordered by arrival date are a feed. Evidence ordered by logic is an argument. The rebuilt body has three tiers, mirroring the CI Report Pyramid:

Evidence line (the four facts, each dated and source-tagged, each labeled [F]). Inference line (one sentence: "Together these point to a strategy shift toward aftermarket services, labeled [CI], corroborated inference from four independent streams"). Stake line (why we care: "Our three largest Gulf Coast accounts already run Veltrax units; regional aftermarket is roughly 30% of margin").

Three tiers, maybe forty words total. The reader's eye travels fact to inference to stake in one pass, which is exactly the climb the Pyramid framework demands, compressed onto one page.

Fix 5: Label the epistemics on the slide itself

MBB conventions and CI honesty meet here. The before slide presented facts and the phrase "continues to invest" with identical visual weight, letting the reader assume everything was equally solid. The after slide tags claims inline: [F] on each fact, [CI] on the inference in the title's support line. Two-character tags, footnoted once.

This looks like humility. It functions as authority: the reader learns your untagged claims never need checking, and your tagged inferences show your reasoning instead of hiding it. Precision compounds into trust; a slide is just the smallest unit where that compounding starts.

Fix 6: Replace "monitor developments" with a decision request

"We will continue to monitor developments" is the analyst handing the work back to the reader. An MBB-grade slide ends with a so-what box that requests a decision or names a next step with an owner and a date.

Rewrite: "Decision requested: approve pre-emptive multi-year service offers to our three exposed accounts before end of quarter. CI re-tests this thesis in 90 days against technician onboarding and published contract wins."

Now the meeting has something to do. The slide can be accepted, rejected, or amended, which means it can succeed or fail, which means it matters.

The after slide, assembled

Title: the falsifiable finding. Left two-thirds: the convergence timeline, four dated markers, one inference callout. Right third: the three-tier evidence block with Ladder tags. Bottom strip: the decision request and the 90-day re-test. Generous white space; one message; perhaps sixty words on the entire page against the before slide's two hundred.

The before slide reported that things happened. The after slide argues that something is happening, shows its evidence, admits what is inferred, and asks for a move. Same facts. Different profession.

The 60-second slide audit

Five questions, run on any slide before it ships:

  1. Is the title a full sentence someone could disagree with?
  2. Does every element on the page support that sentence?
  3. Does the chart prove the title, or merely accompany it?
  4. Can the reader tell fact from inference without asking you?
  5. Does the slide end by requesting a decision or naming an owner and a date?

Five yeses and the slide argues. Fewer, and you know exactly which fix to apply.