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.
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.
This 60-minute session approaches engineering culture the way an anthropologist approaches any human culture: by looking at the beliefs people share, the behaviors that bind them together, and the artifacts they create along the way.
Robert walks through real examples from teams he has led to show how culture emerges in practice - from unconventional job titles and team language, to rituals around technical debt and broken builds, to retrospectives, shared experiences, personalized rubber ducks, onboarding artifacts, and the art a team creates about itself.
Along the way, he'll show why healthy culture can't simply be declared in a mission statement. The strongest cultures emerge from the people already there. Leaders can shape them, reinforce them, and give them room to grow - but they can't manufacture them from a template.
Attendees will leave with:
Whether you're a reluctant manager, a seasoned leader, or someone who has stepped on a rake in production, you'll leave ready to put on your anthropologist's hat and build the kind of engineering culture you'd actually want to be a member of.
Most advice about difficult conversations starts too late. It assumes you already know which conversation you need to have.
But what if you're debugging the wrong problem?
Robert Harris draws on 25 years of engineering leadership - and his training in psychology and anthropology - to examine the human systems underneath the conversations leaders avoid, mishandle, or never realize they need to have. Using real stories from his career, from a production outage to a board asking, “How many developers do we need to fire?“, he'll show why the conversation that looks obvious on the surface is often very different from the real one underneath.
Because before you can have the difficult conversation, you have to find it.
This 60-minute session borrows the engineer's own mental model: debugging.
Humans won't show you their internal state, call stack, or debug log, so engineering leaders have to work from the signals the system actually gives them. Robert introduces three forces operating underneath difficult conversations - power, risk, and reward - and three signals that appear when those forces get out of balance: silence, conflict avoidance, and withdrawal.
Then he puts the model to work.
Through real conversations from his career, attendees will debug what happens when a leader accidentally teaches a team to stay silent, when a promotion changes relationships with former peers, when a boss makes uncertainty dangerous during a production incident, and when a valued employee has already decided to leave - whether either person is ready to admit it yet.
Each conversation becomes a debugging session: inspect the inputs, read the hidden signals, identify the strongest forces, and test the assumptions behind the apparent problem. Sometimes the assertion passes. Often it fails. And sometimes the first difficult conversation you need to have is with yourself.
Attendees will leave with:
Whether the conversation is with your team, your boss, or yourself, the goal isn't to become fearless about conflict. It's to stop solving the wrong problem because you never found the real conversation.
Remote and hybrid teams don’t lose culture when they lose the office. They lose many of the accidental mechanisms that helped culture form: hallway encounters, informal learning, weak ties, shared jokes, spontaneous collaboration, and everyday social connection.
But none of those mechanisms actually require a building.
Drawing on anthropology, engineering leadership, and years of leading distributed teams, this session examines what thriving online communities already know about building culture without physical proximity - and how engineering leaders can intentionally design the digital spaces where trust, identity, learning, and community can grow.
In this session, a software engineering leader with formal training in psychology and anthropology challenges one of the most persistent assumptions about remote work: that meaningful culture requires physical proximity.
The needs behind that assumption are real. Teams need informal interaction, mentorship, shared identity, spontaneous collaboration, belonging, and access to information. But offices satisfy many of those needs accidentally - through hallways, overheard conversations, shared spaces, and proximity.
Remote and hybrid teams have to satisfy them by design.
Using seven common return-to-office arguments as a starting point, this session separates the human need from the physical mechanism traditionally used to meet it. From hallway conversations and brainstorming to onboarding, coordination, and belonging, attendees will explore how distributed teams can intentionally reproduce - and sometimes improve - the functions we once relied on the office to provide.
Then we'll borrow one of anthropology's oldest tools: cross-cultural comparison.
Open source communities and online gaming cultures have built strong distributed identities for decades, often among people who have never met in person. Their success reveals practical lessons about weak ties, shared language, rituals, symbols, informal spaces, and cultural artifacts.
Finally, we'll bring those lessons back to engineering teams through real examples from remote organizations Robert's led: digital watercoolers, team totems, custom dialects and emojis, collaborative art, onboarding artifacts, recognition rituals, and the deliberately designed spaces where culture can take root.
The core idea is simple:
The office gave us cultural infrastructure by accident. Remote teams have to build it on purpose.
Participants will leave with:
• A framework for separating the human needs of a team from the physical mechanisms traditionally used to meet them
• Practical ways to create low-friction digital spaces for spontaneous interaction and weak-tie formation
• Design principles for building shared identity through language, rituals, humor, art, and artifacts
• Concrete examples they can adapt to strengthen culture on remote and hybrid engineering teams
• A new diagnostic question: if the building disappeared tomorrow, what about your culture would still be there next month?
This session is grounded in anthropology, systems thinking, and more than two decades of engineering leadership, and is designed for leaders who want remote and hybrid teams to do more than function - they want them to feel like communities people genuinely want to belong to.
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.
You will learn:
This isn't a talk about tools, frameworks, or performance management templates. It's a story-driven look at the human system you're an inextricable part of - and most of the stories are my own mistakes, drawn from 25 years in engineering leadership and a background in anthropology and psychology.
You will leave with:
If leadership suddenly feels harder than engineering ever did, that's not a personal failure. It's a systems mismatch - one you are well equipped to fix.
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.
Over five modules delivered in a full-day workshop, participants learn to see the human system they're already inside, recognize what their daily inputs train into it, and read the signals it sends back. From there, they assemble a Leadership OS: the integrated stack that determines how a leader shows up under pressure, and the runtime practice that keeps the defaults from taking over. The day closes with applications - the OS running against real situations every engineering leader faces: difficult conversations, deadlocked teams, feedback gone wrong, terminations, and power gradients that turn against the team.
The content draws on twenty-five years of engineering leadership from a former anthropologist, gained across startups, consultancies, and global organizations, told through first-person stories of failure modes and recoveries. Frameworks come from psychology, anthropology, systems theory, and philosophy - translated into vocabulary engineers can use.
Participants leave with diagnostic questions, pre-loaded responses, and a working operating system for leading humans the way they already lead systems: with awareness, intention, and design.
When the pressure is on, your team stops listening and starts watching. What they see is your operating system under load. Human hardware runs emotion before logic finishes loading, so under stress even smart, decent leaders fall back on factory defaults: ego, fear, fight, flight, freeze. Add AI-accelerated output that moves faster than anyone can fully audit, and you get asked for answers you don't have yet, at the moment your defaults are loudest. Some days that's exhilarating. Other days you wonder whether you're still the right person to ask.
In this two part, co-taught session, Robert Harris and Hunter Milligan pair a systems view of leadership with practical skills for the moment itself. Through stories of leaders under increasing load, from a well-meant intervention that backfired to a boss who lost it in front of the team, you'll learn a simple loop for choosing your response (signal, default, interrupt, principle, response) and the core leadership principles worth deciding before you need them. Then you'll practice: a breathing reset that settles your body, a way to stop spinning on a problem you can't solve yet, and a method for getting through the dread of a hard conversation. You'll work real scenarios with the people around you and leave with something steadier than certainty: one honest sentence for when the answer isn't there yet, and the ability to stay clear, consistent, and credible while it arrives.
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:
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.