We bring our expertise. You bring a world we have not lived in.
The people you serve bring another. So do the people answering their questions, delivering the service, building the technology, or making the idea possible in a physical space.
Co-Creation brings that knowledge into the design itself. It is a way of working with clients, people affected by an experience, and specialist partners so their contributions can help shape what we understand, imagine, make, and improve.
At Abstraction, collaboration is not a courtesy we extend after the important decisions have been made. We want to be open to what other people can change about the work.
You do not need to speak like a designer for your experience to matter to the design.
More than asking what people think
There is a difference between asking someone to react to a finished proposal and inviting them to help develop the response.
Both can be useful, but they are not the same kind of participation. Co-Creation makes room for people to contribute before every possibility has been resolved. They might help frame the challenge, map an experience, imagine a different interaction, change a prototype, or examine what an early version has taught us.
IDEO.org's Co-Creation Session method describes this shift from hearing people's views to inviting them to make alongside the design team. Our application extends beyond a particular session: it is part of how we want the working relationship to feel and function over time.
Listening becomes meaningful when what we hear has a chance to affect what we do.
That does not mean every suggestion becomes a feature. It means the contribution is examined, connected to the wider situation, and treated with enough respect to explain what happens next.
Different knowledge belongs in the work
A client may understand the history behind a decision that looks puzzling from outside. An employee may know where a process repeatedly asks for extra effort. A customer may show us that a reassuring message does not answer the question they actually have.
A developer may see a more useful way to connect systems. A photographer, fabricator, writer, or sound designer may introduce a possibility we would not have reached alone.
Those contributions are not interchangeable. Lived experience, operational knowledge, research evidence, creative judgment, and technical expertise have different roles. We want to understand what each can tell us without pretending one person speaks for everyone else.
In particular, client and employee knowledge does not automatically represent the end user. Where we need to learn from the people experiencing a product or service, we should involve them appropriately rather than fill the gap with confidence.
Empathy asks us to take another person's circumstances seriously. Co-Creation gives that person a way to participate in what those circumstances might become.
You should not have to do our job to be involved
We encourage clients to contribute because their experiences can improve the work and because participating can deepen their own understanding. That invitation should not become a demand that they arrive with the solution already designed.
Bring the difficulty you keep encountering. Show us the workaround. Tell us what you want people to feel, what has failed before, or what you have been hoping someone could help you make possible.
We can help turn those contributions into something the team can examine: a clearer question, a sketch, a journey, a set of alternatives, a prototype, or a proposed decision.
Participation can take different forms and levels of involvement. Some clients want to work closely throughout. Others need us to carry more of the task and make purposeful use of their limited time. Some people contribute most effectively through an example or a written response rather than a group conversation.
The relationship should make room for that. Our job is to design useful ways to work together, not to judge commitment by attendance at every meeting.
Shared creation still needs judgment
Co-Creation is not design by unanimous vote.
An idea can be sincerely offered and still conflict with another need, introduce an unacceptable risk, or fall outside what the project can responsibly accomplish. We should be able to explore that without treating the person behind the idea as the problem.
Abstraction remains responsible for synthesis, creative judgment, and the recommendations we make. Clients retain their business decisions and agreed approval responsibilities. Specialist partners bring professional responsibilities of their own.
We clarify those roles instead of using “we all agreed” as a substitute for an accountable decision.
When contributions pull in different directions, we can examine the underlying needs, make alternatives tangible, and ask what evidence would help. Sometimes the right outcome is a test. Sometimes it is a tradeoff the client understands. Sometimes it is recognizing that the original question needs to change.
Design Facilitation helps guide that work. Stakeholder Workshops offer one format for doing it together. Co-Creation is the broader commitment that people's participation can meaningfully influence the result.
A bookshop becoming a place to gather
When a neighborhood bookshop wants to introduce readings and evening events, we explore how the website, event materials and physical shop can support the same welcome.
The request may begin with an events page and signage. Through Co-Creation, we help the people behind the shop shape the larger encounter those pieces will belong to.
The owner might describe the atmosphere they want to preserve. Staff could walk through preparation, arrival, book sales, and the questions they expect to answer. Invited readers and prospective visitors could help explore what makes attending feel welcoming—or uncertain.
Rather than only ask everyone to approve a design, we could work with a rough event journey. Participants might rewrite an invitation in their own words, mark information they would look for, arrange possible arrival steps, or respond to a simple prototype.
That shared material gives the team something specific to learn from.
| A possible contribution | How it could shape the work |
|---|---|
| The owner wants gatherings to feel like an extension of the shop, not a separate promotional brand | Connect the visual language, tone, and experience across the website and space |
| A prospective visitor wonders whether arriving alone will feel awkward | Explore content and welcome moments that address the uncertainty without making assumptions about everyone |
| Staff identify a conflict between event check-in and ordinary purchases | Examine the arrival sequence, information, and responsibilities before designing the sign or screen |
| A production partner identifies a more flexible way to update event signage | Develop an expression that can adapt without losing its character |
| A developer identifies information that can be maintained in one place | Explore how the website, confirmations, and staff material can stay consistent |
The designer's role is not to combine every suggestion literally. It is to understand the needs beneath them and compose an experience in which the parts support one another.
That might affect Content Design, the event-registration interface, printed material, spatial cues, staff preparation, or all of them. Customer Experience Design helps keep the relationship intact across those touchpoints.
We carry what emerges into design and evaluation in the actual setting, returning to the people involved as the idea takes shape. Participation gives the work more to draw on; it also helps us notice when an assumption needs to change.
Partners can help shape the idea—not only execute it
We value specialists for more than production capacity.
A collaborator's understanding of material, technology, sound, movement, craft, or a particular audience can change the direction of a project. Bringing that perspective into the work at a useful moment can help us explore possibilities and constraints together.
Sometimes Abstraction leads. Sometimes we join a team already taking shape. Sometimes a specialist brings us a need for design, development, or a wider creative perspective. We want those relationships to feel reciprocal, with room for each contributor's judgment.
That openness does not remove the need for a clear brief, scope, responsibilities, or decisions. It makes those agreements more useful because the team understands how its contributions connect.
We are comfortable sharing the creative conversation. The result should benefit from the people involved, not be limited by a need to make one company appear to have done everything alone.
Make the contribution visible
People should be able to understand how their involvement affected the work.
That may mean showing the question a conversation helped us uncover, the alternative an employee's knowledge made possible, or the reason a suggestion was not taken forward. It may mean returning with a prototype that incorporates what someone helped us understand and asking what we still have wrong.
We do not want participation to end with “Thanks for your feedback” and no visible connection to the next decision.
The working record can capture contributions, observations, ideas, decisions, rationale, and unresolved questions. We consider how people should be acknowledged and what is appropriate to share. A contribution made in confidence should not automatically become public case-study material.
Likewise, co-creating something does not settle ownership or reuse rights by itself. Those expectations belong in the relevant agreements. The principle is to respect contribution, not to make assumptions about whose work, information, or intellectual property is available for another purpose.
Grow the understanding together
The value of participation can continue after the initial work is delivered.
A client who has helped examine the problem, compare alternatives, and interpret evidence can bring a more informed idea into the next conversation. They can connect what they want to change with what it could do for people and the business.
We want that confidence to grow. The value of our relationship should not depend on keeping the reasoning inaccessible.
Product Intelligence is part of that: knowledge built with the client, retained, and applied over time. Reports and deliverables preserve the record. Active involvement provides another kind of learning—the experience of asking, exploring, deciding, and seeing what follows.
Our Design Thinking loop remains:
Discover → Define → Explore → Design / Develop / Market → Learn → Advance → Discover.
New information can change the next question. A client's observation, a customer's difficulty, or a partner's idea can give the work a different direction. Continuous Improvement keeps that possibility open while the next effort is shaped around an agreed need and scope.
An invitation to work with us
Co-Creation is not an extra package we ask clients to buy. It describes how we want to approach the relationship.
Whether you are bringing a business challenge, a product, a particular skill, or an idea that needs other people to become real, we are interested in what we could make together.
We will bring our perspective. We want yours to matter too.
Return to the Gallery
Encounter A Shared Form in the Gallery