When adding features to a software product it's easy to underestimate the overall time and cost they may take up. To keep the full impact in mind it can be helpful to think of Features As Pets.

When I think of Features As Pets it helps me look past the initial cost of designing and developing a feature and consider its full lifecycle. For example:

you're going to want to tell your users about it

you'll want to check it's being used as intended

you'll need to support it and check that it works in all different places and fix it when it breaks

you may need to work hard to make sure it's compatible with new features you add

you may have to return to the code and refactor it to improve performance

you may need to upgrade libraries and maintain security patches

finally you'll have to decommission it gracefully when it's no longer needed including dealing with data you may have stored

New features are probably one of the key differentiators of your offering compared to others, but it bears a little consideration before adding something — a feature is not just for Christmas.

Features Are Like Pets is from the excellent Intercom on Product Management podcast (Apple, Spotify, ebook).

Features are like pets

Forcing functions are a super way to help make things foolproof, or better, errorproof — as all of us make mistakes with designed things without being fools. You may have used your own forcing function when, in an attempt to make sure you remember your passport or tickets before a flight, you put them directly in front of the door so you couldn’t open it without noticing them. That little dialogue that asks you if you want to save your changes before closing your work, that’s a forcing function too.

My first memory of understanding a forcing function was when working with a giant machine capable of cutting through 100 pieces of paper at a time. The two buttons to operate it were on opposite sides of the machine. I couldn’t start the machine without spreading my arms out wide. There was then no way to also accidentally have your fingers in with the paper and near the blades when it started. Smart.

I learned this sense of forcing function from Don Norman’s classic The Design of Everyday Things. Also from Don, see Mapping.

The other sense of forcing functions for productivity is also really useful: helping kick ourselves into action.

Forcing function — design

Unuseless inventions. Invented by the Japanese. Worth a quick chindogu search.

Sketchplanations tagged with product-design