Product Features & Requirements
Measured by the number of its features
A grossly obese set of requirements
Requirements proliferation
Features and complexity
It's not the features that matter
I'm sorry, I love engineers
Content as value
Intramural brownie points
We optimize what we measure
Chesterton’s Fence
When users never use the features they asked for
Minimum Awesome Product
An Article by Carlos BeneytoUsers are accustomed to a minimum of quality, and they expect that of all new products.
If our product does not [meet basic expectations of quality], people will automatically believe that it is a bad product and they will not take it seriously. It is not what they expect.
Hence my suggestion that the MVP has died and the MAP: Minimum Awesome Product was born.
Time-based analytics
An Article by Ryan SingerAnalytics apps don't tell you much about usage behavior. You might be able to see how many users performed an event, or how many times they did it. But none of the analytics packages out there are good at showing you how often people do things. Are they using to-dos once a week? Every day? Only signing into the app once a month but happily paying for years?
Time matters. You can't understand usage without time.
What 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.
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.
Feature parity
An ArticleWhilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business.
Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'.
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
Adding is favoured over subtracting in problem solving
A Research PaperHow would you change this structure so that you could put a masonry brick on top of it without crushing the figurine, bearing in mind that each block added costs 10 cents? If you are like most participants in a study reported by Adams et al. in Nature, you would add pillars to better support the roof. But a simpler (and cheaper) solution would be to remove the existing pillar, and let the roof simply rest on the base.
A series of problem-solving experiments reveal that people are more likely to consider solutions that add features than solutions that remove them, even when removing features is more efficient.
Not Just a New Feature; a New Compact
A Fragment by Jorge ArangoMy sense is that Slack’s teams think of themselves as adding ‘features’ to a ‘product,’ instead of as stewards of a place where people work.
Understanding the Kano Model
An Article by Jared SpoolThe horizontal axis represents the investment the organization makes. As investment increases, the organization spends more resources on improving the quality (remember, Noriaka was a quality guy at heart) or adding new capabilities.
The vertical dimension represents the satisfaction of the user, moving from an extreme negative of frustration to an extreme positive of delight. (Neutral satisfaction being neither frustrated nor delighted is in the middle of the axis.)
It’s against the backdrop of these two axes that we see how the Kano Model works. It shows us there are three forces at work, which we can use to predict our users’ satisfaction with the investment we make.
Doing It Right
An Article by Brad FrostDoing it right requires a different pace of working and a much broader thought process than “ok, let’s get this thing out the door.” Which is super tough because most workplaces place a huge emphasis on getting things out the door, and fast. Little agile tickets that are expected to be completed in micro sprints to me seem to be antithetical to doing it right.
The Web is Industrialized and I Helped Industrialize It
An Article by Dave RupertIn our cultural obsession with billionaire entrepreneurs we laud new features more than the maintenance and incrementalism work of making old features better and more accessible. Maintenance looks like red minus signs in the spreadsheet. New features look like green plus signs. New features look better on our LinkedIn profiles. New features have that pizzazz, baby.
When gardening, the building of planters and initial planting is a very short process. The majority of your time is spent nurturing and monitoring growth. I personally feel the struggle between maintainer work and new shiny feature work. I enjoy that new feature smell but I know that my day-to-day is more like a janitor on a boat mopping up someone else’s barf. In terms of metaphors, the gardening metaphor is certainly better, and it acknowledges that design and development still tend to be more creative endeavors.
Yagni
A Definition by Martin FowlerYagni originally is an acronym that stands for "You Aren't Gonna Need It". It is a mantra from Extreme Programming that's often used generally in agile software teams. It's a statement that some capability we presume our software needs in the future should not be built now because "you aren't gonna need it".
Product vs. Feature Teams
An Article by Marty CaganThis article is certain to upset many people.
In Praise of Shadows
- Things that shine and glitter
- A naked bulb
- The Japanese toilet
- Empty dreams
- Most important of all are the pauses
Things that shine and glitter
We find it hard to be really at home with things that shine and glitter. The Westerner uses silver and steel and nickel tableware, and polishes it to a fine brilliance, but we object to the practice. On the contrary we begin to enjoy it only when the luster has worn off, when it has begun to take on a dark, smoky, patina.
A naked bulb
The sight of a naked bulb beneath an ordinary milk glass shade seems simpler and more natural than any gratuitous attempt to hide it.
The Japanese toilet
The parlor may have its charms, but the Japanese toilet truly is a place of spiritual repose.
Empty dreams
But I know as well as anyone that these are empty dreams, and that having come this far, we cannot turn back.
Most important of all are the pauses
Japanese music is above all a music of reticence, of atmosphere. When recorded, or amplified by a loudspeaker, the greater part of its charm is lost. In conversation, too, we prefer the soft voice, the understatement. Most important of all are the pauses. Yet the phonograph and radio render these moments of silence utterly lifeless. And so we distort the arts themselves to curry favor for them with the machines.
The glow of grime
Of course this 'sheen of antiquity' of which we hear so much is in fact the glow of grime. In both Chinese and Japanese the words denoting this glow describe a polish that comes of being touched over and over again, a sheen produced by the oils that naturally permeate an object over long years of handling—which is to say grime. If indeed 'elegance is frigid', it can as well be described as filthy.
Lacquerware
There are good reasons why lacquer soup bowls are still used, qualities which ceramic bowls simply do not possess. Remove the lid from a ceramic bowl, and there lies the soup, every nuance of its substance and color revealed. With lacquerware there is a beauty in that moment between removing the lid and lifting the bowl to the mouth when one gazes at the still, silent liquid in the dark depths of the bowl, its color hardly different from that of the bowl itself.
To throw a shadow on the earth
In making for ourselves a place to live, we first spread a parasol to throw a shadow on the earth, and in the pale light of the shadow we put together a house.
The world of shadows
The 'mysterious Orient' of which Westerners speak probably refers to the uncanny silence of these dark places. And even we as children would feel an inexpressible chill as we peered into the depth of an alcove to which the sunlight never penetrated.
This was the genius of our ancestors, that by cutting off the light from this empty space they imparted to the world of shadows that formed there a quality of mystery and depth superior to that of any wall painting or ornament.
That one thing against another creates
Such is our way of thinking—we find beauty not in the thing itself but in the patterns of shadows, the light and the darkness, that one thing against another creates.
Wasting light
Yamamoto Sanehiko, president of the Kaizo publishing house, told me of something that happened when he escorted Dr. Einstein on a trip to Kyoto. As the train neared Ishiyama, Einstein looked out the window and remarked, "Now that is terribly wasteful." When asked what he meant, Einstein pointed to an electric lamp burning in broad daylight.
And the truth of the matter is that Japan wastes more electric light than any Western country except America.
- Poured
The eaves deep and the walls dark
I would call back at least for literature this world of shadows we are losing. In the mansion called literature I would have the eaves deep and the walls dark, I would push back into the shadows the things that come forward too clearly, I would strip away the the useless decoration. I do not ask that this be done everywhere, but perhaps we may be allowed at least one mansion where we can turn off the electric lights and see what it is like without them.
Follow the brush
One of the oldest and most deeply ingrained of Japanese attitudes to literary style holds that obvious structure is contrivance, that too orderly an exposition falsifies the ruminations of the heart, that the truest representation of the searching mind is just to 'follow the brush.'
I could never live in a house like that
Mrs. Tanizaki tells a story of when her late husband decided, as he frequently did, to build a new house. The architect arrived and announced with pride, "I've read your In Praise of Shadows, Mr. Tanizaki, and know exactly what you want."
To which Tanizaki replied, "But no, I could never live in a house like that."
There is perhaps as much resignation as humor in his answer.