Leading the Product Blog

Stop Asking Product Leaders to Be Unicorns

By Adrienne Tan

Stop Asking Product Leaders to Be Unicorns

Nobody has more than 24 hours

I’ll start with something obvious. None of us has more than 24 hours in a day. By the time you’ve slept, sorted out the family or the dog, and cleared the emails that landed overnight, a good chunk of those hours has already gone.

I mention it because going deep on anything takes time. Learning to read a business properly, coaching a team well, getting good with a new tool. None of that happens in the gaps between meetings. When I try to do everything, I end up doing most of it badly, and the thing I miss is usually the thing that mattered most. I don’t think I’m the only one.

Which is why it surprises me how little care we take with what we ask of product leaders.

And yet we’re asked to do it all

Think about the last month. Has anyone told you, kindly and with the best of intentions, that you should get “closer to the work”? And did that same person also expect you to be across the strategy, the stakeholders and the roadmap, and to be personally hands-on with the AI tool the organisation has just rolled out?

I thought so.

A few years ago I wrote that product leadership requires full body armour. I still believe that. What’s changed is how much we now expect product leaders to carry underneath it. Set the direction, but also write the stories. Own the AI strategy, but also build the prototype yourself. The reason I hear most often is that you can’t coach what you don’t do.

I understand why that sounds sensible. Nobody wants a leader who has lost touch with the work. But when you add it all up, what we’re asking for is a unicorn, someone who is the most senior strategic thinker in the room and the most hands-on contributor in the room, at the same time.

You can see it in the job description and the interview

It starts before anyone has even taken the job. Have a look at the next head of product role that comes across your feed. The list of what they’re after usually runs to a page: strategy, vision, roadmap, discovery, delivery, stakeholder management, data, commercial acumen, coaching, and now hands-on AI experience. I’ve read plenty of them and I’m still not sure who they’re written for.

Then the interview comes around, and candidates are tested on both their thinking and their tool usage. They’re asked to show how they’d work through a product problem, and then to prove they can use the tools, often by live coding a product with AI in front of the panel. I also know of a head of product who missed out on a role because they didn’t know how to use the company’s particular business intelligence tool. Most people could pick that up in a few weeks, and yet it was the deciding factor for a role that’s meant to set product direction for the business.

I’m not against testing how people think, or even testing for skills. But when we expect the same person to be the strategic thinker and the hands-on tool user, and judge them on both, we’re hiring for a unicorn from day one. And I can’t think of another senior role where we’d accept that.

We don’t ask this of other professions

Nobody asks a CFO to process accounts payable so they stay in touch with the numbers. You hire a CFO for their judgement, for their ability to read the whole financial picture and make calls nobody else in the building can make. If your CFO is buried in AP, you’ve got a rostering problem, and an expensive one, because you’re paying CFO money for AP work and nobody is doing the CFO’s actual job.

It’s the same with a general counsel. We don’t judge them on how quickly they can use the contract management system. We expect them to understand the tools well enough to guide the people who use them every day. No one tells them to get closer to the tools.

So why do we keep telling product leaders to?

In Australia, product isn’t highly regarded in a lot of organisations, and I think part of the reason is timing. The hands-on work shows up straight away, because you can see the stories, the designs and the prototype this week. The strategic work takes much longer to prove itself. The product has to get to market, and customers have to buy it, before anyone knows whether the strategy was right. So people tend to value what they can see now.

It doesn’t help that product is done differently in every organisation. That’s OK, there’s no single right way to run it. But it means we’re often on shaky ground, because we haven’t got a shared way of explaining the underlying value we bring. Without that, the organisation falls back on the hands-on output it can point to.

That’s costly when you only have 24 hours. Every hour a product leader spends writing acceptance criteria or wrangling a prompt chain is an hour they aren’t spending on the work only they can do. That includes spotting the pattern across five teams that nobody inside one team can see, growing the judgement of the people who report to them, and telling the organisation the truth about where the real risk sits. You won’t find any of that on a sprint board, but it’s a big part of the job.

There’s another cost that’s easy to miss. Often it isn’t the product leader who wants to be hands-on. It’s the executive or the founder who believes they’ll get a better result if the most senior product person is in the details. I understand the instinct, but the team picks up on it. If the leader is always the one doing the work, the team stops stepping into the gap and starts waiting for the leader to fill it.

How we change the narrative

I want to be clear that I’m not arguing for leaders to sit in an ivory tower. Product leaders who drift too far from the work do lose credibility, and fair enough. But staying close and being hands-on aren’t the same thing, and I think we need to start saying so. Here are a few things I’d suggest.

The first is to carry the message that nobody can be a unicorn. Say it in hiring panels, in leadership meetings and whenever roles are being designed. When we expect one person to be the strategist, the coach and the best individual contributor across delivery and AI, we’re avoiding the harder work of building capability across the whole team.

The second, if you’re a leader, is to ask yourself what you’re optimising for. Have a look at last week’s calendar. How much of it went on work only you could do, and how much went on work that made you look busy and close to the action? For me, being close means going to the right reviews rather than all of them, asking the question that surfaces the risk instead of writing the ticket, and knowing enough about the tools, AI included, to help my team decide when to use them. It also means letting people more junior than me make calls and get some of them wrong, because that’s how they build judgement. And if you’re hiring, check that what you’re testing for matches what you say you need.

The third is that it’s OK to fill the gaps with support. Nobody is good at everything, and pretending otherwise is how leaders burn out. If you’re not especially skilled at AI, bring in an AI coach to work with you and the team, rather than assuming you have to become the expert yourself. And if hands-on AI work matters to your organisation, build that skill across the team so it doesn’t all land on the most senior person.

None of us has more than 24 hours, and I’d much rather we designed product leadership roles around that than kept looking for unicorns.

Adrienne Tan

About the Author

Adrienne Tan

Co-Founder and CEO, Brainmates

Adrienne Tan is the CEO and Co-Founder of Brainmates and founder of Leading the Product, ANZ's biggest product community. With 20+ years in product, she's known for cutting through buzzwords, calling out the nonsense, and helping organisations make product thinking actually work, without the drama.

product leadership capability development product advisory product strategy product transformation