3 ms·
> But it also sounds that you're worried about engineers constantly challenging product manager's decisions? No, that's the exact opposite of what I said. In f
by PragmaticPulp 7y ago
> But it also sounds that you're worried about engineers constantly challenging product manager's decisions?
No, that's the exact opposite of what I said. In fact, I explicitly ended my post with a call to action for engineers to communicate concerns, suggestions, and questions to their product managers.
> It doesn't pretend to prescribe that to fix this pattern you need to do the opposite of every one of his bullet points.
That's my point: The article seeds this unrealistic idea of an over-idealized product management process that explicitly includes the reader at every step of the way. It manufactures an anxiety in the reader that a feature factory is a vaguely bad thing and if you recognize any of these 12 vague points, you're working within the bad thing.
Again, my problem isn't with the core suggestions to improve PM process that might be elaborated in the author's other posts. My problem is with the trend of people reading this article, finding some point to identify with somewhere, and erroneously concluding that their employer is doing it wrong and that's a bad thing.
My point was that if you want to be involved in the decision making process, provide feedback, or understand the reasoning behind the decisions you should be proactive about communicating. Instead, I see too many people reading this article and passively becoming disgruntled with their employers, without taking any steps to be more involved. Or the more they are involved, the more the complain about too many meetings, interruptions, and process overhead consuming their time that they'd rather use for quiet focus to get their work done. You can't have your cake and eat it too.
- hitekker 7y ago> without taking steps to become more involved It’s must be pretty comfortable to assume that the engineers here have never tried giving feedback in their workplace.