Fractional product design lead

The problem this solves

There is a stage where a full-time design hire is the wrong shape. The product needs a design decision most weeks and a designer's full attention rarely; the engineers are ahead of the design; and the founder is making calls about hierarchy and flow in the gaps between everything else.

The failure mode is not that nothing gets designed. It is that decisions get made where they are cheapest to make — in a ticket, at the end of a sprint, by whoever is implementing — and never written down. Six months later the product has four ways to do the same thing and nobody can say which is right.

A fractional arrangement is two or three days a week of someone owning that. Not a queue of screens delivered on request, which is a contractor with extra steps, but the design decisions themselves: what ships, in what order, at what quality, and why.

What you get

• Design decisions owned, not queued

  I sit in the planning, argue the trade-offs early, and answer the questions that would otherwise get resolved silently in a pull request.

• Design work shipped every cycle

  Flows, screens and states for what is actually being built, at the pace your engineering runs. Reviewed against the product, not delivered into a folder.

• The patterns written down as they emerge

  A small system that grows out of what the product needed, rather than one designed up front against guesses. Enough that the fifth table looks like the first.

• A team that can carry it

  Whoever ends up owning design after me should be able to. That means the reasoning is written down, not just the screens.

How it runs

1. 1

   Two weeks of listening first

   The product, the roadmap, the users you can reach, and the decisions currently getting made by default. Nothing structural changes in that time.

2. 2

   Name the three things that matter this quarter

   Agreed with whoever owns the outcome. A fractional lead who works on whatever is loudest is an expensive way to stay busy.

3. 3

   Join the cycle you already run

   Your planning, your standups, your tooling. Design that runs on a parallel schedule is design that arrives late by construction.

4. 4

   Ship, review, write it down

   Each cycle produces the work and the reasoning behind it. The second part is the difference between a design lead and a supplier.

5. 5

   Plan for the handover from the start

   The arrangement is meant to end, usually into a full-time hire. I would rather help scope that role than become load-bearing.

The longer version of this, with what happens in each week, is on the process page.

Where this has been done

• Home-care staffing and scheduling

  2 sides, 1 platform, 401 screens

  A home-care agency was running a nurse marketplace, a scheduling board, clinical records and payouts as four separate problems. Designing them as one product, for two sides of the same market, is sustained work rather than a project with an end date.

• Public tender discovery platform

  0 to 1, 7 core surfaces

  Public tenders are published by law and invisible in practice. The product that finds them, warns you in time, and gets a business to a go or no-go in minutes rather than a day had to be designed surface by surface, in the order the build needed them.

Typical engagement

Typically two or three days a week on a rolling monthly basis, with a month's notice on either side. Three months is the shortest block worth starting: the first two weeks are spent learning the product and a shorter engagement never gets past that.

Most of these end in a full-time hire, which is the intended outcome rather than a lost account. I will help write the role and sit in on the interviews.

Who this is not for

• You need a designer available every day at short notice. That is a full-time role, and a fractional one will keep disappointing you.
• The work is a fixed, well-specified piece with a clear end. A sprint or a project quote is cheaper and cleaner.
• Design decisions have to be approved by a committee that meets fortnightly. The value here is decisions made at the speed the build runs.
• You want capacity to execute someone else's already-final designs. That is production work, and there are better-priced people for it.

How I think about this

• Your design system isn't slow. Your product decisions are. — the debt that builds up when decisions are made in tickets
• Feedback needs a subject, and taste is not one — how a weekly review stops being about preference
• You can skip Figma. You can't skip design judgment. — what part of this role does not get faster with better tooling
• Loom was won in the settings menu — the kind of small ongoing decision that compounds

Frequently asked questions

What is a fractional product designer?

Someone who owns the design of a product a few days a week rather than full time, on an ongoing basis. The distinction that matters is ownership: a fractional lead sits in planning and makes the calls, where a contractor takes a defined piece of work and returns it. Companies use the arrangement when the decisions are weekly but the workload is not.

How many days a week do you work with one company?

Two or three, usually fixed days so your team knows when I am there. Fewer than two and I am reacting to what happened rather than shaping what is next, which is the part you are actually paying for.

How long do these arrangements run?

Three months minimum, rolling after that with a month's notice. The first two weeks are spent learning the product and changing nothing, so anything shorter is mostly onboarding.

What happens when we hire a full-time designer?

That is the intended ending. I will help write the role, sit in on interviews if useful, and hand over across a notice period. The patterns and reasoning are written down as the work happens precisely so that handover is not a crisis.

Do you work with our existing engineers or bring a team?

Yours. I join the cycle you already run, in the tools you already use. Design on a parallel schedule with a separate team arrives late by construction, and it is the most common reason these arrangements feel slow.

What timezone do you work in?

Karachi, UTC+5. That overlaps most of the European working day and the US East Coast morning. Planning and reviews get scheduled at your end of the day rather than mine.