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 Poetics of Space
Poetic drugs
In the final chapters Bachelard lets slip (a confession really) how if he "were a psychiatrist," he would recommend a poem by Baudelaire to treat "anguish." His squabble then is not with the purpose but rather the approach of a still-young profession. And of course, why not treat the power of great poems as something akin to "virtual 'drugs'"?
The world itself dreams
For Plato and many medieval philosophers, imagination was construed primarily as a mimetic act of mirroring, representing, copying. This approach was often associated with deceit and illusion, with confounding original realities with secondary substitutes. By contrast, for Kant and the romantics—including German idealists and existentialists like Sartre—imagination was hailed as a productive force in its own right, the source of all true meaning and value.
Bachelard resisted both extremes. For him, imagination was at once receptive and creative—an acoustic of listening and an art of participation. The two functions, passive and active, were inseparable. The world itself dreams, he said, and we help give it voice.
The past of his image upon me
The poet does not confer the past of his image upon me, and yet his image immediately takes root in me. The communicability of an unusual image is a fact of great ontological significance.
In the world of sunlight
And here we come back to that forgotten, outcast word, the soul.
Indeed, the soul possesses an inner light, the light that an inner vision knows and expresses in the world of brilliant colors, in the world of sunlight.
Refuges
Of course, thanks to the house, a great many of our memories are housed, and if the house is a bit elaborate, if it has a cellar and a garret, nooks and corridors, our memories have refuges that are all the more clearly delineated. All our lives we come back to them in our daydreams.
Deprived of all thickness
Here space is everything, for time ceases to quicken memory. Memory—what a strange thing it is!—does not record concrete duration, in the Bergsonian sense of the word. We are unable to relive duration that has been destroyed. We can only think of it, in the line of an abstract time that is deprived of all thickness. The finest specimens of fossilized duration concretized as a result of long sojourn, are to be found in and through space.
Memories are motionless, and the more securely they are fixed in space, the sounder they are.
The odor of raisins
What would be the use, for instance, in giving the plan of the room that was really my room, in describing the little room at the end of the garret, in saying that from the window, across the indentations of the roofs, one could see the hill. I alone, in my memories of another century, can open the deep cupboard that still retains for me alone that unique odor, the odor of raisins drying on a wicker tray. The odor of raisins! It is an odor that is beyond description, one that it takes a lot of imagination to smell. But I've already said too much. If I said more, the reader, back in his own room, would not open that unique wardrobe, with its unique smell, which is the signature of intimacy.
Oneiric topography
If I were the architect of an oneiric house, I should hesitate between a three-story house and one with four. A three-story house, which is the simplest as regards essential height, has a cellar, a ground floor, and an attic; while a four-story house puts a floor between the ground floor and the attic. One floor more, and our dreams become blurred. In the oneiric house, topoanalysis only knows how to count to three or four.
Winter is by far the oldest of the seasons
...and we feel warm because it is cold out-of-doors.
I am the space where I am
Je suis l'espace où je suis.
This is a great line. But nowhere can it be better appreciated than in a corner.
My house is diaphanous
My house is diaphanous, but it is not made of glass. It is more of the nature of vapor. Its walls contract and expand as I desire.