{"id":5652,"date":"2023-07-07T17:11:43","date_gmt":"2023-07-07T17:11:43","guid":{"rendered":"https:\/\/brainapps.io\/blog\/?p=5652"},"modified":"2026-03-29T08:54:26","modified_gmt":"2026-03-29T08:54:26","slug":"conquer-tough-conversations-a-comprehensive","status":"publish","type":"post","link":"https:\/\/brainapps.io\/blog\/2023\/07\/conquer-tough-conversations-a-comprehensive\/","title":{"rendered":"How to Have Difficult Conversations at Work: FRAME Model, Scripts &#038; Ready Checklist"},"content":{"rendered":"<h2>Intro &#8211; a short story and a bold promise<\/h2>\n<p>Sam let a five-minute feedback conversation slide. A missed deadline turned into a sprint, then a fight between two teams, then a delayed product launch. All because a small issue went unspoken. If that sounds familiar, this guide shows how to have difficult conversations at work without drama.<\/p>\n<p>Promise: a compact, repeatable FRAME you can use in 15-45 minutes to get honest outcomes and preserve trust. Use it to prepare, run the talk, and follow up so problems shrink instead of exploding.<\/p>\n<p><strong>FRAME<\/strong> &#8211; Facts, Reach for understanding, Agenda &#038; Goal, Make a plan, End with commitments. Learn the steps, practice the scripts, and use the checklist to move from awkward to effective.<\/p>\n<h2>The FRAME model &#8211; a repeatable framework for every difficult conversation<\/h2>\n<p>FRAME gives you a reliable spine for difficult conversations with employees, peers, or your boss. It keeps the talk focused on observable behavior, shared understanding, and clear follow-up.<\/p>\n<ul>\n<li><strong>Facts<\/strong> &#8211; State observable behavior or incidents. Offer 1-3 concrete examples with dates or deliverables. Facts narrow defensiveness and keep the issue specific.<\/li>\n<li><strong>Reach for understanding<\/strong> &#8211; Invite their perspective. Ask 1-2 open questions and listen. Curiosity uncovers root causes you can fix together.<\/li>\n<li><strong>Agenda &#038; Goal<\/strong> &#8211; Be explicit about why you&#8217;re talking (understand, fix, escalate) and the timebox. Clear purpose prevents hidden agendas and anxiety.<\/li>\n<li><strong>Make a plan<\/strong> &#8211; Co-create actions with owners, deadlines, and simple success metrics. Plans turn intent into measurable change.<\/li>\n<li><strong>End with commitments<\/strong> &#8211; Summarize aloud, confirm acceptability, and set a check-in. Commitments close the feedback loop and protect trust.<\/li>\n<\/ul>\n<p><strong>Timing guide:<\/strong> Prep 5-7 minutes for quick issues or 15-30 for complex ones. Most difficult conversations run 10-30 minutes; formal performance talks may need 45-60 minutes. Reserve 5-15 minutes afterward for immediate notes and next steps.<\/p>\n<h2>Prepare with purpose &#8211; what to do before you schedule the talk<\/h2>\n<p>Preparation decides whether a hard conversation heals or harms. Do these fast checks before you hit &#8220;schedule.&#8221;<\/p>\n<ul>\n<li><strong>Mental prep:<\/strong> Check your emotion. Ask: Am I curious or charged? If you&#8217;re reactive, wait or rehearse until curiosity leads the talk.<\/li>\n<li><strong>Real goal:<\/strong> Decide whether you need to understand, fix an issue, or escalate. That goal shapes tone and agenda.<\/li>\n<li><strong>Stakeholder map:<\/strong> Who needs to know, who should join, who to warn? Involve HR for legal issues, repeated policy breaches, or power imbalances.<\/li>\n<li><strong>Evidence map:<\/strong> Separate facts from interpretations. Pick 2-3 concrete examples you will use and decide what to leave out.<\/li>\n<li><strong>Empathy rehearsal:<\/strong> Answer three quick questions: What pressures might they be under? What explanation would convince me? What small concession could I make?<\/li>\n<li><strong>Logistics:<\/strong> Choose a private, neutral setting and a time when neither person is rushed. Send a short agenda only if it helps frame the conversation.<\/li>\n<\/ul>\n<h2>Run the conversation &#8211; a tight structure that keeps things productive<\/h2>\n<p>Treat the meeting like a short workshop: open, discover, share, decide. Keep FRAME in your head and let curiosity steer the talk.<\/p>\n<p><strong>Opening (first 60 seconds):<\/strong> Neutral opener, permission statement, and outcome. Example: &#8220;Thanks for meeting. I want to talk about X so we can prevent Y &#8211; my goal is to understand and agree a next step.&#8221; Timebox the conversation up front.<\/p>\n<p><strong>Listening &#038; discovery:<\/strong> Ask precise questions and listen more than you speak. Use quick reflective checks like &#8220;It sounds like&#8230;&#8221; to confirm you heard them. Try these prompts:<\/p>\n<ul>\n<li>&#8220;Help me understand what happened from your side.&#8221;<\/li>\n<li>&#8220;What&#8217;s getting in the way of the result we expected?&#8221;<\/li>\n<li>&#8220;How do you see this affecting timelines or the team?&#8221;<\/li>\n<\/ul>\n<p><strong>Share your view without blame:<\/strong> Use fact \u2192 impact \u2192 invitation. Prefer &#8220;I&#8221; language over &#8220;you.&#8221; Example: &#8220;On Tuesday your report arrived two days late (fact), which delayed the review and doubled Abby&#8217;s workload (impact). Help me understand what happened.&#8221;<\/p>\n<p><strong>Keep it two-way:<\/strong> Timebox key parts, check understanding, and use short reflective phrases to stay aligned. If you need to steer, restate the agreed goal and move to options.<\/p>\n<p><strong>Manage emotions and derailers:<\/strong> If emotion spikes, pause, name the feeling, offer a short break, or reset the agenda. Agree to continue later rather than forcing a poor outcome.<\/p>\n<h3>Scripts and examples (copy-ready)<\/h3>\n<p><strong>Manager \u2192 employee (recurring missed deadlines)<\/strong><\/p>\n<p>Opening: &#8220;Thanks for meeting. I want to talk about deadlines so we can keep the project on track &#8211; my goal is to understand and agree a plan.&#8221;<\/p>\n<p>Discovery: &#8220;Help me understand what&#8217;s making it hard to hit the last three deadlines.&#8221;<\/p>\n<p>Impact &#038; next step: &#8220;When reports are late, reviews slip and the release moves. Let&#8217;s try a 2-week plan: you flag risks 48 hours before the due date and I&#8217;ll help re-prioritize blockers. Can we check in Wednesday?&#8221;<\/p>\n<p><strong>Peer \u2192 peer (collaboration issues)<\/strong><\/p>\n<p>Opening: &#8220;Can we talk about collaboration on X? I want us to work smoother.&#8221;<\/p>  <section class=\"mtry limiter\">\r\n                <div class=\"mtry__title\">\r\n                    Try BrainApps <br> for free                <\/div>\r\n                <div class=\"mtry-btns\">\r\n\r\n                    <a href=\"\/signup?from=blog\" class=\"customBtn customBtn--large customBtn--green customBtn--has-shadow customBtn--upper-case\">\r\n                        Get started                   <\/a>\r\n              <\/a>\r\n                    \r\n                \r\n                <\/div>\r\n            <\/section>   <\/p>\n<p>Discovery: &#8220;From your view, what&#8217;s been the blocker to aligning on shared tasks?&#8221;<\/p>\n<p>Next step: &#8220;Can we split ownership clearly and share a quick weekly update for two weeks?&#8221;<\/p>\n<p><strong>Upward feedback (unclear priorities)<\/strong><\/p>\n<p>Opening: &#8220;Can I share something that would help me hit goals faster?&#8221;<\/p>\n<p>Discovery: &#8220;How are you viewing the team&#8217;s top priority this quarter?&#8221;<\/p>\n<p>Proposed fix: &#8220;Could we set a 15-minute alignment weekly or keep a prioritized backlog doc?&#8221;<\/p>\n<p><strong>Variation notes:<\/strong> Shorten for quick check-ins (one example, one discovery question, one action). Lengthen for formal performance talks (add context, examples, and time for questions).<\/p>\n<h2>Solve together &#8211; co-creating a plan and making accountability clear<\/h2>\n<p>Co-creation produces faster, more durable change than orders. Use timeboxes to move from ideas to commitments.<\/p>\n<p><strong>3-minute divergent-convergent technique:<\/strong> Spend 3 minutes listing fixes, pick two, weigh pros and cons for 2 minutes, then select a trial solution. Short timeboxes prevent overthinking.<\/p>\n<p><strong>Decide and document:<\/strong> For every action, capture who, what, when, success metric, and a check-in date. Put it in a shared doc or calendar invite immediately so the agreement is visible.<\/p>\n<ul>\n<li><strong>Who<\/strong> &#8211; owner<\/li>\n<li><strong>What<\/strong> &#8211; concrete step<\/li>\n<li><strong>When<\/strong> &#8211; deadline or cadence<\/li>\n<li><strong>Success metric<\/strong> &#8211; how we&#8217;ll know it worked<\/li>\n<li><strong>Check-in<\/strong> &#8211; agreed review date\/time<\/li>\n<\/ul>\n<p>If you can&#8217;t agree, don&#8217;t force closure. Agree on a time-limited trial, involve a neutral party, or escalate. Even when progress stalls, a clear next step (trial, mediator, escalation) keeps momentum.<\/p>\n<p>Simple roadmaps: 2-week tweaks for behavior, 30-day fixes for performance, 90-day plans for process change. Match the timeline to the problem.<\/p>\n<h2>Common mistakes, recovery moves, and when to stop trying<\/h2>\n<p>Most derailments are predictable. Spot them early and use a recovery script to get back on track.<\/p>\n<ul>\n<li>Starting angry &#8211; pause and reschedule.<\/li>\n<li>Monologuing &#8211; ask, then listen.<\/li>\n<li>Making it personal &#8211; critique behavior, not character.<\/li>\n<li>Vague feedback &#8211; give specific examples.<\/li>\n<li>Public correction &#8211; always critique privately.<\/li>\n<li>Overpromising &#8211; don&#8217;t commit to fixes you can&#8217;t enforce.<\/li>\n<li>Ignoring follow-up &#8211; document and calendar actions.<\/li>\n<li>Skipping documentation &#8211; agreements vanish without a record.<\/li>\n<\/ul>\n<p><strong>Quick recovery scripts:<\/strong><\/p>\n<ul>\n<li><strong>If you lose your cool:<\/strong> &#8220;I&#8217;m getting emotional &#8211; I need a five-minute break and then I want to continue.&#8221;<\/li>\n<li><strong>If they shut down:<\/strong> &#8220;I notice this feels heavy &#8211; would you prefer to pause and pick this up tomorrow?&#8221;<\/li>\n<li><strong>If they become defensive:<\/strong> &#8220;I want this to be productive; let&#8217;s slow down or involve someone neutral.&#8221;<\/li>\n<\/ul>\n<p><strong>When repeated conversations aren&#8217;t working:<\/strong> Signs include no change after documented plans, repeated policy breaches, or safety concerns. At that point involve HR, a mediator, or consider role changes &#8211; the problem may be structural, not conversational.<\/p>\n<h2>Aftercare: immediate follow-up, measuring progress, and your one-page checklist<\/h2>\n<p>Most talks die after the meeting. Follow-up is where the change actually happens: recap, schedule check-ins, measure progress, and reflect.<\/p>\n<p><strong>Immediate actions (within 24 hours):<\/strong> Send a brief recap with agreed actions, create calendar invites for check-ins, and thank the other person. Put the action list in a shared doc or calendar entry so it&#8217;s visible and actionable.<\/p>\n<p><strong>Measuring progress:<\/strong> Track simple metrics like behavior frequency, deadlines met, and stakeholder feedback. Choose a weekly or biweekly cadence depending on urgency.<\/p>\n<p><strong>Self-care and reflection:<\/strong> Debrief privately: what went well, one change for next time, and one concrete learning. Convert feelings into actions, not rumination.<\/p>\n<h3>One-page checklist + ready templates<\/h3>\n<p><strong>Before (5 items)<\/strong><\/p>\n<ul>\n<li>Clarify goal (understand, fix, escalate)<\/li>\n<li>Pick 2-3 facts\/evidence<\/li>\n<li>Do the empathy exercise (3 perspective questions)<\/li>\n<li>Choose private location and time<\/li>\n<li>Send a short invite or agenda if needed<\/li>\n<\/ul>\n<p><strong>During (6 items)<\/strong><\/p>\n<ul>\n<li>Open neutrally and state outcome<\/li>\n<li>Ask discovery questions<\/li>\n<li>Listen and reflect<\/li>\n<li>State impact using facts<\/li>\n<li>Co-create a plan with owners and dates<\/li>\n<li>Confirm next steps and check-in<\/li>\n<\/ul>\n<p><strong>After (6 items)<\/strong><\/p>\n<ul>\n<li>Send recap within 24 hours<\/li>\n<li>Create check-in calendar invites<\/li>\n<li>Document outcome in a shared place<\/li>\n<li>Track agreed metrics<\/li>\n<li>Escalate if no progress<\/li>\n<li>Do a quick personal debrief<\/li>\n<\/ul>\n<p><strong>Meeting opener (copy-paste)<\/strong><\/p>\n<p>&#8220;Thanks for meeting. I want to talk about [topic] so we can [outcome]. My goal is to understand your view and agree one next step.&#8221;<\/p>\n<p><strong>Recap email (copy-paste)<\/strong><\/p>\n<p>Subject: Quick recap &#8211; [topic]<\/p>\n<p>Hi [Name],<\/p>\n<p>Thanks for the conversation today. Quick recap of what we agreed:<\/p>\n<ul>\n<li>Issue: [one-sentence fact]<\/li>\n<li>Action: [who] will [what] by [date]<\/li>\n<li>Success metric: [how we&#8217;ll know it worked]<\/li>\n<li>Check-in: [date\/time]<\/li>\n<\/ul>\n<p>Thanks &#8211; [Your name]<\/p>\n<blockquote><p>&#8220;The goal of a difficult conversation is not to win &#8211; it&#8217;s to get to clarity and keep the relationship intact.&#8221; &#8211; Practical <a href=\"\/course\/leadership\">Leadership<\/a><\/p><\/blockquote>\n<h2>FAQ<\/h2>\n<h3>How do I bring up a difficult topic without sounding accusatory?<\/h3>\n<p>Start with observable facts, state the impact with &#8220;I&#8221; language, then invite their view. Timebox the topic and avoid absolutes like &#8220;always&#8221; or &#8220;never.&#8221; That sequence lowers defensiveness and focuses the talk on solutions.<\/p>\n<h3>How do I prepare feedback for my boss?<\/h3>\n<p>Clarify your goal (align vs. request change), gather 1-2 examples, rehearse the empathy questions, and ask permission to share feedback. Lead with impact and a proposed solution, and offer a short follow-up plan so the request is actionable and respectful.<\/p>\n<h3>What if they deny the facts or push back?<\/h3>\n<p>Stay calm, restate the specific examples, ask for their version, and look for objective evidence. Propose a time-limited trial or checkpoints and document the steps. If denial persists and causes harm, escalate after repeated documented attempts.<\/p>\n<h3>Can hard conversations be done over email or chat?<\/h3>\n<p>Not for high-emotion or sensitive issues. Use email only for recaps or low-stakes clarifications. For most difficult conversations choose a private call or in-person meeting and follow up with a concise recap so tone and nuance aren&#8217;t lost.<\/p>\n  <section class=\"landfirst landfirst--yellow\">\r\n<div class=\"landfirst-wrapper limiter\">\r\n<img decoding=\"async\" src=\"https:\/\/brainapps.io\/blog\/wp-content\/themes\/reboot_child\/bu2.svg\" alt=\"Business\" class=\"landfirst__illstr\">\r\n<div class=\"landfirst__title\">Try BrainApps <br> for free<\/div>\r\n<div class=\"landfirst__subtitle\">\r\n\r\n\r\n<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"24\" viewBox=\"0 0 24 24\"><path d=\"M20.285 2l-11.285 11.567-5.286-5.011-3.714 3.716 9 8.728 15-15.285z\"\/><\/svg> 59 courses\r\n<br>\r\n<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"24\" viewBox=\"0 0 24 24\"><path d=\"M20.285 2l-11.285 11.567-5.286-5.011-3.714 3.716 9 8.728 15-15.285z\"\/><\/svg> 100+ brain training games\r\n <br>\r\n<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"24\" viewBox=\"0 0 24 24\"><path d=\"M20.285 2l-11.285 11.567-5.286-5.011-3.714 3.716 9 8.728 15-15.285z\"\/><\/svg> No ads\r\n\r\n <\/div>\r\n<a href=\"\/signup?from=blog\" class=\"customBtn customBtn--large customBtn--green customBtn--drop-shadow landfirst__btn\">Get started<\/a>\r\n<\/div>\r\n<\/section>  ","protected":false},"excerpt":{"rendered":"<p>Intro &#8211; a short story and a bold promise Sam let a five-minute feedback conversation slide. A missed deadline turned into a sprint, then a fight between two teams, then a delayed product launch. All because a small issue went unspoken. If that sounds familiar, this guide shows how to have difficult conversations at work [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1643],"tags":[],"yst_prominent_words":[],"class_list":["post-5652","post","type-post","status-publish","format-standard","","category-leadership-and-management"],"acf":[],"_links":{"self":[{"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/posts\/5652","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/comments?post=5652"}],"version-history":[{"count":0,"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/posts\/5652\/revisions"}],"wp:attachment":[{"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/media?parent=5652"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/categories?post=5652"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/tags?post=5652"},{"taxonomy":"yst_prominent_words","embeddable":true,"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/yst_prominent_words?post=5652"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}