I assess a team's Collective Stress Profile. It's a lot easier to evaluate leadership teams when things are going well, but true effectiveness is determined by how a team behaves under pressure. I map the specific derailers of each executive - do they withdraw, attack, or conform when stressed? - to create a composite view of the team's shadow side. For example, I recently coached a C-Suite that prided itself on collaboration. Their Stress Profile revealed that under pressure, 80% of the room had a 'Move Away' (withdrawal) response. What the CEO thought was alignment was actually artificial harmony. They were terrified of conflict, so critical issues were being ignored to preserve the peace. To address that, we operationalized friction. We instituted a 'Red Team' protocol where, for every major decision, one person was assigned the role of the dissenter. By making conflict a role rather than a personality trait, we broke the silence, and decision-making velocity increased by 40%.
One of the most reliable ways I assess a leadership team is by reviewing its decision patterns.I look at how decisions actually move, not personality, presentation skills or how aligned meetings feel. I look at how quickly they are made, where they stall, how often they escalate to the CEO, are they reopened repeatedly and what happens when they fail. Leadership effectiveness shows up in those patterns. If everything runs through one person, you do not have a leadership team, you have a bottleneck. If decisions are revisited over and over, clarity is missing. Either decision rights were never defined, or leaders are not empowered to hold the line once a call is made. If dissent disappears entirely, it is usually a signal that speaking up feels risky. This kind of review consistently reveals that performance problems are about structure, not intelligence or effort. Unclear decision ownership, quiet tension between executives, or avoidance of conflict slow the organization down in ways that are easy to miss but expensive over time. Once the friction points are visible, we address them directly. We clarify who recommends, who decides, and who owns execution. We set expectations around what level of information is required for different types of decisions. We also make room for real debate so leaders can disagree rigorously and still leave the room aligned. The impact is tangible. Decision velocity improves, escalations decrease and strategic initiatives stop circling and start moving. Executives spend less time protecting their position and more time building forward momentum. An effective leadership team is not one that agrees all the time. It is one that can debate openly, decide clearly, commit fully, and learn quickly when reality proves them wrong. When decision flow strengthens, performance follows.
After every major engagement, a high-stakes workshop, a difficult client dialogue, a strategic intervention, we debrief. But we don't start with outcomes. We start with process. Each person on the team answers: where did we create clarity? Where did we create friction? And where did our presence actually shift what was happening in the room? This tells me things that performance metrics never will. It surfaces how the team thinks under pressure, how they handle tension, and whether they're modeling the steadiness we're asking our clients to build. In one case, we realized our strategy was strong but we were moving through moments of resistance too quickly, people were complying but not contributing. Slowing down changed everything. The pattern I keep learning: how the team shows up matters as much as what they deliver.
I track how long our average customer stays with us--currently sitting at just under a decade. That number tells me everything about whether my leadership team is actually executing on our core value of building relationships versus just processing transactions. About three years ago, I noticed our customer retention was strong overall, but we were losing newer customers within their first year at nearly double the rate of our established clients. I pulled our service advisors together and realized the problem wasn't technical--it was that my leadership hadn't created systems for the team to follow up after first visits. New customers felt like strangers every time they came back. We implemented a simple practice: every first-time customer gets a personal call from their service advisor three days after their visit. Not a sales call--just "how's the car running, any questions?" Our first-year retention jumped 34% within six months, and those customers are now part of that near-decade average. The method works because longevity is the ultimate BS detector. You can't fake your way into keeping 15,000+ customers coming back year after year unless your leadership team has built a culture where people genuinely feel cared for, not sold to.
I use job site walk-throughs where I specifically ask our project managers and field leads to tell me what I got wrong that week. Not what went well--what *I* screwed up as their leader. Sounds harsh, but when you're running excavation and electrical projects where someone can literally get hurt, you need people who'll call out problems before they escalate. Best insight came after a commercial electrical retrofit where we fell behind schedule. My PM told me I'd set unrealistic milestones because I hadn't factored in the building's outdated conduit access. He was right--I'd rushed the bid without enough front-end assessment. Now our initial inspections include thermal imaging and load calculations that I personally review before committing timelines to clients. This method also exposed that our excavation crew wasn't getting enough autonomy on routine projects. They knew the work cold but were waiting for my sign-off on decisions they should've owned. I shifted to outcome-based check-ins instead of micromanaging daily tasks--our project completion rate jumped and crew morale improved enough that we've had zero turnover in eight months. The uncomfortable conversations are where real performance gains hide. When your team knows you actually want to hear what's broken, they'll help you fix it before it costs you a contract or someone's safety.
I use real-time member feedback through Medallia to assess my leadership team's effectiveness. Every negative comment that comes through gets assigned to a specific manager, and I track two things: how fast they respond and whether that member's satisfaction improves in the next 30 days. The biggest insight came when I noticed our Satellite Beach location had a pattern--members complained about equipment availability during 5-7pm, but our floor staff kept saying "everything's fine." I pulled the Medallia data for that specific timeframe and found 11 comments in one month mentioning the same three machines. Turned out my team lead wasn't actually on the floor during peak hours to see it himself. We shifted his schedule, added a second staff member during that window, and those complaints dropped to zero within three weeks. What changed our whole approach was tracking resolution rates by manager. One of my supervisors had a 41% resolution rate while another hit 89% on similar issues. I sat in on how the high performer handled member concerns--she was following up in person, not just fixing the immediate problem. Now that's our standard protocol, and our overall member retention improved enough that we expanded our REX Roundtable sharing to help other operators build similar systems. The key is connecting feedback directly to the person responsible and measuring whether they actually moved the needle, not just whether they responded.
I track training completion rates alongside employee complaint patterns--specifically looking at *when* people complete required harassment prevention training versus when incidents get reported. Most companies just check the completion box, but the timing tells you everything about leadership effectiveness. About eight months ago, I noticed a client's supervisors were pushing training to the last possible day before deadlines, while their employee-level staff completed it within the first week of assignment. Their HR leader dug in and found that managers were treating compliance as an interruption rather than modeling it as a priority. Complaints in that organization were also clustering in departments where supervisor training lagged the most--not a coincidence. We restructured their rollout so leadership had to complete training first, before it even went to their teams. Supervisor completion jumped from an average of 28 days to 6 days, and more importantly, the number of "I didn't know that was wrong" defenses in complaints dropped by about 40% over the next quarter. When your leadership treats compliance training like it matters, the entire organization's behavior shifts. The insight isn't just about checking boxes--it's about whether your leaders are creating a culture where people actually learn this stuff or just survive it. Completion timing is a proxy for leadership buy-in, and buy-in directly correlates with how your team handles real workplace situations.
One method I use is very simple, but it's uncomfortable on purpose. I ask each leader to do a structured self-assessment around four human traits: humility, growth mindset, courage, and curiosity. Then I compare that to how the team actually experiences them. Not a personality test. Not a KPI dashboard. A reflection exercise. For humility, I ask: Where were you wrong this quarter? Who corrected you? What did you change because of it? For growth mindset: What skill are you actively building right now? Where are you behind? For courage: What hard conversation did you initiate? What decision did you delay that you shouldn't have? For curiosity: What assumptions did you challenge? What question did you ask that shifted direction? Then I collect anonymous feedback from peers and direct reports around the same traits. Not "Do you like this leader?" but "Do they demonstrate these behaviors consistently?" The insight has been powerful. Most leaders overestimate their curiosity and underestimate their defensiveness. Many believe they are courageous because they make tough operational calls, but avoid interpersonal accountability conversations. Some think they are growth-oriented but haven't learned anything meaningfully new in a year. The gap between self-perception and lived experience is where the real work is. I've used that gap to coach very directly. If someone thinks they model humility but their team experiences them as closed off, that becomes the priority. If a leader avoids hard conversations, we don't send them to a seminar, we role-play the conversation and then they schedule it within a week. It has also shaped how we select leaders. Technical skill matters. Strategic clarity matters. But if someone cannot demonstrate humility under pressure, curiosity in ambiguity, courage in conflict, and a genuine growth mindset, they will cap the organization. What this method reinforced for me is simple. Leadership performance is not just about hitting numbers. It's about the emotional and intellectual environment you create. When those four human skills are strong, performance improves naturally. When they are weak, no amount of strategy will compensate. The numbers tell you what happened. Character tells you what will happen next.
I look at **job completion timelines versus customer complaint rates**--specifically how fast we close projects compared to callbacks we get in the 90 days after. At James Kate Roofing, we started tracking this when I noticed our fastest crews weren't always our best crews. One team was finishing residential replacements in under two days but generated 4x more leak callbacks than a slower crew that took an extra half-day. That pattern told me my production managers were rewarding speed over installation quality. We were incentivizing the wrong behavior. I pulled our top performers aside and realized the difference: the slower team was double-checking flashing details and taking photos at every penetration, while the fast crew was skipping documentation steps to hit bonuses. We flipped the bonus structure to reward **zero-callback completions** instead of pure speed. Within six months, our callback rate dropped from 8% to under 2%, and our GAF President's Club status came partly from that shift. My leadership team now understands that how we measure performance directly shapes what behaviors we get--and protecting our reputation matters more than shaving hours off a schedule.
I track our leadership team's effectiveness by monitoring the "80-20 rule" in our service operations--80% of maintenance costs come from 20% of problems. Every quarter, I sit down with department heads and review which recurring customer issues are eating up our budget and time. If the same problems keep appearing, it tells me we're not communicating solutions effectively or empowering our team to make decisions. Last year, this revealed that our parts department was getting hammered with emergency requests for the same hydraulic components. Our service manager had identified the root cause months earlier but hadn't pushed hard enough to change our stocking procedures. We restructured our inventory system based on his insights, and emergency orders dropped by nearly 40% within six months. The biggest lesson: when the same fires keep burning, it's usually a leadership communication problem, not a frontline execution problem. I now require any recurring issue that appears three times in our service logs to trigger an automatic leadership review. Our team knows they won't get blamed for bringing problems forward--they get blamed if they don't escalate patterns they're seeing.
I run a bus charter company in Brisbane, and I assess my leadership team by tracking our "zero cancellation" record. We've literally never cancelled a booking in our entire operation, and maintaining that streak tells me exactly how well my team handles pressure and problem-solving. When COVID hit, we had cancellations rolling in daily and tough decisions to make. I watched how my ops manager handled communication with affected clients and how our lead driver coordinated with our network of partner operators to cover bookings when we were short-staffed. The fact we kept that zero-cancellation streak alive through the pandemic showed me our leadership could adapt under extreme pressure. The biggest insight was finding that our strength wasn't in individual skill--it was in relationships. My team's connections with other small operators meant when our coach broke down 30 minutes before a wedding pickup, we had backup sorted in 15 minutes. Now I specifically hire and promote people who naturally build these networks, not just those with the best driving records. I also learned our weakest point: we were terrible at documenting these workarounds. After nearly losing track of which backup driver was covering what during a particularly chaotic week, I had my team start a simple shared log. Sounds basic, but it transformed crisis management from frantic phone tag into a smooth handover system.
I measure leadership effectiveness through our delivery driver feedback loop. Every week, Robert (our driver) and I sit down for 15 minutes to review what actually happened on routes versus what we planned in the office. If there's a gap between Jody's scheduling and what's possible in the field, that's a leadership communication failure on my end. This method revealed that we were promising same-day delivery windows that looked perfect on paper but created chaos for our driver when customers weren't home or driveways weren't accessible. We were setting up both our team and customers to fail because office leadership wasn't listening to boots-on-the-ground reality. We changed our quote process to include a mandatory field assessment for tricky locations, and Robert now texts Jody directly when he spots potential access issues during other deliveries in that area. Our customer complaints about delivery timing dropped to almost zero, and our Google reviews went from mentioning "good service" to specifically calling out our communication and flexibility. The insight: your frontline team sees problems before leadership does. If you're not creating a weekly space where they can tell you what's broken without fear, you're leading blind.
One method I rely on is sitting down quarterly with each member of my leadership team for what I call "legacy conversations"--not performance reviews, but real talks about whether we're living up to the promise we make to customers. At Benzel-Busch, we don't just sell cars; we sell a promise and stand behind it, so I need leaders who genuinely understand that difference. These conversations revealed something critical a few years back: our service department was technically efficient but wasn't connecting emotionally with customers the way our sales floor was. The data showed strong completion times, but customer retention told a different story. We restructured our service approach to focus on the relationship, not just the repair, and saw our repeat service visits climb significantly. The biggest insight has been that my leadership team performs best when they understand they're custodians of a century-old family legacy, not just managers hitting monthly targets. When I became the third-generation president, I could have just focused on numbers, but instead I ask my team: "Would my great-grandfather Giuseppe, the blacksmith who customized each goat cart, be proud of how we treated this customer?" That question changes everything about how decisions get made around here.
I use our quarterly athletic assessments as a direct mirror for leadership effectiveness. When I look at athlete retention rates and progression data across our training levels (Free, Foundation, Fit, Fortified, Fast, and Freak), I can immediately see which staff members are connecting with kids and which aren't. About six months after joining Triple F, I noticed something weird in our data--athletes were crushing their physical metrics but parents were still expressing concerns during check-ins. Our Director of Athletic Development, Rich Burnett, had built this incredible custom reporting system, but we weren't translating those numbers into conversations families could understand. I started sitting in on parent meetings and realized our leadership team was speaking "sports science" when families just wanted to know if their kid was getting better at football. We pivoted hard. Now every coach has to explain assessment results using sport-specific language--"Your son's improved elasticity means he's exploding off the line faster" instead of "His reactive strength index increased 12%." Our renewal rate jumped because parents finally saw the value we were delivering. Coming from behavioral health, I learned that data means nothing if you can't communicate it in a way that resonates with the person who needs to hear it. The insight was brutal but simple: technical excellence without translation is just noise. My background treating substance use taught me that meeting people where they are matters more than showing them how smart you are.
I track one counter-intuitive metric when evaluating leadership: how many deals they walk away from, not how many they close. In M&A advisory, desperation kills value--I've seen founders lose 40-50% of their exit value because their team pushed them toward the first buyer instead of running a proper process. Last year we had a SaaS company that received an unsolicited $8M offer. The founder's advisors were ready to celebrate and close quickly. We identified 140 potential buyers, ran a competitive process, and closed at $22M--nearly 3x the "bird in hand." The difference was having a team willing to risk the initial offer to find the right buyer. I've built this same discipline into how we operate internally. When our proprietary deal-matching system flags a potential buyer, my team knows I'd rather hear "this isn't the right fit" than watch them force a square peg into a round hole. Since implementing this, our average deal value has increased 30% because we're more selective about which buyers we bring to the table. The insight: leadership effectiveness isn't about always saying yes--it's about having the confidence and judgment to say no. Teams perform better when they're empowered to walk away from bad opportunities rather than pressured to chase every shiny object.
I assess my leadership team's effectiveness through **case outcome tracking combined with team decision speed**. After 20+ years as both a prosecutor and defense attorney--including running the DA's office--I've learned that the best indicator isn't just win rates, but how quickly my team spots opportunities that actually matter to clients. Here's what I found: when I tracked how fast my attorneys identified viable defense challenges (like flawed breathalyzer calibration in DUI cases or procedural errors in drug cases), the ones who flagged issues within 48 hours of intake had 3x higher charge reduction rates. That told me knowledge wasn't the problem--urgency was. We restructured our intake process so every team member does an immediate "red flag audit" before the first client meeting, not after. The real breakthrough came from tracking *which* defenses my team pursued versus which ones actually worked. I noticed younger attorneys were focusing heavily on suppression motions while overlooking simpler diversionary programs like Section 17 for drug cases. One attorney spent weeks preparing a motion when the client qualified for probation without verdict the whole time. Now we run monthly "strategy autopsies" where we compare time invested versus client outcomes--not to criticize, but to spot patterns we're missing. The method works because it's tied to real people's futures, not performance reviews. When my team sees that catching an issue on day one kept someone out of jail versus dragging a case out for months, they change how they work without me forcing it.
I assess my defense team's effectiveness through **case outcome tracking and client feedback loops**. After 25+ years in criminal law--including time as Chief Prosecutor and now as principal attorney--I've learned that wins aren't just about dismissals. They're about how well we protected clients' rights at every stage. Here's what I track: ALR hearing success rates, evidence suppression motions granted, and cases resolved without trial. For example, when reviewing our DWI practice, I noticed officers were consistently misscoring field sobriety tests--claiming arm movement as intoxication when subjects stayed within the legal 6-inch allowance. That pattern told me my team needed deeper NHTSA certification training, which I got myself and now require. The biggest insight? **Documentation quality predicts outcomes.** When we started systematically requesting police bodycam footage in domestic violence cases, we caught inconsistencies that prosecutors missed. This shifted our strategy from reactive defense to proactive evidence challenges. Now my team knows: if documentation exists, we demand it before building our defense strategy. I also hold monthly case reviews where we dissect both wins and losses. One probation violation case taught us that judges respond better to rehabilitation evidence than legal technicalities. We adjusted our approach across all probation cases, and our success rate improved measurably. The key is treating every case result as data, not just a verdict.
I measure leadership effectiveness through **employee retention conversations**--not exit interviews, but quarterly one-on-ones where I ask my team what would make them leave. At CDL Mechanical, I learned this after we started in 2016 and I realized that waiting until someone quits to find out what went wrong was way too late. The biggest insight came when three technicians independently mentioned they felt disconnected from company decisions. They weren't complaining about pay or workload--they just wanted to understand the "why" behind changes. I started doing monthly team huddles where I share financials, upcoming challenges, and ask for input before making operational shifts. Our turnover dropped noticeably after that. I also track how often team members come to me with problems versus solutions. Early on, I was the bottleneck for every decision. Now I measure how many issues get resolved without my involvement--that tells me if I'm actually developing leaders or just creating dependents. When Dale started training newer techs without being asked, I knew the mentorship culture was working. The method works because it's proactive rather than reactive. I'm not waiting for problems to surface through complaints or missed metrics--I'm creating space for honest feedback before small frustrations become resignation letters.
In the nonprofit space, one method I use to assess my leadership team is simple: I look at what customers say after they try to run a fundraiser. Customer reviews, support conversations, and those "can you take a look at this?" moments tell me fast if we are leading well. The biggest insight is how much nonprofit staff are juggling at once. When they say, "you made it really easy," that's a signal our leaders are staying close to real needs and reducing stress. When we hear "I don't know where to start," it means we introduced friction and we need to own that. We use that feedback as a scoreboard, then we act on it. We revisit the product flow so it guides people through a process by answering questions, like someone holding your hand. We also lean into hands-on help, including building campaigns for organizations and reviewing setups so they feel supported from planning through launch. On the leadership side, I make "getting close to customers" a real expectation, not a slogan. We pick clear owners for the fixes, ship changes quickly, and follow up to confirm we actually eased their burden. That cycle has improved focus, decision-making, and teamwork because everyone is aligned around making fundraising easier for nonprofits.
One method I rely on is regular 360 feedback, not just at the individual level but across the leadership team as a whole. It gives us a clear view of how leaders are showing up, how they're supporting their teams, and where blind spots might be forming. We look at patterns over time, not just one-off feedback, so we can see how the team is evolving and whether changes are having an impact. One of the biggest insights this process gave us was around communication. Even strong leaders can slip into silos when things move fast, and that was starting to affect clarity and alignment across teams. By surfacing that early, we were able to adjust how leadership connects—shorter updates, more async communication, and more transparency around decisions. It helped rebuild trust and made things move faster without burning people out.