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.
Wittgenstein's Mistress
- I think very well of him indeed
- A perfect circle
- The Eiffel Tower
- Ceci n'est pas une pipe
- Erased de Kooning Drawing
I think very well of him indeed
When I was still doubtful as to his ability, I asked G.E. Moore for his opinion. Moore replied, ‘I think very well of him indeed.’ When I enquired the reason for his opinion, he said that it was because Wittgenstein was the only man who looked puzzled at his lectures. — Bertrand Russell
A perfect circle
Once, being asked to submit a sample of his work, what Giotto submitted was a circle.
Well, the point being that it was a perfect circle.
And that Giotto had painted it freehand.The Eiffel Tower
When the sun had gotten to the angle from which Phidias had taken his perspective, the Parthenon almost seemed to glow.
Actually, the best time to see that is generally also at four o’clock.
Doubtless the taverns from which one could see that did better business than the taverns from which one could not, in fact, even though they were all in the same street.
Unless of course the latter were patronized by people who had lived in Athens long enough to have gotten tired of seeing it.
Such things can happen. As in the case of Guy de Maupassant, who ate his lunch every day at the Eiffel Tower.
Well, the point being that this was the only place in Paris from which he did not have to look at it.Ceci n'est pas une pipe
There is nobody at the window in the painting of the house, by the way.
I have now concluded that what I believed to be a person is a shadow.
If it is not a shadow, it is perhaps a curtain.
As a matter of fact it could actually be nothing more than an attempt to imply depths, within the room.
Although in a manner of speaking all that is really in the window is burnt sienna pigment. And some yellow ochre.
In fact there is no window either, in that same manner of speaking, but only shape.
So that any few speculations I have made about the person at the window would therefore now appear to be rendered meaningless, obviously.
Unless of course I subsequently become convinced that there is somebody at the window all over again.
I have put that badly.Erased de Kooning Drawing
Once, Robert Rauschenberg erased most of a drawing by Willem de Kooning, and then named it Erased de Kooning Drawing.
I am in no way certain what this is connected to either, but I suspect it is connected to more than I once believed it to be connected to.
The cat
The cat I began to think about instead was the cat outside of the broken window in the room next to this one, at which the tape frequently scratches when there is a breeze.
Which is to say that I was not actually thinking about a cat either, there being no cat except insofar as the sound of the scratching reminds me of one.As there was, or is, no person at the window in the painting of this house.
It is still a house
Perhaps even the very house which I burned to the ground contained such examples, even though it would obviously not contain them any longer, no longer being a house.
Well, it is still a house.
Even if there is not remarkably much left of it, I am still prone to think of it as a house when I pass it in taking my walks.
There is the house I burned to the ground, I might think. Or, soon I will be coming to the house that I burned to the ground.The image of reality
Leonardo wrote in his notebooks backwards, from right to left, so that they had to be held up to a mirror to be read.
In a manner of speaking, the image of Leonardo’s notebooks would be more real than the notebooks themselves.Equidistance
Once, in the Rijksmuseum, I brought in new speakers for my phonograph. What the directions told me to do was make certain that the two speakers were equidistant from each other.
One certainly had to wonder what the person who wrote the instructions could have believed he meant by that.A strange calligraphy
Along the sand there will be frisky shadows, that will dance and fall away.
Or, if there is snow, the flames will write a strange calligraphy against the whiteness.Van Gogh
One of the things people generally admired about Van Gogh, even though they were not always aware of it, was the way he could make even a chair seem to have anxiety in it. Or a pair of boots.
The meaning of music
Once, somebody asked Robert Schumann to explain the meaning of a certain piece of music he had just played on the piano.
What Robert Schumann did was sit back down at the piano and play the piece of music again.
Good morning, Vincent
Perhaps I shall name the cat that scratches at my broken window Van Gogh.
Or Vincent.
One does not name a piece of tape, however.
There is the piece of tape, scratching at my window. There is Vincent, scratching at my window.Good morning, Vincent.
The illusion of anxiety
Or because of hormones.
And so which would not really have been anxiety at all, but only an illusion.
Even if one would certainly be hard put to explain the difference between an illusion of anxiety and anxiety itself.Somebody is living on this beach
Once, I had a dream of fame.
Generally, even then I was lonely.
To the castle, a sign must have said.
Somebody is living on this beach.