Table of Contents
Introduction
As project managers, we spend a lot of time coordinating work across teams: engineers, architects, designers, product managers, and stakeholders. Our job is to keep things moving, align people, and help projects deliver successfully.
However, how well do we actually understand the roles we collaborate with every day? Real collaboration goes deeper than knowing what someone’s job title is. It requires empathy: the ability to step into someone else’s shoes and understand the reasoning behind their decisions. Without that, we’re coordinating around people rather than truly working with them.
To explore that question, I took Digital Product Management: Modern Fundamentals, the first course in the University of Virginia’s five-course Digital Product Management specialization on Coursera, taught by Alex Cowan of UVA’s Darden School of Business. I wasn’t looking to become a product manager, and I wasn’t planning to complete the full specialization. I had a more specific goal: to understand how product managers actually think and why they make the decisions they do.
That turned out to be exactly what I got.
Five Mindset Shifts
Here are five things I learned that genuinely changed how I see the product manager’s role.
1. Not All Product Managers Are Doing The Same Job.
Something I hadn’t expected the course to address was how much the product manager role itself varies. “Product manager” isn’t a single job description. Instead, it’s a family of roles that differ based on how strategic versus hands-on the work is, and whether the product manager is oriented toward business stakeholders or engineering teams.
A Growth Product Manager works at a high strategic level, focused on metrics like user acquisition and retention.
A Generalist Product Manager managing a developer program bridges both worlds, balancing ecosystem strategy with technical realities.
A Specialty Enterprise Software Product Manager goes deep with niche business users to solve very specific, detailed problems.
A Developer Platform Product Manager is the most technical of the four, focused on APIs and tools that other developers depend on.
🔑 Key takeaway: When you don’t know which type of product manager you’re working with, you risk misreading their decisions entirely. A Growth Product Manager obsessed with metrics isn’t ignoring your concerns, but rather doing exactly their job. Understanding the shape of the role helps you understand the logic behind the behavior.
2. They Don’t Just Build Features. They Test Assumptions.
One of the most important ideas in the course is that product development is fundamentally about reducing uncertainty.
Product managers treat new features as hypotheses about what will help users. Instead of assuming something will work, they look for ways to test those assumptions as quickly and cheaply as possible. Their goal isn’t just to build, but to learn whether what they’re building actually solves the user’s problem.
🔑 Key takeaway: Product management is fundamentally an exercise in managing uncertainty. A feature isn’t a deliverable, it’s a bet. And the product manager’s job is to make that bet as informed as possible before significant time and money are spent. It’s not about execution, it’s about validation.
3. They Start with the Problem, Not the Solution.
The course puts a strong emphasis on personas and problem scenarios: defining who the user is, what they’re trying to accomplish, and what obstacles are in their way. This keeps product decisions grounded in real needs rather than internal assumptions.
Instead of asking “what features should we build?”, product managers are asking who the user is, what they’re trying to solve, and what’s standing in their way today.
🔑 Key takeaway: Product decisions are only as good as the problem definition behind them. If a team hasn’t deeply understood who the user is and what’s actually blocking them, any solution they build is essentially a guess. Personas and problem scenarios aren’t just planning tools; they’re the foundation that every downstream product decision rests on.
4. MVP Isn’t a Smaller Product, but a Learning Tool.
Before taking this course, I thought of an MVP as a scaled-down product with fewer features. The course reframed that completely.
An MVP is really about identifying the smallest thing you can build to test whether your idea actually works. The goal isn’t to launch something incomplete; it’s to answer a critical question as quickly as possible: does this help users? Will they use it? Does it solve the problem the team thinks it solves?
🔑 Key takeaway: An MVP is a question, not a product. It’s the team’s way of asking “are we right about this?” before fully committing. The measure of a good MVP isn’t how polished it is. Rather, it’s how clearly it answers the hypothesis it was designed to test. Speed of learning matters more than completeness of delivery.
5. They’re Running Two Tracks at Once … and Always Thinking Ahead.
One of the concepts that stood out most was dual-track Agile: the idea that product teams often operate in two parallel tracks simultaneously. Discovery, where they’re exploring ideas, talking to users, testing assumptions, and validating concepts. And delivery, where they’re building, releasing, and iterating on the product.
In practice, this means a product manager might be running user interviews for a feature six months out while the team is still shipping the current sprint. They’re not distracted; they’re doing exactly what the role requires.
🔑 Key takeaway: Product development is never just about what’s being built right now – it’s equally about what should be built next. Discovery and delivery aren’t sequential phases; they run in parallel by design. That means a healthy product team is always in two conversations at once: executing on what’s been validated, and questioning whether what comes next is the right call.
Final Thoughts
I only took the first course in a five-part specialization, and I came away with more perspective than I expected. The course is rated 4.7 out of 5 by over 5,400 learners and I’d say that reflects what it actually delivers: a clear, well-structured introduction to how modern product management really works, taught by someone who clearly knows the field.
For me, this wasn’t about switching careers. It was about understanding the mindset of a role I work alongside every day and building genuine empathy for the thinking behind the decisions, the method behind what can sometimes look like ambiguity, and the discipline underneath what can feel like constantly shifting priorities.
If you’ve ever found yourself puzzled by a product manager’s decisions, this course gave me the context to finally understand the thinking behind them. And that alone made it worth it.
Resources
Digital Product Management: Modern Fundamentals, taught by Alex Cowan, University of Virginia, on Coursera (https://www.coursera.org/learn/uva-darden-digital-product-management).
