Fictional example

Launch request process map

Follow one fictional product-launch request from intake to a ready-to-schedule handoff. Each card names the owner, the input, the output, and the condition that lets work move.

StartRequest received
FinishLaunch packet ready
ExceptionRights evidence missing
Input → action → outputGreen = handoff conditionRed = stop and return
1

Capture the request

Owner: Campaign coordinator
InputLaunch request and requester contact
OutputRequest card LR-024
Move when: audience, channel, owner, and target date are named.
2

Check the source pack

Owner: Content lead
InputRequest card and source files
OutputComplete source pack or return note
Move when: approved copy, product image, and rights evidence are attached.
Stop path: If rights evidence is missing, return LR-024 to the campaign coordinator. Resume here after the record is attached.
3

Build the launch draft

Owner: Designer
InputComplete source pack
OutputDraft page and asset list
Move when: every asset in the draft appears in the source pack.
4

Review against the brief

Owner: Product reviewer
InputDraft page, asset list, and request card
OutputAccepted draft or named corrections
Move when: the reviewer records acceptance and unresolved corrections are zero.
5

Prepare the schedule packet

Owner: Channel manager
InputAccepted draft and target date
OutputSchedule packet with destination and owner
Finish when: the channel manager acknowledges the packet. This example does not publish or schedule anything.

Handoff result

The normal route ends with one acknowledged schedule packet.

The exception route keeps LR-024 at source review until rights evidence is present.