If your designers are always the bottleneck, the problem probably isn’t your designers. In most teams I join, design is late because it’s brought in too late, and that’s a leadership problem with a clear fix.

It’s a sequencing problem, not a speed problem

The pattern is almost always the same. A product manager writes a ticket or a spec. It’s handed to design with the expectation of polished, high-fidelity screens in a few days. Engineering is already waiting, so design becomes the thing everyone is waiting on.

Making designers work faster doesn’t fix this. By the time a ticket reaches design, the important decisions have already been made without them: what the feature is, what problem it solves and how it fits the product. Design is left to colour in someone else’s outline. When it inevitably raises questions, those questions look like delays.

So when design is chronically late, I don’t start with the designers. I start with when they get involved.

Where the time actually goes

Before changing anything, I look at where work stalls. In my experience, “late design” usually means design is waiting on someone else:

  • A founder’s approval that only happens at the end, when changes are most expensive.
  • Shifting requirements from product, so the brief changes after the work has started.
  • Late technical objections from engineering, raised once designs are finished rather than while they’re being shaped.

None of these is a design problem, but each one shows up in the plan as design running over.

The first four things I change

1. Run discovery and delivery as two tracks. I split product work into two parallel streams: discovery, which works out what to build, and delivery, which builds it. Design works one or two cycles ahead of engineering, so by the time a feature is ready to build, the thinking is done.

2. End the “big reveal”. Designers shouldn’t disappear for two weeks and come back with a finished, end-to-end solution. I ask for rough sketches or wireframes within 48 hours of starting anything. Early, scrappy reviews catch wrong assumptions while they’re still cheap to fix.

3. Agree a proper “definition of ready”. Engineering doesn’t estimate or schedule a ticket until approved designs are attached to it. This one rule changes behaviour quickly, because it makes design a visible part of planning instead of an afterthought.

4. Fix the feedback loop. I map who needs to approve what, and when. Often that means moving a founder’s input to the start of a piece of work rather than the end, and bringing engineering into reviews while designs are still flexible.

None of this needs a bigger team. It needs someone senior enough to change how product, design and engineering work together, which is exactly where a part-time design lead earns their keep.

What a fractional design lead does in a typical week

I usually work with a team for one or two days a week. A typical week looks like this:

  • Embedded time. I’m in the team’s Slack, in the key leadership meetings, and running design reviews, so I work as part of the team rather than as an outside adviser.
  • A standing hour with the founder or product lead to talk through what’s coming, what’s blocked and what needs deciding.
  • Two to three hours on design and engineering alignment: how the design system, research and day-to-day workflow connect with product and engineering, so teams aren’t building in silos.
  • Two to four hours of coaching: mentoring designers, clarifying roles and helping the team grow.
  • Quiet, focused work between meetings: reviewing research, drafting decision frameworks, looking at metrics, and sorting out the structural problems that never fit into a meeting.

The aim isn’t to be in every conversation. It’s to put the structure in place so the team makes good design decisions without me in the room.

When you need a full-time head of design instead

Fractional leadership is ideal for setting up the foundations, fixing processes or covering a leadership gap. It isn’t the right answer forever. These are the signs a company has outgrown it:

  • Your design team reaches four or five people. A part-time lead can support one to three designers well. Beyond that, one-to-ones, career development, reviews and hiring need someone there full-time.
  • Design is needed in every sprint, every day. If several product teams need design input at stand-ups and in daily problem-solving, you need someone who’s always available.
  • Design needs a permanent seat at the leadership table. Owning budget, long-term goals and board conversations is a full-time executive job.
  • The team needs a leader who’s part of the culture. As a company matures, it needs a design leader with deep knowledge of the product and a long-term stake in the team.

Part of a good fractional lead’s job is to help you get to that point: shaping the role, writing the brief and helping you hire the right person.

Where to start

If design always seems to be the bottleneck, look first at when design is brought in, not at how fast designers work. If you’d like a senior view on what’s slowing your team down, get in touch.