Posts Tagged simplicity

how important is prioritization?

Mark Pincus, Zynga;

One of the most important things a manager can do on weekly basis is ruthlessly focus on prioritization. There’s never any lack of good ideas. Every team has 10 great ideas they’re really excited about. The problem is picking which of the 2 or 3 to focus on.

The lesson we get over and over again is a small number of features really connect with the users and get explosive results. You actually have diminishing returns with more features. When you’re picking the right features to go deep on, the user starts to have this trust and expectation that the next thing you bring out is going to be great.

No matter how big or how small your company is, you are always resource constrained. If you talk to Microsoft, or Google, or Yahoo–the biggest companies with the most engineers–every product manager will say they’re resource constrained. If they just could have twice the people, they could get everything done. No matter where you are, you have to be ruthless about how you’re using people. “

http://www.fastcompany.com/1698265/mark-pincus-zynga-farmville-mafia-wars

Leave a Comment

complexity kills

Complexity kills. Complexity sucks the life out of users, developers and IT.  Complexity makes products difficult to plan, build, test and use.  Complexity introduces security challenges.  Complexity causes administrator frustration.

And as time goes on and as software products mature – even with the best of intent – complexity is inescapable.”

Ray Ozzie, dawn of a new day

http://ozzie.net/docs/dawn-of-a-new-day/

Leave a Comment

it is your duty to ask simple questions

why

“We get seduced by the complicated in Western society,” Ms. Zimmerman says. “We’re in awe of it and we pull away from the duty to ask simple questions, which we do whenever we deal with matters that are complex.”

http://www.nytimes.com/2010/05/02/weekinreview/02segal.html?_r=1

We are drawn to complexity. We fear simplicity.

In design, it is easy to slip in to adding choices, options or features.
In thought and words, we like to use long words or acronyms and jargon.
When writing we include needless words, and struggle to stick to the point.

Asking simple, direct and even ‘dumb’ questions can help you get to the heart of the matter.

omit needless words : http://genecloud.wordpress.com/2008/06/05/omit-needless-words/

simplification failure : http://genecloud.wordpress.com/2009/03/09/design-language-simplification-failure/

Leave a Comment

frugal innovation

image

Being budget minded, focused on simplicity, challenging of the design & the processes and being aware of the implications of huge market sizes. Focus on customer.

“The term is quite commonly used in countries such as India or China to describe a specific kind of innovation which takes great care to minimise costs of innovation and cost of final product.

http://elearning.heacademy.ac.uk/wiki/index.php/Frugal_innovation

“Frugal innovation is not just about redesigning products; it involves rethinking entire production processes and business models. Companies need to squeeze costs so they can reach more customers, and accept thin profit margins to gain volume. Three ways of reducing costs are proving particularly successful.”

  • Contract out more work
  • Use existing technology in imaginative ways
  • Apply mass-production technique in new and unexpected areas

The Economist’s special report on innovation in emerging markets http://www.economist.com/specialreports/displaystory.cfm?story_id=15879359

Jeff Bezos;

Q: The company has a reputation for frugality. Does that apply to the way you innovate?
A: I think frugality drives innovation, just like other constraints do. One of the only ways to get out of a tight box is to invent your way out. When we were [first] trying to acquire customers, we didn’t have money to spend on ad budgets. So we created the associates program, [which lets] any Web site link to us, and we give them a revenue share. We invented one-click shopping so we could make check-out faster. Those things didn’t require big budgets. They required thoughtfulness and focus on the customer.

http://www.businessweek.com/magazine/content/08_17/b4081064880218.htm

Leave a Comment

are your eyes bigger than your belly?

eye belly

So much time and energy goes in to designing, implementing, testing and releasing software features that only a minority of people use.

“Only 20% of a mobile phone’s features are used regularly; up to a quarter remain completely undiscovered”

from a study by WDSGlobal

1 billion apps downloaded from the App Store, yet most go used or unexplored. Our appetite is there, and for whatever reason our hunger fades quickly.

“Pinch Media drawing on iPhone analytics data highlights that (only) ~20% of user’s ever return to use an application the day after it is installed. There are many ways to interpret this data: the harshest being that ~80% of user’s are so unimpressed with their application that they never return to it.”

http://www.janchipchase.com/blog/archives/2009/04/1000000000-apps-pfft.html

In some cases breadth of function is important, although no excuse for complexity.

“A lot of software developers are seduced by the old "80/20" rule. It seems to make a lot of sense: 80% of the people use 20% of the features. So you convince yourself that you only need to implement 20% of the features, and you can still sell 80% as many copies.

Unfortunately, it’s never the same 20%. Everybody uses a different set of features.”

http://www.joelonsoftware.com/articles/fog0000000020.html

Is featuritis driven by fear?

“Fear of being perceived as having fewer features than your competitors. Fear that you won’t be viewed as complete. Fear that people are making purchase decisions off of a checklist, and that he who has the most features wins (or at the least, that he who has the fewest features definitely loses). Fear of losing key clients who say, "If you don’t add THIS… I’ll have to go elsewhere."

Be brave. And besides, continuing to pile on new features eventually leads to an endless downhill slide toward poor usability and maintenance. A negative spiral of incremental improvements. Fighting and clawing for market share by competing solely on features is an unhealthy, unsustainable, and unfun way to live.

Be the "I Rule" product, not the "This thing I bought does everything, but I suck!" product.”

http://headrush.typepad.com/creating_passionate_users/2005/06/featuritis_vs_t.html

Leave a Comment

productivity list

1. Do one thing at a time
2. Know the problem
3. Learn to listen
4. Learn to ask questions
5. Distinguish sense from nonsense
6. Accept change as inevitable
7. Admit mistakes
8. Say it simple
9. Be calm
10. Smile

http://www.tate.org.uk/tateetc/issue8/fischliweiss_workingitout.htm

Comments (1)

have 36 ideas, keep 1 good one?

There isn’t a fixed ratio between good features or ideas and ones that need editing or dropping. The ratio is bound to be worse than you would like to think at the time of creation. If 1 in 36 photographs are worth keeping, how many ideas are worth keeping?
Omit, then submit
What you leave out is often what turns good into great. What you leave out is the difference between something that is either 1) never seen or used or 2) simple, clear, and actually digestable. It’s true for photography. It’s true for features in software. And it’s true for plenty more too.”

http://www.37signals.com/svn/posts/1228-a-361-ratio-is-actually-pretty-good

Leave a Comment

why is it hard to do just enough?

“We take on too much, because we are terrified of too little” from The Deadline by Tom DeMarco

Leave a Comment

more or less… on simplicity

“Simplicity–the art of maximizing the amount of work not done – is essential”

http://agilemanifesto.org/principles.html

Leave a Comment

perfection, when there is nothing left to take away

“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”

Antoine de Saint Exupéry

Leave a Comment

seeking simplicity

Following on from less is more;
(http://genecloud.wordpress.com/2007/01/20/less-is-more/)

Interesting snippet on simplicity from Edmon;
“The only thing you need to have in order to recognize and pursue simplicity is:

A. courage (to pursue change)
B. competence (to recognize essentials)
C. open mind (to be pragmatic)”

(http://pages.citebite.com/i1b3f3p4m4iom)

And…how to apply Judo’s principle’s of “Maximum Efficiency, Minimum Effort” to the software construction process in search of ‘doing more with less’.
(http://blogs.ittoolbox.com/eai/software/archives/software-judo-2530)

A few choice quotes;

Prof. Ludwig Wittgenstein
“The aspects of things that are most important to us are hidden because of their simplicity and familiarity.”
Hans Hofmann
“The ability to simplify means to eliminate the unnecessary so that the necessary may speak.”
Albert Einstein
“Everything should be made as simple as possible, but not simpler.”
Charles Mingus
“Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that’s creativity.”

(http://www.heartquotes.net/Simplicity.html)

John Maeda’s Laws of Simplicity
(http://lawsofsimplicity.com/category/laws?order=ASC)

Comments (2)

less is more

simple-logo.png
As a rules-of-thumb, ‘less is more’ is easy to remember and can help constrain over gilding & extravagance in design. As an absolute statement it is not always appropriate, when designing for ‘enthusiasts’, detail and depth are essential parts of a design.

“Less isn’t more, just enough is more”
(http://citebite.com/o7o0o9r3pljr)

‘Just enough is more’, works as it implies a relative measure. ‘Just enough’, as appropriate for the audience, players or customers.
Focus on the ‘just enough’ 20%.

Interesting article on “Why Simple is Complicated“, covering feature comparisons & what drives people to buy more complex products.

Comments (2)

Follow

Get every new post delivered to your Inbox.