The Fundamental Reality
Here's something that seems obvious only after it's been stated: the most fundamental unit of any business is the relationship.
Until a business forms a relationship, it is not a business; it is an idea. Once that idea enters into a relationship with someone else, whether with a co-founder, a customer, an investor, an employee, etc., it has fundamentally changed states. When a business scales, what's really being scaled is its network of relationships. The strength and health of the business varies precisely with the strength and health of those relationships.
This means that the single most important capability for any organization is the ability to build and maintain healthy relationships, both internally and externally. We already know this about external relationships: the market for CRM systems is over $100 billion. We've industrialized the management of customer relationships.
But internal relationships? How well do leaders and teams relate to each other? How do organizations build and maintain the relational health that allows them to execute, retain talent, and navigate pressure? That's where C-FASTR comes in.
Why Measurement Matters
Many leaders believe they have a healthy culture. And they may be right. But even healthy cultures have room to grow, and the best leaders want to know specifically where.
Does your organization have strong practices for stopping collusion, but struggle with "Midwest Nice" or "Southern Nice" that keeps honest feedback from flowing? Is everyone trained in how to diagnose and repair trust when it's damaged? Is your team skilled at understanding other perspectives and finding win-win solutions swiftly? Are these capabilities improving or declining over time? Are they uniformly strong across the enterprise, or are there pockets where teams would benefit from focused, non-judgmental support?
Measurement creates precision. It allows you to see which specific relational capabilities are strong and which need attention. It moves culture conversations from vague feelings ("something's off") to concrete observations ("feedback is flowing well, but we're seeing patterns that suggest accountability needs attention"). It lets you track progress over time and demonstrate to boards, investors, and teams that the investment in culture is producing results.
C-FASTR provides that measurement. It identifies the six core areas where teams either build health or accumulate damage, and makes them visible, discussable, and actionable.
The Six Dimensions
This is the most dangerous dimension, and it's worth understanding clearly.
Imagine your All Hands or Town Hall meeting where the leadership team announces a new initiative. Heads nod. No one raises objections. The meeting ends. And then, usually within minutes, people are back at their desks, in Slack channels, in small clusters by the coffee machine, saying what they actually think. "Can you believe they're going forward with that?" "I didn't want to say anything, but…" "Between you and me, this is never going to work."
The meeting said yes. The hallway says no. And nothing that follows will make sense until you understand that gap.
That's collusion: having the real conversation somewhere other than where it belongs. It's the meeting after the meeting. It's talking about someone behind their back instead of to their face. It's building factions, recruiting allies for your perspective, and creating side channels that bypass the people who actually need to hear what you're thinking.
Now, processing is human. Venting to a trusted colleague after a frustrating meeting is normal. The question is what happens next. Do those concerns get raised where they can actually be addressed? Or do they fester, circulating through back-channels while the people who could do something about them never hear a word?
And if raising concerns directly doesn't feel safe, that's important information too. It points to a feedback problem that needs attention. But the answer is never to let collusion become the workaround. When real conversations go underground, trust becomes impossible, as people learn that what's said publicly isn't what people actually believe. Decisions get made but never truly implemented. People get excluded and never understand what they did wrong, or who they offended, or how.
Collusion is the dimension that prevents all the others from functioning. A team can have strong feedback skills, but if concerns travel through back-channels, those skills never get used. A team can value accountability, but if people are building factions instead of addressing issues directly, accountability becomes merely politics. And whenever collusion takes root in an organization, people in that organization inevitably ask the same question: "If Bob is saying this about Ted behind Ted's back, what is Bob saying about me behind mine?"
Feedback in this model is not the standard corporate definition. It's not the structured sit-down to compare Goals and Objectives against accomplishments for the quarter. In the C-FASTR model, feedback is far more extensive. We give each other feedback all the time: formally and informally, casually and explicitly. Staring at your phone when someone is talking to you is a kind of feedback. Ignoring or delaying an email is a form of feedback. We are giving feedback to and receiving feedback from each other constantly. Feedback is the workhorse of the C-FASTR model; there is no skill you will use more often.
Feedback can be defined as the capacity to exchange honest information about impact, performance, or behavior, and to do so in a way that strengthens rather than damages relationships.
Feedback has two categories: giving it and receiving it. Both sides are critical, but of the two, receiving it is the more important. This is because if a person is bad at receiving feedback, after a while no one will be willing to give it, which is a catastrophic outcome in a relationship.
Feedback is both a skill and a willingness. Many people want to give honest feedback but don't have the skill to deliver it in a way others can actually hear. Similarly, many people will say "I'm open to feedback" until it actually happens; after that, we often find ourselves defending, deflecting, or "what-about-ing" when that feedback arrives. Part of the skill of receiving feedback well is being able to receive feedback even when the giver is not especially good at giving it.
When a culture is doing well with feedback, the idea that "I can't give feedback to them; that's my boss!" becomes unthinkable. Healthy feedback flows in all directions: team member to leader, peer to peer, leader to team member. It's specific enough to be useful and delivered with enough care that the relationship can hold it.
Accountability is the practice of owning outcomes, naming what happened, and following through on commitments. In this model it is roughly interchangeable with Responsibility.
It is enormously difficult to be in a relationship with a person who never takes accountability for their words or actions. When a person is constantly deflecting accountability and expecting others to be the adults in the room, over time trust deteriorates and finger-pointing and CYA activities take root, instead of helping each other learn and improve.
Accountability also means owning the impact of your actions, as distinct from owning the intention. If I'm wearing boots and step on your foot, your foot is in pain. I didn't intend to cause you pain; but you are nevertheless in pain due to my action. My intention was not to cause pain, but the outcome was pain anyway. The learning that must take place involves me taking accountability for the fact that I stepped on your foot. This is not an opportunity to assign blame or shame; these habits often impede the ultimate goal of taking accountability, which is to learn to do better next time.
But here's what makes accountability actually work: it has to exist within a relationship that's heavy with trust. Accountability without trust becomes punishment; it becomes a "gotcha!" culture where people are afraid to take risks because mistakes will be used against them. But accountability in the context of a healthy relationship becomes growth. It becomes a culture where people own their outcomes because they trust that the goal is learning, growth, and improvement, not blame and judgement and "sidelining."
Sensitivity is by far the most difficult skill in the model. It is also the skill that bonds people in healthy relationships faster and more deeply than any other.
"Sensitivity" is the "You get me. You really get me" skill. It's the ability to understand another human being's perspective thoroughly, and to use that understanding to create win-win scenarios. You may not agree with that perspective; but you take the time and trouble to, with genuine curiosity, understand another human being. People generally experience this effort with tremendous appreciation.
Contrary to popular opinion, sensitivity is not fragility or walking on eggshells. It's closer to: just paying attention; noticing when something landed differently than intended; and picking up on shifts in energy or engagement.
Imagine this scenario: a production team has a shipping deadline to meet, but the raw materials they need are "stuck in QA." They're furious with the QA team, considering them lazy slackers who don't understand production pressures. Meanwhile, the QA team is working 20-hour days. The shipment arrived two weeks late, and their tests require seven days to complete. Their view: "If we release these materials and something's wrong, the company gets a massive black eye. Why would you even want us to rush?"
The ability to understand what other human beings are going through is a necessary prerequisite to creating mutually beneficial, win-win solutions. Sensitivity, in the C-FASTR model, is understanding those points of view thoroughly, and then using that knowledge to rapidly create win-win solutions.
Trust is the confidence that others will act with integrity, follow through on commitments, and prioritize the relationship even when it's inconvenient.
But here's what makes trust more complex than it first appears: it's actually three different things operating at once.
Trust as outcome. This is what most people mean when they say "we have a trust problem." Trust in this sense is what accumulates when the other dimensions of C-FASTR are functioning well. You trust someone because they've given you honest feedback even when it was uncomfortable. You trust them because when things went wrong, they owned their part without deflecting. You trust them because they took the time to understand your perspective before pushing their own agenda.
Trust as outcome can't be built by working on trust directly. This is why trust falls and team-building exercises so often fail to produce lasting change. They're trying to create trust as a standalone achievement, when trust is actually the reward for getting the other relational dimensions right.
Being trustworthy. This is about your own behavior: your reliability, your integrity, your follow-through. Do you do what you say you'll do? Do you act consistently whether someone is watching or not? Trustworthiness has several components: competence (can you actually deliver?), integrity (do your actions match your stated values?), and benevolence (do people believe you genuinely have their interests at heart?).
Willingness to extend trust. This is the dimension most people overlook, and it may be the most powerful. Some people default to suspicion. They wait for others to prove themselves before extending any vulnerability. But trust often requires someone to go first. Research on "trust propensity" shows that people vary significantly in their willingness to extend trust to others. Here's the practical insight: one of the fastest ways to build trust with someone is to extend trust to them first.
The asymmetry of trust. Trust builds slowly and breaks quickly. A pattern of honesty, follow-through, and care accumulates over months and years. A single significant betrayal can undo it in an afternoon. This asymmetry means that maintaining trust requires ongoing attention, not a one-time achievement. Trust is not a box to check. It's a garden to tend.
Relationship focus is the conscious attention to how people are relating to each other, not just what they're producing.
This might sound obvious. It's remarkably rare in practice.
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.
The research is clear. Jody Hoffer Gittell's work on relational coordination, spanning 233 studies across 36 countries, shows that relationships characterized by shared goals, shared knowledge, and mutual respect are what enable complex, interdependent work to succeed. Rob Cross and Wayne Baker's research on relational energy found that people who leave others feeling energized after interactions get better performance evaluations, advance more rapidly, and spark more innovation. Jane Dutton's work on high-quality connections found that even brief, momentary interactions affect cognition, health, and sense of belonging. Decades of research on leader-member exchange (LMX) confirms that the quality of the relationship between a leader and each team member predicts that person's performance, satisfaction, commitment, and likelihood of staying.
What does relationship focus look like in practice? It's the leader who, after a tense meeting, checks in privately: "How are you doing after that? I noticed you seemed frustrated." It's the team that builds in time to talk about how they're working together, not just what they're working on. It's the colleague who says "I think there's something between us that we should clear up" instead of letting it fester.
In the C-FASTR model, relationship focus is the dimension that makes all the others possible. 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 the foundation. Everything else is built on top of it.
How the Dimensions Work Together
These six dimensions form an ecosystem in which each aspect supports the others, and weakness in one area affects all the rest:
Feedback requires sensitivity; without it, feedback lands as attack rather than care. Accountability requires trust; without it, it becomes punishment rather than growth. Trust requires the absence of collusion, as you can't trust people who say one thing to your face and another behind your back. And all five dimensions require relationship focus: a commitment to paying attention to the relational dynamics that make everything else possible.
The good news is that strength in one area supports the others. Teams that get good at feedback become teams where concerns don't go underground. Teams where concerns don't go underground become teams with higher trust. Teams with higher trust become teams where accountability feels fair rather than punitive.
The Development of the Framework
C-FASTR emerged from over 25 years of work in organizational development, technology delivery, and culture transformation. The organizations have ranged from Fortune 500 companies (including The Coca-Cola Company) to venture-backed startups to mission-driven nonprofits, across functions including tech, learning and development, and cross-functional team effectiveness.
The consistent observation across all of these contexts: when organizations struggle, the root cause is almost always relational. Feuding leaders. Cross-functional friction. Culture that strains as the company scales. Communication that stops flowing. Trust that erodes. And underneath all of these: patterns of collusion, feedback avoidance, and relationship neglect that went unaddressed until they became crises.
The framework was developed to provide precision where general diagnosis wasn't enough. When a leader says "we have a trust problem," that's usually accurate, but it's often not actionable. C-FASTR provides the next level of specificity: which relational dimensions are contributing to the trust problem, and what specific capabilities need to be strengthened to address it.
The "C" comes first because collusion is consistently the most predictive dimension. Teams that allow the real conversations to happen somewhere other than where they belong eventually struggle in all five other areas. Stopping collusion (i.e., committing to having direct conversations rather than back-channel ones) is often the single highest-leverage intervention available.
What Makes This Approach Resilient
One question worth addressing: who would resist an initiative focused on building healthier workplace relationships?
In practice, very few people do. The framework strives to be relentlessly humane by focusing on helping people work together more effectively, treating each other well, and diagnosing when the working relationship seems to be suffering in large ways or small. It doesn't blame individuals; it looks at patterns and capabilities. It doesn't demand perfection; it asks for attention and effort. It doesn't create winners and losers; it helps everyone get better together.
The organizations that adopt C-FASTR tend to find that it gives language to things people already felt but couldn't articulate. It makes visible the dynamics that were affecting everyone but that no one had a way to discuss. And it provides a path forward that feels achievable: not "become different people," but "build these specific skills together."
Healthy relationships are good for people and good for business. It's a rare organizational initiative that serves both without tension. C-FASTR is one of them.