Design: The Craft of Deciding What Something is For

Design | The Discipline of Deciding
Credit: The DeepDive | Podcast style overview generated using NotebookLM

Source: @cycnez via Unsplash

Summary || DESIGN · The craft of deciding what something is for

Design is often treated as the polish at the end of the work, or the department you call when something needs to look better. But underneath, design is a discipline of deciding: what something is for, who it serves, what it is answerable to, and what happens after it is built.

That matters when making things is becoming easier than ever. It also raises a more uncomfortable question. What if the way we have learned to design has taught us to think too narrowly about time, place, and who or what counts?

Indigenous design perspectives have made me look differently at some of those assumptions, as a body of knowledge that exposes things my own field can too easily overlook.

  • noun

    1. a plan or drawing produced to show the look and function of something before it is built or made.
      "he unveiled his design for the new museum"
      Similar: plan, blueprint, drawing, sketch, outline, draft, model, prototype

    2. purpose or intention that lies behind an action, fact, or object.
      "the marks of design in the natural world"
      Similar: intention, aim, purpose, plan, objective, goal, end

    verb

    1. decide upon the look and workings of something, especially by making a detailed drawing of it.
      "the students were designing a bridge"
      Similar: plan, draft, draw up, devise, conceive, fashion

7min read

What is this

You can usually feel the difference between something that was designed and something that was only assembled. The first has been decided. Someone worked out what it was for and who it was for, and the parts answer to that. The second accumulated. Features got added, decisions got deferred, and the shape it ended up with is the shape nobody quite chose.

Most work is assembled. Design is the harder discipline. It is a way of deciding.

Tim Brown, one of the people who shaped modern design thinking, described design as sitting at the intersection of what people want, what technology can do, and what a business can sustain: desirable, feasible, viable. Those three words matter less than the discipline behind them. They ask us not to sacrifice one for the others simply because one is easier to satisfy.

Strategy decides things too. So do policy and leadership. What makes design distinctive is that you decide by making. You build something, put it into the real world, see what happens, and change it. The deciding and the building are part of the same act.

But before any of that comes a simpler question.

What will this thing answer to?

Everything we build serves something, whether or not anyone has said so out loud. A system might answer to efficiency. A building might answer to the people who use it. A policy might answer to political priorities. A strategy might answer to growth. The important thing is to know. Because once you know what something is for, many of the harder decisions become easier.

This is also why design is more than styling. Styling asks how something looks. Design starts with what it is for, and lets that shape how it looks and feels. Beauty is part of function, too. People tend to experience well-designed things as easier and more pleasant to use. How something feels is part of what it does.

And good design rarely starts from nothing. Much of the craft is noticing what already works somewhere else and understanding whether it can be meaningfully carried across. The interesting question is what is worth making.

Why this matters

We are becoming extraordinarily good at making things. Technology has made it cheaper to create, test and reproduce ideas. AI is accelerating that again. Something that once required weeks of effort can now be produced in minutes.

That sounds like a reason to celebrate creativity. I think it is also a reason to worry about judgement.

When making was difficult and expensive, effort provided a natural filter. If something took months to build, you thought twice before building it. Now we can generate almost anything. The brake has moved. The scarce thing, increasingly, is the ability to decide what deserves to be made.

That is one reason design matters. It gives us a discipline for making choices when we do not yet know the answer. A plan becomes a first draft. An idea becomes something you can put in front of people. A problem becomes something you are allowed to question before you rush to solve it.

This is also where design thinking has earned some of its criticism. A discipline that was meant to help us challenge assumptions can itself become a formula. A workshop, some sticky notes, a Double Diamond, a sprint, and everyone goes home feeling that something has happened. Sometimes it has. Sometimes the method becomes a way of avoiding the harder work.

The hardest problems in organisations are rarely neat. They involve competing interests, history, power, relationships and consequences that extend well beyond the people in the room. No two-week process can make those things disappear. Good design does not remove complexity. It helps us decide what we are prepared to be answerable to within it.

WHAT INDIGENOUS DESIGN OPENS UP

This is where my thinking about design became more interesting. I have been reading about Indigenous design, particularly the Te Aranga Māori Design Principles in Aotearoa, New Zealand and the work of Indigenous architects such as Jefa Greenaway in Australia. I come to this from outside these knowledge systems. I am not trained in them, and I have no standing to interpret them.

So I am not trying to extract a set of Indigenous principles and turn them into another business framework. Quite the opposite. What interests me is what they make visible about the assumptions underneath the way I already think about design.

The first is time.

Most organisational work has a very particular clock. A project starts at kickoff, reaches its milestones, goes live, and eventually closes. We behave as though the work is finished when the thing ships.

Te Aranga brings a different sense of time into view. Whakapapa connects the present to what came before, while principles such as ahi kā speak to an enduring presence that continues to be tended. That changes the question. Alongside “when will this be finished?”, we might ask:

What did this inherit, and what will it leave behind?

Hold that against an operating model, a city, a building or a major change programme and the definition of good design starts to shift.

The second is place.

In much of organisational design, context is something we assess. We understand the environment, identify the constraints, and then design around them. Indigenous design thinking asks us to see place differently. A place is more than an empty backdrop for the project. It has history, relationships, stories and obligations that existed before we arrived. Te Aranga makes this explicit through principles concerned with whakapapa, whenua, taiao and the wider cultural landscape.

The blank canvas was always a convenient fiction.

This is surprisingly relevant to organisational change. We often arrive with a new strategy, a new operating model or a new structure as though the story begins with us. It does not. The organisation already has a history. People already have relationships. There are ways of working that make sense because of what happened before. Good design has to understand the ground it is working on.

The third is who or what counts.

Human-centred design was an important correction to designing around the needs of institutions rather than people. But it still leaves us with a particular question:

Who is the human at the centre?

Indigenous design perspectives widen that circle. The health of land and water can become part of what a design is answerable to. So can community, cultural continuity, future generations and the relationships that hold a place together. It is a different idea of accountability, wider than a stakeholder map.

The question widens, from:

Who uses this?

to:

Who and what is affected by this, whether or not they are in the room?

That is a much harder question.

The fourth is the journey.

Much of professional work is organised around the artefact at the end: the strategy, the building, the policy, the operating model. But Indigenous design thinking places real weight on how something comes into being, including relationships, authority, listening and shared authorship.

That resonates with something I already know from leading change. How a change is done affects whether it lasts. But I have tended to think of that as a means to an end. The relationship-building helps us get to a better outcome. What I am beginning to see is that the relationship can itself be part of the outcome.

And here is the trap.

The temptation, especially for someone working in business, is to take these observations and turn them into four portable principles: think longer, understand place, widen the stakeholder group, co-design. Put them into the next workshop. But that would miss the point.

These ideas belong to particular knowledge systems, histories, places and relationships. Te Aranga is not a universal design methodology waiting to be imported into a corporate toolkit. What they offer someone like me is a disturbance. They make some of my own assumptions harder to ignore.

How it shows up

So what does a design stance actually look like in ordinary work? Probably less like a methodology than we imagine.

It shows up first in the problem you agree to solve.

Most of us take the problem we are handed and get to work. The design move is to pause. Is this actually the problem? Sometimes it is, and the work is simply to solve it exceptionally well. Often it is the first, rough version of a harder question. A confident answer to the wrong question is worse than no answer at all, because it looks like progress.

It shows up in what you are willing to put in front of people before it is ready.

A one-page version of a strategy. A meeting format tried once. A policy tested with ten people. A rough prototype of a service. The point is to learn while the cost of being wrong is still low.

It shows up in who holds the pen.

Consultation asks people to respond to something that has already been designed. Co-design gives people a hand in shaping what emerges. That distinction matters, because the person who sees what is wrong is often the person closest to the work and furthest from the decision. If they are only invited to comment at the end, we may have designed out the thing we most needed to know.

And it shows up in what happens after launch.

This may be the hardest part. We tend to treat implementation as the point at which design becomes reality. After that, the project is finished and operations take over. But if design is really about what something is answerable to, then the obligation does not disappear when the project does.

The thing changes. The context changes. The people affected by it change. Sometimes the original design was wrong. Sometimes it was right for its time and has simply become wrong now. A design stance means being willing to notice that, and change the thing.

Where to look first

You do not need to run a design workshop to bring more design into your work. Start with something you are already building or changing. Ask:

What is this for?

Can you answer in one sentence?

What is it answerable to?

Who decided that?

What existed before us?

What history, relationships or assumptions are already shaping the ground we are working on?

Who or what is missing from the room?

Whose interests, and whose consequences, are not represented at all, even by someone speaking on their behalf?

What could we put in front of real people now?

Not when it is finished. Now.

What will happen after we leave?

Who will live with this decision when the project team has moved on?

These are not a scorecard. They are questions designed to make the invisible parts of a decision visible.

You won't need all of them. Match the aim to the spine, draft into it, then get out of its way. Reaching for a familiar shape out of habit is how a talk sags. The tool's full library holds more of these; this is the working set.

Closing reflection

I started thinking about design as a way of making better things. I think I am now more interested in it as a way of making better decisions about what we choose to make. That distinction matters. Because the more capable we become at making things, the less we can rely on effort, cost or difficulty to tell us what deserves our attention. We have to decide.

And perhaps the deeper lesson from the Indigenous design thinking I have been reading is a reminder that our usual definition of the design problem may be too small. We might think the question is:

What should we build?

But there are harder questions underneath it. What are we building on? What did it inherit? Who is it for? Who else will live with the consequences? What does the process create along the way? And what will it still owe when we are gone?

Design cannot be installed any more than craft can. It lives in a long run of small decisions about what something is for, what it is answerable to, and whether we are still prepared to stand behind those decisions once the excitement of building has worn off.

That applies to organisations. It applies to cities and communities. And, perhaps, it applies to a life. We are all designing something, whether deliberately or by accumulation. The question is whether we are choosing its shape, or simply discovering it after the fact.


.  .  .


Researched and written by Rebecca Agent, with credit to AI tools for assistance in producing this content:

references

See related pieces (on the blog) :


If this content was helpful to you and your work please comment, share, and like !

Bespoke Delivery, Strategic InnovationRebecca AgentComment