Disclaimer
Please note that all names, dates, and specific events in this story have been modified to protect privacy and confidentiality. This is a generalized account based on my experiences.
Hey there, fellow PMs. If you’ve ever stepped into a cross-functional team that’s already knee-deep in chaos, you know the feeling—like showing up to a party where everyone’s already arguing over the playlist. That’s pretty much how my adventure started a couple of years back, when I was assigned to a high-stakes initiative involving developers, database admins, and other cross-functional teams. The goal was to revive the project to streamline data pipelines for a major enterprise overhaul.
From day one, the team morale was off. Projects were lagging—some by four to five months behind schedule! Deadlines were more like suggestions. The team eyed me warily, like I was the new sheriff in town, ready to crack the whip and bark orders. “Here comes another PM to tell us to ‘work faster’ and ‘optimize processes,’” I could practically hear them thinking, who could blame them? I’d been in their shoes before, resenting the outsider who swoops in with a clipboard and a bunch of prescriptive fixes without understanding the trenches.
But the real wildcard was the IT manager—let’s call him Alex. He wasn’t just skeptical; he was a full-on negative influencer. In meetings, he’d lean back with folded arms, poking holes in every idea. “That won’t scale with our APIs,” he’d say, or “Snowflake’s data quality issues will tank this.” His pushback wasn’t unfounded—the tech stack was a beast, riddled with integration headaches from legacy APIs clashing with modern cloud tools like Snowflake, and data quality problems that turned simple queries into all-night debugging sessions. But his attitude? It was draining the team’s energy, turning potential collaborators into silos.
I knew bulldozing through with directives wouldn’t cut it. Instead, I leaned into what I call my “affiliative leadership” playbook—focusing on building relationships, empathy, and harmony before hammering on tasks. It’s that style where you prioritize people over processes at first, creating emotional bonds to foster collaboration. Think less “boss” and more “ally.”
My first move? 1. Listen. A lot. 2. I scheduled one-on-ones with everyone, including Alex, not to grill them but to genuinely understand their pain points. “Tell me about the last time an API call bombed,” I’d ask, or “What’s the trickiest part of wrangling data quality in Snowflake?” I didn’t pretend to know it all; in fact, I admitted my gaps. But I rolled up my sleeves and dove in. Over late-night study sessions (okay, mostly fueled by coffee and online docs), I boned up on the specifics: How RESTful APIs integrate with our setup, Snowflake’s warehousing quirks, and those sneaky data quality pitfalls like inconsistent schemas or duplicate entries that could derail everything.
It wasn’t overnight magic. The first three months were a grind. I facilitated workshops where we mapped out bottlenecks collaboratively—no top-down edicts. We tackled low-hanging fruit first: Streamlining API endpoints to reduce latency, implementing data validation scripts in Snowflake to catch quality issues early. Slowly, projects started inching back on track. Milestones that seemed impossible hit their marks, and the team began to see me not as a pusher, but as someone in the foxhole with them.
Alex, though? He was a tougher nut. It took a full year to get him fully on board. There were setbacks— debates where his passive aggressiveness flared up, and times I wondered if I’d ever crack through. But persistence paid off. By demonstrating respect for his expertise (like deferring to him on API decisions and crediting his insights in team updates), I earned his. One pivotal moment was during a crisis: A major data migration failed due to a Snowflake config error. Instead of pointing fingers, I jumped in with what I’d learned, suggesting a rollback strategy he’d mentioned months earlier. “Hey, Alex, remember that partitioning tip? Let’s try it.” His eyes lit up—he felt heard, valued.
Gradually, he shifted from critic to contributor. He’d proactively flag issues with solutions attached, rally the devs during crunch times, and even champion our progress in stakeholder meetings. By the end, he wasn’t just a supporter; he was an advocate, helping sustain the momentum long after my role wrapped up.
Looking back, this experience hammered home a key lesson: Leadership isn’t about forcing speed; it’s about earning trust through reading the team and becoming the SME. In a world of buzzwords like “agile” and “DevOps,” it’s the human element—affiliative bonds—that turns detractors into allies. If you’re facing a similar uphill battle, start with listening and learning. It might take time (three months for traction, a year for full buy-in), but the payoff? A team that’s not just on track, but a happy bunch of teammates.
What about you? Ever turned a team skeptic around? Drop your stories in the comments—I’d love to hear them!