Solutions Handovers
Team handover
Work moving between teams with its context attached, so nothing is re-explained.
01 / What it looks like running
Start to finish, and where a person still comes in.
- 01 / TriggerOne team marks it done
- 02 / AutomatedContext packaged
- 03 / AutomatedFiles and history attached
- 04 / AutomatedNext team notified
- 05 / Needs a personThe work itself
Automated Needs a person 3 of 5 run without anyone
02 / What stops happening
6 steps become 1.
The struck lines are the ones nobody performs after this is live.
- One team finishes and messages the next
- The next team asks where the files are
- Someone digs out the history
- Someone re-explains the background
- Work restarts, a day later than it needed to
- The actual work, done by the people who do it
03 / Built on
In your tenant, under your licences.
- Power Automate
- Microsoft 365
- SharePoint
Yours may differ. What a process runs on is decided by what it touches, not by what we prefer building with.
Does yours run like this?
It probably runs nearly like this, with two steps that are entirely your own. Those two are the interesting part.