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 Architecture
We have turned our faces towards the future
During the modern era, we have even changed our bodily position in relation to the flow of time; the Greeks understood that the future came from behind their backs and the past receded away in front of their eyes, but we have turned our faces towards the future, and the past is disappearing behind our backs.
A timeless space
Our culture reveres youth, aspires to agelessness and is frightened by signs of age, wear and decay. As a consequence of this obsession, and the qualities of our man-made materials, contemporary environments have lost their capacity to contain and communicate traces of time. Our buildings often seem to exist in a timeless space without contact with the past or confidence for the future.
Theatre Epidaurus, Greece, 330 BC
Mounting the massive cut stone stairs [of the amphitheater], we note the way in which the overhanging front edge of each seat folds down to form the first step up to the next section, the second step being the front edge of the foot space of the next set of seats. This detail is complemented by the way the undercut beneath the front edge of each seat is curved rather than sharp-edged — a detail that, being hidden in the shadows, is first revealed by our touch. An equally subtle detail is the way each stone seat is lifted slightly above the level of the foot space behind it, so that one does not set foot on the surface upon which others sit.
The secret life of sculpture
The sculptures are arranged in informal groupings, carefully placed to catch the natural light that brings them to life, so that, when we enter the room, it seems we have interrupted an ongoing conversation among them.
Church on the Water, Hokkaido, 1985–8
At the edges of the outer walls to left and right, the slate floor is held back, creating a shadowed slot into which the concrete wall slips out of sight. Because the wall does not meet and bear upon the floor, as is usual, the relationship of the wall to the ground is uncertain, and the rippling surface of the black slate floor appears to float free of the walls, merging with the rippling surface of the water.
We must go with them
"You cannot make what you want to make, but what the material permits you to make. You cannot make out of marble what you would make out of wood, or out of wood what you would make out of stone. Each material has its own life, and one cannot without punishment destroy a living material to make a dumb senseless thing. That is, we must not try to make our materials speak our language, we must go with them to the point where others will understand their language."
— Constantin Brancusi
Wood
Wood speaks of its two existences and timescales: its first life as a growing tree and the second as a human artefact made by the caring hand of a carpenter or cabinet maker.
Lightness & Heaviness
"Lightness is born of heaviness and heaviness of lightness, instantaneously and reciprocally, returning creation for creation, gaining strength proportionally as they gain in life, and as much more in life as they gain in motion. They destroy one another also at the same time, fulfilling a mutual vendetta, proof that lightness is created only in conjunction with heaviness, and heaviness only where lightness follows."
— Leonardo da Vinci
Errors & Crimes
"A builder who hides any part of the building frame, abandons the only permissible and, at the same time, the most beautiful embellishment of architecture. The one that hides a loadbearing column makes an error. The one who builds a false column commits a crime."
— Auguste Perret
Desired qualities of light
In today's architectural practice, light is regrettably often treated merely as a quantitative phenomenon; design regulations and standards specify required minimum level of illumination and window sizes, but they do not define any maximum levels of luminance, or desired qualities of light, such as its orientation, temperature, color, or reflectedness.
Salk Institute for Biological Studies, La Jolla, 1959–65
If you are there at sunset, as are the scientists every day, you see the most magical of transformations: the golden glow that fills the sky to the west is first reflected in the water of the ocean and then shoots like a line of fire up through the gathering darkness of the plaza's stone floor, to reach its source in the cubic fountain. The court is breathtaking in its sublime power, opening at the edge of the continent to the Pacific Ocean and framing the light blue-on-dark-blue horizon line of the sea and sky.
Secreted
House and home are two evidently different notions: house is a material, spatial and architectural concept, whereas home is a unique setting and product of the act of dwelling itself. Home is charged with subjective meanings, symbols, memories, and images.
A home is also a set of personal rituals, habits, rhythms, and routines of everyday life. In every sense of the word, home is an extension of its inhabitant. Consequently it can not be an object of design by an architect; it is secreted, as it were, by the actual act of dwelling.
Room continuum
The Modernist aspiration for continuous, flowing space and open interconnections between spaces has a tendency to reduce the sense of room-ness by turning space into a continuum, creating a flow through units instead of projecting a spatial object.
Tree, leaf, house, city
"Tree is leaf and leaf is tree – house is city and city is house. A city is not a city unless it is also a huge house – a house is a house only if it is also a tiny city."
— Aldo van Eyck
Chapel of St. Ignatius, Seattle, 1995–7
The exterior walls of the Chapel of St. Ignatius are made of large, complexly interlocking concrete slabs, a variegated golden-brown in color, and the roofs are clad in light grey metal. At the corners where the joints between the wall panels interlock are windows of various rectangular shapes and sizes, and the egg-shaped metal anchors that were used to lift the walls in place project slightly forward, casting small shadows.
- Bells
Dwelling in ritual
Even a dwelling is a device that generates a distinct pattern of daily activities and their relationships. Some buildings are explicitly built for ritual, but the repetition of any activity, either mundane or religious, tends to ritualize them, and by facilitating this, an architectural structure can turn gradually – sometimes even unnoticeably – into an instrument of ritual.
Ise Shrines, Nagoya, 685–Present
The Ise Shrines at Naiku and Geku, near Nagoya, highly refined idealizations of ancient agricultural storehouses, have been rebuilt at least sixty-one times since first being established. The entire twenty-year building cycle is a continuous, precisely defined ritual. The result is unlike any religious structure in the world, one that is always new, and at the same time over a millenium old.
Memory & Fantasy
Memory and fantasy are related, as are recollection and imagination; one who cannot remember also cannot imagine, as memory is the very soil of imagination.
In our bodies
We tend to think of our memory as a cerebral capacity, but the act of memorizing engages our entire body. Remembering is not solely a mental even; it is also an act of embodiment and bodily projection. Memories are not only hidden in the electrochemical processes of the brain; they are also stored in our skeletons, muscles, senses, and skin.
American Folk Art Museum, New York City, 1998–2001
As we draw closer, we see that the three-faceted planes of the museum are fabricated out of rectangular panels made of white bronze that was poured directly into dammed forms on the concrete floor of the foundry, producing a surface texture similar to both metal and stone.
Take your names with you
When the Masai of Kenya were forced to relocate, they took with them the names of hills, rivers, and plains, and fitted them to the topography of their new domicile.
The same desire is reflected in the countless European place names in the United States, as the borrowed names had the power to project a sense of familiarity in a strange and unfamiliar land.