Individual Team Member · execution thread

Mid-market services company · Request to delivered service

You turn accepted requests into delivery plans the client can rely on. You want to know what good looks like, which steps are yours, and who decides when a plan does not fit.

Context: Same company and process as the Functional Executive example, seen from the seat of the person doing the work.

Fictional simulation · illustrative scenario

This thread follows the Individual Team Member path.

Strategic intent

Every client request delivered on the agreed date, across four functions

Owner: Accountable executive

Goals and measures

Goal	Owner	Measure	Target
Every handoff with a named owner by 30 Mar	Accountable executive · peer executives	Handoffs with a named owner	All handoffs
Your goal: every plan you own confirmed to the client in writing within one working day of credit approval	Delivery Planner (you)	Plans confirmed in writing within one working day	95%

Program and projects

Plan-confirmed handoff redesign · Process owner · project team

Plan confirmation to the client in every request · Process owner · due 30 Jan

Swim-lane process and RASCI · Plan-confirmed handoff · your steps

Accepted request → your draft plan → credit decision → your RASCI check → your confirmation

#	Activity	Swim lane	R	A	C / I	Work instruction
1	Accept complete request	Sales operations	Sales Coordinator	Process owner	I: Delivery Planner (you)	—
2	Draft delivery plan	Operations	Delivery Planner (you)	Process owner	C: Operations scheduler	WI-625
3	One approval within limit	Finance	Finance Analyst	Chief Financial Officer	I: Delivery Planner (you)	—
4	Within the RASCI? (decision)	Operations	Delivery Planner (you)	Process owner	—	WI-628
5	Confirm plan to client	Operations	Delivery Planner (you)	Process owner	I: Sales operations	WI-630

Role / job

Delivery Planner (delivery specialist) · Turns an accepted request into a confirmed delivery plan and keeps the agreed date.

People playbook: PPL-32 Delivery specialist

Procedure

PRO-15 · Plan-confirmed handoff — Move each client request from sale to a confirmed delivery plan with one owner at every handoff.

Numbered work instructions

WI-625 · Delivery plan draft · Delivery Planner · v1.0 · Approved
WI-628 · RASCI check before confirming · Delivery Planner · v1.0 · Approved
WI-630 · Plan confirmation · Delivery Planner · v1.0 · Approved

Evidence

Draft delivery plans · from WI-625 · feeds “Your goal: plans confirmed in writing within one working day”
Delivery commitment records · from WI-630 · feeds “Every handoff with a named owner”

ARC™ feedback

Weekly team huddle · 02 Oct

Analyze: Two plans went out without written client confirmation, and one date was changed outside the planner’s rights.
Refine: WI-628 adds the RASCI check before confirmation; WI-630 step 2 uses the confirmation template.
Commit: Each Delivery Planner uses both from 05 Oct; the process owner reviews them in the next huddle.

Back to Your path, step by step See this scenario in CompassOS

Fictional simulation · illustrative scenario