CaddieOpen in CaddieDownload for Mac

The new rules of product management in the AI era | Sherif Mansour (Head of AI, Atlassian)

Shared by Caddie Library · Updated
Lenny's Podcast1:21:38Open on YouTube
Chapters show their main points

The bottom line

A PM's main job is to close context gaps so the whole team shares one brain and makes good decisions fast. With AI making building cheap, direction is the bottleneck, so PMs, specialists and junior hires matter more.

Key takeaways

  • A PM's core job is to fill customer, market and business context gaps, not to make every decision. 2:24
    • The three contexts are the customer, the product and market, and the business the team operates in.
    • Engineers sit in customer interviews, because their own aha moments build far more empathy than a handed-over summary.
  • AI makes throughput cheap, so direction becomes the real bottleneck. 24:53
    • Atlassian moved PMs and designers into squads where everyone was an AI builder. After about a month, everyone went back to their traditional jobs.
    • Specialists still matter, because AI output is only as good as your knowledge of the domain. Sherif's rule is direct the ship, don't row it.
  • PM is the fastest-growing tech role because teams need people to steer the extra output. 22:52
    • Lenny's job market data shows PM with the most open roles, engineering slowing and design flat.
    • User research has only about 108 open roles globally.
  • Hiring now favours taste-led artist PMs and juniors who bring new ways of working. 33:00
    • When software is cheap to build, experience becomes a differentiator, and artist PMs lead with vision and experience.
    • Juniors adopt new tools more readily than seniors (Sherif recalls 38%), while seniors spot AI slop quickly, so the two complement each other.
  • Product advice depends on its context, so the right move is to ask why it worked. 57:03
    • Starting with a solution suits discovery and product strategy, as with Amazon's huge book inventory becoming an everything store.
    • Bolting AI onto existing workflows, like agents in Jira columns and cards, is how an established product becomes AI native.

We realized throughput's not our problem. Direction's our problem. I need more people to steer the ship.

Sherif Mansour, quoting a PM on his team

Chapter summaries

0:00 Teaser

AI amplifies what a PM is good and bad at, so PMs are needed to speed up decisions rather than to build everything.

  • PMs own decision velocity, not the decisions themselves. 0:47
    • Having access to a tool does not make you an expert in the domain it covers.
    • AI amplifies your strengths and, equally, your weaknesses.
    • Sherif says PMs are some of the worst solution designers in the world.
    • His 12-year-old son vibe codes his own games, skipped syntax entirely, and thinks that is normal.

1:24 What makes a great PM

PMs fill three context gaps to build one shared brain
When everyone holds the same context, the team decides without waiting on the PM, and that is how a PM raises decision velocity.

In a medium or large company a PM earns their keep by filling context, and this matters most when a team scales.

  • Scaling a product team breaks trust and shared understanding, and a shared brain repairs it. 2:50
    • Sherif's answer is aimed at medium to large organizations, which he says differ a lot from startups.
    • Past 20 or 30 people, trust breaks, shared brains break and an us-and-them culture forms. He calls scaling teams the hardest thing he has done at Atlassian.
    • The context goes to humans and, these days, to agents too.
    • He tells PMs to run away from the Jira backlog. If one card seems more important than another, that is context the rest of the team lacks.

4:17 Why your job is to fill context gaps, not make decisions

A PM scales by giving the team the reasoning behind priorities, so they can decide without waiting.

  • Being the bottleneck on every decision is a sign the PM has not shared enough context. 4:48
    • Early in his career Sherif vented to his manager that the team was blocked on him. She told him to spend more time on strategic things.
    • He realized he was too busy planning sprints, and that a shared brain was the way to scale.
    • The gap changes over time: a vision gap this year, a customer gap next quarter, a landscape gap after that.
    • Vision work, market landscape reviews and trying out tools should be done as a team, not by one person coming down from the mountain with instructions.
    • His manager was looking past him while he vented for about ten minutes, yet her advice still landed.

7:10 Examples of context-sharing done well and done poorly

An engineer who watched customers invented document tasks
The usage data only pointed to more icons, and it took an engineer sitting in on the call to see the real need.

When the team shares the PM's journey, engineers produce ideas the PM would not have reached alone.

  • An engineer who watched customers invented tasks in documents. 10:10
    • In 2010, Confluence customers put red stars (not done) and green stars (done) in meeting notes.
    • After the call, an engineer proposed a checkbox users could tick. No one had put tasks in a web document editor before.
    • The usage data alone only suggested shipping more icons.
    • Other practices: designers co-create concepts with the team, a PM has every engineer test AI tools and report back, and engineers staff booths at Atlassian's European customer event.
  • A PM should aim for no extra power over the team. 9:37
    • A squad PM has no reports, so influence without authority is the job. The alternative to handing over a spec is getting everyone on board with the vision.
    • If you disagree with a roadmap item, either your belief has not been shared with the team, or you are wrong.

11:25 The GM/scientist/artist PM triangle

PMs differ in how they naturally do discovery, and few are strong at all three styles.

  • The PM craft triangle sorts PMs into general manager, scientist and artist. 11:44
    • Geoff Redfern created it at Atlassian. Sherif says picking one framework and sticking with it is what matters.
    • A general manager thinks in TAM, profit and revenue. A scientist is hypothesis driven, as in growth teams and A/B tests. An artist is led by emotion, vision and experience.
    • Few people do all three well. Many can do all three at a basic level, which suits zero-to-one projects and startups.
    • Bigger organizations can afford a PM who focuses only on one product's growth metrics.

12:38 How to use the triangle in hiring and calibration

One interview question reveals which type of PM you are
General managerScientistArtist
Discovery styleBusiness-ledHypothesis-drivenVision & emotion-led
Answer to 'improve a product'New opportunity, size the TAMHypothesis, test variantsPaints a vision, works backward
Thinks inTAM, profit, revenueExperiments, A/B testsExperience, intuition
Natural fitBusiness betsGrowth teamsNew experiences
Atlassian uses this triangle in hiring and calibration to match the type of PM to the work, not to fill seats.

A PM's place in the triangle shows in how they answer one open question, and it should guide who goes on which team.

  • Asking for a favorite product and how to improve it reveals a PM's type. 12:48
    • A general manager points to a new business opportunity and sizes the TAM.
    • A scientist starts from a hypothesis and tests variants.
    • An artist paints a visual vision, then works backward to the problems.
    • Atlassian uses the triangle in calibration and hiring, and asks what kind of PM a team needs before adding one.
    • Sherif has seen many PMs who struggled regain energy after moving to a different type of project. He adds, who would have thought diverse teams still matter.

15:01 You don't need to be great at everything

Run toward your natural strengths, admit your weaknesses openly, and build a team that covers them.

  • Leaning into strengths beats fixing weaknesses. 16:10
    • At Atlassian it is a running joke that Sherif is the worst general manager type. He is still on the exec team as head of AI.
    • That joking makes it safe for others to share their weaknesses.
    • He is a strong artist PM. His partner Jamille is his opposite, and each shines where the other is weak.
    • Early in your career, do career discovery, as you would do product discovery, to find what you are naturally good at.
    • Lenny adds that you still need a baseline in everything. Complete mastery is rare, and co-founder and CEO Mike is the exception, critiquing drop shadows that are off by five pixels and then the business model.

18:09 Career coaching: early-career unlocks

Early-career PMs accelerate when given a stretch role just above their level that plays to their strengths.

  • The right opportunity at the right time is the main unlock. 18:38
    • Sherif saw that a PM named Rachel had a scientist brain while a new product was growing. He stepped aside and asked her to take it over.
    • A sign you are good at something is that people praise a project of yours. Study how you approached it, then look for similar work.
    • A leader's job is to spot the opening, which may mean moving someone to another team.
    • Show your manager a framework like the triangle, say where you think you sit, and say you want the next opportunity. In 17 years at Atlassian, Sherif says, new opportunities kept appearing as the company grew.

21:14 Career coaching: senior PM and manager unlocks

At the senior level, growth can mean going deeper into work you excel at or trying something different.

  • A senior PM's next unlock may be a change of direction, not a higher level. 21:25
    • At L6 you have found your groove, so "accelerating" can mean going diverse and trying totally different work.
    • It can also mean chasing similar work, which Sherif still counts as accelerating a career.
    • A PM on his team just marked 10 years at Atlassian. She leads pricing and packaging work across AI.
    • She keeps finding more work across the business that matches what she does well.

22:19 Why PMs are thriving in the AI era

PM demand rose even though many people expected AI to make the role redundant.

  • The expected end of the PM role did not happen. 22:39
    • Lenny's state of the tech job market report looks at hiring trends across PM, engineering and design.
    • When AI arrived, many said PMs were over and asked why companies would need them.
    • Lenny had predicted this outcome in an earlier post.
    • He calls it surprising that the role most written off is now the one thriving.

23:42 Atlassian's AI builder experiment, and what it revealed

The all-AI-builder squads reverted within a month
Early speed hid the real constraint: knowing what to build, not how fast it gets built.

The "everyone becomes an AI builder" story was a misconception, and early speed hid the real problem.

  • Sherif has been debunking the idea that everyone is becoming an AI builder. 23:42
    • He defines an AI builder as someone who spends most of their time building software with AI.
    • A year ago the narrative said this one role would absorb the others.
    • He debunks it with customers and inside Atlassian, and wrote a post about it.
    • Atlassian tested it as a craft question, to see if that was where things were headed.
  • The experiment felt like a huge win at first. 24:32
    • The squads had no PM or designer, and members came from different crafts.
    • In the first weeks, one PM called it unbelievable and said they were building constantly and moving faster than ever.
    • Sherif's reaction was doubt: was that really where it would land?
    • The PM's enthusiasm came in the early days, before the reversal.

25:01 Why throughput is no longer the bottleneck; direction is

Large companies need people who steer, and access to a tool does not make anyone a specialist.

  • Whether a PM should code depends on the size of the company. 25:25
    • Many PMs asked him if they should be coding, and quite a few have committed code in some capacity.
    • Startups and zero-to-one projects need everyone to do anything.
    • Where there are dozens to tens of thousands of engineers, the problem is direction.
    • In his words: not how quick you can pump things out.
  • Cheap building creates chaos that PMs are needed to sort out. 26:22
    • Lenny argues that anyone can build, so prototypes and ideas multiply.
    • The need becomes alignment, buy-in, and judging whether something is ready and will hit goals.
    • Lenny finds it interesting that everyone expected the opposite to happen.
    • He says the thinking now is "what are we actually doing?"
  • The mockup era showed that tool access does not make you a specialist. 27:07
    • Balsamiq promised that everyone could do mockups, and Atlassian adopted many mockup tools.
    • Sherif learned that PMs are some of the worst solution designers in the world.
    • AI amplifies strengths and weaknesses, and artist PMs end up making better mockups.
    • Everyone's circles grow bigger, but they do not overlap more, so specialists still lift quality and taste.

28:48 What PMs should actually be doing with AI

PMs should name the team's context gap first, then use AI to close it.

  • Start from the team's problem, then ask where AI helps. 29:25
    • PMs own decision-making velocity, so the first question is how to help the team move faster.
    • The second question is whether AI can help with that.
    • A customer empathy gap means involving the team and using AI to fill it faster.
    • A vision gap can be helped by prototyping. A market gap can be helped by sending agents to run analysis.
    • Lenny adds that shipping code is rarely the bottleneck and is the last thing to speed up, except at startups or new teams.

31:04 What's trending up and down in PM hiring

Hiring leans toward taste-led PMs and people who can change how a team works.

  • Artist-type, experience-led PMs are trending up in larger organizations. 31:23
    • When everyone has access to the same intelligence, taste matters more than before.
    • Sherif frames this as a nuanced claim about larger organizations.
    • He notes the taste argument has been covered heavily on Lenny's podcast.
    • He did not name specific skills that are trending down.
  • Established teams hire for cultural change. 32:02
    • He defines culture as how work gets done, and the challenge is reinventing each member's job.
    • In interviews he asks what new culture the candidate would bring.
    • He asks how people work with AI and pushes past answers like "I use it to summarize stuff".
    • "AI native" is a relative term, so he looks for new ways of working instead.

32:44 The case for hiring more juniors in an AI world

Juniors bring new habits; seniors catch the slop
JuniorsSeniors
Old habits to unlearnNoneMany
Ways of workingAI-native by defaultMust reinvent
Spotting AI slopWeakFrom a mile away
Domain expertiseLowDeep
In AI tinker weekDemos, tools, coolnessEvals, quality, slop
Atlassian has leaned toward hiring juniors because its established teams need to change how they work.

Juniors carry no old habits to unlearn, and they pair well with seniors who spot slop.

  • Established organizations still need juniors, because their problem is a workforce that must change. 33:15
    • The claim that AI can do juniors' work misses that the real problem is changing how people work.
    • Unlearning old ways and learning new ones is very hard, and someone who doesn't know better finds it easier.
    • His 12-year-old son went from Scratch straight to vibe coding and skipped syntax entirely.
    • The son dismisses a model for failing at something that would have taken days to build.
    • Sherif admits it sounds spicy that juniors' AI slop levels may be higher.
  • Juniors and seniors make a complementary team. 34:28
    • Juniors lack the domain expertise to spot slop, while seniors spot it from a mile away.
    • Atlassian has over-indexed on hiring juniors over seniors because it has an established workforce.
    • In AI builder weeks, all crafts stop and tinker with AI for a week.
    • Juniors show demos and tools, while seniors gravitate to slop, evals and quality.
  • Strong juniors come from varied backgrounds, and curiosity matters most. 36:59
    • Atlassian's Sydney APM cohort mixed arts degrees, law and technology, and computer science.
    • He looks for critical thinking, high curiosity and willingness to try anything.
    • They try anything because they have not done things any other way.
    • Seniors get better quality and productivity from the tools they use but try fewer new ways of working.

38:07 How to spot the artist streak early in candidates

Artist PMs lead with vision and experience, show it early, and the same logic suggests design is undervalued.

  • Artist PMs lead discovery through vision and experience. 38:49
    • They may start with a solution and work back to the problem, guided by intuition.
    • They are more data informed than data driven, and their prototypes tend to flow better.
    • A signal is the person who picks up the whiteboard marker and draws when a discussion is unclear.
    • A growth role needs the reverse, more data driven than informed, which creates a healthy tension.
    • With cheap software and similar features everywhere, experience becomes a differentiator, and he doubts one agent interface will win.
  • The artist streak shows early, even without domain experience. 41:03
    • APM candidates recorded a Loom presenting an app they built for a take-home exercise.
    • One walked through graphs, business case and TAM, and spent little time on experience. Another walked the end-to-end journey to build an emotional connection.
    • The second candidate's discovery was more visual.
    • His son is strong at maths and logic and his daughter loves drawing, in the same household.
    • It is easier to accelerate what you are naturally good at. Artists can be trained, but it is harder.
  • Design may be undervalued because the market has not yet seen that experience matters most. 44:27
    • Lenny sees flat designer hiring and wonders if PMs are filling the gap.
    • Sherif's hypothesis is that the market has not yet had the aha moment on experience.
    • In his 17 years at Atlassian, design has never played a bigger role in driving the roadmap.
    • He is fully convinced experiences will matter most, but calls it a hypothesis: we'll see if it is correct.

46:05 When starting with the solution is the right move

Starting from a solution works when you are discovering what to productize or setting product strategy.

  • Watching what customers already build shows which problems to productize. 47:04
    • Three and a half years ago, Atlassian debated putting a general chat and custom agents into Rovo. The safer idea was a summarize button on Confluence pages.
    • Chat on a whiteboard was a clumsy way to group sticky notes by theme. The team turned it into a select-and-group feature.
    • Nearly 10 million agents run in loops each month in Jira and Confluence. Some stay open-ended, and others, like AI triage, become native features.
    • Mansour calls this "paving the cow path": make the worn track across the grass the real path.
    • He doubts it covers most cases, but says much discovery is implicitly watching customers build their own fix.
  • Product strategy starts from the assets you already own. 50:03
    • "Where do we play, how do we win" can only be answered from what is unique about your company and product.
    • Bezos asked what else needs a ridiculously large inventory, and the answer was an everything store.
    • His exercise for teams: list today's assets, list your beliefs about where things will head, then look for the connection.
    • He also warns that teams now do too little talking to humans, because dashboards make it easy to stay behind a screen.

52:42 Why “bolting AI on” is often the right product strategy

Add agents to workflows your users already run
The users stay where they are, and the workflow slowly moves from AI novice to AI native.

An established product reaches AI native by adding AI to the workflows its users already run.

  • Evolving existing flows beats rewriting a product with millions of users. 53:07
    • Customers have modeled billions of workflows in Jira, many of them outside software. App store approvals and telecom complaints are examples.
    • His formula: list the human workflows in your product, rigid or informal, then find the steps where an agent adds value or efficiency.
    • He admits it "sounds dirty" and would not market it as bolting on. It is still what he would build in an AI native tracker.
    • Reimagining workflows is still worth doing as an exercise. The job with an existing base is moving users from AI novice to AI native.
    • Agents in loops run millions of times with measurable value. A weak agent gets improved or removed.

56:01 The importance of nuance over hot takes

Every piece of product advice has an equally good opposite, so the context behind it matters most.

  • Advice only transfers when you understand where it worked. 56:47
    • Mansour backs an AI builder on zero-to-one projects, even in large organizations. Most organizations with developers have a direction problem instead.
    • He equally advocates starting with the problem. The counter view just gets too little airtime.
    • Sharing what you learned gives others confidence that there is no single right way. He once wrote up craft lessons as blog posts.
    • As Confluence's first PM, he saw product engineers help PMs scale by carrying shared context. No term existed for the role, so he defined it in a post.
  • Reaching exec-level strategy does not require managing people. 1:00:11
    • PMs see managers attending strategy offsites and conclude they must manage too.
    • Atlassian has several distinguished PMs and engineers who work at exec level as individual contributors.
    • Many people move between IC and manager tracks by season. They may run a small team during a zero-to-one, then step back off.
    • He wants this celebrated because it plays to each person's strength.

1:01:31 Why managers still matter

Managing well and doing meaningful IC work together is hard, so Atlassian runs two manager models.

  • Atlassian mixes big-team coaches with small-team managers who own a project. 1:01:54
    • One model manages 10 to 15 people. The other manages three or four and owns a project.
    • The minimum span is three or four reports, and most managers have eight or nine.
    • Assignments follow each person's strengths, which Mansour says gives the best outcome.
    • Big-span managers play the coach role far more.

1:02:42 The most common mistake new PM managers make

New PM managers step back too fast, when teams want leaders who work through outcomes with them.

  • Going hands off too quickly is the top mistake. 1:02:55
    • The best managers at Atlassian join the team and help it get through outcomes.
    • In a product review, a weak manager only says it isn't simple enough. A strong one says let's explore some options together.
    • Space for the team still matters. Mansour says to create it, but not by zooming out completely.
    • He separates managers from leaders. One person can be a good manager and a poor leader, or the reverse.
    • He expects leading by example to matter even more in the AI era.

1:04:05 How to work with visionary founders and strong stakeholders

Your job is closing the gap to chapter 10
Following orders without conviction is the risky path, so get to chapter 10 yourself before you pass anything on.

Treat a visionary leader's conclusion as likely right, and work to understand how they got there.

  • Visionary leaders are chapters ahead, so your job is to close the context gap. 1:04:53
    • He compares it to a movie: the leader is on chapter 10, you are on chapter three, and the team is on chapter one.
    • Following orders without conviction is the dangerous path. He asks instead, What made you reach that conclusion?
    • In his experience founders have been right 99% of the time, because they have thought about the problem far longer.
    • Once he reaches chapter 10 himself, he knows how to bring the rest of the team along.
  • Start from trust, because depth in a domain takes years to build. 1:06:36
    • The pet-project HiPPO (highest paid person's opinion) exists in some companies. A leader with years in enterprise B2B is different from someone who spent a year here and a year there.
    • His rule: assume they're right and assume you're wrong.
    • Sometimes you will prove the leader wrong, but that is not the goal. The goal is the best outcome for customers.
    • Only after the gap is filled can you bring the team along with real conviction.

1:07:12 When you disagree: a framework for transparency

Label every opinion with how strongly you hold it
People with power should say how much weight their opinion carries, and PMs should ask when they don't.

When you disagree, say so openly, settle who owns the call, and make everyone's level of conviction explicit.

  • State your disagreement, ask who owns the decision, then show both sides when you pass it on. 1:07:26
    • Sherif asks are you the decision maker or am I? and then backs whoever owns the call.
    • To the team, he gives the pros and cons of each option and then the decision, without calling anyone out.
    • Leaders often say "I disagree, but I want you to own it," more than you'd imagine.
    • His example was a branding choice that was the best of the worst options, and both sides were real trade-offs.
    • The best PMs argue against themselves. He asks in reviews, why would we not do this?
  • Powerful people should label their opinions, and PMs should ask for the label when it's missing. 1:09:25
    • Dharmesh Shah's hashtags mark an opinion as an FYI, a suggestion, a recommendation or a plea.
    • The PM asks about conviction and plays it back at the end.
    • Atlassian's founders say things like "strong opinion, not my decision."
    • The playback sorts each opinion into a conviction to explore or an input the team decides on.

1:10:51 Final thoughts

Careers are built by other people's sponsorship, so repay it by creating opportunities for someone else.

  • Everyone is a product of someone who made room for them, so find a person to champion. 1:11:08
    • Sherif asks who you are creating opportunities for.
    • If no name comes to mind, find someone you believe in and give them a go.
    • He sums it up as remember where you came from.
    • He also asks listeners to share their own stories, because nuance matters.

1:11:37 Lightning round

Good AI products sit inside the workflow people already use, and open, shared context makes both people and AI better.

  • Gemini inside Google Maps shows the value of putting AI next to the workflow. 1:13:16
    • Sherif calls it a lesson in product workflow proximity, since you don't leave the map to talk to an AI.
    • The AI knew the trip, so his family played quiz games about their destination.
    • It was available in Australia and on Apple CarPlay, and it kept the kids off screens for about 30 minutes.
    • Lenny joked that they just bolted AI on, and Sherif agreed that is often a strong strategy.
  • Decoupling your identity from your job keeps you sustainable. 1:14:42
    • He plays footy with electricians and bricklayers, none of whom work in tech.
    • He says his joking at work is how he handles his nerves.
    • He also reads kids' books with his children and recommends Project Hail Mary.
  • Atlassian's open by default culture gives people and AI more context. 1:17:36
    • Exec reviews are usually recorded and searchable, so AI agents can be run over them.
    • Sherif's hypothesis is that remote workers get more out of AI, because they write and share more digitally.
    • Atlassian is testing the remote hypothesis with data scientists.
    • Lenny notes that AI could also expose things people shouldn't see.
    • His last ask is to question one-line takes like "don't hire juniors" instead of amplifying them.

In the growth library

Sherif Mansour, Head of AI and Product Craft at Atlassian. Sherif Mansour argues that a PM's core job is building a shared brain by filling context gaps, and that AI makes direction, taste and diverse teams more valuable, not less. His team's experiment with all-AI-builder squads ended with everyone returning to their crafts, and PM job openings are now growing fastest.

Lessons that draw on this:

More from Lenny's Podcast · The whole library, and ask it anything

Transcript2680 lines
Teaser 0:00
0:00

when AI became a thing, many people were like, PMs are over. We don't need them. >> For a while, especially a year ago, it felt like the narrative was everyone's becoming an AI builder. We moved some of our product managers and designers to a team. Everyone was the AI builder. There was no PM or designer. I remember checking in with one of the PMs in the first few weeks and he's like, it's unbelievable, man. We've moved faster than ever before. After about a month, he comes back and [music] he's like, everyone's gone back to doing their traditional jobs. We realized throughput's not our problem.

0:26

Direction's our problem. I need more people to steer the ship. >> In spite of what we keep hearing, PM should be shipping code, PM should be building. >> PMs are some of the worst solution designers in the world. Because you have access to the tool doesn't mean you're an expert at the domain that you have access to. AI is really good at amplifying your strengths and equally it amplifies your weaknesses. >> You spend a lot of time thinking about what makes a great product manager.

0:47

>> They don't own decision making. PMs own decision making velocity. The largest, [music] most important part of their job is they're literally filling context. The best PMs are the ones that are thinking about building a shared [music] brain at any scale product or software team. >> What's trending up in what you are looking for when you are hiring PMs? >> This may sound a bit spicy. One misconception I'm often debunking is you don't need to hire juniors anymore. They bring different ways of working to the team. My 12-year-old son vibe codes his own games. He's gone from scratch straight to vibe coding. He's missed the whole syntax and whatever. He thinks [music] that's normal.

What makes a great PM 1:24
1:24

>> Sherif, thank you so much for being here. Welcome to the podcast. >> It's so awesome to be here. Thank you for having me. Uh long time listener, first time caller, so it feels surreal, but good to be here. >> I get that a lot. Um you are head of AI and product craft at Atlassian. You and your team build some of the most important and influential products in the field of product. Uh Jira, ever heard of it? Um something that is very cool about you and your job is you spend a lot of time thinking about what makes great product manager, how to develop great product managers, how to hire product managers.

2:05

You spend a lot of time on the craft of and the skill of being a product manager. Let me ask just this big question and see where it goes. What makes a great product manager? >> In any medium to large organization, I'm going to focus on that because I think it's quite different to a startup. Um I think that the the largest, most important part of their job, to use a phrase that everyone loves using today, context, is I think they're literally filling context. They're filling context with humans and I guess these days with agents too.

2:34

But they're the ones who realize that the best way I can advance this product is not by me taking all the decisions and all that stuff. It's one of my popular misconceptions I love to debunk. Product managers don't own all the decisions. Um but it's about if they can build a shared brain with their team, their cross-functional team, especially their engineers. On I always say three types of context to my teams. Uh you have the customer context, you have the product and market context, and you have the business that you operate in context.

3:04

And you're always filling context gaps. Like the hardest thing I've had to do, Lenny, ever someone asked me the other day, what's the hardest thing you've ever done at Atlassian? And I feel like without a doubt it's just scaling product teams. Everything breaks. Trust breaks, shared brains break, us and them culture starts forming. In any scaled organization more than 20 30 people you're going to run into this. Um so having a job of building a shared brain as a group on those three contexts becomes key because if you can empower everyone with that context um they can move faster. I always say to PMs, your job is to stay away from the Jira backlog. And they're like, wait, what?

3:38

You work at Atlassian, you can't say that. And I'm like, no, no, hang on a second, hear me out for a sec. Run away from your backlog because why why is it that you think some card is more important than another card? There's some context that you have that the rest of your team doesn't. So how can you empower your product engineers, your feature leads, your designers, etc. with that context so that they can make those decisions themselves? Now granted you may never work yourself out of a job, but you're always filling context gaps. Because it might be a vision gap this year, next quarter might be a customer gap, might be a landscape gap. Like, you're always trying to fill context.

4:10

Um now I think the best PMs are the ones that are thinking about building a shared brain at any scale product or software team.

Why your job is to fill context gaps, not make decisions 4:17
4:17

>> So a big implication of this advice cuz I don't think many people would think this is what makes a great PM. This is a really interesting and unique take, this idea of just providing context for the team versus uh there you you even said this. Like your job as a PM is not to make the decisions, it's to help your team make better decisions and through that it's give them context. So kind of the implication here is your job is to help the team have all of the information such that they can all make the right decision versus you having to convince them or be the decision maker.

4:48

>> Yeah, I remember um early on my career uh uh remember sitting down with my manager saying like this is insane. I have so many decisions I need to make. The team's blocked on me. I like I I like I need to move in this direction and that direction that direction. And she looks at me after me venting for like 10 minutes staring in the eye and I could tell she was sort of looking past me not really listening. And she says Sharif, you just need to spend more time on the strategic things.

5:11

And I'm like how do you have time for these things? Like I'm too busy like planning the sprint, working what we're doing next, etc. And uh you realize that the best way to make you and the team scale is by making sure that everyone has a shared brain. You know simple as it can go by simple examples like I try never to do customer interviews without engineers in the room. Like you're building context in your brain. Like sure I can do the interview then get an agent to summarize all that stuff and hand it off to a human and say look here's the findings. But if you're sitting in the same call as me Lenny, like your aha moments and the empathy that you build for the customer is you know 100 times better than someone who's just handing over reports of here's my customer findings.

5:51

So you know that's an example of filling customer context. How can I do that in a way that more engineers feel empowered for that? Um but you know product and strategy context you might get your team involved in visioning together and looking at market landscape together and trying out different tools together and rather than one person doing it and you know coming down from the mountain handing over these instructions.

6:10

>> This episode is brought to you by this season's presenting sponsor WorkOS. What do OpenAI, Anthropic, Cursor, Replit, Sierra, Clay, and hundreds of other winning companies have in common? They're all powered by WorkOS. If you're building for enterprises, you have felt the pain of integrating single sign-on, SCIM, RBAC, and audit logs. WorkOS turns those deal blockers into drop-in APIs built for B2B SaaS. And now there's a new kind of user that needs [music] access to your app, agents. AI agents need to register, authenticate, and get permissions [music] just like a person.

6:45

WorkOS handles it all. Agent auth to give agents scope, revocable identities, agent registration with Auth MD, and AirLock to judge every agent action and allow, [music] deny, or escalate to a human. I've noticed that every startup that I'm an investor in that expands upmarket ends up using WorkOS because they're the best. Go to workos.com to make your app enterprise-ready today.

Examples of context-sharing done well and done poorly 7:10
7:10

I'd love to hear more examples of what this looks like in practice of either what not to do to do this badly and what you think are counter examples of a PM and or doing this context sharing really effectively. >> If you think something's more important than and something else, ask yourself why did you conclude that and like you know reverse engineer your thinking and what made you realize that and why does the other person that you're telling them that does why do they know that? And so it might be because they don't have their data points of the quantitative or qualitative data that were involved there etc.

7:44

It might be because you know they went in those meetings or they don't have that information. And so you're always thinking about what can I do to bring people along on the journey. So the best designers as a great example aren't handing over the designs necessarily. They're getting the team to co-create together and they're exploring concepts together. Now they may take that all and then finesse it and it and bring out this when the team's involved in that process, their aha moments completely change.

8:13

Um, another example might be I had a uh product manager the other day that's getting every engineer in the team to go and use different AI tools and to come back and tell them what worked and what didn't work for them. And that's something we typically wouldn't do. Like we'd say oh the PMs or the designers will go do that, but like getting everyone involved in the process um is a huge one. We I we just came out of our team our annual biannual event in in Europe with customers. We try to take engineers to the booths and engineers man the booths with me and and other people and they're fronting customers and hearing feedback and that's ways we can build shared brains together, right? So um a lot of that. Now granted you may start of your project and you take the decisions yourself and you're trying to get things going, but your job always as a PM is like how do I move away from this thing? How do I get better

8:58

alignment on the vision? They they they put this on the roadmap and I disagree with it. Why do I disagree with it? Maybe there's some strategic beliefs that I have that I haven't built a shared brain around with the team or maybe I'm wrong and they're right and so you're always trying to close those gaps. So you're always trying to find where are the gaps and then what activities can you do to close those gaps? >> So interesting.

9:16

So there's kind of this spectrum that you could think about PMs that uh of how they operate in different companies and one end of the spectrum they're the boss, make all the decisions, they are basically managers of the team. The other is they're just completely equal, no additional power of any kind in decision making. Where in that spectrum do you think PM should be? >> They're always striving uh to be in the uh equal uh no additional power. Now think about it also in theory PMs don't have an an a a PM working in a squad has no reports to them.

9:49

They they have to influence without authority, right? By definition. So and there are two operating models here. There is that I will hand over the spec and you will do what the spec says or there's the model of I'm going to get you all board into the vision and we're going to work on this together to the point where the best engineers are almost like suggesting their own features to solve the customer problems. Some of the best stuff that we've had if I share a quick example, I remember um I love telling this story because it's an old story and people are like, what?

10:14

And 2010 I remember interviewing a Confluence a set of Confluence customers and we could see that um before emoji even existed, customers were putting in these little icons in their Confluence pages, right? Um and now quantitatively you look at the data and you're like, oh people are putting in these icons, we should we should ship more icons, give them more variety of icons, whatever. And we particularly found in this one customer call that um you know, they would put these red stars and these green stars in their meeting notes in Confluence. And I'm like and we we saw this with multiple customers, like a different system they built and we're like, why are you doing that?

10:50

And you know, they would be like, oh the red stars are the things we haven't done and the green stars are the things we've done. And this engineer at the time left the meeting and she's like, why don't we just put a checkbox in a Confluence page and let them like actually tick it. And that don't forget this is 2010, no one had done this on the web. Like putting tasks in a document editor was not a concept that existed.

11:09

And she just pioneered that because of her her aha moment from observing the customer. Um we wouldn't have got that otherwise. Look, there's lots of examples of these, but when they're involved in that journey you're um you're making them the mini product managers in in each of the areas.

The GM/scientist/artist PM triangle 11:25
11:25

>> I know you also have this um framework of how you think about architects of archetypes of PMs. There's um artist PMs, there's a couple others. Talk about that because I think a lot of people they hear PM and it's like one type of person and it turns out you can be a successful PM in different ways. Talk about this this framework. >> Yeah, we we we have a a framework that is um a Geoff Redfern actually created it when he joined us. He shared it with me and we've we're stuck with it then.

11:52

You know, there's different types of PM frameworks out there. I think if you pick one and stick with one it's useful. But he has a what we call he calls the PM craft triangle that you know, one side of the triangle he has a general manager, other side he has a scientist, and the other side he has an artist. And um the the positions of the triangle represent how you might do product discovery more naturally. So as an example uh um a scientist PM will be very hypothesis driven. Think of them in growth teams, think of them as AB testing a lot, etc.

12:19

General manager PM will think more in TAM and business and profit and revenue and you know, all that kind of stuff. And uh an artist PM will be more just emotionally vision led and experience led. Uh and I found this to be a helpful framework because you the classic let's just throw a PM in a team isn't the right meant thing to do. It's

How to use the triangle in hiring and calibration 12:38
12:38

it's like don't throw bodies at the problem. Think about like what type of PM are we after and how can we best map that PM. So we use that a lot in calibration when we're comparing PMs. We use that a lot in hiring. Like you'll you'll ask a general question like what's your favorite product and what will you do to make it better. It's you can tell someone's where they sit in the triangle by how they answer it. Like the make it better answers for the general managers often like there's a new business opportunity we should go after and I think the TAM is this big and I'm going to measure it and whatever and the scientists will start with a hypothesis and they'll be like oh we could you know test these different variants etc. And the artists will just paint some visual vision and then kind of back their way into what the problems are. But they'll start with like this solution experience that

13:22

they want to paint because they feel emotionally led towards that destination for a particular reason, their intuition, their usage or whatever and they'll look backwards and so you can do that. So it's a it's a very helpful tool to say oh we need a new PM on this team and I'm like oh what kind of work are we looking at and do we need that more of an artist, a scientist, a general manager. You get some PMs that say I'd like to do all three.

13:42

The reality is I have found very few people in my career that can do all three really well. Uh and but you can get a lot of people who can do all three at a at a basic level and they're they're awesome for zero to one projects, startups etc. Like as in you need just do whatever you need to do to get to the outcome. That you need that culture a lot in smaller zero one projects or startup teams. Uh the bigger you get the more you can you have the luxury of being like we need someone just to really focus on the growth metrics of this particular product and this particular area or etc.

14:14

>> What I love about this >> there's a bunch of reasons. One is it shows you you can be successful in different ways and you don't have to be one specific type of PM. Two is this explains why you may be suffering and failing right now is you may be the wrong kind of PM for the team you're on now. >> Lenny, the amount of times I've had someone who may not be finding their groove in a particular project, swapping the type of project they're on and they've bounced back, got a new found energy. I can point to so many examples that it happens all the time.

14:44

And it's a classic of like just find the work that's most suitable to that person and just it's not about just throwing PM bodies at the problem. Uh it's just about who would have thought diverse teams still matter. What kind of person do we need in this team? Uh how do they complement the other people? What's the kind of work? And you know, you kind of map that there.

You don’t need to be great at everything 15:01
15:01

>> I know that you also have this um and I I share this this uh philosophy that you don't need to be great at everything uh and just as a as a as an employee as a as a but and as a PM as well that you don't need to be great at everything. Instead, figure out what you're strong at and focus on that. Um and it connects to this framework. Talk about just that and I think it's just this kind of myth you think a lot of people believe.

15:26

>> Yeah, it's uh it's also selfishly Lenny, it's um it it it makes me feel good. Um so the running joke at Atlassian is uh I'm like the worst general manager type person to ever have. Like like if if it's about running the business, don't give that to Sharif. Now, I'm in the exec team, I'm the head of AI, I run the product craft. And I love that people can joke about that about me because I think what that does Lenny is it creates a safe space for other people to be okay to share their weaknesses.

15:56

And then here's the challenge people run into when they run into a weakness. They they have two options. They could try to get better at that thing. Now, sometimes that's left brain, right brain stuff and they might need to work harder at one thing than it is, you know, nature versus nurture kind of topic. Or what I have found to be more useful in my career and I've I've tried to be the I'll get better at that thing, is actually find the thing you're good at and run for the heels towards that direction and ignore everything else.

16:21

And then build a diverse team around you that's good at the other things. So, I am a very heavy strong artist PM, uh but in my you know, I'm responsible for AI across Atlassian. I have a complement Jamille, he works uh with me. He is the complete opposite of me and um and it we are such a good team together and I'm so grateful for him because in my weaknesses he shines and his weaknesses I shine, but together we're an awesome team.

16:47

Um and so uh I always say if you're early on in your career, try as many things as you can to discover like we discover products, we do product discovery, you should do career discovery. Discover what you're naturally good at. Then you have two options, balance it out or just keep running towards the thing you're naturally good at. My recommendation is always uh run to the thing towards you're naturally good at, celebrate your weaknesses publicly so that you can build a complementary team around you uh and create a safe space for everyone else to to to feel like they can share the same.

17:16

>> I believe it's important to say you don't you can be terrible at things like you there's probably a baseline. You have to be good enough at meetings, good enough at strategy, good enough at artist at taste at but you you don't need to be the best at every category. >> Correct. Yeah, I think it's the um again one of those misconceptions that like everyone wants to be Steve Jobs esque kind of like I'm good at everything etc. Now lady don't get me wrong, there are a couple people in the company like I would use Mike our CEO co-founder as an example.

17:46

He will be in a strategy review with you and he'll tell you why your drop shadows are off by five pixels, why the padding and margins are off on the left here. Then he'll go tell you why your business model's completely wrong and flip it around and then he'll go and look at the data inside out and tell you something you you had no idea about. Like those people are incredibly hard to find, but um the vast majority of folks I think find the area they're good at and just keep going in that area.

Career coaching: early-career unlocks 18:09
18:09

>> Let me ask you this, when [clears throat] you coach people in their early career and then in later career if you had to pick one or two kind of most common unlocks that help them accelerate? So say you're coaching someone early career, if you think about the people that you've helped at the beginning of their career and then the second part is just later career, what are kind of the most common unlocks that allow them to all of a sudden become a lot more successful at product management?

18:38

>> Giving them an opportunity that is just above their level at the right time is key. Um and that opportunity you should be very deliberate about. It's something that plays to their strengths specifically. Um for example, this product manager comes to mind that she used to work with me in the early days of a new product that we launched a few years ago at Atlassian. And I realized at the time that she was at the stage where she was more in the scientist brain that the product was growing and I realized also that like I'm probably not the best to lead this and I stepped aside and just said, hey, you know, Rachel, you should probably take over this piece of work.

19:20

So I think it's just really about finding if you know where each person is at on their journey and you have a high you can see where they want to head and what they're good at, waiting for the right opportunity. Your job as a leader is to see that opportunity arise and then, you know, they might be moving them across to a different team or whatever it is. Um I think that is the sweet spot of giving people something. I've been fortunate to be here 17 years and like every time I've like looked around, there's a new opportunity at Atlassian. This is like cuz we've just grown so much. So and these opportunities have happened to play to my strengths. So you know, in the same token, I I need to be looking at that for the people on my team and and passing that on as well. So um I think that's key is just identifying opportunities inside the business is um such an important thing that doesn't get

20:06

talked about as much here. >> So say um early career PM is listening to this, they're going to be wondering, okay, what kind of opportunity should I be looking for that is most likely to help my career? What are signs that this is a good opportunity that may accelerate their career? >> It's probably started with someone telling you >> you did a good job at something. That's probably a good sign that that's the type of work that you're good at.

20:29

So if you're feeling like you've you've found that and people saying that you know they really like the thing I did here, this particular project, they really love how I led growth in this particular area or they love how you know I solved this customer problem in this area, analyze that type of project and ask yourself what how did I approach it? How did it work? Then your next thing is what what other types of projects that are similar that I can go do um is what you should be looking at.

20:53

Tell your manager about I always say to folks a good conversation to have with your manager is pull up one of those frameworks like here's where I think I am in the triangle, whatever framework you want. There's lots of them out there. I'd love to do more of this stuff if you're still discovering or I would love to get better at the thing I'm good at here. Put it you know tell them, indicate to them that you're after the next opportunity. I think it's a huge step you can do to to help yourself.

Career coaching: senior PM and manager unlocks 21:14
21:15

>> What about um let's say senior PM you know I don't know like L6 or even like early manager? What's what's kind of the most common unlock that accelerates their career from that point? >> I think at an L6 you you've really found your groove. Like as in so you I think you're at that decision where maybe you don't want to accelerate if you say accelerate career learning in you mean accelerate your levels. Maybe you want to go diverse as in go try something totally different. You could argue is that accelerating career?

21:46

I would still say that's accelerating your career, right? So or just keep chasing the similar type of work. I think it's key. Um you know this uh particular lady in one of my teams yesterday we celebrated her 10-year anniversary at Atlassian. She found the kind of work that she's really good at. She leads a lot of our pricing and packaging work across AI and all that kind of stuff and she's so good at it. Uh and we just she keeps finding more work across the business that lines up with that. So she's you know chasing uh that kind of work because she knows she does such a good job with that

Why PMs are thriving in the AI era 22:19
22:19

stuff. >> Okay. I want to talk about something that's hot off the presses. I've never I haven't shared this with anyone yet. Uh this I think will be out by the time this episode comes out. I'm doing a state of the tech job market report. I do this every a couple times a year. I've done it maybe three times now where we basically look at hiring trends across tech and we look at PM, engineering, design, things like that.

22:42

One of the most interesting takeaways right now that I hope is out there by the time this is out is that PMs seem to be benefiting most in the AI era. We are seeing the most open PM roles of any role. Uh, engineering is actually slowing down open Andrew roles. Design is very flat, not looking great. Uh, user research uh really not great. There's uh a hundred open roles for user research globally at tech companies right now. A hundred eight a hundred and eight.

23:16

So uh interestingly when AI became a thing, many people were like PMs are over. We don't need them. Why do we need them? Get rid of them. Uh, surprisingly it's the role that seems to be most thriving right now and I actually had a post about this that I predicted this. I feel really good about this. So let me ask you this. Why do you think this is the case? Why do you think PMs are are doing so well in the in the AI era?

Atlassian’s AI builder experiment—and what it revealed 23:42
23:42

>> I think for a while any if I could use a a misconception I've been trying to debunk for a while with especially even our customers and inside Atlassian. I wrote a post about it, but I think for a while if especially a year ago it felt like the narrative was everyone's becoming an AI builder. Everyone and if the definition of an AI builder here to make it more useful is someone who spends most of their time building software with AI and AI builder is all you need and the roles emerging into one etc.

24:08

Um, if I could share a case study I think that adds to one of your data points inside Atlassian. So what we did was we were like okay maybe maybe this is where it's headed. Like let's look at it as a craft. Let's try to create a few squads that have AI builders and we moved some of our product managers and designers to a team a few teams that ran these experi basically built product where everyone was the AI builder. There was no PM or designer, but they came from different crafts.

24:32

I remember checking in with uh one of the PMs in one of the teams and and one of our one of ones in the first few weeks and he's like it's it's unbelievable man. You you like you're constantly building. It's so good. Like I feel like we've moved so fast. We've moved faster than ever before, you know, early days. It was just amazing. Yeah, everyone's going to be an AI builder. I'm like, wow, really? Like is that where it's going to hit?

24:51

Um after about a month he comes back and he's like everyone's gone back to doing their traditional jobs. Like what sorry, what

Why throughput is no longer the bottleneck; direction is 25:01
25:01

what do you mean by that? He's like it sounds so obvious in hindsight. It's like we realize throughput's not our problem. Directions are problem. But throughput's getting cheaper. So, you know, uh I wrote this blog post internally that was, you know, direct the ship, don't row it. And there was a lot of PMs coming to us saying should I be coding? Do I need to code? And you know, quite a few of our PMs have committed code in in some capacity or whatever.

25:25

But it's very obvious in a world where we have again the new ones here is if you're a startup and everyone's moving really fast, everyone needs to do anything which I I'm fully poured into that or a zero to one project. In an engineer in an company where you have the luxury of hundreds, thousands, tens of thousands of engineers, um dozens of engineers, your problem is your direction, uh not not how quick you can pump things out.

25:49

So people who are actually helping everyone steer the ship, uh not more throughput, right? So I think that probably is in support of that Lenny. I think more people are raising there's more throughput, so I need more people to steer the ship. This is probably reflective of some of the results you're seeing on on on more PMs being hired. >> That is an awesome answer. Uh and that that makes like I imagine so many people hearing this are just nodding along.

26:12

>> Uh yes, this is exactly right in spite of what we keep hearing just PM should be shipping code, PM should be building. Um there's a few directions I want to go here I guess just like like the trend kind of to double down what you're saying, what AI is enabling is anyone can build, which is creating a ton of chaos and lot of prototypes and a lot of ideas. And uh what you're seeing here with this data is probably showing is just now the need is, what the hell are we actually doing?

26:39

Let's all get on the same page. It's like more buying. We need more buying. We need more alignment. We need all the things PMs are great at. Also, uh what is great? Is this ready? Is this good? Is this what we want? Is this going to hit our goals? So it's so it's like now that we think about it, I see this makes all the sense. Here's why we need more PMs. Uh it's so interesting that we thought the opposite would happen.

27:03

>> And and we thought the same thing would happen with other crafts, Mert. I mean >> Yeah. >> Uh Lenny, you were uh you were probably around I'm guessing um I'm going to guess your age, Lenny, so no no offense. You're probably around during the Balsamiq mockup era, right? >> Uh absolutely. >> So like you know what do we what the the promise there was everyone can do mockups. Mockups are so easy, right? Let's just ignoring AI prototyping.

27:26

And Atlassian, yeah, Balsamiq exploded and we used a whole bunch of mockup tools and it was we liberate mockups. I I learned so much through that era at Atlassian. I learned that one, yeah, everyone can create a prototype or a mockup. But yeah, actually PMs are some of the worst solution designers in the world. Like as in you you realize like uh because you have access to the tool doesn't mean you're an expert at the domain that you have access to, right? So like now some PMs, more the artist ones end up doing just generally better mockups than others. So AI is really good at amplifying your strengths and equally it amplifies your weaknesses.

27:59

Um so we learned there in that world that specialists specialists are still important and specialization is still important. Like you can only get the AI to do something as good as your knowledge of the specialization is if that makes sense. Cuz you got to learn how to prompt it. Um we saw it with the mockups era and and now we're seeing it again with the prototypes era and everyone can generate a prototype. It's awesome. I mean it certainly helps up speed up decision making and all that stuff, but it um it's a fly in the world with like all PMs and our designers. Like it's yes, everyone's circles are getting bigger.

28:28

Like think of it a Venn diagram, but the the circles aren't overlapping. It's just they're all equally getting bigger. So if they're equally getting bigger, you know, then they're not compressing, if that makes sense. The specializations are still needed to improve the quality and taste that's coming out of each of those things. Yeah, that's just often missed as well,

What PMs should actually be doing with AI 28:48
28:47

I think, that that whole topic. >> I love this. Okay. So so again, this is a a fun spectrum. On one end of the spectrum of what a PM should be doing. On one end, you are now an engineer. You're shipping production. This is part of your job now. The other end is don't even touch AI at all. Just do what you used to do. Like you you you actually spend a lot of time thinking about career ladders and calibration and what a great PM should what a successful PM looks like. So this is something you spend a lot of time on.

29:13

Which what do you think a PM should be doing in terms of AI infusing their job, prototyping, I imagine. Should they be shipping code? What do you think is the right answer for PMs these days? >> I'd tie it back up to the top, Lenny, which is their job is to make sure the team data and decision making PMs own decision making velocity. And so they're they're thinking of how can I help the team move faster? The second question is, oh, can I help me in any of those? I think that's the right mindset. So it's like if I realize that, okay, customer empathy and customer awareness is a huge problem, a context gap my team has, and I just feel like they're not making the right micro decisions because they they don't understand this persona over that persona, etc.

29:59

Then you'll probably be thinking about how can I involve them in the process, but also how can use AI in the process to accelerate them filling that context gap. I I think I would I would go back to the top and just answer that question of like look at your team today. You there's some things that you might feel like is not gelling well and go what is the context gap? And then look at how AI can help you do that. Is it because you don't have direction in the vision? So sure, prototyping might help you get a better vision and clarifying it and all that kind of stuff.

30:29

But you might realize that they don't have a good understanding of the market dynamics and you might send off a bunch of agents to do some analysis and build that with the team, etc. So, using, you know, first stating the problem with the context gap and then using AI to help solve that, I think is is the right approach. >> I love that answer. Very unlikely it will be the bottleneck for a decision making and shipping code to production.

30:52

Most likely that is the last thing that you need to speed up because that is so easy now. Unless, as you said, if it's like a startup or just like a new team or it's just a PM, for example, working on something.

What’s trending up and down in PM hiring 31:04
31:04

Okay. Amazing. So, while we're on this topic of AI, what you hire a lot of PMs, you interview a lot of PMs. I love asking this question. What do you what's kind of trending up in what you are looking for when you are hiring PMs? What are kind of emerging newer skills, habits, traits? And what's trending down? What's less important now? >> Trending up in in certainly larger organizations, I would say, again, to to be more nuanced in the in the topic here is PMs that I'd say that are certainly more of the artist type. And why that's the case is because taste has become more important than ever before when everyone has access to the same intelligence.

31:42

I think that's been covered heavily in your podcast, but I think it's certainly people are more leaning towards experience led PMs. I think that's certainly trending up. The other big thing that's trending up obviously is, you know, if anyone is in an established workforce, as in they have teams that already exist, right? You're asking yourself, how can I reinvent how each each member of my team does their job in the world of AI?

32:09

The problem you have is probably cultural change if you define culture is how work gets done. And so you're looking at one thing I often do with the interviews and the interview process is you're looking at what new culture would this person bring to the team? And that means how can they transform how we work, especially in the world of AI, right? So, asking people how they work with AI is a fascinating question and getting to the deep beyond the like I use it to summarize stuff and whatever and like actually getting to that because you're also looking at cultural ads, you AI natives or AI natives such a relative term because you by the time you kind of But like

The case for hiring more juniors in an AI world 32:44
32:44

you're always looking at like what new ways of working can this person bring? So that's probably the second thing. And the third thing, Lenny, I think this is kind of cultural to some of the narrative that's out there is around hiring people that don't know any better except for AI. And this may sound a bit spicy. Maybe their AI slop levels are higher, but they're actually they didn't grow up uh with knowing anything else. In particular, I'm talking about juniors here.

33:15

So one misconception I'm often debunking with a lot of established organizations is you don't need to hire juniors anymore. And I go, what why do you why do you say that? And it's because oh well, AI can do that for me, yada yada yada. But also as an organization, what are some of the problems you're having? And often the problem is, well, I have a workforce that needs to transform and learn new different ways of working.

33:36

And I don't know about you, but it's really hard for me to unlearn the ways I used to work and then learn the new ways of working. That's very hard. It's much easier to grab someone out of college that's basically been cheating in their university assignments or not knowing any better. Or I love using the example of my son, 12-year-old son. He vibe codes his own games. He's gone from scratch like a visual coding language straight to vibe coding.

34:00

Like he's missed the whole syntax and whatever. He thinks that's normal. Like I'm always blown away when he'll dismiss a model and be like, Dad, this Gemini wasn't that good and blah blah wasn't that good and did this. I'm like, Dude, that would have taken like four days for someone to build. He's like, yeah, whatever. And I'm like, I'm blown away and he's just like, you know. But the long way of saying is I think the third type of person you're after is And I think in particular juniors for established workforces, they bring different ways of working to the team. Now juniors are not great at identifying AI slop because they don't have the domain expertise.

34:34

But your established team, your existing team, your seniors, your people that are specialized, they can pick AI slop a mile away they know the domain really well. And so you're actually looking at how can I build a complementary team here, a complementary workforce between the juniors and the seniors so they can work together. So I would say that's the third big thing is like we have definitely overindexed on hiring more juniors than seniors because because again our context is we have an established workforce, an established team that are learning to transform how they work, which is every organization in the world.

35:06

And so you're going what what's what person can I bring in that doesn't know any better? And so we run these like AI builder weeks and they're fascinating weeks, Lenny, because like we just take a week where all the crafts stop and they tinker with AI for a week engineering design etc. At the same time is very important. The juniors or the the younger people tend to be like showing all this coolness and like demos and tools whatever and the seniors tend to focus on identifying slop, evals, quality problems etc. Like you just notice that just natural gravity and you're like wow this is diverse teams and diverse teams are still very important in the world of AI.

35:42

>> This season's supporting sponsor is DX. Now that everybody at your company is finally using AI, the question that engineering leaders face is no longer are we using AI, but is it paying off? With DX you can measure and benchmark the impact of AI adoption across your full product lifecycle. DX shows you where AI is helping developers and where it's creating new bottlenecks. You can also use it to evaluate AI vendors, monitor costs and licenses and see exactly what's limiting your agents.

36:13

That's why hundreds of enterprises including Snowflake, Sony and BNY use the DX platform to measure AI's impact on developer productivity. Visit getdx.com/lenny to get a demo of DX. That's getdx.com/lenny. Sharif, I am loving this conversation. There's so much good stuff here. Uh okay so uh on this junior piece uh very inspiring I imagine for folks listening to this that are earlier in their career um or trying to into PM from something else after school, are there any kind of trends of where the best uh junior/ young folks come from college wise? Like is I think still going to college? Are they studying computer science? Are they MBAs? Uh, anything there?

36:59

>> Uh, I don't think you have anything unique to share here. I think it's still a mix of computer science. I I spoke to our I went to our APM cohorts last week in in in Sydney and we had them all together and it was a mix of there was like some people with arts degrees, someone with a law law and technology background. So it was a good mix. Again, you're looking for the critical thinking, the the usual staff, the curiosity is super high, willingness to try different things. They they got enough fear. So they're just willing to try anything to try to make it work because they haven't done anything any other way, right? So and we we have numbers to show this Lenny both internally and externally with our customers, our research team.

37:43

So like something like almost 30 I think it's 38% posted a blog about it but like of juniors are more likely to adopt new tools than the seniors both internally and with customers etc. On the flip side, the seniors are getting more quality and better productivity out of the ones they're using, but they're less likely to try different ways of working.

How to spot the artist streak early in candidates 38:07
38:07

>> Okay. So if I were to connect to your three kind of answers of what is trending up, artist PMs, people that bring a culture of open-mindedness and and and trying stuff and experimentation because things are changing so fast, which feels actually pretty close to the third bucket, which is new newer newer workforce folks that are just AI native essentially. So the Venn diagram is essentially artist PMs who are new juniors, let's say.

38:36

So going back to the artist PM, say a little bit more what that looks like because people listening to this are going to be wondering, am I that? How do I become that? Talk more about and as one, as you self-describe yourself as what is what does that look like? What are you grade at as an artist PM? >> An artist PM is, in contrast to a general manager or a scientist type of PM, the way they lead product discovery is largely through visions. They may often actually start with solutions and work back into problems, which sounds again very countercultural because they have some intuition in some particular area.

39:09

They tend to focus on experience more than numerical, you know, more they're more data informed than data driven. Then I want someone in growth to be a little bit more data driven than data informed. You kind of want that healthy tension, right? So uh they they'll tend to do that a lot more. Um a lot of them will tend to actually a good signal is like you'll see a bunch of prototypes. The artist PM from different PMs, the artist ones will generally do the ones that seem more logical uh or or flow better.

39:38

You'll find sometimes, I always say when you're in the room and you're you're discussing a concept or a topic and someone sometimes feels they just pick up the whiteboard marker and draw, that's a pretty good signal that like are we talking about this or are we talking about that? Like uh and so often uh tend to do that. But I I think in the world where more more vendors and more software is cheaper to build, more people have the same sets of features, experience matters more than ever before and I'm not a believer that everyone's going to chat to an agent and the agent interface is the is the final interface.

40:15

I think there'll be many. Uh and so I think experience still matters a lot. So I think that in a world where just generally speaking more people can build more stuff cheaper, faster, easier, experience matters more because that becomes one of your possible differentiators. And so those artists tend to kind of be a better asset, well not a better, a good asset in that world. And so you're trying to complement your workforce to make sure you you've got a mix of these skills.

40:42

>> I imagine it's hard to actually find that combination of a new entrant into PM and very good at this because my suspicion you need to do this for a while to build that gut feeling and the you know the artist experience. True or or not true? >> Someone just sent me we asked all our APMs from last cohort the new cohort coming up to record a loom of a take home exercise and I watched a few of them week before last actually and it was fascinating again to see how again they don't have domain experience but we gave them an exercise to build an app for a particular thing and to see how they chose to present it and lead the narrative of why they're building this particular app whatever.

41:25

You you do pick up the artist streak in them very early on. You can see the ones that will as an example there was a loom of someone that went through and they walked through basically graphs before they even got to any experience and they were like here's the business case here's the TAM here's etc whatever whatever and they were like here's experience and they spent very little time on that in contrast to this other candidate and she walked through the end-to-end journey and talked about like it's funny talked about the lighters and like I think this will be a way to build an emotional connection with someone again don't have to don't have any domain experience but you can see the way they tended to do product discovery tends to be more visual than than the than the other person. So you can at least identify that streak early.

42:10

I mean Lenny I've got two kids my son's really good at maths and and logic and whatever and my daughter just loves drawing and just naturally we put them in the same household we read to them the same books as kids at least I think we did but you can just see the natural their preference in in their style of how they how they work and how they think and so I think that there is a bit of nature and nurture here as well.

42:35

>> Yeah so the implication here is it's not like you can you train to become an artist PM archetype it's mostly you that is how you are as a person and then you build enough experience actually to be good at it. Like I know I'm sure like tell me if you disagree but it's probably this is you and then you can become better at it and you can probably learn how to do some other things better, but I don't know. Yeah, you're nodding along. You're you're >> Yeah, I I think it's easier to to accelerate at the thing you're naturally good at and it's harder to accelerate the thing you have to learn to do, right? I think that's that's applied to anything. So is it possible to train artists? Yeah, totally. Um and you can at least help people identify things or whatever and um it's just harder, right? It's um it's not as uh easy for that like to do.

43:18

>> I love how like it's another counter narrative, I think that's the word you've been using of like okay, we don't need junior people anymore or they're done. They're there are no careers left. Like you could argue they are the only people that will want to hire now. Um I don't think that's what you're saying, but it's like these are the people that are so open-minded and so uh native with what is possible now and not stuck in this old way that that's maybe who we need and the people stuck in the old ways are not are only slowing us down.

43:44

>> It's the theory of diverse teams is still true today and even more true in the world of AI. Like it's it's just so true. >> So this data that I've been seeing of uh designer roles not growing, there's just been like a stasis in the number of designers being hired in tech. Um I wonder if it's because basically PMs are filling in more of that of that gap as you've been describing. PMs basically kind of being the not I'm not and I'm not saying designers are not very useful and amazing and important.

44:13

Uh and I um I'm surprised that designers aren't thriving more in this era where as you said, the experience is a huge opportunity and differentiator, but that's just what the data is showing right now and I wonder if it's because PMs are filling in more of that gap. >> I'd love to dig into that one. I think there's some other hypothesis I would have like >> Hm. >> Another hypothesis I would have, I don't know if this is true or not, is that the market still hasn't got past the aha moment for experience matters more than anything else. I mean uh in the world of AI, maybe if you rewind back, we said all PMs are going to be builders one day and I think we're learning that's certainly not the case.

44:52

I think there's still a misconception to be be be debunked or proven that design is more important in the world of AI than ever before because if everyone has access to the same thing, one of the or at least things that will matter is >> That's what I was thinking. >> you why you prefer something. I I I think that's just a reflection of possibly where we are. That's that would be my leading hypothesis. Um I can just say it Atlassian.

45:16

Uh uh we design has never played a more important role in roadmap driving than ever before. And I've been here for 17 years. Um uh and I am fully convicted by like experiences will matter most, yeah. >> Wow, I love that. Uh let's uh takeaway stock up on your designers right now, buy low while it's on no one's realizing that's the opportunity. Slow it up. Put them in the in the garage with your spare water. Uh okay. I I like yeah, I've been feeling the same thing and it's interesting. So your feeling is maybe we're not yet realizing that this is a huge uh opportunity in the way to differentiate and and win.

45:58

>> Yeah, I mean um we'll we'll we'll see if that that theory is correct. That's my current hypothesis, yeah.

When starting with the solution is the right move 46:05
46:05

>> Cool. Okay. Um I want to go back to a couple of these uh counter narratives you mentioned because I think they're really interesting. One that you touched on a bit that I think is worth spending a little more time on, which is not starting with a solution. Uh PMs are constantly told do not start with the solution in mind. Yep, start with the problem, with the customer pain. Uh don't even don't even talk about the solution yet, all that stuff. Your feeling is that's not actually true in a lot of cases. Talk about what you've experienced, what you've learned there.

46:39

>> Yeah, I think it's again one of those misconceptions. It's a classic easy thing when you're in a meeting and someone says something and you want to look smart, you'd be like well, slow down everyone. What's the problem we're trying to solve? And that's like yo, that person really brought some >> a step back. >> Yeah yeah, nice Lenny. You got that one. Um it's a good question to ask honestly. Yeah, what's the I think it's still a good question to ask. I just think it is what's not talked about enough is sometimes it's it's a great way to start with a solution. So a few examples if I could run through them, I think one um, sometimes it's okay to start a solution when you're trying to discover, you feel like there's a hunch in the area, you're trying to discover what the things you could productize are.

47:20

Uh, maybe some recent examples at Atlassian we have Rovo Rovo Chat, which is our AI assistant if you using our platform, um, and Rovo Agents. They're agents you can deploy in loops inside Jira workflows, Confluence workflows and so forth, etc. And believe it or not, Lenny, again, three and a half years ago when we created agents in Rovo Chat, three and a half, yeah, geez, AI, it's gone fast. Um, we were debating if we should put these in there because the the the theory was why would we put like a general chat in there and why would we put agents in there and let people create their own agents? Why don't we productize, like build the feature that people want, don't give them the general canvas, right? So let's not put chat in there, like let's not let's put a summarize button on top of Confluence pages rather than having a chat button to to do that.

48:10

And what you often learn is actually if you give people a canvas, it's sometimes the fastest way to discover what the main problems are and productize some of those problems. So as a simple example, in Confluence whiteboards, customers can draw sticky notes and collaborate with them whatever and you know, one of the common scenarios is you might use Rovo Chat to group sticky notes into common themes. Now chats not, maybe to tie back to our experience discussion, chats are a terrible experience to do that visually, like you're typing, you're kind of like filling out of them which sticky notes do you want to group into themes? How do you select them?

48:44

And so obviously you can productize that feature and that team lets you select a bunch of sticky notes and decide, you know, I'm going to group these ones into different themes and AI goes and does that for you. Really good example where you productize the use case the chat had, but chat was the infinite use case. Um, another example is uh customers love putting and we have like nearly 10 million agents that run in loops every every month inside Jira and Confluence and you know you you want to give a ticket and you know a ticket to an agent and the agent picks it up and does the triage or agent generates the code or agent reviews the legal contract whatever it is.

49:17

That that's quite common inside Jira. People put agents in loops. And so like we can learn what kinds of agents they're putting in loops and for some of them we're going to leave them as the infinite use case. Let let let customers build their own. And for some of them we're like actually we're going to build an AI triage feature and make that native to the product. And so starting with the customer solution and understanding what the customer is doing helps you work out what the problems are and then you might productize their manual workaround into a a set of capabilities into your product.

49:45

It's a pretty common tactic. Um, I think I've heard some people refer to it as paving the cow path. Like you know there's a uh uh you know there's a walkway and there's a cow that walks straight in the middle across the grass and you're like well why don't we just make that the cow path? Uh and so starting with a customer solution there is a really good uh approach. The second big one really is strategy product strategy.

50:05

The best product strategies are starting by looking at what assets what solutions do you already have today? Because you need to answer where do we play and how do we win? And to answer how do we win you have to look at what unique things that we have as a company as a business as a product right? So you know classic the example everyone I love to give people is like the Amazon bookstore is such a good example who built this ridiculously sized bookstore. It's a huge inventory.

50:31

You know like if you read uh Jack Bezos's book is like what other things he's starting with a solution what other things need a ridiculously large inventory that is a crazy scale? Oh what if it was an everything store? Like do you know what I mean? Like so so starting with a solution for product strategy thinking is another good tactic. You know I said to teams write down what assets you have today then write down your beliefs and see if there's any connection between those two of where things will head uh and do that. So you know giving people a canvas to try things and productizing the solutions they manually built is a good strategy.

51:05

Uh and so is when you are doing product strategy, start with what solutions do you have today and what unique problems can you solve with them? >> Got it. Okay. So it's nice to have here's the paths where starting with the solution's good. Uh you're not saying always start with solution or it's always beneficial. It And essentially in most cases you actually don't except in these two situations. >> Yes. I would actually don't know if it's most cases, but it is important to understand the cases. I would say that a lot of customer discovery is by learning what customers are trying to do with your product and then trying to make that better. So you're actually observing a customer trying to create a solution for themselves in most products.

51:46

And then you're like, oh, let me make that better for you like, etc. So it'll be fascinating to try to come up with a percentage is that most of the time you you know, you're actually implicitly starting with the manual customer solution uh if you like. Um I think it's a good thing good thing to to think about as you go into do exploratory, which we which by the way with AI teams are doing enough of just talking to humans.

52:08

Uh it's become much easier to stay behind more dashboards. >> By the way, I didn't know so you guys have a I didn't know you had this product uh the whiteboard product. I didn't know that was a thing. So this is like Miro, FigJam ish? >> Yeah, Confluence whiteboards is huge. Yeah. So yeah, customers can embed whiteboards in Confluence and they add agents to them and they collaborate real-time collaboration and sticky notes turn them turn them to Jira tickets, all that kind of stuff.

52:29

>> So this is like a feature within Confluence. And and it's Okay, cool. All right. Folks don't know that it is I didn't know it existed. This is this is great good good marketing for the whiteboard product. >> Didn't intend it to be as marketing, but it's a good example I think. Yeah.

Why “bolting AI on” is often the right product strategy 52:42
52:42

>> Okay, cool. There's another counter narrative that you have which is around AI and this kind of um concern people have with just bolting AI onto stuff. And your feeling is that's actually good in many cases. Talk about that. >> This is where the catchy headlines Lenny. Um it is very catchy to say don't bolt AI into your product. You should reimagine the workflow. I I I I certainly believe that. I but however, the nuance is, I think if you have an established product, you have something ready today, the best way to reinvent your product to be AI native is to understand the flows that exist in your product and literally bolt on AI to them.

53:23

Which sounds dirty. Like you may not market it that way, but actually, now just think about it for a second. You've got a product. The product has millions of users. What I see some people doing and I talk to a few startups they're like or a few product companies they're like, we're going to rewrite our product from scratch. I'm like, you don't think you can do that. Um, but isn't the better way to actually work out is how to to evolve, not like totally transform.

53:48

So the example I love to give is the Rover Agents one I just told you about is a good one which is um, customers have already modeled billions of business workflows in Jira. Just as an example, like Jira is like largely used by many non-software teams. It's a misconception most people have is Jira like many for a while you like you get a app approved in your App Store, went through a ticketing system like Jira. It was Jira for a while and then it goes through a whole review process like if you complain about your uh particular service with the telecom company goes through Jira ticket. Like so customers have billions of workflows already modeled on on our platform as an example. And so when it came to like understanding how agents help humans move work forward, we looked at what are the human workflows that exist in the products. That's a good formula to go what are the human workflows that exist

54:34

in my product? Some of them are rigid workflows as in someone's literally defined something. Some of them are informal workflows like lowercase w workflows. They're humans doing something. And then you can go, where can, you know, agents assist with steps of the workflow to generate new value, improve efficiency or something whatever it is. And so in Jira workflows, we basically added the ability to add agents to columns and cards and whatever.

55:01

Is that bolting on lady? Let's use another term. Like maybe like if I was building an AI native work tracking tool, that's probably what I would do anyway. Like, I would build the workflow and then let the agents work on bits of the workflow. And so my message to teams out there is like, hey, yes, reimagine the workflows. You should do that as an exercise. But look at where your customers are today. And if you have an established user base, an established user, it's your job to help them move from AI novice to AI native.

55:30

And so you're trying to transition your customer cohort across as well. And so think about where they're working and where you can slowly introduce AI in those workflows. So again, another misconception there, I think that from a marketing perspective, yeah, you probably wouldn't say bolt on, but literally that like we literally let you bolt on a agent to a Jira workflow and you stick it in a loop and then the agents work in loops and they run you know, millions of times and whatever and you they they're measurable value.

55:57

If it doesn't work, you kick the agent out or you make the emails better for the agent. There's a whole bunch of

The importance of nuance over hot takes 56:01
56:00

stuff you can do there. >> I love all these takes. There's uh when we before we started recording this asked you what's what's the goal you have for this conversation and you talked about how we need more nuance in the conversation of building product. There's all these hot takes uh these really you know viral clips that go out and people are like, oh, that's how I have to do it. And like I'm guilty of people on this podcast saying a thing and then people at a company taking that and this is the way to do it. Lenny's podcast said that's the way to do it.

56:29

Uh which I hate. Uh but and so I love that that's kind of what you're trying to do here is add a lot more nuance to all these what people think is is true. And um and show that it's not you know, we've got all these spectrums and gradients that we've been talking about. Maybe just say more about that why you think that's important. >> You know, the classic thing in in product I think especially is like every advice you've probably got on how to do product, someone probably has a counter totally opposite advice that works just as good.

56:59

And again, you as a product team or a PM or a product leader, you're trying to understand the context in which their advice worked in. And and that's where a lot of the nuance gets missed. You know, the builders one Lenny that we just talked about is a great example where like I think zero to one projects, even in large organizations, you should put an AI builder type onto it. I'm fully convinced into that. But again, most organizations that have access to developers, this is not their problem. Their problem is where to direct the ship. So the context in which the advice is given is super important. Just like start with the solution, not the problem. I I would equally advocate to start with the problem, but not enough people talk about the the counter thing. Um it also just gives people confidence in like am I doing things the right way? And I'm like, is there a right way? Like is it like

57:46

um you know, if you do something and you've learned something, share it with the world. Like I I would often you know, for a while I used to try to write blog posts about like I would share every craft lesson I've learned, you know, that you know, one of the most uh things we're talking about internally is that how do we scale product management inside Atlassian? And I go back to when I started at Atlassian the window product managers on Confluence, the way we did that was these things called product engineers. And I learned what a product engineer was and I I had realized there was no term codified out there and I wrote a blog post about what I learned about product engineers, whatever.

58:19

And you realize product engineers help product managers scale. They help you they're the champions of that shared context that you we talked about earlier, right? So all those nuances, you're like you know, I I don't think it talked about enough, but I I appreciate you running these these talks and hearing people out share their nuances. I think that's that's what needs to happen more. >> Yeah, it's tough. Like I'm in a tough spot sometimes where people share an opinion and many people are like, that is wrong. Why did you give why did you not push back on that? I find the best thing I can do that skills is have different perspectives here and not try to, you know, have everyone like get everyone in line. This is the way to do it. And then people can decide here's what fits for me. Someone actually built a really fun project. Uh so I don't know if people know this. If you go to lennydata.com, you can

59:04

actually uh connect an MCP that has all of my podcast transcripts. You're going to be in there. You're going to be slurped into this MCP soon. [laughter] Uh and it's also all my newsletter posts that you can use it any way you want. And somebody built, I think it was Nome actually, Nome Segal, uh built a tool that's like shows both sides of every debate. >> Oh, that's awesome. Like the contradictory advice? >> exactly. Yeah.

59:28

>> That's so good. Uh and and then you want like that'll be a I'd love to see that dashboard and you'd love to see why it worked, like this advice and why it worked and this advice and why it worked. Um uh is a is a is a it's such a that's awesome. That's so good to see. >> Is there anything you want to say that'll feed into this MCP that'll be forever part of the data set? >> I think I've given quite a few misconceptions here. So we've talked about misconceptions of uh builders, everyone's a builder. We've talked about the misconception of uh all all PMs are the same. I think artist, scientist, general manager is one framework. You can you can do that.

1:00:04

Misconception of um PMs make all the decisions, right? I think that's another one we talked about. Oh, management. Management's another one, Lenny. So like uh you you uh you everyone runs into their career in product management and usually in most organizations you hit a path where you Hang on a second. I want to be involved in that strategy discussion, that strategy offsite. Oh, but it looks like the people that go to that thing or do that activity seem to be managers. I went through this experience myself.

1:00:34

So therefore I need to manage. And they hit this fork in the career where they feel like that's the decision. And uh and so the other I think misconception we need to help debunk is, you know, I think we try to do more of this at Atlassian. You know, we have multiple distinguished uh product managers and engineers now um where they work at the executive executive level. And so we're huge champions of the dual track career paths for individuals and uh managers. And some a lot of people switch between both depending on the season um they're in. Or they think they're starting a zero one. They'll go to managing a small team for a while and then they'll get big and they'll move back off.

1:01:12

And we should celebrate that more because it plays to that person's strength. Um and so that's another that's another misconception like to to be involved in large strategic decisions at exec level at large companies. Um you need to be a manager. No, we have a lot of individual contributors that that contribute at the exec level. Yeah.

Why managers still matter 1:01:31
1:01:31

>> Another sure uh counter narrative that I've been feeling which is that there's always talk of we don't need managers and that managers should be IC as well. And I feel like that's just not a good idea. I feel like managers are actually very important. And I feel like to be a good And I feel like to be a good manager, it's very hard to also do IC work like meaningful IC work. >> It's uh really hard and so you can take two world views there that you could take if you're going to manage manage a lot. So take like 10 15 people or a we want managers that will take three or four and own a project as well.

1:02:08

And and the reality is we have a mix of both at Atlassian. Um and uh again try to play to each person's strength. Um and that's how you'll get the best outcome. And so do we have we have the span of control for managers. We generally try to say you should have at least three or four people minimum. I think most are in the eight or nine I could something like that. But it um yeah, you do have some managers that will take on few people and will own projects.

1:02:38

And some that will take on a lot and play coach role uh a lot more.

The most common mistake new PM managers make 1:02:42
1:02:42

>> Let me ask you this. Uh um for new PM managers, so you just got into it, what do you find is the biggest issue that they run into slash thing they should probably be working on? >> They the number one thing I've seen is they go too hands off too quickly. And they think that's the the best behavior. Um I would it sounds a bit counter cultural. I think the best leaders that we've ever had at Atlassian that continue to be there, the best managers, I shouldn't say managers, managers, leaders could be two separate things.

1:03:16

You could have a leader who's a good manager, a manager is not a good leader and vice versa. Um, so the best managers who are great leaders, um, are able to go in with the team and help them get through outcomes. I can sit in a product review, Lenny, I'd be like, this this isn't simple enough. And it's not like the team was sitting around going, all right, let's let's oh, sorry, I forgot to write simple to the agent.

1:03:38

Like like as in um, but the best managers are like, let's explore some options together and they get in and they help the team work together and get through the outcome. Uh, I think that was that would be my number one observation of they got so hands off and they're like, I'll just I'll I'll almost zoom out completely and let the team do that, which is good. You need to create space. Don't get me wrong. But the teams love it when they see managers lead by example. So I think it's going to be

How to work with visionary founders and strong stakeholders 1:04:05
1:04:04

more important in all of AI. >> That's great advice. Okay, possibly final question. Um, I've heard from a bunch of people that you work very closely with the founders and execs on the big product keynotes that the founders do. >> I love keynotes. >> Something most people don't say. Um, you also work with um, the CEO and co-founders on their like founder presentations, things like that. What's something you've learned about working with, you know, the top of the top that might be helpful for folks that are maybe struggle working with execs?

1:04:37

>> There are so many uh, uh, dangerous last question, Lenny. Um, without a doubt, I I describe working with this as someone who's a strong visionary leader, um, often in founder led companies that's still the case, etc. It's like me and you watching a movie and they're on like scene, you know, chapter 10 of the movie and you're on chapter three and the rest of the teams are on chapter one. And they're saying stuff or whatever and you're thinking, wait, what? Like you're like, are you sure? Like that's everyone's first reaction.

1:05:13

Now, you can do two things at that point as someone who works with that stakeholder or leader or vision leader, etc. You can say, I'm going to follow orders and go do that and just pass that on. But the the dangerous thing you do that is you're doing that with no conviction. You're doing that because the boss asked me to. And or your job could be like By the way, you know, the vast majority of the time you could argue was a was a stakeholder or the founder right or wrong. My my experience they've been right 99% of the time.

1:05:44

It's just what I've realized is they've thought about that thing far more than anyone else. And the aha moments that got them there, my job now is to fill that context gap to work out why did they get there and do I feel convicted of their thing? And I often start by like I don't know man, I'm still working through this. What made you leave that conclusion? And I'm trying to get to chapter 10 as quickly as possible. And once I get to that I know now what I need to do to bring the rest of the people along with me.

1:06:14

So I would say often with these leaders they're thinking about things a lot. And trust start by trusting but they it's not I think the counter narrative here is the hippo highest paid stakeholder whatever I can't remember the acronym was the highest paid opinion >> person opinion >> Yeah, I can't spell people and I totally butchered that one. >> Highest paid person >> Yeah, so I think the flip side is oh there's some stakeholder who thinks this is this is their pet project and whatever. I think that's certainly true in companies don't get me wrong.

1:06:42

But I think when you have someone that you know that has thought about this domain particularly well, especially in the enterprise B2B space you know I would say to someone like you can find if someone's worked in this space for several years, it is vastly different to I did a year here and I did a year there. It takes time to make large changes and whatever. And so assume they're right and assume you're wrong. And try to fill that context gap and sometimes you'll prove them wrong but it's not the goal here. The goal is to get the best outcome for customers.

1:07:09

And so then you can bring the team along on the journey, you know.

When you disagree: a framework for transparency 1:07:12
1:07:12

>> Let me ask you what happens if you actually disagree because I think a lot of people feel this like go through this and they're like that is a bad idea. Tips for handling that? >> So if you feel like you've caught up to the >> aha moment and you're still disagreeing and you feel like you have a good case for why you disagree, I will still state that. And then I will state, is this something you have crazy conviction for? And I'll say, are you the decision maker or am I?

1:07:35

Like I'll ask that. Common question is who owns this decision? Like just be super transparent. And if they really feel like I would like to take this decision or or I want you to decide I disagree, but I want you to decide, but which by the way they do a lot more than you'd imagine like they'd be like I disagree with this, but I want you to I want you to own that decision. Um but I will back you if I disagree and I will back you and move along with it. So transparency is key to to foster that relationship.

1:08:02

>> So but what do you do when you're communicating it to your team and you disagree anything there? Is it stand behind it always? >> Oh no, I'll present both arguments. I will state why I believe one argument is more superior than another and I'll equally argue for the opposite. There was a recent example where uh you know we were we were branding a particular thing and whatever and I I think it was like the best of the worst decisions we you know best of the worst options we can make.

1:08:27

And I'll say I think here are the pros, here are the cons and if you argue for the opposite, I think here are the pros, here are the cons. We have decided to make this decision. I'll try not to call the individual out. And they're both they're both legitimate trade-offs. And we're moving ahead with this one. Um and you need to speak the room of what the other opposite argument that everyone's thinking and represent that appropriately. The best PMs I find can counter like argue against themselves and present you really good reasons why they shouldn't do the thing.

1:08:55

The really blind ones will be like, oh yeah, my thing's the best. It's you know we should definitely do this option. It's the best option of all. Then like often say, why would we not do this? I love asking that in reviews. And then sometimes like I haven't thought about why we wouldn't do this. And I'm like, you should argue for the opposite as well and feel like you've intellectually wrestled with that and then move forward.

1:09:12

>> That is great advice. Something that I'll mention briefly um when I found when someone with power uh sent shares an opinion, a lot of times people take it as that is what we need to do. And Dharmesh Shah has this really great framework he calls flash tags. I don't know if you know this, >> Yep. >> where you basically says okay, he's like hashtag FYI. So when he shares an opinion, it's like okay, this is just an FYI uh or this is a suggestion or this is a recommendation or this is a plea.

1:09:42

>> Yep. >> And he's and it's a nice way for someone that implicitly has power to communicate okay, this is how I feel. Just an FYI, you don't have to do this or it's a plea, please do it. >> Yeah, and I'll say um those are like our founders do that as well quite a bit. They'll say strong opinion, not my decision, blah blah blah. Um I will tell but often you'll get people just in the in the in a discussion, they won't pre you know hashtag their discussion as they talk. And so I'll say to PMs, your job as a PM is to be the person in the room to ask that clarifying question on level of uh conviction on the topic. And you know, just to be clear, you know, you you know, the classic playback technique at the very end, but like as part of that process be like this is a conviction we will go and explore further or this is something we will take as input and then make the decision ourselves and be clear with that. So I'll put that

1:10:32

back on the PM sometimes cuz the stakeholder doesn't always do the hashtag at the end of or before or whatever it is, you know what I mean? >> know, man. Feel like we could talk for hours of all the tips and tricks and tactics you've learned this could go on forever. I'm going to I'm going to end it here so that we have time for another episode someday to go deeper. Um

Final thoughts 1:10:51
1:10:51

but before we get to a very exciting lightning round, is there anything else that you wanted to share, anything else you want to double down on before we get to our lightning round? >> I think to your listeners, nuance, I think we've talked about the nuance is important, so please uh like share your stories. I think the other thing I would just highlight is you're a product of someone else creating opportunities for you.

1:11:16

So ask yourself who are you creating opportunities for? And if you can't think of that name listening to this podcast or watching it, try to find someone that you can champion, be a be a voice for etc. because you believe in them and you you know you want to give them a go and that kind of stuff. So, uh just remember where you came from is a long way of saying that.

Lightning round 1:11:37
1:11:37

>> I love that. Well, Sharif, with that we have reached our very exciting lightning round. I've got five questions for you. Are you ready? >> Let's let's go. >> Let's go. First question, what are two or three books that you find yourself recommending most to other people? >> Look, I read it I read with my kids a lot or read books with my kids. Lately we're reading the Prison Healer Yvette Noni, I think her name is. It's a like a fantasy book in a prison scene, dystopian prison kind of escape story.

1:12:10

Awesome read with my kids. I like I I personally read the Bible a lot. I think it's a book that I just keep coming back and meditating to and gives me some kind of grounding in the world of where AI is headed as well. But like most of my books are are kids books. The other one I read with my kids, Wing Feather Saga is such a good read. It's about a bunch of kids who are heirs heirs to a kingdom and they don't know that they overcome adversity to get there and stuff in it. So, I read a lot of kids books. Yeah.

1:12:42

>> Favorite recent movie or TV show? >> Project Hail Mary was awesome. I I mean I cried a lot of movies, so it's probably a better like yeah, just totally loved it. Awesome watch, very thought provoking, emotional. >> Fun fact, my cousin is the Russian scientist in that movie. >> That's awesome. >> A little somewhat distant cousin, but still related. She's killing it. Okay, next question, favorite slash most interesting AI products that you've recently discovered or just are really hooked on?

1:13:16

>> This is total recency bias. I mean there's a few favorite AI products, but like I'm just going to go with a massive recency bias. We were on a long drive with the kids and Google Maps added Gemini to Google Maps, at least in Australia and Apple CarPlay. I don't know if you've seen that or not. And so when we drive, we typically put on sometimes we put on music, sometimes we put on AI and play a game. We play like a road trip game or we'll play a quiz game and we'll take turns or whatever it is. We everyone will be yelling at the AI while we're driving.

1:13:44

It's very entertaining. But it's was fascinating to see in the map view Gemini added because we just pressed the like it's such a lesson in product workflow proximity. Like I'm in the map. I'm not going to close it off and switch and open one of the AIs to talk to it. I'm just going to chat to Gemini right here. But it's super contextual to the trip. So be like, hey, we're heading to this destination and we started playing some fun quiz games about the destination we're going to etc.

1:14:09

And it was just one of those delightful experiences in the car that I'm like that was awesome. It was a fun experience. I could still see the map and talk to the AI at the same time. The kids had a blast. So it was entertaining. Got them off the screens for at least 30 minutes. >> Did they just bolt AI onto it? >> Oh, nice. I like how you did that. >> Call back. >> They bolted it onto an existing workflow. Some of the best strategies you'll ever do. Nice. Nice, Lenny. I love that.

1:14:32

>> Example of you being right. Here we go. Okay. Uh two final questions. Uh favorite life motto. Is there a motto you often come back to in work or in life that you find really useful? >> People tell me I'm very relaxed and fun at work and always joking. It's usually how I deal with my nerves to be honest, Lenny. Uh but they ask me like why etc. And like I'm always reminded that like you as a person is decouple yourself from your job identity, which is really hard especially in the world of tech.

1:15:04

Um and celebrate the individual outside their work life, I think is an important thing uh that we don't we don't do enough. And um you know, I love playing footy which is like like flag tag uh with a bunch of uh folks who live locally and none of them work in tech. And uh you know, they're just a mix of electricians and bricklayers and whatever and different jobs. But like um they're amazing human beings that don't work in technology. And so reminding people to decouple themselves from their job as their identity I think is something that's healthy uh and will keep you sustainable in your work and in your personal life as well.

1:15:43

>> I will share a quote that uh has come up a couple times on this podcast that it always hits people right in the right in the heart. The only people that will remember that you worked late are your kids. >> So so true. Uh I've read a similar one which is nobody goes to a funeral and the tombstone like it's saying on tombstone this person worked so hard or whatever like that's never in the eulogy or whatever so that's a that's another motivator yeah.

1:16:06

>> They hit the quarterly number. [laughter] All right final question I've been wondering what is going on behind you? There's like all these fun things that happening uh what is what is this explain? >> Uh Atlassian t-shirt culture we make a t-shirt often to tell a story about a moment in our history. So this is like confluence questions was an app that was uh when we had our first QA team that was when we launched a Vietnam office.

1:16:33

There's a story behind each one of these shirts and uh I love collecting them just a great way to tell stories when the bigger you get the stories become more important to to tell the teams and I've got hundreds of these shirts and um one day my wife ripped up my shirts and uh surprised me for a thing she did for my birthday and created up this giant plaque uh this huge uh shirt and stitched together some of my favorite shirts that have stories behind uh each one of them so that's what that is.

1:17:02

>> That's very sweet. I could see that going horribly wrong. What did you do to my shirts? I've been saving these for years. >> I uh wrote a blog internally that was titled my wife ripped up my Atlassian shirts and people like what and then they read the details and whatever but then for our recent uh 20-year anniversary as a company I I just walked through 110 shirts and recorded a video on YouTube it was it was a lot of fun and just like the story behind each one it was just very satisfying.

1:17:27

>> Let me ask you this what's what's uh unique cultural kind of uh ritual of Atlassian that might be fun for people to learn of? >> Uh there's a lot. We are an incredibly transparent company. Uh open company is one of our values. Um like as in every exec review is usually recorded, available to search and find and loom and ask questions and you know run the AI agent through it. So the transparency here, everyone that joins says I've never experienced anything like it. I mean I haven't started a lesson for a long time so I'm used to it, but they're like oh my gosh, when do you stop reading?

1:18:00

Like like there's so much content. So I would say open by default is the ironically Lenny. I think it's also I mean partly because of confluence and the nature of we have of the product we have. People just document and and create and it's open by default. But sharing context is key in the world of AI uh and um and so uh having an open by default approach to things is actually better in the long run for you as a company because they're by definition it means there's more context that the AI has access to and the humans have access to. So the uh openness is is unbelievable here, but um it's it's pretty crazy, but uh people love it.

1:18:41

>> That is that is super interesting. There's there's been a number of companies over time that have done this. GitLab is a good example. And it's interesting now with AI being able to read all of the things and tell you what you need to know. It changes that and like in theory you could like it might expose things that maybe people shouldn't have seen much more easily and quickly. On the other hand, it gives you all the context as you described to make better decisions.

1:19:06

>> I have this theory Lenny. So we have we have a team anywhere policy so you can work any way you like. We have a legal entity so some people choose to work remote a lot. Some people don't. And so just as an example, you know when um I have part of my team is in the West Coast of the USA. They a lot of them like an in office culture. And for reasons and some people in in the APAC region love a distributed culture. Uh I have a theory we're trying to prove out right now, hypothesis, which is those that are remote are more likely to get uh more outcomes out of AI then those are co-located.

1:19:40

>> Mhm. >> Uh and so we're just got a bunch of data scientists trying to prove that out right now, so that'll be a fascinating theory. And the the thing here is that you just tend to write more and share more digitally when you're remote. >> And consume. Yeah. >> Yeah, and when you're in person you just whiteboard more or whatever and they're both good approaches and you need both. But it's um it's a again maybe another counterpoint of the going back to in-office culture maybe.

1:20:04

>> Uh going back to this report that I'm putting out actually remote work has plateaued. There's no it's kind of stalled at 10 15 20% across industries, so that'll be interesting to watch if that grows again with AI. Anyway, I keep asking you questions, but we should wrap up. Uh Sharif, this was awesome. This was such a great deep important conversation that I think is going to help a lot of people. You're talking about opportunity. I think this is going to open up a lot of new opportunities for folks, so uh thank you so much for being here.

1:20:33

Um any is there some way that listeners can be useful to you? That's my final question that I almost forgot to ask. >> If you see something in social media, lovely tag headline on one line grab you shouldn't hire juniors anymore or whatever it is whatever it is you see be the person that asks the nuanced questions and be like what why did that work for you? Why didn't that work for you? Don't be the person that amplifies that one view without first understanding the context.

1:21:01

I think that applies to many things in society, not just product, but yeah. >> Nuance. >> Yeah. >> Um amazing. Sharif, thank you so much for being here. >> Appreciate the time and the opportunity. Thanks Lenny. >> I appreciate you. Bye everyone. Thank you so much for listening. If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify, or your favorite podcast app. Also, please consider giving us a rating or leaving a review as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at lennyspodcast.com.

1:21:34

See you in the next episode.