How We Partner With Clients: A Deep Dive Into Our Product Consulting Process

Product development isn't one-size-fits-all. Every company brings its own challenges, opportunities and constraints, and those shape how a fractional CPO engagement actually runs. After 20 years working on consumer products, I've found that what works is a proven framework, heavily customized.

The belief underneath all of it is simple: use data and research to find where growth actually is, rather than where it feels like it should be. That shapes everything from the first discovery session through long-term execution.

What makes this different from a consultant

Worth saying at the outset, because the labels in this space are used loosely: fractional CPO, interim CPO, consultant and advisor are four different arrangements, and most disappointing engagements are the wrong one bought under a familiar name.

When a company brings me in as their fractional CPO, they're not getting someone running a fixed playbook. They're getting someone who would rather understand the situation than assume it. I spend real time upfront building an accurate picture and a strategy, because without that foundation even excellent execution goes in the wrong direction.

That means the process looks different from most product consulting. Where others jump straight to tactics, I stay in product discovery and research long enough to be sure. It pays for itself across the engagement, because every decision afterwards rests on real data and genuine customer insight rather than on the loudest opinion in the room.

The other half is customization. The framework below has been refined over 20 years, and I adapt it every time. A startup with three engineers has different needs from an established company entering a new market. The framework provides structure; the flexibility is what keeps it relevant.

The 10-step product consulting process

Here's how an engagement typically unfolds. Every step gets adapted to your circumstances, but the shape holds.

1. Discovery: understanding your reality

Every engagement starts with understanding. We'll have one or more sessions covering your company, team, leadership structure, current needs and the opportunities already in front of you. This isn't only about what you think you need — it's about what's actually happening underneath.

During discovery, we're looking for what you truly need to succeed and grow your product. Maybe your team thinks users want feature X, but the data suggests they're actually struggling with workflow Y. Maybe leadership believes the product is ready to scale, but technical debt is creating unseen bottlenecks. These insights shape everything that follows.

2. Planning: creating aligned direction

Once we understand your situation, I'll build a plan for moving forward. As a believer in agile methodology (especially for startups), I don't create year-long plans that become obsolete within months. Instead, I focus on creating a plan that everyone can align behind, with concrete KPIs that measure success.

This planning phase is crucial for product strategy development because it ensures we're all working toward the same goals. We define what success looks like, establish metrics for measuring progress, and create accountability structures that keep everyone focused on outcomes rather than outputs.

3. Data: building trust in your foundation

You'd be surprised how many startups and established teams don't trust their own data. This lack of confidence creates decision paralysis and leads to gut-based choices that often miss the mark. My data-driven consulting approach includes a deep dive into your data ecosystem to ensure it's robust, accurate, and actually useful.

Sometimes this means creating new dashboards that surface the metrics that matter most. Other times, we need to improve your instrumentation to capture data you're currently missing. Occasionally, we discover that the data exists but isn't being interpreted correctly. Whatever the situation, we ensure we have reliable data before making strategic decisions.

I care about this more than is strictly reasonable, and it's usually where the first real surprise turns up. On one fintech engagement, instrumentation alone revealed that a large share of users were taking free credit and never purchasing — a problem nobody could see before the tracking existed.

4. User research: uncovering real opportunities

Data tells you what happened. Research tells you why, and what might happen next. We research your company, competition, customers, partners and market dynamics — how much of each depends on the plan from step two, but the aim is always to validate or challenge an assumption you're currently treating as fact.

This research phase often reveals surprising insights that reshape product strategy. Maybe your biggest competitor isn't who you thought it was. Maybe your customers are using your product in ways you never intended. Maybe there's an adjacent market opportunity that's been hiding in plain sight. These discoveries become the foundation for strategic decision-making.

5. Strategy and hypothesis: creating your path forward

With solid data and thorough research in hand, we can build a set of hypotheses we want to prove or disprove. This is where product consulting becomes truly strategic—we're not just identifying what to do, but why to do it and how to measure whether it's working.

My approach emphasizes hypothesis-driven development because it creates accountability and learning opportunities. Instead of implementing features and hoping they work, we're testing specific beliefs about user behavior, market dynamics, or technical capabilities. This approach reduces risk and accelerates learning.

When opting for the Fractional CPO route, not only will I build the strategy, we'll partner together for the long term to improve and iterate on the strategy and hypothesis as we release and learn.

6. Roadmapping: translating strategy into action

Strategy without execution is just planning. We build a working product roadmap that turns strategic thinking into something your team can actually execute. Whether I'm driving execution directly as fractional CPO or advising, the roadmap has to align with the strategy, be feasible with the resources you have, and be clear enough that people can act on it without asking.

Sometimes roadmapping reveals execution challenges that require process improvements. Maybe your development team needs better project management tools. Maybe your design process creates bottlenecks. Maybe communication between departments needs strengthening. My fractional product leadership addresses these foundational issues alongside strategic planning.

7. Design and technical planning: making it real

Good product strategy needs good execution, which means working closely with UX and UI designers as well as engineering. I work with your existing designers, or bring in a designer I trust, to hold the quality bar.

Having been a software engineer and a CTO for over a decade, I know what building a product actually takes — and how much the difference between a two-week problem and a two-quarter one matters when you're choosing what to build.

Technical planning matters just as much as product planning, because the best idea still fails if it isn't feasible or can't scale. I'll work with your engineering team on plans that are realistic and built for velocity.

8. Test planning: measuring what matters

If we decide to run A/B tests (and we often do), I plan them meticulously. This includes defining the tests themselves, identifying the right metrics to track, creating analysis plans, and establishing success criteria. Poor test planning leads to inconclusive results, so we invest significant effort upfront.

Even when we're not running formal A/B tests, I plan launches with measurement in mind. What metrics will tell us if the product is succeeding? How will we identify potential problems early? What feedback mechanisms will help us iterate quickly? These questions shape how we approach every product launch.

9. Execution and going live: maintaining high standards

During execution, I work alongside your team and any external partners to maintain the highest standards. My fractional CPO role often involves removing blockers, facilitating communication, and ensuring quality doesn't suffer under deadline pressure.

Going live is just the beginning, not the end. I help teams prepare for launch day challenges, monitor early performance indicators, and respond quickly to unexpected issues. Experience has taught me that even well-planned launches can surprise you, so I stay actively involved through the critical early days.

10. Measuring and iterating: getting the rest of the value

First releases rarely reach their full potential, however thorough the research was. That's why measurement and iteration are built into the process from step one rather than bolted on at the end.

After going live, we measure impact against our original hypotheses, analyze what worked and what didn't, and iterate toward full success.

This phase often reveals new opportunities or challenges that weren't visible during planning. Maybe users love the core feature but struggle with onboarding. Maybe adoption is strong in one segment but weak in another. Maybe technical performance is creating user experience issues. My approach treats these discoveries as learning opportunities that inform the next iteration.

Why experience matters here

After 20 years and a lot of companies, I've seen most of these challenges before. That lets me anticipate problems, prepare for them, and help clients step around the common pitfalls. It doesn't mean I have every answer — every product situation is genuinely its own — but it does mean I recognize the patterns quickly.

In practice this shows up early. When a client describes their challenge, I can usually predict the second and third problems it will cause and what they'll need to handle them, which makes for more realistic timelines and more accurate budgets.

Structure, but not rigidity

The framework provides structure; adapting it is what keeps it useful. Markets shift, user preferences move, technical capabilities change. A rigid approach to product strategy dates quickly, so I hold the principles constant and adjust the methods.

That extends to how I work with your team. Some clients want hands-on fractional product leadership with me embedded in daily operations. Others want strategic guidance and will run execution themselves. Some situations call for rapid iteration and frequent pivots; others reward steady, methodical progress. Whichever it is, the hardest part is usually agreeing on what we're not going to do.

Getting started

If you want to work out whether this fits your situation, the place to start is a conversation about where you actually are.

The intro call is free and takes 30 minutes. We'll go through your current product challenges and your growth goals, and see whether this approach matches what you need. If a lighter touch is what you're after, 1:1 mentorship covers some of the same ground at a much smaller commitment.

The call is worth having whether or not we end up working together. Talking a product problem through with someone who has seen it before tends to produce clarity on its own.