Category: Uncategorized

Doing vs being: Practical lessons on building an agile culture

Four global success stories offer insights and lessons learned on achieving organisational agility.

by Nikola Jurisic, Michael Lurie, Philippine Risch, and Olli Salo

Around the world, a growing number of organizations are embracing agility to improve delivery, increase speed, and enhance customer and employee experience.1 Indeed, in the time of COVID-19, many organizations have accelerated their shift to agile. Our recent research found that agile organizations responded faster to the crisis,2 while those that do not embrace agile working may well forfeit the benefits of speed and resilience needed in the “next normal” after the COVID-19 pandemic.

In essence, agility at an enterprise level means moving strategy, structure, processes, people, and technology toward a new operating model by rebuilding an organization around hundreds of self-steering, high-performing teams supported by a stable backbone.4 On starting an agile transformation, many organizations emphasize and discuss tribes, squads, chapters, scrums, and DevOps pipelines. Our research shows, however, that the people dimension—culture especially—is the most difficult to get right. In fact, the challenges of culture change are more than twice as common as the average of the other top five challenges (Exhibit 1).

Shifting culture requires dedicated effort. Unfortunately, many organizations on this journey struggle to articulate their aspired agile culture and bring it to life. This article demystifies culture change in an agile world through four practical lessons drawn from real-life success stories from around the world.

Lesson 1: Define the from–tos

Each organization is unique. Accordingly, each needs its unique culture to power the new agile operating model. Organizations building an agile culture should base their approach on aspirational goals. They also need to understand their current culture, including the behavioral pain points that can be used as a starting point to articulate three to five specific mindset and behavior shifts that would make the biggest difference in delivering business results.

At New Zealand–based digital-services and telecommunications company Spark, one of the first steps the leadership team took in its agile transformation was to launch an effort to articulate the cultural from–tos. Spark boldly decided to go all in on agile across the entire organization in 2017 flipping the whole organization to an agile operating model in less than a year. From the beginning, Spark understood that the change needed to be a “hearts and minds” transformation if it was to successfully enable radical shifts to structure, processes, and technology.

Exhibit 1

More than 70 percent of respondents are transforming to agile; changing the culture is their biggest challenge.

Spark’s culture change started with its Sounding Board, a diverse group of 70 volunteers from across the organization. These were opinion leaders—the “water cooler” leaders and Spark’s “neural network”— not the usual suspects visible to management. The Sounding Board’s role was creating buy-in for and comprehension about the new model and designing enablers (behavioral shifts and new values) to help employees along the agile journey. An early task for the Sounding Board was to identify the behavioral shifts teams would need to thrive in the new agile operating model. Members used their experiences, inspirational examples from other companies, and Spark’s work on culture and talent to define these shifts. And to help inform what changes were necessary, the Sounding Board sought to understand mindsets (those underlying thoughts, feelings, and beliefs that explain why people act the way they do) that were driving behaviors.

The from–to aspirations were then shared with different groups, including the top team, and distilled into four key themes. Each theme had to resonate with colleagues across the organization, be both practical and achievable, be specific to the company (that is, not derived from general agile theory). The resulting articulation of from–to behaviors allowed Spark to understand and compare its existing cultural reality with the desired end state (Exhibit 2).

Exhibit 2

A clear, purposeful cultural aspiration is the foundation of a successful transformation program.

Finally, to set up its from–tos as more than words on paper, Spark made culture one of the agile transformation’s work streams, sponsored by a top team member and discussed weekly in transformation sessions. The work stream brought culture to life through action. The from–to changes were incorporated in all major design choices, events, and capability-building activities. The work stream aligned fully with other culture initiatives that would help to move the needle on cultural change, such as diversity and inclusion.

Melissa Anastasiou, the team member who led the company’s culture workstream, observed: “Like many organizations, the company’s experience has been that culture change is hard and does not happen overnight. It takes collective and consistent effort, as well as a genuine belief in and understanding of the ‘why’ at all levels of the organization. Setting a clear and purposeful vision for what great looks like—and ensuring that this vision is authentically bought in from bottom to top that is, from shop floor to C-suite—put us in the best possible position to deliver the change to full business agile.”

Lesson 2: Make it personal

This lesson is about making the change personally meaningful to employees. To take change from the organizational to the personal frontier, leaders need to give their people the space and support to define what the agile mindset means to them. This will differ between senior leaders, middle managers, and frontline staff, and have different implications for each. Inviting colleagues to share personal experiences and struggles can build transformational momentum and unlock transformational energy.

This was an approach adopted by Roche, a 122-year-old biotechnology company with 94,000 employees in more than 100 countries. In order to build an agile culture, Roche facilitated a deep, personal change process among senior leaders.

More than 1,000 of these leaders were invited to learn a new, more agile approach to leadership through a four-day immersive program that introduced them to the mindsets and capabilities needed to lead an agile organization. The program, called Kinesis, focused on enabling leaders to shift from a limiting, reactive mindset to an enabling, creative one. It also started the journey of learning how to shift from a traditional organization designed for command, control, and value capture to an agile organization designed for innovation, collaboration, and value creation.

Throughout the program, leaders came to recogize the ways in which their individual mindsets, thoughts, and feelings manifested in the design architecture and culture of the organizations they led. This recognition highlights why change programs that start with personal transformation are more successful. Organizations are built and led by their leaders: the way they think, make decisions, and show up shapes every part of the organization. This dynamic is amplified in agile organizations, which have an unusually high degree of openness and transparency.

The Kinesis program focused on leading through example. Roche’s head of talent innovation (the primary architect of the initiative) heard dozens of stories of leaders coming back from Kinesis and showing up differently. Beyond its learning programs, Kinesis also helped make the change personal by catalyzing large-scale experimentation in organization and business models. Within six months of the senior leader programs, many participants had launched agile experiments with their own leadership teams, departments, and several in their organizational units—engaging thousands of people in cocreating innovative ways to embed agility within the organization.

A core tenet of Kinesis was invitation, not expectation. Leaders were invited to apply lessons learned back to their own organizations. With the new mindset and the invitation, most participants did. Compared with the initial expectations of 5 to 10 percent of participants running a follow-up session with their teams, 95 percent chose to do so. Today, agility has been embraced and widely deployed with Roche in many forms and across many of its organizations, engaging tens of thousands of people in applying agile mindsets and ways of working.

Lesson 3: Culturally engineer the architecture

Even the best-designed culture programs can fail if the surrounding context does not support—or worse, hinders—new mindsets and behaviors.

To sustain a new culture, the structures, processes, and technology must be redesigned to support behavioral expectations. To be successful, the desired culture change needs to be hardwired into all elements of the business-as-usual organization as well as the transformation.

Magyar Telekom of Hungary (a Deutsche Telekom subsidiary), invested to embed and ingrain agile mindsets and behaviors throughout the agile transformation it started in 2018. As with Spark and Roche, Magyar Telekom began with the foundational lesson of defining its from–to. The telco started with three core values that, as the transformation matured, eventually evolved into seven values and were translated into slogans for more effective communication:

—Focus, becoming more focused by critically assessing the current tasks and saying no to things that are not worth the required effort

—Ownership, encouraging ownership by nudging employees to think of their tasks as if being performed for their own company

—Retrospection, emphasizing the need to review and assess, celebrating successes and learning from failures

To ensure formal mechanisms supported this agile mindset shift, Magyar Telekom used structural changes on an individual and organizational

level, aligning the people, customer, and business processes as well as the physical and digital working environments to an agile culture.

Magyar Telekom’s people processes, for example, practically reflected four principles:

—All messages employees receive from the company are consistent with its cultural values

—The cultural values and themes of focus, ownership, and retrospection are embedded in all HR and people processes

—The employer brand, recruitment process, and onboarding journey ensure every new employee understands the agile culture’s cornerstones

—Criteria for career progression define and support agile mindsets and behavior shifts

Magyar Telekom’s business processes were also hardwired to support its culture values. One of several examples used to support the focus and retrospective themes was the quarterly business review (QBR), a common element of agile operating models for business planning and resource allocation. QBRs typically involve stakeholders from major areas of the organization to set priorities and manage organizational demand and dependencies.

To further emphasize focus, the telco committed to implementing and scaling the QBR in the whole organization, including nontribe areas such as customer care or field execution. This formal mechanism had strong cultural implications. First, it signaled that the organization was committed to its cultural theme of focus. Second, the company-wide QBR aligned the whole organization around clear priorities, helping employees focus only on activities that create value while explicitly recognizing and deprioritizing activities that do not.

Third, the QBR cycle also included retrospectives to understand and learn from previous successes and failures in a formal, structured, and highly visible process.

Another powerful way to ingrain culture is to change the physical and digital environments. Floors and walls can, quite literally, create either collaboration or barriers between teams. Magyar Telekom altered its floor plans to create spaces for individual squads, as well as all squads in a tribe, to sit and work together. The new physical environment promoted collaboration and continuous interactions. Team-level tools were introduced—including spaces for squads’ ceremonies and writeable walls where teams could visualize priorities, track progress, and engage in realtime creative thinking. Similarly, the digital work environment was updated with agile tools such as Jira issue-tracking and Confluence collaboration software, enabling efficient handling of epics, features and user stories. Within weeks, the Magyar Telekom work spaces turned from stereotypical offices to collaborative incubators of the new agile culture.

Lesson 4: Monitor and learn

Continuous learning and improvement is a core principle of agile working. It applies to agile culture as well. Successful agile transformations have shown the value of monitoring progress, evaluating behavioral change and its impact on performance, and running regular retrospectives to learn from successes and failures. However, measuring behavioral change has traditionally been a challenge.

ING, a well-known leader of agile transformations in banking, innovated here and used multiple approaches to track the impact of its agile transformation on productivity and several dimensions of performance, time to market and volume, and employee engagement. As part of these tracking initiatives, ING also tracked the progress of culture change and its impact on the overall transformation. The bank even teamed with INSEAD’s Maria Guadalupe, a professor of economics, to study and improve the quality of tracking efforts and the resulting insights.

ING’s first tracking initiative was a 40-question survey with 1,000 respondents that ran five times between 2015 and 2017. The survey questions, including those related to culture, were linked to the bank’s objectives and key results. This correlation between the transformation’s soft and hard drivers and its performance metrics allowed ING to see which cultural factors led to results and were critical to the transformation’s success.

According to Michel Zuidgeest, ING’s lead of Global Change Execution, the product-owner roles and their corresponding behaviors, for example, turned out to be one of the most important factors affecting outcomes. Skill sets for product owners, chapter leads, and agile coaches—as well as the way they work together—were not clearly defined at the start of the transformation, and individuals in these roles had to grow the right mindsets and behaviors before team performance improved.

ING’s second tracking initiative, started in 2019, combined a 300-person “working floor” survey with senior leadership interviews across 15 countries. Once again, metrics on agile included culture-related questions on whether people on the floor felt more responsibility, whether they could collaborate better, and whether they were more able to learn from others in the company. In parallel, ING used qualitative methods to track the shift toward an agile culture. Updated performance frameworks and dialogues, for example, tracked whether employees were adopting desired behaviors while a continuous listening framework gave an ongoing pulse check of how people were doing.

ING used the data from its tracking initiatives to produce practical learning. Survey and interview results were used in QBRs, leadership dialogues, and improvement cycles. Outcomes were shared with tribes, the central works council, advisory groups, and others, and used in performance dialogues. ING also shared its findings with universities, sharpening both the company’s tracking efforts and university research. The value of tracking became very clear. ING managed to measure culture progress, establish the correlation between culture and performance, and use culture data to bring its agile operating model to life.

ING’s tracking initiatives produced insights on agile maturity, performance, and culture. Payam Djavdan, ING’s global head for One Agile Way of Working, explains that as the agile culture metrics improved—specifically the sense of belonging, motivation, purpose, and empowerment—employee engagement consistently increased. Similarly, several dimensions of team performance improved as the culture of credibility and clarity took hold while greater autonomy, a core principle of agile culture, allowed teams to take on their own challenges. In parallel, performance dialogues revealed that trust in tribe leads was a defining factor in employees’ engagement and their ability to share the tribe’s purpose.

Culture counts in all organizational transformations; it becomes critical in agile transformations. Organizations can do agile by changing their structure, processes, and technology. But they cannot be agile without changing the way people work and interact daily. Enabling a successful, agile transformation requires a fundamental shift in culture. Lessons from organizations that have successfully made this shift can give others a head start on their own transformation journeys.

Read More

The keys to a successful merger!

The Root Cause Of Every Merger’s Success Or Failure: Culture

George Bradt 

CONTRIBUTOR

Executive onboarding and BRAVE leadership examples worth following.

Opinions expressed by Forbes Contributors are their own.

When you merge cultures well, value is created. When you don’t, value is destroyed. While some will suggest other factors – silly things like objectives and strategies and implementation – they are all derivative. The game is won or lost on the field of cultural integration. Get that wrong and nothing else matters.

The fundamental premise of any merger is that the merging entities will be more valuable together than they are separately. It doesn’t matter if you define value as shareholder equity, impact on the world or basic happiness. A merger is supposed to be an exercise in value creation. Yet, 83% of mergers fail. The vast majority of leaders get something very wrong along the way.

I spoke with Wolff Olins’ strategy director Nick O’Flaherty about applying the findings from their recent leadership study to mergers and acquisitions. He started by asking if Verizon and AOL are merging and acquiring like it’s 1999. He worries that they could be and suggests three key lessons from the “worst merger in history.”

  1. Clearly define the specific value that will be created from the merger. O’Flaherty told me that “AOL and Time Warner wanted something specific from each other – but the outcome of what that actually looked like for customers was never thought through, nor delivered.” And he questions whether Verizon and AOL are “poised to make the same mistakes again.” Specificity around how new value is created is key.
  2. Fully integrate the two businesses.We’ve all seen organizations that acquire another organization and then run them as wholly owned, separate entities. You can’t possibly realize synergies out of separate organizations. Synergies must be created together by teams looking beyond themselves to new problems they can solve for others.
  3. Ensure cultural compatibility. O’Flaherty pointed out the cultural clash that occurred between AOL and Time Warner may happen again. Verizon is all about engineering while AOL is “more creative, more salesy.” No way those two can come together well without some intensive therapy.

Wolff Olins’ recent leadership study backs up these points. It indicated a shift from a concentration on outputs like sales to inputs like creating and building culture. This is in line with the power of building winners over trying to win. The CEOs surveyed talked about the need to hold their reins looser with the new generation, about the need to be more comfortable with ambiguity as they let their employees take greater leadership roles.

The study suggests we’ve moved from “command and control” in the late 19th century to “motivation and delegation” in the late 20th century to “focus and liberation” in this century. The study quotes Keurig Green Mountain’s Brian Kelly’s bias to “small teams and fast sprints with a tolerance for messy processes.”

The key to a successful merger

The key to a successful merger is determining which culture to merge into which. Co-creating a brand new culture from scratch is a lot of hard work with a relatively low probability of success. The more straightforward and more likely to be successful approach is to pick one culture as the host culture and merge the other culture into it.

Vocus’ acquisition of iContact is a case in point. Successfully merging in iContact was so important that they built an entire new headquarters for iContact in the spirit of the Vocus headquarters.

Contrast that with Philip Morris/General Foods’ acquisition of Kraft. Even though Philip Morris/General Foods was doing the acquiring, they chose to merge the General Foods culture into Kraft.

Of course you have to define value creation and fully integrate the businesses. The point is that these are part of merging cultures, not separate efforts. Corporate culture is the only truly sustainable competitive advantage and the root cause of any merger’s failure or success. Make clear choices about the new, combined entity’s behaviors, relationships, attitudes, values and environment. Then insist on embracing those choices as a condition for staying on board.

http://www.forbes.com/sites/georgebradt/2015/06/29/the-root-cause-of-every-mergers-success-or-failure-culture/#18f7b8992173

Read More

What Is Psychological Safety?

by Amy Gallo

No one likes to deliver bad news to their boss. But that’s exactly what I had to do when a project I’d been working on wasn’t delivering the results we expected. I’d been a big advocate for our team taking on the initiative and, personally, I’d invested a lot of time into it — and convinced others to do the same.

When I met with my manager to present the data, which showed that we hadn’t recouped our investment and the initiative had performed worse than planned, I was nervous. I would’ve understood if she had been frustrated or even angry and I expected her to at least ask “What went wrong?” or “How could we have prevented this?” (both questions I’d prepared answers for).

Instead, she asked a simple question: What did you learn?

I now understand that what she was doing was building psychological safety. She understood that learning was key — my (and her team’s) future performance depended on it. Psychological safety is a critical concept for teams and the people that lead them. It’s also a topic we’ve covered quite a bit at HBR. But not everyone knows or fully understands it, so I reached out to Amy Edmondson, the Harvard Business School professor and author of The Fearless Organization, who coined the phrase “team psychological safety,” to get a refresher on this important idea. I asked her about where the term originated, how it’s evolved, and, of course, how people can think about building psychological safety on their own teams.

What is psychological safety?

Let’s start with a definition. Team psychological safety is a shared belief held by members of a team that it’s OK to take risks, to express their ideas and concerns, to speak up with questions, and to admit mistakes — all without fear of negative consequences. As Edmondson puts it, “it’s felt permission for candor.”

Edmondson first landed on the concept when she was doing research for her PhD. She had set out to study the relationship between error making and teamwork in hospitals, expecting to find that more effective teams made fewer mistakes. But what she found was that the teams who reported better teamwork seemed to experience more errors. When she dug into the data, she began to suspect that better teams might be more willing to report their mistakes – because they felt safe doing so – and conducted follow up research to explore that hypothesis.

The “team” in team psychological safety is important. “This is a group level phenomenon — it shapes the learning behavior of the group and in turn affects team performance and therefore organizational performance,” she says. As Edmondson explained to me, the sense of safety and willingness to speak up is not an individual trait, even though it’s something you do feel and experience at the individual level; “it’s an emergent property of the group.” In fact, in most studies, people who work closely together have similar levels of psychological safety compared to people in other teams.

Why is psychological safety important?

First, psychological safety leads to team members feeling more engaged and motivated, because they feel that their contributions matter and that they’re able to speak up without fear of retribution. Second, it can lead to better decision-making, as people feel more comfortable voicing their opinions and concerns, which often leads to a more diverse range of perspectives being heard and considered. Third, it can foster a culture of continuous learning and improvement, as team members feel comfortable sharing their mistakes and learning from them. (This is what my boss was doing in the opening story.)

All of these benefits — the impact on a team’s performance, innovation, creativity, resilience, and learning — have been proven in research over the years, most notably in Edmondson’s original research and in a study done at Google. That research, known as Project Aristotle, aimed to understand the factors that impacted team effectiveness across Google. Using over 30 statistical models and hundreds of variables, that project concluded that who was on a team mattered less than how the team worked together. And the most important factor was psychological safety.

Further research has shown the incredible downsides of not having psychological safety, including negative impacts on employee well-being, including stress, burnout, and turnover, as well as on the overall performance of the organization.

How has the idea evolved?

I asked Edmondson how the idea has changed in the 20 years since she first starting writing about it. Academics have discovered some important nuances. For example, she points out that psychological safety seems to matter more in work environments where employees need to use their discretion. As she explains, “The relationship between psychological safety and performance is stronger in situations where the results or work aren’t prescribed, when you’re doing something creative, novel, or truly collaborative.” She has also written about how hybrid work requires that managers expand how they think about psychological safety.

She and others have also been looking at how psychological safety interacts with diversity on teams. New research by Edmondson and Henrik Bresman, a professor of organizational behavior at INSEAD, has shown that on teams with high psychological safety, expertise diversity was positively associated with performance. While their study is a single one in a single industry (drug development), it’s an important proof point “that psychological safety may be the key to realizing the promise of diversity in teams.”

How do you know if your team has it?

This is likely the question on many leaders’ minds. Edmondson has developed a simple 7-item questionnaire to assess the perception of psychological safety (if you want to run this survey with your team, there’s an instrument you can sign up to use on Edmondson’s website).

How people answer these questions will give you a sense of the degree to which they feel psychologically safe:

  1. If you make a mistake on this team, it is not held against you.
  2. Members of this team are able to bring up problems and tough issues.
  3. People on this team sometimes accept others for being different.
  4. It is safe to take a risk on this team.
  5. It isn’t difficult to ask other members of this team for help.
  6. No one on this team would deliberately act in a way that undermines my efforts.
  7. Working with members of this team, my unique skills and talents are valued and utilized.

Edmondson cautions however that the scores are not definitive; what matters is the variance. “Anyone filling out a survey is doing so in a way that is relative to their expectations,” she says. “For example, if I say ‘yes, I can ask for help’ I’m doing that relative to what I think it ‘ought’ to be.” She suggests managers use the data from the survey to reflect on your team’s experience and be curious about what you could change to improve that experience. Which leads to another critical question: what can you do to foster psychological safety?

How do you create psychological safety?

Edmondson is quick to point out that “it’s more magic than science” and it’s important for managers to remember this is “a climate that we co-create, sometimes in mysterious ways.”

Anyone who has worked on a team marked by silence and the inability to speak up, knows how hard it is to reverse that.

A lot of what goes into creating a psychologically safe environment are good management practices — things like establishing clear norms and expectations so there is a sense of predictability and fairness; encouraging open communication and actively listening to employees; making sure team members feel supported; and showing appreciation and humility when people do speak up.

There are a few additional tactics that Edmondson points to as well.

Make clear why employees’ voices matter.

For most people, it feels safe to hold back and stay silent — they default to keeping their ideas and opinions to themselves. “You have to override that instinct by setting the stage for them to speak up,” she says. Explain clearly and specifically why you need to hear from them, why their viewpoint and input matters, and how it will affect the outcomes of the work.

Admit your own fallibility.

If you, as a leader, can own up to and demonstrate how you’ve learned from your mistakes, it paves the way for others. It’s important to model the behavior you want to see in your team and normalize vulnerability. This includes things like being respectful, open to feedback, and willing to take risks.

Actively invite input.

Don’t assume people will tell you what they’re thinking or that they understand that you want their input. “Explicitly request it,” says Edmondson. She suggests asking open-ended questions like: What are you seeing? What are your thoughts on this? Where do you stand on this idea?

Respond productively.

You can tell people you want their input or it’s OK to make mistakes, but they won’t do those things if they feel like they’re being blamed or shut down. Edmondson suggests asking yourself: When people speak up with a wacky idea or tough feedback, how do you respond? Be “appreciative and forward-thinking.” Also, replace blame with curiosity. As author and coach Laura Delizonna writes, “If team members sense that you’re trying to blame them for something, you become their saber-toothed tiger… The alternative to blame is curiosity. If you believe you already know what the other person is thinking, then you’re not ready to have a conversation. Instead, adopt a learning mindset, knowing you don’t have all the facts.”

What are common misconceptions?

I also asked Edmondson if there are any myths or misconceptions about psychological safety and she pointed to two.

“It’s all about being nice.”

Edmondson says that creating a psychologically safe environment isn’t about being “nice.” In fact, there are many polite workplaces that don’t have psychological safety because there’s no candor, and people feel silenced by the enforced politeness. “Unfortunately, at work, nice is often synonymous with not being candid.”

“You must feel comfortable in a psychologically safe environment.”

“Too many people think that it’s about feeling comfortable all the time and that you can’t say anything that makes someone else uncomfortable or you’re violating psychological safety,” says Edmondson. That’s simply not true. Learning and messing up and pointing out mistakes is usually uncomfortable. Being vulnerable will feel risky. The key is to take risks in a safe environment – one without negative interpersonal consequences. “Anything hard to achieve requires being uncomfortable along the way.” She shares the analogy of an Olympic gymnast. In her training, she pushes herself and her body; she takes risks but does so in a way that she won’t get injured. Edmondson reminds us, “Candor is hard but non-candor is worse.”

. . .

My boss’s simple response when I came to her feeling defeated has had a huge impact on me. That one question — What did you learn? — changed the way that I view my own missteps — with more compassion and understanding — and how I treat others when they make mistakes. As my experience shows, by making psychological safety a priority, leaders set up their teams for success now and long into the future.

Read More