Professional Workshop Design

Professional Workshop Design

When to Use

Use this skill when the request involves designing, rebuilding, or significantly improving a workplace learning experience intended to develop skills, shift behaviors, or produce a tangible work product during the session itself.

Specific trigger scenarios:

• A corporate trainer or L&D professional asks to design a half-day or full-day workshop on a specific workplace skill (conflict resolution, data storytelling, giving feedback, change management, etc.)
• A team lead or manager needs to run a structured team development session and wants a full facilitation package -- not just an agenda
• An HR business partner is designing onboarding programming that includes skill-building components beyond information delivery
• A consultant is creating a workshop they will deliver to a client organization and needs a professional, complete deliverable
• A facilitator has a topic and a room of people but no structure, activities, or outcomes defined
• Someone needs to convert a lecture-style training into a participatory workshop format
• A team is about to go through a process change and needs a working session that produces decisions, alignment, or a shared plan

Do NOT use when:

• The audience is students in K-12 or higher education -- use workshop-design for academic contexts where pedagogy, not andragogy, governs the design
• The request is for a multi-module learning program spanning weeks or months -- use online-course-design, which handles instructional sequencing, LMS integration, and course-level architecture
• The user wants to design a conference presentation, keynote, or panel -- those are performance and communication design problems, not learning design problems
• The request is for a meeting facilitation guide without a skill-building or product-output purpose -- a meeting agenda is not a workshop
• The user needs a coaching framework for one-on-one development conversations -- that is a separate facilitation context
• The workshop is primarily a knowledge transfer event (a briefing, a policy rollout, a product demo) -- if participants will not practice, decide, or create something, a workshop is not the right format

Process

Step 1: Gather the Six Workshop Design Inputs

Before producing any design artifact, collect these six inputs. If the user has not provided them, ask directly -- do not invent them.

• Topic and scope: What specific skill, behavior, or outcome is this workshop targeting? Push for specificity. "Communication skills" is not a topic. "Giving critical feedback to a peer without damaging the relationship" is a topic.
• Audience profile: Job roles, seniority level, prior exposure to the topic, team composition (cross-functional vs. intact team), and any political or cultural dynamics that will affect engagement.
• Business driver: What organizational problem, failure, or opportunity is this workshop responding to? This anchors the design and makes the learning objective defensible to stakeholders.
• Duration and modality: Exact time available (90 minutes, half-day, full day), in-person or virtual or hybrid, and room/platform setup.
• Group size: Number of participants matters for activity design -- groups of 8 behave differently than groups of 40.
• Constraints: Pre-read or pre-work feasibility, budget for printed materials, technology available, whether a co-facilitator is present, any topics that are politically sensitive or off-limits.

Step 2: Translate Business Problem Into Measurable Learning Outcomes

Learning outcomes are the design contract -- every activity, debrief, and evaluation item must trace back to them. Write outcomes using Bloom's Taxonomy action verbs calibrated to the right cognitive level.

• For a 2-4 hour workshop, 2-3 outcomes is the right number. More than 3 outcomes almost always indicates scope creep.
• Use this formula: "Participants will be able to [verb at appropriate Bloom's level] [specific skill or knowledge] [in what context or condition]."
• Avoid knowledge-only verbs (understand, know, learn, appreciate) -- these are not observable in a workshop setting.
• Map each outcome to a Bloom's level appropriate for the audience's starting point: Apply (use a framework on a real scenario), Analyze (diagnose a situation using a structured lens), Evaluate (compare options and make a defensible recommendation), Create (produce a draft plan, document, or approach).
• If the business driver is behavioral change on the job, the workshop outcome must include at least one Apply or higher-level verb -- otherwise the learning will not transfer.
• Write a corresponding success indicator for each outcome: How will you know, during the workshop, that participants achieved it?

Step 3: Select the Right Activity Architecture

The activity sequence is the engine of a workshop. Each activity must earn its place by doing one of three jobs: building knowledge, building skill, or producing a deliverable the participant will use.

• Experience-before-instruction (EBI) sequencing: Lead with an activity that surfaces what participants already know and believe, then deliver the conceptual frame. This activates prior knowledge and creates a "need to know" before teaching. A common mistake is opening with a lecture -- adults disengage when they cannot connect new information to experience.
• Activity type selection by outcome level:
  • For Apply outcomes: case studies, role plays, structured practice with real scenarios
  • For Analyze outcomes: diagnostic tools, red team/blue team exercises, peer critique protocols
  • For Evaluate outcomes: scenario comparison, force ranking, decision matrices with real constraints
  • For Create outcomes: structured drafting sessions, prototyping, structured peer review
• The 70/30 rule: No more than 30% of workshop time should be facilitator-led instruction or content delivery. At least 70% should be participant activity, discussion, or application. In a 4-hour workshop, that means no more than 72 minutes of slides or lecture total -- and those minutes should be distributed in chunks of no more than 10-15 minutes at a time.
• Debrief design is not optional: Every activity requires a structured debrief using the What/So What/Now What model (developed by Borton, popularized in experiential learning). "What happened?" surfaces observations. "So what does that mean?" extracts the learning. "Now what will you do differently?" creates the transfer commitment.
• Group size calibration: Dyads work best for sensitive skill practice (feedback, conflict conversations). Triads work well when you need an observer role. Groups of 4-5 optimize for diverse discussion. Groups larger than 6 produce social loafing -- one or two people do the work and the rest disengage.

Step 4: Build the Full Agenda With Time Allocations

Construct the agenda at the minute level, not just the block level. Vague time blocks ("Activity 1: 45 min") produce sessions that run over and drop the most important content.

• Opening segment (10-15% of total time): Context setting, learning contract, WIIFM (What's In It For Me) -- participants need to understand why this workshop exists and what they will walk away with. Do not skip this or rush it. Resistance and disengagement in workshops almost always trace back to a failed or absent opening.
• Block structure: Alternate between facilitator-led and participant-led segments. Never stack two facilitator-led segments back to back. A reliable alternating rhythm: activity -- debrief -- mini-lecture (concept frame) -- application activity -- debrief.
• Cognitive load management: Insert a low-stakes reflection or individual activity every 45-60 minutes. Continuous discussion without individual processing time disadvantages introverts and those for whom English is a second language.
• Build in buffer: Add 10% buffer to every activity estimate. A 30-minute case study discussion will routinely run 33 minutes. A 60-minute workshop with no buffer will end 6-8 minutes late. In a 4-hour session, build in a single 15-minute explicit break plus informal buffer distributed across transitions.
• Closing segment (10-15% of total time): Action planning, synthesis, and evaluation. The most commonly cut element when sessions run long -- and the most important for transfer. Protect this time.
• Virtual workshop adjustment: Cut all time estimates by 15-20% for virtual delivery. Attention degrades faster on screen. Break a 4-hour in-person workshop into two 90-minute virtual sessions with a break day between them if the calendar allows.

Step 5: Write the Facilitator Guide

The facilitator guide is the document that lets a competent but unfamiliar facilitator run the workshop confidently. It is distinct from the participant materials.

• Two-column format: Left column shows what the facilitator says or does (including exact suggested language for key transitions, activity instructions, and debrief questions). Right column shows timing, materials needed, and watch-outs.
• Activity instructions must be self-contained: A facilitator should be able to run each activity from the guide alone, without needing to reconstruct the intent from context. Include: objective of the activity, exact instructions to give participants, time allocation, materials, debrief questions in sequence, and what a good outcome looks like.
• Facilitation notes for likely resistance: Anticipate the three or four most likely points of participant resistance or confusion for this specific topic and provide suggested facilitator responses. This is where domain knowledge of the workshop topic is essential.
• Energy management cues: Note where energy typically dips in a workshop of this length and type, and include a re-engagement technique at those points (pair-share, stand-up activity, whiteboard capture, or a short polling question in virtual settings).
• Timing checkpoints: Mark "checkpoint" moments in the guide -- points where the facilitator should assess timing and adjust. Identify which activities are expandable (can go 10 minutes longer if discussion is rich) and which are non-negotiable (must complete for the session to close cleanly).

Step 6: Design the Evaluation Using Kirkpatrick's Four Levels

Most workplace workshops are evaluated only at Level 1 (did people like it?). A professionally designed workshop includes evaluation design at Level 1 and Level 2, with a plan for Level 3 and 4 follow-up even if the client cannot commit to it yet.

• Level 1 -- Reaction: A 5-8 item post-session survey measuring relevance, facilitator effectiveness, and likelihood to recommend. Use a 5-point Likert scale. Include one open-ended question: "What one thing will you do differently as a result of this workshop?" -- this item also functions as a Level 3 leading indicator.
• Level 2 -- Learning: Designed into the workshop itself, not administered separately. Can be a pre/post knowledge check (if knowledge transfer is part of the outcome), a skill demonstration during the final activity, or a completed artifact (action plan, draft document, decision matrix) that demonstrates application. The final activity in a well-designed workshop IS the Level 2 assessment.
• Level 3 -- Behavior: A 30-day follow-up check-in, survey, or manager observation guide sent to participants and their managers. Even a 3-question email survey sent 30 days out captures useful data. Design this instrument during the workshop design phase, not as an afterthought.
• Level 4 -- Results: Identify the business metric this workshop is intended to move (reduced conflict escalations to HR, faster onboarding to productivity, improved 360 feedback scores, decreased error rate in a process). Not every workshop has a cleanly attributable result, but naming the metric -- even without baseline data -- creates accountability and demonstrates L&D's connection to business outcomes.

Step 7: Package the Complete Workshop Deliverable

Assemble all components into a coherent, labeled package. A professional workshop package has five components:

• Agenda (participant-facing): Clean, formatted version of the session schedule with activity names and timing. Does not include facilitator notes.
• Facilitator guide (facilitator-facing): Complete run-of-show with all scripts, debrief questions, facilitation notes, and timing checkpoints.
• Participant materials: Handouts, worksheets, frameworks, and templates participants use during activities. Each item should be usable after the workshop as a job aid.
• Activity materials: Any materials specific to activities -- case study scenarios, role-play cards, scenario cards, assessment instruments. Labeled clearly by activity.
• Evaluation instruments: Level 1 survey, Level 2 assessment (if a separate instrument), and Level 3 follow-up plan.

Output Format

## Workshop Design Package: [Workshop Title]

**Designed for:** [Job roles / team / audience description]
**Business driver:** [The organizational problem or opportunity this addresses]
**Duration:** [X hours] | **Modality:** [In-person / Virtual / Hybrid]
**Group size:** [X participants] | **Facilitator setup:** [Solo / Co-facilitated]
**Version:** [1.0 -- initial design]

---

### Learning Outcomes
By the end of this workshop, participants will be able to:
1. [Bloom's verb] [specific skill] [in specific context] -- assessed via [Level 2 method]
2. [Bloom's verb] [specific skill] [in specific context] -- assessed via [Level 2 method]
3. [Bloom's verb] [specific skill] [in specific context] -- assessed via [Level 2 method]

---

### PART 1: PARTICIPANT-FACING AGENDA

| Time | Segment | Format | Materials |
|------|---------|--------|-----------|
| 0:00-0:15 | Welcome, context, and learning contract | Facilitator-led | Slides |
| 0:15-0:35 | Opening activity: [Name] | [Pairs / Small groups / Individual] | [Handout #] |
| 0:35-0:45 | Debrief + concept frame: [Topic] | Large group + mini-lecture | Slides |
| 0:45-1:15 | Activity 1: [Name] | [Format] | [Materials] |
| 1:15-1:30 | Debrief: [Key question] | Large group discussion | -- |
| 1:30-1:40 | BREAK | -- | -- |
| 1:40-2:10 | Activity 2: [Name] | [Format] | [Materials] |
| 2:10-2:25 | Debrief + concept frame: [Topic] | Large group + mini-lecture | Slides |
| 2:25-2:50 | Application activity: [Name] | Individual / Pairs | Action plan template |
| 2:50-3:00 | Synthesis, commitments, and evaluation | Facilitator-led | Evaluation form |

---

### PART 2: FACILITATOR GUIDE

#### Opening (0:00-0:15)
**Facilitator says:** [Suggested language for welcome and context-setting]
**Key point to land:** Why this workshop exists -- connect to the business problem explicitly.
**Learning contract:** Establish participation norms. Suggested norms: [specific norms for this topic]
**Watch-out:** [Common issue in the opening for this topic -- e.g., participants who already feel they have this skill and disengage early]

---

#### Opening Activity: [Name] (0:15-0:35)
**Objective:** [What this activity surfaces or activates]
**Instructions to give participants:**
  > "[Exact language]"
**Time:** [X] minutes
**Grouping:** [How to form groups]
**Materials:** [What participants need]

**Debrief sequence (What / So What / Now What):**
1. What: "[Specific question]"
2. So What: "[Specific question]"
3. Now What: "[Specific question]"

**What good looks like:** [Description of a productive debrief outcome]
**Facilitation watch-out:** [Specific risk for this activity]
**Timing note:** [Expandable / Non-negotiable] -- if discussion runs long, [adjustment instruction]

---

#### Concept Frame: [Topic Name] (included in opening debrief segment)
**Core model or framework:** [Name and 2-3 sentence explanation]
**Key points to land:**
1. [Point 1 -- specific to topic]
2. [Point 2]
3. [Point 3]
**Common misconceptions to address:** [Specific misconception this audience typically holds]

---

#### Activity 1: [Name] (0:45-1:15)
[Same format as opening activity -- objective, instructions, debrief, watch-out, timing note]

---

#### Activity 2: [Name] (1:40-2:10)
[Same format]

---

#### Application Activity: [Name] (2:25-2:50)
**Objective:** Participants create a specific artifact they will use after the workshop
**Instructions:** [Step-by-step]
**The artifact:** [Description of what participants produce -- must be immediately usable]
**Debrief:** Pair-share, then 2-3 volunteers share with the room
**Watch-out:** Participants who do not have a real situation to apply to -- provide a prepared scenario as a fallback

---

#### Close (2:50-3:00)
**Synthesis question to the room:** "[Specific question]"
**Logistics:** Evaluation form distribution, any follow-up communication
**Facilitator reminder:** Collect evaluation forms before participants leave -- response rate drops to under 20% if sent via email after the session

---

### PART 3: PARTICIPANT MATERIALS

#### Handout 1: [Name]
[Framework, model, or job aid content -- fully written out, not described]

#### Handout 2: [Name -- typically the application worksheet]
[Structured template with labeled fields participants complete during the application activity]

---

### PART 4: EVALUATION

#### Level 1 -- Reaction Survey
Rate each item 1 (strongly disagree) to 5 (strongly agree):
1. This workshop was relevant to my current work.
2. The activities helped me practice, not just learn about, the topic.
3. I would recommend this workshop to a colleague in a similar role.
4. The facilitator created an environment where I felt comfortable participating.
5. The time allocated was appropriate for the content covered.

Open response: What is one thing you will do differently as a result of this workshop?

**Target benchmark:** Mean score of 4.2+ across items 1-3 indicates the design is landing. Below 4.0 on item 2 signals activity design needs revision.

#### Level 2 -- Learning Assessment
**Method:** [Describe the Level 2 assessment built into the application activity or final artifact]
**What "demonstrated competence" looks like:** [Specific criteria]

#### Level 3 -- 30-Day Follow-Up Plan
**Follow-up instrument:** 3-question email survey to participants at day 30
1. Have you applied [specific skill from the workshop] at least once since the session?
2. If yes: describe one situation where you used it and what the outcome was.
3. What support, if any, would help you continue applying what you learned?
**Recommended:** Share results with participant managers as a coaching prompt

#### Level 4 -- Business Metric
**Target metric:** [Specific, named organizational metric]
**Baseline (if known):** [Current state]
**Attribution approach:** [How you will attempt to isolate the workshop's contribution -- pre/post comparison, manager observation, etc.]

---

### DESIGN NOTES FOR FACILITATOR
- [Any specific political or cultural dynamics to be aware of with this audience]
- [One or two facilitation techniques especially effective for this topic]
- [How to handle the most likely point of participant resistance]

Rules

1. Never confuse a workshop with a training or a meeting. A workshop is defined by participant practice and product creation. If the user's request is primarily about information delivery (a new policy, a tool demo, a product briefing), redirect them: a well-designed presentation plus a Q&A is more appropriate than forcing a workshop structure onto passive content.

2. Learning outcomes must use observable Bloom's verbs. Reject verbs like "understand," "appreciate," "learn," or "be aware of" -- these cannot be observed or assessed in a workshop setting. If the user provides outcomes written this way, rewrite them before proceeding with design.

3. The 70/30 rule is non-negotiable. At least 70% of workshop time must be participant activity, not facilitator talking. Calculate this explicitly when building the agenda. If the math does not work, cut content -- not activities.

4. Every activity must have a debrief. An activity without a debrief is an exercise. The debrief is where learning is constructed. Use the What/So What/Now What structure as the minimum debrief scaffold. Debrief time should be roughly 30-40% of the activity time (a 20-minute activity deserves a 7-10 minute debrief).

5. Group size governs activity design. Activities designed for groups of 12-16 do not scale to groups of 40+ without structural modification. If the group is larger than 25, every discussion-based activity must be redesigned as small-group work with a structured report-out, not open large-group discussion.

6. Virtual workshops require fundamentally different design, not just the same design on Zoom. Virtual sessions must include participant interaction every 5-7 minutes maximum (polling, chat response, annotation, breakout room). A 90-minute virtual session with one breakout and otherwise passive listening is not a workshop -- it is a webinar. If the user requests a virtual workshop, apply virtual-specific design from the start.

7. The application activity in the closing segment is the most important activity in the workshop. It is the primary Level 2 assessment, the transfer mechanism, and the artifact participants take back to their work. It must never be cut for time. If the session is running long, cut earlier content delivery segments, not the application activity.

8. Do not design for topics you have not confirmed with the user. If the user says "design a workshop on leadership," ask which aspect of leadership, for what audience, responding to what business problem. "Leadership" is not a workshop topic -- it is a category containing dozens of possible workshop topics.

9. Evaluation design is part of workshop design, not a follow-on task. Level 1 and Level 2 evaluation instruments must be produced as part of the workshop package. A "we'll figure out evaluation later" approach is a professional design failure. Level 3 and Level 4 plans should be included even if implementation is uncertain.

10. Participant materials must be usable as job aids after the workshop. Any handout or worksheet a participant completes during the session should be designed so it functions as a standalone reference tool back on the job. If a participant's only record of the workshop is their notes on a slide printout, the materials have failed their design purpose.

Edge Cases

The user has a very short time window (60 minutes or less): A 60-minute session is not long enough for a full workshop if the goal includes skill practice and application. Be direct about this constraint. Design the session as a structured working session with one focused activity and debrief, not a compressed version of a full workshop. Recommend the user either expand the time to 90 minutes minimum or reframe the objective to something achievable in the time available -- for example, a shared understanding exercise or a commitment-setting session rather than skill development.

The topic is sensitive or carries emotional weight (conflict, bias, mental health, performance issues): Sensitive topics require two specific design adjustments. First, the opening learning contract must include explicit participation norms that address the sensitivity directly -- for example, "we will share observations, not judgments" or "this is a safe space to practice, not a performance evaluation." Second, activities must use scenarios that are realistic but not so close to current team dynamics that participants feel exposed or targeted. Do not use real names or real recent incidents as case study material. Create composite, anonymized scenarios. Include a facilitator note about recognizing and managing emotional activation in participants.

The audience is highly skeptical or has been "trained to death": When the audience has low trust in L&D or has been through many workshops that produced no change, the design must work differently. Open the session by naming the skepticism explicitly and inviting it: "You've probably sat through sessions on this topic before. Let's start with what hasn't worked." This is an application of Knowles' principle that adults need to know why they are learning -- but it goes further, acknowledging that prior learning experiences may have been poor. Reduce facilitator-led segments to the absolute minimum. Lead with activities. Let participants discover the frameworks through their own experience rather than receiving them from a facilitator.

The user is designing the workshop for someone else to facilitate: When the designer is not the facilitator, the facilitator guide must be significantly more detailed. Every activity needs exact scripted language for the setup, not just a summary. Debrief questions must be written out completely. Watch-outs must be specific and actionable. The guide should also include a facilitator preparation checklist (what to review, what to rehearse, what to arrange logistics for) and a 30-minute pre-session setup guide. Specify that a facilitator run-through -- even a 60-minute table-read of the guide -- is a non-optional step before delivery.

The workshop is part of a larger program: When this workshop is one module in a learning journey, three things change in the design. First, do not re-teach concepts covered in prior modules -- build on them explicitly ("In the last session you learned X -- today we will practice applying X to Y"). Second, design a connect-forward element in the closing: tell participants what the next session will build on from today's learning and assign a practice task between sessions. Third, the Level 3 evaluation should be designed as a cumulative behavior measure across the program, not a standalone 30-day check-in.

The user wants to adapt an existing training into a workshop: Many users are starting with a slide deck of content and want help converting it into a workshop. The adaptation process has a specific sequence: (1) identify every point in the existing content where participants could practice something instead of being told something -- these become activities; (2) identify the two or three most essential conceptual points that cannot be cut -- everything else either becomes pre-read material or gets cut entirely; (3) rebuild the flow using the experience-before-instruction principle, which typically means moving the activities earlier and the concept frames later than they appear in the original training. Warn the user that a good training-to-workshop conversion typically retains about 30-40% of the original slide content and adds significant new activity material.

Group is mixed in terms of experience level with the topic: When participants range from novice to experienced on the same topic, do not design a single track that disadvantages both groups. Two approaches work: (1) tiered activities, where novices and experienced participants receive different scenario complexity levels for the same activity structure; (2) peer teaching design, where experienced participants are intentionally paired with novices and the debrief draws on what the experienced participants did differently. The second approach also reinforces the experienced participants' learning through the act of teaching. Avoid the common mistake of designing to the lowest common denominator -- experienced participants will disengage, which poisons the room energy for everyone.

Example

Input: "I need to design a half-day workshop on giving and receiving feedback for 20 mid-level managers at a financial services firm. They're going into their annual performance review cycle next month. The VP of HR says managers are avoiding difficult conversations and defaulting to vague, positive feedback that doesn't help employees develop. The workshop needs to be in-person. I'll be facilitating it myself."

Output:

Workshop Design Package: Having Honest Performance Conversations

Designed for: Mid-level managers (individual contributor supervisors and team leads), financial services sector Business driver: Managers are avoiding difficult feedback conversations during the performance review cycle, resulting in vague, development-free reviews that do not improve performance and create legal risk during underperformance processes Duration: 4 hours (half-day) | Modality: In-person Group size: 20 participants | Facilitator setup: Solo-facilitated Version: 1.0 -- initial design

Learning Outcomes

By the end of this workshop, participants will be able to:

1. Diagnose the specific avoidance pattern driving their own reluctance to give difficult feedback -- assessed via self-diagnostic worksheet completed in the opening activity
2. Apply the SBI (Situation-Behavior-Impact) feedback model to at least two realistic performance scenarios specific to financial services management contexts -- assessed via written scenario practice in Activity 1
3. Conduct a structured performance conversation that includes a specific developmental commitment, using a co-created conversation framework -- assessed via observed role play in Activity 2, with peer and self-evaluation

PART 1: PARTICIPANT-FACING AGENDA

PART 2: FACILITATOR GUIDE

Opening (0:00-0:15)

Facilitator says:

"Before we get into the content, I want to name why we're here. The performance review cycle starts in four weeks. And if you're like most managers -- including excellent ones -- there's at least one conversation on your list that you've been putting off. Today is about making sure you don't put it off again, and that when you have it, it actually helps the person on the other side of the table. We're not here to talk about feedback theory. We're here to practice the real conversations."

Key point to land: Connect the workshop explicitly to the business timeline (review cycle starting next month). Make it immediately relevant by naming the avoidance pattern directly, without judgment.

Learning contract -- suggested norms to establish:

• "What's said in this room stays in this room -- we'll be using real scenarios, and we need psychological safety to practice honestly."
• "This is a practice space, not a performance evaluation. Getting it wrong here is the point."
• "Phones down during activities. You have 4 hours. Your team can wait."

Watch-out: Financial services managers often have high status orientation and may resist being asked to role-play or to admit difficulty with a management fundamental. Name this explicitly: "Some of you have been managers for 10+ years. That doesn't make this easy -- in fact, the longer you've been avoiding a conversation, the harder the first one is. That's what we're here to fix."

Opening Activity: The Avoidance Audit (0:15-0:35)

Objective: Surface the specific avoidance pattern driving each participant's reluctance, and break the implicit assumption that everyone in the room finds feedback easy or is failing for the same reason.

Instructions to give participants:

"Take Handout 1. You have 8 minutes to answer these four questions individually -- do not share yet, and be honest with yourself. This is not collected. When you're done, turn to the person next to you and share: what is one pattern you noticed in your answers?"

Handout 1 content -- The Avoidance Audit: Think of a performance conversation you have been delaying or dreading. Answer the following:

1. What specific concern is holding you back? (Check all that apply)
   • Fear of damaging the relationship
   • Uncertainty about whether my assessment is fair
   • Concern the person will become defensive or upset
   • Worry about saying it "wrong"
   • Not sure the feedback will actually change anything
   • The person's reaction in previous conversations has been difficult
   • Other: ________
2. How long have you been sitting on this feedback?
3. What has the cost been of not giving it? (To you, to them, to the team?)
4. What would you say if you knew the person could hear it without any defensiveness?

Time: 8 minutes individual, 7 minutes pairs Grouping: Self-selected pairs with neighbors Materials: Handout 1

Debrief sequence:

1. What: "Without sharing specifics, what was the most common concern that came up in your pair conversations?" -- capture on whiteboard
2. So What: "Look at what we've captured. This is not a skills problem -- most of these are emotional or relational concerns. What does that tell us about what's actually making feedback difficult in your organization?"
3. Now What: "The framework we'll work with today addresses each of these concerns specifically. The goal is to leave with a tool that reduces the ambiguity and the risk enough that the avoidance becomes harder to justify than the conversation."

What good looks like: Whiteboard should show 5-7 distinct avoidance drivers. The most common for this audience will be "fear of damaging the relationship" and "concern about defensive reaction." These two themes should be explicitly connected to the SBI model in the following concept frame.

Facilitation watch-out: Some participants will share more than is productive -- real, current employee situations with identifying details. Redirect: "I'm going to stop you there -- let's keep it anonymous so we can focus on the pattern, not the person."

Timing note: Expandable by 5 minutes if pair discussion is rich and producing useful whiteboard content. Non-negotiable minimum is 15 minutes total.

Concept Frame: Why We Avoid Hard Feedback (0:35-0:50)

Core framework: The Threat/Reward Response in feedback conversations (based on David Rock's SCARF model applied to feedback delivery)

Key points to land:

1. Avoidance is not weakness or cowardice -- it is a rational response to perceived social threat. The brain processes social threat (damaged relationship, conflict) using the same neural circuits as physical threat. Understanding this removes shame from the avoidance pattern.
2. Vague feedback does not protect the relationship -- it creates the slow-burn resentment of a relationship where no one is honest. The most damaging feedback conversations are the ones that never happen.
3. Structure reduces threat for both parties. When a manager uses a consistent, predictable framework for a difficult conversation, it signals to the recipient that the feedback is about observed behavior and impact -- not a judgment of their character. This is precisely what SBI is designed to do.

Common misconception to address directly: "Good feedback should feel natural and conversational -- using a framework feels robotic." Counter: surgeons use checklists. Pilots use pre-flight protocols. The stakes in a performance conversation are high enough that structure is a professional tool, not a crutch. The goal is to practice the framework until it feels natural -- that takes repetition, which is why this workshop exists.

Introduce SBI:

• Situation: Describe the specific, observable situation. When. Where. Under what circumstances.
• Behavior: Describe the specific, observable behavior -- not the interpretation, not the intention, not the character trait. What you saw or heard, not what you concluded.
• Impact: Describe the concrete impact on the team, the work, the client, or you. Not "it was unprofessional." Specifically: what happened as a result?

Activity 1: SBI Clinic -- Rewriting Vague Feedback (0:50-1:30)

Objective: Participants practice distinguishing vague, evaluative feedback from specific, behavioral feedback and rewrite real-world examples using the SBI model.

Instructions to give participants:

"In your groups of 4, you have 6 scenario cards -- each one shows a piece of feedback that a real manager might give. Your job is: first, identify what's wrong with it (too vague? evaluative? characterizes the person rather than the behavior?). Then rewrite it using SBI. You should have an SBI version for each scenario in 25 minutes. One person per group will share your best rewrite with the room."

Scenario cards content (Handout 2 -- financial services-specific):

Card 1: "Your communication style is sometimes off-putting to clients." -- Problem: no situation, no specific behavior, "off-putting" is an evaluation. Rewrite target: "In the Morrison account call last Tuesday, when the client asked about the fee structure, you responded before he finished his question and described the tiered pricing without checking whether he had the context to follow it. He asked the same question again later, and we lost 10 minutes re-explaining. The impact was that we ran over the meeting time and left him less confident than when he came in."

Card 2: "You need to take more ownership of your work." -- Problem: "ownership" is abstract, no behavior specified, could mean 10 different things.

Card 3: "Your attitude during the Q3 review was problematic." -- Problem: "attitude" is a character attribution, no specific behavior, "problematic" is evaluative without content.

Card 4: "You're a strong contributor but you need to work on your leadership presence." -- Problem: "leadership presence" is a performance review cliché with no behavioral definition.

Card 5: "Your analysis is usually good but sometimes you miss things." -- Problem: no situation, no specific behavior, frequency hedging ("sometimes," "usually") undermines the message.

Card 6: "You handled the client situation poorly." -- Problem: no specific situation identified (which one?), "poorly" is evaluative without content.

Time: 25 minutes group work + 10 minutes report-out (one rewrite per group of 5 groups reporting = 2 minutes each, plus facilitation)

Grouping: 5 groups of 4 (assign groups -- do not let participants self-select, which creates cliques). Mix seniority levels within groups.

Materials: Handout 2 (scenario cards), space to write

Debrief sequence:

1. What: "What was the hardest card to rewrite, and why?"
2. So What: "What do all six original examples have in common? What pattern do you see in the language we default to?" -- Answer the facilitator is drawing out: all six use evaluative labels ("off-putting," "ownership," "attitude") instead of observed behavior. This is the fundamental design flaw in most performance feedback.
3. Now What: "When you look at the feedback you're sitting on right now -- the conversation from your Avoidance Audit -- can you write an SBI version of it? Take 90 second

…(truncated)