 and you have too much co-creation. That was a question that I got from Katrina some time ago and I think the answer, the short answer is definitely. Absolutely, you can have too much co-creation but it's all about how and when you use co-creation. So I think there is a big misconception that in a lot of service design, design thinking, projects, co-creation or involving users, employees, customers in the process is always a good thing. The more co-creation the better. The truth is co-creation can ruin your project. It can lead to disaster when you involve people at the wrong time in your process and for the wrong reasons. Now I think the best application of co-creation is where you invite people to, where you use co-creation as a research tool. So let me give you an example. For instance, you're redesigning a hospital. Well, it would be smart to involve staff and patients in the design process but not to let them pick out a new floor plan or let them decide which floor plan is the best. Like you would use Lego to design some floor plans and then you would say, well, which one works the best and then we're going to use that. That's terrible. That's a recipe for disaster. What you need to do instead is use Lego. For instance, use drawings, involve staff and patients to imagine their ideal hospital experience. And then you, as an expert, as a designer, should be able to digest insights out of that, patterns. So what are the underlying things people are saying? What are the needs and desires that they are expressing? And then you take those needs and desires and make them into a good plan, make them into a good floor plan because that's your job or it's the job of an architect maybe to actually use those insights and translate them in a floor plan. But don't ask customers, users, employees in your co-creation process to come up with answers. Don't ask for opinions. That's, again, a recipe for disaster use, co-creation for research. Also, in prototyping, co-creation is great. In prototyping, of course, you're going to prototype with the people who will be using your service. But don't ask them to say if this is right or wrong. Ask them, what do you like about this? How does it make you feel, stuff like that? And then take the insights out of that. Look for patterns. So getting back to the question of Katrina, can you have too much co-creation? You can have too much of anything if you use it the wrong way. And I'm a big fan of co-creation if used correctly. I've seen co-creation gone bad and ruined complete projects. So be careful, it's a powerful tool, but know how to use it. What's your take on co-creation? When should you use it? When shouldn't you use it? What are the limits? What are some of the best practices? Leave a comment down below and I'll see you in the next video. Bye-bye.