Updated September 2026: in 2019 I was left alone with a demanding delivery contact, with no offshore support, and small requests grew into daily changes to every slide and the structure itself. I have rewritten it into advice on handling daily iterative changes when you are working alone.
The offshore delivery lead had made it clear there would be no support from his side. The first requests were to add a few slides. Soon every slide was being changed, and then the structure. Using my repository and experience, I finished each day's changes by evening, hoping that would be the last round. The next morning brought more.
Why do iterations never seem to end?
Because each reviewer sees new possibilities once they read a draft, and nothing stops them from asking. Without an agreed number of review rounds or a content freeze, iterations continue until the deadline forces a stop.
How do you bring iterations under control?
- Batch changes: collect requests during the day and apply them once, in the evening.
- Confirm the structure first: agree the storyline before polishing individual slides.
- Set a freeze date after which only corrections are accepted.
- Log every change with the requester and date.
What if you have no support?
Make the workload visible. Share the change log with your manager after a few days: how many changes, how many hours. Ask for either help or a limit on rounds. Working alone is sometimes unavoidable, but it should be a known decision, not an accident.
How do you keep quality up under constant change?
Keep versions. Save each day's deck with a date, so you can go back when a change is reversed, which it often is. Use a template so formatting stays consistent however much content changes.
Should you push back on structural changes late on?
Yes, politely. Structural changes near the end create the most work and the most risk of errors. Ask whether the change is needed for the client or just a preference, and point out what it will delay.
What does finishing each day's changes achieve?
It builds a reputation for reliability. But it can also teach the requester that there is no cost to asking. Pair responsiveness with a visible log, so the effort is recognised.