One of the challenges of stepping into a new design leadership role is knowing what to carry forward from your previous experience and what to leave behind. Approaches that worked well in one organization can struggle in another, not necessarily because the ideas are flawed, but because the conditions are different.
Over several roles, I've shifted my thinking, focusing instead on understanding what the current workplace environment stimulates or represses before building anything.
This helps me develop strategies grounded in the team's reality, not just my past wins.
Ditch Your Solutions (For Now) and Learn the Landscape
Start by setting aside what worked elsewhere. An organization's conditions can support design efforts or quietly undermine them. Before introducing new processes, look for the patterns that help or hinder how people work together.
Gauge readiness early. Does leadership recognize design's value? Can partners take on new ways of working, or are they already overwhelmed? What pressures, such as cuts or reorganizations, might derail the effort? Do you have enough influence to act on what you learn?
Where design primarily serves other functions, the immediate priority may be delivering credible work, explaining decisions, and building influence rather than introducing a comprehensive strategic handbook. Nielsen Norman Group's work on UX maturity offers a useful reference here: organizational support, culture, processes, and outcomes matter alongside the design team's capabilities.
When starting a new role, I suggest a focused workshop with your design team and, where possible, colleagues from engineering or product. The aim is to understand how design actually functions: what supports it, what holds it back, and what the organization is ready to change.
At Meta, I conducted a three-day workshop while leading the Enterprise Infrastructure, Security, and Analytics (EISA) Design team. The sequence below reflects that experience, but the diagnostic principles can be adapted. Not every organization needs three days. In a startup under immediate pressure, a few shorter sessions may be more realistic. The point is to understand the conditions before prescribing solutions.
Day One: Where Are We?
Don't dive into big visions yet. Begin with the everyday hurdles.
At Meta, we mapped trust flows and resistance between groups, asking questions such as: How does engineering usually react to design ideas? Where do real product decisions happen? What sank the last design initiative, and why? Who holds informal influence?
These questions can uncover uncomfortable truths about an organization. That discomfort is part of seeing the landscape clearly.
Day Two: How Did We End Up Here?
Next, trace how things got this way. We examined decision histories, earlier failed attempts, and external pressures such as market shifts.
Past choices can make some changes easier and others harder. Understanding those choices helps explain stuck conversations and strained relationships rather than treating them as isolated problems.
It's not always easy, but I've seen this give teams the context they need to move forward without repeating old mistakes.
Day Three: Where Do We Want To Go?
The third day turned toward the future. The aim was to help the team identify its needs rather than wait for me to dictate them.
For leaders adapting this approach, bring the present, the past, and the hoped-for future together. Agree on commitments across time horizons appropriate to your organization. That might mean quick wins in 30 days, more substantial shifts over a year, and deeper changes over three. These are planning horizons, not promises.
At Meta, this work led to our first EISA Design & Research Handbook, with strategy, goals, and measures co-created across teams. In my experience, that shared work gave the handbook buy-in that an imported playbook would have lacked.
The connection matters: what you learn about decision-making, relationships, and constraints should shape the handbook's roles, processes, and priorities.
The handbook captures the agreements that emerge from the diagnosis.
Making Design Part of the Engineering Solution
A handbook is unlikely to help if it is written by designers alone and imposed on everyone else.
In Meta's engineering-heavy environment, we positioned design on page one as a front-end contribution to engineering. It wasn't a universal definition of design's role. It was a way to make that role understandable and useful within our organizational context.
Seek allies in product and engineering early. Look for people who see design's successes as shared successes. If those relationships aren't there yet, building them may matter more than documenting new processes.
Your Design & Research Handbook should capture agreements about:
- Roles and responsibilities within the wider organization.
- Success measures that matter beyond design.
- Processes that respect actual constraints, including deadlines.
- Communication that fits how partners work.
- How the handbook will be reviewed and updated.
Proven methods travel, but how you apply them varies.
User research, for example, can take different forms depending on the resources, relationships, and working rhythms available.
Keep the Handbook Useful
A handbook can become a burden if maintaining it consumes time without helping people work.
To prevent that, link reviews to business cycles, designate owners for sections, and record where practice diverges from the document. Use clear, shared measures to judge whether the agreed ways of working are helping. Keep the handbook responsive to organizational behavior rather than treating the document itself as the achievement.
I focus on cultivating conditions where design flourishes naturally, then document what emerges.
If a comprehensive strategic handbook risks becoming bureaucracy, choose something lighter, such as a shared wiki or quick-start guide. In an environment that suppresses collaboration, even carefully written documentation can gather dust.
Whether you're entering a mature organization or building a design practice from scratch, diagnosis helps you decide what needs to be captured, what needs to change first, and whether a handbook is the right intervention at all.
References
Pernice, Kara, Sarah Gibbons, Kate Moran, and Kathryn Whitenton. “The 6 Levels of UX Maturity.” Nielsen Norman Group, June 13, 2021. Last reviewed January 24, 2024.
