Yeah – I agree. Collaboration is key. Client input can sometimes seem like a hinderance but it’s always gonna be part of the design process. I do think as designers we need to stick up for our beliefs but I think we need to communicate the reasons behind them so that we provide the client with all the facts. If they then choose to ignore them then thats fine. We tried.
I agree with Lasse’s comment, that it’s potentially a recipe for disaster—herding cats. But I think you give us an adequate structure for these seemingly structure-less meetings.
Thanks for the great article. I’m currently collaborating with a client on a new web-based product in worksessions, after several rounds of us doing iterations on our own and making formal design presentations to the client. Our designs were doing what they asked for, but were not gaining traction with the busy and distracted client team. We reduced the size of the team involved and started working in 3-4 hour chunks directly with the client (who is the VP of engineering). In two sessions we have made great progress. The client is fully engaged and having fun. The work is innovative. If we had taken this approach sooner it would have saved the client time and cost.
Copy & paste the code below to embed this comment.
Kevin Segedi
This article perfectly provides for a solution to my team’s pain points. We have evolved into this type of workflow, but haven’t been good at creating the best goals. A map can only help you find a destination that has been chosen! This article serves as a nice map to also show the shortest path to creating satisfaction for all.
Exactly sayin what im trying to do with my project teammates at the moment, like to read what experienced ppl have to say about collabortion and team management. Thank you for that
26 Reader Comments
Back to the ArticleNeil Turner
Yeah – I agree. Collaboration is key. Client input can sometimes seem like a hinderance but it’s always gonna be part of the design process. I do think as designers we need to stick up for our beliefs but I think we need to communicate the reasons behind them so that we provide the client with all the facts. If they then choose to ignore them then thats fine. We tried.
Scott Walldren
I agree with Lasse’s comment, that it’s potentially a recipe for disaster—herding cats. But I think you give us an adequate structure for these seemingly structure-less meetings.
Tania Schlatter
Thanks for the great article. I’m currently collaborating with a client on a new web-based product in worksessions, after several rounds of us doing iterations on our own and making formal design presentations to the client. Our designs were doing what they asked for, but were not gaining traction with the busy and distracted client team. We reduced the size of the team involved and started working in 3-4 hour chunks directly with the client (who is the VP of engineering). In two sessions we have made great progress. The client is fully engaged and having fun. The work is innovative. If we had taken this approach sooner it would have saved the client time and cost.
Kevin Segedi
This article perfectly provides for a solution to my team’s pain points. We have evolved into this type of workflow, but haven’t been good at creating the best goals. A map can only help you find a destination that has been chosen! This article serves as a nice map to also show the shortest path to creating satisfaction for all.
Tommy Bekri
Exactly sayin what im trying to do with my project teammates at the moment, like to read what experienced ppl have to say about collabortion and team management. Thank you for that
Wahne Tubman
How can these sessions work when you have teams in multiple locations? How can you alter this approach for global teams?