You are here

You are here

Why you should lead your digital transformation from the bottom

public://pictures/douglas_squirrel1.jpg
Douglas Squirrel Director, Squirrel Squared
public://pictures/jtf_headshot_color_cropped.jpg
Jeffrey Fredrick Managing Director, TIM, an Acuris Company
 

How can you ensure that your organization’​​​​​​s digital transformation succeeds? Some answers are easy—but can be dangerous. Others are harder, but are more likely to lead to success. Which answers are right for your organization as you progress on your digital transformation journey

Let’s start with the easy answers first.

[ How important is DX to your org? Take our survey and find out how you stand next to the competition. Plus: Get up to speed on digital transformation with TechBeacon's Guide. ]

1. Focus on rituals and ceremonies

The simplest thing to do is to establish as your bible one of the hundreds of books on agile development, lean methods, or DevOps adoption. Make it the one true source of your best practices.

If you’re taking a more hands-on approach, you might anoint one person to be your coach, or "high priest," and then do what that person tells you. There are standards for sprint length and backlog size and there are frameworks—so many frameworks: SAFe and LeSS, and dynamic systems development method (DSDM).

Your teams will go to stand-ups every day, and hold grooming sessions, and invite you to sprint reviews. The problem is that, although they will look agile, there is no guarantee they will be agile. Far too often this focus on form gives you the same slow, unresponsive results you had before, only dressed up in agile clothing.

2. Track and trace the team

Agile methods, particularly Scrum, give you lots of tools for measuring progress: burnup charts, backlogs, velocity, story points completed, and so on. Software vendors are only too pleased to sell you tools that track, graph, slice, and dice these metrics, or provide similar ones for DevOps and lean approaches, and tell you how performance stacks up against last week or the industry average.

These tools are great at producing management fodder and the illusion of control. Unfortunately, high scores and pretty graphs don’t mean your team is delivering agile results, and you can nail your metrics and estimates every sprint right up to the moment you deliver a disappointing pile of useless features.

The central reason these approaches don’t pay off is that they focus on what is easily seen and monitored by the managers at the top, avoiding the hard work of cultural change and commitment that happen at the team level.

James Shore calls these approaches "Cargo Cult Agile." Like the primitive people who started superstitiously donning coconut headphones and signaling nonexistent planes in the hope they would bring them modern goods, adopters of these methods are copying agile actions and tools and hoping that will give them agile results. This hope is just as forlorn as it sounds, and the 84% of digital transformations that fail are witnesses to it.

We wrote our book, Agile Conversations, to propose and explain how to implement a harder answer, we use a method we have seen give dramatic results in team after team.

[ Find out how to roll out Robotic Process Automation with TechBeacon's Guide. Plus: Download Enterprise Requirements for RPA ]

The harder answer: Build trust and reduce fear

Hold difficult conversations with your team. Build trust by sharing your own reasoning and inquiring into the inferences and theories of your team members. Having built mutual trust and understanding, you can move to revealing and mitigating the fears that hold back your team, and come to understand the assumptions behind those fears.

Only after addressing these cultural issues can you—with the help of the participants—expect to benefit from an agile framework or a DevOps approach that fits your organization well and has your team members’ commitment.

If improving your conversations sounds like a challenging route to digital transformation success, good! You’ve understood why we warned you it was the hard answer. But the good news is that there are solid, concrete methods for preparing for and holding these difficult conversations, starting with conversational analysis.

To create a conversational analysis, think of a previous conversation that went poorly, or one you are worried about having—any conversation that raises questions of trust and fear would be a good candidate. Divide a piece of paper into two columns; on the right, put the words that you and the other person said (a sample of a few key lines is plenty), and on the left, put the thoughts and feelings that you had as the corresponding lines were spoken.

Once you’ve recorded the information, it’s time to score yourself for transparency and curiosity, the two key elements of effective conversations.

Curiosity

On the right, circle all the question marks in sentences spoken by you. If there are any questions (often there won’t be, revealing a total lack of curiosity!), reflect on whether each question was genuine. Could the answer have changed your mind, or were you leading the witness and making a disguised statement ("Surely we can finish that feature by Thursday.")?

Transparency

On the left, underline each emotion or thought that you did not share on the right-hand side. You don’t have to have used the same words, but if you're like most people (including us!) you’ll have left out your most valuable, strongest feelings and ideas, missing the chance to show vulnerability and build trust.

Take the next steps

Finally, revise your conversation to increase your curiosity and transparency. Add a genuine question, describe a feeling, or bring up a challenging example. Ask a friend to role-play the revised conversation with you, so you can solidify your learning and find a natural way to express yourself in the more effective way you’ve now learned.

If you and your team develop conversational skills in this way—and build on them with other techniques like test-driven development for people (for more on this, watch Douglas presentation) and coherence busting that start with conversational analysis—you will be able to approach future conversations effectively.

In these ways, the harder answer, the true path to agile success, will not seem so daunting. And you’ll be able to engage in all the conversations we cover in Agile Conversations, not just trust and fear, but why, commitment, and accountability.

With the help of these key conversations you’ll be able to create a real transformation that works for everyone, and with the buy-in you need to succeed. It’s the harder path, but it’s the only one we know that works every time.

Want to know more? Hear Douglas Squirrel and Jeffrey Fredrick speak on leading a digital transformation from the bottom at DevOps Enterprise Summit London — Virtual, which takes place June 23-25, 2020. 

[ Get up to speed on IT Operations Monitoring with TechBeacon's Guide. Plus: Download the Roadmap to High-Performing IT Ops Report ]