Brain Wiring for Construction Professionals.

Brain Wiring: Why Continuous Learning Should Be a Condition of Employment

Here’s the deal. I have noticed something genuinely dramatic happening to my own understanding over the past year, and it came from an unexpected source, the sheer discipline of writing books faster than I ever thought possible. That process has taught me something worth sharing directly with anyone serious about this industry.

How I Am Actually Writing Books This Fast

People sometimes ask how I am producing so many books so quickly. The honest answer starts with raw material. Between podcast transcripts, video transcripts, articles, training content, and graphics, I have somewhere around six to seven thousand real pieces of content already sitting in text form, built up over years of actually doing this work.

That was not always the case. My very first book took roughly twelve to fourteen years from the initial outline to actual publication, much of it originally dictated by voice during a long drive, then edited and refined over and over. I even scrapped an entire earlier version of a different book after a collaborator started taking credit for it, and honestly, that early draft was not very good anyway. The version that eventually replaced it turned out to be one of my strongest, earning a genuinely high rating from real readers.

Going from one book roughly every year, to two books a year, to a book every three months, and now to a genuine book a week did not happen because the underlying work got easier. It happened because the accumulated archive of real content, combined with a genuinely disciplined process, finally let that existing depth of knowledge move from my head onto the page at a pace that actually matches how fast I am learning new things.

Why AI Collaboration Changes the Math, When Done Right

Of the roughly two dozen books I have written, about half came entirely from my own thinking and organization, with no AI collaboration at all. The rest were built through a real, deliberate process with AI, and I want to walk through exactly how that works, because the process itself matters as much as the tool.

Here is the actual sequence I follow when building a chapter with AI assistance.

• Build a real outline first, load relevant transcripts as background material, and clearly explain the actual goal for that section.
• Ask for a draft, listen to it critically, and give direct feedback, sometimes across several rounds, until it genuinely holds up.
• Cross check any new idea that emerges against the rest of my existing material before treating it as something worth keeping.

Here is something genuinely useful I discovered along the way. Working inside a closed project that only references my own loaded material produces writing that is technically accurate and, honestly, a little flat. Working instead inside an open conversation that blends my own material with broader outside knowledge and commentary produces something noticeably richer. Think of the difference between plain bacon and eggs served with nothing else, versus a properly seasoned dish with real depth built in. Both are technically the same core ingredients. One tastes like an actual meal.

I only discovered this by actually testing both approaches on the same book and comparing the results honestly, rather than assuming one method was obviously correct in advance. That willingness to test an assumption against real output, rather than simply trusting a guess about which setup should work better, is itself a small example of the same discipline this whole post is actually about.

What I Have Personally Learned Through This Process

Here is the part that genuinely surprised me. I spent roughly ten years collecting logistics concepts, studying real experts in that space, and learning directly in Japan, and I still discovered real gaps in my own understanding while actually drafting the book. Concepts like Eliyahu Goldratt’s drum buffer rope method, or the specific differences between production Kanban, replenishment Kanban, and pull Kanban, only became genuinely clear to me once I had to actually explain them well enough for a real chapter to hold together.

That pattern has repeated constantly. I am learning somewhere between a dozen and sixty genuinely new concepts every single week, simply through the discipline of having to draft this material clearly enough for someone else to actually understand it. I recently walked through a massive manufacturing warehouse, uninvited to share an opinion, and quietly spotted a dozen or more real problems with how the plant was organized and how work was actually flowing through it. I said nothing, since nobody asked. I noticed everything, because I am genuinely sharper than I was even a year ago.

Why This Should Change How Every Role Approaches Learning

This is exactly why I believe continuous, role specific learning deserves to be treated as a genuine requirement, not an optional bonus. You cannot lead a logistics operation, run a prefabrication effort, or manage a project team well without actually reading, studying, and training in the specific material your role demands.

Here is roughly how I would build that discipline into any organization I ran.

• Logistics staff genuinely re-reading their core reference material at least once a quarter, using audio if that fits their schedule better.
• Project engineers revisiting the relevant training material on a consistent six month cycle, treated as a real job responsibility.
• A genuine, ongoing book club running at the company or jobsite level, focused specifically on the material each role actually needs.

Why I Deliberately Make This Material Easy to Access

I want to share something practical here too. I intentionally do not restrict the digital rights on the books I publish, meaning people can download them freely and feed them into their own AI tools for summaries or audio conversion. I hold the actual intellectual property, and I would rather see this material spread and genuinely used than protect it so tightly that fewer people actually benefit from it.

Why This Deserves to Be Treated as Seriously as Any Professional Requirement

Pilots retrain constantly. Doctors retrain constantly. Every genuine professional field treats ongoing learning as a real requirement, not a nice extra. Construction deserves the exact same standard. Given how much outdated or simply incorrect information still circulates across this industry, I genuinely believe we cannot afford to treat continuous learning as optional any longer.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build a genuine, role specific brain wiring habit, real reading, real retraining, and real reinforcement, rather than treating initial onboarding as the only training anyone ever receives.

So here is the challenge. Pick the single most relevant piece of training material for your own specific role, and commit to revisiting it on a real, recurring schedule, not just once when you started. Track honestly how much sharper your own diagnostic instincts feel after a genuine quarter of doing that consistently.

Jason Schroeder said it plainly: “We’ve all got to start doing this brain wiring thing.” Make continuous, role specific learning a genuine habit, and watch how much more you start noticing that used to slip right past you.

On we go.

FAQ

Why does the article distinguish between writing with AI inside a closed project versus an open conversation?

Because a closed project that only references a person’s own loaded material tends to produce technically accurate but somewhat flat writing, while an open conversation blending personal material with broader outside knowledge tends to produce something richer and more engaging. That distinction matters for anyone using AI tools to draft content, since the specific setup chosen genuinely affects the quality of what comes out.

Why did drafting a book actually reveal gaps in the author’s own understanding, despite years of prior study?

Because explaining a concept clearly enough for someone else to genuinely understand it requires a deeper level of mastery than simply being familiar with the idea personally. The discipline of writing forced a level of precision that surfaced real gaps, like fully understanding drum buffer rope or the different types of Kanban, that years of general familiarity had not fully closed on their own.

Why does the article recommend different reading schedules for different roles, like quarterly for logistics staff versus every six months for project engineers?

Because different roles carry different levels of complexity and different rates of change in the relevant material, so a single universal schedule would not genuinely fit every position well. Matching the reading cadence to how quickly a role’s core material actually needs reinforcement keeps the practice genuinely useful rather than becoming a generic requirement disconnected from actual need.

Why does the author choose not to restrict digital rights on the books he publishes?

Because the priority is genuinely spreading useful knowledge across the industry rather than protecting the material as tightly as possible. Allowing people to download and repurpose the content, including feeding it into their own AI tools for summaries or audio versions, reflects a belief that wider use of accurate information matters more than maximizing control over how it gets consumed.