RD* studio

Case 06 — Take Blip · Internal DesignOps

The 1:1 that survives every reshuffle

Take Blip's design org reshuffled constantly — teams opened, disbanded, designers rotated across units. A designer's story got lost in every move, until the leaders agreed on one way to keep it.

Role
UX Design Chapter Leader — one of five design leaders
Scale
80 UX designers · 4 business units
Methods
Benchmarking · Qualitative research · Service blueprint · Journey mapping
Status
Internal — adopted across all design leadership
01 — The situation

An org built to reshuffle

I joined Take Blip as a UX Design Chapter Leader — one of five design leaders responsible for 80 UX designers spread across four major business units. Each unit ran multiple teams, typically a PM, a data analyst, a conversation analyst, a designer, and three developers, each handling one to four client projects at a time.

The org was designed to move. New teams opened, old ones disbanded, and designers rotated constantly — often switching business unit and leadership in the same move. Every rotation put a designer in front of a leader who knew nothing about their projects, their career trajectory, or how they were actually doing.

Standardizing how designers were tracked and managed was one of the first challenges I took on. The obstacle was not tooling — it was that five leaders each ran 1:1s and tracked progress their own informal way, in forms no other leader could pick up.

80UX designers
5design leaders
4business units
1–4projects per team
BU 01 BU 02 BU 03 BU 04
1 UX designer rotating — new team, unit, or leader team: PM · data · conversation · designer · 3 devs
01 — The operating reality: 80 designers in four business units, in constant rotation between teams, units, and leaders.
02 — The turn

Design the handoff, not a dashboard

Two decisions shaped everything that followed.

First: look outside design before proposing anything. Development, product management, and data analysis had been running 1:1s and tracking their people all along. I consulted leaders from each of those disciplines and compiled the findings into a benchmarking report of recurring themes and best practices. Design did not need an original process — it needed the best of what already worked around it.

Second: aim the system at the leader-to-leader handoff. Every rotation handed a designer to a leader with no record of their projects, their progress, or how they were doing. So instead of imposing a tool on designers, I designed and facilitated a workshop where the five of us mapped our informal processes and their commonalities, and turned the overlap into a shared standard. An agreement among leaders, so a designer's record could survive the move from one of us to the next.

The system's first user was not the designer — it was the handoff between two leaders.
Before × × context lost context lost After Team A · BU 01 Team B · BU 03 Team C · BU 02 record record
before — five informal processes after — one shared record
02 — The journey the system had to fix: a designer rotating through three teams. Before, each handoff reset their story; after, one record travels with them.
03 — The work

From five habits to one standard

  1. Benchmark three other disciplines

    Consulted leaders in development, product management, and data analysis on how they ran 1:1s and tracked team members. Compiled a benchmarking report identifying the key themes and best practices worth carrying into design.

  2. Surface the five informal processes

    Designed and facilitated a collaborative workshop with the other design leaders. We mapped how each of us actually ran 1:1s and tracked progress, then isolated the commonalities — the raw material for a standard everyone would recognize as their own.

  3. One script, one tracking framework

    Structured the system around two artifacts: a standardized 1:1 conversation script, and a framework for tracking projects, team dynamics, client interactions, and collaboration with PMs — the full context a new leader needs on day one.

  4. Indicators for the human side

    Defined metrics and indicators for career progression, emotional well-being, and overall role health — so the system tracked the person, not just the project list.

  5. Roll out across all design leadership

    Introduced the framework to every design leadership team, so that when a designer moved between teams or units, their record, career thread, and well-being history moved with them.

The standard — three artifacts 1:1 script Tracking framework Projects Team dynamics Client interactions PM collaboration Indicators Career progression Emotional well-being Role health
03 — Anatomy of the standard: the 1:1 script, the four tracking dimensions, and the three human indicators. Marker positions are illustrative — the structure is the artifact.
04 — Where it landed

It became how design leadership worked

The framework was introduced across all of Take Blip's design leadership teams. It significantly improved how UX designers were managed and supported: disruption from frequent reassignments was minimized, career guidance and project tracking got better, and alignment between leadership and design teams grew stronger — helping the design function scale while keeping designer satisfaction and growth in view.

This was internal DesignOps work, so the artifacts live inside the company — there is nothing public to link here. The diagrams above redraw the system's structure from the case documentation.

What this says about how I work

  • Research before opinion, even inward — an internal process problem got the same treatment as a client project: benchmarking, qualitative research, service blueprint, journey mapping.
  • One protocol, not five workarounds — my first instinct was not to fix my own 1:1s, but to build a standard all five leaders could share.
  • Leading peers by facilitation — the standard held because the other leaders helped map it in a workshop, instead of receiving it as a memo.