Why Project Data Hygiene Matters
I recently sat in a product wide status meeting. This is a meeting comprised of team leaders across 10 different teams.
Not a small meeting.
The purpose of the meeting is twofold:
- Create visibility across teams
- Unblock teams that are stuck
It’s a new discipline at the company, so the team is still figuring out how to make such a large meeting productive. The meeting is held weekly. Each week improvements to the meeting are made based on feedback from participants.
During the meeting each time has the opportunity to run through the status of each of their projects. It’s a typical conversation centered on Red, Yellow, Green status with a conversation about why and what’s being done to course correct.
Now, here is where things go off the rails.
Leaders hyper-focus on the details of what is being presented.
They ask questions about why something is done, but still has open tickets. Or how a project can be green if less than 25% of the work is complete and there is one week left to go until the launch date.
