Purposeful Simplicity, Unthoughtful Complexity

complexity, fractal, simplicityMost people or organizations do not, by design, create a product or service with the goal of “making the most complex product that nobody can use”.  In other words, rarely do we see purposeful complexity but instead we see much unthoughtful complexity.

i am going to create the most complex product or service and nobody will be able to use it!  i’ll make sure that after my customers experience my product or service, that they feel deflated & completely unsuccessful.

On the other hand, people and organizations that make it a goal towards simplicity and ease-of-use, actually make a very, very concerted effort — in other words, purposeful simplicity.

So, if great effort is required to achieve simplicity and almost no effort is needed to achieve complexity, why is there so much complexity in our products and services?  Why do so many of us feel stupid, dumb, and that it’s our fault after experiencing a product or service?

I believe the answer is simple:

lack of reflection and concern for the customer

Simplicity and Complexity need each other — @johnmaeda teaches this to us; I grant that some processes and products require complexity, but I argue that most complexity is achieved because of unthoughtful concern for the customer.

Here are some questions that can serve as anchors and keep us grounded to the customer experience:

  1. how will the customer feel after she experiences my product or service? (ala diego)
  2. what will the customer remember after they experience my product or service?
  3. why are they using my product or service?  how many steps does it take?
  4. could i make things simpler for my customer?
  5. if the customer were in my shoes, what would she do?
  6. if a 12 year old were in my shoes, what would he do?
  7. if my 72 year old filipino, immigrant, non-computer savvy mother were in my shoes, what would she do?

Stay anchored; Stay grounded.  The customer writes your paycheck.  Remember who you are working for.


Short URL: http://bit.ly/4zpGp

Share This Post:



  • Digg
  • Twitter
  • Facebook
  • Google Bookmarks
  • del.icio.us
  • StumbleUpon
  • LinkedIn
  • MySpace
  • HackerNews
  • Reddit
  • Live
  • email

2-pizza teams (10)
3 C's (3)
37signals (1)
5S (38)
A3 Report (9)
adoption (7)
agile/software (59)
ajax (4)
amazon (53)
apple (3)
apple iphone (7)
axiom (3)
Aza Raskin (9)
backcountry.com (2)
berlin (1)
bill gates (1)
bill marriott (1)
blog tag (1)
book reviews (4)
bullwhip effect (5)
business (397)
business plans (3)
busm361 (13)
BzzAgent (12)
call center and queueing (11)
car buying (2)
Carbonite (1)
change management (5)
chicago (1)
click fraud (1)
click-to-ship (21)
clocky (2)
colin powell (2)
community (2)
company interviews (18)
company interviews (6)
complexity (32)
costs (8)
culture (7)
customer experience (10)
customer obsession (52)
customer recovery function (1)
customer segmentation (8)
customer service (17)
design thinking (14)
digg (4)
drum-buffer-rope (38)
dublin (1)
dynamic systems (24)
eBay (6)
economics (3)
efficiency (4)
ethnography (29)
family (18)
featuritis (15)
flexibility (1)
forecasting (2)
four performance dimensions (2)
Fun With The 2×2 Matrix (1)
game theory (7)
Gemba (67)
genchi genbutsu (68)
general (135)
germany (1)
google (15)
Gretchen Rubin (1)
heijunka (65)
holidays (1)
hoshin kanri (1)
how to be a human (1)
IDEO (2)
image uploading (1)
interviews (4)
iphone (5)
ishikawa (69)
IT at Toyota (67)
jason fried (1)
just-in-time (4)
kaizen (4)
kanban (46)
law of instinct (1)
Leadership (46)
lean (167)
Lean Consumption Maps (98)
learning curve (1)
licketyship (1)
mark cuban (1)
martin luther king (1)
mary poppendieck (1)
metrics (73)
microsoft (6)
milton friedman (1)
moving average (1)
muda (68)
nba fines (1)
net promoter score (nps) (1)
obeya (39)
Off-Topic (1)
onstar (1)
operations (108)
pageviews (3)
pareto principle (39)
patent (1)
peanut butter manifesto (2)
philosophy (3)
Poka-Yoke (6)
poppendieck (3)
powerpoint sucks (2)
private equity (4)
process measures (6)
product development (20)
productivity (4)
quality (41)
quasimodal design (1)
queueing theory (41)
Raffle (1)
rational choice (2)
regression analysis (18)
respect for people (6)
root cause analysis (60)
sarah+palin (2)
seth godin (1)
simplicity principle (10)
six sigma (128)
snowboarding (2)
social media (3)
spam (1)
statistical process control (46)
strategy (46)
suburban (1)
supply chain (24)
takt time (8)
teaching (2)
team size (9)
technology (104)
the beer distribution game (1)
The Happiness Project (1)
the profit tree (7)
The Visual Factory (11)
theory of constraints (41)
time (2)
timeline (3)
tony+hsieh (11)
toyota (75)
travel (1)
trump bankruptcy (1)
turnaround (5)
twitter (8)
uspto (1)
utah deal flow (2)
variation (69)
venture capital (1)
Visual Management (11)
waste (59)
website traffic (2)
Wing Chun (2)
wisdom of crowds (1)
wisdom teeth (1)
word-of-mouth marketing (18)
yahoo (2)
zappos.com (12)
zero defects (3)

WP Cumulus Flash tag cloud by Roy Tanck and Luke Morton requires Flash Player 9 or better.


If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.

Comments

This makes me think of all the “unthoughtful complexity” that goes into corporate mission/vision statements, marketing materials, and promotional puffery that organizations produce. They tend to be bloated, turgid, nearly incomprehensible, and absurdly complex.

blog post: Purposeful Simplicity, Unthoughtful Complexity http://tr.im/iTq9

This comment was originally posted on Twitter

Great thought, but then I’m biased! RT @shmula blog post: Purposeful Simplicity, Unthoughtful Complexity http://tr.im/iTq9

This comment was originally posted on Twitter

Nice post on building products for customers… http://tinyurl.com/cyk7lo

This comment was originally posted on Twitter

RT @ravisohal Nice post on building products for customers… http://tinyurl.com/cyk7lo

This comment was originally posted on Twitter

It’s a complicated business keeping things simple.

Most organizations do not, by design, create a product with goal “making the most complex product that nobody can use” http://is.gd/uacr

This comment was originally posted on Twitter

Nice insight, while we must solve a problem or design a system that can handle the inherent complexity contained in that problem or system ADDING complexity just complicates things.

Leave a comment

(required)

(required)


Additional comments powered by BackType