Creating an “Architecture of Participation”

design team tabletime at sparc

This past Thursday I was fortunate to hear Bill Taylor of Fast Company speak at the Charleston Chamber of Commerce annual event. There were a lot of components to his talk that sounded like the culture we’ve created Sparc. The phrase that caught my attention was the “Architecture of Participation“. There have been many times that I’ve thought of gathering the right people in a room as being an “architect” of people. My friend Taylor seems to be an expert at that. Or when my developer buddy Josh “architects” a solution by knowing what technologies play well together & essentially get shit done. This type of “architect” means as a leader, you facilitate problem solving by leveraging your team for the solution. That’s why we have a team, right? I think we were already doing this well, but sometimes having a word for it helps bring these quiet practices to light; formalizes them.

What interests me in the Architecture of Participation is how it calls out a leadership style I’m very comfortable. Traditional leadership has relied on the leader to identify & solve a problem on his own, then project the solution onto the people below them. The concept of leadership through participation means that rather than working in a vacuum, I can leverage the smart people around me. In the end, they’re typically the ones implementing the solution – this helps them “own it” as well. The Architecture of Participation simply means I facilitate the conversation & then let people be good at what they are already good at. Coming from a creative background, we (my team) is already skilled at working as a team – nothing new here. Learning & creative process intentionally leverages diverse skillsets, so why not problem solving on a leadership level?

I moved forward w/ a plan this past week to create “advocates” within our design team. Motivated individuals who can help lead the team in one aspect of design. This scales me, and offers the opportunity for these smart people to own a focused element that we need as a team. The advocates focus on aspects such as design quality, user experience or front-end development. Things our team need, but I can’t always facilitate the conversation 100% of the time on.

It’s a great thing to work with talented people. By creating an Architecture of Participation, we enable more creative solution & allow the smart people we work with to scale the team as a whole.