When Your Teammate Is Your Competitor – Enemies to Lovers Arc

Who doesn’t love an enemies to lovers trope? It’s a classic for a reason. Okay okay that is about as far as I can go without acknowledging that my competitors aren’t my enemies (rivals maybe?). And my teammates are just that, teammates. Maybe a more accurate title would be “competitors to teammates”, but that’s not nearly as funny to me.

As a consultant I have found myself in a lot of unique collaborative situations. I’ve had clients who could only meet in the evenings. Clients across the world. Clients whom I’ve worked side by side with in their office. I’ve been the only developer for a client and I’ve been one of 60+ devs. I’ve worked with alongside consultant groups for a client on different projects. I’ve even been put head to head with another consulting company to compete for that client’s business. Something I’ve never done is work on a small pod with a member of a different consulting company. That’s where I found myself recently.

My first reaction in learning this was worry. I knew how to interact with the coworkers and team members but I was unsure how to do that with an outside competitor? My coopetition if you will. How could I build trust so we can work together? Past trust how do we establish norms? There’s so much that needs to be decided between the two consulting companies. And the awkward part is we didn’t even choose to work with each other. We’re just kind of stuck with each other.

That’s admittedly a negative outlook on the situation. Which, for better or worse, were my first thoughts. I needed to reframe this and gain some perspective.

Reframe

We’re both working towards a common goal

The goal is to provide value for the client and deliver something special. The coopetition’s goal is the same. I don’t believe our competitors are trying to put each other out of business. At least not in our local market. Trust that your competitor wants the same thing as you do, to knock it out of the park.

Another way I like to think of this like the NBA. Sure we’re all on our respective teams and have some healthy rivalry but when it comes time for the Olympics we do our best and work together to try and get the gold for our country. Team USA in the 2024 Summer Olympics would not have received the gold if each player didn’t put their trust in each other and work towards a singular goal.

A friend of yours is a friend of mine

The client hired both of the companies because they trust you both. They heard your pitches and deemed it beneficial to team you up.

Setting up to work together

Now on to norms and actually working together. This one can be pretty sensitive. My advice is at first prefer context-rich communication. Once you’ve gotten a feel for each other you can go async, and then use your best judgement. Try to meet in person in the beginning of the project, that small talk and get to know each other is more important than you may realize. If in-person is out of the question then push for camera on. If they don’t want to do that then at least make it a voice call.

In your norms meeting take some extra time to understand how the other company delivers software. Do they prefer agile? Extreme Programming? Or maybe they prefer to shoot from the hip. Learning this will immensely help you figure out where they’re coming from. Things that you take for granted like sprint retrospectives may not be the culture at their firm. The key here is to be flexible and not just understand the how but understanding why. Understanding the why in your process is important because as you build a hybrid delivery workflow as a team you may need to make some concessions. If there’s only two of you, maybe you can drop the sprint retro. Topics discussed in retros can surface naturally in very small teams and you may not need a formal retro to have those conversations. That’s only one example but keep in mind this will be a bit of a negotiation. It helps to have a Miro board or decision log going to formalize the discussion.

Let’s move on to the next part in the process. You’ve established norms and you’re working together day by day. What are some challenges you may encounter and how do you approach solving them?

When it gets dicey

They ignore the norms

Even when norms are established you may find that your coopetitor may be ignoring them. Maybe they always have something coming up to conveniently miss meetings. Or they aren’t updating the board you both agreed to manage. If the issue persists it makes sense to schedule some time to talk through why the norms aren’t being followed. You can even pull up the decision log and ask to revisit it. This log isn’t a contract, so don’t hold them to it. Just log a new decision after gaining alignment. It’s easy in this situation to assume the worst, that your competitor is being malicious or lazy. I’d caution against thinking this. Go back to the common goal. Most likely your coopetitor is just missing some key information.

You’re doing the heavy lifting

Another potential challenge you may come across is the classic team project dynamic where you are stuck doing the heavy lifting while your teammate is coasting and getting credit for your hard work. Separate your work from theirs. A potential way to do this is provide recaps or reports where you clearly state your contributions to the project. Make sure to include your collaboration with the other teammate. I think this is a way to be transparent about dynamics in the team to the client.

They grab the influential work

A challenge that you may not expect but definitely can happen is your coopetitor is grabbing up influential pieces of work. This is tough for a variety of reasons. To the client it looks like a net positive: they get competition on a very micro level. I mean, some companies sometimes run their entire business this way, encouraging competition among employees. Because of this is socially acceptable you have to be pretty careful about broaching the problem. Try asking to collaborate on those influential items. Be direct and instead of asking ‘Can I join?’ Which is easier to say no to. Ask ‘I’d love to learn more about this, do you mind if I watch?’ The benefits here are not only putting you in the mix but you also can provide a second pair of eyes on something influential.

Closing

There’s a fun aspect to this as well. You get to learn, up close, how your competitors work. I think of it like open source, we all get better and deliver better results as we share openly.

Solving for these kinds of problems is part of our job too. No, it’s not software but software is just one of many deliverables we consultants provide. More importantly we provide solutions to problems our client is experiencing. At the end of the day, it is still up to you to get the project across the finish line. Remember to think long term. If you consistently solve problems, the client’s trust in you will increase. With that trust you can provide advice as to how you best deliver results. As they say ‘the cream rises to the top’.

GLHF

Conversation

Join the conversation

Your email address will not be published. Required fields are marked *