Julia Moser·
One prompt, three audiences. The same project data becomes an exec summary, a team update, and a client note — Friday reporting went from ninety minutes to fifteen.
Transforms raw weekly project data into three purpose-built updates — executive, team, and client — each with its own altitude, risk framing, and call to action.
Tri-Audience Status Update
You are a senior project manager writing the weekly status update three times — once per audience. Same underlying facts, radically different altitude. Never copy sentences between versions.
Raw project data for this week (tickets closed, milestones, blockers, decisions made, budget/hours, upcoming dates):
{{project_data}}
Audience notes: {{audience_context}}
Write three versions:
**1. Executive summary (max 100 words).** Lead with trajectory: on track / at risk / off track, and whether that changed since last week. Only include details that require an executive decision or protect them from surprise. Money and dates outrank activity. If there is a decision needed, state it as a direct question with a deadline and a default ("unless we hear otherwise by Thursday, we will...").
**2. Team update (max 250 words).** Specific and operational: what shipped, what is blocked on whom, decisions made this week WITH their rationale (teams resent decisions without reasons), and next week's priorities per workstream. Credit people by name for concrete wins. Blockers name the blocking party neutrally and state what unblocking looks like.
**3. Client note (max 150 words).** Confident but honest: progress in terms of THEIR outcomes, not our tickets. Translate internal jargon into client value. If there is a delay, state it plainly with the mitigation already in motion — never let a client learn a date slipped from the invoice. End with what we need from them, if anything, as a single clear ask.
Rules across all three: no filler ('great progress this week!'), no hedging without information ('might possibly'), risks stated with their probability and impact in plain words. If the raw data hides a risk I have not flagged, surface it in a note to me AFTER the three updates — do not put it in the client version without my sign-off.
Ergebnisse
**1. Executive summary**
Webshop relaunch: **at risk** (was: on track). Payment provider certification moved their audit slot by two weeks — go-live 15 Sept holds only if we start checkout integration against their sandbox this week. Budget: 62% consumed at 58% scope; within tolerance. **Decision needed:** approve CHF 8k for the provider's expedited certification track — unless we hear otherwise by Thursday, we proceed with the standard track and accept a 7-day buffer loss.
**2. Team update**
Shipped: product catalog migration complete — all 4,300 SKUs validated (Dario caught the variant-mapping bug that would have duplicated bundles). Search relevance tuning is live on staging.
Blocked: checkout integration waits on sandbox credentials from PayFlow — requested Monday, chased Wednesday. Unblocked means: credentials in the shared vault. Sandra owns the escalation call Friday 10:00.
Decisions this week: we cut the wishlist feature from launch scope. Rationale: it depends on the account system that slipped to phase 2, and a stub version would create support tickets without value. It returns in October's release.
Next week: Frontend — checkout UI against mock API (Priya's mock is ready). Backend — inventory sync load test, target 500 req/s. Content — legal pages final review with Rechtsdienst.
**3. Client note**
Your product catalog is fully migrated and verified — all 4,300 articles, including the bundle variants that needed special handling. Search on the test environment now returns noticeably better results for your top 50 queries; you can try it with the link below.
One date to flag: our payment provider moved their certification audit, which puts pressure on the 15 September go-live. We have already requested their expedited track and will confirm the timeline by Friday. The launch date remains our commitment.
**Needed from you:** final sign-off on the returns policy text by Wednesday, so legal pages can go into review.
---
**Note to you (not for client):** hours burn on the search tuning workstream doubled week-over-week while its ticket count stayed flat — that pattern usually means hidden rework. Worth a quiet check before it shows up in the budget line two weeks from now.
Modell: GPT-4o
18 Likes12 SavesScore: 13
1 Kommentar
Grace Williams·
The private risk note at the end is the feature. A report that quietly tells YOU things before telling stakeholders is how reporting should work.