The Situation
The agile training was there. The cycle-time gains weren't.
Vistaprint was in the middle of a company-wide agile transformation, but the Product Design organization wasn't seeing the cycle-time gains other teams were. Briefs sat in queue. Strategy and Creative talked past each other. Operations was firefighting handoffs. Designers were spending almost as much time waiting and chasing as they were creating.
The team had been trained on agile in the abstract — sprints, standups, retros — but training hadn't translated into a different way of working. What they didn't have was a clear definition of who was responsible for what, an accurate picture of where time was actually being spent, or an operating rhythm that surfaced bottlenecks while there was still time to fix them.
The Intervention
I led the agile rollout inside Product Design — starting with where the time was actually going.
The work was sequenced deliberately: diagnose before redesigning, pilot before scaling, and only train the broader team on the framework once the operating mechanics were already proven on a real project. Six stages, in order:
-
Diagnose with the team, not at them.
Ran working sessions with Strategy and Creative leads to surface the real friction — what wasn't working, where time was being lost, where roles were unclear — and clustered findings into root causes leadership could act on.
-
Map the actual workflow.
Built a Value Stream Map of the end-to-end Product Design process — every step from planning through brief, concept, buildout, review, and release — categorizing each as value-add or waste so the conversation was about evidence, not opinion.
-
Pilot on the biggest waste source first.
Business identity card design consumed 56% of design resources and generated hundreds of "filler hours" of unassigned time each year. Designed a continuous "pull" system (no release-bound scoping; designers grab next set when done) and tested it across five full project releases with a named pilot team before any broader rollout.
-
Redefine roles based on what the brainstorms surfaced.
Re-distributed Team Lead vs Art Director responsibilities and reset meeting attendance and etiquette — so the right voices were in the right rooms at the right stages of the work.
-
Replace meeting volume with operating cadence.
Designed a clean weekly grid — TL reviews, AD reviews, Client reviews on alternating days — that gave designers more sign-off windows, less stop-and-start, and a visible progress board.
-
Scale the framework after the mechanics were proven.
Once the pilot demonstrated cycle-time gains, mapped Strategy / Operations / Creative functions to the Value / Flow / Quality (VFQ) framework so every team member could articulate the question their role was responsible for answering — and stood up five cross-functional squads pairing TL, Creative Lead, Product Owner, and designers around specific customer pipelines.
The Result
Cycle time cut in half — earned by mapping the system before changing it.
By the time the new operating model was running across all squads, projects moved from assignment to completion in ~6 days instead of ~14 — a ~56% reduction in cycle time without changing the team, the brief volume, or the quality bar. The Product Design organization caught up to and then surpassed the cycle-time targets the broader agile transformation had set.
The more durable output was structural: the team had a vocabulary (VFQ), a structure (cross-functional squads), and a measurement system (cycle time + first-pass approval rates) that made future improvements traceable. When something slowed down, standups surfaced it the next morning. When something improved, the retro captured the pattern so the next squad could use it. And because the rollout was earned through a real pilot — not just decreed — the team owned the changes from the start.