Skip to main content

Luke Arm - How long between invention and innovation?

Look at the advances in less than a decade.  Here's a video from May 2016 from IEEE Spectrum.

Prosthetic Hand Restores Amputee's Sense of Touch

Luke Arm (Sept. 2009)

How long did Luke Skywalker have to wait for his prosthetic arm? Not long he was back in the action within days it seems.

I’ve been loosely following the Luke Arm - Dean Kamen’s name of the DARPA funded prosthesis. First I’m floored that in 30 months the team could create such a beautiful design (beautiful in an engineering way). The human arm (counting the hand also) has 22 degrees of freedom (DOF) (movements like forearm rotation). The traditional hook and cable prosthetic has just 3 DOF. That hook was designed in the days of sailing ships, updated with aircraft cabling to allow some movement after World War I.

The typical user gives up on the frustrating hook/cable arm after a few years. Why? Kamen’s group think it is the low return on investment (ROI) the arms provide the user. They don’t provide enough benefit (mobility, dexterity, functionality) for their cost - here cost is not money as many are provided by VA benefits - but cost in more human terms, like comfort of the device interface. Just one of the drawbacks; the socket is designed to cup the “stump” and becomes sweaty and slippery reducing functionality and decreasing comfort.

Update:  see 3D Printing a Better Socket for Prosthetic Limbs ( by David Sengeh of MIT Media Lab

Want to see the Luke arm in action? YouTube - IEEE Spectrum (video).

Now what puzzles me is that it took less that 3 years to invent the prosthetic arm but will take at least 3 years in clinical trials (FDA) if there is funding for the trials. DARPA funding does not extend into the clinical trial. But why does this device even require FDA approval and trials?

If this was a game console (Wii or Xbox) controller - like a Power Glove it would not require FDA approval. How is the Luke arm different?

Deka (Kamen’s company) received $18.1 million for a 30 month contract started in 2005, and delivered working prototypes in late 2007. A modular device weighing less that the human arm and nearly just as capable! It appears to be a wonderful invention, waiting on FDA approval to become an innovation.

What’s the difference between invention and innovation? Innovation is when that wonderful idea actually gets to usefulness in society. It is typically a 30 year process between invention and innovation. Will we have to wait another 30 years?

Ray Kurzweil has plotted the exponential curve of innovation for some well know inventions, see:  Mass use of Inventions (mass use defined as 1/4 of US population).

More info on the Luke arm and other DARPA prosthetic arm research at IEEE Spectrum.

Update: May 2014 - It appears that the DARPA project is on a fast track - it will not take 30 years.

USA FDA approves Deka to market a prosthetic arm that can perform multiple, simultaneous powered movements controlled by signals picked up from sensors on the user's arm (electromyogram or EMG).

See story and video from re/code:
FDA Approves Robotic Prosthesis Controlled by Muscle Contractions By James Temple

See Also:

Weird but related - a robotic arm that can catch random objects thrown to it.
Robotic Arm Catches Objects on the Fly

Kids Design Their Own Prosthetics 

A Budget Exoskeleton


1 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…

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, …

What belongs on the Task Board?

I wonder about these questions a lot - what types of task belong on the task board?  Does every task have to belong to a Story?  Are some tasks just too small?  Are some tasks too obvious?  Obviously some task are too larger, but when should it be decomposed?  How will we know a task is too large?

I answer these questions with a question.  What about a task board motivates us to get work done?  The answer is: T.A.S.K.S. to DONE!

Inherent in the acronym TASKS is the point of all tasks, to get to done.  That is the measure of if the task is the right size.  Does it motivate us to get the work done?  (see notes on Dan Pink's book: Drive - The surprising Truth about what motivates us) If we are forgetting to do some class of task then putting it on the board will help us remember.  If we think some small task is being done by someone else, then putting it on the board will validate that someone else is actually doing it.  If a task is obvious, then putting it on the board will take vi…

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.

In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.

Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    To Do
    Work In P…

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.