How I Communicate

The Experiment

In February 2026, I did something most consultants would never consider: I asked my AI operations team to study every conversation I'd had with clients over the past eight months and tell me the truth about how I communicate.

Not a personality assessment. Not a 360 review with diplomatically worded feedback. A forensic analysis of every recorded conversation turn — what I said, how long I talked, when I asked questions versus made statements, when I created space for others versus filled it myself.

The first version of the assessment came back, and I challenged it. Not because the findings were uncomfortable — though some were — but because the evidence base was too narrow. It relied too heavily on session summaries instead of raw transcripts, and it drew conclusions from one client engagement that it applied broadly.

So I told the team to go deeper. Read every transcript. Cross-validate across clients. Quantify what can be quantified. And don't soften the findings.

They came back with a 737-line assessment that corrected assumptions I'd held for years. The correction story matters as much as the findings: the willingness to be wrong about yourself is the prerequisite for actually understanding yourself.

What follows is the public version — curated for context, anonymized to protect client relationships, and shared because I believe radical self-assessment is the kind of transparency this industry needs more of.

What the Numbers Say

Before any interpretation, here's what surprised me most: the gap between what I assumed about my communication and what the data actually showed.

The finding that corrected my biggest assumption: I am not a monologuer. Not with clients. The monologue rate across 13,683 turns is 0.1–0.5%. Over half my turns are quick responses — acknowledgments, redirects, comprehension checks. I teach through rapid interactive exchange, not long speeches.

The "talks too much" pattern does exist — but only in one specific context: internal processing conversations. With clients, I create space. The data made this distinction unambiguous across two completely different engagements.

The Language Shift

One of the most interesting quantitative findings was how my language changes by context:

• "We can" nearly triples in client-facing conversations — shifting from analytical framing to capability signaling
• "We want" quadruples — inclusive direction-setting that only appears when I'm with a client team
• Question rate increases from 15.5% internally to 18.2% client-facing — I ask more questions when facilitating others

These shifts are not conscious. I didn't know about them until the analysis revealed them. But they show something I think is important: communication adapts to serve the people in the room, not just the person speaking.

Five Modes on a Dial

The original assessment proposed two modes: "External Chris" versus "Internal Chris." The deeper analysis found that framing was too simple. I operate on a continuous dial with at least four distinct public modes — plus one internal mode that stays behind closed doors.

The fifth mode is internal — how I process with my closest collaborator. Long, associative, stream-of-consciousness. It's where I do my thinking, and it's also where most of my growth areas live. I'm sharing that this mode exists because pretending I'm always in "Coach" mode would be dishonest. The discipline I bring to client conversations is real. The discipline I bring to internal processing is... a work in progress.

What I Do Well

The assessment identified eight strengths. Five of them are things I want people who work with me to understand, because they shape how our conversations will feel.

The Reframe

This is the single most consistent pattern across every client, every context, every transcript. I don't give advice. I change how people see.

This isn't a technique. It's how I process the world. I hear the signal inside the noise and play it back in a way that makes the pattern visible.

Pattern Recognition Across Domains

I see structural problems the way most people see furniture — immediately, intuitively, and with certainty about what belongs and what doesn't.

Architecture-as-Teaching

I don't just design data models — I teach clients the reasoning behind every architectural decision. The data shows 43% of my turns are 10–80 words of explanation. I establish the principle before the implementation. The architecture serves the teaching, not the other way around.

This is the opposite of dependency. Clients who work with me learn to think architecturally, not just use the system I built. By the time we're done, they can make their own architectural decisions.

Non-Defensive Reception of Feedback

The transcripts show this consistently: I take hard feedback without flinching.

When a colleague suggested my website content might be too complicated, I didn't get defensive. I explained my reasoning, acknowledged the input, and moved on. When a client said certain recurring meetings were unproductive, I relayed the feedback to the team without softening or rationalizing.

The assessment found no instances of me arguing with critique or dismissing feedback. I absorb, process, and act. Whether that's always fast enough is a different question — but the defensiveness isn't there.

Creating Champions

I deliberately build internal capability rather than dependency.

Another client went from uncertain platform user to internal champion over six months. I told them: "You're setting a great foundation for the rest of the team." I position myself as the person who helps people use what they already have — not the person who brings something they don't.

The "Right? So" Method

My most frequent verbal pattern appears hundreds of times across transcripts. For years, I assumed it was a filler — a verbal tic I should probably work on eliminating. The assessment proved me wrong.

"We're not going to subscribe to what the platform says we need to do. It's completely system independent. This could be applied to any CRM or any system you wanted to use. Right? So, we're going to rename the lifecycle stages to these stages."

It's not a filler. It's a pedagogical device that keeps the listener cognitively engaged while I build a logical chain. Assert → Check → Imply. It works because it makes the listener's comprehension visible in real time — the "right?" creates a micro-moment where they can nod, question, or redirect before I draw the implication.

I use it in every coaching session. I didn't design it consciously. The assessment just finally named what I'd been doing all along.

What I'm Working On

This is the section most consultants would never publish. But the whole point of this exercise is that radical self-assessment only works if you share the uncomfortable parts too.

Emotional Bypass

When someone shares something emotionally charged in the middle of a session, my reflex is to jump to the architectural solution. The feeling lands, I register it, and then — too quickly — I pivot to fixing the problem instead of sitting with the person.

The assessment found 7 bypass instances and 8 counter-examples across one engagement. The ratio is close to even. But the quality isn't: I bypass when emotion arrives unexpectedly. I sit with it when I have space to choose.

The encouraging trend: the sit-with moments cluster more heavily in recent months. Growing awareness, not yet consistent application. The practice I'm working on: when someone shares something emotionally charged, my next sentence should acknowledge the feeling before the architectural pivot. The architecture isn't wrong — the sequence sometimes is.

Coaching-to-Telling Ratio

Across all transcripts, my estimated ratio is 30% coaching questions to 70% telling statements. My question rate is 16.5–18.2% depending on context.

For a consultant, that's fine. For a coach, it's moderate. My diagnostic questions are strong — I'm good at asking the question that reveals the real problem. But true coaching questions (“What do you think should happen next?” / “What's getting in the way?”) are rarer than they should be.

Architecture Gravity

I'm drawn to data model and architecture work the way certain people are drawn to puzzles. The transcripts show this is my most consistent gravitational pull — a conversation about strategic positioning can end up in object-level architecture within the same breath.

I named this pattern myself in a client session:

"I'll ask for help from you guys to help bring me down to earth sometimes when I start talking about this stuff... I can get like four layers deep really quickly."

The self-awareness is there. The self-regulation is inconsistent. Before diving into a property workshop or technical walkthrough, I'm learning to ask myself: "Is this something only I can do, or am I doing it because I enjoy it?"

The Moment That Changed Everything

In early 2026, a new team member joined us. During their first week, they were getting oriented — learning our systems, understanding how we work, exploring our tools and our client data.

They looked at me directly and told me:

One word. No defensiveness. No explanation. No redirect. No "well, we're working on it."

I'm the founder of a methodology built on the idea that organizations need unified visibility across their operations. And a person in their first week told me my own business fails that test. My response was a single word of agreement.

Then I said: "My way has not been successful, so hopefully there's only one way to go."

This moment matters to me more than any framework I've built, any show I've hosted, any client success I've enabled. Because it proves something about who I actually am versus who I present myself to be.

A lesser leader would have explained. Deflected. Reframed. I just said: correct. And framed the addition of new team members as the solution rather than defending my approach.

The assessment called this "the single most important transcript for understanding who you actually are. Not the polished frameworks. Not the methodology. A man who can look at his own gap and name it without flinching."

What This Means for You

If you're considering working with me, here's what this assessment means in practice:

Most consultants present a polished version of themselves and hope you never see behind it. I'd rather you know exactly who I am, how I work, and what I'm actively improving. If that level of transparency makes you uncomfortable, we're probably not the right fit. If it makes you think "finally, someone who's honest about their own gaps" — that's the foundation we build on.