In previous posts, we discussed what you can learn about your team from tracking a minimum of data. We introduced throughput as the most meaningful metric you can get from only the completion time of a work item. In a subsequent post, we explained how you can calculate cycle time and work in progress by tracking the start time of a work item. In this post, we focus solely on how to calculate failure demand and what it tells you about the true delivery capacity of your team.
Introducing organizational change is a tricky business, especially when it involves new technology. Even seemingly innocuous changes to technology can have a far-reaching impact on your organization, disrupting the ways you work. Your initial vision of a smooth implementation, rapid adoption, and a high return on investment is easy to say, not so easy to achieve. For example, it is widely discussed that 70% of transformations fail.
Following on from my blog post covering the first two ideals from the Unicorn Project here, I’d like to continue discussing the next two of the five ideals from the book.
The next two ideals from the Unicorn project focus on two important factors of the improving flow in your organization:
Continuous improvement of work
Part of the continuous improvement of work talks to the importance of challenging the status quo, something that can be difficult without psychological safety. Both are necessary to deliver better outcomes from working together.
Let’s delve into these two ideals.
As we introduce technology into our organizations and transform the way they deliver value, bureaucracy is often cited as a common barrier. So why have it at all?
As organizations grow, the “side of desk” style of management eventually starts to fail. Communication becomes more complex as you add more people and more teams. For the company to continue delivering high-quality value, they put standards into place. Governance exists to support the continued delivery of business as usual and the satisfaction of regulatory requirements. However, too much management feels bureaucratic. What would be great would be to have just enough to support your governance needs without hindering innovation.
So how do you create your Minimum Viable Bureaucracy (MVB)?
Today I want to talk about a common digital transformation topic I get asked about, application modernization. More specifically, how everyone is doing it but so few successfully. Typically the conversation starts with one of the following:
“I need to move off my legacy system, how can I use containers to do this?”
“How do we move to a cloud-native microservice architecture?”
“We’ve been told to move everything to the cloud, how do we do that with thousands of applications?”
Often, my initial answer is another question: “Out of curiosity, how did you get to this as your solution?”
Strangely, at that point, it often falls off the rails.
I’ll answer these questions in more specifically at the end, today though I want to talk about complexity and the need to experiment.
One of the biggest problems here is that these are all solutions looking for a problem. While we hope they may be appropriate solutions, hope is not a strategy. On their own, there is not enough information to provide guidance an...
The Unicorn Project from IT Revolution, brings together a number of interesting ideas. In the coming weeks, we are setting up a series of meetups to discuss these ideas from the book and how people look to apply them to their own projects. The first meetup is here.
One of the central themes of the book is around 5 ideals. These are:
Locality and Simplicity
Focus, Flow and Joy
Improvement of Daily Work
Ahead of each of the meetups I plan on writing a blog on the topics we plan on discussing. So first up, I’m diving into the first two ideals and how they might be applied. Let’s go!