We often treat management frameworks like rigid code-bases—expecting the same input to yield the same output from every engineer. But when I began parenting my 11-year-old nephew with Autism and ADHD, I learned quickly that standard "commands" resulted in runtime errors, timeouts, and unexpected crashes.

Surprisingly, the strategies I developed to support his executive function and sensory needs mapped directly to my initial struggles in engineering management. In this talk, we will explore the parallels between supporting a neuro-divergent teenager/child and leading a high-performing development and quality team. We will cover why "implied" context causes friction, how to manage context-switching costs, and why the "Why" matters more than the "What." You will leave with tips for creating a documentation-first, clear-communication culture that benefits your junior developers, your senior architects, and everyone in between.