products
Eating your own dog food
To anticipate all the uses and abuses
To read things that are not yet on the page
To love deeply a world of things
Product owner vs. product manager
Ensuring Excellence
The other way to build a massive tech company - doing it slowly
Framing vs. Shaping
The Nature of Product
An Article by Marty CaganToo many product managers and product designers want to spend all their time in problem discovery, and not get their hands dirty in solution discovery – the whole nonsense of “product managers are responsible for the what and not the how.”
Why Scrum is killing your product
An Article by Henry LathamWhat happens to user experience in a minimum viable product?
An Article by Ryan Singer"Feature complexity is like surface area and quality of execution is like height. I want a base level of quality execution across all features. Whenever I commit to building or expanding a feature, I'm committing to a baseline of effort on the user experience."
There’s a distinction to make: The set of features you choose to build is one thing. The level you choose to execute at is another. You can decide whether or not to include a feature like ‘reset password’. But if you decide to do it, you should live up to a basic standard of execution on the experience side.
Features can be different sizes with more or less complexity, but quality of experience should be constant across all features. That constant quality of experience is what gives your customers trust. It demonstrates to them that whatever you build, you build well.
Research, empathy, simplicity, speed
An Article by Matthew StrömAs Nosrat provides a simple list of essential ingredients for any great meal, can we describe a simple list of essential components for digital products?
Here are four elements that I believe are the foundation of great digital products: Research, Empathy, Simplicity and Speed.
August short No. 2: Glass
An Article by Riccardo MoriGlass looks and feels perfectly tailored to my photo sharing needs and expectations. For me it’s even better than pre-Facebook Instagram in the sense that it pushes me to select and share what I think are good photos (same as it happens with Flickr), rather than making me obsess with getting ‘the Instagram shot’ at all costs every day or multiple times in a day. It doesn’t cheapen photography like Instagram has done for years.
That’s why I hope Glass’s founders/developers will resist feature creep. Resist user objections like: I don’t think Glass is offering that much for the subscription price they’re asking. There are a lot of people who will gladly pay for having a cleaner, simpler, focused experience.
Apps Getting Worse
An Article by Tim BrayToo often, a popular consumer app unexpectedly gets worse: Some combination of harder to use, missing features, and slower. At a time in history where software is significantly eating the world, this is nonsensical. It’s also damaging to the lives of the people who depend on these products.
...Maybe we ought to start promoting PMs who are willing to stand pat for an occasional release or three. Maybe we ought to fire all the consumer-product PMs. Maybe we ought to start including realistic customer-retraining-cost estimates in our product planning process.
We need to stop breaking the software people use. Everyone deserves better.
The Hot Potato Process
An Article by Dan MallThe big misconception I’ve seen designers and developers often fall victim to is believing that handoff goes one way. Designers hand off comps to developers and think their work is done. That puts a lot of pressure on the designer to get everything perfect in one pass.
Instead, great collaboration follows what Brad Frost and I call “The Hot Potato Process,” where ideas are passed quickly back and forth from designer to developer and back to designer then back to developer for the entirety of a product creation cycle.
Signing party
An ArticleSince the Macintosh team were artists, it was only appropriate that we sign our work. Steve came up with the awesome idea of having each team member's signature engraved on the hard tool that molded the plastic case, so our signatures would appear inside the case of every Mac that rolled off the production line. Most customers would never see them, since you needed a special tool to look inside, but we would take pride in knowing that our names were in there, even if no one else knew.
Software that nobody wants
An Article by Gandalf HudlowFinding value is the result of enabling individual and group-level discovery attempts. It's not the result of everyone following one leader's gut.
What just happened is a new software product/feature was created that no customer wanted. This happens way too often. In fact, most hyper important software projects that must be done by date certain or else, have deep flaws that cause some variation of this phenomenon, flaws that include:
- Not wanted - Company specified a solution to a problem that customers don't actually have
- No Rarity - Company is pursuing an iKnockoff of existing products. The market already has two scaled competitors with working solutions, customers naturally spend budget on products that are already successful to avoid risk
- Incorrect Packaging - Customers need a website, but the company created an iOS app instead
- Incorrect Pricing - Customers need SaaS pricing, but the company created a shrink wrapped, on-premise solution with CapEx and maintenance agreements instead
Don't Serve Burnt Pizza
A Fragment by Jiaona ZhangSay you’re trying to test whether people like pizza. If you serve them burnt pizza, you’re not getting feedback on whether they like pizza. You only know that they don’t like burnt pizza. Similarly, when you’re only relying on the MVP, the fastest and cheapest functional prototype, you risk not actually testing your product, but rather a poor or flawed version of it.
Broken world thinking
A Fragment by Amanda MenkingConsider, for example, how “broken world thinking” can benefit product design. What if the person (or team) who invented a new technology collaborated with the person (or team) who would one day repair the same technology? What if the innovation stakeholders and the infrastructure stakeholders collaborated closely with the end users? What if every new product designed by a technology company was designed in such as way as to factor in what happens to the product after planned obsolescence?
Putting Thought Into Things
An Essay by Oliver ReichensteinBuilding structure requires serious listening, serious reflection, and serious imagination. All this requires experience, and no matter how experienced you are, it costs you. We spend our time and nerves to save users their time and nerves. Well-designed things give us the invaluable present of time. Well-designed products do not just save us time, they make us enjoy the time we spend with them. They make us feel that someone has been thinking about us, that a nice person took care of the little things for us. This is mainly why we perceive well-designed things as more beautiful the longer we use them, and the more used they become.
Two Cycles
Gorgeous artwork by Minori Asada.
Among the trees
To accommodate the spaces between the trees, I built three walls in a radial pattern. Filling out the spaces on both sides of these three spline-like walls, I came up with a structure that appears to be slipped in among the trees. This design allowed us to proceed without cutting down any of the woods.
Small economies
I refer to small money-earning business that consist of the work of a visible individual, or have evolved from a personal hobby or skill, as "small economies". We can include in this category newer forms of at-home work—side businesses, telecommuting and the like. The amount of income is unimportant; meager profits are compensated for by the motivation of the owner. A small economy may or may not be someone's main form of livelihood, but it is always a spontaneously conceived and continuing activity.
An extremely closed structure
Nearly all housing in Japan today consists of exclusively residential units for salaried workers and their nuclear families. Such residences have, by definition, no reason to interface with their surroundings.
Salaried workers commute to workplaces outside, and often a considerable distance from, their homes. Residences built for these workers do not contain a place of livelihood—in the broader sense, a place for exchange. This "residence-only housing" is only a place for the nuclear family to eat and sleep, with no occasions for interaction with the outside world, and no need to foster a sense of belonging to the community at large. Thus the only organizational principle is the maintenance of privacy. Both in external appearance and in lifestyle, it is an extremely closed structure.
Ecological cycles
This house exists in the midst of a year-long cycle of natural phenomena. One might say that this cycle entails the periodic "rise and fall" of the ground surface. In winter it sinks below a snow cover that grows head-high or more; as spring approaches, this height gradually decreases until we can see the actual ground surface, not yet covered with undergrowth. With summer the vegetation grows higher and higher until the plaza seems once again to be lower than its surroundings. With the falling of the leaves, autumn restores our ability to penetrate these surroundings at eye level, at least until the snow begins to fall again... Through the four seasons, we experience the sensation of the ground rising and falling, like the ebb and flow of the tide.
I call this cycle of natural phenomena an ecological cycle.
Doing community
There is a Japanese catchphrase, community suru, literally "making" or "doing" community. I will never forget the queasy feeling that came over me when I first heard that term, phrased as if community were a kind of event.
Hold an event, bring people together, get people who might otherwise never meet to interact. It's a wonderful thought. I have nothing against events per se. However, if they are not spontaneous and voluntary, they will not last. That is my objection to the keep-it-lively concept of community. The perception of community as event stems, I think, from a yearning for the festivals and rituals that once flourished in rural communities in Japan. But those events occurred precisely because a community existed, not the other way around.
What are those borders made of?
Functionalist modern architecture has prioritized the functionality of interiors and treated surfaces and external appearances as an outcome of that priority. Diagrams illustrating functional layouts generally frame them with thick borders. Updating conventional program theory entails questioning what those thick borders are actually made of, and how they should be designed. A dynamic program theory should be one that turns these thick borders into more organic interfaces that will foster exchanges and interactions.
An ecological cycle
In the design of his own residence / workplace, Toshiharu Naka created a small ecological cycle. Rows of green planters in front of the wall protect the house from the sun and help cool it in summer. Rainwater is collected via catch-basins from the roof, and used to water the planters.
In the water buckets is a micro-cycle — fish live in the buckets, eating mosquitos from the planters, eliminating the need for pesticides.