Asked after the slides were printed
The reorg was announced Monday. The listening sessions started Tuesday. Every concern raised had already been decided against.
InsteadAffected people answer the draft before anyone decides.
The video
Video planned60 secondsHow every video is made
The script
- The one point
- The people a change affects answer the draft before the sponsor decides, and the decision record keeps each objection with its answer.
- Why a video
- The same moment shown twice: one reorg in two orders, decide then ask versus draft, answer, decide, side by side, with time passing between announcement and listening, and the sponsor deciding live.
- Picture
- Brand mark and sound, then the heading ‘Asked after the slides were printed’ on the site’s background, fading straight into the guide with no black.
- On screen
- Asked after the slides were printed
- Picture
- Guide in the standard room and place. Lower third: guide’s first name, ‘Soundly Run guide’. Burned-in captions.
- Voice
- The reorg was announced Monday. The listening sessions started Tuesday. In a company this size, the sponsor sits furthest from the work, so asking comes last.
- On screen
- Announced Monday. Listening started Tuesday.
- Picture
- A timeline: ‘Decided’ stamp, then ‘Announced’, then ‘Asked’. Concern notes arrive after the stamp and bounce off it. A loop arrow draws back: a second announcement, a second round of meetings. No numbers.
- Voice
- Every concern lands on a decision already made, and comes back later as a second announcement and more meetings.
- On screen
- Every concern raised had already been decided against.
- Picture
- Drawn Needs you screen, Example tag top left, context ‘Company crew’, cursor visible. Step band on prepare: callout 1 on Drafted by, ‘Priya, support process owner’. Step band on review: callout 2 on Answered by, ‘31 of 38 affected people’; callout 3 on Objections, ‘12, each with a written answer’. Cursor then moves to Changed by answers and Still open.
- Voice
- Priya, nearest the work, approved the draft. Then the people it changes answered: 31 of 38, twelve objections, each answered in writing and kept with the decision. Night shift keeps its own queue. Weekend cover is still open.
- On screen
- Example · Decide on merging the support queues
- Picture
- Step band on decide. ‘Approve the change’, ‘Change’ and ‘Pass’ visible. Click on approve held two seconds. Heading becomes ‘Decided’; row reads ‘Sam, COO and sponsor, 18 Mar · approved’. Guide in picture-in-picture.
- Voice
- Sam, the sponsor, decides with every objection and its answer attached: approve the change, change it, or pass.
- On screen
- Decided. Every objection and its answer attached.
- Picture
- Guide in the same framing as The moment, inset of two timelines side by side: ‘Decide, announce, ask’ above ‘Draft, answer, decide’.
- Voice
- Nobody holds listening sessions after the announcement any more. The helper drafts and groups the answers; the sponsor decides. It does not watch, score or replace anyone.
- On screen
- Affected people answer the draft before anyone decides.
- Picture
- Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
- On screen
- Asked after the slides were printed
On screen as proof
- Example Needs you screen: ‘31 of 38 affected people’ answered, ‘12, each with a written answer’
- ‘Changed by answers: Night shift keeps its own queue’
- ‘Approve the change’ click held two seconds, Change and Pass visible
Before and after
- Before
- Early consultation feels risky, so the sponsor signs off, then asks
- After
- Affected teams answer the draft before sponsor sign-off
- Before
- Impact assessed by people furthest from the work
- After
- The role nearest the work drafts the impact first
- Before
- Objections logged in a survey nobody closes
- After
- Every objection gets a written answer before deciding
How it works
The draft goes to the people it changes first, and the decision record keeps each objection with its answer.
- The impact by role is drafted first, with the process owner nearest the work, who approves it before anyone decides.
- Each affected team answers the draft; the change lead writes an answer to every objection, kept with the decision.
- The sponsor decides with every objection and its answer attached, and the decision records what the answers changed, for each person to see.
Needs youExample
Company crew
Decide on merging the support queuesDecided
- Drafted by
- Priya, support process owner
- Answered by
- 31 of 38 affected people
- Objections
- 12, each with a written answer
- Changed by answers
- Night shift keeps its own queue
- Still open
- Weekend cover, answer due Thu
- Decides
- Sam, COO and sponsorSam, COO and sponsor, 18 Mar · approved
Source: change draft, 14 Mar
Approve the changeChangePassApproved. All 38 see the decision and what their answers changed.
Built to work in the email, calendar, chat, finance and sales tools you already use.
What it never does
- Acts alone only inside limits a person sets; asks first for anything else.
- Reaches only what its job needs.
- Never watches, scores or replaces anyone.