Company Culture
Reduce Small-Team Culture Shock with Agile

Summarized using AI

Reduce Small-Team Culture Shock with Agile

Jamie Riedesel • May 04, 2016 • Kansas City, MO

The video, titled "Reduce Small-Team Culture Shock with Agile," features Jamie Riedesel, a DevOps engineer at HelloSign, presenting at RailsConf 2016. Riedesel discusses the cultural challenges faced when professionals transition from traditional IT environments to small Agile teams. This presentation is designed to assist individuals in better integrating into Agile frameworks by highlighting the significant differences between these two working cultures.

Key Points Discussed:

- Cultural Differences: Riedesel emphasizes the contrast between traditional IT, which operates as a service organization, and Agile, which fosters innovation and collaboration. Traditional IT organizations often work through a bureaucratic structure, requiring approvals for improvements, while Agile teams are encouraged to be generative, creating and enhancing products collaboratively.

- Organizational Challenges: The speaker shares that traditional IT can be fragmented, with unclear ownership and bureaucracy stifling innovation. He illustrates this with an example of managing 125 independent services across various platforms, complicating maintenance and communication.

- Hostile Work Environments: Riedesel discusses how traditional IT settings can cultivate negative atmospheres - marked by microaggressions, disengagement, and emotional labor - fueling burnout among professionals.

- Psychological Safety: Citing a Google report, he highlights that psychological safety is crucial for effective teamwork. Those transitioning from traditional IT may struggle with this concept, as they may have come from environments where expressing ideas was not encouraged.

- Reflexive Change Resistance: Riedesel discusses how change imposed from above can lead to discontent, complicating the implementation of Agile practices.

- Bonding through Negativity: While professionals often share challenges to bond over common experiences, this can create toxicity that alienates newer team members.

- Strategies for Integration: Riedesel advocates for a shift in mindset when transitioning to Agile, emphasizing collaboration, the importance of open communication, and the need for structured support to foster psychological safety.

Conclusions:

- The transition to Agile requires patience and empathy, recognizing that those migrating from traditional IT will need time to adjust to new methodologies.

- Organizations must nurture a supportive culture that values psychological safety and fosters innovation to ensure successful integration and engagement of all team members.

Riedesel encourages viewers to reflect on their own experiences and consider how positive changes can emanate from lessons learned in past environments as they progress toward a more collaborative landscape.

Reduce Small-Team Culture Shock with Agile
Jamie Riedesel • May 04, 2016 • Kansas City, MO

Reduce Small-Team Culture Shock with Agile by Jamie Riedesel

Ever hire someone from a traditional IT organization who seemed like a great person, only to have them end up a sucking pit of negativity that had to be fired? Traditional IT can be an incredibly hostile environment, leading to survival strategies that aren’t always compatible with small agile-based teams. In this session, I will show how these survival strategies came to be, and ways to deprogram them to reduce your recruiting churn. Better yet, the tools to do so are already in agile.

Help us caption & translate this video!

http://amara.org/v/J48O/

RailsConf 2016

00:00:09.710 I'm Jamie Riedesel, a DevOps engineer at HelloSign. Today, I'm going to talk to you about culture shock in small team Agile environments. I call this an immigration talk because there is a significant difference between traditional IT and small team Agile. Software organizations are experiencing a net migration from these traditional IT teams as the nature of traditional IT changes. I made this migration roughly five years ago, and I failed at it; I got fired. However, I learned a lot through this experience, and this session is my way of giving back to the community. My goal is to help people like me integrate better into this optimistic software world.
00:00:40.770 To start, I want to discuss some cultural differences and build empathy for those who may not understand traditional IT. If you have never worked in a traditional IT environment, it is significantly different from what we encounter in Agile. Traditional IT operates as a service organization, where tasks are completed for other parts of the organization under their direction. Experts in traditional IT are typically in charge of maintaining services but must seek approvals for any necessary improvements. Contrastingly, in a small team Agile environment, the focus is generative — it continually creates and improves products in collaboration with the entire group and product experts.
00:01:18.270 These viewpoints are starkly different. For instance, traditional IT organizations can be incredibly heterogeneous in terms of the supported technologies. In one organization I worked with, we identified 250 different server instances supporting 125 independent services, which is not just one product. This diversity presents challenges in maintaining continuity, as there are many different platforms, software frameworks, and databases to manage. It is not unusual to have a mix of Oracle, SQL Server, and PostgreSQL running concurrently. There tends to be a significant separation of duties as well, where development teams may not even be part of the IT service organization. In some cases, the database administrators and network staff may operate independently, creating communication barriers.
00:02:43.220 These complications often lead to unclear ownership regarding responsibility for various parts of the system. In traditional IT organizations, having ownership of a service is often fragmented; of the 125 services we managed, only a small number were fully owned by the IT organization. Many systems support individual departmental applications, where IT may own the servers but not the applications on those servers, leading to confusion over who is responsible for what.
00:03:21.760 The culture within these organizations tends to be bureaucratic and, at times, pathological. A bureaucratic culture focuses on strict rules; innovation is permissible but must adhere to rigid processes and approvals. In contrast, a pathological organizational culture is power-based. If you have encountered a controlling manager, you know how difficult it can be to get anything approved unless it directly supports their interests or projects. These organizations are often resistant to creativity, and any attempt to innovate may be stifled unless it is aligned with the local boss's agenda.
00:04:41.030 To illustrate this further, let's discuss psychological safety. A Google report published a few months ago highlighted the importance of psychological safety in effective teams. They discovered that the key factor that makes a team effective is if all members feel safe to express their thoughts and ideas. Furthermore, the report emphasized that no single technique or process should be imposed on a team to ensure effectiveness. Teams must develop their unique methods for maintaining psychological safety, particularly when transitioning from a hostile environment.
00:05:07.020 From my perspective as someone who has made this transition, it is essential to understand that those who come from traditional IT are arriving with a very different view of what constitutes a safe environment. Moreover, there are significant issues related to how service providers are treated in these organizations. Americans, for instance, have a poor track record of treating service workers with respect. Despite being highly trained professionals tasked with managing substantial systems, we often feel taken for granted. This feeling can cultivate a toxic environment, especially when service providers are expected to comply with demands that they personally see as poor decisions.
00:05:50.800 Microaggressions are prevalent in these environments. People from traditional IT background may face negativity from all directions. For those of us working in direct IT, we experience frustrations that disrupt our work. Malware, unauthorized users, and failed requests are everyday challenges that erode morale. When it comes to IT support, there are unfortunate occurrences, such as users bypassing established protocols, which can lead to significant repercussions for the service team.
00:06:36.090 As we navigate our roles, we discover the disruptive impact of being forced to support unknowledgeable users. For instance, reformatting machines due to repeated malware infections can unveil some uncomfortable truths, such as seeing inappropriate material from users. These experiences shape perceptions of our colleagues and contribute to a hostile work environment.
00:07:21.760 The unwritten rules of systems administration can define the extent of responsibility each team member feels. With every team believing their way of addressing the needs of the organization is the best, personal biases only exacerbate the situation, creating further animosity among teams.
00:08:01.480 When considering the various issues that arise in traditional IT, it is essential to discuss the emotional labor involved. As I've experienced firsthand, the repeated frustrations lead to a weariness that pushes professionals to disengage from their responsibilities. For example, when someone in the team faces an unresolvable technical issue, they often disengage, perpetuating the cycle of negativity and exacerbating the problem.
00:08:55.360 Let’s further explore the concept of reflexive change resistance. When changes are mandated from above without input from the affected team members, it creates an environment ripe for discontent. It becomes difficult for teams to implement changes that dramatically affect their workflow. This leads to a cycle where pressure builds around implementing changes before they are adequately evaluated, which can lead to deteriorating project outcomes.
00:09:39.240 Compartmentalization is also common in traditional environments. Each department works independently, tending to their concerns while attempting to ignore the chaos surrounding them. While empathizing with the challenges faced by others, they choose not to lend a helping hand to avoid piling on additional stress.
00:10:45.920 The final aspect I wish to touch upon is the bonding through negativity. IT professionals frequently share their struggles with one another, often leading to humor rooted in the shared pain of their experiences. While the sentiment is relatable, it can create a toxic atmosphere that further alienates newer team members who may not share the same sense of humor.
00:11:59.130 Addressing these issues requires a conscious effort to break the cycle. Migration towards Agile necessitates a shift in mindset — a departure from traditional IT protocols towards a more collaborative and positive approach. Through integrating humor and open communication, we can mitigate the harmful effects of negativity and foster an environment more conducive to innovation.
00:12:52.480 We are confronted with the question of how to maintain our sanity amidst these challenges. The migration towards Agile requires support from well-rounded teams that can foster collaboration and bring about change. By creating circles of insight and growth, we can support one another and establish an effective change management process.
00:13:46.480 As we move towards adopting Agile methodologies, organizations must value psychological safety. It is crucial for fostering a sense of community among team members and requires a departure from hierarchical models of communication. This approach will pave the way for healthy interactions among teams as they adjust to rapid changes and demands.
00:14:54.100 The role of management becomes vital in creating a culture that encourages creativity and refrains from squashing innovative ideas. Managers must active listen and facilitate collaboration, rather than relying exclusively on predefined managerial structures. By redefining performance evaluations and focusing on encouraging contributions from all team members, we can work toward establishing a more generative environment.
00:15:52.670 In conclusion, as we facilitate these organizational changes, we must remember the necessity of patience and understanding when working with those migrating from traditional IT. Providing structured support, reiterating the need for psychological safety, and recognizing that these individuals require time to adapt to new methodologies is essential for long-term success.
00:16:54.040 The journey toward Agile presents both challenges and opportunities. It highlights the necessity of recalibrating our priorities and rethinking how we enable collaborative efforts. In achieving a better alignment between teams bound by common goals, we can ultimately begin to overcome those ingrained behaviors that have been present for so long.
00:17:53.670 Lastly, I encourage you all to think critically about your own experiences, reflect on the dynamics within your teams, and consider how positive cultural transformations can emerge from the lessons we have learned from past experiences. It is through these adaptations that we can foster that crucial psychological safety that allows all individuals to contribute to the best of their abilities.
00:18:49.350 As we move forward, I wish you all the best in navigating the exciting landscape ahead. Embrace your experiences, learn from one another, and remember to take care of one another while facilitating this transformative process. Thank you for your time.
Explore all talks recorded at RailsConf 2016
+106