My definition of a stupid question

Stupid questions should not be confused with simple questions.

If a question has only one logical (or possible) answer, that can be deduced by the asker, then it is a stupid question.

I get these types of questions a lot as a Product Manager. I view my job as making things less ambigious. If there are multiple ways to do something, my job is to pick that way. Beyond that, the team should be able to find their own way. This creates engagement, makes their jobs more interesting and meaningful, and can help drive innovation (input from many instead of input from one).

One way I accomplish this is by a) clearly defining the customer segment and their behaviors/values, and b) setting up prioritized design guidelines. Both give program managers, developers, designers, etc the tools they need to make decisions for themselves. I've watched some very impressive decisions made by the team, simply based on their understand of our customers and how they behave.

My job is not to document the obvious. That's inefficent.

Then again, maybe that is why I am changing jobs.

No comments: