From Code to People - The Book is already here!
Get it now!

Your Leadership Duo Is a Relationship. Treat It Like One.

Picture this. A CTO and a CEO, two years into building together. Great energy at the start: whiteboards, late-night calls, “we think exactly the same way”. Then quarterly planning. Five minutes in, it turns into a fight about the roadmap that has nothing to do with the roadmap.

“Since when do you think we should slow down hiring?” “Since March. I mentioned it.” “You mentioned it once. In a hallway.”

Nobody did anything wrong that day. They just hadn’t really talked for six months.

In episode #188 of the podcast, I spoke with Aleksandra Los, Co-Founder of Relayn. Ola has built ventures across crypto (yes, renting Lamborghinis for crypto), personal development tech and now deterministic AI agents. And she said something that stayed with me: “I think of founder relationships as romantic relationships.” Two human beings, two perspectives, and constant change.

You might be thinking: “Alex, I’m not a Founder.” Fair. But almost every tech leader I mentor has a Co-Founder in practice. The EM and PM pair. The CTO and CEO. The tech lead and product owner. Two directors sharing one platform. No equity split; the same dependency.

Most Partnerships Don’t Break. They Drift.

Noam Wasserman from Harvard Business School drew on data from almost ten thousand founders for The Founder’s Dilemmas, and the thread running through the book is clear: the decisions that hurt young companies later (who leads, who decides, what happens when goals change) are usually the ones nobody wanted to discuss early.

Inside organizations, it’s the same. Leadership pairs rarely explode. They drift. Small unspoken disagreements pile up into communication debt, and you pay it back with interest, usually in front of your team. And your team notices the gap between the two of you long before you name it.

The Check-In Ritual (Borrowed From a Marriage)

Ola shared a framework from Jay Shetty, author of 8 Rules of Love, which he uses with his wife Radhi. Ola adapted it to co-founding. Let me adapt it one more step for leadership pairs:

  1. Weekly (15 minutes): “How can I help you next week?” One thing each. Not a status update, you have Jira for that. Each of you owns a clear area (product, delivery, people), and the question is how to support each other’s priorities.
  2. Monthly (45 minutes): “Are you happy with how we support each other?” A retrospective for the two of you, with one key question: “Is there something I did this month that frustrated you, and you didn’t mention it?” Uncomfortable the first time. Priceless the tenth.
  3. Quarterly: “Is this going in a direction we both want?” Jay and Radhi do it once a year. But as Ola said, a year in a startup can be an eternity, and in a tech organization reshaping itself around AI, it’s not much different. Check whether you still see the same future, and whether you still want to build it together.

Why does the cadence matter so much? Gallup found that 15- to 30-minute conversations have a bigger impact than longer ones, but only if they happen regularly. Their research is about managers and employees, but the mechanism works between peers too: frequent small conversations beat rare big ones. It’s the same reason I keep repeating that rituals shape our results, not one-time resolutions.

Start With a Prenup

Ola’s second tip: before you start building, ask the questions that feel way too early. Her example for founders: “Imagine we’re super successful in ten years. Do we sell or do we IPO?”

For a leadership duo, your prenup questions sound more like this:

  • When quality and the deadline collide, who makes the final call?
  • What do we do when we disagree in front of the team?
  • What does success look like for each of us in a year (not for the company, for us)?

This is contracting in practice: making the rules explicit, so nobody has to guess. And disagreement itself is not the enemy. Team conflict isn’t always a bad thing. Unspoken conflict is.

Don’t Give Your Power Away

This is the part of the episode that hit me hardest. Ola admitted that three times she started building from the mindset “I have this great idea, but I can’t do it without someone technical.” And every time, she gave the other person too much power. She was so grateful they were building with her that she kept the relationship going long after she should have ended it.

I see the same pattern in tech organizations. The new EM who never challenges the senior PM. The CTO who swallows their doubts because “the CEO brought me in”. Gratitude is beautiful. Gratitude as a reason to stay silent is a trap.

Ola’s answer to “what do you wish you knew at the beginning?” says it all: the depth of the relationship you have with yourself is reflected in the depth of the relationships you’re able to build with others. A partnership works when both people bring their full half, not when one of them is just grateful to be in the room.

Try the Person First

If you’re choosing a new partner (a co-founder, your first PM, a co-lead), Ola’s advice is beautifully simple: before you build together, do something fun together. Mini golf, billiards, axe throwing. Watch how the other person reacts when things go wrong, when they’re tired, when they’re losing. It really is a bit like dating. With AI and vibe coding, you can build a prototype in a weekend. So test the person first, then the product.

The Bottom Line

Your leadership partnership is one of the most important systems you own. And like every system, it fails quietly without maintenance. Fifteen minutes a week is a small price for not discovering in month six that the two of you have been building two different companies.

So, here’s my question for you: when was the last time you asked your leadership partner, “Is there something I did that frustrated you, and you didn’t tell me?”

Want the full conversation with Ola (Lamborghinis included)? Listen to episode #188 of the Leman Tech Leadership Podcast. For tools like this every week, join the free Leadership Pulse. And if you want the whole toolbox in one place, grab my book From Code to People, where I walk through the CQ Leadership Method step by step.

Until next time, lead without burnout.

Wanna share?

Leman Leadership Pulse

Join a Community over 500 leaders on their way to communication without burnout

Get your one-stop weekly source for inspiration and growth. Every week, we deliver selected content straight to your inbox, designed specifically for forward-thinking leaders like you.

Thank you for signing up!
An error occurred. Please try again.
Aleksandra Lemańska

Listen to Leman Tech Leadership Podcast

Tune into the Leman Tech Leadership Podcast to discover the secrets of becoming a Tech Leader people are eager to follow and never want to leave!

Get Inspired by My New Book

From Code to People. This book is for every technical expert who was told: "Congrats, you're a leader now." …with zero guidance on how to actually lead. No fluff. No theory you'll forget in a week. Just the shifts that make people want to work with you as their leader.
New book!