BOOK A CALL

December 11, 2017

Too much Agile Guidance for C-Suite

By Russ Lewis. Published online December 11, 2017

One key action: Agile Guidance for C-Suite leadership

If my job title was a three-letter acronym and the first letter was a “C”, I might be un-festively fed-up with people telling me how to run my agile digital transformation. Two more ‘top ten something-or other things CEOs and CIOs should worry about’ appeared last week, which according to the advice in the lists themselves, is 75% more agile guidance than anyone can manage.

Of all this recent agile guidance to C-suite, what are the three things that senior managers can actually do to improve business agility? Better than that, what’s the ONE ACTION for leaders that will guarantee a successful agile digital transformation?

Last week’s top ten lists were from the wonderful John Cutler, with 10 ways C-suite can support agility and management consulting firm McKinsey & Co with CEO guide to 10 traps to avoid for digital transformation. The latter reminded me of A leader’s guide to Agile by Santiago Comella-Dorda et al., which is not only well-researched, but contains a list of six habits leaders should emphasise. And they didn’t feel the need to change the title to ‘Top 6 habits for Agile leadership’.

Be Prepared

What strikes you first about Cutler’s list is that each item begins “Be prepared to…”, perhaps in homage to the naming of the episodes of Friends or perhaps because leaders have duties, generally, and should be prepared to be accountable for them. In Scouting for Boys, Baden-Powell explained the meaning of the Be Prepared motto as “you are always in a state of readiness in mind and body to do your duty”.

Focus – no more than three balls allowed in the air at a time

Up first is “focus and do less at once”. Cutler’s words here and you can say “be prepared to…” to yourself, are echoed in everything ever written for managers. Common sense and simple science make it plain that having too much work in progress (WIP) slows-down throughput.
The more complicated or complex the work, the greater the damage that too much WIP has on flow and quality. This is governed by Kingman’s formula, illustrated here with a doctor’s office metaphor by Gregg Gordon (we did this as an exercise in my Kanban class last week) and explained in Christoph Roser’s article on variation and lead times.

Not even Executives can Multi-Task

You wont believe me, but not even executives can multi-task – humans are wired for rapid task switching, but according to the research it always introduces defects and we do especially badly at switching between familiar and unfamiliar tasks. For example checking your phone for important emails (familiar) and listening, actively, to someone describing the project they’re involved with.
I often say to senior managers that your position gives you a view that is broader and at a higher level of abstraction than others, allowing you to see things in the bigger picture that are invisible from ‘down amongst the weeds’ where most people operate. But you have to pay extreme attention to what people are telling you if you are to hear what they’re not saying. They aren’t aware of it, you have to listen, actively, to hear it.

Purpose via Prioritisation

The great advantage of recommending focus is that to do so, you have to decide where you want to be in twelve months’ time and the strategy you will employ to get there. Richard Rumelt’s terrific book Good Strategy, Bad Strategy describes the kernel of good strategy as a governing thought that states the destination and how to remove the obstacles to get there. It is supported by (no more than) three key actions, not fifteen initiatives, not seven major programmes of change, just three outcomes that mid-level managers and teams can visualise, measure, plan and course-correct themselves to achieve.
One example of a key action chosen by a leadership team I’ve been working with was to improve transparency of WIP, so that all stakeholders could see the actual work being done by teams and measure the capacity of those teams so they could better prioritise their work requests.

Bibliography

Meyer, Evans, Rubinstein. 2001. American Psychological Association

Rumelt, Richard. 2012 Good strategy, bad strategy: the difference and why it matters. Paperback ed. London: Profile Books.
Categories: , ,
Newsletter signup

    Recent Posts

    How to restore Teams Wiki data after Jan 2024

    Microsoft killed Wiki on Teams - who knew they would delete our data too - here's how to restore it

    Read More
    Transformation research update

    'Managing Tensions not People' as transformation method research update at the end of 2023 This time last year I was searching through the ambidexterity literature for tensions other than the usual explore-exploit. I built a website to publish my progress online, which I think was a diversion! Literature research update I found more than 70 […]

    Read More
    The HOW of Transformation

    The HOW of Transformation recorded at the Global Digital Transformation Summit in Berlin 2023 Summary Managers who manage tensions enjoy greater performance, especially in complex and dynamic environments. In this 36-minute talk: I tell the story of Transport for London's transformation from a one-sided fares Operator to an integrated Developer-Operator. And show how technologists using […]

    Read More
    In praise of rights licensing bots

    I was at the digital transformation summit in Berlin last week when I got a scary "unlicensed use" email from a rights licensing lawyer. The rights licensing bot service sent me a screenshot of the page and the cartoon I was alleged to have used. I say alleged because I didn't recognise the cartoon or […]

    Read More
    Ways of Working: 5 improvements for leaders

    Most ways of working still rely on functional hierarchy, where managers make decisions and workers do the work. Managers know they can't change this work structure, but they can transform its effectiveness without asking for permission and without needing a budget. Before exploring the changes that transform the way people work, we need to recognise […]

    Read More
    Manage tensions if you want an agile transformation

    Today’s challenge is that traditional management approaches, where managers tell people what to do and how to do it, are not as effective as they once were. Agile transformation takes years, but changing management’s focus from people to tensions could be a better solution. It is simpler, faster, and considerably more cost-effective. Management is the […]

    Read More
    October 6, 2021
    What does focussing on culture mean to XYZ Consulting?

    We have some mid-tier consultants in at the moment who are "focussing on culture." Since we don't separate culture from delivering value to customers, I asked what that meant in practice. Apparently: "A generic scheme of manoeuvre could involve a diagnostic that looks at things like empowerment, psychological safety, collaboration, purpose, customer centricity… then based […]

    Read More
    March 16, 2024
    How to restore Teams Wiki data after Jan 2024

    Microsoft killed Wiki on Teams - who knew they would delete our data too - here's how to restore it

    Read More
    May 15, 2014
    Slothful Lessons in Agile

    Slothful Behaviour is Good If ever an animal captured the principle of "maximising work not done", it must surely be the sloth. A curiously slothful practitioner of business agility. Strangely endearing and charmingly enigmatic, sloths are surprisingly inspiring. There exists a Sloth-Club which was formed "to promote slothful behaviours" such as ecology, economy and vegetarianism […]

    Read More
    1 2 3 13
    linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram