Neuroinclusive Engineering: Turning Cognitive Difference into Software Engineering Strength
GOTO Copenhagen 2026Software teams ship better code when the way they collaborate actually fits the people doing the work. This masterclass is a practical introduction to neurodiversity in tech and how to design everyday engineering practices that reduce friction, protect focus, and unlock strengths across different thinking styles.
You will learn why neurodivergence is more common than most teams assume: up to 20% in the general workplace, and often even higher in tech and engineering environments.
More importantly, you’ll learn what to do about it without turning it into HR theory or awkward labels. Through hands-on work with real situations from your own team, you will learn how to shape concrete team agreements and simple interventions that make meetings, communication, planning, code reviews, and feedback safer and more effective for everyone.
Key Takeaways
- Understand what neurodiversity is and how it commonly shows up in software teams
- Identify “neurotax” in engineering workflows (interrupts, meetings, ambiguity, review dynamics) and redesign for clarity
- Create practical team agreements for communication, focus time, decision-making, and collaboration rituals
- Support performance without forcing disclosure: build conditions that work whether people share diagnoses or not
- Apply small, high-leverage changes that improve psychological safety, quality, and sustainable pace
Who Should Attend
Software developers, tech leads, architects, and engineering managers who want smoother collaboration, clearer communication, and more sustainable high performance. No prior knowledge of neurodiversity is required.
Prerequisites
Bring a laptop and a real example of a recurring friction point from your work (a meeting format, planning ritual, code review pattern, or collaboration challenge).
Format
A mix of short inputs, hands-on exercises, and peer dialogue. The focus is on concrete engineering situations and everyday friction points, using light-weight experiments to adjust team practices in ways that can be tested directly in your current setup.
