Most professionals write the same way: gather the data, line up the bullets, reach the conclusion at the end. The logic feels airtight. The reader still gets lost.
A contributor on r/PromptEngineering just made the case for doing the exact opposite, and the argument is hard to ignore. The post’s author, who spent years defaulting to bullet points, describes a structural shift that changed how they communicate to clients, teams, and stakeholders, and, unexpectedly, how they write AI prompts.
The framework is called the Pyramid Principle. It starts with your conclusion. Everything else is justification.
The Problem With Bottom-Up Thinking
Bottom-up structure is intuitive. You gather evidence, analyze it, and arrive at a recommendation. That’s how the thinking happens, so it’s also how most people write it down.
The problem: the reader experiences your uncertainty before they understand your point. They have to hold all the context in working memory, waiting for the conclusion that explains why any of it matters.
Pyramid thinking flips the order. You lead with the recommendation, then provide the reasons, then back each reason with evidence. Same information. Completely different cognitive load.
The original poster puts it this way: leading with your conclusion isn’t arrogant. It’s respectful of the reader’s time.
How the Structure Works
The Pyramid has three levels:
🔺 Level 1: The Apex
One statement. Your recommendation or core insight. Not “we have a retention problem” but “we need to cut onboarding from 14 steps to 4, that’s what’s killing retention.” Specific and actionable.
📐 Level 2: The Pillars
2 to 4 independent reasons that support the apex. Each one stands alone. Together they cover the full argument. The test: if you remove one pillar, does the apex still hold? If yes, that pillar is weak or redundant.
📊 Level 3: The Foundation
Specific evidence for each pillar. Data, examples, observations. Ranked by strength, strongest first.
The Rule That Makes It Actually Work: MECE
The pillars need to satisfy a condition the author calls MECE: Mutually Exclusive, Collectively Exhaustive.
Mutually Exclusive means no overlap between pillars. Collectively Exhaustive means together they cover the complete argument, no significant gaps.
Without MECE, the structure feels repetitive or incomplete. Experienced readers notice the gaps even when they can’t name them. This is the hardest part of the method in practice, and where most people fail. Overlapping reasons are easy to write. Genuinely independent, exhaustive pillars require actual structured thinking.
A Concrete Example
The post walks through a real case. Apex: “We should kill the free tier.”
Pillar 1 (Economics): Free users consume 40% of infrastructure, generate 2% of revenue.
Pillar 2 (Product): The best features require context the free tier doesn’t support.
Pillar 3 (Signal): The highest-converting leads come from trials, not free accounts.
Three independent pillars. Together they cover the full argument. Each backed by evidence. The author’s conclusion: that’s a 90-second pitch that would take 20 minutes to build bottom-up.
Notice how each pillar covers different ground. Economics, product fit, and conversion signal don’t overlap. Remove any one and the others don’t substitute for it. That’s MECE working correctly.
Why This Applies to Prompt Engineering
The original poster flagged something worth paying attention to: the Pyramid Principle applies directly to how you structure prompts.
When you build a prompt bottom-up, context first and task last, the model has to infer where you’re going. It spends inference on figuring out what you want before it starts doing it. When you lead with the objective and organize supporting context in layers, the output is sharper and more aligned to intent.
Pyramid structure isn’t just a communication tool. It’s a design principle for any information a model has to parse and act on.
Where to Apply This
The framework is worth pulling out in three specific situations:
- Anything a senior stakeholder will read, where time is short and clarity is non-negotiable
- Real-time responses to complex questions in meetings, when you need structure on the spot
- Prompts that need to guide structured reasoning in an LLM
The community response to the post surfaced one additional connection worth noting. Several people pointed out that working backwards, starting from the desired outcome and defining what it takes to get there, is a complementary method. Amazon has documented this approach extensively. The common thread is top-down design: know where you’re going before you explain how to get there.
The Hardest Part
Finding the apex is usually not the problem. Most people have an instinct for their recommendation. The difficulty is in the pillars.
Building reasons that are genuinely independent, together exhaustive, and each backed by evidence is where the method requires real effort. That friction is the point. It’s where clear thinking separates from structured-looking noise.
If you’ve tried top-down structuring before, whether for communication or for prompts, the pillar step is where to focus. What’s your approach to making them actually MECE?
Frequently Asked Questions
Q: How do I know if I’ve found the REAL apex versus just a symptom?
The hardest part is distinguishing between an observation and an actual conclusion. “Retention is dropping” is a symptom; “our onboarding is too complex for first-time users” is the real apex. Your test: does it point to a specific change or action? If you’re just stating what’s happening, dig deeper. Once you nail the true apex, your pillars usually fall into place naturally.
Q: How do I verify my pillars are actually Mutually Exclusive and Collectively Exhaustive (MECE)?
Use this test: remove one pillar. If your apex still holds up without it, that pillar is weak and needs rework. Also scan for overlap , if two pillars could merge or contradict each other, they’re not properly exclusive. Your reader should feel the argument is complete and nothing repeats or contradicts.
Q: Is the Pyramid Principle just repackaging existing frameworks like Amazon’s ‘working backwards’ or essay outlines?
Yes and no. The core idea , start with desired outcome, then build supporting reasons , is used in humanitarian program planning (log frames), essay writing (triangles), and business strategy. The Pyramid Principle’s unique strength is the MECE rule, which forces you to avoid overlap and guarantee completeness. Different names, same top-down logic.
Q: Can I use this to structure AI prompts, or is it just for business presentations?
It works everywhere. Whether you’re crafting a prompt, writing a report, or pitching to investors, starting with your main ask (the apex) then supporting reasons is universal. This aligns with senior leadership communication , same thinking structure applies whenever you need to persuade or explain something complex.
I stopped structuring my thinking in lists. I use the Pyramid Principle now. Here’s the difference.
by u/Critical-Elephant630 in PromptEngineering