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 Elements of Typographic Style
Leave the road when you wish
The subject of this book is not typographic solitude, but the old, well-traveled roads at the core of the tradition: paths that each of us is free to follow or not, and to enter and leave when we choose – if only we know the paths are there and have a sense of where they lead. That freedom is denied us if the tradition is concealed or left for dead. Originality is everywhere, but much originality is blocked if the way back to earlier discoveries is cut or overgrown.
If you use this book as a guide, by all means leave the road when you wish. That is precisely the use of a road: to reach individually chosen points of departure. By all means break the rules, and break them beautifully, deliberately and well. That is one of the ends for which they exist.
Typography exists to honor content
In a world rife with unsolicited messages, typography must often draw attention to itself before it will be read. Yet in order to be read, it must relinquish the attention it has drawn. Typography with anything to say therefore aspired to a kind of statuesque transparency. Its other traditional goal is durability: not immunity to change, but a clear superiority to fashion. Typography at its best is a visual form of language linking timelessness and time.
Typographic style
Literary style, says Walter Benjamin, “is the power to move freely in the length and breadth of linguistic thinking without slipping into banality.” Typographic style, in this large and intelligence sense of the word, does not mean any particular style – my style or your style, or Neoclassical or Baroque style – but the power to move freely through the whole domain of typography, and to function at every step in a way that is graceful and vital instead of banal.
A state of energetic repose
Read the text before designing it.
Discover the outer logic of the typography in the inner logic of the text.
Make the visible relationship between the text and other elements (photographs, captions, tables, diagrams, notes) a reflection of their real relationship.
Give full typographic attention even to incidental details.
Invite the reader into the text.
Reveal the tenor and meaning of the text.
Clarify the structure and the order of the text.
Link the text with other existing elements.Induce a state of energetic repose, which is the ideal condition for reading.
Evenness of color
The density of texture in a written or typeset page is called its color.
Once the demands of legibility and logical order are satisfied, evenness of color is the typographer’s normal aim. And color in the typographic sense depends upon four things: the design of the type, the spacing between the letters, the spacing between the words, and the spacing between the lines. None is independent of the others.
A single note
The simplest scale is a single note, and sticking with a single note draws more attention to the other parameters, such as rhythm and inflection. The early Renaissance typographers set each book in a single font – that is, one face in one size. Their pages show what sensuous evenness of texture and variety of rhythm can be attained with a single font of type.
The higher courts
Refer typographic disputes to the higher courts of speech and thinking.
Type is idealized writing, and its normal function is to record idealized speech. Acronyms such as CD and TV or USA and UFO are set in caps because that is the way we pronounce them. Acronyms such as UNESCO, ASCII, and FORTRAN, which are pronounced not as letters but as words, are in the process of becoming precisely that. When a writer accepts them fully into her speech and urges readers to do likewise, it is time for the typographer to accept them into the common speech of typography by setting them in lower case. Other acronymic words, such as laser and radar, have long since traveled the same road.
An antiphonal geometry
A book is a flexible mirror of the mind and body. Its overall size and proportions, the color and texture of the paper, the sound it makes as the pages turn, and the smell of the paper, adhesive and ink, all blend with the size and form and placement of the type to reveal a little about the world in which it was made. If the book appears to be only a paper machine, produced at their own convenience by other machines, only machines will want to read it.
Sizing and spacing type, like composing and performing music or applying paint to canvas, is largely concerned with intervals and differences.
The page is a piece of paper. It is also a visible and tangible proportion, silently sounding the thoroughbass of the book. On it lies the textblock, which much answer to the page. The two together – page and textblock – produce an antiphonal geometry. That geometry alone can bond the reader to the book. Or conversely, it can put the reader to sleep, or put the reader’s nerves on edge, or drive the reader away.
Pure but silent
Architects build perfectly proportioned kitchens, living rooms and bedrooms in which their clients will make, among other things, a mess. Typographers likewise build perfectly proportioned pages, then distort them on demand. The text takes precedence over the purity of the design, and the typographic texture of the text takes precedence over the absolute proportions of the pure but silent page.
A sterile sameness
Another kind of random variation involves the interaction of the craftsman’s skill and the texture of materials. The letterforms of Griffo and Colines were cut with immense care. But the letters they cut were struck by hand in copper or brass, then cast and dressed and set by hand, inked by hand with handmade ink and printed by hand in a handmade wooden press on handmade paper. Every step along with way introduced small variations planned by no one. In the world of the finely honed machine, those human-scale textures are erased. A sterile sameness supervenes.
The computer is, on the face of it, an ideal device for reviving the old luxury of random variations at the threshold of perception (quite a different thing from chaos). But conventional typesetting software and hardware focuses instead on the unsustainable ideal of absolute control – and has been hamstrung in the past by the idea of a single glyph per character. There have been several recent attempts to introduce a layer of random variation, but all have had to work against the grain of technological development.
Waiting to repay the gift of vision
Like a forest or a garden or a field, an honest page of letters can absorb – and will repay – all the attention it is given. Much type now, however, is delivered to computer screens. It is a good deal harder to make text truly legible on screen than to render streaming video. Both fine technology and great restraint are required to make the screen as restful to the eyes as ordinary paper.
The underlying problem is that the screen mimics the sky instead of the earth. It bombards the eye with light instead of waiting to repay the gift of vision – like the petals of a flower, or the face of a thinking animal, or a well-made typographic page. And we read the screen the way we read the sky: in quick sweeps, guessing at the weather from the changing shapes of clouds, or in magnified small bits, like astronomers studying details. We look to it for clues and revelations more than wisdom. This makes it an attractive place for the open storage of pulverized information – names, dates, or library call numbers, for instance – but not so good a place for thoughtful text.
Respect
Respect the text first of all, the letterforms second, the type designer third, the foundry fourth.
The needs of the text should take precedence over the layout of the font, the integrity of the letterforms over the ego of the designer, the artistic sensibility of the designer over the foundry’s desire for profit, and the founder’s craft over a good deal else.
Little by little
Check every text you set to see where improvements can be made. Then return to the font and make them. Little by little, you and the instrument – the font, that is – will fuse, and the type you set will start to sing. Remember, though, this process never ends. There is no such thing as the perfect font.
An end in itself
Typography, like language, is more important to me for what it allows to happen than for anything it accomplishes on its own. I hope that in writing a book on the subject I have not given the impression that either typography or design is an end in itself.
Not as a star
But I’m warning you,
this is my last existence.
Not as a swallow, not as a maple,
not as a cat-tail and not as a star.