"There falls a shadow between the conception and the creation. In the annals of innovation, new ideas are only part of the equation. Execution is just as important."
T.S. Eliot quote from Walter Isaacson's biography of Steve Jobs
"There falls a shadow between the conception and the creation. In the annals of innovation, new ideas are only part of the equation. Execution is just as important."
T.S. Eliot quote from Walter Isaacson's biography of Steve Jobs
Neal Mitchell in Ideas | Permalink | Comments (0) | TrackBack (0)
|
Since Steve Jobs died, many have tried to retrospectively discover what made him successful… what were the special things he did differently than those “mere mortals” driving around in Silicon Valley in fancy cars?
One in particular concerns the “Reality Distortion Field” which apparently was his trick of getting "10 pounds of flour to fit into a 5 pound sack." In other words, to get people to do impossible things in a shorter period of time than they believed was possible.
With his passing, this super-hero skill has been built up into an almost magical power. I don’t buy the “magic” part.
Neal Mitchell in Best Practices | Permalink | Comments (2) | TrackBack (0)
|
We advise clients to refresh their schedules twice a week (at a minimum).
Often, we observe that teams only seem to look at their schedules once a week, when they do the refresh. So increasing the frequency increases the awareness of the schedule, and time in general.
Best-in-class teams do refreshes three or more times a week. The fastest teams we’ve worked with do it every day (<15 min/session). One client recently had six teams doing it twice a day on a very time senstive program.
Problem: Create a means to get across a waterway (without getting wet)
Solution: Build an un-bridge
I love the solution that RO&AD Architecten came up with (above) for the Municipality of Bergen op Zoom in the Netherlands. It is a great example of looking at the problem differently and of not using “conventional wisdom” to solve a problem. Their site is as clever as their bridge.
This “contrarian” bridge reminds me of corporate examples of technology solutions we’ve been involved with in Silicon Valley. These business and technical solutions came from people who were able to conceptualize problem/solution differently. Some organizational cultures encourage this behavior and others aggressively discourage it (knowingly and unknowingly).
Why isn’t contrarian thinking the norm?
In our experience, we’ve seen lots of bad decisions (we know in retrospect they were bad because of the measurable failure they caused later on); but at the time they were made, they were “excellent decisions” made by “subject matter experts” that could not be challenged.
So how does this happen?
Neal Mitchell in Decision Modeling, Ideas | Permalink | Comments (0) | TrackBack (0)
|
Simon Sinek’s “start with why” concept works well to describe the three elements of a decisionAccelerator model.
Sinek’s idea is that the “Why” defines the Purpose, Cause, and or Belief of what you are trying to achieve. Often we find that this is not clearly articulated or commonly understood by a group of people, yet without knowing the “why for” of something, it is very hard to define the steps to get there and it is hard to motivate people to extraordinary performance. We all need to know why we are doing something; just knowing what we are doing and how it is done is not enough.
Often we see clients focused on the HOW (i.e. the technical solutions), yet they have not reachded consensus about WHY they are doing it and WHAT they must accomplish through the technical solution options (or the HOWs). The models are simple, the group thought process is the value.
So lets look at this idea as it is applied to a decision model (below). The Goal statement is why we are doing it, the Objectives outline what we want to achieve, and the Alternatives are how we’re going to accomplish the Objectives.
Neal Mitchell in Decision Modeling | Permalink | Comments (0) | TrackBack (0)
|
Five important best practice "speed" concepts include:
Let's discuss in more detail...
Neal Mitchell in Best Practices | Permalink | Comments (0) | TrackBack (0)
|
I’d argue “no” for the most part, but there are exceptions. Let me defend this unconventional “opinion.”
Refresh Planning... The weekly rhythm of refreshes is what makes them work. Team members know they are accountable to their colleagues every week at a set time. It can’t move and it can’t be postponed. And doing them more than once a week is even better, but they must be short and crisp value-added events.
The rhythm is what makes it work. It is the first regular discipline that most teams experience and it is the start of gaining control over the schedule. Late, postponed, missed meetings never help a project finish faster.
I’ll review the concepts underlying our Acceleration Workshop in this screencast.
We’ve successfully used this process to “discover” strategic schedule pull-in opportunities on complex projects. By “strategic” I mean large schedule acceleration opportunities, for example in one recent case… a 6-month pull-in on a 20 month program by using this team engagement approach. The trick is to harness the collective intelligence of a group of people in order to get them to “innovate” on the schedule, in the same way they “innovate” to create technology.
Recently, we were asked by a client to define the factors that determine the duration needed to create sustainable change.
The key is to jolt the system, transfer, and exit rapidly. We know that any sustainable change must come from within the organization and can't be forced from the outsitde. We also know from experience that we have to place enough external pressure, for a sustain period of time, in order to change behavior patterns. We've learned that it is essential to leave behind the capability for continuous improvement.
The factors that contribute to becoming autonomous include:
More on this topic at my Sustainable Change post.
Neal Mitchell in Organization | Permalink | Comments (0) | TrackBack (0)
|