Illustrative scenario: an organization introduces one intake process for marketing requests. Employees need to know where to submit work, managers need to reinforce the change, and the service team needs enough information to triage requests.
Objective: increase use of the new intake route and reduce incomplete requests. Dates below are relative to an illustrative launch, not an actual client schedule.
Audience
Need
Tactic
Executive sponsor
Explain the purpose and model the change
Short sponsor announcement.
People managers
Answer questions consistently
Team talking points and escalation guidance.
Requesters
Know what to do differently
Launch email, FAQ, and practical checklist.
Service team
Apply consistent triage
Owner-led office hours and issue log.
01 / SPONSOR ANNOUNCEMENT
One place to request marketing work
We’re introducing a shared intake process so requests arrive with the information our team needs to plan the work.
At launch, use the intake form for new requests. Include your audience, objective, needed date, and approver. Work already underway will stay with its current owner.
Submitting a request begins triage; it does not confirm a delivery date. The team will review scope and priorities with you.
Your managers will share the launch details and where to get help.
02 / MANAGER TALKING POINTS
A five-minute team conversation
Explain why: one entry point makes requirements and ownership easier to see.
Show what changes: new requests go through intake; active work stays with its owner.
Make it concrete: walk through one realistic request together.
Invite questions: ask what could make the new process difficult to use.
Close the loop: send unresolved questions to the rollout owner and share the response.
03 / EMPLOYEE EMAIL
Starting at launch: a simpler route for marketing requests
Subject: New marketing requests: what to include and what happens next
When you have new marketing work to request, start with the shared intake form.
Before submitting, have four things ready: the audience, the outcome you need, the requested date, and the person who will approve the work.
The team will check the brief, clarify missing information, and confirm priorities and timing. Your submission is not a confirmed deadline.
Already working with someone? Keep that conversation with the current owner. If the new process creates a barrier, raise it with your manager so the rollout team can address it.
Production CTA: Open the intake form. Insert the approved internal destination before release.
02 / REQUESTER FAQ
Answer the questions that stall adoption.
What if I do not know the full scope?
Describe the audience, objective, and decision you need help making. Flag what is still uncertain.
What if a request is urgent?
Explain the deadline and its consequence. The team will triage it against existing commitments; urgency does not automatically confirm availability.
What happens to existing work?
It stays with its current owner unless the team explicitly agrees to move it.
What if I cannot use the form?
Ask your manager to raise an access or accessibility issue with the rollout owner and arrange an alternative submission route.
03 / ROLLOUT & LEARNING
Measure behavior after the announcement.
When
Deliverable
Owner / check
Two weeks before
Pilot with a small requester group
Rollout owner checks clarity, access, and missing fields.
One week before
Sponsor message + manager briefing
Sponsor approves purpose; managers receive FAQ.
Launch
Employee email + help session
Service owner confirms destination and support coverage.
Week 1
Issue-log review
Fix recurring process barriers before increasing reminders.
Weeks 2–4
Adoption review
Compare with a defined pre-launch baseline.
Measure
Definition
Interpretation
Route adoption
New requests using intake ÷ all new requests
A low rate calls for channel and barrier review.
Brief completeness
Requests with required information ÷ intake submissions
A low rate suggests unclear fields or guidance.
Time to triage
Median time from submission to first substantive response
A delay may indicate capacity or workflow issues.
Strategy, content, and the details that make delivery work.
Elizabeth Carpenter