Structure & Organization

The Cost of Poor Structure

Research consistently shows that poorly organized messages lead to:

• 47% lower comprehension -- audiences understand less than half of what was intended
• Rapid attention loss -- listeners mentally disengage within 30 seconds of a rambling message
• Reduced credibility -- disorganized speakers are perceived as less competent, even when their content is strong
• Decision paralysis -- when information is scattered, audiences struggle to take action
• Wasted time -- meetings run long, emails require follow-ups, reports get returned for revision

The Power of Good Structure

Well-structured communication delivers immediate, measurable benefits:

• Clarity -- your audience grasps the main point immediately
• Retention -- organized information is remembered 40% better than unstructured content
• Persuasion -- logical flow makes arguments more convincing
• Efficiency -- structured messages take less time to deliver and less time to process
• Professional authority -- organized communicators are trusted and promoted faster

The Three Levels

Level 1 (Top): The Answer -- Your main conclusion, recommendation, or key message. This is what you would say if you only had 10 seconds.

Level 2 (Middle): Supporting Arguments -- The 2-4 key reasons that support your answer. Each argument should be independent and collectively they should be exhaustive.

Level 3 (Base): Evidence and Data -- The specific facts, numbers, examples, and analysis that back up each supporting argument.

Without the Pyramid (Bottom-Up)

"So I have been looking at our customer data for the past quarter, and I noticed that we had 12,000 support tickets, which is up 34% from last quarter. I also looked at our Net Promoter Score and it dropped from 72 to 58. Then I analyzed the ticket categories and found that 67% were related to our new checkout flow. I also talked to three enterprise clients who mentioned they were considering switching providers. I ran the numbers on customer lifetime value and... anyway, I think we should probably roll back the checkout redesign."

With the Pyramid (Top-Down)

"We should roll back the checkout redesign immediately. Three factors support this:

First, customer satisfaction has declined sharply. Our NPS dropped from 72 to 58, and support tickets increased 34% to 12,000 this quarter.

Second, the new checkout flow is the primary cause. 67% of all support tickets are directly related to it.

Third, we are at risk of losing key accounts. Three enterprise clients have indicated they are considering switching providers."

Without the Pyramid

"The development team has been working on the mobile app since January. We started with the authentication module, which took longer than expected because of the API changes. Then we moved to the dashboard, and the designer was out sick for two weeks so that pushed things back. We also discovered some performance issues during testing that need resolution. The QA team found 23 bugs, 15 of which are now fixed. We still have the payment integration and notification system to build..."

With the Pyramid

"The mobile app will launch two weeks behind schedule, on March 15th instead of March 1st. Here is the current status:

Completed (70%): Authentication and dashboard modules are built and tested. 15 of 23 bugs have been resolved.

In progress (20%): Payment integration is underway and on track for completion by March 8th.

Remaining (10%): Notification system and final 8 bugs. We need one additional QA resource to meet the revised deadline."

Without the Pyramid

"Hi team, I have been doing some research on our onboarding process. I looked at how other companies handle it and found some interesting data. Hubspot reduced their time-to-productivity by 50% by implementing a buddy system. I also read a study from Brandon Hall Group that says companies with strong onboarding improve new hire retention by 82%. Our current process takes about 6 weeks before new hires feel productive, and our 90-day attrition is at 15%. I was thinking maybe we could revamp things..."

With the Pyramid

"I recommend we redesign our onboarding program. This would reduce 90-day attrition (currently 15%) and cut time-to-productivity from 6 weeks to 3.

The business case is strong: Companies with structured onboarding see 82% better retention (Brandon Hall Group). Hubspot achieved 50% faster productivity through a buddy system alone.

The investment is modest: The redesign requires 40 hours of HR time and a $5,000 technology investment, with projected savings of $180,000 annually in reduced turnover.

I have a detailed implementation plan ready. Can we discuss at Thursday's meeting?"

When to Use the Pyramid Principle

• Business emails and memos -- executives want the bottom line first
• Status updates and reports -- lead with the headline, then provide detail
• Presentations to senior leadership -- they may leave early or interrupt with questions
• Consulting deliverables -- clients are paying for answers, not process
• Any situation where your audience is busy -- respect their time by leading with what matters most

Exception: In sensitive situations (delivering bad news to an emotional audience, or building consensus in a politically charged environment), you may need to build context first before stating your conclusion.

What It Is

Information is organized in the order it occurred or will occur -- past to present, first step to last step, beginning to end.

When to Use It

• Telling stories or sharing experiences
• Explaining processes and procedures (how-to guides)
• Providing historical context or timelines
• Describing events (incident reports, meeting recaps)
• Project plans and schedules

Example

"Here is how we resolved the server outage: At 2:14 AM, monitoring detected the failure. By 2:20 AM, the on-call engineer was notified. At 2:35 AM, the root cause was identified as a memory leak. By 3:10 AM, a patch was deployed. Full service was restored by 3:25 AM."

What It Is

Information is organized by physical or geographic location -- left to right, top to bottom, near to far, room by room, region by region.

When to Use It

• Describing physical layouts or spaces (office plans, store layouts)
• Regional business reports (performance by territory)
• Travel itineraries and directions
• Describing objects, diagrams, or user interfaces
• Architecture and design descriptions

Example

"Our expansion covers three regions: The East Coast office in New York handles enterprise clients and generates 45% of revenue. The Midwest hub in Chicago manages mid-market accounts and logistics. The West Coast team in San Francisco drives product development and tech partnerships."

What It Is

Information is grouped into categories or themes. Each category covers a distinct aspect of the topic.

When to Use It

• Training materials covering multiple skills or knowledge areas
• Product descriptions with multiple features
• Reports covering multiple departments or business functions
• Presentations with distinct sub-topics
• Any message where the information does not follow a natural sequence

Example

"Our employee benefits fall into four categories: Health (medical, dental, vision insurance and wellness programs), Financial (401k matching, stock options, and tuition reimbursement), Time Off (vacation, sick days, and parental leave), and Professional Development (conference budget, mentorship programs, and skills training)."

What It Is

First describe the problem in detail so the audience understands the pain, then present the solution and its benefits.

When to Use It

• Sales pitches and proposals
• Recommending changes to processes or policies
• Grant applications and funding requests
• Troubleshooting guides
• Any persuasive message where you need buy-in

Example

"Problem: Our customer support team currently takes an average of 4.2 hours to respond to tickets. Industry standard is under 1 hour. This is driving a 23% increase in customer churn.

Solution: Implement an AI-powered triage system that auto-categorizes and routes tickets. Based on pilot results, this would reduce response time to 45 minutes and cut churn by an estimated 15%."

What It Is

Explain why something happened (causes) and what resulted (effects), or predict what will happen if certain actions are taken.

When to Use It

• Root cause analysis and post-mortems
• Explaining trends or changes in data
• Risk assessments and impact analyses
• Scientific and technical explanations
• Arguing for or against a course of action

Example

"Three factors caused our Q3 revenue decline: First, the competitor launched a lower-priced alternative, pulling away price-sensitive customers (cause). This resulted in a 12% drop in our small business segment (effect). Second, our delayed product launch pushed enterprise renewals to Q4 (cause), creating a $2M revenue timing gap (effect). Third, the new sales territory alignment disrupted existing relationships (cause), leading to a 30% increase in deal cycle length (effect)."

What It Is

Present two or more options, ideas, or situations side by side, highlighting similarities and differences.

When to Use It

• Vendor or tool evaluations
• Decision-making memos presenting options
• Before-and-after analyses
• Competitive analyses
• Any situation where your audience must choose between alternatives

Example

"We are evaluating two CRM platforms:

Salesforce offers deeper customization, a larger third-party ecosystem, and stronger enterprise features. However, it costs 60% more and requires dedicated admin staff.

HubSpot provides a more intuitive interface, faster implementation (3 weeks vs. 3 months), and built-in marketing tools. However, it has limited customization for complex workflows.

For our mid-size team with limited IT resources, HubSpot is the stronger fit."

Choosing the Right Pattern

Ask yourself these questions to select the best structure:

• Does sequence matter? Use chronological.
• Does location matter? Use spatial.
• Are there distinct categories? Use topical.
• Is there a pain point to address? Use problem-solution.
• Am I explaining why something happened? Use cause-effect.
• Am I helping someone choose? Use compare-contrast.

You can also combine patterns. A proposal might use problem-solution as its overall framework, with chronological order within the implementation plan and compare-contrast for vendor selection.

The Three Tiers

Tier 1 -- The Lead (Must Know): The single most important thing your audience needs to know. If they read nothing else, this is what matters. Answer: Who? What? When? Where? Why?

Tier 2 -- Key Details (Should Know): Supporting facts, figures, and context that deepen understanding. This is where your evidence and important nuances live.

Tier 3 -- Background (Nice to Know): Historical context, additional examples, tangential information. If this section were cut entirely, the core message would still be clear.

Benefits for Every Medium

• Emails: Busy readers scan the first few lines. If your key point is buried in paragraph four, it may never be read.
• Reports: Executives often read only the executive summary. Place your conclusions and recommendations there.
• Web content: Users scroll quickly. Above-the-fold content gets 80% of attention.
• Presentations: Audiences are most attentive in the first two minutes. Use that window for your most important message.
• Slack and chat messages: The first line determines whether people read the rest.

Applying Progressive Disclosure in Communication

• Subject lines give the headline
• First paragraph gives the summary
• Body provides key details and evidence
• Attachments or links offer the full deep-dive for those who want it

This layered approach respects different audience needs: the executive who needs the headline, the manager who needs the details, and the specialist who needs the raw data.

Unchunked Information

"Please update the customer database, send the quarterly report to finance, schedule the team meeting for next week, order new laptop for the intern, review the marketing proposal, call the vendor about the delayed shipment, update the project timeline, prepare slides for the board meeting, and respond to the client complaint."

Chunked Information

"Here are your tasks for the week, grouped by area:

Administrative: Update customer database, order laptop for new intern, schedule team meeting for next week.

Reporting: Send quarterly report to finance, update project timeline, prepare board meeting slides.

External: Review marketing proposal, call vendor about delayed shipment, respond to client complaint."

Types of Signposts

Previewing: Tell the audience what is coming. "I will cover three topics today: budget, timeline, and staffing."

Transitioning: Signal a shift from one topic to the next. "Now that we have covered the budget, let us turn to the timeline."

Summarizing: Recap what has been covered. "So far, we have established that revenue is up but margins are shrinking."

Emphasizing: Flag the most important point. "If you remember nothing else from this meeting, remember this..."

Concluding: Signal the end and next steps. "In summary, here are the three actions we agreed on..."

Adding Information

Furthermore -- adds a point of equal weight. "Furthermore, customer feedback supports this direction."

In addition -- introduces supplementary information. "In addition, we have secured funding for Phase 2."

Moreover -- adds something that strengthens the previous point. "Moreover, the data shows consistent improvement."

Also -- simple addition of another point. "The team also completed the security audit."

Similarly -- introduces a parallel point. "Similarly, the London office saw growth."

Contrasting or Qualifying

However -- introduces a contrasting point. "However, the timeline presents challenges."

On the other hand -- presents an alternative perspective. "On the other hand, the risk may be worth taking."

Nevertheless -- acknowledges the previous point but introduces a counterpoint. "Nevertheless, the long-term benefits outweigh the costs."

In contrast -- highlights a direct difference. "In contrast, our competitors are investing heavily in this area."

Although -- introduces a concession. "Although the initial cost is high, the ROI is strong."

Conversely -- signals an opposite direction. "Conversely, reducing staff could accelerate burnout."

Despite this -- acknowledges a challenge before continuing. "Despite this setback, the project remains viable."

Showing Cause and Effect

Therefore -- draws a logical conclusion. "Therefore, we recommend proceeding with Option A."

As a result -- describes the outcome of a cause. "As a result, customer satisfaction improved by 20%."

Consequently -- shows what followed. "Consequently, the team was restructured."

Because of this -- connects cause to effect. "Because of this, we need to revise our approach."

This led to -- narrative cause-effect. "This led to a complete overhaul of the process."

Thus -- formal conclusion. "Thus, the evidence supports the hypothesis."

Sequencing and Ordering

First / Second / Third -- explicit numbering. "First, we need to assess the damage."

Next -- signals the following step. "Next, we will build the prototype."

Then -- continues a sequence. "Then, the team will conduct user testing."

Finally -- signals the last item. "Finally, we will present findings to the board."

Meanwhile -- indicates simultaneous events. "Meanwhile, the marketing team will prepare the launch campaign."

Subsequently -- indicates what came after. "Subsequently, the policy was revised."

Emphasizing and Illustrating

In particular -- highlights a specific point. "In particular, the sales team exceeded targets."

Specifically -- narrows to detail. "Specifically, we saw a 34% increase in mobile traffic."

For example -- introduces an illustration. "For example, Company X achieved similar results."

Notably -- flags something worth attention. "Notably, this is the first quarter we exceeded $1M."

Most importantly -- signals the key point. "Most importantly, customer retention improved."

In fact -- reinforces with evidence. "In fact, the data shows a 50% improvement."

Summarizing and Concluding

In summary -- begins a recap. "In summary, we have three priorities for next quarter."

To conclude -- signals the ending. "To conclude, I want to highlight our key achievements."

Overall -- provides a big-picture assessment. "Overall, the project was a success."

In short -- provides a brief recap. "In short, we need more resources."

To sum up -- wraps up a discussion. "To sum up, all three departments met their goals."

The key takeaway is -- highlights the essential point. "The key takeaway is that early investment pays off."

Opening (10-15% of your time)

Your opening serves three purposes: capture attention, establish credibility, and preview what is coming.

• Hook: Start with a surprising statistic, a relevant story, a provocative question, or a bold statement. Never start with "So, today I am going to talk about..."
• Context: Briefly explain why this topic matters to this audience right now.
• Roadmap: Preview your structure. "I will cover three things today: the problem, our proposed solution, and the expected results."

Body (75-80% of your time)

This is where your content lives. Organize it using one of the patterns we covered: chronological, problem-solution, topical, or any combination that fits.

• Limit to 3 main points -- this is the Rule of Three. Research shows audiences can retain three main ideas from a single presentation. More than that and retention drops dramatically.
• Support each point with evidence, examples, or stories
• Use transitions between sections -- "Now that we have seen the data, let us look at what it means for our strategy."
• Build in audience interaction every 8-10 minutes (questions, polls, brief activities)

Closing (10-15% of your time)

Your closing determines what people remember. End weak and your entire presentation loses impact.

• Summarize: Restate your three main points in one sentence each
• Call to action: Tell the audience exactly what you want them to do next
• Memorable close: End with a callback to your opening story, a powerful quote, or a forward-looking statement. Never end with "That is it" or "Any questions?"

The Rule of Three: Why It Works

The Rule of Three is deeply embedded in human cognition and culture. Three points create a pattern that feels complete and satisfying.

• "Life, liberty, and the pursuit of happiness"
• "Government of the people, by the people, for the people"
• "Blood, sweat, and tears"
• "Stop, look, and listen"

In business: frame your message around three reasons, three benefits, three steps, or three recommendations. If you have more than three points, group them into three categories.

Effective Email Structure

Subject line: Summarize the purpose and any required action. "Decision needed: Q3 budget allocation by Friday"

Opening line: State the purpose immediately. "I am writing to request approval for..." or "Here is the summary of today's meeting."

Body: Use short paragraphs (2-3 sentences max), bullet points for lists, and bold for key information. Group related points together.

Closing: State the specific action needed and the deadline. "Please review and approve by end of day Thursday so we can begin implementation on Monday."

Effective Report Structure

Executive summary: The entire report compressed into one page. Include your conclusions and recommendations here -- many readers will not go further.

Introduction: Background, scope, and methodology.

Findings: Organized by theme, in order of importance. Use headings and subheadings liberally.

Analysis: Interpretation of findings, implications, and connections.

Recommendations: Specific, actionable next steps with owners and timelines.

Appendices: Raw data, detailed charts, and supplementary material for those who want to go deep.

Effective Proposal Structure

Problem statement: Clearly define the pain point you are addressing. Make the reader feel the urgency.

Proposed solution: What you will do, how it works, and why this approach.

Benefits and outcomes: What the reader gains. Quantify where possible.

Implementation plan: Timeline, milestones, and resource requirements.

Investment: Cost breakdown and ROI projections.

Call to action: What you need the reader to do next.

Effective Essay Structure

Thesis statement: Your central argument or claim, stated clearly in the opening paragraph.

Body paragraphs: Each paragraph covers one idea that supports the thesis. Open with a topic sentence, provide evidence, and explain its significance.

Counterarguments: Address opposing viewpoints to strengthen your position.

Conclusion: Restate your thesis in light of the evidence presented, and explore broader implications.

Transitions between paragraphs: Each paragraph should flow logically into the next. The last sentence of a paragraph should connect to the first sentence of the next.

The Four Steps

P - Point: State your main idea or position clearly and concisely. "I think we should delay the product launch by two weeks."

R - Reason: Explain why you hold this position. "Our beta testing revealed three critical bugs that could damage our reputation with early adopters."

E - Example: Provide specific evidence or an illustration. "Last year, when we launched the dashboard feature with known issues, we lost 200 users in the first week and spent six weeks on damage control."

P - Point (restated): Circle back to your main idea with added authority. "So a two-week delay now will save us months of recovery later. I recommend we push to March 15th."

Scenario 1: Your boss asks, "What do you think about remote work?"

P: "I believe a hybrid model works best for our team."

R: "It combines the collaboration benefits of in-person work with the focus time and flexibility of remote work."

E: "Since we started our Tuesday-Thursday in-office schedule, team productivity is up 15% and our employee satisfaction scores improved by 22 points."

P: "So I would recommend we continue with the hybrid model and formalize it as policy."

Scenario 2: A colleague asks your opinion on a marketing campaign concept.

P: "I think the concept is strong but needs a clearer call to action."

R: "The messaging creates great emotional resonance but does not tell the audience what to do next."

E: "Look at the Nike 'Just Do It' campaign -- it is aspirational but always tied to a product. Our ad creates the feeling but does not connect it to a purchase path."

P: "I would keep the creative direction but add a clear CTA at the end."

Scenario 3: In a meeting, someone asks why a project is behind schedule.

P: "We are behind because of an unforeseen integration dependency."

R: "The payment API we are integrating with changed their authentication protocol mid-sprint, requiring us to rebuild our connection layer."

E: "This is similar to what happened with the shipping module in Q2, where an external API change cost us 10 days."

P: "We are now five days behind but have a recovery plan. I will share the revised timeline by end of day."

Quick Frameworks for Thinking on Your Feet

What? So What? Now What? -- Describe the situation, explain why it matters, then propose next steps. Great for status updates.

Past-Present-Future: -- Where were we, where are we now, where are we going? Great for progress reports.

Problem-Solution-Benefit: -- What is wrong, how do we fix it, what do we gain? Great for proposals.

Feel-Felt-Found: -- "I understand how you feel. Others have felt the same way. What they found was..." Great for handling objections.

The 5-Second Pause Technique

When asked a question, resist the urge to start talking immediately. Take a breath and mentally:

1. Identify your main point -- what is the one thing you want them to take away?
2. Pick one supporting reason -- why is this true?
3. Think of one example -- what evidence do you have?

This pause feels longer to you than to your audience. In fact, audiences perceive a brief pause as confidence and thoughtfulness, not hesitation.

Before (Unstructured)

"Hey everyone, so in the meeting today we talked about a lot of things. Sarah mentioned the client is unhappy with the delivery timeline and Tom said we might need to hire a contractor. We also discussed the budget and it looks like we are over by about 12%. Oh and the design review is scheduled for next Thursday. Also marketing wants to move the launch date up by a week, but engineering is not sure they can make it. Let me know if I forgot anything."

After (Structured)

"Subject: Meeting Recap - Project Alpha: 3 Decisions Needed

Key Issues Discussed:

1. Client timeline concern: The client is unhappy with our delivery schedule. Tom proposed hiring a contractor to accelerate. Decision needed by Friday.

2. Budget overrun: We are 12% over budget. Finance team will provide options by Wednesday.

3. Launch date conflict: Marketing wants to move launch up one week. Engineering is assessing feasibility and will report by Tuesday.

Next Steps:

- Design review: Thursday, 2 PM, Conference Room B

- All decision owners: please respond to your items by the dates above."

Before (Unstructured)

"The team has been working really hard this quarter. We started with the new CRM implementation in January and it took longer than we thought because the data migration had issues. We also lost two team members to other departments, which slowed things down. On the positive side, we closed the Acme deal which was huge. We are also working on the new pricing model and have done some competitive analysis. Training for the new system is about 60% done. We think we can finish everything by end of Q2 but we might need some extra budget."

After (Structured)

"Bottom Line: We are on track to complete all Q1 initiatives by end of Q2, with one risk requiring your input.

Wins:

- Closed the Acme deal ($450K annual contract)

- CRM data migration completed; system is live

- New pricing model draft complete; competitive analysis finished

On Track:

- CRM training: 60% complete, on schedule for March 30

- New pricing model: stakeholder review scheduled for March 15

Risk:

- We lost two team members to internal transfers. Without backfill or $15K in contractor budget, Q2 completion is at risk.

Ask: Approval for $15K contractor budget. I can present the business case at Thursday's meeting."

Before (Unstructured)

"Hey, so I looked at your presentation and it is pretty good overall. The data on slide 7 was interesting but I think there might be a mistake in the chart. Also, the font is kind of small on a few slides. The opening is strong though! I liked the customer story. Maybe you could add more about the competitive landscape? And the conclusion felt a bit rushed. Oh, and can you add the Q4 projections? Great job overall though."

After (Structured)

"Great work on the presentation. Here is my feedback organized by priority:

Must fix (before the meeting):

- Slide 7: The chart data appears incorrect (shows 45% but the table below says 52%). Please verify and correct.

- Add Q4 projections -- leadership will ask for them.

Should improve:

- Strengthen the conclusion: add a summary slide with 3 key takeaways and a clear call to action.

- Increase font size on slides 4, 9, and 12 (currently too small for a conference room screen).

Consider adding:

- One slide on competitive landscape (keeps your argument airtight if questioned).

What works well (keep as is):

- The opening customer story is compelling and grabs attention immediately."

Before (Unstructured)

"We have been working on a solution for your needs. Our team has experience in this space and we think we can help you improve your operations. We offer several services including consulting, implementation, and ongoing support. Our pricing is competitive and we have worked with companies similar to yours. We would love the opportunity to partner with you. We can start as soon as next month and the project would take about 8-10 weeks. Let us know if you are interested."

After (Structured)

"Your Challenge: Your order fulfillment process currently takes 5 days, causing customer complaints and $200K in annual returns from delayed shipments.

Our Solution: A three-phase warehouse automation project that will reduce fulfillment time to 24 hours.

Expected Results:

- 80% reduction in fulfillment time (5 days to 24 hours)

- Projected $180K annual savings in reduced returns and support costs

- Improved customer satisfaction scores within 60 days of launch

Timeline: 8 weeks from kickoff. Phase 1 (assessment): weeks 1-2. Phase 2 (implementation): weeks 3-6. Phase 3 (testing and go-live): weeks 7-8.

Investment: $95,000 (ROI positive within 7 months based on projected savings).

Next Step: I would like to schedule a 30-minute call next week to walk through the detailed implementation plan. Does Tuesday or Wednesday work?"

Before (Unstructured)

"So I have been thinking about this and, well, there are a lot of factors. Customer churn is one issue, but there is also the pricing thing, and our competitors just launched that new feature, and I talked to some customers who said... well, some of them like our product but others are frustrated with the onboarding, and then there is the support issue where tickets are piling up. I think maybe we should... I mean, there are a few things we could try..."

After (Structured, Using PREP)

"I recommend we focus on fixing our onboarding experience as the top priority. [Point]

Here is why: Our data shows that 60% of churned customers leave within the first 30 days, and customer feedback consistently points to a confusing setup process as the main frustration. [Reason]

For context, when Slack simplified their onboarding in 2019, they saw a 30% reduction in early-stage churn. Our situation is similar -- great product, poor first impression. [Example]

So while pricing and competitor features are real concerns, fixing onboarding will have the fastest and most measurable impact on churn. I suggest we form a two-person task force to redesign the first-week experience by end of next month. [Point restated]"

Original message:

"Hi team, just a few things. The office will be closed on Friday for maintenance. Also, we are switching to a new project management tool starting next month -- training sessions will be held on the 15th and 17th. Oh, and the quarterly all-hands meeting is on the 20th at 3 PM. Please submit your travel expenses by end of this week. The kitchen refrigerator will be cleaned out on Thursday so take your stuff. Also, the new health insurance options are available on the HR portal -- you need to make your selections by the 25th. And one more thing -- the parking lot will be repaved next weekend so use the street parking on Monday."

Your task: Restructure this message using a topical (category-based) approach. Group related items and prioritize by importance and deadline.

Scenario: You need to convince your manager to let the team switch from weekly in-person meetings to biweekly video calls. Here are your scattered notes:

• Team spends 2 hours per week commuting to the office for the meeting
• Meeting often runs over the 1-hour slot
• Two team members are in different time zones
• A survey showed 80% of the team prefers video calls
• Biweekly cadence would free up 26 hours per year per person
• We could use the off-weeks for async written updates
• Video calls are automatically recorded for those who cannot attend
• Our most productive quarter last year had biweekly meetings

Your task: Write a pyramid-structured message: lead with the recommendation, then 2-3 supporting arguments, then evidence under each argument.

For each scenario below, identify which organizational pattern would be most effective and explain why:

1. A post-mortem report explaining why a product launch failed
2. A training manual for new employees on using the company software
3. A memo comparing three vendors for a new contract
4. A presentation about your company's global operations
5. A pitch to investors about why they should fund your startup

Use the PREP method to respond to each question. Write out all four components (Point, Reason, Example, Point restated).

1. "Should we invest in employee training programs?"

2. "Is it better to specialize in one skill or be a generalist?"

3. "Should our team adopt a four-day work week?"

Original technical update:

"We migrated the PostgreSQL database from version 12.4 to 15.2. This required updating the pg_hba.conf for SCRAM-SHA-256 authentication, rebuilding all indexes due to the B-tree deduplication changes, and rewriting three stored procedures that used deprecated syntax. We also upgraded the connection pooler from PgBouncer 1.15 to 1.19. Downtime was 47 minutes, which was within our 60-minute maintenance window. All replication slots are healthy and streaming."

Your task: Restructure this same information for two different audiences: (A) your CTO who is technical but needs the business impact, and (B) a project stakeholder who is not technical and just needs to know if things are working.