PSYCH 678 Week 6 Presenting to a Business Audience Example

Twenty Minutes With the Partners: Building and Delivering a Midpoint Presentation That Ends With a Decision

[Student Name]

University of Phoenix

PSYCH/678: Consulting and Business Skills

Week 6 Assignment

[Instructor Name]

[Date]

The engineering firm, its people, the results and all figures are composites written for a model paper; presentation guidance comes from the sources listed.

Six months after the partners approved the implementation, I had twenty minutes on the agenda of their quarterly management meeting to report midpoint results and ask for two decisions. What follows covers the build, the talk itself and how the room responded.

The Audience

The room held Ted, the managing partner, who introduced forced distribution and agreed reluctantly to end it; Lauren, the operations chief, who sponsored the work; and eleven managers, most of them engineers by training, comfortable with numbers and impatient with anything that sounds like human resources jargon. Ted needed to see that dropping the quota had not opened the door to inflated ratings. Managers needed to hear that the extra work of check-ins was worth it.

Structure: Answer First

Minto (2009) argued that clear business communication starts with the main idea and then groups supporting ideas beneath it in a logical pyramid, so that the audience knows the point before hearing the reasons. Her suggested opening sketches the current state of affairs, names what has disturbed it and so raises a question, then answers that question, and urged writers and speakers to group supporting points so that each group summarizes the ideas below it.

My opening slide carried one sentence: "The new system is working; we recommend making it permanent and funding a second year at $14,000." Then came the situation, last year's departures and distrust; the complication, whether ending the quota would cost the firm its ability to distinguish performance; and the answer, supported by three grouped points: engineers trust ratings more, managers are giving feedback and ratings still differentiate.

The Evidence

Each supporting point had one slide. Trust: agreement that ratings reflect contribution rose from 29 to 47 percent on the six-month pulse survey, short of the 55 percent target but moving. Feedback: 84 percent of check-ins were completed in the first two quarters, and the share of engineers reporting quarterly feedback rose from 36 to 79 percent. Differentiation: in the midyear calibration, 26 percent of engineers were rated in the top category, below the 30 percent limit, and the distribution still separated strong performers from others. No engineer rated in the top two categories has left since launch, compared with four in the same period last year, though six months is too short to be sure.

Designing Slides for Comprehension

Mayer and Moreno (2003) described how multimedia presentations can overload the limited capacity of people's visual and verbal channels and offered ways to reduce that load. These include moving words off the screen into narration, removing interesting but extraneous material, signaling what matters, placing words next to the graphics they describe, avoiding narration that repeats on-screen text word for word and breaking complex material into segments.

Accordingly, each slide carried one headline sentence stating its message and one graphic, such as a before-and-after bar chart for trust, with labels on the bars instead of a legend. I narrated rather than reading text. I removed a slide on the history of performance appraisal research that I liked but the audience did not need.

The slide I was proudest of, a summary of a century of appraisal research, was the first one I cut.

Making It Stick

Heath and Heath (2007) examined why some ideas are remembered and acted on while others fade, concluding that sticky ideas tend to be simple, unexpected, concrete, credible, emotional and told as stories. Abstract statistics persuade less than a concrete case, especially when paired with data that make the case credible.

So between the data slides, I told one story, with permission: a mid-level engineer who had been moved down in calibration last year and was interviewing elsewhere told me that her first quarterly check-in was the first time her manager had asked about her goals in three years. She withdrew from the other firm's hiring process. Managers nodded; two later said they had similar stories.

Translating the Concepts

I avoided psychological terms. "Frame-of-reference rater training" became "training managers to use the same yardstick." "Psychological safety" did not appear. The business case slide repeated the cost of a senior departure, $150,000, beside the program's cost to date, so every manager could do the arithmetic. I also showed managers' time cost, about two hours per engineer per year, because hiding it would have invited the first skeptical question of the afternoon.

Rehearsal

I rehearsed the talk three times, two times by myself against a stopwatch and one time with Lauren, who played Ted. The first run took twenty-eight minutes, mostly because I explained the survey method in detail no one in the room would ask about. Cutting that to one sentence, with the method in a backup slide, brought the talk to seventeen minutes and left time for questions. Lauren's role play surfaced two questions I had not prepared for: whether managers who skipped check-ins would face consequences and whether last year's calibrated ratings would be revisited. I added short answers to my notes for both.

What I Left Out

Several findings did not make the main deck. Differences between offices, the details of the coaching sessions and the full survey results went into an appendix handed out after the meeting. Leaving them out was hard, because each represented real work, but the audience needed three points and a decision, not a tour of the engagement. Managers who wanted more could read the appendix, and two did, sending follow-up questions the next day.

The Hard Question

Ted asked the question I expected: "How do I know ratings won't creep up next year?" I had prepared a backup slide showing the partner review guide, which flags any team where more than forty percent receive top ratings, and I proposed that he chair the first annual review. He agreed, which mattered more than any chart.

The Close

My last slide repeated the two requests: make the guided rating system and quarterly check-ins permanent policy, and approve a second-year budget of $14,000 for refresher training and new-manager onboarding, with HR taking over facilitation after that. I asked for a decision before the end of the meeting. Ted and Lauren conferred briefly and approved both, and the HR manager left the meeting with a date to begin planning the second year.

Reflection

Three choices made the difference. Leading with the answer kept the room from waiting. Cutting slides forced me to decide what mattered. Preparing for Ted's question turned his likely objection into his ownership. If I did it again, I would show the target I missed, trust at 47 instead of 55 percent, more prominently and explain what we are doing about it, because an engineer audience notices when a number is softened.

Conclusion

A twenty-minute presentation built answer first, with one message per slide, one concrete story and a prepared answer to the hardest question, turned six months of work into a decision.

References

Heath, C., & Heath, D. (2007). Made to stick: Why some ideas survive and others die. Random House.

Mayer, R. E., & Moreno, R. (2003). Nine ways to reduce cognitive load in multimedia learning. Educational Psychologist, 38(1), 43-52. https://doi.org/10.1207/S15326985EP3801_6

Minto, B. (2009). The pyramid principle: Logic in writing and thinking (3rd ed.). Pearson Education.