Hey there,

My dad founded a commercial air conditioning contracting business in Southern California in the mid-1970s. I worked there many summers growing up, and it's where I started my career after university, spending eight years there before moving on. So I had a front-row seat to how he thought about the work.

He'd win a commercial construction bid, standard HVAC install, spec'd out by someone else's engineer, and his job was to build what was on the page. But he also had an engineering education, and it wouldn't let him just take someone else's drawings at face value. He'd look at a set of plans and see alternatives that nobody had asked him to consider, with an almost automatic sense of the cost and benefit of each one.

So instead of diving straight into construction, he'd stop and evaluate whether there was a better way to re-engineer the system. More effective, more efficient, less cost. He'd bring the redesign to the owner and, more often than not, they'd accept it.

Eventually, in the mid-to-late 80s, the thinking became its own business. He spun off a separate company for engineering services and design, distinct from the contracting work. Sometimes it fed projects his own construction company would also build, what the industry calls design/build. But mostly it served projects well outside Southern California that other contractors would build. Of course, the concept of paying an engineer for design work wasn't new. There was already an engineer's name on those original drawings he kept improving. What was unusual was a contractor, someone whose job was to build what was on the page, consistently stopping to rethink the design and eventually building a whole separate business around that impulse. He'd figured out, partly through a willingness to stop and evaluate rather than dive straight into construction, and partly because his training had equipped him to see what a rushed pass would miss, that his particular version of that thinking was worth paying for on its own.

A Different Version of the Same Lesson

Years later, at Sony, I watched a version of this play out in a completely different world. This was 2001 through 2004, when everything about media was being rewired at once: internet, software, platforms, services. My boss ran a team inside a massive multinational company, and a lot of what his job actually required was figuring out how to position our work in the best possible light as the ground kept shifting underneath us.

I'd walk by his office and he'd look like he was daydreaming. Not on a call, not typing, just sitting there. And then he'd call me in and tell me what he'd been thinking about. He was reading the organization and the industry at the same time, trying to work out where the ground was moving next and how to position our team ahead of it.

What made him different from someone who just happens to have good instincts is that he didn't stop at having the read. He'd walk us through not just what he saw but why, the specific signals he was tracking and the reasoning that connected them. What he actually taught us wasn't a trick or a technique. It was the plain necessity of giving yourself the space to think, and the unique position it puts you in when you do.

"He'd figured out, partly through a willingness to stop and evaluate, and partly because his training had equipped him to see what a rushed pass would miss, that the thinking itself was worth paying for on its own."

The Take Everyone's Already Making

You've probably seen this argument by now, because it's everywhere. AI is making us worse thinkers. We're outsourcing synthesis, outsourcing drafting, outsourcing judgment calls, and the cognitive muscle is atrophying. Every conference panel in the AEC world seems to have at least one person warning that if we let AI do the thinking, we'll forget how to do it ourselves. There's something to that concern, and I've written about it before.

But there's a version of this argument that gets the causality exactly backwards.

Think about what my dad was pushing against in the 1980s. Think about what my Sony boss was carving out space for in 2003. The pressure to skip thinking in favor of doing, to fill every available hour with visible, measurable output, has been building for decades. Long before anyone had heard of ChatGPT or Copilot, organizations were systematically optimizing away the exact kind of unstructured time that real thinking requires. AI didn't create the thinking shortage.

That's an uncomfortable realization if you're a leader who's been framing AI as the threat to deep thinking. Because it means the thinking was already gone. AI is just the most convenient, most recent scapegoat for a loss that your own culture produced. In most companies, everyone was already running flat out, billing every hour, filling every minute with coordination and documentation and reactive work. They didn't lose their thinking to AI. They lost it to a decade of productivity hacking, always-on availability, and the quiet cultural belief that all 24 hours in a day are inventory to be filled.

My dad owned his company. Nobody was standing over him demanding he look busy. But even he had to push past his own feeling that stopping to evaluate a problem was a kind of idleness, when what it actually was is the highest-value thing he could do. My Sony boss had a different version of the same problem, an organization that read idle-looking time as unproductive time, where he had to justify the space he was taking to think. Different pressures, same underlying fight, and AI didn't invent either version of it.

Which is exactly why AI might be the thing that fixes it.

Where This Lands for AEC

If you run or work inside an architecture, engineering, or construction firm, none of this should feel abstract. These are firms built on exactly the kind of judgment my dad was selling: the ability to look at a system, a site, a structure, and see something a rushed pass would miss. That's the actual value proposition of these firms, and it's also the first casualty of a culture that measures worth in hours logged and drawings turned.

AI's real opportunity in AEC isn't shaving time off a deliverable. It's absorbing the 80 percent of detail work, the redlines, the coordination, the repetitive documentation, that has been quietly crowding out the thinking your firm was actually founded on. The competitive advantage isn't who turns around a set of drawings fastest. It's who still has people capable of standing in front of a problem and seeing the better version, the way my dad did before anyone thought to pay him for the thinking out loud.

That's a real choice, though, not a given. Buying back the hours is the easy part. Whether your firm actually uses them to think, rather than immediately refilling them with more billable work, is the part that determines whether any of this pays off.

Break a Pencil,

P.S. I've been spending time with AEC leaders on exactly this question lately. If this is a tension your firm is already living with, I'd genuinely like to hear how. Hit reply and tell me what "thinking time" looks like, or doesn't, where you work.

Reply

Avatar

or to participate

Keep Reading