Measuring drift without a meeting

A status meeting is an expensive way to learn something your tools already know. Eight people, one hour, every week, and most of it goes on reading tickets aloud.

What drift actually measures

Drift compares the work that should be done by today with the work that is, then weighs each gap by what it blocks. A late task with nothing behind it barely counts. A late task that holds up three teams counts for a lot.

The result is one number that anyone can read. It does not ask how people feel about the plan. It only reports what the plan and the work say when you put them side by side.

Getting a first reading

You need three things: a plan with dates, issues that close when work is done, and a list of what depends on what. Most teams already have the first two. The third takes an afternoon, and it does not need to be perfect to be useful.

Run it for two weeks before you change anything. You want to learn what a normal week looks like for your team, so that a real change stands out.

What happens to the meeting

When that number moves, people ask better questions. Not what is the status, but why did this jump on Thursday, and who needs help because of it.

Most of the meeting goes away. What stays is shorter, and it is about decisions instead of updates.