from Hacker News

Debugging Unaligned Project Teams

by shbhrsaha on 12/26/21, 10:38 PM with 5 comments

• by NickNameNick on 12/27/21, 10:50 PM

  This page doesn't cover it, but surely projects need to be re-aligned (or even cancelled) just as often as the teams implementing them, if the WHY/WHAT/etc don't make sense.

  And yet, I can't recall ever seeing a project that had been started actually get restructured or cancelled. Only psuedo-completed and abandoned.

• by beckingz on 12/27/21, 10:28 PM

  The framework proposed is to make sure that everyone on a project understands:

  - WHY we’re doing anything - WHAT success looks like - WHO is responsible for doing it - HOW they’re going to do it - WHEN they’re going to do it

• by vp8989 on 12/28/21, 2:29 AM

  I like this framework. Is this only applicable for debugging projects that are already in motion, but going poorly?

  I was trying to think if it could also be used to shape the discussion and documentation in the planning/design phase. But at that stage it seems like you'd first need to declare WHO is responsible for deciding what the appropriate WHY/WHAT are?