Christopher Parsons discusses how the difficulty of implementing knowledge management (KM) for AEC firms varies by existing state and ambition. He describes a spectrum: some clients already have organized (even if analog) resources and only need a searchable repository, while others (e.g., ~60-person firm) had no systems and required a year to document tribal knowledge. He also describes using the KM product (Synthesis) as a tool to drive cultural change — leaders requiring sharing to shift collaboration norms. Resource availability and organizational readiness determine the lift.
Chapters
Can you talk about is this a heavy lift for people when somebody's looking at implementing something like this? Like, what kind of a lift is it for them to start having something usable to pull from? Do I have to say it depends for you? Or like, man, it is. It's the answer to almost every question that comes up like this. But like, to put. To put some more thought behind that, one of the variables I would look at for it depends is your kind of existing state. So we've had clients come on board who had a very, like, maybe in a more analog way or a less efficient way, organized, really good resources, and they just needed a really good bucket that was searchable and easy to use to put them in. And that's been a really easy transition. And they came in and their Deltec data was great, and their open asset data was great. And we just basically plugged it all together and off they go. Not quite that simple, but that's one end of the spectrum. We've had other clients who have come on board who I'm not going to name them. I'll let them tell. Maybe they'll tell their story on this. But, like, I'll use them as an example. They came on board at like 60 people and had nothing in terms of systems. And they had severe growing pains. And they were getting all this work, they were growing. They're like, we cannot keep operating like this without really clear procedures and standards and a way to connect the people. Like, it's just not working anymore. And so they basically, they took a year to implement because they had to write everything. These are things that they had never, ever written down. It was all just kind of social or tribal knowledge. And so that was actually the lift. We've had clients use synthesis as a Trojan horse for the culture change they were wanting to effect. So I can think of one CEO who took over one of our clients, and it's an engineering firm, and they had kind of a. You know, I say this, I'm going to put a disclaimer out here. Some of the most collaborative, sharing knowledge. Best clients we have are engineers. Like, they do really, really well with our product. This culture was kind of more of the caricature that some architects may say about engineers, right? They just were very close to the vest. They weren't sharing. It was a tough environment. And she came in and basically, like, collaboration is the key to our thriving and actually maybe even survival as a company. And so she used this kind of social intranet at the time as a way she used sharing on the platform and asking all of the kind of leaders and held them accountable to sharing X amount of time as a way to make that culture change of making the company more collaborative and open and transparent. So I'm kind of a little all over the map there, but that's honestly what our journey's been like. We just find people in various states of existing content and also what they're ambitious and then how much they can resource the thing. So sometimes people try and take this on with like three other things going and some people wait until they can really get a strong Runway at it.