Rebuilding the channel on purpose

When leaders notice institutional context slipping, their first instinct is more aggressive documentation or indexing wikis into AI retrieval tools. That solves lost context for readers, but not the senior engineer’s problem. Writing a static wiki page never forces a veteran to defend trade-offs or trace failure cascades under questioning. Documentation captures static answers; only live human friction keeps architectural fluency sharp.

Restoring that friction does not mean restricting juniors from using AI assistants, nor does it mean adding optional team meetings that get cut the moment a deadline tightens. If directors are rewarded solely on ticket velocity, informal coaching will always lose to the sprint board. Instead, leadership must embed live human articulation across the four moments where architecture is built, rehearsed, stress-tested and passed on.

• At code review: require verbal design defense on cross-boundary pull requests. Instead of letting seniors review large AI-generated diffs silently, require a ten-minute live walkthrough whenever a change touches service boundaries, retries or state machines. The junior explains what the code assumes about upstream systems; the senior explains why the boundary exists, replacing downstream code forensics with upstream architectural dialogue.
• Between incidents: run live system walkthroughs without slides. Once a month, a senior engineer walks peers through a critical production workflow on a whiteboard, tracing failure modes and historical trade-offs out loud. Where the explanation stalls or relies on guesswork, institutional memory has decayed before an outage can expose it.
• After an outage: require unscripted architectural narratives in postmortems. Do not let seniors satisfy an incident review by pasting a runbook link or an AI-generated summary. Require the service owner to explain live to adjacent teams how a failure propagated and why the boundary exists. Unscripted explanation under peer questioning is the only reliable test of whether a team still understands the software it runs.
• At the 90-day check-in: test architectural handoff, not just ticket count. AI makes it easy for a new hire to close starter tickets in week two without learning how the system fits together. Use the first structured performance check-in to verify whether the new engineer can modify a core workflow and explain its failure modes without escalating to the senior owner. If early ticket velocity is high but every structural change still routes back to one veteran after a quarter, AI is accelerating surface work while core architecture stays trapped in one head.

Every seasoned engineer knows the feeling of trying to explain a familiar system out loud and finding the words no longer come cleanly. That stumble rarely means they lost their edge. It means the friction that kept their understanding sharp was automated away, and leadership must put it back before the next outage asks for an answer.