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

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...

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the four problems that companies face, or are trying to overcome, as they make product decisions . Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions. They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to ...

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem...

Cauvin

Search This Blog