2011: Another big year

Some highlights (the work-related ones anyway):

  • Feb: Set up Positive Incline Limited
  • Feb: Kanban Leadership Workshop (aka Kanban Coaching Workshop) with David Anderson in London
  • Mar-Sep: Continued part-time dev management role in Budapest, Hungary (and a big thank you to my former colleagues at Encore International, now part of M&C Energy Group)
  • Mar-May: Kanban consultancy in Johannesburg, South Africa as a DJA&A associate
  • Jun: The Kanban Leadership Retreat in Reykjavic, Iceland (#klris)
  • Oct-Nov: The Lean/Kanban conferences in Antwerp and Munich and the LESS conference in Stockholm (#lkbe11, #lkce11 and #less2011 respectively)
  • Nov: Speaking to my local (Matlock) business networking group about Kanban. Not just for techies! (#MBCnetworking)
  • Dec: Joined DJA&A full-time (more on that next year)
  • Dec: Leading my first 2-day DJA&A Kanban class in London

Top posts of 2011:

Older posts still going strong:

Real Kanban Questions #3: What makes for a good improvement?

Or, given a proposal for change, how do I know it’s a good one?

Dangerous answer: “Because it has a good ROI”

Too often, ROI is used as a tool to justifying changes of questionable benefit. Grandiose schemes, off-the-shelf solutions, restructurings, divestments – we’ve all seen them. It’s not always terrible, but we can do better!

A better answer: “Faster, better, cheaper – pick three”

Changes that promote early feedback tend to improve both speed and quality, but cheaper? Don’t overlook the biggest cost of all, namely opportunity cost – another way of saying that overall benefit to the business must be a primary concern. And if the economics still don’t work, keep trying! Perhaps you can implement your change incrementally, working on the next small change as the previous one proves itself and the system adjusts to a “new normal”.

To see this in action, a couple of real examples:

  1. The sign-off that takes weeks of chasing to complete, never yielding any benefit in quality. Better? That was the intention, sadly not realised in practice, a situation tolerated for years. Faster? Quite the opposite. Cheaper? Again no.
  2. The deployment scripts that take not just “20% time” but hard, scheduled effort to develop. Yes there’s a cost, but the value of being able to deploy quickly, reliably and (let’s say) opportunistically is very significant. Faster? Definitely. Better? Check. Cheaper? Absolutely!

Even better than “pick three” is “pick four!”, where the fourth element is a compass check, looking for alignment to wider vision, goals, or values. Good values make for quick tests: the first example above might have been rejected on the grounds that was likely to add complexity, discourage collaboration and disperse accountability.

What’s your experience? Do you live in a world of ROI-driven change, and what is that like? Is your team good at finding improvements that make your process better, faster and cheaper? What happens when change is in conflict with wider concerns? Are those values made explicit?

Real Kanban Questions #1: How do we know that the things we are working on are the most valuable?

That’s partly a question of perspective.  How is the input queue replenished?  Is the team deciding for itself and worrying about whether they’re doing it optimally, or perhaps having work selected for them and worrying that they’re having their time wasted?

One very cool but rarely discussed effect of limiting work in progress (WIP) with Kanban is that it pushes choice back upstream.  Or to put this the other way round: too much WIP and the prioritisation and risk management problem is sucked into the development team.  Horrible!  Better to keep it where it belongs: in a partnership between the team and its key stakeholders. Getting this right goes a long way towards neutralising the value question; difficulty here likely reflects broader problems in the organisation.

Ultimately, only time will tell how valuable the work will turn out to be.  Collaborate, be transparent about the decisions you make and how you make them, keep feedback cycles short. For maximum effectiveness in the short run, reframe the question from “how valuable?” to “what will we learn?” and refocus the work accordingly.  If value is hard to measure and still harder to predict, you can at least learn to test your assumptions quickly!

Finally (and partly as a warning against getting hung up on the value question), remember that winning in long run depends on maintaining a healthy level of investment in capability-building work, alongside the more obviously urgent value-driven stuff.  The alternative is to risk being left behind, and you need no ROI calculation to tell you how bad that would be!

[While we're here, not long now until my Kanban class in London, 5th-6th December 2011. Info here, registration here.  Don't miss it!]

Lean reading marathon

I have just finished reading these five books in quick succession:


The Leader’s Guide to Radical Management
: Reinventing the Workplace for the 21st Century by Stephen Denning


The New Economics
for Industry, Government, Education by W Edwards Deming


Toyota Production System
: Beyond Large-scale Production by Taiichi Ohno


Toyota Kata
: Managing People for Improvement, Adaptiveness and Superior Results by Mike Rother


The Lean Startup
: How Constant Innovation Creates Radically Successful Businesses by Eric Ries

The Denning book has a very interesting take on old and new models of business leadership, with lessons that business can draw from the Agile and Lean development communities.  A good and interesting read but a couple of nits to pick:
1) Scrum receives special attention but without any real analysis of why (or why not)
2) With 70+ recommendations it was easy to lose track of the underlying principles

I would have left Steve Denning there, but he came to LESS 2011 in Stockholm this month, giving an excellent keynote and holding a Birds-of-a-Feather (BoF) session on leadership storytelling. I was greatly impressed by both, two of the best sessions of the whole conference. His book The Leader’s Guide to Storytelling: Mastering the Art and Discipline of Business Narrative is now on my reading wishlist.

I approached Deming and Ohno together as an exercise in going back to original sources – both books must surely be required reading for anyone interested in Lean, even if only as historical reference points.  I was however very struck by the timeliness of the Deming book nearly 20 years after publication and appreciated his warnings against the dangers of “tampering” (a word he uses with some precision) with systems that are prone to random variation.  The Ohno book gave great insight into the origins, influences and historical context of the Toyota Production System, and most especially the exceptional determination and clarity of vision with which Ohno and his mentors applied themselves.  My lasting impressions from this pair of books aren’t so much technical but the feeling that I have encountered some remarkable people.

Mike Rother’s Toyota Kata is my book of the year. I could only read it slowly, finding myself at regular intervals putting the book down to think!  It fills a big gap in Lean literature, explaining the Toyota Production System not as something fixed but as the result of decades of ongoing work, that work being the expression of a uniquely self-sustaining and self-renewing approach to management and leadership.  I wonder if there is an organisation outside the armed services that does this quite so systematically and thoughtfully?  There are lessons we can take away on making transformations endure, but still must be admitted that not many organisations have Toyota’s staying power. That’s a humbling thought.

Taking Ohno and Rother together, it seems clear that Toyota’s approach to improvement relies less on good tools or the employee suggestion box but rather on working towards process goals which would seem well beyond the reach of most other companies.  It is no wonder others struggle to keep up!  Continuous improvement seems such an easy thing, but it is no easy option when you are led with focus and determination, guided by a “True North” to which few would dare aspire.

Last but not least, Eric Ries’s Lean Startup book.  My expectations were driven downwards by the Twitter hype surrounding this book, but I was wrong to be so cautious!  There is real depth here, surprising insights right to the last chapter.  In particular, the “validated learning” concept seems set to be regarded as one of those oh-so-simple but elegant and language-changing ideas. It resolves so many of those frustrating loose ends that get argued about endlessly in Agile and Lean circles, such as the “why” of development work, the meaning of “done” and the appropriateness of metrics.  Now we have new and powerful ways to talk about the values, economics and direction of Lean development that sit very well with Kanban.

So, quite a marathon, but what a great investment!

Upcoming

A busy few weeks ahead:

  1. Sept 21: Limited WIP Society Manchester, Manchester, England
  2. Sept 29-30: Pre-conference Kanban tutorial at Agile Cambridge, Cambridge, England
  3. Oct 3-4: Lean & Kanban Benelux (LKBE 2011), Stuurboord, Antwerp, Belgium
  4. Oct 17-19: Lean & Kanban Central Europe (LKCE 2011), Munich, Germany
  5. Oct 30-Nov 2: Conference on Lean Enterprise Software and Systems (LESS 2011), Stockholm, Sweden

I have good reason reason to be excited about all of these:

Manchester is the closest big city to my home since I moved away from London in 2009; props to Ian for getting this meetup up and running.  While we here, I must mention Zsolt and the Budapest meetup that I attended this week.

The Kanban tutorial in Cambridge with David Anderson kick-starts what we hope will be become a regular training offering in the UK.  And yes, I’m an associate, currently the only one based in the UK.

I look forward to LKBE and LKCE not just as speaking opportunities but as the chance to catch up with some of the people who have challenged and inspired my thinking over the past couple of years.

LESS is where we reach out and learn from other communities and disciplines.  And I can’t wait to return to Sweden – I just wish I had held on to more of my childhood Swedish!

Anyway… I hope to see you at one or more of these great events.  Look me up!