How Do Product Leaders Earn Trust and Plan?

TL;DR

Earn trust by bringing specific insights grounded in customer needs, market dynamics, competitors, metrics, and product knowledge. Strong product organizations pair that credibility with problem-focused teams, nested success metrics, rolling planning, rapid prototyping, and permission to pivot or stop work when evidence challenges the roadmap.

Transcript

you're often the youngest person in the room what have you learned about how to Garner trust and win over Skeptics the thing I would say is bring the Insight know that I customer Know Thy Market know like competitors know like numbers no thy product I'm curious what you find most holds back new PMS your brain is so accustomed to having a scarcity m... Read More

Key Insights

• Trust is earned by bringing relevant insight into the room. Costello recommends knowing the customer, market, competitors, numbers, and product so that confidence rests on useful evidence rather than age, seniority, or presentation alone.
• Scarcity thinking can prevent product managers from recognizing alternative paths. Asking how the opposite might be true can loosen a rigid assumption, reveal that apparently conflicting options may coexist, and reduce the tension attached to making a difficult choice.
• Asana's core product organization is responsible for its desktop, web, and mobile applications. Its work includes goals, portfolios, projects, tasks, and reporting, all directed toward creating clarity for individuals, teams, and organizations.
• Clarity at work means understanding purpose, plans, progress, and responsibility. Asana frames this through the practical question of who is doing what, by when, and why, because greater certainty can help people complete work more efficiently.
• Durable product strategy is organized around target customers and problem spaces. Asana moved away from structures centered on projects and locations, creating areas that give teams closer to the work greater agency and accountability.
• Success metrics are nested across organizational levels. Asana uses research and development metrics, pillar metrics, area metrics, and often one or two measures at the team level, connecting broad product strategy to focused execution.
• Rolling planning combines direction with adaptability. Asana plans every six months across a 12-month horizon, holding more confidence in the immediate half and less in the following half while giving the business visibility into what may come next.
• Roadmaps should permit learning to change commitments. Asana aligns teams on success, encourages rapid and iterative shipping, and uses prototypes to discover whether planned work should continue, change direction, or be removed before excessive investment.
• Related book: The 15 Commitments of Conscious Leadership
• Related book: The Alchemist

Questions & Answers

Q: How can a younger product leader earn trust from skeptics?

A younger product leader can earn trust by bringing useful, specific insight rather than relying on status. Costello recommends deeply knowing the customer, market, competitors, relevant numbers, and product. That preparation makes contributions more credible because recommendations are connected to evidence and context. Confidence becomes a consequence of understanding the problem, not merely an attempt to appear senior.

Q: How can product managers overcome scarcity thinking?

Product managers can challenge scarcity thinking by asking, "How might the opposite be true?" Costello describes this question as a way to interrupt the assumption that only one path is available. Considering the opposite can reveal alternative options or show that two apparently conflicting goals are both possible, making the decision feel less restrictive and emotionally tense.

Q: What does Asana's core product organization manage?

Asana's core product organization manages the company's desktop, web, and mobile applications. The scope includes product experiences such as goals, portfolios, projects, tasks, and reporting. Its broader purpose is to create clarity for individuals, teams, and organizations, helping people understand their work, coordinate responsibilities, track progress, and pursue intended outcomes more efficiently.

Q: What does clarity at work mean in Asana's product strategy?

Clarity at work means making purpose, plans, progress, and responsibility understandable. Costello summarizes the desired outcome with the question, "Who is doing what by when and why?" When teams have greater certainty about those elements, they can coordinate more efficiently and spend less effort resolving ambiguity about ownership, timing, direction, or the reason behind the work.

Q: How did Asana change its product organization as it scaled?

Asana moved from organizing primarily around projects and locations toward a structure containing pillars, areas, and working teams. Each area focuses on a specific target customer and problem space. This structure is intended to create more durable thinking while placing agency and accountability closer to the teams responsible for understanding problems and delivering product outcomes.

Q: How does Asana connect strategy to product metrics?

Asana uses a nested measurement structure that parallels its organizational and product strategy. Broad research and development metrics sit above pillar metrics, followed by area metrics. At the team level, one or two measures often receive concentrated attention. This hierarchy connects company-level direction with the particular customer problems and outcomes that individual teams are responsible for advancing.

Q: How does Asana plan across a rolling 12-month horizon?

Asana revisits its plan every six months while maintaining a view across the next 12 months. The immediate six months carry higher confidence, while the following six months carry lower confidence. This method gives the business visibility into upcoming work and supports alignment between product and go-to-market planning, while preserving room to respond to progress, opportunities, or new technology.

Q: Why should product teams be allowed to change a roadmap?

Product teams should be allowed to change a roadmap because placing an item on it does not prove that completing the item remains the smartest choice. Asana encourages prototyping, fast iteration, and alignment around success rather than rigid dates. Evidence gathered during development may justify adjusting scope, changing direction, or cutting work that no longer appears valuable.

Summary & Key Takeaways

• Paige Costello leads the Asana product organization responsible for its web, desktop, and mobile applications. Her teams seek to create clarity about purpose, plans, progress, and responsibility so individuals, teams, and organizations can work more efficiently and understand who is doing what, by when, and why.

• Asana evolved from organizing work around projects and locations toward durable areas defined by target customers and problem spaces. Its strategy and measurements form a nested structure across research and development, pillars, areas, and teams, with increasingly specific metrics and accountability placed closer to the teams doing the work.

• Planning shifted from a primarily annual process to a rolling 12-month view revisited every six months. Near-term plans carry greater confidence than the following half. Teams align on success instead of rigid delivery dates, prototype early, ship iteratively, and retain permission to pivot or remove work from the roadmap.