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.
Understanding Understanding
A dot went for a walk
A dot went for a walk and turned into a line.
The dot, the line, the dance, the story, and the painting had found connections. Memory became learning, learning became understanding.Learning is remembering what one is interested in. Learning, interest, and memory are the tango of understanding.
Creating a map of meaning between data and understanding is the transformation of big data into big understanding.
The dot had embraced understanding.
Understanding precedes action.
Each of us is a dot on a journey.Admitting ignorance
The most essential prerequisite to understanding is to be able to admit when you don't know something. Striving to be the dumbest person in the room.
When you don’t have to filter your inquisitiveness through a smoke screen of intellectual posturing, you can genuinely receive or listen to new information. If you are always trying to disguise your ignorance of a subject, you will be distracted from understanding it.
Information imposters
Information imposters: This is nonsense that masquerades as information because it is postured in the form of information. We automatically give a certain weight to data based on the form in which it is delivered to us. Because we don’t take the time to question this, we assume that we have received some information.
My favorite example of this is in cookbook recipes that call for you to “cook until done.” This doesn’t tell you very much. Why bother? Information imposters are fodder for administravitis.
Michaelangelo's hammer
A young man named Michelangelo stands in front of a huge granite monolith. He stands there at a time in history before the technologies that brought us the hammer and chisel have occurred. He gazes at the rock. He dreams his dream and the best that he is able to say is, What a wonderful stone you are.
…
Michaelangelo now stands in front of the same rock. Thrust into his hands are a hammer in one and a chisel in the other. He looks at his hands, at the technological tools that they hold, and gazing at the same stone, with epiphanic zeal, says I must let Moses out.
I won't get
If I don't ask, I won't get.
Talking with Clinton
When you are talking with Clinton, he is not looking over your shoulder to see who else is in the room. You can tell he is not thinking about how he is going to respond to you. He is there, present and listening.
By the way, when you scramble the letters in the word listen, it becomes a new word: silent. We’re so often wrapped up in our own self-talk, we forget to listen and learn the information in the first place…and you can’t remember or understand something you never observed.
Scales of change
To understand revolutionary change in its full complexity – not just what happened, but why it happened – we need a model that works across multiple scales, and the disciplines that traverse them.
The method
Well no, see, that’s the tricky part. I always try to come up with things that when they find out the method, the method is as interesting as the effect itself. — David Blaine
Selling your own ignorance
When you sell your expertise - and what I mean by sell is to move ahead in a corporation, or sell an idea to a publisher, or sell an ability to a client - by definition, you’re selling from a limited repertoire.
However, when you sell your ignorance to move ahead, when you sell your desire to create and explore and navigate paths to knowledge, when you sell your curiosity - you sell from a bucket with an infinitely deep bottom that represents an unlimited repertoire. And, you sell in a way that’s not intimidating, in a way that joins the explanation to the fascination that comes with understanding.
You only understand something relative to something you already understand
A good question is better than a brilliant answer
The eyes of a traveler
We’ve all heard that travel broadens the mind. But beneath this cliché lies a deep truth. Things stand out because they’re different, so we notice every detail, from street signs to mailboxes to two you pay at a restaurant. We learn a lot when we travel, not because we are any smarter on the road but because we pay such close attention. On a trip, we become our own version of Sherlock Holmes, intensely observing the environment around us. We are continuously trying to figure out a world that is foreign and new.
Too often, we go through our day-to-day life on cruise control, oblivious to huge swaths of our surroundings. To notice friction points – and therefore opportunities to do things better – it helps to see the world with fresh eyes. When you meet creative people with lots of ideas constantly bubbling to the surface, you often come away feeling that they are operating on a different frequency. And they are, most of the time. They have all their receptors on — and frequently turned up to eleven. But the fact is, we are all capable of this mode. Try to engage a beginner’s mind. For kids, everything is novel, so they ask lots of questions, and look at the world wide-eyed, soaking it all in. Everywhere they turn, they tend to think, Isn’t that interesting? rather than, I already know that.
By adopting the eyes of a traveler and a beginner’s mindset, you will notice a lot of details that you might normally have overlook. You put aside assumptions and are fully immersed in the world around you. In this receptive mode, you’re ready to start actively searching out inspiration.
Cart before the horse
It seemed to him that in pursuit of an all-purpose, all-serving health care plan, the country was designing an ocean liner before it even understood why boats float.
The What and the How
How many aspects of problem solving and design solutions are there? Many, many might answer.
But there are actually just two: What to do and how to do it.
Before anything else, before you consider how you’re going to get it done or how much you’ll have to pay for it or how you’ll get permission to do it — before anything else, you have to decide what you want. You have to decide what kind of place you want to live in, what kind of community, what kind of city.
We don’t pay enough attention to the old adage: Be careful what you wish for, because you just may get it.
Thinking with the hand
The idea of thinking with your hands is not the exclusive domain of sculptors or engineers. In healthcare, for exams, surgeons have a powerful link between the head and the hands. Of course, like all healthcare professionals, their work involves a lot of deep knowledge and understanding. But it’s not all in their brain. If you were in medical school, learning to be a surgeon, for example, would you want your professor to be someone who writes about surgery or would you rather be taught by a surgeon? Many surgeons don’t publish scholarly articles. They spent time perfecting their skill with their hands. In some ways, the relationship between surgery and the larger field of medicine is analogous to the relationship between design and the larger field of engineering. Designers — and design thinkers —often think with their hands.
A pattern of understandings
The clock has no finished design and it has been made without any careful drawings or mathematical calculations. The pieces are only made if I can hold their details in my head as I make them, without reference to any set of external measures. I do make rough sketches of some parts as a path to understanding them, but never use these during the making of the parts. The clock gradually grows through trial and error and lots of physical work with metal, but out of this has come a set of principles of making that were not clear to me before doing the clock. I have finally realized that what I am actually making is a pattern of understandings of the process of making rather than the things that are actually being made. — Richard Benson
#15
How different am I, making clock number 15, from the process of natural selection laboring under changing conditions to generate the biological constructs? That ancient evolutionary system works on the basis of trial and error repeated in huge numbers over immense spans of time, with the failures discarded and the successes retained. At times it seems to me that my clock making is quite similar, as my mind, just barely thinking, sorts through huge numbers of possibilities and discards them as failures before even trying them, so the few that are made have a pretty good chance of success. Is this foresight some form of understanding? I think not. No revelation here, just enough thinking to spur the maker on to cut some piece of metal which, once made, might fail or succeed. Yet — in either case — the thing made and its creation remains the sole root of any real understanding that takes place. The clock is crude but gets built, and even in its base simplicity teaches its maker how to understand what must be understood for something to be made. — Richard Benson
A classroom without walls
The city is education – and the architecture of education rarely has much to do with the building of schools. The city is a schoolhouse, and its ground floor is both bulletin board and library. The graffiti of the city are its window displays announcing themselves, telling about what they’re doing and why and where they’re doing it. Everything we do – if described, made clear, and made observable – is education: the Show and Tell, the city itself. It is a classroom without walls, an open university for people of all ages offering a boundless curriculum with unlimited expertise. If we can make our urban environment comprehensible and observable, we will have created classrooms with endless windows on the world.