Today's goals
C1Frame the update around impact, not activity.
C1Surface risk early and precisely.
C1Close with a one-line decision needed.
The task · rewrite it
Before“Hi team, I’ve been working on the claims API integration this week. There were some issues with the test environment and I had to coordinate with the data team. I think it’s mostly going okay but a few things are still pending. Will keep you posted.”
C1Rewrite it impact-first. Lead with status, surface the risk precisely, and add one crisp “decision needed” line. Keep it under four sentences.
Stretch: make the “ask” specific enough that your US lead can reply in one word.
Model · C1
Claims API integration is on track for Friday. One risk: the test environment was down Tue–Wed (now resolved), which compressed UAT. Decision needed: confirm we can use the staging dataset for UAT, or I’ll need one additional day. Happy to jump on a call if easier.Practise speaking
Record a 30-second standup update: what you did, what’s blocking you, and what you need. Then listen back.
Tap to record · stays on your phone
Language to use · tap what you'll use
Flagging a blocker
One blocker:…I’m blocked on… until…This is at risk because…
Giving an ETA
On track for [day].Now expecting [day] because…Slipping to [day] — here’s why:
Making the ask
Decision needed:…Could you confirm… by [time]?I need [X] to stay on schedule.
✓
Session complete — nice work.
Can you do it?
I can lead with impact, not a list of activities.
I can state a risk in one precise sentence.
I can write an ask that gets a one-word reply.
Before next time
Take a real thread from this week and rewrite your update impact-first, with a single decision-needed line. Bring it next session.