C.A.M.P. Framework: Building Connection in Engineering Teams

Processes don’t ship great products. People do, and they do it when they trust each other. In my experience leading engineering teams, nothing drives performance like strong team connection.

In my diverse career, the highest performing teams weren’t the ones with perfect processes. They were the ones built on trust by people who believed in each other and what they were building.

I’ve worked at a lot of different companies, big and small. I’ve seen a lot of different leaders and I’ve seen a lot of different ways of operating those businesses. Where I’ve seen the most consistent success is when I’m excited about the product I’m building and who I’m building it with. Some of those people I happily keep in touch with today.

C.A.M.P. stands for Connection, Autonomy, Measurement, and Purpose, four pillars of happy, high performing teams.

Connection is the first and most foundational pillar of the C.A.M.P. framework. It’s often the hardest to build, but it’s also the most resilient. Teams have shipped complex products, responded to major incidents, and overcome impossible deadlines not because their processes were flawless, but because they trusted one another.

How often have you thought:

“I could leave this job… but I really like working with this team.”

That’s the power of connection.

What Do We Mean by “Connection”?

In engineering teams, connection shows up in how we:

• Collaborate on design reviews

• Debate solutions without defensiveness

• Share wins (and own failures) openly

• Check in on each other during high-pressure releases

Connection also refers to how individuals relate to the company’s purpose, its mission, values, and leadership. It answers two questions:

• Do I feel like I belong on this team?

• Do I believe in where we’re going?

How Do You Know If a Team Is Connected?

You don’t need a survey, you’ll see it in behavior:

• Healthy tension during technical debates

• Laughter during stand-ups

• Openness during retros

• Support during outages

These aren’t just warm fuzzies. They’re signs of psychological safety, the strongest predictor of high-performing engineering teams, as proven by Google’s Project Aristotle.

“how do you get your team laughing so much?”

I’ve managed teams where other managers would approach me and ask, “how do you get your team laughing so much?” That’s how I knew the team was connected and thriving. People on the team were promoted shortly after.

How to Build Connection

✅ At the Individual Level

It’s easy to think culture is a manager’s job. But every engineer, junior or senior, can foster connection. Everyone is actually a leader in their own way, as one powerful TED Talk argues: everyone leads, regardless of title. You can start building a more inclusive environment with belonging cues: small verbal and non-verbal signals that say, “You’re part of this group.”

Try this:

• Ask,“What’s your take?”during a code review or design meeting.

• Share something about yourself that’s not work-related like what you’re reading, watching, or struggling with.

These gestures create space for people to bring their authentic selves to work. And when people feel seen, they engage more deeply.

“The authentic self is the core of a person, which contains leadership qualities such as compassion, perspective, curiosity, and confidence.”
— Richard Schwartz

✅ At the Manager Level

As an engineering manager, you set the tone intentionally or not.

To build a connected, psychologically safe team, model the following:

• Self-Awareness
  Your words and actions set precedent. If you talk over people or never admit fault, others will follow.

• Vulnerability
  Admit when you’re wrong. Share what’s hard. It signals that learning and failing are safe here.

• Empathy
  Consider how a new process, a weekend deploy, or a poor sprint outcome mightfeelto someone else.

• Compassion
  Recognize when someone is struggling and act. Not because it’s your job, but because it’s the right thing to do.

Also, don’t overlook the value ofintentional team rituals— especially in remote environments:

• Virtual coffee chats

• “Demo Fridays”

• In-person offsites, when possible

The best teamsdon’t just code together, they grow together.

Assessing Connection in the Team

Add in a few questions to your one on ones to gauge the team connection health.

Try these:

• Who have you worked closely with this week?

• Do you think anyone could use some help?

• Who do you think has really stood out this week?

Connection to the Company

Building connections within the team is half the story. The other half is connecting to something bigger: the company itself.

Most companies talk about values; but many fail to live them. As a manager, your job is to translate those big ideas into everyday relevance.

Here’s how:

• Show how a feature aligns with the company’s mission.

• Use values as a guide during tough trade-offs.

• Repeat the “why” behind decisions, not once, but often.

People don’t lose faith in companies because of hard choices. They lose faith when those choices feel disconnected from values.

Breaking your values as a company will force employees to compare your actions against their personal values.

And remember: the average engineer probably doesn’t care how much profit the company makes unless they understand what that profit enables. Is the company going somewhere meaningful?

For most engineers, company success doesn’t meaningfully change their day-to-day. Even with profit-sharing, most engineers don’t see meaningful returns for the extra hours they work. They need to understand what that success enables.

A great analogy comes from Simon Sinek, comparing a company to being a car and you’re going on a road trip. The money the company makes is the gas going into the tank. The company needs money, of course, but that’s not why you join a company. You join a company because it’s doing something compelling. The car is going someplace exciting!

Assessing Connection to the Company

Use these questions to gauge your team’s connection to the company:

• What really stood out to you about our last all hands meeting?

• In your words, what would you say the company’s most important goal is?

• What’s your take on the recent major decision regarding …? How do you feel about it?

In Summary

Connection fuels performance. It's how engineering teams navigate conflict, build trust, and solve hard problems together.

To build it:

• As an individual: Use belonging cues and bring your whole self to work.

• As a manager: Model vulnerability, empathy, and psychological safety. Create space for human moments.

• At the company level: Keep the mission, vision, and values visible, relevant, and real.

A connected team doesn’t just deliver code, it delivers culture, trust, and resilience.