What a fractional design lead actually does

They own design direction and the definition of good for your product, part-time, as a member of your team rather than a vendor delivering to a brief. The thing that separates it from advice is delivery ownership: they are accountable for what ships, not only for having opinions about it. Everything else — how many days, which meetings, whether they draw — follows from that and varies.

I do this work, so this is a description of a job I'm selling. The useful part isn't the description, it's the one question at the end of the next section, which is the question I'd want asked of me.

Why the definition is slippery

Most pages describing this role describe the activity. SeaLab's is a good one — it puts the person "inside your product process: attending standups, partnering with PMs and engineers, making architectural design decisions, and building the systems and culture that outlast the engagement." That's accurate, and the emphasis on integration rather than deliverables is the right emphasis.

But like nearly every page in this category, including the ones with prices on them, it doesn't say how much time the engagement is or what the person is accountable for. I checked; it doesn't commit to a number, and that isn't dishonesty. Engagements genuinely differ, and a page that promised "eight days a month" would be wrong more often than right.

The problem is what the vagueness does to a buyer. Two proposals can both say "fractional design leadership," quote a similar retainer, describe similar activities, and be different products.

The line that matters is delivery ownership

Here's the distinction, drawn from my own rate card because it's the clearest example I can point at without characterising someone else's business.

I sell two things that look identical from the outside. Fractional — $12k a month — owns the design direction and the system everyone builds against. Advisory — $5k — is standing access without delivery ownership: a weekly session, design review, help with hiring and org design. Same person. Often the same weekly meeting in the calendar.

The difference is what happens when someone asks "is this good enough to ship?" Under advisory, the answer is an opinion, and somebody on your team still has to decide. Under fractional, the answer is a decision, and it's mine, and I'm the one who's wrong if it was the wrong one.

That gap is most of the price difference, and it's most of the value difference too. It is also the thing that determines whether the engagement changes anything — because a team that already knows what to build and lacks only reassurance will get very little from the cheaper version, and a team that can't converge will get nothing at all from it.

So the question to ask any candidate, including me: when my team disagrees about a design decision and I'm not available, who decides, and are you accountable for the outcome? An answer that routes back to you is advisory, whatever the proposal is titled. That's not a worse product — sometimes it's exactly right — but you should know which one you're buying.

What ownership looks like when it's real

On EarthWonders, a 0→1 marketplace for fine-mineral collectors, the constraint stopped being design fairly early. It was iteration speed — the loop between deciding something and seeing it run was too slow to learn from. So I took GitHub access and built the hard surfaces as working prototypes against real data, so the team could argue with something they could click instead of a comp.

I bring that up as a definition rather than a credential. Owning delivery means the boundary of the job moves to wherever the work is actually stuck. If the answer to a blocked decision is "that's engineering's problem now," the ownership was nominal.

It has a limit, and it's worth stating plainly: one part-time person cannot be the permanent owner of a function. Fractional works when judgment is the constraint. It does not work as a substitute for a design team.

What the week looks like

For my engagements, concretely:

• One standing working session. Not a status meeting — the hour where open decisions get closed.
• Async availability for decisions in between. This is the part that actually determines whether a part-time arrangement works. A decision that waits six days for the weekly call has already cost more than the meeting saved.
• Hands-on work where it matters most. Usually the two or three surfaces that set the pattern for everything else.

Note what isn't there: daily standups, a review queue, and a ticket backlog. A fractional lead sitting in every ceremony is a full-time hire being paid part-time, and they will be the bottleneck within a month.

What they own, and what they don't

The last row on the left is the one that separates a good engagement from an expensive one. If the team can't converge any better in month six than in month one, the work didn't happen, however good the screens looked.

How it differs from the adjacent things

If you're still choosing between these, I wrote the longer version of that argument, and when to make the full-time hire instead is its own decision.

How to tell it's working, at day 60

Not "do I like the designs." Three checks that don't depend on taste:

1. Has an argument that used to recur stopped recurring? Specifically: can someone on your team state the rule that settled it?
2. Can somebody who isn't the design lead tell you what "good" means for this product in a sentence that would survive review?
3. Is there something running that people outside the team have formed opinions about? The deliverable should be something you can open, not a document about what it might become.

If all three are no at day 60, the engagement isn't working, and the honest move is to say so rather than renew and hope. That applies to me as much as anyone.

Related: what fractional design leadership costs, when to hire your first design leader, agency, fractional, or in-house, the EarthWonders build, and how I work.