Home //
Would Your Team Still Follow You if You Weren’t Their Boss?
Building, Configuring, and Running your Leadership OS
PRESENTED BY
Robert Harris
Founder of Coded2Lead
In moments of uncertainty, teams don't listen more closely to their leaders. They watch them.
What they're watching is your operating system under load. The skills that earn an engineer a promotion reward a logic-first OS stack: analyze, decide, execute. That stack misfires the moment you lead people, because human hardware runs emotion before logic finishes loading. The tools you mastered for the machine don't work on the team, and most technical leaders inherit that bug the day they step into the role.
This session rebuilds the stack as a Leadership OS, an operating system for how you show up under pressure, assembled in layers and grounded in psychology, anthropology, and Stoic philosophy.
First we build and configure it: Emotional Observability as the I/O bus that reads both your team and yourself, Stoicism as the discipline that opens space between stimulus and response, and a set of core leadership principles as the configuration that decides what fills that space.
Then we run the leadership applications: the everyday and high-stakes situations all engineering leaders face, each drawn from a real moment across a 25-year career, usually the ones that went wrong the first time.
Attendees will learn:
- Why a logic-first OS fails as a leadership stack, and what belongs underneath it
- How to develop Emotional Observability as a practice instead of treating empathy as a fixed trait
- How trust behaves like a bank account, collecting deposits and overdraft fees during moments of pressure
- How to handle the five situations that test every leader - teaching, one-on-ones, feedback, team decisions, and power dynamics - without dropping into factory defaults
All of it serves one diagnostic question: would your team still follow you if you weren't their boss?
Attendees leave with a framework for becoming a leader who earns a yes, and one application to run the moment they get back to their desk.
Robert Harris
Robert N. Harris is the Founder of Coded2Lead, a coaching practice dedicated to transforming software engineers into emotionally intelligent leaders. A 4x software engineering executive based in Houston, TX, Robert draws on 20+ years of pragmatic leadership experience - alongside a unique academic background in psychology and anthropology - to tackle the toughest problems in technology: the human ones.
His claim to fame is helping small engineering teams punch above their weight. He’s helped companies shrink product cycles from months to weeks, launch new products in months instead of years, and scale revenue by 10x.
He’s mentored tech leads, managers, and founders across industries, blending technical rigor with surreal metaphors, visual storytelling, and deeply empathetic insight. Whether he's refining a brand identity or helping a developer navigate imposter syndrome, Robert’s approach is iterative, creative, and always human-centered.
When he’s not coaching, you’ll find him in the garden, under the stars, or behind the wheel - using race cars, astronomy, and nature as unexpected mirrors for leadership growth. His mission: to help engineers debug themselves, lead with courage, and build systems where people thrive.
If a business is willing to invest in software engineering, he’ll make sure they get the most out of that investment.
More from Robert
ALL SESSIONS ↗Human Systems for Engineering Leaders - Building your Leadership OS
The toughest problems in engineering leadership have nothing to do with the technology, and everything to do with the humans building it. The technical skills that earn an engineer the promotion can be adapted to produce great leaders, but only with the right translation layer. Without it, leaders default to instincts that work on technical systems but fail on human ones. This workshop installs that translation layer.
An Anthropologist’s Guide to Engineering Cultures
What happens when a self-taught programmer with a background in anthropology ends up leading engineering teams? Robert Harris traces his path from BASIC on a Commodore 64, through a decade in archaeology and the social sciences, to running software teams - and the lessons that came with becoming a manager by accident and a leader on purpose. The hardest problems he ran into weren't technical. They were human. So he went back to his training as an anthropologist to solve them.
Designing Digital Hallways
Engineering culture is not created by values statements or team rituals. It emerges from thousands of small signals - who speaks, who hesitates, what gets reinforced, and what quietly disappears. Across years of observing software engineering organizations, one pattern appears consistently: when teams go remote or hybrid, culture doesn’t disappear - informal signal flow does. The hallways where trust, learning, and psychological safety once formed are removed, and nothing intentionally replaces them.
Human Systems for Engineering Leaders
You were promoted for being good at writing code. Then you were handed responsibility for a team of humans, with no training and no manual. Meetings. Conflict. Silence. Motivation. Trust. The instincts that made you a strong engineer don't transfer directly to people. Computers do what you tell them. People adapt to the environment you create - including the parts you never meant to. Here's the good news: you don't need a new personality or a new skill set to lead well. The skills you've built as an engineer - diagnosis, systems thinking, debugging under pressure, designing for resilience - are the same ones that produce strong leaders. What's usually missing is the translation layer that lets you point them at a human system instead of a technical one. This session builds that translation layer. We'll look at leadership not as personality traits or management hacks, but as a human system - a loop of inputs, outputs, and state that you already shape from the inside. We'll walk that loop in three parts: learning to see the system, understanding the inputs that quietly train it, and reading the signals it sends back to you.
Two and a half days with the people writing the playbook.
Insightful sessions, inspiring ideas, and meeting your peers — the skills and methods that take your organization to the next level.