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.
Letters to the Future
The lapse of many years
At this point I wish to emphasize what I believe will ultimately prove to be the greatest purpose of our museum. This value will not, however, be realized until the lapse of many years, possibly a century, assuming that our material is safely preserved. And this is that the student of the future will have access to the original record of faunal conditions in California and the west, wherever we now work. He will know the proportional constituency of our faunae by species, the relative numbers of each species and the extent of the ranges of species as they exist today.
— Joseph Grinnell, 1910
The Grinnell System
The recording of field notes was common practice for biological surveyors and naturalists generations before Grinnell. His system continues this tradition but is distinguished by its distinctive standardized format. It consists of three sections:
- The journal contains a narrative account describing the study site and summarizing each day’s activities and observations, including a list of species encountered. This section is often peppered with sketches, photographs, or maps.
- The catalog is a sequential record of all voucher specimens collected, each with a unique field number and the information needed for the specimen’s museum tag, such as its sex, mass, breeding status, and standard body measurements.
- Species accounts are species-specific summaries of information and observations, gradually accumulated over multiple days at a site or across multiple sites, that eventually grow to detailed summaries of physical description, seasonal behaviors, microhabitat associations, and other characteristics.
Separating the notebook in this fashion allows each section to have its own context-specific structure and format.
Jim's system
From the earliest days of my fieldwork until now, throughout a given day I jotted notes, typically in pencil, into a small, spiral-bound pocket notebook, remembering the admonition not to trust one’s memory but to record observations as continually as possible. I then transcribes these notes into my handwritten journal in the evenings on the best of days or every few days when an intense field effort allowed.
From 2000 onward, I would still takes pencil notes in a small pocket notebook in the field, but I transcribes these into a word-processor document with margins set for the size of our field note pages. I combined this document with my field catalog for a particular trip and eventually both would be bound in the same manner as standard, handwritten field notes.
This approach had the advantage of producing both an archival paper copy as well as an electronic copy. It was also easy to intersperse specialized maps and digital photographs, which had become the norm by this time, throughout the journal text.
John's system
I have two field notebooks: a “raw" notebook and my formal Grinnellian notebook.
In the field, I take all my raw notes in a waterproof notebook using a fine-point permanent pen (or pencil when its raining). The entries have virtually no structure other than the date at the top of (almost) every page.
At the end of the day, I transcribe the notes into my Grinnellian journal as if I were writing a latter to a colleague.
Record them all
You can’t tell often in advance which observations will prove valuable. Do record them all!
— Joseph Grinnell, 1908
Recommendations for field notes
Being an end-user of someone else’s field notes certainly gives you insight into the benefits of good note-taking skills. Our experiences as end-users and creators of archival field notes lead us to a few specific recommendations:
(1) Don’t get bogged down in the details of format or style.
Rules are counterproductive if they prevent a researcher from taking field notes in the first place.
You will get more return by focusing on your content than by refining your formatting.
(2) Compose your notes as if you were writing a letter to someone a century in the future.
Writing for an external audience requires you to be more explicit in your descriptions and to take less knowledge for granted. Avoid the use of abbreviations, symbols, and other shortcuts that only you will understand.
Ask yourself: How would you describe this to someone over the phone?
(3) It is better to spend five minutes writing the important details than twenty minutes writing the trivial ones.
Field notes
Field notes example.
Camp's notes
Grinnell-era field notes example, Charles L. Camp.