Case 48

Weekly Update for Leadership

Scenario

You lead a finance system upgrade at Rowan Insurance. The leadership team wants a short weekly update and has complained that past updates were long and vague.

Why this framework

Uses PIN: what it's for, the context and source of truth, and a narrow ask. Enough for most everyday work.

Example context

Project tracker, Rowan Insurance finance system upgrade (status at Friday 30 October 2026). Go-live date: 1 March 2027 (unchanged). Workstream 1 Chart of accounts redesign: complete, signed off 23 October. Green. Workstream 2 Data migration: trial load 2 of 3 due 30 October, done 30 October, 6.2% of supplier records failed validation (tolerance 2%). Amber. Workstream 3 Integrations (claims and payroll feeds): claims feed built and tested; payroll feed build due 6 November, now forecast 20 November because the payroll vendor's test environment is unavailable. Red. Workstream 4 Training: plan approved; sessions start 11 January 2027. Green. Budget: £2.4m, spent £1.31m to date, forecast on budget. This week's notes: data team cleaning duplicate supplier records, about 900 duplicates found, cleanup expected by 13 November before trial load 3 on 20 November. Payroll vendor has offered a shared test slot from 9 November. If payroll feed slips past 27 November, user acceptance testing start (4 January) is at risk. Need from leadership: decision by 6 November on whether to pay the vendor's £18,000 fee for a dedicated test environment. Next week: supplier cleanup, payroll vendor meeting 3 November, cutover plan draft.

Prompt

Purpose: Write this week's update on the finance system upgrade for the leadership team, who will read it in two minutes.

Context: Use the attached project tracker and this week's notes. The tracker is the source of truth for dates and status.

Narrow the ask: Four short sections: progress this week, risks and what we are doing about them, decisions or help needed from leadership, and next week's focus. Under 200 words. Say plainly if anything is behind schedule.

Materials (pasted here in place of the attachments):
Project tracker, Rowan Insurance finance system upgrade (status at Friday 30 October 2026). Go-live date: 1 March 2027 (unchanged).
Workstream 1 Chart of accounts redesign: complete, signed off 23 October. Green.
Workstream 2 Data migration: trial load 2 of 3 due 30 October, done 30 October, 6.2% of supplier records failed validation (tolerance 2%). Amber.
Workstream 3 Integrations (claims and payroll feeds): claims feed built and tested; payroll feed build due 6 November, now forecast 20 November because the payroll vendor's test environment is unavailable. Red.
Workstream 4 Training: plan approved; sessions start 11 January 2027. Green.
Budget: £2.4m, spent £1.31m to date, forecast on budget.
This week's notes: data team cleaning duplicate supplier records, about 900 duplicates found, cleanup expected by 13 November before trial load 3 on 20 November. Payroll vendor has offered a shared test slot from 9 November. If payroll feed slips past 27 November, user acceptance testing start (4 January) is at risk. Need from leadership: decision by 6 November on whether to pay the vendor's £18,000 fee for a dedicated test environment. Next week: supplier cleanup, payroll vendor meeting 3 November, cutover plan draft.

Example output from ChatGPT

Finance System Upgrade: Weekly Leadership Update

Rowan Insurance | Week ending 30 October 2026

1. Progress This Week

  • Chart of accounts redesign completed and signed off.
  • Data migration trial load 2 completed on schedule, but 6.2% of supplier records failed validation against a 2% tolerance.
  • Claims integration built and tested.
  • Go-live remains 1 March 2027. Budget forecast remains on track at £2.4m (£1.31m spent).

2. Risks and Mitigations

  • RED: Payroll integration is two weeks behind schedule, now forecast for 20 November. Vendor has offered a shared test slot from 9 November.
  • AMBER, data quality: Approximately 900 duplicate supplier records identified. Cleanup targeted for 13 November.
  • If payroll integration slips beyond 27 November, the 4 January user acceptance testing start is at risk.

3. Leadership Decision Required

  • By 6 November: Approve or decline the vendor's £18,000 dedicated test environment fee to address testing constraints.
  • Decision needed to manage the payroll integration delay and protect downstream milestones.

4. Next Week's Focus

  • Continue supplier record cleanup ahead of trial load 3 on 20 November.
  • Meet payroll vendor on 3 November to confirm testing arrangements.
  • Draft the cutover plan.