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 Eyes of the Skin: Architecture and the Senses
Thin ice
Today the 'depth of our being' stands on thin ice.
Extensions of the tactile sense
"Touch is the parent of our eyes, ears, nose, and mouth. It is the sense which became differentiated into the others." — Ashley Montagu
All the senses, including vision, are extensions of the tactile sense; the senses are specializations of skin tissue, and all sensory experiences are modes of touching, and thus related to tactility.
The computer creates a distance
Computer imaging tends to flatten our magnificent, multi-sensory, simultaneous and synchronic capacities of imagination by turning the design process into a passive visual manipulation, a retinal journey. The computer creates a distance between the maker and the object, whereas drawing by hand as well as working with models put the designer in a haptic contact with the object, or space.
The quality of an architectural reality
The quality of an architectural reality seems to depend fundamentally on peripheral vision, which enfolds the subject in the space...neurological investigations suggest that our processes of perception and cognition advance from the instantaneous grasp of entities towards the identification of details, rather than the other way around.
A hierarchical system of sense
During the Renaissance, the five senses were understood to form a hierarchical system from the highest sense of vision down to touch. Vision was correlated to fire and light, hearing to air, smell to vapour, taste to water, and touch to earth.
The inhumanity of contemporary architecture
The inhumanity of contemporary architecture and cities can be understood as the consequence of the neglect of the body and the senses, and an imbalance in our sensory system.
The art of the eye has certainly produced imposing and thought-provoking structures, but it has not facilitated human rootedness in the world.
Modernist design at large has housed the intellect and the eye, but it has left the body and the other senses, as well as our memories, imagination and dreams, homeless.
Estrangement and detachment, hospitals and airports
It is thought-provoking that this sense of estrangement and detachment is often evoked by the technologically most advanced settings, such as hospitals and airports.
Sonorisms IV
'an unending rainfall of images' (Calvino)
a cancerous growth of vision
we are unable to see or imagine life behind these walls
the patina of wear
to carve a volume into the void of darkness
time turned into shapeThe tacit wisdom of the body
It is evident that the architecture of traditional cultures is also essentially connected with the tacit wisdom of the body, instead of being visually and conceptually dominated. Construction in traditional cultures is guided by the body in the same way that a bird shapes its nest by movements of its body.
Mere retinal art
Instead of an existentially grounded plastic and spatial experience, architecture has adopted the psychological strategy of advertising and instant persuasion; buildings have turned into image products detached from existential depth and sincerity.
Architecture of our time often appears as mere retinal art.
Stage sets for the eye
With the loss of tactility, measures and details crafted for the human body – and particularly for the hand – architectural structures become repulsively flat, sharp-edged, immaterial and unreal. The detachment of construction from the realities of matter and craft further turns architecture into stage sets for the eye, into a scenography devoid of the authenticity of matter and construction. The sense of 'aura', the authority of presence, that Walter Benjamin regards as a necessary quality for an authentic piece of art, has been lost.
Vision reveals what the touch already knows
Deep shadows and darkness are essential
During overpowering emotional experiences, we tend to close off the distancing sense of vision; we close the eyes when dreaming, listening to music, or caressing our beloved ones. Deep shadows and darkness are essential, because they dim the sharpness of vision, make depth and distance ambiguous, and invite unconscious peripheral vision and tactile fantasy.
The street of an old town
How much more mysterious and inviting is the street of an old town with its alternating realms of darkness and light than are the brightly and evenly lit streets of today! Homogenous bright light paralyzes the imagination in the same way that homogenization of space weakens the experience of being, and wipes away the sense of place. The human eye is most perfectly tuned for twilight rather than bright daylight.
To carve a volume into the void of darkness
The nocturnal sound is a reminder of human solitude and mortality, and it makes one conscious of the entire slumbering city. Anyone who has become entranced by the sound of dripping water in the darkness of a ruin can attest to the extraordinary capacity of the ear to carve a volume into the void of darkness. The space traced by the ear in the darkness becomes a cavity sculpted directly in the interior of the mind.
The door handle is the handshake of a building
Time turned into shape
A pebble polished by waves is pleasurable to the hand, not only because of its soothing shape, but because it expresses the slow process of its formation; a perfect pebble on the palm materializes duration, it is time turned into shape.
Authentic architectural experiences
Authentic architectural experiences consist of approaching or confronting a building, rather than the formal apprehension of a facade; of the act of entering, and not simply the visual design of the door; of looking in or out through a window, rather than the window itself as a material object; or of occupying the sphere of warmth, rather than the fireplace as an object of visual design.
Architectural space is lived space rather than physical space, and lived space always transcends geometry and measurability.
From body to body
During the design process, the architect gradually internalizes the landscape, the entire context, and the functional requirements as well as his/her conceived building: movement, balance and scale are felt unconsciously through the body of the observer, the experience mirrors the bodily sensations of the maker. Consequently, architecture is communication from the body of the architect directly to the body of the person who encounters the work, perhaps centuries later.