Create a process map from the activities, inputs and outputs behind your work. Describe the scope and owners, then review the handoffs before sharing it.
Set the start and end conditions
“Customer onboarding” could mean everything from a sales conversation to the first renewal. Define the boundary explicitly. In this example, the signed contract starts the process and the customer’s first successful use completes it. Account setup and training are activities inside that boundary.
List the required input for each activity and the output that allows the next activity to begin. A setup task might need approved account details and produce an active workspace.
Use outputs to expose missing work
Read the map as a chain of deliverables. If training needs a configured workspace but no activity creates one, the gap is visible. If a handoff has no receiving owner, add one. Keep measures such as waiting time separate from processing time when discussing improvement.
Use a flowchart for detailed branching and a swimlane diagram to emphasize responsibility across teams.
Compare the current and proposed process
Describe the current process first, including known rework. Save that version before proposing changes. Ask for a second view that combines redundant handoffs or changes an activity’s owner, then review the outputs that still need to exist.
The map is a discussion artifact. It does not measure actual lead times, automate tasks or prove that a proposed change will improve performance.
Make it about your work
Edit this starting prompt, then send it when you are ready.