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 Real World of Technology
Technology is a system
Technology is not the sum of the artifacts, of the wheels and gears, of the rails and electronic transmitters. Technology is a system. It entails far more than its individual material components. Technology involves organization, procedures, symbols, new words, equations, and, most of all, a mindset.
Fish and water
How does one speak about something that is both fish and water, means as well as end?
Defining activities
One has to keep in mind how much the technology of doing something defines the activity itself.
Holistic and prescriptive technologies
Holistic technologies are normally associated with the notion of craft. Artisans, be they potters, weavers, metal-smiths, or cooks, control the process of their own work from beginning to finish. Using holistic technologies does not mean that people do not work together, but the way in which they work together leaves the individual worker in control of a particular process of creating or doing something.
The opposite is specialization by process; this I call prescriptive technology. Here, the making or doing of something is broken down into clearly identifiable steps. Each step is carried out by a separate worker, or group or workers, who need to be familiar only with the skills of performing that one step. This is what is normally meant by "division of labor".
That which requires caring
Today's real world of technology is characterized by the dominance of prescriptive technologies.
The temptation to design more or less everything according to prescriptive and broken-up technologies is so strong that it is even applied to those tasks that should be conducted in a holistic way. Any tasks that require caring, whether for people or nature, any tasks that require immediate feedback and adjustment, are best done holistically. Such tasks cannot be planed, coordinated, and controlled the way prescriptive tasks must be.
Prescriptive technologies eliminate the occasions for decision-making and judgment in general and especially for the making of principled decisions. Any goal of the technology is incorporated a priori in the design and is not negotiable.
One-machine policy
Today population forecasts are based on extensive and reliable data. However, no such demographic base exists for the world's growing population of machines and devices. Now may be the time to take machine demography seriously and enter into real discussions about machine population control.
The downgrading of experience
Today scientific constructs have become the model of describing reality rather than one of the ways of describing life around us. As a consequence there has been a very marked decrease in the reliance of people on their own experience and their own senses.
The downgrading of experience and the glorification of expertise is a very significant feature of the real world of technology.
Reciprocity
Whenever human activities incorporate machines or rigidly prescribed procedures, the modes of human interaction change. In general, technical arrangements reduce or eliminate reciprocity. Reciprocity is some manner of interactive give and take, a genuine communication among interacting parties.
Instruments of cooperation
When work isn't shared, the instruments of cooperation – listening, taking note, adjusting – atrophy like muscles that are no longer in use.
When all you have is a hammer
The success and spread of a particular tool – and this tool can be organizational or administrative as well as mechanical – has another consequence. Any task tends to be structured by the available tools. It can appear that the available tools represent the best or even the only way to deal with a situation.
Thus is may be wise, when communities are faced with new technological solutions to existing problems, to ask what these techniques may prevent and not only to check what the techniques promise to do.
Consumption
The proponents of technology in the 1840s were very enthusiastic about replacing workers with machines. But somehow I find no indication that they realized that while production could be carried out with few workers and still run to high outputs, buyers would be needed for those outputs. The realization that though the need for workers decreased, the need for purchasers could increase, did not seem to be part of the discourse on the machinery question. Since then, however, technology and its promoters have had to create a social institution – the consumer – in order to deal with the increasingly tricky problem that machines can produce but it is usually people who consume.
Bridges as walls
The biographer of Robert Moses, Robert A. Caro, refers to the bridges and underpasses of the famed New York State parkways. These bridges and underpasses are quite low, intentionally specified by Moses to allow only private cars to pass. All those who traveled by bus because they were poor or black or both were barred from the use and enjoyment of the parkland and its "public amenities" by the technical design of the bridges. Even at the time of Robert Moses, a political statement of the form "We don't want them blacks in our parks" would have been unacceptable in New York State. But a technological expression of the same prejudice appeared to be all right. Of course, to the public the intent of the design became evident only after it was executed, and then the bridges were there.
Designed to be ruins
I don't want to talk here about the grand designs of the past – the sort of thing one finds in majestic cities, in palaces and temples; the sorts of layouts that brought a friend of mine to sum up his first impression of Washington D.C. by saying, "The place seems to be designed to be ruins."
Little sense of season
The real world of technology denies the existence and the reality of nature. For instance, there is little sense of season as one walks through a North American or western European supermarket.
Just as there is a little sense of season, there is little sense of climate. Everything possible is done to equalize the ambiance – to construct and environment that is warm in the winter, cool in the summer.
Humility
Maybe what the real world of technology needs more than anything else are citizens with a sense of humility – the humility of Kepler or Newton, who studied the universe but knew they were not asked to run it.
Technological middle age
In the automobile's technological middle age, it is hard, if not impossible, to tune or repair one's own vehicle. Technical standardization of cars has occurred, and with it the elimination of the user's access to the machine itself. At the same time, the infrastructures that once served those who did not use automobiles atrophied and vanished. Some may say they were deliberately starved out. Railways gave way to more and more roadways. And thus a technology that had been perceived to liberate its users began to enslave them.
All things change
The authors of this prognostication evidently assumed that the introduction of the sewing machine would result in more sewing – and easier sewing – by those who had always sewn. They would do the work they had always done in an unchanged setting. Reality turned out to be quite different.
It should be evident by now that there is no such thing as "just introducing" a new gadget to do one particular task. It is foolish to assume that everything else in such a situation will remain the same; all things change when one thing changes.
Exploiting emotion
There are no shortcuts to the investment of time and care in friendship and human bonding, and it is fraudulent to pretend otherwise. When human loneliness becomes a source of income for others through devices, we'd better stop and think a bit about the place of human needs in the real world of technology.
The receiving end
At times it helps to rephrase an observation in line with a perspective from the receiving end of technology. When my colleagues in the field of cold-water engineering speak of "ice-infested waters", I am tempted to think of "rig-infested oceans". Language is a fine barometer of values and priorities. As such it deserves careful attention.
Speaking people
Surely those who oversee and guide municipal transportation systems ought to use public transit during their work days. Why not put a clause to that effect in their job description or contract?
Requiring those whose work has a major impact on people's lives to experience some of the impact is really not too much ask. It means that they speak "people" rather than French, Cree, or Spanish.
Ping-pong patterns
The role of asynchronicity in unraveling social and political patterns without apparent replacement with other patterns cannot be overestimated. The ping-pong pattern of verbal communication is no longer tied to space or time.
Mechanisms and organisms
"Kant described a mechanism as a functional unity, in which the parts exist for one another in the performance of a particular function.
An organism, on the other hand, is a functional and structural unity in which the parts exist for and by means of one another in the expression of a particular nature.
This means that the parts of an organism – leaves, roots, flowers, limbs, eyes, heart, brain – are not made independently and then assembled, as in a machine, but arise as a result of interactions within the developing organism."
— Brian Goodwin, How the Leopard Changed His Spots