When I decided to call myself a Fractional Product Design Partner, I thought I was giving a name to a new way of working. However, the more I look back, the less new it feels.
I have never been someone who stays for years inside the same product company or team. I tend to enter around a problem, help make sense of it, do the work, strengthen the team, and move on when the problem no longer needs me in the same way.
Solve the problem. Strengthen the team. Don’t make yourself permanently necessary.
I wasn’t working under fractional contracts then, but the instinct underneath the model was already there. Now I have decided to give it a name.
The question behind the calendar
The easiest way to explain fractional work is through time: one day a week, two days a week, a percentage of a role instead of a full-time hire.
It is also the least useful place to begin. The calendar tells you how time is allocated. It says very little about what the person will be responsible for or which outcome they are there to influence.
For a founder or product leader, the more useful question is: what is happening in the company that we cannot resolve with the capability we already have?
Maybe the team is shipping but the outcome is not moving. Research exists, but it is not changing the roadmap. A redesign feels urgent, although nobody agrees on what it needs to solve. Or the company needs senior design leadership but does not yet know whether that need is permanent.
These are not always capacity problems. They are often problems of judgement, direction, and leadership. Fractional Product Design brings senior involvement into one of these moments without assuming it must become a permanent role.
Access has to match responsibility
For this to work, access matters more than the number of days. Not access to every meeting, message, or document (nobody needs more meetings 😅), I need access to the context, evidence, people, and decisions shaping the product.
One of my current engagements began as a one-off audit of several pages in a content-heavy product. The expectation was that I would produce a report and the team would take it from there.
The audit showed that the problems did not live inside individual pages. The navigation told different stories in different places, important proof was difficult to find, and the visual language felt accumulated rather than coherent. I turned those findings into connected areas of work and a strategic roadmap.
But a roadmap is still a report.
To turn it into the product, I needed to work with the people making the decisions and doing the work. At first, I wasn’t always in those conversations. The recommendations existed, but the thinking behind them wasn’t reaching the right rooms.
Once that changed, I could move from diagnosing the system to helping the team change it from the inside out. The audit became an ongoing retainer. The new navigation and information architecture are live, and a new visual language has been delivered. The sales team is already reporting stronger engagement from existing clients with the new look and feel. It is early, qualitative feedback, and the work is still in progress.
But the diagnosis did not remain inside a document. We are turning it into the product together.
What the model asks from both sides
A company cannot ask someone to influence an important outcome while keeping them at the edge of the system producing it.
The engagement still needs boundaries: what the partner owns, which decisions they can influence, what remains with the team, and what should be different when the work ends. Within those boundaries, access has to match responsibility. The company needs an internal sponsor who opens the relevant rooms and remains accountable for what the organisation does with the work.
I have responsibilities too. I cannot hide safely inside recommendations. I need to stay accountable to what happens next and help the internal team become more capable rather than more dependent on me.
The goal is not to make myself permanently necessary. It is to help the company move through a consequential moment, leave the product and the decision-making stronger, and be honest about when the engagement should evolve or end.
Sometimes the answer is not fractional
Fractional should not become the answer to every hiring or product problem simply because the model is becoming more visible.
If the team knows what it needs to build and the constraint is sustained execution, it probably needs delivery capacity. If the company needs permanent ownership of its design people and direction, it probably needs a full-time leader. And if it cannot share context or provide access to decision-makers, a fractional partner will struggle to contribute beyond recommendations.
The stronger fit is a company that can build and ship but is facing a consequential decision or an outcome it cannot fully explain. It needs experienced judgement now, enough hands-on involvement to make the work real, and support that strengthens the team without assuming the need is permanent.
So before asking how many days a week you need a fractional partner, ask what you need that person to help change: which decision is difficult? What outcome is not moving? Which conversations will they need to enter? What will they be allowed to make real?
Because fractional is not a number of days, it is a different kind of relationship built around a specific need.
Maybe it is not a new way of working for me after all. Maybe it is simply the first time I have given the way I have always worked a name.
Thank you for being in the room,
Sónia
First published in the LinkedIn edition of In the Room, 2 September 2026.