To lead our collaborative future, architects need to decentralize or risk being further marginalized.
Architects know that they need to collaborate to succeed. But how will they go about doing it? How, in other words, will they make collaboration happen? As importantly, how will architects make the changes necessary to become not only more collaborative, but leaders of this effort, amidst disruptive change?
AEC leaders already do a great deal to encourage collaboration amongst their teams, providing vision, collaboration-conducive work environments, collaboration technology, and by removing obstacles – including themselves –when necessary, gladly getting out of everyone’s way. They encourage diversity, discussion – even disagreements – as a basis for moving the project forward. By telling their collaboration stories, leaders paint a picture of what collaboration looks like when it is done well. Most importantly, AEC leaders make sure every team member is making the same project. But AEC leaders cannot assure this happens in every meeting on every project. Who, then, on the team will lead the day-to-day collaboration challenge?
Barriers to Collaboration
We know collaboration is hard and takes time — to build relationships, to clear-up misunderstandings, to listen and to get things done. Past experience can hold teams back, and one of the barriers to collaboration remains organizational silos.
Brand erosion is also an impediment to collaboration. For a designer whose singular voice is her expression through her work, collaboration is equated with joint authorship, to some the antithesis of creative expression, muddying the message of the work, dispersing and diluting the voice and design intent of the creator. This thinking is of course mistaken, as leaders need to make clear. One only needs to compare a Beatles tune with any of the band member’s solo efforts to recognize that teams make better decisions – and importantly, results – than individuals. The real fear in collaborating is that we – and our work – will be mediocre, a race toward the lowest common denominator, and with it, irrelevance: we will be seen as just one more designer among designers.
The truth, of course, is by not collaborating architects become marginalized. Not knowing how to effectively collaborate will lead to their irrelevance.
Complexity and Speed
Of the trends impacting our new world of work – including digital tools, collaborative work processes with attendant blurring of roles and responsibilities, working remotely and together earlier – two trends have made all the others a necessity: complexity and speed. Our technology has an impact on the anticipated speed of decision-making. When still hand-drafting, while facing a construction-related question or dilemma, architects would say: We’ll work it out in the field. This was the architect’s go-to VIF: where the contractor on the architect’s behalf would be expected to Verify In Field. Later, working in CAD, architects would say: We’ll work it out in shop drawings. With little bim: We’ll work it out in CDs. And today, with social BIM, We need to work it out NOW!
In the face of increased project speed, we will be tempted to slow down. And we are well advised to do so. Studies show to make decisions that stick, we’re better off delaying choices for as long as practically possible. According to Frank Partnoy in Wait: The Art and Science of Delay, the best professionals understand how long they have available to make a decision, and then, given that time frame, they wait as long as they possibly can: “we are hard-wired to react quickly. Yet we are often better off resisting both biology and technology.” Since our current technology and integrated work process does not accommodate our waiting – in fact, it discourages it – leaders need to make it safe for their teams to make assured, unrushed decisions.
Likewise, despite construction being wickedly complicated, we should not be tempted to oversimplify. We need to take the complex and make it seem simple – without oversimplifying – resisting the temptation to treat a complex task as simpler than it is, potentially leading to oversights and mistakes.
Decentralize or be Marginalized
Architects continue to see themselves as central to decision-making, whether at the top of the project pyramid or a prominent point of the team triangle. Contracts notwithstanding, architects are not the point. For collaboration to work, architects need to get off the pyramid and go wherever and whenever they are needed.
Decentralization implies the transfer of authority from central to local offshoots who represent the firm and serve as its public face, whether as project manager, project architect or project designer – sometimes any two, or all three. These offshoots – like starfish arms – contain the complete DNA and trust of the organization.
Although collaboration requires the architect to decentralize, it has to start at the top, where firm leaders entrust employees to lead teams. What will it take for architects to decentralize? Successful collaboration requires facilitative leadership. For the architect to take on this role, they must play the part of process facilitators over content creators, becoming in essence co-creators. When each teammate contributes as a co-creator, no single person has to carry the load, including the leader. Decentralization allows architects to join the project – and be immediately effective – midstream. Ideally, the architect is called in before the owner even considers undertaking a building project, but the reality is – due in no small part to their own making – the architect is often called upon when the project is already well underway.
Given the collaborative nature of today’s project teams, consideration needs to be given to the firm representative’s leadership and communication style. As proxy stand-ins for the firm, each team leader needs to be able to communicate effectively at all times, with all in the room. Architects’ often-unconscious communication habits will be increasingly scrutinized and decreasingly tolerated in these tight-knit groups. Architects, working more closely with others from every facet of practice, will need to become more familiar with their communication style, paying particular attention to the ability to adjust one’s style to those of others from other work cultures and walks of life.
FOCI: Multiple-centered – not centerless – leadership
Architects – seeing that others have helped narrow their options significantly – narrow them further by opting to see themselves as single purpose entities. One example of this is described in Victoria Beach’s salvo in the newly published 15th edition of the Architect’s Handbook of Professional Practice where she asks architects to see themselves more as design-focused celebrity chefs and less as engineers assuring the health, safety and welfare of the public. For architects, it’s a both/and, not either/or, proposition.
In fact, architects in the coming years will be needed less as content providers of design intent than as facilitators, orchestrators, collaborators and integrators (or FOCI) of this information and process. Architects will have an opportunity to lead this process if they can learn to become better listeners, aggregators and refiners of the information that arises during the various stages of design and construction.
With the blurring of roles brought about by working collaboratively on integrated teams, the architect’s job is to keep decisions – often multiple decisions – in play. Collaboration and digital practice require a formwork on which to base multi-faceted decisions on increasingly complex projects. One such formwork is that of the rubric FOCI: in lieu of a singular central focus of the center, think of the multiple centers of the ellipse. A redefinition of decision-making that takes digital technology and collaboration into consideration creates such a formwork that will help the architect to communicate effectively with multi-disciplinary teams. To move from a circular to an elliptical model, the architect needs to decentralize.
To decentralize, architects also need to move away from the spotlight where they are the central focus. Many architects are introverts and would gladly succumb the spotlight to others. Architects don’t need to be the loudest one in the room to lead, just the one who listens best. To accomplish this, architects need to focus less, and FOCI more, by serving as project facilitators, orchestrators, collaborators and integrators. By decentralizing, the architect is no longer decision-maker so much as facilitator of project information and decision-making process. As facilitative leaders, architects can become experts in knowing how to find information as opposed to what the information is. When collaborating, it is not about how much any one person happens to know: projects today are too complex for any one person to know everything. Knowing from whom – and where – on the team to find information is more important than one’s ability to store and retrieve it. Architects will also serve as strategic orchestrators of large teams from the earliest stages, often made up with primary, secondary and even tertiary players. The C in FOCI is in flux: the C can represent collaborators or creators or controllers or coordinators. Architects, of course, are component and system integrators.
This post is an excerpt from Randy Deutsch’s article How We Can Make Collaboration Work: How architects can decentralize rather than be marginalized in the Jan-Feb 2014 Trends issue of DesignIntelligence journal.