Structured Expression: The Art of Speaking to the Point

Structured Expression: The Art of Speaking to the Point

When your boss says “get to the point,” are you still rambling? In a world of information overload, the ability to express yourself clearly and concisely is not just a nice-to-have skill. It is a competitive advantage.

What Is Structured Expression?

Structured expression equals structured thinking plus perspective-taking. It is the process of organizing information in a logical, clear, and persuasive manner, making it easy for the audience to understand, remember, and act upon.

The theoretical foundation comes from Barbara Minto’s Pyramid Principle, developed during her time as the first female consultant at McKinsey and Company. The pyramid principle has been a classic training framework at McKinsey for over 40 years.

The Communication Funnel Problem

Without structure, information suffers massive loss at each stage:

Structured expression minimizes this loss by organizing information so the audience can follow your logic and retain key points.

The Four Principles of the Pyramid

Principle 1: Conclusion First State your conclusion upfront, then expand with supporting arguments. This respects the audience’s limited attention and time.

Principle 2: Top-Down Each upper level summarizes the level below. The conclusion概括s the arguments; the arguments概括s the evidence.

Principle 3: Grouping Information at the same level must be logically categorized using the MECE principle: Mutually Exclusive (no overlap) and Collectively Exhaustive (no gaps).

Principle 4: Logical Progression Within each group, information follows a logical order: chronological, structural, or by importance.

Exception: Do not lead with the conclusion when delivering negative news or when the audience is likely to strongly resist your message. In these cases, build context first.

Seven Practical Frameworks

Framework 1: PREP (Universal Reporting)

Best for: Most work reports, meeting contributions, daily communication. The structure leverages memory patterns by placing key information at the beginning and end.

Framework 2: STAR (Event Description)

Best for: Interview answers, performance reviews, project summaries. Makes your narrative complete, logical, and credible.

Framework 3: FABE (Persuasion)

Best for: Supplier negotiations, product recommendations, improvement proposals. The key is emphasizing benefits from the audience’s perspective.

Framework 4: SCQA (Opening/Preface)

Best for: Report openings, speech introductions, email writing. Four variants exist: standard (S-C-A), direct (A-S-C), concern-focused (C-S-A), and confidence-focused (Q-S-C-A).

Framework 5: AIDA (Interest Generation)

Best for: Product introductions, proposal persuasion, marketing communication.

Framework 6: SPIN (Consultative Questioning)

Best for: Supplier audits, requirement discovery, quality issue investigation. Helps convert hidden needs into explicit needs.

Framework 7: GPEC (Impromptu Speaking)

Best for: Meeting contributions, social self-introductions, unexpected presentations.

Workplace Applications

Reporting to Headquarters

Use PREP with data support:

1. Point: “This quarter, APAC product defect rate dropped 15 percent, meeting annual targets.”
2. Reason: Three key factors: supplier improvement, process optimization, upgraded inspection standards.
3. Example: One specific supplier case showing before-and-after data.
4. Point: “Recommend continuing the supplier quality improvement program next quarter, projecting another 10 percent reduction.”

Supplier Quality Meetings

Combine FABE with SPIN questioning:

FABE approach:

• Feature: “Your last three batches had a 3.2 percent welding defect rate.”
• Advantage: “This improved from 5.1 percent last quarter, but remains above the 2 percent target.”
• Benefit: “If we bring it below 2 percent, rework costs drop 30 percent for both sides.”
• Evidence: Show benchmark data from other suppliers achieving 1.5 percent.

SPIN questioning:

• Situation: “What are your current welding process parameters?”
• Problem: “Where are defects most concentrated?”
• Implication: “If this persists, how will it affect delivery and costs?”
• Need-Payoff: “If we provide technical support, how quickly could you improve?”

Quality Incident Reports

Apply the 2W1H structure with MECE grouping:

• What: Define the problem using 5W2H (who, what, when, where, why, how, how much)
• Why: Root cause analysis with 5 Whys and fishbone diagram
• How: Countermeasures in three categories: immediate containment, permanent corrective, preventive action

Cross-Department Meetings

Master the “Rule of Three.” Organize content into three aspects:

1. Status overview with data and trends
2. Main issues with analysis (maximum 3 issues)
3. Action plan and support needed

The rule of three works because it matches memory capacity (7 plus or minus 2), represents completeness, and forces logical organization.

Email Communication

Open with SCQA:

1. Situation: “As you know, we have been working on improving welding quality.”
2. Complication: “However, the latest batch still shows a 3.2 percent defect rate.”
3. Question: “How can we close this gap?”
4. Answer: “We propose three actions. Please confirm by Friday.”

Five Techniques for Getting Yes

Appeal to their interests. Frame everything from the other party’s benefit perspective. “This approach can reduce your rework costs by 30 percent.”

Highlight risks (use carefully). Convey potential consequences to create urgency. “If this issue persists, it may affect future orders.”

Grant them choice. Offer options so they feel in control while still reaching your objective. “Would Option A or Option B work better for your team?”

Elevate their status. Satisfy the need for respect and recognition. “With your team’s technical capability, this improvement should be well within reach.”

Build camaraderie. Find common ground and create a sense of partnership. “Let us work together to solve this problem.”

The 30-Day Training Plan

Week 1: Build Awareness

• Learn the PREP framework
• Before every report or speech, write down your conclusion in one sentence
• Practice the “Rule of Three” at least three times daily
• Observe good communicators and analyze their structure

Week 2: Framework Practice

• Learn STAR for event description
• Learn SCQA for email openings
• Before writing every email, draft the structure using SCQA
• Before speaking in meetings, organize thoughts with PREP

Week 3: Deepen Application

• Learn FABE and SPIN for supplier and client communication
• At the next quality meeting, use “Rule of Three” plus visual reporting
• Practice perspective-taking: before every communication, ask “What does the other party care about most?”
• Start using mind maps to organize complex problems

Week 4: Internalize the Habit

• Learn the GPEC framework for impromptu speaking
• Review all important communications from the month and identify improvement areas
• Teach PREP or the “Rule of Three” to a colleague
• Create a personal communication style improvement plan

Long-term practice suggestions:

• Continuous practice: Spend 2 minutes before every important communication drafting your structure
• Observational learning: Notice how TED talks and excellent reports structure their content
• Review and improve: After every communication that did not go well, think “If I could do it again, how would I adjust the structure?”
• Teach to learn: Share structured expression with your team for mutual improvement

Structured expression is not a talent. It is a trainable skill. Before every communication, take two minutes to identify your conclusion first. That simple habit will transform how people perceive and respond to you.

What is one communication situation this week where structured expression could have made a difference?

結構化表達：把話說到點子上的藝術

當領導說「說重點」的時候，你還在囉嗦嗎？在資訊過載的時代，清晰簡潔地表達自己的觀點，不僅是一項加分技能，更是一種競爭優勢。

什麼是結構化表達？

結構化表達 = 結構化思維 + 換位思考。它是將資訊按照邏輯清晰、有說服力的方式組織起來，讓受眾聽得明白、記得清楚、產生認同的表達過程。

理論基礎來自芭芭拉·明托的金字塔原理。明托是麥肯錫公司首位女性諮詢顧問，金字塔原理已成為麥肯錫超過40年的經典培訓教材。

溝通漏斗問題

沒有結構的資訊在每個環節都會大量流失：

結構化表達透過有序組織資訊，幫助受眾跟上邏輯、記住要點，從而降低溝通損耗。

金字塔四大原則

原則一：結論先行 先說結論，再展開論述。尊重受眾有限的時間和注意力。

原則二：以上統下 上層是對下層的概括總結。結論概括論點，論點概括論據。

原則三：歸類分組 同一層級的資訊必須按邏輯分類，遵循 MECE 原則：相互獨立（無重疊）、完全窮盡（無遺漏）。

原則四：邏輯遞進 同一組內的資訊按邏輯順序排列：時間順序、結構順序或重要性順序。

例外情況： 傳遞負面資訊或受眾可能強烈反對時，不宜結論先行，應先建立共識和鋪墊。

七大實戰框架

框架一：PREP（萬能匯報）

適用於大多數工作匯報、會議發言、日常溝通。利用記憶規律，將重要資訊放在開頭和結尾。

框架二：STAR（描述事件）

適用於面試回答、績效匯報、項目總結。使敘述完整、有邏輯、可信。

框架三：FABE（說服客戶）

適用於供應商談判、產品推薦、改善提案。關鍵是從受眾角度強調利益。

框架四：SCQA（序言/開場）

適用於報告開頭、演講開場、郵件撰寫。有四種變體：標準式、開門見山式、突出憂慮式、突出信心式。

框架五：AIDA（激發興趣）

適用於產品介紹、提案說服、行銷溝通。

框架六：SPIN（顧問式提問）

適用於供應商審核、需求挖掘、品質問題調查。幫助將隱藏性需求轉化為明顯性需求。

框架七：GPEC（即興演講）

適用於會議即興發言、社交場合自我介紹、臨時匯報。

工作應用場景

向總部匯報

使用 PREP 加數據支撐：

1. 結論： 「本季度亞太區產品不良率下降15%，達到年度目標。」
2. 依據： 三個關鍵因素：供應商改善、製程優化、檢測標準升級。
3. 事例： 一個具體供應商案例，展示改善前後數據。
4. 重申： 「建議下季度繼續推行供應商品質提升計劃，預計可再降10%。」

供應商品質會議

FABE 與 SPIN 提問結合：

FABE 方式：

• 特點：「貴廠最近三批貨的焊接不良率為3.2%。」
• 優點：「相比上季度5.1%有進步，但仍高於2%的目標。」
• 利益：「如果降到2%以下，可減少30%的返工成本，雙方都受益。」
• 證據：展示其他供應商達到1.5%的標竿數據。

SPIN 提問：

• 狀況：「目前的焊接工藝參數是怎樣的？」
• 問題：「不良主要集中在哪些位置？」
• 暗示：「如果這個問題持續，對交期和成本會有什麼影響？」
• 需求解決：「如果我們提供技術支持，貴廠有信心在多長時間內改善？」

品質異常報告

應用 2W1H 結構加 MECE 分組：

• What：用5W2H精確定義問題（何人、何事、何時、何地、為何、如何、多少）
• Why：5 Why 加魚骨圖分析根本原因
• How：對策分三類：臨時圍堵、永久矯正、預防措施

跨部門會議

掌握「講三點」。將內容歸納為三個方面：

1. 狀況概述（數據加趨勢）
2. 主要問題及分析（最多3個問題）
3. 行動計劃及需要協助的事項

講三點之所以有效，是因為符合記憶規律（7加減2），代表完整性，且強迫自己歸納總結。

郵件溝通

用 SCQA 開場：

1. 情境：「如您所知，我們一直在努力提升焊接品質。」
2. 衝突：「然而，最近一批貨仍有3.2%的不良率。」
3. 疑問：「我們如何彌補這個差距？」
4. 解答：「我們提出三項行動方案，請於週五前確認。」

引導對方說 Yes 的五個技巧

投其所好。 從對方的利益出發。「這樣做可以幫貴廠減少30%的返工成本。」

脅之以災（慎重使用）。 傳達可能的風險。「如果這個問題持續，可能影響後續訂單。」

授之以權。 給出選項，讓對方感覺有選擇自由。「您看方案A還是方案B更合適？」

抬其身份。 滿足尊重需求。「以貴廠的技術實力，這個改善應該不難。」

與之同伍。 建立同伴感。「我們一起想辦法解決這個問題。」

30天訓練計劃

第1周：建立意識

• 學習 PREP 框架
• 每次匯報或發言前，先用一句話寫下結論
• 每天至少3次用三點結構回答問題
• 觀察優秀的溝通者，分析他們的結構

第2周：框架實踐

• 學習 STAR 用於描述事件
• 學習 SCQA 用於郵件開頭
• 每封郵件動筆前先用 SCQA 擬定結構
• 會議發言前用 PREP 組織思路

第3周：深化應用

• 學習 FABE 和 SPIN 用於供應商和客戶溝通
• 下次品質會議用「講三點」加圖解匯報
• 練習換位思考：每次溝通前想「對方最關心什麼？」
• 開始用思維導圖整理複雜問題

第4周：內化習慣

• 學習 GPEC 框架應對即興發言
• 覆盤本月所有重要溝通，找出改善點
• 教同事使用 PREP 或「講三點」
• 制定個人溝通風格改善計劃

長期實踐建議：

• 持續練習： 每次重要溝通前花2分鐘擬定結構
• 觀察學習： 注意 TED 演講、優秀報告的結構設計
• 覆盤改進： 每次溝通不順時，思考「如果重來，我會怎麼調整結構？」
• 教是最好的學： 把結構化表達教給團隊，共同提升

結構化表達不是天賦，是可以訓練的技能。每次開口前，花兩分鐘先想好你的結論是什麼。這個簡單的習慣會徹底改變別人對你的看法和回應。

這一週，有哪次溝通場景如果用結構化表達可以做得更好？