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.
Dieter Rams: As Little Design as Possible
Beyond improvement
In so many ways Dieter Rams’s work is beyond improvement. Although new technologies have since offered new opportunities, his designs are not undermined by the limits of the technologies of their time. The concave button top, designed to stop your finger from slipping as it made the long travel necessary for earlier mechanical switches, does not point to obsolete mechanisms. Instead, it reminds us how immediately and intuitively form alone can describe what an object does and suggest how we should use it.
Cardinal sin
Indifference towards people and the reality in which they live is actually the one and only cardinal sin in design.
The duty of industrial design is first and foremost to users and the users are, generally, human beings, with all their complexities, habits, ideas and idiosyncrasies.
On display
The SK4 record player, aka 'Snow White's Coffin'.
Instead of being hidden away in a piece of furniture, the controls and the functional aspects of the device were not only on display, but they were the predominant feature of the design.
Rams suggested making a transparent lid from a new plastic that had just come on the market and was being used for advertising displays. It was an inspired thought and lent the phonograph just the lightness needed to balance the metal and wood of the base, as well as helping to define the acoustics. It also set the standard for all record players that followed - a turntable without a Perspex dust cover is now almost unthinkable.
Long-term
"Apart from his own design work, this is the second greatest achievement of Dieter Rams: establishing a design department within a company, which succeeded for decades in preserving its own individual approach and rigorously advancing it, without really being influenced by changing market interests." — Klaus Kemp
He is right; it was a remarkable feat. It takes a considerable degree of doggedness and conviction to follow the ungratifying and difficult path of insisting on a consistently long-term view in a corporate world that is constantly shifting and full of short-term decisions.
Humble servants
Our electrical appliances should be humble servants, to be seen and heard as little as possible. They should ideally stay in the background, like a valet in the old days, that one hardly noticed. — Erwin Braun
They should accompany an individual over a long period of time without hindering or disturbing through ‘extravagant forms, loud colors or flashy proportions’.
Restrained beauty
Braun design had a beauty that was more than skin deep. It would be wrong to say that because the Braun approach spurned fashion in an ongoing quest for functional and useable perfection, it ended up with this beauty by accident. There is a very strong aesthetic sense in both the proportion and materials of nearly all the products of the Rams era. They have a ‘restrained beauty’, he admits.
Braun products designed by Rams and his team have a haptic aesthetic as well: when you pick them up, handle them, and use them as the tools they are supposed to be, you become aware of the effort that has gone into making them sit comfortably in the hand, of the texture, weight and balance they possess, and of the satisfying click of the control buttons.
Camels
When you look at the consumer products generated by many other manufacturers, and even by Braun today, there seem to be an awful lot of camels around. Maybe these companies are too diffuse, have the decision-makers in the wrong places or are continually making the wrong decisions and have no one to stop them. They make products with short-term goals in mind, seducing the eye of the buyer with fashionable colors, sensational curves or exotic surfaces. They may have external designers and, perhaps most significantly, the brand identity is defined by external marketing concerns, rather than design or user-related issues.
The lesson to learn from Braun is that allowing a consistent philanthropic design approach to define a company can be extremely successful if it is executed with discipline, flexibility and good timing combined with hard work and, not least, great talent.
A timeless quality
Of all Rams’s products, the 606 Universal Shelving System is perhaps his most successful in fulfilling his own principles of good design. It is still in production today, some fifty years after its conception. The system is distinctive yet unobtrusive, and when the shelves and cabinets are filled, its slim profile allows it to fade quietly into the background.
Its ‘plainness’ lends it a timeless quality that has transcended the vagaries of fashion like no other of Rams’s designs. It was conceived in such a way as to optimize its function as simply and in as many different situations as possible, while still permitting upgrades and alterations without falling into obsolescence: all later adaptations and additions could still be integrated into the original structure and sizes.
"Fashion objects are not capable of being long-lived," said Rams in 2007. "We simply cannot afford this throw-away mentality anymore. Good design has to have built-in longevity. I believe that the secret of the longevity of my furniture lies in its simplicity and restraint. Furniture should not dominate, it should be quiet, pleasant, understandable and durable."
A certain kind of world
Perhaps more directly than with the Braun products, my furniture arose from a belief in how the world should be ‘furnished’ and how man should live in this artificial environment. In this respect, each piece of furniture is also a design for a certain kind of world and way of living, they reflect a specific vision of mankind.
Designing detail
My heart belongs to the details.
I actually always found them to be more important than the big picture.
Nothing works without details.
They are everything, the baseline of quality.Truly functional design only comes from the most careful and intense attention to detail.
Although he did not directly design all products and even had very little to do with some of them, he constantly encouraged tiny improvements that could make a good design better. This attention to detail ranged from the acuteness of angles in forms; the size, feels and distances between switches; the integration of handle fixings; the placement and nature of graphic elements on the products themselves and extended to product photography and packaging.
Designing detail is about achieving a fine balance in all aspects and areas of the product, including those external to the object.
Controlled!
Braun design is greatly reduced - stripped of all that is unnecessary. Nevertheless, there is a strong aesthetic characterized by balance, order and harmony.
Self-control is very important. Although my own taste is involved it always has to be under control. Not suppressed though! Controlled!
Chromatic mutiny
Nevertheless there were a number of colorful appliances produced by Braun, particularly from the late 1960s onwards, when plastics in bright primary colors became fashionable and available.
T3 domino lighter
KMM 2 coffee grinder
HLD 4 hairdryer
KF 145 coffee maker
HT 95 pop-up toasterWhen Rams’s team used color in such a way, it was uncompromising in its intensity: loud and demanding. The highly reduced forms of the products that it clothed, which had gently rounded edges, smooth opaque surfaces and discreet (usually black) detailing only served to increase this intensity.
"The intention was to create product alternatives for people who wished for strong color highlights in their living environments. This impulse came from marketing - not from design,” says Rams, dissociating himself from this approach. This was one instance where marketing got the upper hand in the decision-making process and the design team had to bow to contemporary fashion.
Indeed, there is a defiant aspect to these chromatic exceptions; they are not so much compromises as mutinous responses. Nevertheless, the resulting products are beautiful objects in their stand-alone way.
Color codes
When not compelled to do otherwise, the Braun design team’s use of color in products was reduced to highly specific areas such as control switches. Restricting the use of color to small points on an otherwise neutral object concentrates its effect, which is shifted away from decoration and towards function, especially when each color is assigned a signal role such as green for ‘on / off' switches, red for ‘fm’ and yellow for ‘phono’ on hi-fis or yellow for the second hand on clocks and watches.
This color coding of operating details is a primary example of the self-explanatory nature of Braun products.
Shorten the wings
The labile tastes of certain decision-makers in a company are often a great burden for designers. Too many feel themselves qualified to pass judgment. And how insensitive, how superficial these judgments often are.
Taste, believes Rams, is something that needs to be trained, since the aesthetic decisions at this level in product design are intrinsically bound to the entire form and function of the object. It would be unimaginable, for example, that the management of an aerospace company would ask the designers of a new plane to shorten the wings because they think it would make it look prettier.
The evolution of Braun design principles
1975
Three general rules govern every Braun design - a rule of order, a rule of harmony and a rule of economy.1976
The function for us is the starting point and the target of every design.
Experience with design is experience with people.
Only orderliness makes design useful to us.
Our design attempts to bring all individual elements into their proper proportions.
Good design means to us: as little design as possible.
Our design is innovative because the behavior patterns of people change.1983
Good design is innovative.
Good design renders utility to a product.
Good design is aesthetic design.
Good design makes a product easy to understand.
Good design is unobtrusive.
Good design is honest.1985
Good design is innovative.
Good design makes a product useful.
Good design is aesthetic.
Good design makes a product understandable.
Good design is honest.
Good design is unobtrusive.
Good design is long-lasting.
Good design is thorough down to the last detail.
Good design is environmentally friendly.
Good design is as little design as possible.Less, but better
There must be millions less of things, less words, less gestures, less of everything. But every word and every gesture will become more valuable. If we can put it all into perspective we will need less things as a result.