Situation
When I stepped into the Design Manager role, the team was talented but fragmented. Design reviews were informal and inconsistent. Kickoffs happened late—often after engineering had already made assumptions. Bug triage was chaotic. Designers felt reactive, not strategic. The process wasn't broken in one place; it was slightly broken everywhere.
My Role
As the new Design Manager, I had both the mandate and the opportunity to reshape how we worked. I didn't want to impose process for its own sake—I wanted to understand where the real friction was and build the minimum structure needed to resolve it.
How I Brought Order
I ran a team retrospective in my first month: what's working, what's not, what we wish existed. I synthesized the output into three categories of pain: unclear briefs at project start, inconsistent feedback during design, and unclear handoff criteria at the end. Those became my three focus areas.
Design Work
Built a lightweight kickoff template that captures user goal, success metric, constraints, and out-of-scope in one page. Introduced bi-weekly design critique with a structured format (present context → ask a specific question → get targeted feedback). Established a handoff checklist that both designers and engineers sign off on. Ran a workshop series on design–eng collaboration that became quarterly.
Impact
Within two quarters, design team satisfaction scores (measured in our quarterly pulse surveys) improved from 6.2 to 8.4 out of 10. Engineers reported feeling 'more confident' in what was being handed to them. Project kickoffs with the new template had 2x fewer 'scope creep' flags from PM. The critique format was adopted voluntarily by two other product teams.
Reflection
Process design is product design. You're designing for the people on your team as users—understanding their frustrations, removing friction, and making the right behavior feel natural. The best processes disappear; they just make work better without anyone noticing the scaffolding.