Skip to main content

What's new with your User Experience?

I was sitting with some colleagues at the pub the other night, talking about one of my favorite subjects - Apple computer's highly innovate nature.  One person reflected that the one thing that made the iPhone successful was the touch screen.  That other devices had used a touch screen, but had not gotten in quite right.  Other devices that were using touch screens were clunky to use. He had apparently used several different devices with touch interfaces.  A benefit of the company he works for that has a loner program (want to try their software on a mobile device - borrow it for a few weeks).  I chatted with the person that runs the program, they have all the new toys and every week its like Christmas morning opening new packages.  What a brilliant program.

Yes, I'd have to agree that one of the keys to the iPhone's success is the new user experience it allows.  Along with the wonderful opportunity for people (mere babes) to use a computer with absolutely no instruction at all.  Countless people tell stories of their 2 and 3 year-olds using iPhones to navigate to their favorite applications.

I remember when Apple introduced the paradigm shifting mouse in 1984.  I taught a summer school program where 6th & 7th graders could learn to program (BASIC) with the Apple II Plus computer.  One half of the first day was teaching students to use the mouse.  The kids got it much quicker than the older teachers.  However I still spent hours teaching the user interface techniques of a mouse.  Can you imagine teaching someone the techniques of mousing?  Break it down - learn to point, to click, the timing of a double click, the advanced drag and drop.  With a touch interface this is needless.  We have been using a finger to point and touch since we've been 6 months old - it is natural.

I gave my mother a used first generation iPhone, no manual, no instructions, just sent it via mail in a box.  Now my Dad said she's just as bad as the young kids, constantly on the internet, reading, watching TV, multitasking and googling things in real time.  She's a Digital Immigrant.

My father never wanted to use a computer.  He said he would use one when he could just talk to it and it would type his reports and papers as well as his secretary.  Yes he worked back in the days when even middle managers had secretaries and typing pools. This didn't keep him from enrolling me into the 9th grade typing class.  I was one of only two boys in a 40 girl class for beginning typing.

My father foresaw the power of typing and of computers.  I was in typing class because he had so much stress working on his master's dissertation and computer classes he had to take in the 1970s.  In 1976 he was sure typing would be a skill I would need in life.  In 1979 he brought home an Apple II computer to see if it would interest my brother and me.  It did, I learned BASIC programming.  Then he bought the first personal computers (Apple II Plus) for students in the Stanley county school systems.

So learning new computer user interface has been in my family for years.  First user interface we learned, typing (1976), then mousing (1984), then touch interfaces (2007) with the iOS products, next....  voice.  My father's vision is happening.  My father-in-law uses Naunce's Naturally Speaking on the Mac to write proposals and email today.  My wife uses Naunce's Dragon in preference to typing. In the near future this may become the primary user interface.

This change in user interface will require changing your software application.  How close to the bleeding edge is your software application interface?  Are you planning for the future?  My family is willing to test it for you.  We are experts, including the 2 year old niece.
Post a Comment

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.


Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

What is your Engagement Model?

What must an Agile Transformation initiative have to be reasonably assured of success?

We "change agents" or Agilist, or Organizational Development peeps, or Trouble Makers, or Agile Coaches have been at this for nearly two decades now... one would think we have some idea of the prerequisites for one of these Transformations to actually occur.  Wonder if eight Agile Coaches in a group could come up with ONE list of necessary and sufficient conditions - an interesting experiment.  Will that list contain an "engagement model"?  I venture to assert that it will not.  When asked very few Agile Coaches, thought leaders, and change agents mention much about employee engagement in their plans, models, and "frameworks".  Stop and ask yourselves ... why?

Now good Organizational Development peeps know this is crucial, so I purposely omitted them from that list to query.

One, central very important aspect of your Agile Transformation will be your Engagement model.  

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?

Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.

Metrics for a Scrum Team (examples)

What metrics do you collect to analyze your scrum team?

We live in a world of data and information.  Some people have a mindset that numbers will diagnose all problems – “just show me the data.”  Therefore many directors and senior managers wish to see some list of metrics that should indicate the productivity and efficiency of the Scrum team.  I personally believe this is something that can be felt, that human intuition is much better in this decision realm than the data that can be collected.  However, one would have to actually spend time and carefully observe the team in action to get this powerful connection to the energy in a high-performing team space.  Few leaders are willing to take this time, they delegate this information synthesis task to managers via the typical report/dashboard request.  Therefore we are asked to collect data, to condense this data into information, all while ignoring the intangible obvious signals (read Honest Signals by Sandy Pentland of MIT).
What if …