Updated September 2026: in January 2020 I joined a call expecting to pull existing slides from the repository, but the delivery lead started briefing new work and asked me to set up recurring calls. My manager still thought only reusable slides were needed until I pointed out it was a new request. I have rewritten it into advice on clarifying whether a request is reuse or new work.
My manager and I joined the call to help the delivery lead find slides from the repository. Instead, he began explaining a new piece of work and asked me to schedule recurring calls with onsite for the coming weeks. I waited for the call to end to discuss it with my manager, who still believed the task was sharing reusable slides. When I stressed that this was new work, he understood.
Why does reuse become new work?
Because "just share the existing slides" is often how new work is first described. The requester thinks old material will cover it; once they explain the need, it clearly will not. Without a pause to clarify, the assignment grows unnoticed.
How do you clarify on the call?
Ask one question: "Is this a new request we should plan for, or are we sharing existing material?" It is polite, and it forces the scope into the open. Note the answer.
What should you tell your manager?
- That the request is new work, not reuse.
- The expected effort and duration, including the recurring calls.
- What else you are working on, so they can decide priority.
Should you set up recurring calls immediately?
Only once your allocation is confirmed. Scheduling calls commits you to the work in everyone's eyes. A short "I will confirm with my manager and send the invites today" is enough.
How can reuse requests be handled faster?
A well-organised repository lets requesters find material themselves. Point them to it with a link, and reserve your time for tailoring.
What did this teach me?
That managers often agree to requests based on a one-line description. Speaking up early, as I did after the call, lets them decide with the real picture.