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.
On Love
Not knowing quite what they mean
"Do you understand all the symbolism?"
"Not really, besides its being Venus and Cupid."
"I didn't even know that, so you're one up on me. I wish I'd read more about ancient mythology," she continued. "But actually, I like looking at things and not knowing quite what they mean."
We're not children, you know
We're not children, you know.
And with these words, she placed her lips on mine and we embarked on one of the longer and more beautiful kisses mankind has ever known.
To think
Few things are as antithetical to sex as thought. Sex is instinctive, unreflective, and spontaneous, while thought is careful, uninvolved, and judgmental. To think during sex is to violate a fundamental law of intercourse.
A cruel paradox
When we look at someone (an angel) from a position of unrequited love and imagine the pleasures that being in heaven with them might bring us, we are prone to overlook a significant danger: how soon their attractions might pale if they began to love us back. We fall in love because we long to escape from ourselves with someone as ideal as we are corrupt. But what if such a being were one day to turn around and love us back? We can only be shocked. How could they be as divine as we had hoped when they have the bad taste to approve of someone like us? If in order to love we must believe that the beloved surpasses us in some way, does not a cruel paradox emerge when we witness this love returned? "If s/he really is so wonderful, how could s/he love someone like me?"
Shoes
It was perhaps a pedantic matter over which to come to such a decision, but shoes are supreme symbols of aesthetic, and hence by extension psychological, compatibility. Certain areas and coverings of the body say more about a person than others: shoes suggest more than pullovers, thumbs more than elbows, underwear more than overcoats, ankles more than shoulders.
I marshmallow you
Then I noticed a small plate of complimentary marshmallows near Chloe's elbow and it suddenly seemed clear that I didn't love Chloe so much as marshmallow her. What it was about a marshmallow that should suddenly have accorded so perfectly with my feelings toward her, I will never know, but the word seemed to capture the essence of my amorous state with an accuracy that the word 'love', weary with overuse, simply could not aspire to.
From then on, love was, for Chloe and me at least, no longer simply love, it was a sugary, puffy object a few millimeters in diameter that melts deliciously in the mouth.
A social animal
What does it mean that man is a "social animal"? Only that humans need one another in order to define themselves and achieve self-consciousness, in a way that mollusks and earthworms do not. We cannot come to a proper sense of ourselves if there aren't others around to show us what we're like.
"A man can acquire anything in solitude except a character," wrote Stendhal.
Possible lives
Watching Alice talk, light a candle that had blown out, rush into the kitchen with the plates, or brush a strand of blonde hair from her face, I found myself falling victim to romantic nostalgia, which descends whenever we are faced with those who might have been our lovers, but whom chance has decreed we will never properly know. The possibility of an alternative love story is a reminder that the life we are leading is only one of a myriad of possible lives, and it is the impossibility of leading them all that plunges us into sadness.
The threat of happiness
Dr. Saavedra had diagnosed a case of anhedonia, a disease defined by the British Medical Association as a reaction remarkably close to mountain sickness resulting from the sudden terror brought on by the threat of happiness. It was a common disease among tourists in this region of Spain, faced in these idyllic surroundings with the sudden realization that earthly happiness might be within their grasp, and prey therefore to a violent physiological reaction designed to counteract such a daunting possibility.
I don't see a wall
"I don't know, really. It's just a sense I have that ever since about the middle of September, we haven't really been communicating. It's like there's a wall between us and you're refusing to acknowledge it's there."
"I don't see a wall."
"That's what I mean. You're refusing to admit there was ever anything other than this."
"Than what?"
Romantic terrorism
Once a partner has begun to lose interest, there is apparently little the other can do to arrest the process. Like seduction, withdrawal suffers under a blanket of reticence. The very breakdown of communication is hard to discuss, unless both parties have a desire to see it restored.
This leaves the lover in a desperate situation. Honest dialogue seems to produce only irritation and smothers love in the attempt to revive it. Desperate to woo the partner back at any cost, the lover might at this point be tempted to turn to romantic terrorism, the product of irredeemable situations, a gamut of tricks (sulking, jealousy, guilt) that attempt to force the partner to return love, by blowing up (in fits of tears, rage, or otherwise) in front of the loved one. The terroristic partner knows he cannot realistically hope to see his love reciprocated, but the futility of something is not always (in love or in politics) a sufficient argument against it.
Certain things are said not because they will be heard, but because it is important to speak.
Walls
As the plane pierced through the clouds, I tried to imagine a future: a period of life was coming brutally to an end, and I had nothing to replace it with, only a terrifying absence.
What would life mean from now on? Though we continued holding hands, I knew how Chloe and I would watch our bodies grow foreign to each other. Walls would be build up, the separation would be institutionalized, I would meet her in a few months or years, we would be light, jovial, masked, dressed for business, ordering a salad in a restaurant—unable to touch what we were now revealing: the sheer human drama, the nakedness, the dependency, the unalterable loss. We would be like an audience emerging from a heart-wrenching play but unable to communicate any of the emotions they had felt inside, able only to head for a drink at the bar, knowing there was more, but unable to touch it.
In order that
No philosophy is further from the thought that what happens to us is random than psychoanalysis. I did not simply love Chloe and then she left me. I loved Chloe in order that she would leave me. It was not for the shape of her smile or the liveliness of her mind that I had chosen Chloe. It was because the unconscious, perverse casting director of my life had recognized in her a suitable character to leave the stage after inflicting the requisite amount of suffering.
The significance of love's burden
There is an Arabic saying that the soul travels at the pace of a camel. While most of our self is led by the strict demands of timetables and diaries, our soul, the seat of the heart, trails nostalgically behind, burdened by the weight of memory. If every love affair adds a certain weight to the camel's load, then we can expect the soul to slow according to the significance of love's burden.
What does wisdom counsel?
We start trying to be wise when we realize that we are not born knowing how to live, that living one's life is a skill that has to be acquired, like learning to ride a bicycle or play the piano. But what does wisdom counsel us to do? It tells us to aim for tranquility and inner peace, a life free from anxiety, fear, idolatry, and harmful passions. Wisdom teaches us that our first impulses may not always be trustworthy, and that our appetites will lead us astray if we do not train reason to separate vain from genuine needs.
Once again begun to fall
Such lessons appeared all the more relevant when Rachel accepted my invitation for dinner the following week, and the very thought of her began sending tremors through the region the poets have called the heart, tremors that I knew could have meant one thing only—that I had once again begun to fall.