Great product management is the craft of bringing clarity to complexity — understanding users deeply, aligning stakeholders, and making decisions that balance value, feasibility, and long-term vision. In this Q&A, I walk through how I think about the problems and trade-offs that shape successful products. My goal is to provide a transparent look into the principles and methods that guide my work.
Building the Right Product
Strategy: What makes a good Product Strategy?
A strong product strategy tells a clear story for achieving a future vision. It aligns business outcomes with real user needs and technical feasibility, while adapting to market shifts and validated learnings. Good strategy avoids premature solutioning and focuses on delivering meaningful impact over outputs.
For Example:
At a global petcare company (via Ciklum), I led product strategy for a unified internal sales tool. The business had multiple passive dashboards but lacked actionable insights and didn’t know where to begin. Working with a UI designer and key business stakeholders, we aimed to do an expedited discovery (8 weeks) to identify the most urgent issues.
We identified three core user personas and interviewed ~25 team members across accounts like Chewy, Amazon, and Walmart to understand their day-to-day jobs. Analyzing the results using the jobs-to-be-done framework, I uncovered two central issues negatively impacting the business: slow reaction times to sales anomalies and limited forecasting capabilities. While I created a long-term strategy and roadmap, the UI designer developed wireframes and prototypes to achieve alignment with stakeholders and users for the initial anomaly detection release.
Our approach generated significant internal excitement due to the speed of discovery, clarity of focus, and the tangible outcomes delivered in the initial roadmap release and Figma prototypes.
User Needs: How do you make sure that you understand what users really need?
I focus on surfacing users’ underlying motivations — “the why” — not just what they say they want. My approach includes:
Conducting discovery interviews using open-ended, context-driven prompts
Applying frameworks like Jobs-to-be-Done or Customer Journey Mapping to uncover unmet needs
Synthesizing input from support tickets, usability tests, and behavioral analytics (click paths, drop-offs)
Comparing qualitative insights with usage data to spot gaps between intent and action
Example:
I was tasked with helping an enterprise quick-service restaurant determine how to develop their loyalty program, which included integrating with a SaaS loyalty platform built by Punchh. While understanding how the platform would work for the business, I researched user sentiment for other implementations. I uncovered a major user issue: users disliked needing to add a food item to their cart before applying a reward. After confirming this was a platform-wide problem, I pushed Punchh to change this behavior — and they did.
Roadmap: What’s your approach to building a product roadmap?
I build outcome-based roadmaps, starting with business goals, user needs, and market context, then shaping themes that clarify where the product is headed and why. I keep roadmaps flexible — they’re a tool for alignment, not a fixed plan.
I adjust the roadmap when new information makes it necessary, including user feedback, adoption data, technical limitations, or shifts in business priorities. If a feature isn’t being used as expected or feedback reveals new pain points, I work with stakeholders to re-sequence or pivot while keeping the overall vision intact.
Prioritization: How do you decide what to build next?
Macro prioritization depends on product maturity, long-term objectives, and user sentiment. At the micro level, I use a structured approach considering:
Customer Value
Business Impact
Technical Complexity
Strategic Alignment
Inputs include user research (interviews, feedback loops, help desk), product analytics (funnel drop-offs, usage metrics), and stakeholder input. I’ve used models like RICE and Value vs. Effort, but I view them as tools for discussion — not absolute rules.
Ultimately, prioritization comes down to the outcomes we’re trying to achieve and the associated risk. When uncertainty is high, I bias toward the simplest next step to learn quickly. When validation is strong, I focus on delivering value as efficiently as possible without disrupting users.
Data & Methods: What do you usually rely on in your product work?
Product Analytics (via any available tools or a PowerBI-like tool):
Behavioral analytics
(funnels, drop-offs)
Adoption metrics
(retention, feature usage)
Performance & reliability indicators
(load times, errors)
User sentiment
(NPS, support tickets)
Concept Validation:
Wireframing, prototyping, and experimentation to test hypotheses — through early designs reviewed with users or lightweight production experiments.
Market Analysis:
Market trends and competitor insights to complement internal product data, guide prioritization, and surface opportunities or risks.
Voice of Customer:
Survey insights, user interviews, support channels, and customer success inputs, synthesized using tools like Dovetail or Miro.
Conceptual Modeling:
Journey maps, story maps, flowcharts, experience diagrams, personas, ontologies, and other models to explore problem spaces and align teams around shared understanding.
Leadership & Communication
Expectations: How do you manage expectations without causing friction?
I focus on consistent communication and upfront framing. My goal is to align stakeholders on the outcomes we’re driving toward, rather than locking in on specific solutions. I make tradeoffs and constraints transparent early, and keep roadmap visibility high so no one feels surprised.
I also make a point of sharing the rationale behind decisions, ensuring stakeholders see the logic and thought process. Even if someone disagrees, they understand why the choice was made and can support moving forward.
When misalignment surfaces, I approach it with curiosity, asking clarifying questions and aligning on a plan that avoids compromise while seeking a win-win. Often this includes finding areas of agreement and either deferring low-priority debates or running small experiments to close knowledge gaps before making a larger commitment.
Example:
While at WWT, I consulted for an east-coast grocery chain that wanted to build a web app for generating quick-service restaurant menus, replacing a ticket-based process. After several weeks of discovery, I realized the app’s complexity outweighed its value. I reframed the conversation around opportunity cost, showing what would need to be deprioritized to build the app and demonstrating how the ROI aligned better with a small, low-code solution. By bringing data and a clear path to achieve the same outcomes, I helped the client pivot—saving $300K and redirecting resources toward higher-priority initiatives.
Delivery Team: How do you work with the delivery team day-to-day?
I adapt my level of involvement based on team composition, especially whether there’s a dedicated Product Owner.
Discovery Activities
In early exploration, I partner primarily with designers and/or tech leads to define and shape opportunities:
User research: Conducting interviews and synthesizing insights
Problem framing: Clarifying business goals, user needs, and constraints
Opportunity mapping: Using journey maps, story maps, and conceptual models
Feasibility alignment: Involving technical leadership to surface risks early
Concept validation: Supporting wireframing, prototyping, and user testing
Delivery Activities
Once a direction is chosen, I collaborate with the full delivery team to execute:
Remote coordination: Using instant messaging and virtual whiteboards for async work
Backlog ownership: Writing/refining user stories, prioritizing, sequencing
Documentation & visibility: Maintaining alignment via Jira, Confluence, Figma
Team rituals: Standups, planning, retros to track progress and resolve blockers
Remote Work: How do you keep a fully remote team aligned?
I use a mix of structured rituals and flexible async tools to keep teams aligned without creating meeting fatigue. My approach includes:
Rituals: Regular standups, planning, demos, retros
Async communication: Slack/IM for quick updates; Confluence for documentation
Visual collaboration: Figma, Miro, Jira boards for visibility and clarity
Transparency: Clear agendas, notes, and open access to artifacts
Availability: Keeping my calendar up to date and acknowledging requests quickly
I also emphasize building trust by sharing progress and risks/unknowns, encouraging others to do the same. This fosters a transparent, collaborative culture even in distributed environments.
Conflict: How do you handle disagreements?
I start by reframing the discussion around shared outcomes. Each team usually has a valid perspective, but from the viewpoint of their own priorities. By restating the problem we’re solving and the impact we’re aiming for, I create a common baseline.
Next, I break down each perspective so people feel heard and make tradeoffs explicit. For example, I outline:
Business Impact
User Impact
Technical Constraints
This clarifies what we gain or defer with each path.
If alignment still doesn’t emerge, I look for small experiments that reduce risk and give us data, or I propose a short time window (e.g., a month) to show progress. The goal isn’t to win — it’s to maintain momentum, preserve trust, and ensure decisions feel transparent and thoughtful, even when they’re not everyone’s preferred outcome.
Success
Success Criteria: How do you measure success for a product or feature?
I define success by aligning on outcomes for both the business and the user. I start by asking business stakeholders what success looks like to them—whether that’s adoption, revenue, retention, or efficiency. From there, I hypothesize what success would look like for the user and define appropriate measurements for both.
I use leading and lagging indicators to structure this thinking. Leading indicators might include adoption or activation metrics that show whether users are engaging as expected. Lagging indicators focus on longer-term outcomes such as retention, satisfaction, or revenue impact. Across roles, I’ve applied these concepts in different ways, but the goal is always the same: identify early signals of progress, connect them to long-term outcomes, and ensure the product is delivering meaningful value.
Achievements: What is one of your proudest achievements?
At Tolam Earth, as the Director of Product, I led the company’s first product from concept to MVP launch in just four months. This was a zero-to-one initiative in a complex space: building a digital carbon offset marketplace with deep regulatory, technical, and financial implications.
I defined the platform vision, created the roadmap, and scaled the team from two engineers to a 30+ cross-functional unit across three workstreams, working at both the strategic level and running one of the workstreams. I also developed the payments strategy, researching payment models, aligning with legal, and evaluating over 50 vendors before selecting a partner.
The MVP launch enabled us to secure a $2.5M enterprise contract. I’m proud of this product not just for the outcome, but for how we translated strategy into execution through speed, alignment, and focused delivery.