Blogs / Six Contexts of Design Practice

Design · 5 Min Read

Six Contexts of Design Practice

How designers recognize what a situation requires, move between roles, and remain responsible for what their work changes.

Design work rarely unfolds in the order a process diagram promises. A prototype raises a question that changes the research. Research exposes a disagreement about what the organization should be doing. An intervention encounters conditions that require the team to reconsider both its approach and its understanding of the problem.

These movements are not necessarily departures from good practice. They are often the work itself.

Over approximately a decade of professional design practice and six years of teaching, I’ve become interested in how designers recognize these changes and respond to them. Working across roles and organizational environments, and observing how students approach design problems, has led me to distinguish six contexts of practice: strategy, team, research, intervention, prototyping, and transition.

Each context demands particular forms of attention. Each brings different responsibilities into view.

The designer’s expertise lies not simply in possessing methods, but in recognizing what a situation requires and knowing how to respond.

Sometimes that means choosing another tool. Sometimes it means reconsidering the problem, involving someone with different expertise, or recognizing that the responsibility you now carry is not the one you expected.

Contexts, not a prescribed sequence

A context describes the conditions and demands of the work. A role describes how a designer shows up within those conditions. That role is not always freely chosen: expectations and relationships may impose a responsibility, make it a matter of negotiation, or reveal it gradually.

I use five role names across these six contexts: the Design Strategist, the Embedded Ally, the Design Journalist, the Design Choreographer, and the Design Scientist. The Scientist appears in both prototyping and transition because experimental inquiry matters both when testing an idea and when learning from its consequences over time.

These are not permanent identities, job titles, or fixed specializations. A designer may inhabit several at once, revisit them, or find that some are more relevant to their responsibilities than others. They are neither a career ladder nor a claim that every designer should practice equally across all six contexts.

They are a way to examine what the work is asking of us.

This distinction matters because a universal process can make the sequence appear more authoritative than the situation. When the method determines what deserves attention, rather than helping us investigate it, professional judgment has been displaced by compliance.

A working toolkit offers a different relationship to methods. It becomes a vocabulary: something we draw on, combine, question, and develop through practice. The responsibility is not to use every tool, but to understand what a tool helps us see and what it may leave out.

Six contexts in practice

Strategy Context: The Design Strategist

The strategist asks: What should we be addressing, and why does it matter?

Strategy is not simply planning a solution at a larger scale. It involves examining the arrangements within which design will operate: priorities, resources, incentives, relationships, and the distribution of power.

What does the organization consider valuable? Who benefits from the current arrangement? What would an intervention preserve, challenge, or make possible?

Systems mapping, long-term visioning, stakeholder analysis, and organizational goals can help make these relationships discussable. But completing a map or setting an objective does not settle the strategic question. The designer still has to judge whether the work deserves attention and whose account of the problem is guiding that judgment.

Strategy also requires recognizing that an organizational priority and a community priority may not be the same. A mandate to improve a service does not automatically authorize the designer to decide what improvement means for everyone affected.

The strategist establishes direction, but that direction remains open to what research, collaboration, and implementation reveal.

Team Context: The Embedded Ally

The Embedded Ally asks: Who needs to be involved, and what conditions will allow us to work honestly together?

Collective work depends on more than gathering people in a workshop. It requires relationships in which people can question assumptions, disclose uncertainty, disagree, and contribute without having their knowledge dismissed.

I think of this as team intimacy and cohesion: enough trust to undertake difficult work together, not an expectation that everyone will agree.

Working agreements, retrospectives, peer mentoring, and deliberate attention to participation can support that trust. Their value depends on how people use them. A retrospective that cannot acknowledge a consequential disagreement is unlikely to change the conditions producing it.

The Embedded Ally also pays attention to authority. Who can challenge the brief? Who is expected to accommodate decisions already made? Whose contribution is treated as expertise, and whose is treated as feedback?

This responsibility can remain active while the designer is researching, setting direction, or testing an intervention. It is not a preliminary team-building exercise that must be completed before the real work begins.

Research Context: The Design Journalist

The Design Journalist asks: What do we need to understand, and how will we learn it?

Research is not a step in the process. It is a posture: a willingness to attend to what is happening without forcing it too quickly into familiar categories.

Interviews, contextual inquiry, studying precedents, and systems mapping can help develop that understanding. Making can also become inquiry. A sketch or prototype may expose a question that conversation alone has not made visible.

The important distinction is between gathering material and developing an understanding that can withstand scrutiny. An interview does not automatically establish a need. A compelling observation does not explain its own causes. The designer must examine interpretations, competing explanations, and the limits of what has been learned.

The Design Journalist remains attentive to whose account is missing. Research should not become a way to collect support for an intention that is no longer open to revision.

This context overlaps with every other one. Strategic assumptions need investigation. Team tensions may require listening rather than another exercise. An implemented design can reveal conditions that were not visible beforehand.

Intervention Context: The Design Choreographer

The Design Choreographer asks: Where and how might we intervene meaningfully?

An intervention is not always a new product or a direct solution. It may involve changing a relationship, a working arrangement, an incentive, or a condition that prevents something else from happening.

The choreographer considers how actions interact. A promising idea may depend on decisions elsewhere in the organization. A service change may shift work onto people who were not involved in defining it. An apparently small adjustment may matter because of where it sits within a larger arrangement.

A theory of change can make assumptions about actions and outcomes explicit. Participatory approaches can help those affected shape the intervention. Speculative work can open alternatives before a team commits to one direction. None removes the need to judge whether the proposed change is appropriate.

Strategic patience matters here. Acting immediately is not always the most responsible way to act. Sometimes the work is to build agreement, develop understanding, or change the conditions that make an intervention possible.

The strategist asks what deserves attention. The choreographer concentrates on how change might happen. In practice, each question can reopen the other.

Prototyping Context: The Design Scientist

The Design Scientist asks: What do we need to learn, and what can we make to investigate it?

Prototyping tests understanding rather than “finishedness.”

A paper sketch, a clickable interface, or a trial workflow can each be useful if it addresses a consequential question. The point is not to produce the most polished representation possible. It is to make an uncertainty available for examination.

Stephanie Houde and Charles Hill offer a useful distinction between prototypes that investigate an artifact’s role in someone’s life, its look and feel, and its implementation. These are different questions, not a required progression from rough to complete. A prototype can explore one or several dimensions, provided its purpose and limits are clear. [web:24]

The Scientist’s responsibility includes explaining what the prototype does not establish. A convincing demonstration may leave technical feasibility unresolved. A working implementation may tell us little about whether the proposed intervention is desirable.

Prototyping overlaps with research because making can generate understanding. It overlaps with teamwork because different collaborators may interpret the same prototype differently. The experiment is only as useful as the question, the participation, and the interpretation around it.

Transition Context: The Design Scientist

In the transition context, the question changes: What is happening as this intervention becomes part of everyday life, and what must we do in response?

Here, the Design Scientist’s attention extends beyond a bounded prototype toward implementation, consequences, and continuing adaptation. The role name remains the same, but the responsibility changes with the context.

Delivery does not settle whether an intervention is working. People adapt it, resist it, depend on it, or find uses the team did not anticipate. Organizational conditions change. Benefits and burdens may become visible at different times and to different people.

Outcome measures, follow-up inquiry, feedback from affected people, and revisiting the assumptions behind an intervention can help guide that work. Measurement should not be limited to proving that the original intention was achieved. It should leave room to discover that the intention itself needs reconsideration.

Not every designer controls what happens after launch. Responsibilities may be distributed across teams, institutions, and communities. That makes it important to establish who can recognize problems, who can act on them, and how learning will reach those with the authority to make changes.

Transition is not simply the last context. Consequences can reopen strategy, research, collaboration, and intervention.

How the work changes the role

Movement between contexts is not always a conscious choice.

A designer may intentionally take a strategic role because the team is solving the wrong problem. They may adopt an investigative posture because an assumption needs testing, or concentrate on relationships because collaboration has become difficult.

At other times, circumstances have already changed the role before the designer recognizes it.

Stakeholder expectations may place a designer in a coordinating position. Community priorities may require them to listen rather than propose. Institutional responsibilities may constrain what they can change. An unexpected material limitation may turn a proposed intervention into a research question.

Designers shape the conditions of their practice, while those conditions also shape how designers show up.”

Roles can be chosen, negotiated, imposed, or gradually recognized. Contextual judgment therefore involves more than selecting a mode of practice. It requires reflection and attunement: noticing what has changed, how relationships are affecting the work, and whether the responsibilities we have assumed remain appropriate.

Consider a prototype test that reveals a problem with the underlying service rather than the interface. Improving the prototype may no longer be the most consequential task. The work might now require organizational decisions, further inquiry, or expertise that was not previously involved.

Or consider an implemented intervention whose outcomes look acceptable in aggregate but whose burdens fall unevenly. The responsibility is no longer simply to measure performance. It may be to question the measure, revisit the intended outcome, and involve those experiencing the burden.

These are not additional phases to insert into a process. They are reasons to reconsider what kind of work is needed.

Working across expertise and intention

Moving between contexts can also mean working across disciplinary boundaries. But methodological versatility does not confer specialist expertise.

Knowing how to facilitate a discussion does not mean knowing enough to settle an engineering, ecological, financial, or public-health question. The designer’s contribution may be to make relationships visible, help different accounts of the problem meet, and recognize where another form of knowledge must change the direction of the work.

This is one way the six contexts can support transdisciplinary practice. They encourage attention to responsibilities that cross established job descriptions without suggesting that the designer should absorb every discipline into their own.

I’m also beginning to consider altitude, depth, and range as language for describing movement between contexts. Altitude concerns changing the level or scale of inquiry and intervention. Depth concerns developing sufficient understanding of underlying conditions. Range concerns navigating across contexts, responsibilities, methods, and disciplinary fields. A change in the work may ask us to shift scale, investigate further, or involve knowledge beyond our own.

These are emerging reflections, not additional roles or a formal model. Neither a broader view nor greater range is automatically better. Sometimes the responsible move is to stay with a particular interaction, material constraint, or unresolved relationship until it is properly understood.

Nor does the designer’s intention automatically deserve priority. Contextual judgment includes asking whose priorities define the problem, who has authority to determine desirable outcomes, and whether our preferred intervention conflicts with the needs of those who will live with it.

Sometimes the appropriate contribution is to propose. Sometimes it is to facilitate, collaborate, reconsider, or step back.

Useful structure is not methodological prescription

There are legitimate reasons to establish shared ways of working. Students need structures through which to learn. Teams need coordination. Organizations need accountability, and people affected by design deserve more than an appeal to improvisation.

The distinction is not between structure and freedom. It is between structures that support judgment and prescriptions that replace it.

Across practice and teaching, I’ve come to value structure for the judgment it helps people develop, not for the consistency with which it can make them repeat a sequence.

A team can agree on how decisions are recorded, how evidence is challenged, and who must participate without insisting that every problem follow the same sequence. A designer can depart from a preferred method while remaining responsible for explaining why, what was learned, and what uncertainty remains.

Contextual practice is not permission to avoid rigor. It asks more of the designer: to select, adapt, combine, or abandon methods for reasons that others can examine.

The toolkit matters. So does the judgment governing its use.

Responsibility beyond delivery

Designers are in the consequences business, whether we acknowledge it or not.

What we make enters arrangements that already exist. It changes possibilities, distributes effort, and affects what other people can do. Responsibility therefore extends beyond the quality of the artifact to the conditions it reinforces and the consequences it helps produce.

The six contexts are useful if they help us recognize that responsibility more clearly. They are less useful if they become another checklist through which we certify that design has happened.

As AI becomes part of more design work, I’m interested in what it will change about these responsibilities. How might it alter the roles designers assume, the expertise they need around them, and the relationships through which judgments are made? If more activities can be delegated or accelerated, how will we decide what deserves doing, whose intentions should guide it, and how its consequences will be understood?

Design expertise is tested when the situation no longer fits the method we know.

The responsibility then is to notice the mismatch, reconsider how we are showing up, and work with others to determine what the changed conditions require. A familiar method may still serve us. It cannot make that judgment on our behalf.

Selected reference

Houde, Stephanie, and Charles Hill. 1997. “What Do Prototypes Prototype?” In Handbook of Human-Computer Interaction, second edition, edited by M. Helander, T. Landauer, and P. Prabhu. Amsterdam: Elsevier Science B.V. [web:24]