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.
Introduction to Permaculture
The conscious design and maintenance of agriculturally productive systems which have the diversity, stability, and resilience of natural ecosystems. It is the harmonious integration of the landscape with people providing their food, energy, shelter and other material and non-material needs in a sustainable way.
About Permaculture
The word Permaculture is taken from the Latin Permanens–meaning to endure of persist through time and cultura–referring to cultures–coming together. Permaculture is an interdisciplinary design science in the field of sustainable system design, with sustainable defined as:
a system which over its lifetime produces energy equivalent to or in excess of what it consumes.
Permaculture ethics
Permaculture operates on three:
- Care of Earth
- Care of Species
- Return of Surplus to the first two
Using akido on the landscape
I have spoken, on a more mundane level, of using akido on the landscape, of rolling with the blows, turning adversity into strength, and using everything positively. The other approach is to karate the landscape, to try to make it yield by using our strength, and striking many hard blows. But if we attack nature we attack (and ultimately destroy) ourselves.
Permaculture principles
There are two basic steps to good permaculture design. The first deals with laws and principles, while the second is more closely associated with practical techniques.
The principles are inherent in any permaculture design, in any climate, and at any scale. They are, briefly:
- Relative location: every element is placed in relationship to another so that they assist each other
- Each element performs many functions.
- Each important function is supported by many elements.
- Efficient energy planning for house and settlement.
- Emphasis on the use of biological resources over fossil fuel resources.
- Energy recycling on site.
- Using and accelerating natural plant succession to establish favourable sites and soils.
- Polyculture and diversity of beneficial species for a productive, interactive system.
- Use of edge and natural patterns for best effect.
Design is a connection between things
The core of permaculture is design. Design is a connection between things. It's not water, or a chicken, or the tree. It is how the water, the chicken and the tree are connected. It's the very opposite of what we are taught in school. Education takes everything and pulls it apart and makes no connections at all. Permaculture makes the connection, because as soon as you've got the connection you can feed the chicken from the tree.
To enable a design component to function efficiently, we must put it in the right place.
Inputs and outputs
For things to work properly, we must remember that:
- The inputs needed by one element are supplied by other elements in the system; and
- The outputs needed by one element are used by other elements (including ourselves).
Each element performs many functions
Each element in the system should be chosen and placed so that it performs as many functions as possible.
Each important function is supported by many elements
Important basic needs such as water, food, energy, and fire protection should be served in two or more ways.
The wild energies
Sectors deal with the wild energies, the elements of sun, light, wind, rain, wildfire, and water flow. These all comes from outside our system and pass through it. For these, we arrange a sector diagram based on the real site, usually a wedge-shaped area that radiates from a centre of activity.
Elements are placed according to intensity of use, control of external energies, and efficient energy flow.
Turn them into cycles
Permaculture systems seek to stop the flow of nutrient and energy off the site and instead turn them into cycles, so that, for instance, kitchen wastes are recycles to compost; animal manures are directed to biogas production or to the soil; household greywater flows to the garden; green manures are turned into the earth; leaves are raked up around trees as mulch.
Time stacking
The British devised a system of farming in which pastures were broken up after the animals had been on them a few years. The pasture was plowed up and put into a high nutrient-demand crop, followed by a grain crop, followed by a root crop. One year it was left fallow to rest the soil. This was sustainable, but it took a long time to cycle.
Masanobu Fukuoka, that master strategist, deals with time stacking. He does not have to follow, because he never removes the main part of the crop from the soil. He starts the next crop before the last crop is finished.
The garden is a riot
In conventional agriculture, vegetation is kept at the weed or herb level using energy to keep it cut, weeded, tilled, fetilised, and even burnt; that is, we are constantly setting the system back and incurring work and energy-costs when we stop natural succession from occurring.
Instead of fighting this process, we can direct and accelerate it to build our own climax species in a shorter time.
There is no attempt to form the garden into strict neat rows; it is a riot of shrubs, vines, garden beds, flowers, herbs, a few small trees, and even a small pond. Paths are sinuous, and garden beds might be round, key-holed, raised, spiraled, or sunken.
We should not confuse order and tidiness
To the observer, this may seem like a very unordered and untidy system; however, we should not confuse order and tidiness. Tidiness separates species and creates work, whereas order integrates, reducing work and discouraging insect attack. European gardens, often extraordinarily tidy, result in functional disorder and low yield. Creativity is seldom tidy.
Perhaps we could say that tidiness is something that happens when compulsive activity replaces thoughtful creativity.
The number of ways in which things work
The importance of diversity is not so much the number of elements in a system; rather it is the number of functional connections between these elements. It is not the number of things, but the number of ways in which things work.
Species guilds
Guilds are made up of a close association of species clustered around a central element (plant or animal). This assembly acts in relation to the element to assist its health, aid in management, or buffer adverse environmental effects.
An edge is an interface
An edge is an interface between two mediums. Edges are places of varied ecology. There is hardly a sustainable traditional human settlement that is not sited on those critical junctions of two natural economies. Successful and permanent settlements have always been able to draw from the resources of at least two environments.
An edge is a sieve
The edge (boundary) acts as a net or sieve: energies or materials accumulate at edges, e.g. soil and debris are blown by wind against a fence; seashells form a line at the tide-marks on a beach; leaves accumulate at kerbsides in a city.
Everything works both ways
Disadvantages can be viewed as "problems" and we can take an energy-expensive approach to "get rid of the problem", or we can think of everything as being a positive resources: it us up to us to work out just how we can make use of it.
"Problems" can be intractable weeds, huge boulders lying on the perfect house site, and animals eating garden and orchard produce. How can we turn these into useful components of our system? Boulders on the perfect house site, for example, can be incorporated into the house itself, for beauty and as a heat storage system.
The quality of thought
It is the quality of thought and the information we use that determines yield, not the size or quality of the site.
Let the goals suggest themselves
There are several ways to start the design process, depending on your nature and needs. You can start out by defining your goals, as precisely as possible, and then look at the site with these goals in mind. Or you can take the site with all its characteristics (both good and bad), and let goals suggest themselves. Of the two questions—"What can I make this land do?"—or—"What does this land have to give me?"—the first may lead to exploitation of the land without regard to long-term consequences, while the second to a sustained ecology guided by our intelligent control.
Maps and observation
Maps are useful only when they are used in combination with observation. Never try to design a site by just looking at a map, even if it is thoroughly detailed with contour lines, vegetation, erosion gullies, and so on marked in.
Maps are never representative of the complex reality of nature. Remember, "The map is not the territory."
Reading the landscape
As we walk about a site and talk to people, we can note our observations. At this stage, we try to store the information we gain in some accurate way, carry a notebook, or a camera and tape-recorder, and make small sketches. The notes we end up with can later be used to devise design strategies.
We do not just see and hear, smell and taste, but we sense heat and cold, pressure, stress from efforts of hill-climbing or prickly plants, and find compatible or incompatible sites in the landscape. We note good views, outlooks, soil colours and textures. In face, we use (consciously) all our many senses and become aware of our bodies and responses.
Beyond this, we can sit for a time and notice patterns and processes: how some trees prefer to grow in rocks, some in valleys, others in grasslands or clumps. We see how water flows on the site, where fires have left scars, winds have bent branches or deformed the shape of trees, how the sun and shadows move, and where we find signs of animals resting, moving, or feeding. The site is full of information on every natural subject, and we must learn to read it well.
The group of blind mullahs
In a natural landscape, each element is part of the greater whole, a sophisticated and intricate web of connections and energy flows. If we attempt to create landscapes using a strictly objective viewpoint, we will produce awkward and dysfunctional designs because all living systems are more than just a sum of their parts. Our culture has tried to define the landscape scientifically, by collecting extensive data about its parts.
These methods are much like the group of blind mullahs in the Sufi tale, who try to describe an elephant.
If you have to do tedious work
If you have to stand somewhere doing tedious work, at least make it interesting.
The perverse arrangement of older houses
The main problem lies in the often perverse arrangement of older houses, which face the road rather than the sun, and in the mania for glass windows on all outside walls.
Always start at the doorstep
If you are having trouble knowing where to start, always start at the doorstep.
The American lawn
The American lawn uses more resources than any other agricultural industry in the world. The American lawn could feed continents if people had more social responsibility.
Why should it be indecent to have anything useful in the front half of your property or around the house where people can see it? Why is it low-status to make that area productive? The condition is peculiar to the British landscaping ethic; what we are really looking at here is a miniature British country estate, designed for people who had servants. It has become a cultural status symbol to present a non-productive facade. The lawn and its shrubbery is a forcing of nature and landscape into a salute to wealth and power, and has not other purpose or function.
The only thing that such designs demonstrate is that power can force men and women to waste their energies in controlled, menial, and meaningless toil.
From consumption to production
I see no other solution (political, economic) to the problems of mankind than the formation of small responsible communities involved in permaculture and appropriate technology. I believe that the days of centralised power are numbered, and that a re-tribalisation of society is an inevitable, if sometimes painful, process.
The greatest change we need to make is from consumption to production, even if on a small scale, in our own gardens.
People who force nature force themselves
People who force nature force themselves. When we grow only wheat, we become dough. If we seek only money, we become brass; and if we stay in the childhood of team sports, we become a stuffed leather ball.
To become a complete person, we must travel many paths, and to truly own anything, we must first of all give it away.
Eaves and sun