5 ms·
And then after saying no, you can watch the executives hire or promote up someone who says what they want to hear regardless of its feasibility, usually while u
by notabee 9y ago
And then after saying no, you can watch the executives hire or promote up someone who says what they want to hear regardless of its feasibility, usually while using the latest buzzwords. Lacking domain knowledge or the interest to acquire it is a good sign that they will lack the awareness to avoid facile answers.
- eanzenberg 9y agoSaying "No" or shutting that door down is a bad thing that I don't like either. Rephrase it by using "sure, we could build that, however it will require X person-days with a team of Y senior level engineers."
- s73v3r_ 9y agoDon't do that. All they're going to hear is "Sure, we could do that." They're not going to listen to the rest of it, and then it's going to be your fault when stuff doesn't work.
- Thrymr 9y agoAnother way to say it is "We could do that, but it will delay this other thing that is on your roadmap as top priority for X months."
- eanzenberg 9y agoThat's the point. Almost anything is possible with the right team. Once it's communicated in terms of cost then the assessment is made whether it's worth it or not.
- s73v3r_ 9y agoYou're assuming they listen to the cost. For many of these terrible bosses, the second they here "We can", they tune the rest of it out.
- glup 9y agoThis. As a PM, this is great for communicating tradeoffs to clients and senior management. As a dev, this is great for communicating tradeoffs to PMs. And conservative estimates of development time (e.g., the dev doubles the time estimate) result in solid, well-designed, thoroughly tested products.