Customer relationships get CRMs. Employee relationships, which drive performance, innovation, and caring for those customer relationships, get... nothing. C-FASTR™ addresses that. Employee relationship quality becomes visible, measurable, and scalable.
Engagement surveys tell you how people feel. Exit interviews tell you why they left. Neither tells you why the team can't execute, or what to do about it.
C-FASTR measures six core capabilities that reveal how well your teams are:
C-FASTR helps build Relationship-Smart Cultures™. That means everyone who enters the culture gradually becomes an expert relationship diagnostician: able to see what's broken and how to address it swiftly, skillfully, and thoroughly. Teams gain the tools to identify "people issues," the cultural permission to speak up, and the shared language to diagnose and repair problems internally.
Read the full framework reference → Research, citations, and the complete intellectual foundation.
The silent agreements that let problems fester, and the conversations that happen behind your back.
Collusion is the most dangerous dimension because it's invisible until it's catastrophic.
It shows up two ways. First, the passive form: people tacitly agree to avoid difficult conversations, let underperformance slide, or pretend problems don't exist to preserve false harmony.
But the active form is worse. It's the meeting after the meeting. It's talking about Ted to everyone except Ted. It's building factions, recruiting destructive cliques, venting to colleagues with no intention of addressing the issue with the person who needs to hear it. The honest conversation is happening, it's just not where it belongs.
This is what makes collusion feel like betrayal. Because it is.
And here's what it does to a team: once people realize the back-channels exist, they start asking the only logical question: "If Bob is saying this about Ted behind Ted's back, what is Bob saying about me behind mine?"
That question poisons everything. Trust becomes impossible when what's said publicly isn't what people actually believe. Decisions get made but never truly implemented. People get excluded and never understand why.
High-collusion environments often feel peaceful on the surface. Underneath, resentment builds, problems compound, and the culture quietly rots. By the time collusion becomes visible, significant damage has already occurred.
Of the six dimensions, Collusion is the one that quietly destroys teams. It's comfortable in the moment and catastrophic over time. Most culture interventions fail because they don't surface collusion; they work around it. C-FASTR makes collusion visible before it compounds into something worse.
The continuous stream of signals we send each other about whether we're paying attention, and how we're managing this interaction.
Feedback in C-FASTR is not the annual review. It's not the structured sit-down. It's everything we signal to each other, constantly: formally and informally, casually and explicitly. Looking at your phone while someone is talking to you is feedback. Delayed email responses are feedback. The tone you take in a meeting is feedback. We give and receive feedback thousands of times a day.
Feedback has two sides: giving and receiving. Both matter, but receiving is harder and more important. Because if you're bad at receiving feedback, eventually nobody gives it, which means you're flying blind and have no real mechanism for improvement or growth.
In the C-FASTR model, feedback covers such questions as: Can I tell you your work needs improvement in a way you can actually hear? Can you hear it without getting defensive? Can you tell me my delivery was terrible, and can I hear that without telling you to stop being so sensitive? This is the skill of feedback: how we talk to each other, how we listen, how we make it safe to tell each other the truth.
The willingness to own outcomes and hold each other to commitments.
We know the basics of accountability: clarity; learning; people knowing what they're responsible for; following through on commitments. In a relationship-smart culture, this goes deeper: owning the impact of your actions, not just the intention. "I didn't mean to" doesn't undo the harm, it just explains how it happened. The learning begins with owning what actually occurred without blame, fingerpointing, defending, or attacking. In a relationship-smart culture, effective accountability requires trust as a foundation. Accountability without trust becomes punishment, a "gotcha!" culture where no one wants to own up to anything because it could be career- or relationship-shortening.
The "You get me. You really get me" skill.
Sensitivity is the most difficult capability in the model. It's also the one that bonds people in healthy relationships faster and more deeply than any other.
Contrary to popular opinion, sensitivity is not fragility or walking on eggshells. It's the ability to understand another human being's perspective thoroughly, and to use that understanding to create win-win solutions. You may not agree with that perspective, but you take the time to genuinely understand what someone else is experiencing.
Consider: a production team is furious at QA for holding up their materials. "We can't sell product we haven't made!" Meanwhile, QA is working 20-hour days running tests that take seven days to complete. Their view: "If we release bad materials, the company gets a massive black eye. Why would you even want us to rush?" Both teams are right. Both teams think the other doesn't understand. The ability to understand what the other is going through is the prerequisite to finding solutions that work for everyone.
People want to be understood even more than they want to be agreed with. When someone tries to understand your perspective, genuinely and humbly, even if they do not agree or endorse it, something shifts in the relationship in a profoundly positive direction: conflicts resolve faster, and the solutions that emerge actually work for everyone.
The foundation everything else rests on, and the outcome you can't build directly.
Trust is actually three different things operating at once.
Trust as outcome. This is what most people mean when they say "we have a trust problem." But here's the key insight: you can't fix trust by working on trust directly. Trust is what accumulates when the other dimensions of C-FASTR are working well. You trust someone because they give you honest feedback, own their impact, and understand your perspective. You don't fix trust. You fix the relationship. Trust follows.
Being trustworthy. This is within your control. It has three components: Competence: can you actually deliver on your commitments? Integrity: do your actions match your stated values? Benevolence: do people believe you genuinely have their interests at heart? You can behave with integrity regardless of whether others recognize it. The behavior comes first; trust is the return.
Willingness to extend trust. This is the dimension most people overlook, and it may be the most powerful. Trust often requires someone to go first. If everyone waits for proof before extending trust, no one ever starts. One of the fastest ways to build trust is to extend it before it's "earned." Most people feel the weight of that trust: they don't want to let you down. Your extension of trust becomes a self-fulfilling prophecy.
One more thing: trust builds slowly and breaks quickly. A pattern of follow-through accumulates over months. A single betrayal can undo it in an afternoon, which is why relationship-smart cultures teach people how to repair trust when it breaks: how to talk about what happened and rebuild those bonds. Trust is not a box to check. It's a garden to tend.
The conscious attention to how people are relating to each other, not just what they're producing.
Most organizations are structured entirely around outputs: projects, deliverables, metrics, results. The work gets all the attention. The relationships that make the work possible are assumed to take care of themselves.
They don't.
Consider: two colleagues are tense with each other. Meetings with both of them feel strained. There's a coolness that wasn't there before. What happens next? Usually nothing. Everyone pretends not to notice. People route around it, avoiding situations where the two need to collaborate. The friction quietly taxes the team's effectiveness, but since no one names it, no one addresses it.
In a relationship-focused culture, someone says something. Not an accusation, just an observation: "I've noticed some strain between you two lately. Is there something going on that would be worth talking through?" The willingness to name what's happening, before it calcifies into resentment, before workarounds become permanent, is relationship focus in action.
The small things matter more than most people realize. Remembering what someone mentioned last week and asking about it. Being fully present when someone comes to talk to you. Helping someone succeed at their task because you're invested in them, not because you have to. These aren't nice-to-haves. They're the connective tissue that holds teams together under pressure.
Here's why this dimension is foundational: you won't invest in giving someone difficult feedback if you don't care about the relationship. You won't take accountability for your impact if the relationship doesn't matter to you. You won't bother understanding someone else's perspective if you're not invested in finding a way forward together. Relationship focus is what makes all the other dimensions possible.
"You don't fix trust. You fix the relationship. Trust follows."
"Relationships are infrastructure, not soft skills."
"Culture is a garden, not a machine. You tend it, you don't fix it."
"Love builds better fences than fear."
Where decisions stick. Where problems surface before they become crises. Where people grow, and stay. Let's talk about what that looks like for your organization.
Book a Conversation