A customer co-creates a service: more commitment than a conversation about ideas
Define a customer co-creation cycle, mutual contributions and limits before developing a service together.
Article language: English

In this article
A customer says, “We'd be happy to help you develop it.” That is good news, but not yet an agreement to collaborate. They may mean one conversation, sharing an example or involving their team in later trials. A provider may hear a promise of regular testing while the customer means a polite willingness to comment. The difference often emerges when someone tries to schedule a third meeting.
A customer co-creating a service, sometimes called a design partner, participates in work on a solution that is still changing. They bring a specific context and return to later versions. For the relationship to make sense, name both sides' contributions, limits on use of material and decisions that remain with the provider. An attractive name alone does not provide time or access to real work.
What unknown should the customer help investigate?
In a fictional example, a studio is developing a service for preparing and updating catalogues for small manufacturers. It currently delivers individual projects. It now wants to examine how a recipient communicates changes, assesses a version and recognises readiness to publish. The invited customer regularly changes product variants and can show that process. Their role is not merely to say whether they like a new package.
Formulate the unknown before inviting someone. “We want to understand how you distinguish an approved change from a proposal” lets the customer assess whether they can help. “We are building the future of catalogues and looking for partners” still needs translation. A person should know which task their team will contribute to and why their particular experience is needed.
In Urban and von Hippel's work on lead-user analysis, users with needs ahead of the market also bring knowledge of their own solutions. The authors describe separately testing concepts with more typical recipients. Our co-creating customer does not automatically become such a user. The useful distinction is that an idea developed around one particular need requires further assessment outside that context.
This is broader participation than the advisory voice of a customer council (in Polish). A council can describe experiences and comment on direction. A co-creating partner should undertake a defined task with the evolving solution, show an obstacle and return after a change. If both sides have time only for a conversation, name the relationship according to that scope.
Do not require the customer to design the new service alone. They may explain their own task well without knowing other recipients' possibilities or the provider's resources. Their proposal is important material, not a ready-made instruction for the whole company. Ask why and in what situation the idea would help before entering it into the work scope.
Choose a participant based on access to the necessary experience. A director may approve participation, while someone else updates the catalogue. If collaboration is to cover team work, plan for the practitioner's presence and permission to spend time. The purchaser's signature alone does not create an opportunity to observe the daily task.
What do both sides actually undertake to do?
Describe a cycle in ordinary actions. The customer shows a suitably prepared case, the studio develops a version, a user performs the agreed task and both sides discuss the result. Indicate the expected effort and an end point. This is not a rigid schedule for every minute, but distinguishes real participation from unlimited availability “if needed”.
Establish what the customer receives during and after collaboration. Do they use working material for assessment? Do they also buy a defined result for their business? Which elements may still be changed or withdrawn? Commercial terms and rights need their own agreements. Do not replace them with a general statement that both sides “benefit from innovation”.
The provider should have capacity to respond to observations. If the customer's team completes a trial but the company has no time to read the results and prepare the next move, the relationship stops at collecting comments. Plan time for those responsible for analysis and decisions. Lack of room for a change is not the same as lack of value in the customer's information.
Research by Storey and Larbig, as described in its available abstract, concerns the relationship between customer participation, absorption of their knowledge and change in a service concept. The authors also point to resources enabling adaptation. We do not derive a guarantee of successful co-creation. Inviting a customer does not replace the company's work on what it heard.
Define in advance what happens to confidential information. In the example the studio may need a way to describe a variant, not the manufacturer's entire customer list. Prepare limited material and check whether it is enough for the task. If not, name the specific gap and agree appropriate access. Do not start with the full archive just in case.
Also agree a way to stop participation. The customer may change priorities or lose the ability to share the task. The provider may decide the concept lacks sufficient basis. In either case the parties need to know what happens to working materials and team expectations. Co-creation should not create an obligation to be polite indefinitely.
How can a trial avoid scripting the answer?
Choose a real task within the agreed scope. For example, the customer communicates a change to one variant and checks whether its meaning is preserved in the new catalogue version. Do not prompt every next move if the future service will not include that help. Record where explanation was needed and who gave it.
GOV.UK's guide to user research in beta covers the whole developing service, including support and offline steps. These are public-service guidelines, not a mandatory business procedure. For our catalogue, a similar perspective prevents assessment of the form alone when the central difficulty may appear only when approving the material.

Keep the solution version and the trial question. If you change the communication method, layout and support scope at once, it is hard later to identify what affected the observation. Several changes may be made, but describe them honestly. Do not credit the whole result to a new button if a specialist manually guided the user through the same trial.
A business-experiment hypothesis card (in Polish) can help. Co-creation may involve several such questions, but each should be recognisable. Can the customer identify an approved change? Is the material sufficient to assess the version? Do they know what needs another consultation? Overall satisfaction does not automatically answer these three questions.
Ask what happened before collecting ideas for improvements. “What did you do after receiving the version?” reveals the work. “Which feature is missing?” immediately moves the conversation to a solution. A participant may propose a new screen when clearer status information would suffice. The company must identify the need, not implement every suggestion without assessment.
After a change, return to a similar task and observe what happens. Distinguish the new experience from memory of the previous trial. Someone familiar with the project may bypass an ambiguity a new customer still does not understand. Later, test entry by someone outside the shared history too. A trusted relationship gives depth of experience but does not replace that perspective.
Which customer wish should change the service?
Give every material comment a next step. It may change the shared concept, require separate checking or remain an individual need outside the developing scope. Explain the reason as far as appropriate. Do not promise to fulfil every request as the price of maintaining a good atmosphere. Co-creation would then become a custom order with growing scope.
In the example, the customer wants the studio also to update its internal price list. That may be a valuable problem, but it does not automatically follow from a catalogue service. The company should establish whether a similar need concerns the intended recipient and whether it wants to handle it. “Since you already know the products” is not sufficient justification for a new responsibility.
Also record occasions when the customer used the solution differently from expected. They may have passed working material to several departments and discovered missing version labels. This need not mean user error or an application the company should immediately include. First reconstruct the purpose of the action and assess whether it fits the service boundaries.
Do not confuse participation in development with a commercial recommendation. A reference conversation with a supplier's customer (in Polish) has a separate purpose. Consent to a trial is not consent to public use of a company name, statement or result. A co-creator should be able to say something does not work without fearing that the remark will later appear on a sales slide after careful shortening.
If knowledge comes from a customer forum (in Polish), distinguish a public idea from agreed participation in later trials. An active person may only want to help others. Do not assign regular work to them because they previously gave several good answers. An invitation to co-create requires a clear description of the greater contribution.
When the customer's participant changes, return to the collaboration goal. The new person may perform another task and not know the reasons for earlier decisions. Give them a brief history of the question, tested versions and unknowns, not just files. Do not assume an earlier manager's approval gives the new person time and access on identical terms.
A cycle note can retain four things: observation from the task, its interpretation, the decision on a change and the question for the next trial. If a change was deferred, name the missing basis or resource constraint. The customer need not receive all internal documentation, but should understand what happened to their contribution. This lets them assess whether further participation still makes sense for them.
Do not prolong the stage only because the relationship works well. If new conversations no longer answer the development question, move to ordinary cooperation or end the trial. Continued contact can be valuable under another model. It should have an appropriate name and scope rather than keeping a testing commitment alive indefinitely.
How can the stage end without claiming the whole market is ready?
At the end, gather what was actually done, which changes resulted and which questions remain open. The solution may serve the co-creating customer well while still requiring checks with other recipients. Do not announce validated demand based on one company's willingness to collaborate intensively. Record the special conditions that made its participation possible.
If the customer will continue to use the result, agree on first use after formal acceptance (in Polish) and the later support route. Development trials with close participation by the author do not always match everyday service. State what changes after the stage ends and what support remains in scope.
With Aeneia Design, the team can discuss translating approved findings into website structure, option descriptions and a digital task flow. The detailed scope needs agreement. Start with documented needs and company scope decisions. A website design does not replace management of the whole service-development process.
Good collaboration leaves more than a wish list and a series of pleasant meetings. It allows a specific change, its basis and the limit of the conclusion to be identified. The customer spent time and showed the team's real work. The company should be able to say what it learned about the service, even when not every suggestion entered the final scope.







