Introduction: why this action matters for adoption
Desk-drop documents are a small intervention with a practical purpose: they put the right change information directly in front of the people who need to act on it. Used well, they reduce friction, make the change visible in the flow of work, and give managers and employees a shared reference point for “what is changing, what it means for me, and what I do next.” Change management research consistently emphasizes structured, repeated, targeted communication rather than one-off announcements [Prosci, 2024]. (prosci.com)
This action matters because adoption depends on individual understanding, confidence, and follow-through, not simply project delivery. CIPD frames change management as the work of helping organizations manage, enable, support, and embed change effectively [CIPD, 2025]. (cipd.org) A desk-drop is therefore not “collateral”; it is a change communication and engagement tool that supports readiness, manager conversations, training, reinforcement, and behavior change.
What this action is and when to use it
A desk-drop document is a concise physical or digital material placed directly where impacted people will see it: on a desk, in a locker, beside equipment, in a team huddle pack, in an email attachment, on an intranet tile, or in a collaboration channel. It is most useful when people need a quick reference, a reminder before a behavior change, or a bridge to more detailed support.
Use it during awareness-building to explain the “why,” during readiness activities to summarize “what this means for your role,” at go-live to reinforce the “what to do now,” and after launch to remind people of new behaviors. It should not be used as the only communication for complex, sensitive, or high-resistance changes. Prosci’s guidance is clear that change communication should be planned, sequenced, targeted, and aligned with the broader change management plan [Prosci, 2024]. (prosci.com)
Preparation: inputs, stakeholders, materials, timing, and decisions needed
Start with the change impact assessment. The desk-drop should reflect the actual impact on the audience, not generic project language. For employees, emphasize personal impact, timing, required actions, support, and where to ask questions. For sponsors, emphasize business rationale and visible talking points. For managers, include conversation prompts and escalation routes. Prosci’s research distinguishes organizational messages, often best sent by senior leaders, from personal-impact messages, where people managers are preferred senders [Prosci, 2023; Prosci, 2024]. (prosci.com)
The core inputs are the approved key messages, audience list, timing plan, distribution channel, owner, print or digital requirements, accessibility requirements, and feedback route. The CDC Clear Communication Index recommends a clear main message, a call to action, visual cues, and limiting information so the audience is not overwhelmed [CDC, 2019]. (cdc.gov) For digital materials, apply accessibility basics: meaningful reading order, adequate contrast, labels or instructions where input is needed, and accessible text rather than image-only text [W3C, 2024]. (w3.org)
Step-by-step facilitation guide
Confirm the adoption objective. Define the behavior the desk-drop should support: attend training, use a new process, stop an old workaround, complete a readiness task, or ask a manager for help. PMI recommends measuring not only communication reach but also comprehension and behavior change [PMI, 2015]. (pmi.org)
Segment the audience. Create different versions only where the impact differs. A call center agent, regional manager, sponsor, and HR partner may need the same headline but different actions.
Draft for action. Put the main message first, then the role impact, action required, date, support link, and contact route. Use plain language, short sections, and visual emphasis.
Validate with stakeholders. Ask the sponsor to confirm the business message, the project team to confirm accuracy, HR or legal to review sensitive implications, communications to check tone and brand, and a manager or employee representative to test clarity.
Equip managers before distribution. Send managers a preview, a short script, likely questions, and escalation guidance. Gallup’s engagement research and Prosci’s change research both reinforce that managers strongly shape the local employee experience [Gallup, 2015; Prosci, 2023]. (news.gallup.com)
Distribute at the right moment. Time the desk-drop close enough to the required action that it is useful, but not so late that employees feel surprised. For high resistance, pair it with a team discussion or office hours.
Close the loop. Monitor questions, QR-code visits, attendance, manager feedback, and adoption behavior. Revise the material if people misunderstand the action.
Example: how this could be applied in a real change initiative
A finance team is moving from spreadsheet-based expense approvals to a new workflow tool. Two weeks before go-live, the change manager prepares a one-page desk-drop for approvers. The headline says, “Starting July 15, approve expenses in FlowPay, not email.” The page shows three actions: complete a 20-minute simulation, approve only in the new queue after go-live, and contact the finance change champion for help. A QR code links to the job aid and training calendar.
Managers receive the document one day earlier with a five-minute huddle script. At go-live, the same message appears as a digital desk-drop in the team channel. After launch, the change manager compares training completion, first-week approval cycle time, help-desk tickets, and manager feedback.
Roles and responsibilities
Role | Responsibility |
Change manager | Owns audience targeting, message intent, distribution plan, manager enablement, and measurement. |
Sponsor | Approves business rationale and reinforces why the change matters. |
People manager | Explains personal impact, hosts discussion, answers first-line questions, and escalates concerns. |
Communications partner | Improves clarity, tone, brand, channel fit, and sequencing. |
Project or product lead | Confirms technical accuracy, dates, support links, and process details. |
Adoption lead or champion | Tests usability, supports peer questions, and reports field feedback. |
Common mistakes to avoid
Avoid treating the desk-drop as an announcement rather than an adoption aid. Do not overload it with project history, jargon, or every possible scenario. Avoid distributing it before managers are briefed, because employees often ask their immediate manager what the change means for them. Do not use the same version for audiences with different impacts. Finally, do not measure success by “sent” or “printed” alone; measure whether people understood and acted.
Measures of success or adoption indicators
Measure type | Example indicators |
Reach | Number distributed, email open rate, QR scans, intranet visits. |
Understanding | Pulse question results, manager-reported questions, short knowledge checks. |
Engagement | Attendance at huddles or office hours, comments submitted, champion feedback. |
Adoption behavior | Training completion, process usage, reduction in old-workaround activity, system log data. |
Reinforcement | Fewer repeat questions, improved compliance, manager confidence, reduced support tickets. |
PMI recommends measuring communication readership and engagement during execution, then post-deployment adoption and behavior indicators after launch [PMI, 2015]. (pmi.org)
Checklist for the change manager
Adoption objective is defined.
Audience and role impacts are confirmed.
Sponsor and manager messages are aligned.
Document has one main message and one clear call to action.
Material is concise, visual, accessible, and linked to more detail.
Managers receive a preview, script, FAQ, and escalation route.
Distribution timing matches the project phase and employee action needed.
Feedback and adoption measures are in place.
Optional reusable message outline
Headline: What is changing and when?
Why it matters: One sentence on the business or employee reason.
What this means for you: Role-specific impact.
What you need to do: One to three actions.
Where to get help: Manager, champion, support channel, QR code, or link.
What happens next: Next milestone, reminder, training, or go-live date.
References
Prosci. “Best Practices in Change Management.” Published May 26, 2023; updated Oct. 30, 2025. https://www.prosci.com/blog/change-management-best-practices
Prosci. “5 Steps to Better Change Management Communication + Template.” Published Mar. 31, 2024; updated May 21, 2026. https://www.prosci.com/blog/change-management-communication
CIPD. “Change management.” Factsheet. June 17, 2025. https://www.cipd.org/en/knowledge/factsheets/change-management-factsheet/
Ferraro, Jack P. “Measure twice, change once: practical strategies for change management.” Project Management Institute. Oct. 10, 2015. https://www.pmi.org/learning/library/practical-strategies-for-change-management-9887
Centers for Disease Control and Prevention. “CDC Clear Communication Index: A Tool for Developing and Assessing CDC Public Communication Products — User Guide.” August 2019. https://www.cdc.gov/ccindex/pdf/clear-communication-user-guide.pdf
World Wide Web Consortium. “Web Content Accessibility Guidelines (WCAG) 2.2.” W3C Recommendation. Dec. 12, 2024. https://www.w3.org/TR/WCAG22/
Gallup. “Managers Account for 70% of Variance in Employee Engagement.” Apr. 21, 2015. https://news.gallup.com/businessjournal/182792/managers-account-variance-employee-engagement.aspx
