I work in an organization where the developers pretty much run the show, it sounds like heaven but we bump into churn situations like this all the time.
The thing the author doesn't really realize in this article is that building consensus and making sure everyone agrees with the priority of the project is part of the job.
It kinda sounds like he had pet project that others disliked so they tried to kill it by claiming the "dashboard team" was handling it. Then he attempted to vicariously micromanage the project from another team.
The thing the author doesn't really realize in this article is that building consensus and making sure everyone agrees with the priority of the project is part of the job.
It kinda sounds like he had pet project that others disliked so they tried to kill it by claiming the "dashboard team" was handling it. Then he attempted to vicariously micromanage the project from another team.