Improve Visibility by Rejecting Bogus Status Updates

My paranoia is kicking in and I sense something is wrong.

It’s our weekly status meeting and Mark is leading the effort to stand up an integration test framework for our new authentication service. The next step is to get a test running in CI that blocks the build on failure. He needs to work with Susan, the service owner, to get this in place.

The status doc says “Met with Susan to discuss standing up initial blocking test.”

A status should communicate one of three different states:

  • Progress is moving forward but there are some blockers hindering current or future progress.
  • The team is blocked and not making progress.

As written, Mark’s status fails to fall into any of these three states. Technically meeting with someone represents some progress, but there is no reference to the state of the project.

Status reports are often vague to avoid conflict.

In this case the corrected status is:

“The test work is being deferred in favor of completing the service implementation.”

This is far more illuminating and gives me something to work with. Perhaps this tradeoff is the right call, or I need to chat with Susan’s manager to ensure our priorities are aligned. Regardless, the status update is now delivering value and I have the information I need to support my team.

This post was created with Typeshare

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Travis Newcomb

Thoughts on the personal & leadership challenges faced in rapidly growing organizations. (Apple, Chime, Eventbrite, Cisco, …)