How Diamond Schmitt Is Redesigning Apprenticeship for a More Demanding Profession | Michael Leckman

Over the past several decades, architectural practice has become dramatically more productive. Projects that once required large teams can now be delivered by just a handful of people.

However, that progress has had an unintended consequence for apprenticeship.

Michael Leckman, Principal at Diamond Schmitt Architects, remembers a time when relatively inexperienced people could join a larger project team, take on bounded tasks, and gradually learn by watching more experienced architects work. Today, teams are smaller, projects move faster, and there are fewer places for someone who is still learning the fundamentals to contribute.

During our conversation, I compared it to learning to surf. Traditional apprenticeship gave people a chance to learn on three-foot waves. Increasingly, the waves are twelve feet high.

So how do we help emerging professionals become ready for those larger waves without shortcutting the experience, mentorship, and judgment that great architects still need?

For Diamond Schmitt, part of the answer has been to stop relying on projects alone to provide that education. To be clear, emerging professionals still learn by working alongside more experienced architects, but the firm is also investing in the learning infrastructure outside those projects: teaching the fundamentals of practice and building science, helping people understand how buildings go together, and giving them easier access to the firm's standards, best practices, and accumulated knowledge.

The idea is to help people build a broader base of knowledge faster than they could one project at a time. And then, when they need something in the flow of work, make it easy to findβ€”whether that's a learning resource, a standard, a past project, an expert, or increasingly, an answer surfaced through AI.

The goal is to redesign apprenticeship for a profession that keeps getting more demanding, where the waves keep getting bigger.

Emerging professionals still need the experience, mentorship, and judgment that come from working on real projects. But if the industry is asking them to surf twelve-foot waves, firms have to do more to prepare them for those conditions before they paddle out.

That means building their foundational knowledge faster, giving them access to more of the firm's collective experience, and making the right learning available when they need it.

I invited Michael onto the Smarter by Design podcast to explore how Diamond Schmitt is approaching that challenge, and what the rest of the AEC industry might learn from it.

I really enjoyed this conversation, and I think you will too.

β–Ά Watch or Listen

Watch or listen to this episode via YouTube, Spotify, Apple Podcasts or wherever you get your podcasts.

πŸ“Ί πŸŽ§ YouTube
πŸ“Ί πŸŽ§ Spotify
πŸ“Ί πŸŽ§ Apple Podcasts


πŸ“š Show Notes + Resources

KA Connect Talks

Smarter by Design Newsletter and Podcast

Webinars


πŸ“ƒ Episode Transcript

This transcript was lightly edited for clarity.

Chris: Michael Leckman, welcome to Smarter by Design.

Michael: Thanks, Chris.

Chris: You've been at Diamond Schmitt since 1988, and over that time, you've watched the firm grow and change quite a bit. And not just in terms of headcount or size, but number of offices, leadership, technology, project types, the way that we work. You're a principal now of this 300-person firm, and you've also been a senior leader pushing Diamond Schmitt to become much more intentional about how knowledge moves through the firm and how people learn.

One of the things that you and Sam talked about at KA Connect is this idea of accelerated mentorship. Let's just start there. Why does mentorship need to be accelerated? What's happening with mentorship these days?

Michael: I think the number of projects and the number of team leads has grown so fast. And I say "so fast" β€” the firm's grown over 30 years β€” but I would still say the market is asking us to change so fast that there could be a breakdown in the ability to mentor the teams. So that's one side of it.

The other side of it is I think that there are still incredibly talented, quiet, under-the-radar design professionals who are doing a great job, but could be doing much more for themselves and for us. So I think we're trying to address possibly a gap in the way the firm has grown, but also to reach those very quiet people.

Chris: So it's both making sure that people aren't getting left behindβ€”

Michael: Correct.

Chris: And by that, I think you mean they're potentially ready for more, but they don't speak out for themselves and tell people that they're ready for more.

Michael: Yes, well put. That's right. I should mention that one of the things we do in our traditional mentorship is that we move teams around. We're on five floors here, and when a new team is created, we disrupt their current situation. We ask them to move from the ground floor to the fifth floor and join a team. There's only one reason to do that: communication and mentorship.

So already we have that core. But even in that group β€” and it could be as few as five or six, or it could be as many as 22 who are all congregating in one corner of a studio so that they can be closer together β€” when you get to a group of that size, and that's not uncommon for us in the peak phase of a project, people can still be left behind.

Chris: Even within the project team?

Michael: Within the project team, conversations are happening too fast. The terminology may be new to them. The drawing formats may be new to them. So it's both office-wide and within the team, despite what I think is a really effective team communication situation, which is that we move people to this one studio. We opened a studio just down the street to my left here because we had a project of 25 people, so that they could sit together and learn the building type and the contractor and the client all at the same time.

Chris: So why is this more of a challenge now than 10 years ago, or even when you started in 1988?

Michael: Yeah, ouch. (laughs) It's all happening so fast. I'm reminded that one of our most important early projects was a $14 million project for which we had 14 people. I remember thinking, "Oh, that's interesting, sort of a person per million dollars of construction value," right? That's not the case anymore. We have $100 million projects and we've got three team members, four team members.

Chris: Wow.

Michael: So each team member is asked to do a lot more and to be investigating components of the building in a lot more detail than they were ever able or asked to do before. I mean, that formula fell apart pretty quickly after 1984, which is when that project was completed. But still, that ratio has changed radically. We're asking people to be able to work on that most powerful tool, Revit, and do the work of four or five or six people or more to put together a 60-drawing architectural package.

Chris: And earlier in their career than we used to ask them, I think, is implicit. Is that true?

Michael: Correct, correct. Yeah, that's right. Earlier in their career. So they're seeing much more, faster.

Chris: So where do you think the traditional way that you've done architectural apprenticeship is breaking down, given that we're asking them to do more faster? What's not working?

Michael: It used to be that we hired students from the local schools on work terms, and we could very often hire second-year students, and we would have a place in the team to be able to mentor them along. And often, if we were lucky enough, they would come for more than one term. Over those multiple terms, their co-op program on its own, but also the co-op program with us, would've had them mature in a really good way.

We realized a few years ago that the projects were moving so fast that we really didn't have a place for those second- and third-year students. They just weren't well enough equipped to join teams. In the past, we would have someone who could give them small enough tasks, with defined enough parameters and clear enough direction, that they could work on something for a couple of days, and it wouldn't break the team to have them be learning and not necessarily contributing. That's an example.

And so recently we've had to make that difficult decision that we're hiring summer students only further up that food chain: third and fourth year, fourth year and first-year master's students. Because when they come to the office, the teams are smaller. It used to be that the teams might have been seven or eight people. Now they're three or four or five people. Everybody's got to be able to contribute.

Chris: There's nowhere to hide on a team and absorb what you need to absorb to grow.

Michael: That's right.

Chris: I had this mental picture in my mind when you were explaining that, of surfing. I imagine surfing three-foot waves as a beginner versus a beginner coming out and there are 12-foot waves, and they're like, "This is not how you learn to surf, on these really, really big waves. Someone's going to get hurt."

Michael: That's right. That's right.

Chris: So one of the strategies is we just wait until they're a little bit more mature in their learning journey. But where is that happening? Is that happening in another firm, or are other firms, you think, facing the same challenge? What happens in those two years?

Michael: It's tough. We've had conversations with the different schools about how to better prepare the students for those co-op terms. And unfortunately for us, we've had to err on the side of more experience, so we just haven't been hiring them.

Chris: Just given the nature of how the work has changed. So somewhere between how they're handing them off from school and what the reality of practice is, there's a bit of a gap.

Michael: And the gap is concrete knowledge of how to make buildings. It's not design. Obviously you need a bit of both in order to make a meaningful contribution to the early phases. So we need them to have that great design vision, but we also need it to be integrated with knowledge of making buildings.

Chris: Once you get them, how much do you have to intentionally invest in developing their concrete knowledge of making buildings?

Michael: Well, as you know, we went through a process of understanding what it is that the early-career architects really wanted, and what they wanted was the fundamentals. They needed more fundamentals. It was a gap that we saw, and we still see, and we wish that the schools could fill in better.

But nevertheless, we do have a program, and it's in many different forms. It's 30-minute seminars, it's lunchtime videos, it's short-format videos. It's a lot of different programs, together with components in our intranet, in our DSX, our Diamond Schmitt Exchange.

Say someone's doing reflected ceiling plans. They've never done it before. They don't know how much coordination's going on. The project lead has given them some indication of what's supposed to happen, and it doesn't matter how many times a project lead says it, you still feel that terror when you go back to your desk: did I understand it completely?

So we have those videos and some drawing guidance in our DSX to help people. It's really to help that group through these fundamentals components, which it doesn't seem like we could do enough of. We're doing them a lot.

And we do them in different formats, right? We do them as narrative storytelling β€” what we call building science in the service of design. We try to tell the story of what the design intent was and how building science supported it, so that they get a sense of that hierarchy. And then we have other scenarios where project leads are talking about oops moments in a project: "This was an oops, we had to fix it. This is the kind of thinking that may have led to it, and this is how it should be done correctly." So we have those as well.

Chris: So the fourth-year students come in, they have a better base of fundamentals, but there are still a lot of holes that you have to fill.

Michael: Correct, yeah.

Chris: And so in the past β€” let's call it the traditional apprenticeship model β€” a project lead might have had the time, because of slower, less complicated projects, to sit with, let's call her Denise, and go through how to do an RCP. I'm putting a lot of words out there; you're going to tell me which of these are true or not true.

Now, because things are moving so fast, one of the things you're trying to do is say, "Actually, Denise, go take this course, whether it's live or on demand, and read these resources on your intranet and get yourself somewhat educated on this. I'm telling you what's important about the project, but go learn about the basics of RCPs, try it, and I'm there to guide you" β€” versus having to instruct every single person who ever joins one of my teams on RCPs one-on-one. Is that close?

Michael: That's close. I would say that there was a moment where the project lead β€” if you had three or four typical classrooms next to each other β€” would have done a complete pass of one of the classrooms and said, "This is what it needs to look like. This is the hierarchy of all the elements. This is the pattern-making that we're engaged in. These are the design intents that we're trying to fulfill. This is the technology that's being incorporated. Here's one. Now do the other three."

Chris: Now, would they draw that one with the student, or would they bring it to the student and sayβ€”

Michael: It could have been either way, right? And I'm saying "student," but it could be a junior, it could be a junior well along in their progress. Sometimes you get something back and you realize that there are too many markups. You just have to put a piece of trace on it or go into Bluebeam and draw it again and be able to say, "This is actually the way that we want to see it developed. Remember that there's a lot you're not seeing here: the structure behind, the sprinkler lines, the ducts, all that stuff. You've got to put that all together and find the basis of the pattern that respects all of the elements that need to be coordinated."

Chris: One of the things that I've heard from other clients, and I want to ask you if this is true for you, is that those project leads generally liked doing that kind of mentorship β€” "I'll show you one, then you go do some" β€” and they feel very guilty that they can't do it in the same way that they used to. Is that fair?

Michael: I think that's fair. I think that's fair. And there are still many project leads who do that, right? Sometimes there's no other way than to set the direction, rather than give the verbal instruction or the principles and let them come back. So many are still doing it. And Bluebeam's their friend. Bluebeam is the modern trace, of course.

Chris: I've been using this phrase a little bit lately, a new social contract with project leads. To some degree, Diamond Schmitt as an institution will handle some of that fundamental education to help the project leaders out. They can take some of that off their plate, and Diamond Schmitt handles that. And so they can handle more of the project-specific "this is how it applies to the project we're working on," versus "here are the basics of how this thing works." Is that true?

Michael: That's true. I mean, to a certain extent, that's the hope: that we're providing that infrastructure, the foundations that maybe the schools of architecture have chosen not to give. We get students from schools in other parts of the world β€” the EU, Germany and France, and in some cases the UK β€” where all that is very well taken care of.

Chris: The building science is a bigger part of their education?

Michael: Yes, yeah. And interestingly, on the other hand, they also manage to teach architectural concept development in some ways stronger than many of our schools. So we continue to have those conversations with the feeder schools, let's call them that. They're excellent students, and we have many, many graduates from those schools.

But it's interesting to look at the top 5% and see their success, and then understand how one gives that level of knowledge to those who aren't so talented that they would excel in any school they went to. What about the rest? What about the next 25 or 30%? As I said, when we see those applicants from particular areas in the EU, it's a whole lot stronger.

So we're interested in the top 5%; that's who works in our studio. But we're also interested in what would be necessary in the schools for that next tranche of master's graduates to be given a leg up as well.

Chris: You mentioned identifying what β€” let's just call them emerging professionals, to give a more generic term β€” needed. Can you talk about that process of finding out that that's the kind of learning Diamond Schmitt needed to invest in, that you needed to build more of those foundations, that that's what people were hungry for? How you came to find that out and what you did about it?

Michael: Well, there were two steps, actually. The first step was that we were getting feedback from the field that, let's put it this way, some of the drawings were not performing the way we wanted them to. And so we started by having our contract administrators run a feedback loop, and that was a natural thing to do.

Each of these initiatives β€” and we've had many over the years β€” has a shelf life. There's energy to get them going, there's good attendance, and then they fade a little bit. Whether people miss one session or two sessions, the next thing you know, the project responsibilities take over and they fade into the background. That's not to say that they didn't help; they just had this shelf life.

After that, we started thinking about an internal education program that would create more continuity. In other words, an infrastructure so that those groups weren't only relying on the energy they had at the end of their project day to get things done, but something more. And that's when we started talking about DSU, Diamond Schmitt University.

Chris: Roughly what year? Do you have a sense?

Michael: 2017.

Chris: 2017, good.

Michael: There were two threads in the original idea for Diamond Schmitt University. One was, as it's now called, fundamentals, and the other one was called exploration. And we thought that the exploration side was a stronger way to start the Diamond Schmitt University program than the fundamentals side.

Chris: So what's the difference?

Michael: The exploration side is bringing in international speakers to talk about design ideas. Filmmakers, photographers, writers, thinkers, planners β€” that's who we had come into the office.

Chris: So design culture and ethos and process and inspiration, that kind of thing.

Michael: Correct, yeah. And it was great. It was great. We set up a group to look ahead six months and think: who could we bring in from your network of interesting people who happens to be in Toronto right now? Who could we bring in to talk about what they're doing, to make sure that we're continuously broadening our perspective on the influence of our projects?

It was extraordinary. We had a group of about 15 people who got together for an hour and brainstormed with yellow stickies and all sorts of things until we got to a point where we thought, "Okay, those are categories that we would be interested in pursuing, and those are people who could align with those categories. Let's see if we can make a curriculum out of that." And we thanked them very much, and we did it again six months later. It was a really energizing thing to do.

As you might know, I came to architecture after studying building science. I studied building science first. I always have a sense that there's a story to tell β€” I'll say a poetic story β€” about building science that is not limiting; it's opening. That's what I tend to think. So I was hoping that would have traction in our first round of Diamond Schmitt University programming. It didn't.

And it was only after we had the design-focused, design culture program well underway that we started to see some things start to fragment. And Sam did a survey. Sam Bordenβ€”

Chris: At the time, your learning and development leaderβ€”

Michael: At the time, our learning and development leader at Diamond Schmitt. She said, "You know what? I'm hearing that I should probably do a survey, and maybe we need a course correction." And it happened to coincide with us supporting her going to the University of Toronto to take courses on the theory of adult education. So she went away, she came back, and she said, "I'm going to undertake this survey and see what comes back." And what came back overwhelmingly was that the fundamentals needed support in the studio. I mean, we knew it, but it was far more so than maybe we could have predicted.

Chris: So that's the needs analysis, I think Sam has called it.

Michael: Yes.

Chris: And so she's really asking those emerging professionals, "What learning opportunities do you need to help you go to the next level?" Did she survey other people? How comprehensive was it? I guess I mean, was she trying to matchmake, saying, on one hand, here's what emerging professionals need, and then here's what the principals and project leads say they need, and trying to find the Venn diagram intersection?

Michael: That's a beautiful analogy. I don't think it was quite that way. I think we were hearing strongly that we needed to change course and address this perceived professional development gap. To a certain extent, we were providing the other side of the Venn diagram. We were saying, "Oh, we think we should be talking about design and nothing else." And we were hearing, "Yeah, there should be a little bit more."

Now, that's not to say that even during that period, in the early days of Diamond Schmitt University, we weren't also investigating and exploring different ways of bringing that other content. Whether it was with individual contract administrator seminars, or we actually had an individual who was really ready to produce a six-week or 10-week program of fundamentals. It never quite got the legs. It never quite got the energy to the extent that it needed to, and that we learned later it should have had.

Chris: What do you think kept it from getting traction the first time you tried it, and why do you think it's working better this go-around?

Michael: We probably didn't define it properly. It's often a case of the right person with the right energy at the right time, and then giving them support. Maybe that's just it, really. And remember that every one of the initiatives has maybe an 18-month arc where it's given all this energy. So we had a few 18-month arcs within that first four or five years, and getting them revved up to start again with a new person or a new energy or a new voice of some kind wasn't working.

Chris: Having known the Diamond Schmitt story a bit, what I think is maybe also true is that those courses were mostly synchronous, live, versus now you're making more on-demand content. So there's the energy management of that subject matter expert who has to teach the thing over and over and over again that you're looking out for.

Michael: So true, so true. I think we started recording more deliberately about five or six years ago, and then quite a bit in the last four years. When we started recording, we were able to start focusing on specific content that could find itself in DSX β€” which wasn't originally in an LMS system, only later in the LMS, but anticipating an LMS system. We actually had a rough one started before the polished one arrived.

So there's no question that in the current format, with more and more recordings and with a team β€” we've now got Rowan Davidson, who's managing the operational side and growing into the strategic side β€” we're making sure that all that material gets from the presentation to the LMS system. So there's been a radical change, I'll say, in the last four years in the ability to make use of intermittent energy rather than continuous, long-arc energy, and then have it become part of a longer arc.

Chris: And so if I'm back to that principal who needs Denise to do the RCP, now instead of looking ahead at the calendar saying, "Well, we're teaching RCPs in eight weeks. Oops."β€”

Michael: It doesn't work.

Chris: Right. Now I can get Denise what she needs more immediately, as you build out this foundational curriculum.

Michael: Right. Exactly. And I think one of the things about that concept, too, is that there's skill and knowledge, but there are also ways of thinking. What I'm hoping for more in upcoming recorded sessions is reminding people how to think your way through an RCP.

It used to be that the interior elevations and the RCPs were the last thing you ever thought of. In our building types, you've got to think about them a whole lot earlier, and there's a whole lot more to coordinate now than ever before, I would say, and also at a fast pace. So how does one share, in a short-form video that you can watch again and again, the starting points for how one does that? Because if you've been told by the project lead, "This is what I want, this is what I want it to look like," you may not know what you're actually drawing. In the old days, you didn't have to know. Move that circle from there to there, check, done.

Chris: Yes.

Michael: Now you have to know.

Chris: Because we're in BIM now, not in CAD?

Michael: Correct, correct. Well, even if you were in CAD, you weren't given the clues in 3D that you had to be solving. You had to go to the mechanical set, you had to go to the electrical set, you had to go to the structural set, you had to make sure you weren't interfering with all those things. And then you went back to the RCP and you sorted it all out, and maybe you did many, many overlay traces to make sure that you were getting it right. So you have to know more now, and a lot more is being thrown at you, that you may or may not know you're influencing, than ever before.

Chris: Which makes me think about brains a little bit. If you're responsible for a larger and larger surface area of technical knowledge, and projects are moving very quickly β€” the simplest thing I can think of is, I don't know anybody's phone number anymore.

Michael: No, nor do I.

Chris: And so I think there's maybe an opportunity here. If I do an RCP tomorrow, and then in nine months, and then again in 22 months β€” between now and that second time I do one, I will have forgotten most of what I learned in order to do the first one. Maybe I've remembered 30% of it. I may remember the big picture, but I don't remember the details. So there's this ability to relearn, this way that I can continue to get apprenticed by the firm at the moment of need, because the amount of surface area I'm asked to cover is so much broader.

Michael: Yeah, yes, I agree. But I also think that the thing to be teaching, that would apply to RCPs or to interior elevation studies or to anything, is the way of thinking about it. Not the drawing task, not the modeling task. What is the design intent here? What are the materials being used? Do you have good command of what they all are? Linear wood slat ceilings with integrated diffusers and lay-ins? Do you have good command of what the design potentials are?

Because it may be coming to you as a raw space, in which case you're designing it. Or it may be coming to you as a finished design, and you're now fulfilling it and being given the design concept tools to make sure that you're not messing it up, but actually making it better through the step that you're responsible for. That to me is key.

So I would say you're right, there are things that you're going to remember that will now be in a video, maybe, that can help you six months from now. But one of the things that keeps changing is the tools.

Chris: Correct.

Michael: And so understanding the underlying design intention and the strategy for making things right would've applied the same way by hand, by CAD, by BIM, and by whatever BIM 5.0 is.

Chris: So you're building a good internal theory of mind of how buildings work and how they go together. And I think what you're saying is that part is the most important, because the tools might change, the actual materials or systems might somewhat change, but understanding those core fundamentals β€” that's the part you want to make sure people get the opportunity to learn.

Michael: Right. And the great thing about the accelerated mentorship possibilities is that you can hear it first in the team environment that we create β€” which we know is disruptive, and which we love so much β€” and then you can watch it again. You can make sure that you've got it by being able to look at it again and again.

I'm going to use an analogy: learning to swim late in life. I've been using Instagram, and there are stroke improvement videos on Instagram β€” underwater, above water, from the front, from the back, animated models. And I have to watch them every day, to make sure that the visual is imprinted on my learning, so that when I get in the pool, I'm working with a visual of the stroke and not the words of the stroke.

So I think the same is true about what we're hoping for, and what we've seen in some cases, which is the advantage of being able to watch it again and again. It's not just once. It's not even twice. If you want to get this right, the short-form videos on the design thinking underlying whatever building component we're talking about need to be watched many, many times.

Chris: I think it's so interesting you use that example. I've read this in books and heard it on podcasts over the last couple of years, using two sports. One of them was skateboarding and the other was basketball: what a 13-year-old and a 16-year-old and a 20-year-old can do in those sports now versus pre-YouTube, basically.

Michael: Correct, correct.

Chris: The skill level has just gone through the roof earlier, because they're able to see not just what their local coach shows them or some kids on their block. They're able to study what the best people in the world do and watch it over and over and over again, in slow motion, on demand.

Dan Hottinger in our community said the thing that I've said a million times: we don't have 20 years to build a 20-year architect anymore.

Michael: Right, I love that.

Chris: So let's say we have eight. How do we do that? I think partly what we're getting at here is giving them tools to be able to do reinforcement learning. I think that's what you're talking about with swimming, right? You're doing reinforcement learning, but then also β€” let's say you move from doing a crawl stroke to doing a breaststroke β€” you continue to expand your repertoire, with or without a coach.

Michael: Right. Well, yeah. And I hope what happens to our staff is what happened to me. The lifeguard has been watching me for 18 months, and a week ago she said, "Where have you been taking your lessons?" And I said, "Instagram." And she said, "You're getting..." Anyway, all to say thatβ€”

Chris: No, no, no, no, go ahead.

Michael: No, that's it. It's really just that it's a discovery for me. It can be intellectually true, but having been doing it myself now for about six months in this trajectory that I'm on, I know that it's what I'm sure a lot of our cohorts are doing already in some categories. And I think it's absolutely the right aspiration for us to have about the learning content we're making within the office.

Chris: And I think there's another element that I suspect is there, because I'm going through a similar thing where I'm learning some new skills around powerlifting. I'm able to learn not only the actual mechanics, but you're getting at the why behind it. Why are these the mechanics? How does the body actually work? Getting the kinesiology. And I think what you've said your goal is with these foundations is to get at that deep why β€” what makes it all work β€” as well as how to do the thing.

Michael: Absolutely. Sam and I presented in the summer, and we were talking about the feedback we got when we presented the beautiful chartβ€”

Chris: I think you're talking about the modern learning organization maturity model.

Michael: Maturity model. Thank you, yes.

Chris: Which you took and made your own, which I loved.

Michael: I did. I took it and made it my own. But when we heard the commentary back, I think a lot of the ideas underlying the commentary were exactly that. The conversations we have in teams include the very practical, straightforward mechanical task β€” this is how you do it β€” but more importantly, they include the moments of doubt and questioning and inquiry that make you say, "Well, this is the way we normally do it, but in this building, with this grid, with this ceiling height, with these demands, none of those rules apply. So we've got to think about some new rules here."

And being able to share that: "Oh, I can change the rules. I don't have to just follow the rules. I can change the rules in order to answer this most important question." No one actually said that in any of the commentary, but I know that that's part of our DNA. The Diamond Schmitt DNA is to say, "Okay, if it's not working, just change the rules. Make it work some new way."

And being able to communicate that β€” we were just talking about reinforcement learning β€” in a live environment, it happens at a different pace and you can't repeat it, but you hear it from maybe a few individuals over time, over the course of theβ€”

Chris: They tell stories of having to blow up an approach because it wasn't working, and that gives you permission to know that that's something you can do.

Michael: Exactly. So that's a judgment call about how to get success next time.

Chris: I used this phrase "social contract" before, but I was referring more to principals or project leaders at that time. Now I want to turn it around on learners. What you would've asked of somebody joining Diamond Schmitt 20 years ago was not watching swimming videos or RCP videos, or upskilling and doing reinforcement learning on your own with this discovery. You're asking them, I think, to be more self-directed in order to be able to keep up with the bigger waves that you're facing, the more difficult tasks.

And maybe the expectation used to be more, "I'm joining this company, they're going to tell me how to do my job, and they're going to hand everything to me." It sounds like in order to be successful in a new paradigm, you have to be more entrepreneurial or ambitious in figuring out your way through the project. Am I reading that right?

Michael: Yes, yes. We have so many sources of validated information now. I'm working with a few recent hires right now in the office who actually joined us because I said, "There are going to be lots of different ways for you to learn here, and you will get the most from your time with us if you take advantage of them all, including knocking on my door and letting me point you in some directions that you might not find on your own."

Well, sure enough, that has started happening. And I usually start by saying, "Have you checked OpenAsset? Have you checked Diamond Schmitt University? Have you used the AI search on DSX?" And one said, "Yes, but there's no material on this particular topic that I can find whatsoever." And as it turned out, it was a pretty fascinating question. So we just talked it through.

And then I said, "But by the way, now that we've talked it through and I know where you're going, these two projects have a virtually identical scenario to what you're working on right now. This is where you can go and see if you can enhance it." And of course, he was already there. He had already researched that through DSX.

So that's one particular person. Another person, an incredibly talented young architect, will take any suggestion and run with it. And of course, as you can imagine, what I often suggest is, "Have you looked that up on DSX?" Some will just humbly walk away and look it up and not come back and talk about it again, but this person does. This person says, "I did look it up. I also watched the video, and I really didn't understand. In my culture, the issue of sustainability wasn't nearly in the foreground like it is here in Canada, and now I understand."

So those are things that are starting to happen. So yes, there's a contract, which is that we're expecting people to not just go to the web, but go to our web more often.

Chris: So there's a piece of this social contract that is on the learner: self-directed, search first, whatever. There's a piece of it that's on the leaderβ€”

Michael: Absolutely.

Chris: Which is: share the why, help them navigate resources. If the resource has a hole and they can't find it, explain it, talk them through. It's not like you're going away saying, "Don't talk to me." It's "search first, and then let's go deeper."

Michael: Exactly.

Chris: But there's a third part to this, at least β€” maybe we'll identify more β€” which is on Diamond Schmitt as a knowledge and learning organization: to have good learning and knowledge resources and keep them up to date. And when holes are identified, to fill them. You can't have all of it documented, but especially filling high-priority holes, right?

Michael: Of all the immense challenges we have on that side, it's the most immense, because just when you think you've filledβ€”

Chris: Filling holes is the most immense challenge? Yeah, let's talk about that.

Michael: I was part of a group who were trying to create appropriate drawing standards, reference drawings, so that people could have a visual reference point for the way that our packages should look before they go out. And I'm from a different cohort. I did work in BIM, but I'm not working in BIM anymore. So I had an expectation of the way that it should be fulfilled. I was politely asked to leave the committee. Well, actually what they did was they disbanded and re-formed a new committee and didn't inviteβ€”

Chris: Didn't invite you. They started a new group chat and they left you out of it, right?

Michael: I was zero houred in the committee. It was the best thing that could have ever happened. The new group β€” working with the tools, working with someone who had a really strong visual sense, who wasn't being given the friction that my point of view was creating β€” ended up at a place that I am very happy with. But it took a while.

So we have this first document, which is our drawing manual. And you would think, "Doesn't every office have a drawing manual?" But given the number of times the tools have changed, the steps to get the drawings have changed significantly. So here we are. I was looking at a package just before I came to this meeting to join you, Chris, and I had to admit that the drawings have taken a dramatically big step forward as a result of the new drawing manual and the hands of the people who are in the current cohort. You would think that should be degree zero of every architecture firm. How many drawing manuals have you had to pass?

Chris: So what you're getting at, I think, is that it's not only filling holes. It's keeping those holes filled and keeping them up to date with how fast technology and practice are changing.

Michael: Absolutely. And we've had many, and often they've been the role of an individual person. We've had technical leads before. We've had AutoCAD scripters before who created a following of people who thought, "Oh, we just have to do it that particular way and we'll get the right drawings," and they did. And then you change platforms, and you've got to start all over again.

So I would say, as of today, based on what I saw from my own team on the drawings, we've made an enormous leap forward by seeing the power of one well-constructed, supported document β€” one that is not only a document, but is also supported by all of the filters and families that are created in BIM. The key people in it all were two: one is an architect and brilliant graphic designer, and the other one is our BIM director. And of course, it had to be them.

Chris: Right.

Michael: So when I've seen what that grouping did, I realize now, for future holes β€” maybe this is a lesson strictly for me β€” identify the hole, identify the right people, and step away.

Chris: Yeah, I was getting at another dimension of the social contract, which is for the subject matter expert. What I understand is that the output β€” the goal of the drawing manual β€” needs to be made now using tools where your deep expertise isn't. You know the previous paradigm of tools. So how could you be the person to tell people how to achieve this outcome if you're not in those tools every day?

Michael: Even though I knew the visual output, the drawings themselves.

Chris: Yes.

Michael: But because of the angles from which I was coming at it, they were not resonating with the team who had to implement it.

Chris: So there's a kind of selflessness that we're asking of experts, to some degree: if you're not the one closest to the line or the tool or whatever you call it, let somebody else lead. But you could still review, right? You still looked at it and gave your thoughts and your feedback.

Michael: Absolutely, yes, yes, yes. And I refer to it constantly.

Chris: So hole filling β€” you said this is one of your biggest challenges. And the first place you went was, because things are moving so quickly, keeping them filled. Do you think the bigger challenge is keeping what you have up to date, or is it that new things keep emerging and you have to figure out how to teach and document and tell the firm the best way you know how to do it?

Michael: I think it's the latter. It's mostly the latter, actually.

Chris: New things are the hardest?

Michael: Well, you could think that making an exterior wall has been the same for 25 years, that it hasn't really changed. But it has changed. Materials have changed in a significant way, and the perception of those materials has also changed. The fundamental principles haven't really changed that much, but the way that they find themselves in a drawing has β€” the way that you have to think them through in a drawing, using the tools and the supports that BIM creates for you.

BIM is largely pick and place. You pick a wall type and you place it. You don't necessarily have to know where it fits on the slab edge so that all the materials run through the way that they should, because the way the tools are constructed, they help you a little bit. But you need to know those things.

And I would say, if we could do the same Diamond Schmitt first-principles-based strategy as we did for the drawing manual β€” have a Diamond Schmitt first-principles-based way to build four types of walls. There are many catalogs out there that can show you most of it. Unfortunately, most of them have a mistake of some kind. They may not be for our climate, they may not be for our industry, they may not be for the right construction type.

All to say, having that available to the next cohort, done in a very clear way so that they can teach themselves or re-watch β€” reinforcement learning β€” all of the stories around the way the wall material meets the ground, the way that the wall material meets the sky. Understanding the idea, and then the technical interventions that make the building go from good to excellent.

Chris: Well, I was going to ask how you prioritize hole filling. You went to walls, which makes me think you haven't done the Diamond Schmitt first-principles version of wall types, but maybe that's something that you're going to start working on.

Michael: In our multifamily condo tower group, it's very well worked out, but in our institutional groupβ€”

Chris: I see.

Michael: β€”and building types, it's less worked out.

Chris: Yeah. I want to come back to that question of prioritization. How do you think about that without getting depressed?

Michael: Poof. I would say we have succeeded when we've been opportunistic and worked organically, based on things that come to you: you seize the opportunity and you run with it. I would say that has been how we have evolved successfully as a firm through different eras of the economy and different eras of the tools.

And so β€” and it seems to be an inverted way of looking at it β€” you're not trying to solve the problem; you're trying to solve the people first. Find someone who's got energy, someone who's got the right way of communicating, someone who's got engagement with a group beyond their project, and see if they can run with it. That has largely been how we have evolved in so many different categories.

So, just like with the drawing manual: they thought they'd brought the right people together, but they hadn't. They had to disband. They started again, they focused, and it was one person who persisted and made the brilliant decision to add this person with a very keen graphic sensibility. And they also have to have bandwidth, extra bandwidth. It doesn't happen within your project day, usually.

Chris: If there's something important that can help the firm, did you have to create the opportunity for bandwidth? How did that work?

Michael: I mean, when I'm saying bandwidth, I mean the ability to just, in your private time, do a little more.

Chris: Right.

Michael: And do we support it? We certainly acknowledge it in a big way. If someone has done the heavy lift of taking on a subject matter that has been troubling us for some time, and they find the way somehow to give it extra attention, sometimes over months, and deliver a document like our drawing manual β€” but also many others β€” that is a representation of their commitment to the firm, their engagement with topics that improve the firm. And that is a significant first step to promotion.

Chris: Okay, so you're getting toward promotion and advancement criteria β€” and I don't know if it's implicit or explicit β€” that say you help build and maintain the knowledge of the firm. That's what leaders do.

Michael: That's right. That's right.

Chris: Is it explicit or not?

Michael: It's absolutely explicit, yes. Let me make sure that I'm not going to forget a category here. In our guide to what it takes to be an associate, which is the first big step in the firm, we talk about design excellence. We are really nothing if we aren't innovating in design: materiality, spatial, site design, and all that stuff. So design excellence first. In the original definition of the firm, design excellence meant that you can lead projects to national design awards. So not a low bar β€” a high bar.

The next one is project management. Can you manage your group? And it's implicit in project management that you're managing the group on time and on budget.

So you're running a project and it's an excellent project. You're managing a team, and the team is saying that you're a supportive manager. Next is business development. Can you participate in the RFP process? It's so well set up in our office: there are usually three components β€” the statement of understanding, the statement of work plan, and the work plan itself β€” which the project leads usually provide. And it's really hard to do in a workday.

The next one is technical mastery: that the buildings aren't just complete, but done at a level that represents high-quality institutional buildings. And then last but not least is mentorship, teamwork, and engagement.

We expect our leaders to have those five categories in their sights and to be ready to contribute to all of them. And as you progress, you're contributing to them weekly, if not daily.

Chris: And just to put a finer point on it, the last category, I think, is the one that's most related to what we're talking about.

Michael: Yes, yeah.

Chris: Is the expectation mentoring and teamwork on your project? Or at what point are you responsible not just for my team learning, but for Diamond Schmitt, the organization, learning?

Michael: The last word was engagement, and that's a euphemism for looking outside your project, being involved in wider office-related issues, and improving the office.

Chris: I want to close by talking about something that your firm does really well, in my opinion, as an outside observer, which is your dedicated investment in knowledge and learning management. You've got people who do this for the firm full-time.

Michael: Correct.

Chris: And I want to maybe start with how you got to be the executive sponsor β€” principal in charge, however you frame it internally β€” of that group, why you took that on, how you started building the team, and when you knew it was time to bring on full-time people. I'd love to hear that journey.

Michael: The journey starts really with Jeanette Parker, who we called the office Siri. (Chris laughs)

She was someone who had a very broad view of the company, because she was involved at a management level, managing our filing systems, and at a grassroots level β€” before we got to Wendy Gomoll β€” managing our samples. And she was with the records and archives group, trying to understand how to coordinate all that. So she was someone who could see that there was a limit to what she could do to manage knowledge. She wasn't called a knowledge manager. I don't even remember what her actual official title was.

I was away for some time in 2016, and when I came back, she said, "Guess what? That project that you and I have been talking about β€” some way of getting our intranet to be more complete β€” we're going to make this happen." We had an intranet before KA Connect. It was home-built, a DIY version, and it had run its course, I guess you could say. It wasn't able to meet our expectations. And so she said, "We're going to pursue KA Synthesis, and this is all the things that it can do. Will you be the sponsor?" And I said, "Well, you and I have been having this conversation for a while. I'd be happy to be the sponsor." So Jeanette was reallyβ€”

Chris: She pulled you in?

Michael: She did.

Chris: Interesting. And so she was the archivist managing records, but said, "There's this other big challenge that we have, this opportunity. I want to do that thing. And I can't do that if it's in the passion budget. There's too much work to do."

Michael: Too much work to do. So we've got to build a team around this. So we then created the team to work with Susan and Sarah to figure out how to build our own intranet. She, if I'm not mistaken, was part of all those earliest meetings where we were trying to figure out what we were going to do and how we were going to do it.

I should mention the possible reason that I was part of it, other than the fact that I tried to build an intranet on FileMaker. (Chris laughs) I thought, "I know, we're going to make the equivalent of hockey cards' worth of information that people are going to fill out at the end of a project, and that way we'll have the 10 most important things that someone learned, and it's going to be in a FileMaker database."

Chris: Yeah, and people can just go search there and find out whatever they want.

Michael: Exactly.

Chris: Perfect. (Michael laughs)

Michael: And Jeanette and I had shared stories about how to put something together that was capturing that knowledge. Also, prior to that, believe it or not, we had a fighter pilot who was working for us briefly, and he started doing project debriefs for us. And he said, "Well, when you have an incident in a fighterβ€”"

Chris: After-action review. Right, right, right. Yeah, exactly.

Michael: Exactly. So then you have to ask yourself the three whys. Why did it happen? But why did that happen? Well, why did that happen? He was in the office, I think, for six or seven months, and it was interesting to hear people keep searching for that third why, to understand the structural or administrative or procedural issue that was underlying a problem.

So we had some momentum on trying to capture knowledge, but we didn't really know how to get there. And I was involved in some of those. And I'm also occasionally β€” certainly more so in the last eight or nine years, but even prior to that β€” sought out to do internal training or education of some kind. So it was a natural affinity that seemed to be there.

Chris: And so Jeanette went from being your archivist, your information manager, to being your director of knowledge management. Wendy became a manager of knowledge management. And you had Sam, who, if memory serves, was an executive assistant and then became your manager of learning and development, I think?

Michael: Correct. So that was an example of organic opportunism. We saw someone who had a particular way of working, a way of thinking, and we wondered whether this could be a role she could fill. We guessed right, and she grabbed hold of it and just ran, in the most interesting ways that we couldn't have predicted.

Chris: Maybe I'll set this question up a little bit better. My belief is that now, where we are in 2026 heading into 2027, the idea that you're going to manage the knowledge and learning of your firm using a passion budget β€” it being the nighttime thing on somebody's list β€” I don't think you can keep up with the pace of change and the volume of knowledge and all the things we talked about: filling the holes, creating fundamentals training, accelerating the apprenticeship approach. That doesn't seem possible to do without somebody waking up every morning and saying knowledge and learning are the top thing on their mind, right?

But in 2017, was that a hard sell, to say, "We're going to take some of these people and point them at this problem, and this is what they're going to do, and they're going to be, quote-unquote, overhead people"? Do you remember any resistance, or were people generally okay with it?

Michael: I think there was so much enthusiasm about the potential that KA Synthesis could fulfill. The early-day videos and demonstrations that we were shown caught on very quickly. And it was such an improvement over anything we had conceived to that point. And Jeanette and Wendy were already there.

Chris: Yup.

Michael: And Jeanette and Wendy always have many other things that they're doing.

Chris: Right, they're not purely running Synthesis at the company.

Michael: They're not purely running Synthesis. But there are times when you introduce a new version of it that it takes over much of their days. So is it mostly a 50% responsibility? I would say it's mostly a 50% responsibility, and it ebbs and flows. And as I was saying, when there's a need to act, it becomes probably never 100% of their time β€” probably closer to 90 β€” but nevertheless, a lot of their time.

So it had a lot of support early, Chris. It really did. And then when we were given data to share on a quarterly basis about the uptake within the office, that was irrefutable. We could feel it, and the engagement that it led to β€” again, irrefutable.

Chris: I want to close by trying to recap where we've been, and then looking ahead toward the future a little bit in terms of this accelerated mentorship that you're really in the middle of β€” or maybe you might even say at the beginning of β€” looking out 10 years from now. As you and Sam and I were preparing for KA Connect, we were referencing it as Michael's dream, your vision for what the future of knowledge and learning could look like at Diamond Schmitt. I wonder if you can bring us into that dream and vision and let us know how you see all this working, if it works as you imagine.

Michael: The senior architects, from principals to senior associates to associates, feel so completely comfortable with the content on the learning management system that they can remember sections of videos that they want to share with teams. They're making reference to it on a regular basis; it's part of conversations. And when they have an issue that they think needs to be shared with the wider office, we have a setup for them to be able to step right into and do a five-minute video that would tell, in a technically correct, passionate, and performative way, a story about how to get through a difficult issue β€” or a difficult issue that doesn't have an answer, but maybe everyone faces. Whatever it is, they'd be able to go from fluency to sharing in the most direct, unencumbered way.

Chris: That's beautiful. I wrote down as you were talking that it's an integrated part of the practice. It's infrastructure for the company, and it's living, breathing infrastructure that's constantly being updated.

Michael: Yeah, that's the dream.

Chris: And then as AI gets better, both ours and in general, the gap between getting to that knowledge in the flow of work and when you need it should hopefully get closer and closer.

Michael: And we are just on the verge of adding the AI-activated plugin to our BIM teams. We're not quite there yet, but that would be the other side of it. What did we say we absolutely needed? We had to build the infrastructure. We have to embed it, so we're in the process of embedding it. And then we want to help people use it and put it where they need it most β€” and actually help the senior people know how to direct people to use it. So those are the three things.

So it's a long, slow climb. But I can feel it with this next generation of principals, who I think need to be at the next KA Connect so that they can feel the energy that other knowledge-focused leaders have, and be able to bring it back like I do every time I go.

Chris: Yeah, I like that phrase, knowledge-focused leaders. Maybe even to broaden it, there's this tension between "I became a designer to go build great projects and have an impact on my community" and all of those things β€” I don't know how many people went into school thinking, "I'm going to help build a great organization and build a great firm." I think it was maybe more about the impact and the design opportunities.

But I think you have been a great example of a firm builder as a person, an institution builder, with that ability to find people who want to be firm builders. And part of that is that knowledge is so critical. This is how you're able to pass it through the generations: somebody has to say, "I want to make the collective better." But we also need other people who go make great projects. Both things have to be true. We have to be a business and a practice, but we also have to do great design, and those aren't mutually exclusive.

Michael: Maybe two things. I'm lucky enough to be able to do both, right? To be working on great projects and to be given the license to continue to contribute to the learning environment. And it couldn't be more appropriate, because I need to be having an ownership transition β€” an ownership transition of the learning environment. And I'm very much hoping to be able to encourage other leaders to be at KA Connect to keep that fire going.

Chris: And get them surrounded by other people who are institution builders, so they feel like they're not alone and that it's a fun thing to do.

Michael: Exactly, exactly.

Chris: Yeah, great. Michael, thank you so much for your generosity, not just in joining the podcast today, but in general, in sharing with our community. You've been an inspiration to me and to many others in this community, you and your team. So I really appreciate you being here.

Michael: Thanks very much, Chris. Pleasure to be here.

Next
Next

Cutting the Complexity Tax