Appendix D · An example week
A Week, Role by Role
An example calendar for each of the five roles
What the week looks like on each calendar. Thursday morning has no meetings – each person on the core team reads their own slice of the KPIs, solo. The Collab runs Thursday afternoon, and Friday is open.
Scheduled session. Coding Day runs as long as it needs. Solo and flexible, no meeting. Open.
Definer · Customer-centric
CX
Gets to the bottom of the customer need
12 hours in meetings of a 40-hour week
The open time – Watching live customer activity and "Was this better?", talking with customers, keeping the live queue of concerns current.
Definer · The Translator
Product
Turns the customer need into a business case
12 hours in meetings of a 40-hour week
The open time – Market and competitive reads, the numbers behind the next business case, and keeping stakeholders informed.
Definer · The Experience
UX
Defines the brand, the UI and the workflow
8 hours in meetings of a 40-hour week
The open time – Tending the design system AI project, refining personas, and prototyping what's coming next.
Owns the guardrails
Engineering
Keeps the build sound
9 hours in meetings of a 40-hour week
The open time – Maintaining the guardrails, context files and Pipeline, watching errors and load, and tech debt.
Business-centric · Stakeholders
Reviewers
The Business and Stakeholders who own the outcome – Finance, Support, Sales, Marketing, Legal and anyone else with a stake
6 hours in meetings of a 40-hour week
The open time – Their own work. Live customer activity, the measures and every session are on the Dashboard and in the AI project, any time.