Show Notes
Middle management is not usually the part of a career anyone dreams about, which is probably fair since most dreams do not involve inheriting more responsibility while time and authority stand nearby pretending they were not invited. Still, there is something important that happens in that space if you are paying attention. You start to see how decisions move through a firm, how unclear expectations become someone else’s burden, and how much leadership depends on remembering what pressure felt like before you had the ability to pass it along.
More from Life of an Architect
Ep 212: Schedules - Who Owns Your Time explores the demands of architectural practice, shifting deadlines, and the hidden cost of making every commitment work.
The universe has rules, and apparently so does the office - most of them explaining why schedules expand, promotions go sideways, and adding more people can make a late project even later. In Episode 211, Andrew and I use 11 laws, principles, effects, and razors as a practical lens for making better decisions, managing people, and surviving the occasional meeting that should have been an email.
In Episode 210, “The Cost of Loyalty,” we look at how the relationship between employees and firms has changed, why loyalty can no longer be assumed, and what research says about engagement, compensation, career growth, flexibility, and retention. The conversation explores how architecture firms can rebuild genuine commitment by creating clearer opportunities, investing in people, and making professional growth worth staying for.
Ep 209: Understanding Residential Contracts breaks down five ways architects charge for residential work, along with the tradeoffs of each.
Most people treat asking good questions as something you either have a knack for or you don't. Bob makes the case that it's actually a trainable habit, one built on slowing down long enough to catch a guess before it disguises itself as a real question. Along the way, he and Andrew revisit an old closing segment from the show's early days, the one where negotiating the question mattered more than answering it, and connect that memory back to the discipline architects rely on every time technical requirements and design instincts have to share the same decision.