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.
Contrasting Concepts of Harmony in Architecture
The realm of feeling
Alexander: If you say: "Well, look, you're a feeling type, and I'm a thinking type, so let's not discuss that because we are always going to be on different sides", then it removes from this discussion what I feel to be the absolute heart and soul of the matter when it comes to buildings. Now I don't want to deny at all what you are saying about personalities. But I really cannot conceive of a properly formed attitude towards buildings, as an artist or a builder, or in any way, if it doesn't ultimately confront the fact that buildings work in the realm of feeling.
Panic
Alexander: It never occurred to me that someone could so explicitly reject the core experience of something like Chartres. It's very interesting to have this conversation. If this weren't a public situation, I'd be tempted to get into this on a psychiatric level. I'm actually quite serious about this. What I'm saying is that I understand how one could be very panicked by these kinds of feelings. Actually, it's been my impression that a large part of the history of modern architecture has been a kind of panicked withdrawal from these kinds of feelings, which have governed the formation of buildings over the last 2000 years or so.
Why that panicked withdrawal occurred, I'm still trying to find out. It's not clear to me. But I've never heard somebody say, until a few moments ago, someone say explicitly: "Yes, I find that stuff freaky. I don't like to deal with feelings. I like to deal with ideas.”
The pitched roof
Eisenman: I would argue that the pitched roof is – as Gaston Bachelard points out – one of the essential characteristics of "houseness". It was the extension of the vertebrate structure which sheltered and enclosed man. Michel Foucault has said that when man began to study man in the 19th century, there was a displacement of man from the center. The representation of the fact that man was no longer the center of the world, no longer the arbiter, and, therefore, no longer controlling artifacts, was reflected in a change from the vertebrate-center type of structure to the center-as-void.
The trick of little machines
Alexander: Up until about 1600, most of the world views that existed in different cultures did see man and the universe as more or less intertwined and inseparable ... either through the medium of what they called God or in some other way. But all that was understood. The particular intellectual game that led us to discover all the wonders of science forced us to abandon temporarily that idea. In other words, in order to do physics, to do biology, we were actually taught to pretend that things were like little machines because only then could you tinker with them and find out what makes them tick. That's all fine. It was a tremendous endeavor, and it paid off.
But it may have been factually wrong. That is, the constitution of the universe may be such that the human self and the substance that things made out of, the spatial matter or whatever you call it, are much more inextricably related than we realized. Now, I am not talking about some kind of aboriginal primitivism. I am saying that it may actually be a matter of fact that those things are more related than we realize. And that we have been trained to play a trick on ourselves for the last 300 years in order to discover certain things. Now, if that's true – there are plenty of people in the world who are beginning to say it is, by the way, certainly in physics and other related subjects – then my own contribution to that line of thought has to do with these structures of sameness that I have been talking about.
In other words, the order I was sketching out last night is ultimately, fundamentally an order produced by centers or wholes which are reinforcing each other and creating each other. Now, if all of that is so, then the pitched roof would simply come about as a consequence of all that – not as an antecedent. It would turn out that, in circumstances where one is putting a roof on a building, in the absence of other very strong forces that are forcing you to do something different, that is the most natural and simple roof to do. And, therefore, that kind of order would tend to reappear – of course, in a completely different, modern technological style – simply because that is the nature of order, not because of a romantic harkening back to past years.
Merely a building
Eisenman: Le Corbusier once defined architecture as having to do with a window which is either too large or too small, but never the right size. Once it was the right size it was no longer functioning. When it is the right size, that building is merely a building. The only way in the presence of architecture that is that feeling, that need for something other, when the window was either too large or too small.
Fucking up the world
City Hall by Rafael Moneo, Logroño, La Rioja, Spain.
Alexander : At least my experience tells me, that when a group of different people set out to try and find out what is harmonious, what feels most comfortable in such and such a situation, their opinions about it will tend to converge, if they are mocking up full-scale, real stuff. Of course, if they're making sketches or throwing out ideas, they won't agree. But if you start making the real thing, one tends to reach agreement. My only concern is to produce that kind of harmony.
The thing that strikes me about your friend's building – if I understood you correctly – is that somehow in some intentional way it is not harmonious. That is, Moneo intentionally wants to produce an effect of disharmony. Maybe even of incongruity.
Eisenman: That is correct.
Eisenman: I find that incomprehensible. I find it very irresponsible. I find it nutty. I feel sorry for the man. I also feel incredibly angry because he is fucking up the world.
A good table
Eisenman: Tolstoy wrote about the man who had so many modern conveniences in Russia that when he was adjusting the chair and the furniture, etc., that he was so comfortable and so nice and so pleasant that he didn't know – he lost all control of his physical and mental reality. There was nothing. What I'm suggesting is that if we make people so comfortable in these nice little structures of yours, that we might lull them into thinking that everything's all right, Jack, which it isn't. And so the role of art or architecture might be just to remind people that everything wasn't all right.
Alexander: I can't, as a maker of things, I just can't understand it. I do not have a concept of things in which I can even talk about making something in the frame of mind you are describing. I mean, to take a simple example, when I make a table I say to myself: "All right, I'm going to make a table, and I'm going to try to make a good table." And of course, then from there on I go to the ultimate resources I have and what I know, how well I can make it. But for me to then introduce some kind of little edge, which starts trying to be a literary comment, and then somehow the table is supposed to be at the same time a good table, but it also is supposed to be I don't know what; a comment on nuclear warfare, making a little joke, doing various other things... I'm practically naive; it doesn't make sense to me.