Home //
PRESENTED BY
Robert Harris
Founder of Coded2Lead
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.
In this session, a software engineering leader with formal training in psychology and
anthropology examines why remote teams so often struggle with silence, disengagement, and false alignment - and why most culture initiatives fail to address the real problem.
Using cross-cultural comparison, this talk contrasts engineering organizations with digital communities that have thrived online for decades, surfacing what those cultures get right about feedback, trust, and informal learning.
The core insight is simple but uncomfortable: distance is not the enemy of culture,
poorly designed environments are.
Rather than focusing on tools, mandates, or performative connection, this session
reframes culture as an environment shaped by observable behavior, especially
leadership behavior. Attendees will explore how meetings, async communication, and
everyday leadership moments become the new hallways - for better or worse - and how
teams silently adapt when those spaces fail them.
Participants will leave with:
• A practical lens for diagnosing signal loss in distributed teams
• Clear indicators that silence is masking risk, not agreement
• Design principles for creating “digital hallways” that allow trust, community, and
psychological safety to emerge naturally
• A deeper understanding of how leadership behavior trains culture - whether
intentionally or not
This session is grounded in real-world leadership experience, systems thinking, and
comparative cultural analysis, and is designed for engineering leaders who want to build resilient, high-trust teams in remote and hybrid environments without sacrificing
performance.
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.
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.