TLDR: If you need deep execution in one narrow area with a strong team already around it, hire a specialist. But if your real problem sits at the intersection of product, data and delivery (which is where problems usually live), a fractional product generalist who can work across all of it is typically faster, more useful and better value.
Click to discuss this article with your favourite AI
There’s a hiring instinct that feels completely rational: when something isn’t working, find the person who does that thing for a living.
Conversion is soft? Find a CRO specialist. Analytics are a mess? Bring in an analytics consultant. Product direction is unclear? Hire a product manager.
You have a problem. You find someone whose entire professional identity is solving that exact problem. Clean logic.
The trouble is that most real problems aren’t that clean.
What people actually mean when they say “specialist”
When someone hires a subject matter expert, they’re buying depth. Deep knowledge of one tool, one discipline or one methodology. Someone who has spent years getting very good at exactly one thing.
That’s genuinely valuable in the right context. A specialist sitting inside a mature team, with a clear brief and strong adjacent support, can do exceptional work.
But fractional engagements don’t usually land in that context.
Businesses bringing in fractional product support are usually in one of a few situations:
- No full team in place yet
- Had one, but it got expensive to maintain
- Have some people but not the right mix
- Things have grown faster than the current setup can handle
In all of those situations, the problem is rarely just one thing. It’s the space between things.
The gaps are where it breaks
The pattern usually looks something like this:
- Data collection in place, but no-one turning it into decisions
- A/B tests running, but disconnected from the product roadmap
- A dev team ready to build, but no-one to translate the brief into something actionable
None of those are specialist problems. They’re coordination problems. And coordination problems need someone who can see the whole board.
A specialist brought into one of those situations tends to solve their piece well and then stop. The analytics consultant tidies the implementation and hands back a clean setup. The CRO person designs a testing programme. The PM writes a roadmap. Each piece is fine on its own. But the pieces don’t talk to each other, because no-one is responsible for the connections.
That’s not a failure of the individual specialists. It’s a mismatch between the type of problem and the type of hire.
The strongest argument for a product generalist is exactly this: their broad knowledge lets them anticipate dependencies, translate between disciplines and hold an overall picture of what success actually looks like. They’re the person who notices that the experiment you ran last quarter contradicts the assumption your roadmap is built on. Or that the analytics implementation can’t support the reporting you’re planning to build. Or that the feature your dev team is about to ship doesn’t match what your users are actually trying to do.
None of that requires being the deepest expert in any single tool. It requires having worked across enough of them to know how they interact.
The economics are simpler than they look
There’s a practical angle here too, and it’s worth saying plainly.
A fractional product generalist can cover ground that would otherwise require multiple separate engagements running in sequence. One person who can run your analytics audit, help design your experimentation programme and translate product requirements to your dev team costs less than three specialists brought in one after the other. Each needs to be briefed, onboarded and managed separately.
And because that one person holds context across all of it, nothing gets lost in the hand-off. The insight from the analytics work informs the experiment design. The experiment results feed back into the product decisions. The whole thing compounds instead of resetting each time a new specialist starts.
The fractional model has moved well past novelty. It’s now a deliberate choice businesses make when they want senior cross-functional experience without the overhead of a permanent hire who covers only one lane.
Senior fractional product generalists typically work across 10 to 20 hours per week per engagement. The cost is significantly lower than a full-time salary, and the breadth of what gets covered in those hours can be wider than what a permanent specialist covers in a full week.
When a specialist is genuinely the right call
I want to be honest about where this argument doesn’t hold, because there are real situations where a specialist is clearly the better answer.
If you have a specific, technically complex problem, such as a server-side experimentation architecture, a full Adobe Analytics rebuild or a data pipeline that needs a proper data engineer, a generalist is not who you want. Bring in the specialist. That’s what they exist for.
If your team already has strong product and strategy coverage and you simply need execution within a specific platform, the same logic applies. Go narrow. The generalist adds noise, not value, when the coordination problem has already been solved.
And if you’re operating at scale with large, defined digital disciplines, specialists are essential. You need people who stay in their lane and go deep.
The product generalist case is strongest when:
- You’re lean and need one person to cover a meaningful amount of ground
- The problem crosses disciplines rather than sitting inside one
- You need someone to hold both strategic direction and technical context at the same time
- You want someone who will coordinate and execute, not just produce a report and leave
What this looks like in practice
I’ll be direct about where I sit in this, because I think it’s more useful than a vague pitch.
My depth is in experimentation. I’ve designed and run over 250 experiments for companies including Bupa, RedBalloon and Deep Blue Company, with roughly $70 million in measured incremental revenue across that work and has won awards. That’s the specialist credential.
But experimentation doesn’t exist in isolation. It depends on solid analytics, a product roadmap worth testing against and a development team that can ship clean treatments. I’ve worked across all of that: analytics implementation across GA4, Adobe Analytics, Segment and others, product management from discovery to delivery and enough of the technical layer to understand what’s actually feasible before anyone writes a brief.
That combination is what a T-shaped product generalist means in practice. Deep in one place. Functional across the rest. The two things reinforce each other.
An experiment result means something different when you also understand the analytics implementation it came from. A product decision lands differently when the person making it has built reporting and knows what data you’ll actually have to measure it against.
That’s the product generalist case, stated plainly. Not that specialists don’t know their area well. They do. The question is whether the problem you’re actually trying to solve lives inside one area.
In my experience, most don’t.
They’re the kind where someone needs to look at the whole thing, say “that’s where it’s breaking” and then actually do something about it.
Fractional support for Fractional leaders
The product generalist skill set complements other fractional leaders by allowing them to plugin in needed resources to complete the strategies they provide their clients. You don’t need to hire a team or maintain a roster of freelancers.
Supercharging small to medium businesses
The product generalist skill set means one hire for many deliverables, you supercharge your growth without having to make multiple hires and you know exactly who you are working with.