Build High Performing Team Accountability with the CROP Trust Model

Most leaders think they’re evaluating their team correctly. They’re not. They’re screening for one dimension — technical competence — and missing the three that actually determine whether a person will execute, follow through, and make sound decisions when no one is watching.

Dr. David Farrar, Managing Partner at Koliso, spent 6 years earning his formal psychology credentials, 5 years in military service where he was trained in structured after-action reviews, and 4 years as Global Organization Effectiveness Manager at the world’s largest private company before launching his consulting practice. His work sits at the intersection of organizational psychology and practical leadership execution — and his core argument is blunt: the soft stuff is the hard stuff.

As Farrar puts it: “The soft stuff is the hard stuff. That’s how you get leverage and you get results by surrounding yourself with a team of people who can do really well in your business.” For founders and GTM leaders trying to build high performing team accountability without adding headcount, this conversation is a masterclass in what actually drives execution.

Key Takeaways

To build high performing team accountability, leaders must evaluate trustworthiness across four dimensions — not just technical skill. The CROP model (Competent, Reliable, Open, Principled) gives leaders a repeatable framework to assess both current team members and new hires. Psychological safety only drives performance when paired with explicit purpose. External assessment is essential because internal teams cannot safely deliver candid feedback upward. After-action reviews generate both retention and referrals simultaneously.

• Competence alone disqualifies no one — but it qualifies no one for leadership either. Selecting project leads based solely on technical skill is the most common and costly delegation mistake founders make.
• Reliability and openness are the two dimensions most likely to fail under growth pressure. If someone won’t follow through on commitments or hides problems, scaling accelerates the damage.
• Psychological safety without purpose creates permissiveness, not performance. You must define what the safety is in service of — risk-taking, invention, honest feedback — or it becomes a license to underperform.
• Leader participation is binary: when leaders exempt themselves from psychological safety initiatives, the program fails. Every time.
• External assessment is non-negotiable because no one inside the organization — regardless of stated safety — will tell a senior leader they’re not doing what they claim to be doing.
• After-action reviews (AARs) serve two functions simultaneously: they improve client satisfaction and generate qualified referral introductions without the social awkwardness of direct asks.
• Behavioral interview questions that don’t telegraph the right answer are the most reliable tool for assessing the Principled dimension before hiring — and the specific prompts Farrar uses are reproducible by any hiring manager today.

Deep Dive

Why Technical Competence Is the Wrong Filter for Project Leadership

Promoting or assigning the most technically skilled person to lead a project is the default decision at most growing companies — and it’s wrong most of the time. The skills that make someone an expert practitioner are categorically different from the skills that make someone a reliable, accountable, transparent project leader. When founders and VPs use competence as their sole selection criterion, they create a structural accountability gap that compounds as the company scales.

“When you ask leaders how they choose the people that they put in charge of projects or whatever, they often only rely on the first element of trustworthiness, which is is the person competent. And technical projects, like you say, a lot of times the person who heads it up is the most technically competent, but that’s not necessarily the person that you want to have leading the project.”

The consequences aren’t theoretical. A technically strong individual contributor who lacks reliability will miss deadlines quietly. One who lacks openness will hide problems until they become crises. One who lacks principles will cut corners on decisions made outside your line of sight. The CROP framework — Farrar’s four-dimension trust model — is built specifically to close this gap.

What Is the CROP Model and How Does It Build Team Accountability?

The CROP model is a four-part framework for evaluating trustworthiness in team members and leaders. It covers Competence, Reliability, Openness, and Principled behavior. Each dimension is equally critical — missing even one creates a specific, predictable failure mode in delegation, accountability, or execution. Leaders use CROP both to diagnose gaps in existing team members and to structure behavioral interviews for new hires.

The four dimensions in practice:

Competent — Do they have the technical or functional skills the role actually demands? This is necessary but not sufficient. Farrar’s point is not that competence doesn’t matter — it’s that stopping here is where most team accountability structures break down.

Reliable — Will they follow through on what they commit to? Reliability is observable over time, but in a hiring context it must be probed through behavioral questions about past commitments, missed deadlines, and how they communicated when things went off track.

Open — Are they transparent about their work, problems, and receptive to feedback and course correction? This dimension determines whether you’ll hear about problems early enough to fix them — or only after they’ve compounded.

Principled — When you cannot directly observe their work, will they make the right decisions anyway?

“When you can’t check in with them and you can’t see what they’re doing, are they going to do the right thing anyway?”

This last dimension — Principled — is the hardest to assess in a hiring context and the most dangerous to assume. Farrar’s Behavioral Interview Framework for Assessing Principles addresses it directly. The method relies on neutral questions that don’t telegraph the socially desirable answer, then extracts stories that reveal actual decision-making patterns under pressure.

The three prompts: “Tell me about the last time you had to make a difficult decision.” “Tell me about a decision you made that was different to what people expected.” “Tell me about a time when it was hard to make a decision because other people didn’t agree with you.”

The follow-up work is to listen for the logic and values embedded in each story, then pattern-match across answers: Does this person cut corners? Ignore colleagues? Cave when pressed? The stories will tell you before the hire.

How Do You Create Psychological Safety While Maintaining Accountability?

Psychological safety without an explicit purpose degrades into permissiveness. To build high performing team accountability, psychological safety must be paired with clarity about what the safety enables — specific expectations around risk-taking, transparency, and innovation. Without this pairing, teams interpret safety as protection from consequences rather than as the foundation for high-stakes performance.

Farrar is explicit about this in what he calls the Psychological Safety with Purpose Pairing model:

“You have to give them psychological safety. And then you have to show that safety in the service of what… If you feel psychologically safe, I’ve given you an opportunity to do what? Well, you ask people to take risks. You ask people to be inventive.”

The implementation sequence matters. First, normalize failure as a learning mechanism — Farrar’s after-action review methodology handles this directly by making retrospection a structural habit rather than a crisis response. Second, define explicitly what safety enables: in this environment, people are expected to experiment, flag problems early, and challenge assumptions. Third, establish clear performance feedback loops so that risk-taking is bounded and intentional, not arbitrary.

The failure mode is predictable: leaders who mandate psychological safety training without defining its purpose create environments where people feel protected from accountability rather than equipped for higher performance. Safety without direction creates permissiveness. Purpose without safety creates fear. Both are lethal to team performance at scale.

Why Leader Participation Determines Whether Accountability Programs Succeed or Fail

Psychological safety and accountability initiatives are only as strong as the most senior leader who actively participates in them. When leaders exempt themselves — or even passively underengage — they signal to the entire organization that the initiative is for others, not a cultural standard. This single factor predicts program failure more reliably than any other variable.

“The worst consultant programs I’ve ever worked on are ones where it’s somebody underneath the leadership team who says, this is a thing we need to do training on. And the leader says, but I don’t need to attend. Those things almost never work.”

This is why Farrar’s Leadership Assessment and Mirror Model begins every engagement with an external assessment of leadership behavior — before any team-level work. The logic is sequential: you cannot install accountability structures in a team whose leadership hasn’t first been assessed, confronted with gaps, and committed to behavioral change.

The assessment process reflects findings back to leadership in specific, non-accusatory terms, then evaluates their response. Are they receptive and willing to implement changes? Or do they become defensive? The answer to that question determines whether the engagement proceeds — or whether Farrar resets the scope or exits early. Proceeding with a defensive leadership team wastes resources and produces no sustainable change.

This is also why external assessment is structurally necessary, not just preferable:

“At least in my experience, that’s got to be somebody external. Nobody in the company, especially if there isn’t psychological safety, can tell you like, ‘Hey, you don’t do what you say you’re…’ No, no one’s going to say that to you. So, you need somebody that you’ve hired to be able to tell you the truth, basically.”

The internal team assessment problem is self-reinforcing: the absence of psychological safety prevents candid upward feedback, which means leaders never receive the information they need to create psychological safety. External assessment breaks the loop.

How After-Action Reviews Generate Referrals Without Social Awkwardness

The After-Action Review (AAR) methodology — borrowed directly from military debrief practice — is a structured retrospective that serves two simultaneous functions: it improves client satisfaction by surfacing improvement opportunities, and it creates natural conditions for referral introductions without the social pressure of direct asks.

“Every after-action review, you psychologically, and even in the military, you start with what went well that we just did, that we should keep doing. And people will tell you, you know, this was great because of X, Y, and Z. And you go, ‘Great. Where were there other opportunities to do things differently and better?’ Sometimes that leads to your client offering you more work, cuz here’s an opportunity they’ve seen in their business. And sometimes that process leads them to talking about somebody else they know who could benefit from the same thing.”

The sequence is critical. Starting with what went well is not a courtesy — it’s the psychological setup that makes clients articulate your value in their own words, creating social proof they already believe. Moving to improvement opportunities surfaces either additional scope or adjacent problems in the client’s network.

The referral question that follows — “Do you know anyone else who’s facing issues like this?” — lands without friction because it’s positioned as peer problem-solving rather than a sales ask. Farrar’s framing is precise:

“If you ask a client for a referral, it’s tough on them. It’s socially awkward. But if you make it a regular habit to talk to all of your clients about what went well, what could be different or better, then clients will tell you what went well, and you know, where the opportunities are. And then you ask them, ‘Do you know anyone else who’s got issues like this?’ And they’ll often just tell you.”

For GTM leaders building a word-of-mouth growth strategy, this is the most durable pipeline mechanism available. It scales with client satisfaction, costs nothing to run, and produces warm introductions that close at dramatically higher rates than outbound.

Why Complacent Leaders Cannot Survive Organizational Change

Senior leaders who lack accurate self-awareness about their behavior, impact, and alignment with stated values are structurally unprepared for organizational change. Complacency is not a personality flaw — it’s an information problem. When leaders stop receiving candid feedback, their internal model of their own leadership diverges from reality. When change arrives, that gap becomes a liability.

“Senior leaders being complacent about what they do is not going to help them when change comes along. And they need to have something like a mirror to look into to make some changes.”

Farrar’s prescription is direct: “Find a mirror. Maybe it’s a trusted adviser, maybe it’s a consultant. Find something objective and take a good hard look at yourself.” The mirror is not optional — it’s the foundation for every other change initiative. Leaders who skip this step and proceed directly to team-level interventions are building on an unexamined foundation.

For founders and GTM leaders at growth-stage companies, this mirrors the broader team accountability structure challenge: leadership self-awareness is a prerequisite for team performance, not a downstream outcome of it. The sequence runs from leader assessment → leader behavior change → psychological safety creation → team accountability → execution quality. Skipping the first step doesn’t accelerate the process — it invalidates it.

About Dr. David Farrar

Dr. David Farrar is a psychologist and Managing Partner at Koliso with a unique combination of credentials: 6 years of full-time formal training in psychology, 5 years of military service where he was trained in structured after-action review methodology, and 4 years as Global Organization Effectiveness Manager at the world’s largest private company. His work applies organizational psychology rigor to practical leadership accountability challenges in growing businesses.

Farrar built his consulting practice entirely through word-of-mouth referrals generated from client results — a deliberate proof-of-concept for the after-action review referral methodology he now teaches. His practice, Koliso, focuses on leadership assessment, team performance diagnostics, and psychological safety implementation for organizations navigating growth or structural change. His military background gives him a practitioner’s relationship with high-stakes accountability structures that most organizational consultants lack.

Ready to Build a Team That Executes Without Constant Oversight?

Farrar’s core insight applies directly to founders and GTM leaders managing cross-functional teams at $2–10M ARR: you cannot delegate effectively to people you haven’t assessed across all four CROP dimensions. Most team accountability gaps aren’t hiring problems — they’re evaluation problems. Leaders are using an incomplete model and then surprised when reliability, transparency, or principled behavior fails under pressure.

The frameworks covered in this episode — CROP, the Behavioral Interview Framework, the Psychological Safety with Purpose Pairing, and the After-Action Review system — are implementable immediately, without adding headcount or budget. But they require honest assessment of where your current team and your own leadership behavior actually stand.

If you’re ready to apply structured team accountability diagnostics to your growth challenges, the next step is a conversation with a strategist who can help you identify which gaps are costing you execution capacity right now.

Talk to a Growth Strategist →

Frequently Asked Questions

What are the four elements of the CROP trust model and why does each matter?

The CROP model evaluates trustworthiness across four dimensions: Competence (do they have the required skills?), Reliability (do they follow through on commitments?), Openness (are they transparent and receptive to feedback?), and Principled (will they make the right call when no one is watching?). Most leaders only screen for competence when selecting project leads. Missing any one of the other three creates execution gaps — unreliable follow-through, hidden problems, or corner-cutting under pressure. All four dimensions must be present for effective delegation and team accountability.

How do you assess if someone is truly principled before hiring them?

Use neutral behavioral interview questions that don’t telegraph the right answer. Dr. David Farrar recommends three specific prompts: “Tell me about the last time you had to make a difficult decision,” “Tell me about a decision you made that was different to what people expected,” and “Tell me about a time when it was hard to make a decision because other people didn’t agree with you.” Listen for the logic and values behind their choices, then pattern-match across answers to detect corner-cutting, ignoring colleagues, or capitulation under pressure. The stories reveal character more reliably than direct questions about values.

Why do psychological safety initiatives fail when leaders don’t participate?

Psychological safety programs collapse when leadership exempts itself. According to Dr. Farrar, the worst consulting engagements are ones where a mid-level stakeholder commissions the training but the leader declines to attend — those initiatives almost never produce lasting change. Safety is modeled from the top down. When leaders don’t demonstrate vulnerability, transparency, and accountability themselves, no amount of team-level training closes the gap. Leader opt-out signals that safety is for others, not a cultural standard — and employees read that signal immediately regardless of what the training materials say.

How do you ask for referrals without making it awkward or uncomfortable?

Stop asking for referrals directly. Instead, embed the ask inside a structured after-action review. Start by asking the client what went well and should be kept. Once they’ve articulated the value you delivered in their own words, ask where there were opportunities to do things differently. Then close with: “Do you know anyone else who’s facing issues like this?” This sequence works because you’re positioned as a problem-solving partner, not a vendor hunting leads. The client offers an introduction naturally because the conversation has already framed the need — no social pressure required.

How do you create psychological safety while maintaining accountability to outcomes?

Psychological safety must always be paired with explicit purpose — defined expectations for what that safety enables. Dr. Farrar’s Psychological Safety with Purpose Pairing model requires two simultaneous steps: first, normalize mistakes as learning opportunities through structured retrospectives; second, define clearly that safety is in service of risk-taking, invention, and candid feedback — not protection from performance standards. Without the purpose component, safety degrades into permissiveness. Without the safety component, accountability creates fear. Both must be present. After-action reviews operationalize both simultaneously by making learning and honest assessment a structural habit.