Formats
Product in development

Weekly team check-in in three lines

One blip a week for teams that do not need a daily rhythm: shipped, focus, need.

Once a week, on the day your team picks

The three lines

  1. Shipped

    What is the main thing you shipped this week?

  2. Focus

    What is your one focus for next week?

  3. Need

    What do you need from someone else? Leave empty if nothing.

Each line: 80 characters at most.

Copy the template

Shipped: 
Focus: 
Need: 

Plain text. Paste it into any chat tool or document and use it today.

An example weekly check-in blip

  • Shipped New onboarding emails are live for all signups
  • Focus Rewrite the pricing page copy
  • Need Need a decision on the annual discount by Wednesday

A written sample, not a real team's update.

Questions

What is a weekly team check-in?

A short written update each person shares once a week so the team knows what moved, what comes next and who needs help, without holding a status meeting.

How long should a weekly check-in be?

Short enough that everyone reads all of them. A blip is three lines of at most 80 characters, so a team of eight is 24 lines in total.

Is a weekly check-in better than a daily standup?

It depends on how fast the work changes. Teams with long tasks and few handoffs often do fine with one blip a week. Teams that block each other daily need the daily one.

Write one in the demo

tblip is in development. The template above works without it.