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.
Suburban Nation
A system for living
Unlike the traditional neighborhood model, which evolved organically as a response to human needs, suburban sprawl is an idealized artificial system. It is not without a certain beauty: it is rational, consistent, and comprehensive. Its performance is largely predictable. It is an outgrowth of modern problem solving: a system for living. Unfortunately, this system is already showing itself to be unsustainable.
The five components of sprawl
The dominant characteristic of sprawl is that each component is strictly segregated from the others.
- Housing subdivisions, also called clusters and pods
- Shopping centers, also called strip centers, shopping malls, and big-box retail
- Office parks and business parks
- Civic institutions
- Roadways
Subdivisions
Subdivisions can be identified as such by their contrived names, which tend toward the romantic—Pheasant Mill Crossing—and often pay tribute to the natural or historic resource they have displaced.
An unmade omelet
The successes of turn-of-the-century planning, represented in America by the City Beautiful movement, became the foundation of a new profession, and ever since, planners have repeatedly attempted to relive that moment of glory by separating everything from everything else. This segregation, once applied only to incompatible uses, is now applied to every use. A typical contemporary zoning code has several dozen land-use designations; not only is housing separated from industry but low-density housing is separated from medium-density housing, which is separated from high-density housing. Medical offices are separated from general offices, which are in turn separated from restaurants and shopping.
As a result, the new American city has been likened to an unmade omelet: eggs, cheese, vegetables, a pinch of salt, but each consumed in turn, raw.
Beauty and function
In truth, a lot of sprawl—primarily affluent areas—could be considered beautiful. This raises a fundamental point: the problem with suburbia is not that it is ugly. The problem with suburbia is that, in spite of all its regulatory controls, it is not functional: it simply does not efficiently serve society or preserve the environment.
Six qualities of traditional neighborhoods
- The center
- The five-minute walk
- The street network
- Narrow, versatile streets
- Mixed use
- Special sites for special buildings
Market segments
The segregation of housing by “market segment” is a phenomenon that was invented by developers who, lacking a meaningful way to distinguish their mass-produced merchandise, began selling the concept of exclusivity: If you live within these gates, you can consider yourself a success.
Cookie cutter
One term that gets a lot of play these days is “cookie cutter.” Developers are mortified about the way this term is used to describe their subdivisions, and they expend a good deal of energy—and money—avoiding it. As much as 20 percent of their construction budget goes toward the application of superficial variety—different shapes, colors, window types, different styles of tack-on ornament, French Provincial next door to California Contemporary. But these efforts are in vain, because beneath the surface articulation is a relentless repetition of the same building. The best way to create real variety is to vary not the architectural style but the building type. Indeed, in places like Georgetown, styles vary only slightly, but one never hears the term cookie cutter, thanks to the wide range of building types.
Worthwhile destinations
Pedestrian life cannot exist in the absence of worthwhile destinations that are easily accessible on foot. This is a condition that modern suburbia fails to satisfy, since it strives to keep all commercial activity well separated from housing.
The twenty-minute house
Despite the way that it sounds, the “twenty-minute house” is not a derogatory label. Quite the opposite—it refers to the fact that a house has only twenty minutes to win the affection of a potential buyer, since that is the average length of a realtor visit. The building industry has responded to this phenomenon by creating a product that is at its best for the first twenty minutes that one is in it.
Like trying to cure obesity by loosening your belt
“Trying to cure traffic congestion by adding more capacity is like trying to cure obesity by loosening your belt.”
Homebuilders
The term homebuilder describes the house as a product that exists independent of its context. This approach would be appropriate if houses floated freely in space, or in some other environment where actual interaction between neighbors was neither possible nor desired. But houses are not meant to exist in isolation, so to think of the individual house as the ultimate outcome of the builder’s craft robs that craft of its broader significance.
The cul-de-sac kid
In this environment where all activities are segregated and distances are measured on the odometer, a child’s personal mobility extends no farther than the edge of the subdivision. Even the local softball field often exists beyond the child’s independent reach.
The result is a new phenomenon: the “cul-de-sac kid,” the child who lives as a prisoner of a thoroughly safe and unchallenging environment.
This “isolation and boredom” is the outcome of an environment that fails to provide teenagers with the ordinary challenges of maturing, developing useful skills, and gaining a sense of self.
On-site parking
Most cities require new and renovated buildings to provide their own parking on site. This is probably the single greatest killer of urbanism in the United States today. It prevents the renovation of old buildings, since there is inadequate room on their sites for new parking; it encourages the construction of anti-pedestrian building types in which the building sits behind or hovers above a parking lot; it eliminates street life, since everyone parks immediately adjacent to their destination and has no reason to use the sidewalk; finally, it results in a low density of development that can keep a downtown from achieving critical mass.
Architectural mysticism
In response to their growing sense of insignificance, some architects have tried to regain a sense of power through what can best be described as mysticism. By importing arcane ideas from unrelated disciplines—such as contemporary French literary theory (now outdated) —by developing illegible techniques of representation, and by shrouding their work in inscrutable jargon, designers are creating increasingly smaller realms of communication, in order that they might inhabit a domain in which they possess some degree of control. Nowhere is this crisis more evident than in the most prestigious architecture schools.
Globally, locally, regionally
Think globally, act locally, but plan regionally.