[benkross]

Hey j_baker thanks for sharing your perspective. The beauty and curse of code is that it's hard to have subtext that isn't explicit, like in your example. Again if "Let's see what product thinks" has the negative connotation you allude to, in my mind that is a horribly run company. We are still very small (6 ppl) so I want everyone to think like product managers and CEOs - as long as they fulfill their core responsibilities. It gets a little harder bc sometimes, engineers will be vetoed, not because they don't have great ideas, but ultimately, there is some negotiation between a great product/experience and something sellable or to work with a time constraint.

I personally think it is ASININE not to involve my engineers in the decision process, bc they might be able to optimize my business process, or even my thoughts as a product owner. I am a sales and marketing guy, that desperately wants to become a good product manager. The only way I can do that is by learning from others' approaches. If you'd like to continue the dialogue feel free to email me at [e-mail]

Cheers,

Ben CoFounder ProjectSherpa [e-mail]