Rituals for design quality

Scaling a design team with lightweight practices to ensure consistent outcomes.

The challenge

When I took on the Head of UX role at SoftServe, the team grew from 7 to 26 designers across multiple locations. With that growth came a challenge: maintaining consistency and design quality. Each designer had a different approach, leading to fragmented workflows, varying usability standards, and misalignment across projects.

Instead of adding overhead, I introduced pragmatic rituals—lightweight, high-impact touchpoints that helped designers align, iterate effectively, and maintain high standards. These rituals became an integral part of our workflow, improving quality while keeping up with the fast-paced environment.

Feedback and iteration

In a fast-paced outsourcing environment, designers work across multiple projects with tight deadlines. There’s no time for lengthy review cycles or endless iterations. Yet, without structured feedback, inconsistencies creep in—misaligned UI elements, usability gaps, and overlooked design principles. I needed a way to embed quality into the process without disrupting efficiency.

At SoftServe, I introduced four key rituals to create fast, focused, and high-impact feedback loops. These weren’t just meetings—they were practical touchpoints that helped designers stay aligned, iterate quickly, and elevate their work.

Weekly design critiques and jams

Early on, I noticed that designers often worked in silos, missing opportunities to learn from each other. When issues surfaced, they were already too late in the process, requiring costly fixes. To address this, I introduced small-group critiques—teams of up to five designers reviewing each other’s work. The goal wasn’t just to identify flaws but to sharpen problem-solving skills and push designs further.

Sometimes, critique wasn’t enough. That’s where design jams came in. Instead of just discussing feedback, designers collaborated in real-time to explore variations and refine tricky details. This practice not only improved individual projects but also built a stronger, more connected design culture.

Leadership design reviews

With designers moving fast across multiple projects, I needed a way to catch critical issues before they escalated. Instead of a single review at the end, I set up checkpoints at key milestones: problem framing, concept validation, high-fidelity design, usability testing, and pre-release.

These weren’t rigid approvals but structured discussions—a chance to ensure clarity, challenge assumptions, and strengthen decisions before they reached development. The outcome? Fewer late-stage revisions, stronger stakeholder alignment, and a clearer path from idea to execution.

Monthly design update

One of the biggest challenges in a growing team is visibility. Designers were solving similar problems, yet knowledge-sharing was limited. To fix this, I introduced a simple but effective habit—each designer prepared one slide per project with objectives, mockups, and a Figma link.

This wasn’t just documentation—it created an async space for feedback. Designers could browse, compare solutions, and comment without interrupting their workflow. Over time, this practice led to more consistent design patterns, faster iteration, and fewer redundant discussions.

Office hours with experts

Not every design challenge fits into a critique or a leadership review. Sometimes, designers needed deeper conversations—whether about design systems, research insights, or content strategy. Instead of forcing ad-hoc discussions, I introduced dedicated office hours where specialists were available to consult on complex problems.

This simple shift had a huge impact. Instead of waiting for approvals or making isolated decisions, designers had direct access to expertise at the right moment. As a result, decisions were made faster, design consistency improved, and execution became smoother.

Learning and improvement

Good design isn’t just about how a product looks before launch—it’s about how well it works once users get their hands on it. A feature may pass usability testing, but real-world use often exposes gaps, edge cases, and friction points that weren’t obvious during design. To keep improving, we needed ways to learn from actual usage, uncover hidden issues, and turn insights into better experiences.

I introduced three key rituals to make learning and iteration a structured part of our process.

Deep dive sessions

In fast-moving projects, teams often move on too quickly, missing the opportunity to reflect on what worked and what didn’t. To fix this, I introduced deep dive sessions at two key moments—before launch, to ensure we weren’t overlooking critical insights, and after release, to assess what needed improvement. These discussions helped us move beyond gut instinct and make refinements based on real user behavior and usability findings.

Real-life product experience

Designers often rely on user feedback but don’t always experience the product firsthand. To close this gap, I encouraged the team to use our product just like our customers would—not in test environments, but in real-world scenarios. They then shared their struggles, surprises, and usability pain points in open forums. This built a stronger sense of empathy and led to polished, frustration-free interactions that wouldn’t have surfaced in controlled testing.

Bug bashes

A polished design in Figma doesn’t guarantee a flawless experience in production. Minor inconsistencies—misaligned elements, incorrect paddings, or broken interactions—often creep in, leading to a disjointed experience. To prevent this, I introduced bug bashes where designers and developers tested the product together before launch. This hands-on approach helped catch errors early and educated engineers on key design principles, improving execution quality over time.