# Clarify before you communicate The problem isn't how you say it. It's that you haven't finished thinking. SCQA, STAR, PEARL: three structures for thinking before speaking. Source: https://mblq.co/en/articles/clarify-before-you-communicate Published: 2026-02-27 Author: Martin Blanquer Also available in French: https://mblq.co/fr/articles/clarify-before-you-communicate.md Your message is clear in your head. You present it in a meeting. No one reacts. The founder asks a question that shows they missed the main point. You rephrase. Still doesn't land. You walk out thinking you should have prepared better slides. The problem isn't the slides. The problem isn't your eloquence. The problem is that your thinking wasn't clear before you opened your mouth. ## The real problem A confusing message is never a word problem. It's a thinking problem. ([Some people struggle with writing clearly...](https://www.linkedin.com/posts/shreyasdoshi_some-people-struggle-with-writing-clearly-activity-6940078222327910400-2bst)) The symptom is a confusing message. The cause is unfinished thinking. It's a common trap for PMs because the job pushes you to communicate constantly. A standup, an alignment meeting, an email to the founder, a Slack message to the team. There's no time to structure your thinking. So you communicate on the fly, with whatever information comes to mind, in the order it comes to mind. And you wonder why your audience checks out. Barbara Minto formalized the problem 40 years ago: we think bottom-up (from data to conclusion), but we need to communicate top-down (from conclusion to data). ([Minto Pyramid & SCQA](https://modelthinkers.com/mental-model/minto-pyramid-scqa)) The effort of communication isn't finding the right words. It's reversing the natural order of your thinking. They hadn't finished thinking. They didn't know what their conclusion was, or why it mattered to their audience, or what specific question they were trying to answer. And no slide template can fix that. ## The SCQA test SCQA is a four-field test — *Situation, Complication, Question, Answer*. If you can fill them in, your thinking is ready. If you get stuck on one, that's where the work begins. > Interactive demo on the web version: [SCQA walkthrough](https://mblq.co/en/articles/clarify-before-you-communicate). SCQA is a thinking tool, not a slide template. ([The SCQA Framework](https://parametricpro.com/blog/scqa-framework)) You never show it as-is to your audience. You use it upstream to verify that you know what you want to say. SCQA tells you what to say. Not how to say it. And the how depends on what you need from your audience: understanding, or a decision. ## Structure to inform: STAR STAR (*Situation, Task, Action, Result*) is built for informing: a status update, a retro debrief, a post-mortem, a user test summary. > Interactive demo on the web version: [STAR walkthrough](https://mblq.co/en/articles/clarify-before-you-communicate). STAR is chronological. That's its strength and its limit. It tells what happened in the order it happened. It's perfect for factual reporting. It's not enough for convincing, because it doesn't surface the insight, the reason your audience should care. ## Structure to convince: PEARL PEARL (*Problem, Epiphany, Action, Result, Learning*) is built for convincing: a feature pitch, a roadmap arbitration, an escalation, a resource request. The key difference with STAR: PEARL puts the insight first — the Epiphany. Not what happened, but why your recommendation isn't obvious and why it's right. > Interactive demo on the web version: [PEARL walkthrough](https://mblq.co/en/articles/clarify-before-you-communicate). Jackie Bavaro (former Head of Product at Asana) created PEARL around a simple idea: *"The more your decisions were obviously right, the lower your level."* ([Use PEARL instead of STAR to shine in your PM interviews](https://jackiebavaro.substack.com/p/use-pearl-instead-of-star-to-shine)) ## In practice The point isn't memorizing three acronyms. It's knowing which one to apply and when. You've just seen the same data — the Spain launch — structured with STAR and then with PEARL. With STAR, the head of growth knows what you did, but not what they should decide. With PEARL, they have an insight, a recommendation, and a decision to make. The data is identical. The structure changes everything. But structure isn't enough. You can build a perfect PEARL — if you haven't clarified your conclusion first, you'll convince of the wrong thing. That's why SCQA comes first. It never shows up in the final deliverable. No one will congratulate you for filling it in before a meeting. But it's what makes the difference between a PM who walks into a room with a vague idea and a PM who walks in with a message. ## The clarity test Next time you're preparing an important message, take the test. > Interactive demo on the web version: [Clarity check](https://mblq.co/en/articles/clarify-before-you-communicate). If you get stuck on any of them, you don't have a communication problem. You have a clarity problem. And the solution isn't a better template. It's 10 minutes of silent thinking. Got your answers? Try it with a real topic. > Interactive demo on the web version: [Takeaway playground](https://mblq.co/en/articles/clarify-before-you-communicate). Next time you walk out of a meeting where your message didn't land, you'll know the problem was never the slides.