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.
The Architecture of Happiness
A few millimeters apart
Aesthetes force us to consider whether happiness may not sometimes turn on the presence or absence of a fingerprint, whether in certain situations beauty and ugliness may not lie only a few millimeters apart, whether a single mark might not wreck a wall or an errant brush stroke undo a landscape painting.
Tragic colors
Life may have to show itself to us in some of its authentically tragic colors before we can begin to grow properly visually responsive to its subtler offerings.
Classical absurdity
Corbusier observed that the requirements of flight of necessity rid airplanes of all superfluous decoration and so unwittingly transformed them into successful pieces of architecture. To place a Classical statue atop a house was as absurd as to add one to a plane, he noted, but at least by crashing in response to this addition, the plane had the advantage of rendering its absurdity starkly manifest.
Ideas of a good life
In essence, what works of design and architecture talk to us about is the kind of life that would most appropriately unfold within and around them. They tell us of certain moods that they seek to encourage and sustain in their inhabitants. While keeping us warm and helping us in mechanical ways, they simultaneously hold out an invitation for us to be specific sorts of people. They speak of visions of happiness.
To describe a building as beautiful therefore suggests more than a mere aesthetic fondness; it implies an attraction to the particular way of life this structure is promoting through its roof, door handles, window frames, staircase, and furnishings. A feeling of beauty is a sign that we have come upon a material articulation of certain of our ideas of a good life.
The people we love
The objects we describe as beautiful are versions of the people we love.
The search for happiness
If the search for happiness is the underlying quest of our lives, it seems only natural that it should simultaneously be the essential theme to which beauty alludes.
An equivalence
In both early Christianity and Islam, theologians made a claim about architecture likely to sound so peculiar to modern ears as to be worth of sustained examination: they proposed that beautiful buildings had the power to improve us morally and spiritually. They believed that, rather than corrupting us, rather than being an idle indulgence for the decadent, exquisite surroundings could edge us towards perfection. A beautiful building could reinforce our resolve to be good.
Behind this distinctive claim lay another astonishing belief: that of an equivalence between the visual and ethical realms.
Inwardly to resemble
What we want, at the deepest level, is inwardly to resemble, rather than physically to possess, the objects and places that touch us through their beauty.
We can conclude from this that we are drawn to call something beautiful whenever we detect that it contains in a concentrated form those qualities which we personally, or our societies more generally, are deficient.
The gathering darkness of a Sunday evening
Our jobs make relentless calls on a narrow band of our faculties, reducing our chances of achieving rounded personalities and leaving us to suspect (often in the gathering darkness of a Sunday evening) that much of who we are, or could be, has gone unexplored.
What we don't like
A grasp of the psychological mechanism behind taste may not change our sense of what we find beautiful, but it can prevent us from reacting to what we don’t like with simple disbelief.
Our understanding of the psychology of taste can in turn help us to escape from the two great dogmas of aesthetics: the view that there is only one acceptable visual style or (even more implausibly) that all styles are equally valid.
Over-imagination
An architect intent on being different may in the end prove as troubling as an over-imaginative pilot or doctor. However important originality may be in some fields, restraint and adherence to procedure emerge as the more significant virtues in a great many others.
We rarely wish to be surprised by novelty as we round street corners. We require consistency in our buildings, for we are ourselves frequently close to disorientation and frenzy.
The extremes of order and complexity
Such works emphasize the truth of the ancient maxim that beauty lies between the extremes of order and complexity.
It follows that the balance we approve of in architecture, and which we anoint with the word ‘beautiful’, alludes to a state that, on a psychological level, we can describe as mental health or happiness. Like buildings, we, too, contain opposites which can be more or less successfully handled.
Beauty and strength
Yet the bridge testifies to how closely a certain kind of beauty is bound up with our admiration for strength, for man-made objects which can withstand the life-destroying forces of heat, cold, gravity or wind.
We respond with emotion to creations which transport us across distances we could never walk, which shelter us during storms we could not weather, which pick up signals we could never hear with our own ears and which hang daintily off cliffs from which we would fall instantly to our deaths.
With grace and economy
Both bridges accomplish daring feats, but Maillart’s possesses the added virtue of making its achievement look effortless - and because we sense it isn’t, we wonder at it and admire it all the more. The bridge is endowed with a subcategory of beauty we can refer to as elegance, a quality present whenever a work of architecture succeeds in carrying out an act of resistance - holding, spanning, sheltering - with grace and economy as well as strength; when it has the modesty not to draw attention to the difficulties it has surmounted.
The dignity of age
Wood and stone, and now concrete and wood, age slowly and with dignity. They do not shatter hysterically like glass, or tear like paper, but discolor with a melancholy, noble air.
Apportioning value
Contrary to the Romantic belief that we each settle naturally on a fitting idea of beauty, it seems that our visual and emotional faculties in fact need constant external guidance to help them decide what they should take note of and appreciate. ‘Culture’ is the word we have assigned to the force that assists us in identifying which of our many sensations we should focus on and apportion value to.
There was no fog in London
It is books, poems and paintings which often give us the confidence to take seriously feelings in ourselves that we might otherwise never have thought to acknowledge. Oscar Wilde referred to this phenomenon when he quipped that there was no fog in London before Whistler started painting the Thames. Likewise, there must have been little beauty in old stones before Japanese priests and poets began writing about them.
To the worms and the trees
We owe it to the fields that our houses will not be the inferiors of the virgin land they have replaced. We owe it to the worms and the trees that the buildings we cover them with will stand as promises of the highest and most intelligent kinds of happiness.