DBC. Embrace it now.
What’s DBC? DBC stands for Design by Committee. Did you just shudder?
At Critical Mass, we use a form of design facilitation called Rapid Design Labs (RDLs) as a collaborative method to work with our clients. They help drive out requirements and ideas for solutions and they are great for building trust among the collaborators. I’ll be writing more posts about design facilitation and our RDL method here in coming weeks.
I was about to start a Rapid Design Lab last week when one of the participants complained that he “didn’t believe in Design by Committee”. On the face of it, it seemed like a legitimate concern. After all, everyone knows that DBC is bad, isn’t it? In typical hindsight, here’s what I should have said. Simply, DBC is inevitable on any project with more than two people. DBC is simply human nature. We need a method to embrace it.
If you design or create any kind of solution for other people, you’ve participated in some form of Design by Committee. If it doesn’t happen while your client is briefing you, it happens during the design process. If it doesn’t happen during the design process, it happens when you receive feedback. If it doesn’t happen during feedback, it is bound to during one of the many stakeholder presentations you’ll be expected to give.
We all pretend that we can control DBC. We do it by attempting to specify how our clients brief us or give feedback. We try to control it by defining specific roles and responsibilities and attempting to educate others about their place in the process. Some of us play the emotion card, pouting when others don’t participate the way we believe they should. And how successful are we in all this? Not very. It’s time to accept that we can’t expect people to offer specific opinions limited to certain things and delivered at certain times.
Let’s be more realistic. Let’s acknowledge that our clients have challenges that they need our help with. For example, they may understand the trials and tribulations of their business better than anyone, but still find it hard to articulate their needs and requirements. We should also acknowledge what they have to offer. Clients want to participate in finding the solution and have good ideas that deserve exploration. Finally - let’s also acknowledge our clients’ rights. They have internal client and external customers to satisfy and have the right to respond to what we create.
So how do we engage our clients more openly, collaboratively and productively? I think we need to start by finding ways to embrace DBC. We also need to manage the associated risks. Without a solid approach, we can become victims’ of DBC’s worst problems:
* Time wasted on circular debate
* Mediocre solutions produced through negotiation rather than ideation
* Lack of attention to a more strategic view of the problem
* Too much focus on individual tactics
This is where the practice of design facilitation becomes critical. What is design facilitation? Like other forms of traditional group facilitation, design facilitation employs meeting techniques and group exercises to help groups create potential solutions and agree on the best way to proceed. The idea isn’t new - architecture firms have used design charrettes for years and IDEO’s Deep Dive process is a type of design facilitation (in my opinion). Now it’s time for digital marketing practitioners to embrace this practice.
Next time, I’ll talk more about what I believe are best practices in design facilitation methods.


This is one of the single most difficult areas that a creative lead faces. Steering the group-think in a productive direction that yields strong creative execution backed by intentional purpose. Can’t wait to see the next installment.
Hi Dave,
Wonderful article. I love the way you turn DBC on its head. I am very interested in the next installment as well.
I would add in to the discussion that typical artifacts used in the design process appear ineffective when they are not understood and I would argue that they are anything but understood. I’m speaking of everything from wireframes to IAs to creative briefs. We ask for sign off on artifacts that even our own teams struggle to grasp from a larger picture point-of-view. ie: everyone can agree that a single wireframe should or should not have a piece of content, but I’ve found very few are able to place this in the context of a flow or experience.
Part of the question I have been asking of late is whether or not we are giving the proper tools to our clients and our internal team members to actually realize, discuss and then approve the experiences we are creating. We’ve been experimenting with using Axure for live (low-fi) prototype building together with team members, stakeholders and clients. We are suddenly able to discuss the whole experience across participants and I have been amazed more than once at the results.
Sean
Hey Sean and Bruce
Thanks for the feedback. I’m thinking that the next post will talk a little about rapid design labs and how they work. I’ll try to incorporate your comments including some discussion about conducting constructive conversations and the most effective types of deliverables.
Dave
Looking forward to it!!