Great product leaders aren’t just managing backlogs and shipping features. They’re building high-performing teams by cultivating trust, clarity, and a culture of ownership.

In this post, I’m sharing lessons I’ve collected over years of leading product teams—lessons about credibility, communication, coaching, and how to help your team actually thrive. Whether you’re a new manager or a seasoned leader, I hope this gives you a helpful framework (and a few reminders) for leading well.

🧱 Part 1: Leadership Starts with Trust and Credibility

1. Always Maintain Credibility

If your teammates and manager can’t rely on your word, they’ll start second-guessing everything. That’s why consistency matters—especially in small things, like time estimates. Don’t habitually under- or overpromise. Delivering on your word builds long-term trust.

2. Build Social Currency

People should want to follow your lead. That means making others look good, giving credit generously, and operating in a way that serves everyone’s best interest.

3. Make People Feel Heard

Don’t just tell people what to do—include them in the process. Ask questions like:

“Steve, what do you think?”

Even small gestures make a big difference in helping your team feel seen, valued, and invested.

4. Adapt Your Communication Style

Talk to creatives differently than you would to an executive.

• Executives want brevity and clarity: check the box and move on.

• ICs love the nuance and detail—meet them there.

📐 Part 2: Manage Expectations with Clarity

5. Give Ranges, Not Absolutes

When estimating effort or timelines, communicate uncertainty. Say “8–12 hours,” not “10 hours.” Ranges help set better expectations and create space for change.

6. Focus on How You Manage, Not Just What

You don’t need to be the expert in everything. Ask thoughtful questions. Read between the lines.

“Why are we working on X? How is that helping us get to Y?”

That kind of thinking helps you lead any project—technical or not.

7. Prep Before Meetings

Don’t use meetings to gather basic info. Reach out beforehand so people aren’t caught off guard. It helps your team come off sharp, prepared, and aligned.

8. Interrupt With Care

If a meeting is drifting, find the right moment to step in:

“This is really helpful context, but I want to make sure we stay on track…”

Interrupt to refocus, not to dismiss.

🧠 Part 3: Understand Your People Deeply

9. Learn Your Team’s Personality Types

Is someone an over-estimator or under-estimator? A last-minute finisher or early bird? Learning their quirks helps you anticipate how and when things get done.

10. Prioritize with Clear Eyes

Before panicking, ask:

• What’s the worst-case?

• What’s the best-case?

• What’s urgent vs. what’s important?

11. Focus on People First

Ask: “What’s in your way?”

Remove friction. Be a shield. Set them up to do their best work.

🔍 Part 4: Improve the System, Not Just the People

12. Use a Systems Mindset

Don’t just treat symptoms. Ask why repeatedly to get to the root cause.

Melissa thought the copywriter was slow, but the real issue was a bottleneck in the approval process.

She fixed the system—not the person.

13. Get Communication Out of Your Head

Make assumptions explicit. If “copy approved” means different things to different people, clarify it.

14. Question Legacy Processes

Ask:

“What’s something we’ve always done—and is it still useful?”

15. Create the System. Don’t Be the System.

People shouldn’t always come to you. They should be able to do things without you. That’s real scale.

👥 Part 5: Coaching Is Your Real Job

16. Your Employees Are Your Customers

Ask how they like to receive feedback. Provide recognition generously. Coach them to be problem-solvers, not just doers.

17. Teach Ownership, Not Just Execution

Guide with questions. Empower people to find their own solutions—even if their idea is different than yours. Ownership leads to growth.

18. Management Is a Partnership

“I’m in this with you. I’m here to help however you need.”

Support, listen, push. That’s how great managers show up.

🔥 Part 6: Avoid the Trap of Being “Busy”

19. Stop Being Busy

Busyness is not productivity. If you’re always reacting (Slack, email, meetings), you’re probably not thinking strategically—and your team can’t rely on you.

Use This System to Reclaim Time:

1. Make a list of everything you do

2. Automate what you can

3. Delegate what should be done by others

4. Cut what doesn’t matter

5. Focus on what only you can do

🏁 Final Thoughts: Coach First, Ship Second

“If you’re not being proactive about your team, you’re ignoring them.”

Even if your job is product, your real job is people.

• Invest in your team.

• Build systems that scale.

• Communicate with clarity and care.

• Coach, don’t just delegate.

A great, healthy team will do all the work. Your job is to help them get there—and then get out of the way.

Let’s be real—AI feels like magic… until it doesn’t.

One minute it’s helping you write an email or summarize a research paper, and the next, it’s confidently telling you that Abraham Lincoln invented the iPhone.

If you’re feeling a little overwhelmed (or underwhelmed) by all the AI buzz, don’t worry. You’re not alone—and you definitely don’t need to be technical to get started.

In this beginner-friendly guide, I’ll walk you through the basics of how AI tools like ChatGPT actually work, how to write better prompts, and how you can start using these tools right now to save time, spark ideas, and impress your coworkers (or your dog, if you work from home).

🧠 How AI Tools Like ChatGPT Actually Work

Let’s demystify things.

Most generative AI tools have three key ingredients:

• Training Data → This is like the AI’s textbook—millions of articles, books, and websites used to help it learn patterns in language and logic.

• The AI Model → Think of this as the student who read all the textbooks and can now answer questions, write essays, or even tell a dad joke.

• The Application → This is where you come in. ChatGPT, Claude, Gemini—these are the friendly interfaces where you chat with the AI and get your answers.

To recap:

📘 Training Data = The textbooks
🧠 AI Model = The student
💬 App (like ChatGPT) = The chatbot that gives you answers based on what it learned

💬 Top AI Chatbots You Can Try Today

Here are a few popular ones to explore:

• ChatGPT (OpenAI): Great for writing, coding, explaining

• Claude (Anthropic): Understands huge documents with calm, friendly

• Gemini (Google): Deeply integrated with Google tools

• Copilot (Microsoft): Deeply integrated with Microsoft tools

They’re all multimodal now too, meaning they can handle more than just text—like images, PDFs, and even spreadsheets. ✨

✍️ Prompting: How to Talk to AI (So It Understands You)

Here’s a fun secret: the better your input, the better your output.

Think of writing prompts like giving instructions to a helpful (but slightly overenthusiastic) intern. Be clear, give context, and tell them what good looks like.

Here are a few frameworks I like:

1. RTF – Role, Task, Format

Instruct the AI on who it is, what to do, and how to deliver the response.

🗣 “You are a career coach. Write a cover letter for a junior marketer applying to a wellness startup. Keep it under 300 words.”

2. TAG – Task, Action, Goal

Use this when you know what you need done, but don’t want to overthink it.

🗣 “I need to write a thank-you email after a job interview. Draft 3 versions. The goal is to leave a strong impression.”

3. RACEF – Role, Action, Context, Example, Format

More advanced—great when you need high-quality, tailored output.

🗣 “You are a professional UX copywriter. Write onboarding microcopy for a finance app that helps freelancers manage taxes. Use the tone from these examples. Format in bullet points.”

⚠️ A Few Things to Keep in Mind

AI is powerful—but it’s not perfect. Here’s your friendly beginner’s cheat sheet for using it responsibly:

• Hallucinations → Sometimes, it makes stuff up. Check your facts.

• Training Cutoffs → Most models only know info up to a certain point (GPT-4’s free version knows up to 2023).

• Bias → AI reflects its training data, which includes human biases. Use your judgment.

• Privacy → Don’t copy/paste your company’s secret roadmap or grandma’s social security number into an AI app. Use secure tools if you're dealing with sensitive info.

🛠 Real Ways to Use AI in Everyday Work

Whether you’re a marketer, student, data analyst, or just trying to get through your inbox faster, AI tools can help. Here are some simple ways to get started:

📝 Summarize

• “Turn this article into 5 bullet points.”

• “Summarize this 1,000-word blog post for a LinkedIn post.”

🧠 Explain

• “Explain Kubernetes like I’m five.”

• “Help me understand this legal clause in plain English.”

✏️ Edit

• “Rewrite this email to sound friendlier.”

• “Proofread this and fix any awkward phrasing.”

💡 Brainstorm

• “Give me 10 offsite ideas for a remote team.”

• “Suggest taglines for a sparkling water brand.”

🔍 Research

• “Compare the top note-taking apps in 2024.”

• “Summarize the latest trends in generative AI.”

🎯 Use Cases by Role

Here’s how different people might use AI in their day-to-day:

For Job Seekers & Recruiters

• Draft resumes, cover letters, and thank-you emails

• Generate interview questions and rubrics

• Compare candidates and write job descriptions

For Teachers & Students

• Summarize textbook chapters

• Build lesson plans and quizzes

• Get feedback on essays or presentations

For Marketers & Creators

• Write social media posts, blogs, and emails

• Generate product descriptions and landing page copy

• Brainstorm campaign ideas or hooks

For Analysts & Data Teams

• Upload CSVs and ask, “What insights do you see?”

• Create charts and summaries

• Get SQL queries or Python scripts written for you

For Designers

• Get UX feedback on a landing page screenshot

• Generate placeholder copy (CTAs, headlines)

• Ask for layout ideas or tone suggestions

📌 Final Thoughts: Just Start Somewhere

You don’t need to know how it all works. You don’t need to be a prompt engineer. And you definitely don’t need to memorize which model does what.

You just need to start.

Try it once—ask ChatGPT to rewrite your email. Ask Claude to help you plan your next trip. Use Gemini to polish your pitch deck. Small wins add up fast.

Because the future of work isn’t about replacing people with machines. It’s about people who know how to work with machines.

So go ahead—take your first step. It’s not about being perfect. It’s about being curious.

Product success doesn’t come from heroic individual effort. It comes from clarity of roles, strong collaboration, and shared ownership across a product leadership triad: the Product Leader, the Product Manager, and the Product Owner.

Too often, we try to collapse all product responsibilities into a single role. This creates real risk:

• Execution quality drops as one person spreads too thin

• Individuals burn out from covering too many bases

• Business value goes unrealized due to gaps in coverage

To build successful products and healthy product teams, we need to understand the distinctions—and the collaboration—between the three key roles.

The Three Key Roles in Product Management

Let’s explore what each role contributes and why they all matter.

🧭 The Product Leader

(a.k.a. The Portfolio Strategist)

If the product team were a ship, the Product Leader is standing at the top deck with the telescope. They’re focused on the long-term course—where we’re heading, and why it matters for the business.

They don’t steer the ship day to day, but they do make sure everyone’s headed in the right direction.

🎯 What they do:

• Define and manage the portfolio vision and strategy

• Align product work with executive priorities

• Build business cases for big initiatives

• Help remove blockers at the org level

• Hire, mentor, and support PMs across the board

🧰 What they produce:

• Portfolio Roadmap

• Strategy Docs

• Business Cases

• Executive Briefings

🌟 Why they matter:

They create alignment at the highest level and make sure the product portfolio supports the broader company mission. Also? They keep teams focused on the big picture—especially when the day-to-day gets chaotic.

🧠 The Product Manager

(a.k.a. The Lifecycle Owner)

The Product Manager is right in the thick of things—translating strategy into reality, and reality into lessons. They're owning the product through its entire lifecycle, from fuzzy idea to measurable impact.

They're part strategist, part collaborator, part customer whisperer.

🎯 What they do:

• Define the product vision and connect it to real business goals

• Talk to customers (a lot), run research, test hypotheses

• Shape the roadmap, prioritize what to build (and what not to)

• Partner with design, engineering, marketing, and ops

• Track performance and evolve the product based on feedback

🧰 What they produce:

• Product Vision & Strategy

• Roadmaps

• OKRs / KPIs

• Feature Backlog

• Business Case

🌟 Why they matter:

They bring focus, clarity, and customer obsession. They also help make sure we’re solving the right problems, not just building more stuff.

🔧 The Product Owner

(a.k.a. The Delivery Catalyst)

Ah, the unsung hero of iteration. The Product Owner is deep in the engine room, working side by side with the development team to keep work flowing—and to make sure every story has a clear “why.”

They live closest to the sprint rhythm and help ensure teams are shipping the most valuable work right now.

🎯 What they do:

• Own the team backlog (user stories, bugs, tech enablers, etc.)

• Translate roadmaps into detailed, ready-for-dev stories

• Write and refine acceptance criteria

• Lead sprint ceremonies (planning, grooming, reviews)

• Make prioritization calls based on value, effort, and team input

🧰 What they produce:

• Sprint Objectives

• User Stories

• Acceptance Criteria

• Release Plans

🌟 Why they matter:

They connect strategy to execution and keep the team laser-focused. Also, they make sure feedback is heard and incorporated—without slowing things down.

🤝 Collaboration Is the Secret Sauce

Each role has a distinct focus. But none of them can succeed in a vacuum. When the triad is working well, you feel it:

• Product Leaders give context and alignment from the top

• Product Managers turn strategy into actionable plans

• Product Owners keep delivery tight, fast, and meaningful

The handoffs are clean, the collaboration is constant, and the product actually moves forward in a way that feels intentional—not chaotic.

But when one role is missing—or overloaded—everything starts to wobble. The roadmap gets fuzzy. Priorities get murky. People get frustrated. And let’s be honest… it’s no fun for anyone.

🫣 You Can’t Do It All (And You Shouldn’t Try)

It’s tempting to try and wear all the hats. Especially at startups, or in under-resourced teams, where one person is expected to own:

• Vision

• Strategy

• Business case

• Roadmap

• User research

• Story writing

• KPI tracking

• Cross-functional alignment

• …and probably lunch planning, too

But that’s a fast track to burnout. And more importantly—it’s not scalable.

Great products are team efforts. And the triad model is one way to make that team structure healthy, sustainable, and effective.

Final Thought: Build the Right Thing, the Right Way, Together

When roles are clear and trust is high:

• Product Leaders focus the portfolio

• Product Managers turn vision into action

• Product Owners deliver value sprint by sprint

And together? They build things that matter—without sacrificing team health or quality along the way.

So if you’re a PM feeling stretched thin: you’re not doing it wrong. You might just be doing it alone. And there’s a better way.

Let’s make space for collaboration. It’s where the good stuff lives.

Let’s be honest: product management is a bit of a balancing act. One part gut instinct, one part structured decision-making… and one part trying to remember which framework you bookmarked last month but never got around to using.

Over the years, I’ve tried a bunch of frameworks. Some were helpful, some were confusing, and some just sat in a dusty Notion doc. But a few have stuck—because they’re simple, practical, and actually helped me move a product (and a team) forward.

Here are seven that I find myself coming back to again and again—along with quick examples to show how they come to life in the real world..

1. Jobs to Be Done (JTBD)

💡 “People don’t buy products. They hire them to do a job.”

What it is:
JTBD is a framework that gets to the root of why someone uses your product—not just what they do or who they are.

Forget user personas named “Savvy Susan” or “Techie Tom.” JTBD asks: What problem is this person trying to solve in their life?

How to apply it:
Say you’re building a digital receipt app. It’s tempting to think: “People want a better way to store receipts.”

But dig deeper. What are they actually hiring your product to do?

• “Help me get refunds faster.”

• “Make tax season slightly less horrible.”

• “Avoid digging through old emails at midnight.”

Once you understand these jobs, you can prioritize features like return deadline alerts, PDF export for taxes, or even just a really great search.

2. RICE Scoring

📊 A slightly nerdy but incredibly useful way to prioritize.

What it is:
RICE stands for Reach, Impact, Confidence, and Effort. It’s a simple formula to help you figure out which ideas are worth pursuing (and which should quietly go back into the idea vault).

How to apply it:
Let’s say you’re weighing these three features:

• Apple Wallet integration

• Dark mode

• AI-powered receipt scanner

You score each feature on:

• Reach: How many users will it affect?

• Impact: How much value does it create?

• Confidence: How sure are you?

• Effort: How much time/energy will it take?

Even if dark mode isn’t the flashiest feature, it might win because it’s fast to build and improves user satisfaction. RICE helps remove some of the emotion from prioritization—and adds just enough math to make you feel like you know what you’re doing.

Dark mode, while less impactful, may get prioritized because it offers the best return on investment in the short term.

3. Product/Market Fit Pyramid (Dan Olsen)

🧱 A five-layer stack for finding the right product for the right people.

What it is:
This framework breaks product/market fit into five elements:

1. Target customer

2. Underserved needs

3. Value proposition

4. Feature set

5. UX

How to apply it:
For our digital receipt app, you might fill it out like this:

• Target customer: Online shoppers, age 25–40

• Underserved need: Hard to track receipts across retailers

• Value prop: “A single place to manage receipts, returns, and spending.”

• Feature set: Smart inbox, spending insights, return reminders

• UX: Clean, mobile-first, minimal taps

If something’s off—say users aren’t sticking around—this pyramid helps you diagnose where the disconnect is. Sometimes it’s not the UX… it’s that you’re solving a problem they don’t actually care about.

4. North Star Metric Framework

🌟 Pick one metric that matters most—and steer toward it.

What it is:
Your North Star Metric (NSM) is the one number that best represents how your product creates value for users. It keeps everyone aligned and focused.

How to apply it:
Let’s say your NSM for the Spendy app is:

“Receipts successfully parsed and stored per active user per month.”

That metric captures both usage and value. It’s something marketing, design, and engineering can all rally behind. (Bonus: it’s harder to game than just “signups.”)

5. Kano Model

🎁 Not all features are created equal.

What it is:
The Kano Model helps you think about features in terms of how they impact user satisfaction:

• Must-Haves: Basic expectations. If they’re missing, users are mad.

• Performance Features: The more, the better.

• Delighters: Unexpected extras that make users smile.

How to apply it:
You survey your users and find:

• Must-Have: Ability to search for receipts

• Performance: Quick dashboard load times

• Delighter: Magic OCR that scans printed receipts from a photo

This helps you sequence your roadmap. First nail the must-haves, then stack on the performance features, and sprinkle in a few delighters to keep people talking.

6. Lean Canvas

📄 Your business idea on one page (yes, really).

What it is:
The Lean Canvas distills your product concept into nine simple boxes—from the problem to the solution to your unfair advantage.

How to apply it:
Let’s mock one up for a receipt app:

• Problem: Receipts are messy, hard to track, and easy to lose

• Customer Segments: Online shoppers, freelancers, small biz owners

• Unique Value Prop: “Your entire purchase history in one inbox.”

• Solution: Auto-forward email receipts, scan paper ones, organize and tag

• Channels: App Store, Google Ads, financial influencers

• Revenue: Freemium + premium for long-term storage

• Cost Structure: OCR processing, cloud storage, dev team

• Key Metrics: Monthly active users, scanned receipts, upgrades

• Unfair Advantage: Spendy.com email + brand simplicity

This canvas helps you pressure-test your assumptions early, before you spend 6 months building the wrong thing.

7. HEART Framework (by Google)

❤️ Measure what really matters to your users.

What it is:
HEART stands for:

• Happiness

• Engagement

• Adoption

• Retention

• Task Success

It’s a way to look beyond vanity metrics and focus on meaningful user experience.

How to apply it:
Post-MVP launch, you might track:

• Happiness: NPS after onboarding

• Engagement: How often users open the app

• Adoption: % of users using return reminders

• Retention: % active after 30 days

• Task Success: % of receipts scanned without issues

By reviewing these, you’re not just shipping features—you’re making sure they’re actually helping people.

Wrapping Up

You don’t need to memorize every framework in the PM universe. But having a few reliable ones in your back pocket can make decision-making feel a lot less murky.

Start with one or two that resonate with where you are right now. Adapt them. Remix them. Tape them to your wall if that’s your thing.

Because at the end of the day, great product management isn’t about frameworks. It’s about clarity, curiosity, and making things better for the people we serve.

And if a framework helps you do that a little more confidently? That’s a win in my book.

Let’s face it—“platform” might be one of the most overused words in tech. Somewhere between “synergy” and “AI-powered,” it’s lost a bit of meaning.

But if you’ve ever had to actually build a platform—one that multiple teams rely on, that works at scale, and that people want to use—you know just how tricky (and valuable) it really is.

I’ve had the chance to lead platform initiatives in a few different settings—most notably at Yahoo, where I worked on content management and publishing tools, and later during my consulting time with Strategic Education, where I helped unify digital experiences using Adobe Experience Manager. Different orgs, different goals, but the same core idea:

Build something once. Make it reusable. Help everyone move faster.

Let’s dig into a few lessons I’ve learned the hard way.

So… What Is a Platform?

A platform isn’t just a fancy term for shared code. It’s not just a set of APIs. And it’s definitely not a giant bucket labeled “stuff multiple teams use.”

A platform—when done well—is a scalable foundation that enables other teams to move faster with less friction. It’s a product that powers other products. And the users? Usually developers, designers, content creators, or anyone building on top of it.

One thing I’ve come to believe strongly:

If people don’t want to use your platform, it’s probably not a platform. It’s a requirement. And nobody gets excited about those.

Start with a Vision: Who Are You Helping, and Why?

The best platforms I’ve seen don’t start with architecture diagrams—they start with empathy.

At Yahoo, our platform vision was pretty simple: Help each editorial team publish content faster without rebuilding the same tools 10 different ways. That meant creating a shared API layer and CMS experience that still allowed for some flexibility and brand personality.

At Strategic Education, the platform was less about speed and more about cohesion—bringing Strayer and Capella into a unified experience while honoring what made each unique.

In both cases, the real question wasn’t “What can we build?” It was “What problems do teams keep running into, and how do we solve them once, for everyone?”

That mindset—solving shared problems at scale—is at the heart of platform thinking.

Developer Experience (DX) Is the Product

Here’s an easy way to kill a platform: make it confusing or slow to adopt.

I’ve learned (again, sometimes the hard way) that internal developers are your customers, and their experience matters just as much as any external user.

If onboarding takes weeks, docs are out of date, or support is a black hole… they’ll build their own thing. And they won’t look back.

So ask yourself:

• Is it easy to get started?

• Is it clear what this platform does—and doesn’t do?

• Do teams want to use it, or do they just have to?

If the answer is “ehhh,” it might be time for a DX refresh. Small things—like quickstarts, Slack support, or sample apps—can go a long way.

Reuse Is the Real ROI

One of the simplest metrics I love to track is: how many teams are using this thing? And more importantly—are they using it the same way, or hacking around it?

At Yahoo, we celebrated every time a new team adopted a shared publishing service or component. Not just because it felt like a win (though it did!), but because it meant:

• Less duplicate work

• Faster launches

• More consistency

• Easier updates down the line

And honestly, that’s what makes platform work satisfying: when you see it ripple out into real-world impact.

Don’t Forget the Business Lens

Look, it’s easy to get deep into the weeds of scaling, caching, or decoupling services—and hey, that stuff’s important. But it’s not the point.

The real value of a platform is what it unlocks for the business.

A few ways to frame that:

• Are we reducing time-to-market for new features?

• Are we helping teams say “yes” to new use cases, not “maybe in six months”?

• Are we lowering costs by avoiding duplicate efforts?

If your platform metrics aren’t tied to business outcomes, it’s hard to get continued investment—or buy-in from leadership. Keep the big picture in mind.

Final Thought: Build for Empowerment, Not Control

Here’s the trickiest part of platform work—it’s a little invisible. When things are working well, nobody notices. And when they’re not, well… you hear about it a lot.

That’s why platform teams need a unique mix of technical depth, empathy, product sense, and honestly, a good sense of humor.

Because in the end, building a successful platform isn’t about owning everything. It’s about enabling others to go further, faster—with less friction.

And when you get that right? You’re not just shipping code. You’re shipping velocity.

There’s more to great product management than defining features and shipping code. Great PMs—and great PM teams—operate across a full stack that includes discovery, delivery, team leadership, and cultural development.

This post outlines how I think about modern product management across four layers:

1. Product Discovery

2. Product Delivery

3. Product Leadership

4. Team Excellence

1. Product Discovery: Explore the Right Problems

Every product journey starts in the discovery phase, where you define both the problem space and the solution space.

✅ Problem Space

PMs are responsible for deeply understanding user problems. This isn’t a one-time survey—it’s an ongoing cycle of user interviews, stakeholder feedback, and sometimes just spotting a problem yourself.

When assessing a problem, I ask:

• How painful is this problem? Is it a daily frustration or a rare annoyance?

• How common is it? Does it affect a few users or an entire market?

• How much will our solution reduce the pain? Will people adopt it quickly? Will it change habits?

• How feasible is the solution? Can we build this now, or do we need major ecosystem shifts to support it?

💡 Solution Space

Once the problems are well understood, we move to solutioning. This is where brainstorming, stakeholder feedback, and user validation come into play. The goal isn’t just to generate ideas—it’s to identify the highest ROI opportunities.

That’s where the Opportunity Assessment comes in.

Opportunity Assessment

An opportunity assessment is a concise 1–2 page document that outlines:

• Impact: What will change if we succeed?

• Effort: How hard is this to build?

• Risks: What could go wrong?

• Market/context: Why now?

This becomes the business case for prioritizing one opportunity over another.

2. Product Delivery: Execute with Precision

Once a solution is prioritized, we move into delivery—translating intent into product experiences.

This includes:

• Epics and user stories that clearly communicate goals to engineering

• Designs (wireframes, prototypes, high-fidelity mocks)

• Copy/content that aligns with tone, clarity, and intent

• Milestones and release planning

📊 Impact Assessment

Every feature we ship should be followed by a thoughtful impact assessment. Did we solve the problem we set out to solve? Did the solution live up to the promise made in the opportunity assessment?

Impact can be:

• Quantitative: Adoption, engagement, revenue, retention

• Qualitative: User feedback, satisfaction, sentiment

This loop completes the discovery-to-delivery cycle.

3. Product Leadership: Lead with Purpose

Leading a product team is a lot like practicing servant leadership. The job of a PM leader is to:

🎯 Set the Vision

Define what success looks like. Where are we going? Why does it matter?

🧭 Show the Road

Help your team navigate uncertainty. There are many ways to go from A to B—your job is to help them find the shortest, most impactful path.

🏃 Get There Faster

Once the path is clear, remove roadblocks and accelerate progress. That can include:

1. Coaching and skill development

2. Unblocking bureaucracy

3. Rolling up your sleeves to help deliver

Hands-on leadership is key. The best leaders aren’t just “meeting managers.” They’re right there in the weeds when it matters.

4. Striving for Team Excellence

If you want to build world-class products, you need a world-class team. That means building systems and rituals that push everyone to get better—together.

One tactic I’ve found effective: Team Excellence Initiatives—each owned by a senior PM with their own OKRs. These focus on growth in targeted areas like:

📚 Knowledge Sharing

• Weekly Slack posts with useful insights

• Team-led knowledge presentations

• Guest speakers (internal or external)

• Shared reading + group application of takeaways

• Courses, certifications, conferences

🌐 Remote Team Bonding & Culture

• Biweekly virtual hangouts for fun and connection

• Rotating triads for monthly coffee chats

• Annual team offsite to bond, brainstorm, and reset

• Fitness or fun competitions (yes, even workout challenges!)

Culture is not accidental. In remote teams especially, it needs to be designed intentionally.

Final Thought: OKRs are Anchors, Not Chains

One final note: OKRs are critical, but they’re not handcuffs. PMs should commit to achieving outcomes—not delivering specific initiatives. Initiatives may change as we learn. The destination stays the same, but the path can (and should) adapt.

A strong OKR system includes goals like:

• Number of user research sessions per quarter

• Key result metrics aligned to user impact

• Clear tie-in to problem space, not just feature output

In Summary

Great PMs don’t just ship features. They:

• Understand problems deeply

• Identify high-impact solutions

• Lead cross-functional teams with clarity

• Create a culture of excellence

This is how product managers become force multipliers—not just for their teams, but for their entire organizations.

As product managers, our job isn’t to ship tickets. It’s to create leverage.

But what does leverage really mean? And where should we focus our time to create the most of it?

There are two core concepts I share with my team:

1. Managerial Output: This is what you produce as a manager. It’s not just your own contributions—it’s the output of your team plus the output of the surrounding teams you influence. Great PMs expand their radius.

2. Managerial Leverage: Some activities create more output than others. The best PMs recognize that their time is limited and focus on the things that produce the most leverage per unit of effort. That’s the real job.

So where does a PM create the most leverage?

The Leverage Pyramid: Vision, Strategy, Scope, Backlog

Here’s a simple framework I use:

Vision → Strategy → Scope → Backlog

Think of this as a pyramid, where the foundation lies in Vision and Strategy—and the optimization happens through Scope and Backlog.

At the top of the pyramid is the backlog—individual tasks and user stories. Important? Sure. But high leverage? Rarely.

At the base is vision—the compass that orients the entire team. This is where a product manager has the highest potential to shape outcomes.

Let’s break this down.

Vision: The Heart of the Team

A good vision describes where you’re going and why it matters. It’s not a feature set or a KPI target. It’s the end state of your team’s efforts, expressed clearly and ambitiously.

But here’s the catch: Your team’s vision has to fit within the company’s vision.

I’ve seen too many PMs go off-script, charging in like the “CEO of the product” trying to “do epic shit.” And while I admire the energy, it has to align with the bigger company narrative—or you’ll end up building something impressive but irrelevant.

PMs should spend real time talking with leadership to internalize the company’s vision—and recalibrate as the company evolves. At Shopify, we called this “staying on the green path.” It means you’re pushing boundaries, yes—but always within bounds.

And when you get it right? The vision becomes a filter for every micro-decision your team makes. It becomes the source of team pride. It becomes your leverage.

Strategy: Your Gameplan for Action

If vision is the “why,” strategy is the “how.” It’s the plan you craft to navigate constraints, market dynamics, customer needs, and technical realities—and move toward the vision.

And no, strategy is not a roadmap.

A roadmap is an output of strategy. A real strategy should answer:

• What are we building, and why?

• Who are we targeting, and why?

• How will we grow, and why will that work?

• How does this improve our position in the market?

The more your strategy can answer those questions (especially the “why”), the more your team will act with clarity and autonomy.

Scope and Backlog: Optimization Work

Scope and backlog are necessary—but they’re not where you create foundational leverage.

• Scope defines what you need to build to realize your strategy.

• Backlog breaks that down into the units of work your team will tackle.

They help you go faster toward a known destination—but they’re only effective when you’ve already figured out where you’re going and why.

That’s why I encourage PMs to spend more time downstream than upstream. If your strategy is fuzzy or your vision isn’t aligned, no amount of backlog grooming will get your team where it needs to go.

A Simple Litmus Test

If you want to test whether your team has clarity, ask this:

Can an engineer or designer on your team explain:

• The vision you’re working toward?

• The strategy that’s guiding how you get there?

If not, don’t start another sprint. Go back to the foundation. That’s where your leverage lives.

Closing Thoughts

I built this framework early in my career because I wanted to create a team where:

1. Everyone knew how their work contributed to the company’s vision.

2. Everyone could explain why we were approaching the problem in a specific way.

That’s the real unlock. That’s how you turn product managers into product leaders. And that’s how you stop managing backlogs—and start shaping futures.

Every product role, whether Product Leader, Product Manager, Product Owner or Product Analyst requires it’s own unique set of skills and behaviors; but truly great product people share common traits and qualities that transcend titles.

I’ve grouped these qualities into three categories, and four traits within each for a total of 12 key traits:

1. Be Inspirational: Great product managers (PMs) inspire those around them with bold visions, thoughtful ownership, and an empowering leadership style. They think big, embrace responsibility, and cultivate empathy to motivate and guide their teams toward success.

2. Build Great Relationships: Building strong, collaborative relationships is fundamental to product management. Great PMs communicate effectively, build trust, and influence stakeholders by aligning shared goals and leveraging collective strengths.

3. Get Things Done: Delivering results requires action, adaptability, and determination. Great PMs wear many hats, make decisive choices, and stay reliable while embracing change to ensure forward momentum.

Be Inspirational

1. Think Big: Great PMs do not constrain their thinking or get bogged down by limited resources, time or budget. They seem big opportunities and develop actionable plans to take advantage of them

2. Take Ownership: Great PMs take ownership over what they, and their team, do. They feel a sense of responsibility over every aspects of their product. They don’t make all the decisions, but they take ownership over the decisions being made.

3. Empower the Team: Great PMs empower their team. They include their team in key discussions and decisions, and delegate autonomy to their team, all while staying committed and focused on the outcome.

4. Be Empathetic: Great PMs take time to genuinely understand their team members and stakeholders. They seek to deeply understand other perspectives by putting themselves in other’s shoes and use that perspective to make thoughtful decisions.

Build Great Relationships

1. Be a great collaborator: Great PMs collaborate with their team. They empower their team to have a voice at the table. They recognize their team’s strengths and leverage those where appropriate in solving problems and making tough decisions.

2. Communicate Effectively: Clear, concise, and frequent communication is the hallmark of a great PM. They are approachable and ensure stakeholders stay informed and aligned.

3. Influence Stakeholders: Great PMs know how to make a case that is hard to refute or ignore. They use data when appropriate and can compel others to buy into their vision and get onboard.

4. Earn Trust: Great PMs understand people and recognize the importance of building trust with their team and stakeholders. They do what is necessary to earn each person’s trust and turn them into an ally, instead of just a colleague.

Get Things Done

1. Wear Multiple Hats: Great PMs aren’t above any title — they execute and do whatever is necessary to ship their product. They recruit others, write documentation, conduct customer research, escalate, do sales and troubleshoot tickets, to get things done.

2. Be Decisive (Decision Maker): Great PMs are decisive, even in the face of incomplete information. They have good product instinct, good business judgement and aren’t afraid to take risks in making business decisions.

3. Embrace Change: Great PMs are adaptable and embrace change. They ask great questions, accept change that aligns with the goals and are willing to pivot. They have backbone and speak up if they do not agree with the change.

4. Be Reliable: Great PMs are reliable and can be counted on by their team members. They are available to their team and responsive in a timely manner.

You don’t need to excel at every one of these traits. Start with one. As you master these traits, you’ll be on your way to becoming a truly exceptional product manager. All the best.

Many of the products we all know and love have been built by companies that use product management frameworks. Products that look very simple often take many months or years to build - which is largely due to companies spending time on product discovery, planning and testing prior to building. It’s no coincidence that companies that invest time in these additional steps build some of the most successful and loved products, and in this article, we’ll look at why these steps will improve the chance of your product being successful.

There’s no shortage of product management frameworks, and there’s no one framework that rules them all. You can use any framework that resonates with you, or even develop your own framework. The important thing is to recognize that frameworks provide a scalable process to build and improve your products in a consistent way.

In this article, we’ll introduce the concept to solution (CTS) product management framework. Like the name, this framework provides actionable steps you can follow to take your idea from a simple concept all the way to a real product solution.

The CTS product management framework includes six key phases:

1. Discovery, Market and Competitive Research.

2. Mission, Vision and Strategy.

3. Product Design and Roadmap.

4. Prototype, Test and Iterate.

5. Execution and Delivery.

6. Measure and Evolve.

Let’s unpack each of these.

Phase 1: Discovery, Market and Competitive Research

The objective of this first phase is to understand the business or your target user’s problem, quantify the magnitude of the problem and get familiar with any existing solutions that exist to address the problem.

More specifically, in this phase, you’ll seek to understand the problem space through qualitative and quantitative research. Qualitatively, you’ll conduct user research with external users and internal stakeholders, and quantitatively, you’ll analyze data available to you to form insights about the opportunity. Here are a few sample questions that you can start with to learn about the problem, the market and competition.

• How painful is this problem? Does this only happen on occasion, or is it happening many times a day? Is this just a minor annoyance or a deep source of frustration?

• How many users are experiencing this problem? Is this a unique situation faced by a niche group, or something an entire industry struggles with? Is this only an issue in a few places, or is it happening all around the world?

• What solutions exist today that try and address the problem? Are users satisfied with these existing solutions, or is there an appetite for a better one?

• How feasible is your solution? Is it technically possible to be implemented? Would your solution add immediate value, or would an entire ecosystem shift — like the creation of a two-sided market — need to happen? Can you pursue this incrementally, in a smaller space, like a specific city or narrow vertical?

Note: This is not an exhaustive list of discovery questions by any means. These questions are intended to spark curiosity for your own discovery needs.

There’s no set rules for how many interviews you should conduct, or how much time you should spend reviewing competitive products. This is largely based on your own intuition. When you feel like you have enough information to summarize a concise problem statement with supporting rationale and data, it’s time to move onto to the next phase.

Phase 2: Mission, Vision and Strategy

Now that you’ve defined a problem statement, you can craft a mission, vision, value proposition and strategy for how you intend to solve that problem. Let’s start by defining what each of these mean.

• Mission: Why does your company or product exist? What is your purpose? And, what are you hoping to achieve (with regards to addressing the problem statement)? As you craft your mission statement, it’s important to think about your motivation for addressing the problem. A few things to consider:

  • Consider Trends: Is the space growing or declining? Who are some of the existing players in the space and do we have the resources and expertise to compete?

  • Consider Opportunities: Can we build a product or solution to the problem, that aligns with our company’s mission?

  • Consider our own Strengths & Weaknesses: What are our company's strengths that we should leverage in building in this space? And weaknesses that we should avoid?

Once we have crafted a mission statement, the next step is to define our vision.

• Vision: What does the future direction of your product look like? Your vision statement is essentially an inspirational prediction of what the world looks like assuming your product or company is successful in achieving its mission. Your vision should be compelling and motivate your team to work towards this future direction of your product.

Next we explore our product’s value proposition.

• Value Proposition: This illustrates the unique value your product delivers to your users and the company. It should answer why your users should use your product (over a competitive offering)?

Now, that we’ve crafted a mission, vision and value proposition, the next step is to define a strategy.

• Strategy: This illustrates how your product will realize its vision. In other words, what is your plan (typically within 3 - 5 key investment areas you will make) to achieve your vision.

And finally, you should define key goals and success metrics to measure the progress of your strategy in achieving your vision. Your success metrics can take the shape of multiple objectives & key results (OKR’s) or a single north star metric. In either case, you want to ensure that a positive impact to your success metrics correlates to value delivered to your users.

Phase 3: Product Design and Roadmap

In this phase, you’ll start to ideate on what your product will look like and what will be its initial feature set. As you think beyond the initial feature set, you’ll build out your product roadmap.

Your roadmap should illustrate key outcomes your product is intended to deliver over a period of time. This time period can be specific (with targeted feature release dates) or it can be relatively vague (with your product features bucketed into now, next and later).

The goals and success metrics you defined (in Phase 2) will inform key decisions you make when building your roadmap. As you prioritize one feature over another, you’ll want to consider how a particular feature will impact your goals and drive your success metrics in the right direction.

Phase 4: Prototype, Test and Iterate

In this phase, you will take the first step in developing the first version of your product that you can test with real users to validate if you are heading in the right direction. This is your MVP (Minimum Viable Product). The primary objective of your MVP is to get data from users to understand if your product has potential, or if you should consider a different solution.

Phase 5: Execution and Delivery

In this phase, you will continue developing your product. You might utilize an agile development process, which includes creating a product backlog, refining your backlog regularly and working with your development team to deliver increments of business value.

As you develop subsequent versions of your product (v2, v3, etc.), you should also continue testing and learning by presenting these to your users to gather feedback and iterate. You should be open-minded to making updates to your product vision and roadmap as you continue to gather data from real users about how your product is taking shape.

Phase 6: Measure and Evolve

At this point, you have delivered your product, but how do you know if your product is delivering value to your users and the company (business)? This is why measuring and evolving your product is important to ensure your product is making a positive impact, and realizing its value proposition.

You might choose to measure the impact by conducting user interviews, conducting A/B (multivariate) testing, analyzing data and/or conducting internal reviews. There’s no wrong answer here. The key takeaway is to measure your product with users, gain insights and use these insights to continuously make improvements to your product.

In Summary

This is just one framework you can use to take your idea from a concept to a real product. In summary, we walked through (1) Conducting discovery, (2) Defining a mission, vision and strategy, (3) Building a roadmap, (4) Developing an MVP and testing it with users, (5) Continuously executing and improving your product, and (6) Measuring your product to ensure it is delivering it’s intended value to users and the business.

There’s so much more to say about each of these phases individually, but consider this a directional map for how to get started. All the best.