Haim Repael
CLOSE

Leadership

Taking Myself Out of the Bottleneck, Twice

A quality gate that waited on me, a reporting line nobody had drawn, and two ways to make a team faster by needing me less.

Haim Repael · 2 min read

STAR AT A GLANCE
Situation
Graphics QA held launches up for days, often waiting on me, and a new brand ownership in Marketing left unclear what should reach me.
Task
Remove myself as the bottleneck without lowering the quality bar or losing touch with what matters.
Action
Built a skill and an internal tool for GQA, had designers make the fixes and open pull requests reviewed by developers, and wrote one explicit reporting agreement with the brand lead.
Result
About twelve designer pull requests in three months, GQA runs during the launch so the delay is gone, and the reporting friction ended.

Some of the most useful leadership work makes you less necessary. Here it happened twice, in two very different places.

SituationTwo kinds of waiting

The gate. Before anything shipped, someone had to check that what was built matched the design to the pixel. That check, graphics QA, was an official Design Gate. It held projects up by a few days: the handover, then a session of fixes. Often it was waiting on me.

The line. When Sapir, who leads Brand, took more ownership of brand design inside Marketing, a gap opened. It wasn't clear what she should bring to me and what she should simply decide.

TaskKeep the bar, lose the queue

Quality couldn't drop, and I didn't want to lose touch with the decisions that mattered. But neither process should depend on my calendar.

ActionA tool for one, a document for the other

For GQA, we built a skill and an internal tool to run the process, first for developers. As the designers learned to write code, I worked with the developers so designers could make the GQA corrections themselves and open the pull requests. A developer still reviews and merges every one. Then the design team took over the gate itself, so it would stop holding up launches.

For Marketing, Sapir and I spent a month going through every Marketing process together. Then we wrote one detailed document: which meetings she runs alone and which I join, where I come in (creative direction, strategic thinking, brainstorming with the team, approving major new designs like a new website), and what she decides without reporting at all.

ResultThe delay is gone

  • Close to twelve designer pull requests in three months, each reviewed and merged by a developer.
  • GQA now runs while we launch to production, so the days of waiting disappeared.
  • The reporting friction ended. Sapir knows exactly when to bring me in, and I still know about everything I want to stay connected to.

What travels

A gate that only one person can open is not a quality process. It's a queue. Moving the gate closer to the people who do the work, with a reviewer still holding the merge, kept the bar exactly where it was and took the wait out of it.