<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nathan Suver on Medium]]></title>
        <description><![CDATA[Stories by Nathan Suver on Medium]]></description>
        <link>https://medium.com/@nate.suver?source=rss-c6de5a3d89ef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eBSg9SWPqimCuzdsgQI3xA.jpeg</url>
            <title>Stories by Nathan Suver on Medium</title>
            <link>https://medium.com/@nate.suver?source=rss-c6de5a3d89ef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 18:01:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nate.suver/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Nobody Yelled About the Broken Glass]]></title>
            <link>https://medium.com/@nate.suver/nobody-yelled-about-the-broken-glass-fc1b104cded4?source=rss-c6de5a3d89ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc1b104cded4</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[psychological-safety]]></category>
            <category><![CDATA[leaderhip]]></category>
            <dc:creator><![CDATA[Nathan Suver]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 01:44:04 GMT</pubDate>
            <atom:updated>2026-10-16T15:52:05.106Z</atom:updated>
            <content:encoded><![CDATA[<h4>The best leadership I’ve seen this year came from a catering crew, not a corner office.</h4><h3>The Catering Door</h3><p>On Saturday night I worked security at Lafayette College’s Bicentennial Ball, a black-tie gala on the campus Quad for nearly 400 alumni, parents, and friends. My post for eight hours was the catering door, helping out a friend who needed extra staff for this large event. My job was simple: let in catering and event staff, block everyone else. The scale of the event was massive; 60 to 70 waiters, caterers and kitchen staff, all moving at breakneck speed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BAb7YORt57_1Di8Wyk6b9g.jpeg" /><figcaption>A giant temporary outdoor venue, custom built for the event</figcaption></figure><p>Although I wasn’t there to watch the staff work, I couldn’t help noticing them, especially the folks in charge. It was clearly an extremely high-pressure environment, and you could feel the energy.</p><p>About two hours in, a staff member dropped a glass in the middle of this maelstrom of humans, and I waited for the inevitable yelling. Instead, one of the bosses called out, “That’s coming out of your paycheck!” Everyone in earshot smiled, and people came over to help clean it up. A minute later the work was moving again. This didn’t happen just once. It happened a number of times with the same pattern each time: people swooped in to help. This was a ritual.</p><p>The stakes of the event were enormous. That night the college announced <a href="https://news.lafayette.edu/2026/10/10/lafayette-college-celebrates-its-bicentennial-with-50-million-in-new-gifts/">$50 million in new gifts and commitments</a>, including the most endowed professorships it had ever announced at once. <a href="https://news.lafayette.edu/2026/05/13/multitalented-entertainer-vocalist-pianist-actor-harry-connick-jr-to-perform-at-lafayette-bicentennial-ball/">Harry Connick Jr. was headlining the event</a>; even I didn’t understand the full scale of this thing until I was in the middle of it. And yet, despite the pressure, nobody yelled, nobody was cruel. I watched coordinators continuously pat their staff on the back and say “good job” or “great work, keep going”, even as they moved at full speed.</p><p>None of this was surprising for a well-performing team. What was surprising was that none of it was for show. They didn’t know anyone was watching them. The thing that really stood out for me was how their behaviors seemed to get more positive as the pressure and pace increased. As someone who has watched engineering teams for two decades, I’ve seen far smaller stakes produce far worse behavior.</p><h3>This matches what we know from the research</h3><p>It’s difficult to know how these cultural behaviors evolved, whether through trial and error, training, or something else, but these behaviors (and outcomes) are backed by research.</p><p>Amy Edmondson’s study of 51 manufacturing teams introduced team psychological safety: a shared belief that it’s safe to take interpersonal risks. Teams that had it learned more, and learning drove performance. “Coming out of your paycheck” explicitly named the failure, made it funny, and signaled to everyone that nobody was actually in trouble.</p><p>Nale Lehmann-Willenbrock and Joseph Allen videotaped 54 real team meetings. Joke-laughter-joke patterns, not jokes alone, predicted better team performance, both right away and two years later. The catch? Where job insecurity was high, the humor stopped helping. The paycheck rib works because everyone knows nobody’s paycheck is getting docked.</p><p>Karl Weick and Karlene Roberts studied aircraft carrier flight decks and found that reliability comes from “heedful interrelating”: each person acting with awareness of how their work connects to everyone else’s. Nobody assigned anyone to the broken glass. People saw a gap and filled it.</p><h3>A reminder that leadership isn’t a job title</h3><p>The night went off without a hitch. I can’t prove that the culture made it work, and I only saw one door, not the whole operation.</p><p>But what this crew did is exactly what the research supports: make failure survivable, keep the humor going, pay attention to each other, and don’t be cruel. For me, this was a reminder that leadership isn’t some highly paid suit sitting in a corner office. It’s someone who decides, every time a glass shatters, what the next five seconds feel like.</p><h3>References</h3><ul><li>Edmondson, A. (1999). Psychological safety and learning behavior in work teams. <em>Administrative Science Quarterly, 44</em>(2), 350–383. <a href="https://doi.org/10.2307/2666999">doi:10.2307/2666999</a></li><li>Lehmann-Willenbrock, N., &amp; Allen, J. A. (2014). How fun are your meetings? Investigating the relationship between humor patterns in team interactions and team performance. <em>Journal of Applied Psychology, 99</em>(6), 1278–1287. <a href="https://doi.org/10.1037/a0038083">doi:10.1037/a0038083</a></li><li>Weick, K. E., &amp; Roberts, K. H. (1993). Collective mind in organizations: Heedful interrelating on flight decks. Administrative Science Quarterly, 38(3), 357 — 381. <a href="https://doi.org/10.2307/2393372">doi:10.2307/2393372</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc1b104cded4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You moved to public cloud. Cool. Did your organization?]]></title>
            <link>https://medium.com/@nate.suver/you-moved-to-public-cloud-cool-did-your-organization-0563bd86105b?source=rss-c6de5a3d89ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/0563bd86105b</guid>
            <category><![CDATA[organizational-change]]></category>
            <category><![CDATA[public-cloud]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[Nathan Suver]]></dc:creator>
            <pubDate>Fri, 02 Oct 2026 15:21:38 GMT</pubDate>
            <atom:updated>2026-10-02T15:26:57.270Z</atom:updated>
            <content:encoded><![CDATA[<p>Most organizations now treat public cloud as the default place to run things. Workloads move, data centers shrink or disappear, and the migration dashboard turns green. Somewhere in a quarterly review, someone reports that 80% of applications are “in the cloud,” and everyone nods. Everyone gets bonuses. Neat.</p><p>What that number doesn’t tell you is whether anything else changed.</p><p>After years leading DevOps and engineering teams, I’ve seen plenty of organizations migrate substantial workloads while leaving their governance, processes, roles, and decision-making almost exactly as they were. The servers moved. The organization didn’t. I’m now studying this gap as part of my doctoral work, and this piece outlines the research I’m proposing.</p><p><strong>What we already know</strong></p><p>The research on cloud has largely shifted from asking <em>why</em> firms adopt it to asking <em>how much</em> they actually use it and what that does for the business.</p><p>A 2023 study by Khayer, Islam, and Bao surveyed 296 Chinese firms and looked at two dimensions of what they call cloud assimilation. <strong>Depth</strong> is how intensely cloud is used in core processes and how critical the workloads are. <strong>Breadth</strong> is how many services and applications are in the cloud. They found that both improve firm performance, mainly by making the organization more agile with operations, customers, and partners. They also found that getting a complementary mix of depth and breadth mattered more than keeping the two perfectly balanced.</p><p>Separately, Lal and Bharadwaj (2016) interviewed 21 Indian organizations and found that cloud adoption increased several kinds of flexibility: economic (shifting from capex to opex, paying for what you use), process (scaling infrastructure up and down quickly), IT performance, and market flexibility.</p><p>So the short version is: when cloud is genuinely embedded in how a firm works, it tends to pay off. The part that most people seem to forget is that public cloud is a paradigm shift. And research shows that if you treat it like that, the benefits are enormous.</p><p>Here’s the problem. Khayer and colleagues discuss the need to redesign internal processes and strengthen information sharing, but those organizational changes are implied in their model rather than measured. Lal and Bharadwaj’s study was qualitative and explicitly called for quantitative follow-up. Other quantitative work on cloud value tends to measure outcomes like process or financial performance without capturing the structural, governance, and skills changes that cloud usually demands.</p><p>In other words, we have decent evidence that cloud use connects to performance, but very little measurement of the organizational machinery in between.</p><p>There’s an older idea from institutional theory that helps frame this. Kostova and Roth (2002), studying how multinational subsidiaries adopt practices from headquarters, distinguished between <em>implementation</em> (doing the required behaviors) and <em>internalization</em> (actually believing the practice is valuable and committing to it). When a unit has high implementation and low internalization, they called it <strong>ceremonial adoption</strong>: complying in form, not in spirit. You’ve felt this before, those all-hands meetings where the CTO has some new idea but it doesn’t really latch on.. you merely comply without internalizing the content.</p><p>Their work predates public cloud, but the pattern will be familiar to anyone who has watched a “cloud transformation” that consisted mainly of a lift-and-shift-and-we-added-load-balancers and a new invoice. The logic suggests a firm can score high on cloud depth and breadth while internalizing very little of the governance, roles, and operating routines that make cloud worth the money.</p><p><strong>What I’m proposing</strong></p><p>I’m proposing a construct I’m calling <strong>Cloud Organizational Readiness (COR)</strong>: the extent to which an organization strategically, structurally, and procedurally reshapes itself around cloud. Rather than inventing new survey items, COR combines five constructs already validated in prior research:</p><ol><li><strong>Top management support:</strong> whether leadership treats cloud as strategic and is willing to take on its risks.</li><li><strong>Organizational competency:</strong> whether the firm has hired the right people and committed real resources.</li><li><strong>Trading partner support:</strong> whether the firm actually verifies its cloud providers on availability, security controls, PII handling, and identity and access management.</li><li><strong>Relative advantage:</strong> whether people inside the firm see cloud as genuinely beneficial.</li><li><strong>Technical IT capability:</strong> whether the firm can standardize and integrate new technology without its existing complexity getting in the way.</li></ol><p>The core question is whether COR sits between cloud usage and performance. Specifically, I’ll test whether deeper and broader cloud use is associated with higher readiness, whether readiness is associated with better firm performance, and whether readiness <em>mediates</em> the link between cloud usage and performance. If it does, that would suggest the performance gains attributed to cloud depend substantially on the organizational changes around it, not just on how many workloads you’ve moved.</p><p><strong>How I’ll test it</strong></p><p>The plan is a survey of IT managers, cloud architects, and operations leaders, recruited through LinkedIn and a paid research panel, analyzed using structural equation modeling. If you work in this space, I may be asking for 15 minutes of your time at some point.</p><p><strong>Where this might fall apart</strong></p><p>A few honest limitations. It relies on self-reported data, so respondents may rate their own cloud maturity and firm performance generously. Because the same survey measures both cause and effect, common method bias is a real risk; using public financial filings for performance would be stronger, at the cost of limiting the sample to public companies. And with one respondent per organization, a cloud architect and a CFO at the same firm might describe very different realities.</p><p><strong>Why it matters to practitioners</strong></p><p>If the hypotheses hold, the takeaway is uncomfortable but useful: the migration percentage on your dashboard is a weak proxy for value. What may matter more is whether leadership, skills, vendor governance, and internal belief in the platform moved along with the workloads.</p><p>That’s a harder thing to put on a slide. It’s also, possibly, the thing you’re paying for.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0563bd86105b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Great Teams Survive Bad Organizations — A Study Of Microcultures]]></title>
            <link>https://medium.com/@nate.suver/why-great-teams-survive-bad-organizations-a-study-of-microcultures-b1c1f7650a8a?source=rss-c6de5a3d89ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1c1f7650a8a</guid>
            <dc:creator><![CDATA[Nathan Suver]]></dc:creator>
            <pubDate>Sun, 25 Jan 2026 20:17:31 GMT</pubDate>
            <atom:updated>2026-01-25T20:17:31.228Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why Great Teams Survive Bad Organizations — A Study Of Microcultures</h3><p>Every organization has a culture. Walk into their office, and you’ll see their values hanging on the wall. You’ll hear the slogans at the all-hands meetings. On the website, you’ll see the stock photos of unbelievably happy people laughing around laptops, dutifully serving the corporate mission. But inside most companies, workers usually experience something very different: a slow drip of stress, opaque decisions, inconsistent leadership, profits over empathy, and policies that seem to ignore the human beings doing the work.</p><p>And yet, despite this broader dysfunction, there are always a few teams that somehow thrive. They aren’t perfect, but they feel different. They are tight-knit, supportive, psychologically safe. People on these teams stick around longer. They grow. They take risks. They do good work even when the larger organization feels chaotic. They really like coming into work in the morning!</p><p>These islands of sanity are what my research calls positive team microcultures, and the results from my study show just how powerful they can be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*HI-4LmAk7zVZSTRuGFH9zQ.png" /></figure><h3>So What Makes a Team Microculture “Positive”?</h3><p>A positive microculture isn’t about perks, happy hours, Friday lunches, or having a fun Teams/Slack channel. It’s built primarily on three ingredients: <br><strong>- Cohesion:</strong> The team feels united around its work, supports each other, and solves problems collectively. <br><strong>- Psychological Safety: </strong>The confidence that people can speak up, make mistakes, and ask for help without fear. <br><strong>- Supportive Communication: </strong>Open, respectful dialogue that makes challenges discussable instead of dangerous.</p><p>These ingredients don’t operate in isolation; they reinforce one another. Cohesion creates belonging, psychological safety creates permission, and supportive communication creates the pathways where real conversations can happen. When a team has all three, it forms a kind of internal buffer, a localized climate that feels healthier and more predictable than the broader company around it. That contrast is what makes microcultures so powerful, especially in environments where dysfunction is the norm rather than the exception.</p><p>To understand whether positive team microcultures truly buffer people from toxic organizational climates, I ran a quantitative study with working professionals from a variety of industries (a stepping stone for my doctorate). Using a structured online survey, respondents answered validated questions measuring team cohesion, psychological safety, communication quality, and organizational toxicity, along with their intentions to stay or leave their employer. These measures came from well-established research instruments, including Edmondson’s psychological safety scale and Carless &amp; De Paola’s cohesion scale, supplemented by a new communication measure designed specifically for this study. Once the data was collected, I used a series of regressions to test which team-level qualities were most strongly related to turnover intention.</p><p>The results struck me as a bit surprising:</p><p><em>Cohesion helps a bit, communication is really complicated, and psychological safety is the powerhouse that predicts whether people want to stay.</em></p><h3>The Most Surprising Finding</h3><p>The study’s biggest surprise came from testing whether positive communication alone could buffer employees from organizational toxicity. <br>It didn’t. <br>When organizational toxicity was combined with low psychological safety or weak cohesion, communication alone didn’t save the day. In fact, without those other supports in place, more communication correlated with _higher_ turnover intention. This suggests a reality many workers already know intuitively: A team can talk a lot without feeling safe, and just talking about problems alone doesn’t solve them.</p><p>When communication happens inside a psychologically unsafe environment, it’s often just negotiation, conflict resolution, or damage control. Said differently, communication helps only when the team environment is healthy enough to support it.</p><h3>Psychological Safety is the Real Lever</h3><p>Across all analyses in the study, one factor dominated everything else:</p><blockquote>Psychological safety was the single strongest predictor of whether employees intended to stay. (It explained nearly a quarter (24%) of the difference all on its own.)</blockquote><p>This means organizations can pour energy into DEI programs, talent pipelines, engagement surveys, or new performance frameworks, but if employees don’t feel safe to speak openly, ask for help, or admit mistakes, they will eventually leave. Psychological safety isn’t a “nice to have.” <br>It’s a retention and culture strategy. And it’s built almost entirely at the team level.</p><h3>The Core Insight: Microcultures Beat Macro-Cultures Every Time</h3><p>One of the most important takeaways is this:</p><blockquote>Employees experience the organization through their immediate team and not through the CEO’s messaging or the company’s stated values.</blockquote><p>Even in chronically toxic workplaces, people will stay if their direct team feels like a refuge. Conversely, even in companies with healthy corporate cultures, people will leave if their direct team is dysfunctional. This means that the frontline managers are the most important cultural leaders in any organization, and these leaders are the drivers of team level cultures. Remember, retention and morale are shaped by the relationships people experience every day. Positive microcultures are often the only reason employees survive, or even thrive, in otherwise broken environments.</p><h3>What Leaders Should Do with This</h3><p>If you lead people, even a single person, your role is far more culturally significant than you might realize. Creating a positive microculture doesn’t require sweeping organizational change. It requires:</p><p><strong>- Setting clear expectations. </strong>This one is obvious.<br><strong>- Modeling vulnerability. </strong>This heavily reinforces psychological safety (e.g. “If you admit that, then I can be honest too”). It shows empathy, and that you are aware of their human experience. It signals “I care enough about my relationship with you to take a social risk.”<br><strong>- Inviting dissent.</strong> You are a human first, and a manager second. You are far from perfect. As Nassim Nicholas Taleb discussed in his book “Anti-Fragile”, people become _more_ capable through exposure to volatility. Invite it, and grow from it. Stop caring about your ego.<br><strong>- Protecting your team from noise. </strong>For example, give your employees the agency to decide “If the meeting has no value, I should leave, and not look back”<br><strong>- Celebrating progress.</strong> Leaders don’t do this enough. Occasionally buy a sheet cake. Or smash a PC in your parking lot when you eliminate the scary computer under the corner desk that is running your companies payroll.<br><strong>- Occasional team lunches. </strong>Sure, these are fun, but they don’t move the needle much. The other stuff is a lot more important. Still, who doesn’t like free food.<br><strong>- Sharing context </strong>instead of hoarding and hiding information, encouraging learning, experimentation, and asking smart questions. They make books about this stuff, seriously. You should read all of them. <br> <br> These actions don’t take a lot of effort, but collectively they create psychological safety, the foundation of high-performing, low-attrition teams.</p><h3>The Real Outcome: Microcultures Will Build You A Better Company</h3><p>Organizational culture is slow to change. It requires systems, policies, politics, leadership alignment, and years of reinforcement. But team microcultures? You can change that immediately!</p><p>A single manager can transform the lived experience of work for the people they lead. They can build trust where none existed, and buffer their team from toxic patterns. They can create an island of psychological safety that becomes a lighthouse in the storm.</p><p>If companies want to keep their talent, and unlock their people’s best work, they shouldn’t start by fixing the entire culture from the top down. That’s not going to work.</p><p>Start with your team, because that’s where the real change happens.</p><p><em>(this article is based on an upcoming academic paper I’m working on, which I’m publishing next year)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1c1f7650a8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Conductor and the Dancers]]></title>
            <link>https://medium.com/positive-team-microcultures/the-conductor-and-the-dancers-2b1f2993271b?source=rss-c6de5a3d89ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b1f2993271b</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Nathan Suver]]></dc:creator>
            <pubDate>Sun, 22 Jun 2025 16:18:32 GMT</pubDate>
            <atom:updated>2025-12-10T13:33:05.415Z</atom:updated>
            <content:encoded><![CDATA[<p>Every engineering team I’ve managed eventually hits the same wall: growth breaks everything. More developers means more merge conflicts, more dependencies, more chaos. So we add more process, more gates, more rules. We hire release managers. We buy expensive (and sometimes useful) tools. But what if we’re solving the wrong problem entirely?</p><p>A few months ago, watching traffic in Bangalore changed how I think about scaling teams.</p><h3>The Colossal Traffic Jam</h3><p>I had the privilege of attending a friend’s wedding in India. A once in a lifetime experience, and a pretty big deal that came with tons of stereotypical advice:</p><ul><li>Don’t drink the water (turned out fine)</li><li>Don’t eat from this huge list of forbidden foods (I ate everything; it was awesome)</li><li>Get a SIM card, or don’t get a SIM card (still confused on this one)</li><li>Traffic is insane and like nothing you’ve ever seen</li></ul><p>That last one stuck with me. Shortly after arrival, we found ourselves in full-blown Bangalore traffic.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FA31xOD4tW9w%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DA31xOD4tW9w&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FA31xOD4tW9w%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/83ec23a54b5bf97816315e735a8f8710/href">https://medium.com/media/83ec23a54b5bf97816315e735a8f8710/href</a></iframe><p>Pure chaos! A mishmash of motorcycles (carrying impossible cargo loads), cars, <a href="https://en.wikipedia.org/wiki/Auto_rickshaw">tuk-tuks</a>, ox-drawn carts, bicycles, and every other wheeled contraption imaginable. Streets absolutely packed. Honking off the charts. Total bedlam! Or so I thought.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JVNiQlR7Y3sPpEMAM9Vn4g.jpeg" /><figcaption>Too much cargo on a motorcycle</figcaption></figure><figure><img alt="A family of 4 on a motorcycle" src="https://cdn-images-1.medium.com/max/710/1*7mQZcXIF5vxvi9UVvytZIw.jpeg" /><figcaption>A family of 4</figcaption></figure><p>With nothing but time, I started observing more closely and noticed something remarkable.</p><h3>The Dance Nobody Choreographed</h3><p>Yes, there was explosive population growth straining the traffic infrastructure. But fascinating behaviors emerged:</p><ul><li>The honking wasn’t angry. It was communication. Unlike in the US where honking means “move, $%^*! idiot!”, here it meant “hey, I’m behind you, just letting you know.” Pure coordination signal.</li><li>Traffic never completely stopped, it just flowed different than you’d expect. Every inch of road filled as volume increased. When congestion hit, drivers created “new roads” (dirt paths, sidewalks, whatever worked).</li><li>Everyone seemed aware of everyone else. Like partners dancing a waltz they’d never rehearsed.</li></ul><p>No one was in control. The few traffic lights I saw were treated as suggestions. Complex intersections worked smoothly as drivers danced around each other. It all just worked.</p><p>This is the opposite of US traffic, where we follow laws religiously. Even hardened criminals stop for red lights. We don’t trust other drivers; we trust the system. We follow an invisible conductor.</p><p>When I asked our drivers about this behavior, most said: “This is just what we do, I don’t really think about it.” No one seemed to know why the system evolved this way, but I suspect it’s an inevitable response to rapid growth that outpaced infrastructure.</p><h3>The Engineering Parallel</h3><p>I started seeing parallels everywhere in software teams.</p><p>As engineering teams grow, we get “traffic problems”:</p><ul><li>Merge conflicts blocking releases</li><li>Dependency hell slowing deploys</li><li>Developers “forgetting their SQL scripts” or botching feature flags</li><li>Code review bottlenecks</li><li>Endless and painful planning meetings</li></ul><p>The default management response? More rules, more process, more gates. Hire a release manager. Buy better tools. Add more checkpoints.</p><p>But this creates cognitive overhead that seems to suck the joy out of work. Sound familiar?</p><h3>Two Models of Scale</h3><p><strong>The Conductor Model</strong> (what most teams default to):</p><ul><li>Centralized control and coordination</li><li>Detailed processes for every scenario</li><li>Rules prevent problems before they happen</li><li>Success depends on following the system perfectly</li><li>Breaks down when the conductor becomes the bottleneck</li></ul><p><strong>The Dancers Model</strong> (what I saw in Bangalore):</p><ul><li>Distributed coordination through communication</li><li>Principles over processes</li><li>Rapid adaptation when problems arise</li><li>Success depends on awareness and trust</li><li>Scales naturally with the size of the group</li></ul><h3>What Dancing Looks Like in Practice</h3><p>Instead of rigid merge windows, teams coordinate continuously:</p><ul><li>“Hey, I’m about to merge something big to xyz services”</li><li>Slack/Teams channels for deployment coordination</li><li>Quick sync-ups when conflicts emerge. Sync-ups that materialize WITHOUT management intervention.</li><li>Deliberate self-awareness of our engineering teams. Everyone <strong>must</strong> be aware they are dancing. And those that are not dancing are causing degradation.</li></ul><p>Instead of process gatekeepers, everyone owns the flow:</p><ul><li>Developers responsible for their code from commit to production</li><li>Shared ownership of CI/CD pipelines and monitoring</li><li>Teams that break it, fix it. Or if it’s broken, and no one knows who breaks it, everyone stops dancing until it’s fixed.</li></ul><h3>The Trust Problem</h3><p>“But what about compliance? Quality gates?”</p><p>Good questions. The key insight: dancers need more skill, not less accountability.</p><p>Bangalore drivers are incredibly skilled because they HAVE to be. The system only works because everyone takes responsibility for their piece of the dance.</p><p>Same with engineering teams. Dancing requires better technical skills, because you can’t coordinate if you don’t understand the impact of your changes. It requires stronger communication, but not the endless spewing of emails nobody reads; think about how you honk! And it requires a mentality of shared ownership of your product (e.g. your story isn’t done when some agile tool says it’s closed, it’s done when it’s in a satisfied, paying customers hands).</p><p>The accountability is higher, not lower. But it’s distributed accountability, not centralized control.</p><h3>Making the Transition</h3><p>You can’t flip a switch from conductor to dancers. Here’s how to start:</p><p><strong>1. Start with communication protocols</strong></p><ul><li>Establish your team’s “honking”.. what, when, and how to coordinate. Determine what is noise and what is signal. Kill the noise, and pay attention to the signal.</li><li>Create lightweight channels for awareness without overhead</li></ul><p><strong>2. Eliminate one process gate per quarter</strong></p><ul><li>Pick your most painful bottleneck</li><li>Replace it with a communication practice</li><li>Measure what happens (probably nothing bad)</li></ul><p><strong>3. Push decisions closer to the work</strong></p><ul><li>Let the people doing the work make more choices</li><li>Provide principles and context, not prescriptive rules</li><li>Accept that some decisions will be suboptimal (same as with process). These are opportunities to learn.</li></ul><p><strong>4. Build skills before removing scaffolding</strong></p><ul><li>Teach people to see the bigger picture</li><li>Create psychological safety for coordination failures</li></ul><h3>When You Know It’s Working</h3><p>You’ll see the same signs I saw in Bangalore traffic:</p><ul><li>Problems get solved quickly by the people closest to them</li><li>Communication increases but feels less formal</li><li>Bottlenecks shift and adapt rather than backing up the whole system</li><li>People take ownership beyond their immediate responsibilities</li><li>The system flows even when growing rapidly</li></ul><h3>The Choice</h3><p>Every scaling challenge forces a choice: do you trust systems or do you trust people?</p><p>Conductors trust systems. Dancers trust people.</p><p>Both can work, but only one scales gracefully with rapid growth. And only one preserves the joy that makes great engineers want to stick around.</p><p>Maybe it’s time to put down the conductors baton and join the dance.</p><p><em>(originally posted on </em><a href="https://suver.com/the-conductor-and-the-dancers/"><em>https://suver.com/the-conductor-and-the-dancers/</em></a><em>)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b1f2993271b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/positive-team-microcultures/the-conductor-and-the-dancers-2b1f2993271b">The Conductor and the Dancers</a> was originally published in <a href="https://medium.com/positive-team-microcultures">Positive Team Microcultures</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>