Warner Music Group / Delivered workflow
Move a request from intake to closure
The problem
Each request needed repeated setup, and progress was spread across disconnected handoffs.
My contribution
I built a Microsoft 365 workflow connecting the request, records, tasks, updates, and closure.
Request setup fell from roughly two hours to five minutes. People could see ownership and status.
02 / See the thinking in practice.
Explore an example.
Try the workflow
One request. See what happens.
Fictional sample of the workflow I built. Edit the form or explore a stage. Nothing is sent or saved.
The right questions, up front.
Choose a change type. The form asks for the context that matters.
The setup takes care of itself.
One submission creates three connected pieces of work.
-
Planner task
The request is ready for an owner to pick up.
DEMO-001 · Clarify the project handover guide -
Microsoft Lists record
The requestor can follow the status in one place.
DEMO-001 · Received -
Shared request folder
Attachments and related emails stay with the request.
Team inbox / DEMO-001
Update the work. Everyone stays in sync.
Planner progress updates the tracker and keeps the requestor informed.
Sample Planner task
Clarify the project handover guide
Requestor’s tracker
DEMO-001In progress
Sample update: Alex Morgan’s request is now in progress.
Complete the task. Keep the record.
Completing the Planner task triggers closure and moves the folder out of the active inbox.
Planner task
Clarify the project handover guide
CompleteArchived together
Request + supporting records
Archive / DEMO-001
Close the loop with the people affected.
The workflow generates a Service Request Bulletin. After a person reviews it for accuracy and approves it, publication and notifications to the requestor and impacted group happen automatically.
Sample Service Request Bulletin
Clarify the project handover guide
- Reference
- DEMO-SRB-001 / DEMO-001
- Affected work
- Operations / project handover
- Change summary
- Add a clear handover checklist and identify who accepts the completed work.
- Audience
- Alex Morgan + the impacted group
Illustrative bulletin fields. Approval roles, effective dates, and contacts were also part of the original bulletin.
03 / Bring it back to the role.
What this demonstrates.
I turn a business need into a connected workflow, with clear ownership from submission to closure.
Project scope and example context
Reconstruction of my delivered workflow, using fictional names and values. It is not connected to Microsoft 365.