2 ms·
These two are a very common form of dysfunction in large companies. The team trying to do feature Y needs feature X, the team responsible for feature X is behin
by ChuckMcM 9y ago
These two are a very common form of dysfunction in large companies. The team trying to do feature Y needs feature X, the team responsible for feature X is behind because feature W is taking longer than expected. Sometimes a person can see that feature W is hung up waiting on feature Y, and you discover an structural form of deadlock.
At the ground level engineers are frustrated because if they could just get "those idiots" to do the one thing they needed they could make progress. Without ever realizing that they were the "those idiots" in someone else's dependency tree.
If you are a senior technical leader (or want to be one) it is always worthwhile to follow these threads to figure out what is going on, even though it might seem like a distraction. The larger the organization the more challenging this can be but most people will tell you what they are working on and why its important (which is to say what will be fixed/improved/made possible by its delivery)