Tag Archives: iteration

Podcast: Building Organizational Capability

The Software Process and Measurement Cast 420 features an interview with me, by Thomas Cagley, on Building Organizational Capability (download podcast).

John Hunter in the podcast:

Changing how organizations are managed makes a huge difference in people’s lives, not all the time and I understand most of the time it doesn’t. But when this is done well people can go from dreading going to work to enjoying going to work, not every single day – but most days, and it can change our lives so that most of the time we are doing things that we find valuable and we enjoy instead of just going to work to get a paycheck so we can enjoy the hours that we have away from work.

photo of John Hunter

John Hunter, Zion National Park, Utah, USA

Here are some links where I go into more detail on some of the topics I discuss in the podcast:

Thomas Cagley: If you have the power to change any 2 things that affect decision making what would they be and why?

John Hunter:

First that results are evaluated. Make decisions then evaluate what actually happens based upon what you do. Learn from that, improve how you make future decisions and keep iterating.

That idea of evaluating what actually happens is extremely powerful and will reinforce going in the right direction because if you evaluate most decisions many organizations make nothing got any better. And after doing that many times you can learn this isn’t working, we need to do something better.

And the second would be more prioritization. Make fewer decisions but take more time to make those decisions, implement those decisions, evaluate those decisions, learn from those results and iterate again.

I hope you enjoy the podcast.

Related: Software Process and Measurement Podcast With John Hunter on my book Management MattersDeming and Software Development

Google: Experiment Quickly and Often

Google Thinks Small by Quentin Hardy, Forbes:

Brin and Page have created a corporate organism that tackles most big projects in small, tightly focused teams, setting them up in an instant and breaking them down weeks later without remorse. “Their view is that there is much greater progress if you have many small teams going out at once,” Schmidt says. The mission overall: to collect “all the world’s information” and make it accessible to everyone. “It’s a cause.”

Hundreds of projects go on at the same time. Most teams throw out new software in six weeks or less and look at how users respond hours later.

Google has advantages in making this work for them (it is easy to find reasons it won’t work elsewhere). However, this is basically piloting changes on a small scale, analyzing the results and repeating that quickly. Quick, frequent experimentation with iteration is a tactic all organizations would benefit from.

The clear visible mission is also helpful. When an organization has an organizing principle everyone can understand then action can be guided by individual aim toward that purpose. When the understanding is missing organizations often have to rely on top down instruction and having far too many issues passed up the hierarchy for a decision.

And getting a small group of people to make things work quickly is also great. Many organizations get bogged down with byzantine management structures that slow action to a crawl.