Home //
An Anthropologist’s Guide to Engineering Cultures
Leadership builds a team. Culture builds a tribe.
PRESENTED BY
Robert Harris
Founder of Coded2Lead
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 90-minute session borrows the engineer's own mental model to do it. Culture decomposes into beliefs, behaviors, and artifacts - the abstract classes - and you only observe them through their implementations: the language a team speaks, the rituals and ceremonies it repeats, the experiences that bond it, and the artifacts and art it leaves behind. Robert walks through real examples from teams he has led, including a pull request dumpster-fire beacon, rubber duck onboarding kits, and the rake every new hire steps on once.
It also makes the case that culture was never built by the building. Open source tribes and the gaming guilds of twenty years ago mastered distributed collaboration long before anyone called it remote work, and their playbook still holds for co-located, hybrid, and fully remote teams alike.
Two warnings close the loop: why copying another company's culture produces a cargo cult, and why a culture behaves like a spoked wheel, where you tune the whole system one adjustment at a time.
Attendees will leave with:
- A working taxonomy for reading and shaping the culture they already have
- Concrete rituals, language, and artifacts to adapt to their own teams, wherever those teams sit
- A systems view of culture that explains why the obvious fix usually isn't
Whether you're a reluctant manager, a seasoned leader, or someone who has stepped on a rake in production, you'll leave with the tools to turn dysfunction into culture, and culture into a team that holds together when you're not in the room.
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.
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.
Would Your Team Still Follow You if You Weren’t Their Boss?
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.
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.