Skip to main content

Product Design Example

My recent entry on whether it is appropriate for a product manager to dictate user interface design generated several comments. Random proposed a hypothetical example to help clarify the issue. He wrote (punctuation edited):

"Here is a hypothetical case. Assume all the customers have browsers that support Java Applets. So the Applet UI would work in the given market. Assume you are building a Web app of some kind. Assume there are three different people in the role of product manager, product designer, and software developer.

Who decides whether the UI is HTML or applets? How is it decided?"

I would say the product developer plays the most direct part in determining whether the UI is based on HTML, applets, or some other technology. However, all three roles play a part.

The product manager formulates the requirements in completely UI-neutral terms. The product designer specifies the UI without dictating what technology to use to realize the UI. The product developer decides on the technology that will implement the UI the designer has specified.

However, a great deal of cooperation, feedback, and iteration are nonetheless necessary to make this process work.

A product manager can formulate requirements all he wants, but it may not technically be possible to satisfy them. The product designer may not be able to conceive of a user interface that satisfies an ease of use constraint, for example. The product manager and designer must therefore cooperate to formulate requirements that are realistic.

Similarly, a product designer can specify a user interface that no UI technology (HTML, applets, etc.) is designed to implement. The development team might have to write their own UI framework to implement what the designer specified. Writing their own framework might be a good thing, or it might unacceptably delay release of the product. The designer and developer must cooperate to specify a user interface that is possible to implement on schedule.

Ultimately, the product developer should determine which implementation technology to use. But the product manager's and designer's inputs drive the decision, and the product developer's expertise on what's feasible feeds back into the requirements and UI design.

Comments

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio