Design leaders face a familiar challenge: being responsible for the quality of the work without having sufficient influence over the conditions that shape it. We can develop talented teams, give thoughtful feedback, and build strong relationships, yet still find design treated as a service brought in after important decisions have already been made.
I’ve spent years working to develop design teams from isolated functions into interconnected systems and infrastructure. That work has changed how I understand design leadership. Supporting designers matters, but so do the arrangements through which they collaborate with other disciplines, the incentives shaping product decisions, and the organizational structures that determine where design judgment counts.
My Scalar Leadership Approach is a framework for leading design organizations. It brings these responsibilities together through an evolving synthesis of systems thinking, scholarship on scale, and professional practice.
Its central proposition is straightforward: changing the scale at which we examine a design-leadership problem can change what we understand the problem to be, which conditions require attention, and what interventions become possible.
The aim is not to become a design leader who personally holds everything together. It is to create conditions in which designers and their partners can exercise judgment, agency, and leadership.
What makes design leadership scalar?
My academic development and professional practice have continually informed one another. Over approximately a decade of studying and practicing design, including my education at Parsons and doctoral work in Transition Design at Carnegie Mellon, systems thinking became a way of asking questions about the work: What relationships sustain this situation? Where do decisions originate? Who experiences their consequences?
Several works helped shape this orientation. Donella Meadows’s Thinking in Systems explains why addressing one part of a system in isolation can leave interconnected problems unresolved. Charles and Ray Eames’s Powers of Ten makes changing perspective across physical scales tangible. Jamer Hunt’s Not to Scale examines the complications of scale and connections between everyday decisions and consequences that exceed our immediate view. [web:16][web:38][web:36]
These works did not provide a ready-made leadership framework. My contribution is to bring a systems-and-scale orientation into the practical realities of designing, building, managing, and leading design organizations.
Those realities require attention to several interconnected conditions: the capability of designers and teams, the relationships between design and other functions, and the institutional arrangements shaping design’s participation in decisions. A difficulty encountered in one place may be sustained elsewhere.
Organizational life does not map neatly onto physical magnitudes, and a wider view is not necessarily a better one. Sometimes the important detail is a designer’s uncertainty about a decision they are expected to make. Sometimes it is a dependency between teams. Sometimes it is an incentive that makes everyone’s local decisions reasonable while producing an outcome nobody wants.
Scalar thinking means moving between these frames without assuming that one contains the whole explanation.
Three modes, not three stages
The approach operates through three modes: Scale Deep, Scale Wide, and Scale Up. They are not a maturity ladder. A design leader does not finish developing people before addressing collaboration or wait for perfect collaboration before questioning an organizational policy.
Nor are the modes simply positions in a hierarchy. They describe different ways of examining and intervening in the conditions surrounding design. A designer can identify an institutional constraint; a senior leader may need to work closely with an individual. A single conversation may require attention across all three modes.
Scale Deep: Design the People Systems
Scale Deep concerns individual capability, team cohesion, and the conditions that allow designers to exercise judgment.
In my leadership practice, I’ve used “air cover” to describe part of this responsibility: knowing team members as whole people, understanding their aspirations, and providing support without taking ownership of every decision. That support includes clear roles, access to resources, meaningful growth opportunities, and enough proximity to the work to recognize when someone needs help.
Trust and accountability belong together. Giving someone autonomy while leaving expectations obscure is not the same as enabling independent judgment. I work toward mutually understood scope, milestones, and outcomes, with room for designers to determine how they get there.
This also means staying close to craft. Frameworks cannot substitute for understanding the work. Prototyping, examining design decisions, and talking to customers remain ways of helping teams see possibilities and remove barriers.
Scale Deep is not simply coaching someone to perform better within unchanged conditions. It includes asking whether the people systems themselves make good design work possible.
Scale Wide: Design the Collaboration Systems
Scale Wide concerns the relationships, decision-making practices, and shared ways of working between design and other disciplines.
I’ve found that challenges involving platform development, AI integration, or product strategy rarely belong to one discipline. They combine technical, social, and market considerations. Collaboration becomes difficult when these different ways of understanding a problem meet without clear arrangements for working through them.
I call the useful tension between disciplines “productive friction.” The aim is not to eliminate disagreement. It is to create conditions in which disagreement can improve a decision rather than become a contest over ownership.
In my practice, this has included joint workshops with engineers, collaborative sessions with product managers, and structured exchanges between disciplines. The underlying questions matter more than the format:
- When should different disciplines become involved?
- What information do they need?
- Who can make which decisions?
- How will unresolved disagreements be addressed?
Clear service models also matter. Teams should understand how to engage design, how work is scoped, and what participation requires. Otherwise, a function intended to improve collaboration can become another bottleneck.
Scale Wide makes design practice accessible without requiring designers to mediate every interaction.
Scale Up: Organizations Are Designable Systems
Scale Up concerns the structures, policies, incentives, and strategic arrangements that determine how design participates in organizational decisions.
One of my hardest lessons has been that organizations are designable. Their arrangements are consequential, but they are not immutable. Hiring criteria, planning processes, budget decisions, and definitions of success can all become objects of inquiry and intervention.
This does not mean a design leader has unilateral authority to redesign the organization. It means treating these conditions as open to examination rather than accepting them as a permanent backdrop.
In practice, this requires relationships with other leaders, an understanding of organizational priorities, and patience with resistance. Demonstrating design’s contribution matters, but results still need to be interpreted and connected to decisions. They do not simply speak for themselves.
Scale Up asks how design judgment can become part of governance rather than remaining advice offered during execution.
One problem, different possibilities
Consider a design team struggling with product quality. The visible issue might be inconsistent work, but that description does not yet tell us where to intervene.
Through Scale Deep, I would ask whether designers have the capability, feedback, and clarity they need. Are people able to raise concerns? Do they understand the standard they are working toward? Is someone being held responsible for a decision they cannot actually make?
Through Scale Wide, I would examine the collaboration around the work. Are requirements changing without discussion? Are design and engineering working from different assumptions? Do handoffs conceal decisions that should have been made together?
Through Scale Up, I would examine the conditions surrounding both teams. Does planning reward speed while treating quality as negotiable? Is design involved only after commitments have been made? Are staffing and scope decisions incompatible with the expected outcome?
These are not three competing explanations from which a leader must choose one. Several may be relevant. The purpose is to avoid prescribing training for a coordination problem, adding a process to compensate for an unresolved incentive, or escalating an issue that could be addressed through a direct conversation.
This is the distinction between deciding what to do and developing how to see. The intervention follows from the diagnosis, and the diagnosis remains open to revision.
Five dimensions: what is at stake?
The three modes help a design leader determine where to direct attention and intervention. The five dimensions help assess what is at stake and what an intervention may affect.
- Personal authenticity: whether designers can exercise judgment in ways consistent with their values, responsibilities, and growth.
- Product excellence: the quality, coherence, and usefulness of what reaches people.
- Team dynamics: how people work together, share knowledge, and develop collective capability.
- Strategic alignment: how design decisions connect to objectives and the methods used to pursue them.
- Organizational influence: how design participates in institutional decisions, priorities, and resource allocation.
The dimensions are not additional stages or separate competencies to master. They help make responsibilities and consequences visible across the modes.
Consider introducing a design system through shared standards, documentation, and decision-making between design and engineering. The intervention operates primarily through Scale Wide because it changes how disciplines work together. Its consequences extend further.
Designers must learn the system and exercise judgment about where it supports or constrains their work, raising questions of personal authenticity. Shared components affect product excellence. Decisions about ownership and contribution shape team dynamics. The system’s priorities need strategic alignment, while maintenance, funding, and governance involve organizational influence.
That does not mean every design-system initiative belongs exclusively to Scale Wide. Developing designers’ capability may call for Scale Deep; securing ongoing ownership and resources may require Scale Up. The modes help locate the work that needs attention. The dimensions help examine its implications.
Mapping those implications does not guarantee a positive cascade. A standard intended to improve consistency might constrain useful experimentation. Documentation intended to distribute knowledge might create maintenance work without clear ownership.
I use the dimensions to ask where benefits and burdens fall, not merely to describe how many areas an initiative touches. The point is to make trade-offs more visible before they become someone else’s problem.
Build influence that does not depend on your presence
I use “design currency” to describe the structural influence design has in organizational decision-making, resource allocation, and strategic direction.
Outputs still matter. Product quality, delivery, and customer experience are not distractions from design leadership. But they do not tell us everything about whether an organization is becoming more capable of producing good work.
I also look for changes in how work happens:
- Are designers able to make appropriate decisions without waiting for permission?
- Can cross-functional teams use shared practices without design facilitating every exchange?
- Is design judgment sought before major commitments, rather than after them?
- Do useful practices survive changes in personnel?
- Are resources and responsibilities aligned with the quality the organization expects?
I look at these changes alongside the quality of the work, the team’s experience, and the outcomes for customers. Adoption alone tells me little. I want to understand whether a practice helps people make better decisions, where it creates friction, and what still depends on someone stepping in.
Context matters. Authority, culture, organizational maturity, and available resources affect what is possible. A design leader may recognize an institutional problem without having the power to change it. The approach can help distinguish a local adjustment from a change that requires a coalition.
Small experiments are useful here. A revised critique format, clearer engagement agreement, or different planning conversation can test an assumption. I pay attention not only to the intended result but also to what the change makes easier, harder, or newly visible elsewhere.
Leadership that outlasts the leader
The question I return to is not only “How can I become a better design leader?” It is “How can I build a design organization in which others can exercise judgment and leadership?”
That does not diminish personal responsibility. Someone still needs to make decisions, give difficult feedback, protect standards, and remain close enough to understand the work. But design leadership becomes fragile when those responsibilities depend on one person continually compensating for conditions nobody addresses.
Scalar Leadership directs attention toward those conditions. It asks us to move between developing designers, shaping collaboration, and influencing institutional arrangements while remaining attentive to their consequences.
Building design currency is a long game. Its value is not that everyone begins using design language or that the design function acquires more territory. It is that sound design judgment becomes easier to exercise, useful knowledge becomes accessible, and better decisions no longer require the same person in every room.
That is what I mean when I say design becomes infrastructure, not service.
Selected works
- Meadows, Donella H. Thinking in Systems: A Primer. Edited by Diana Wright. Chelsea Green Publishing, 2008. [web:16]
- Eames, Charles, and Ray Eames. Powers of Ten. Film. Eames Office, 1977. [web:38][web:40]
- Hunt, Jamer. Not to Scale: How the Small Becomes Large, the Large Becomes Unthinkable, and the Unthinkable Becomes Possible. Grand Central Publishing, 2020. [web:36]