February 21, 2021

Agile Delivery is a challenge for organisations like yours

By Russ Lewis. Published online February 21, 2021

Achieving Agile Delivery is the toughest challenge of an executive career, no matter if it’s called digital transformation, adoption, or DevOps.

The reality behind the highly-polished powerpoint decks and magazine stories is that despite fortunes being spent over many years, Agile is ‘out of reach’ to many leaders and managers. The evidence shows that challenges remain unresolved in many large organizations, including:

  • Massive overruns and project failures. Plans are made on untested assumptions, which in-turn become critical dependencies for further plans. When the original assumption is proven unsafe the investment and future expectation has become so great, speaking-out becomes career-threatening.
  • Unpredictable IT process behaviour. Ill-informed decision-making destabilises processes, making them unmanageable and undependable. 
  • Inability to learn from mistakes. Check-box attitudes to learning and making improvements means the same problems just keep repeating. 

Luckily, some managers intuitively know how to get the best from people. Their teams may not be Agile, but they do work together to reach clear and common goals, deal with problems promptly, and seem to have fun along the way. They are effective, efficient, motivated knowledge workers. Their managers support and trust their team members and that confidence seems to be returned in approval and satisfaction. 

What if those good teams and managers could incorporate practices that made them more agile? And if they could help to increase agility throughout the organization? 

What would they need to do that? What is stopping them from doing it?

Everything written and practiced under the names Lean or Agile in the past forty years is based on common-sense. If it’s not,  then it can be easily validated with a simple experiment. Yet somehow, folk are afraid of it or perhaps, afraid of the consequences of trying it. 

Phrases like ‘fear of failure’ and ‘failing fast’ make people even more nervous, because failure is not an option in most workplaces. Actually, nobody wants failure at all, they want to reduce the risk of failure to something so small that nobdoy loses sleep over it. That’s one of the things Agile is good for, but since everyone’s got the idea about failure in thei heads, they are too worried to find out what it was really about.

Turns-out this is just one of many knowedge gaps in the minds of so-called ‘knowledge workers’. That’s people who think and negotiate and plan and use computers for a living. Except they also need to understand each other, so they spend a lot of time meeting with each other. Computer programmers, engineers, BAs and technical writers are all knowledge workers, but so are managers. They’ve been KWs for a lot longer, even before computers and their work is about connecting people with information that’s important for their job and looking after resources such as money and people. 

Newsletter signup

    Recent Posts

    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
    Collaboration versus simplification for organisational change

    One of my favourite books on organisational change is ‘Who Moved my Cheese?’ It’s short, and mice looking for cheese to eat is an appealing analogy. It’s a model for managers because it covers four theoretical outcomes of change. Those outcomes are: what happens if I (or we) do, or don’t make this change, what […]

    Read More
    12 signs that using 'ambidexterity as an agile transformation model' is not my original idea

    You see, I thought I was the first agilist to make the connection between agile transformation models and organizational ambidexterity. Certainly, it seemed original when it emerged in conversation with my supervisor. In fact, it was Dr Alireza Javanmardi Kashan’s idea (better make it 13 signs), but it came from our conversation so we said […]

    Read More
    What is contextual ambidexterity?

    Contextual ambidexterity is a culture that expects exceptional performance in both innovation and operation, overturning the illusion that it is either/or. Contextual ambidexterity is agile for managers.

    Read More
    The Future of Agile Leadership

    Introduction The future of leadership is Agile There are many different types of leadership styles and not all work well in every situation. The most popular method, the "Command and Control" style which has been dominant for centuries, may be on its way out as research shows that this type of leadership does not foster […]

    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
    September 23, 2014
    Agile Estimation Cards and the Art of Kitchen Renovation

    Construction runs to a well-established plan Simon is a project manager who is having some building work done at home - an extension with a new kitchen. We were discussing Agile project management and specifically Estimation Cards. He pointed-out that his "development team" consisted of builders, electricians, plumbers and kitchen fitters, who all worked to […]

    Read More
    September 6, 2013
    Agile Prototyping to Confirm Requirements

    Delivering Value Early This post nails the value to customers of rapid, or agile prototyping. We first met the charming people at MECA on Tuesday afternoon, so we could hear directly what they wanted from their new information system. Why did we want to meet with them when we had a (very clear) 250 page […]

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