Skip to content

Lesson 3 — Perception and Client Politics: The Soft Skills

"Perception becomes reality... Regardless of all of the numbers and pointing to the S.O.W. and all the things that we said we were going to do and whether we accomplished it or not, none of that matters. Because if they don't feel like we've succeeded, they're not going to want to get us in the future."

— David Russell

1. Perception IS Reality

You might think your job is ticking boxes on a project plan. It is not. Your job is managing the client's feeling of confidence.

David makes this concrete with a scenario every new employee can picture:

"If you walk into the office in the morning, and you're three or four minutes late, and I say, 'Good morning,' when you walk in — do you think I'm admonishing you, or do you think I am greeting you?... It's in your head. Reality is your perception of it."

— David Russell

The same action — saying good morning — means completely different things depending on what the other person believes about the situation. That is exactly what happens with clients. If we do excellent work and say nothing about it, the client does not experience the excellence. They experience the silence.

Approach What Happens
Silent professional Client introduces messy data. Consultants spend 7 extra hours fixing it. Project ships on time. Client thinks: "That took longer than I expected." Satisfaction: neutral at best.
Communicated extra mile Same situation, but you document and surface it. "Your contract covered 8 hours of data cleansing. Because the raw files were fragmented, we invested 15 hours — here is the log — to guarantee the deadline." Satisfaction: high. Trust: increased.

The work was identical. The client's experience was completely different.

2. Bring a Patient, Not a Cadaver

This is the most critical operational rule at Cortado.

When a project timeline starts to slip, you have two options: raise your hand early while the problem can still be solved, or say nothing until the deadline passes and then explain why you are late.

"One of the most important things an executive wants is to be brought a patient, not a cadaver... As a doctor, I can help you when you bring me a patient. As a doctor, I cannot help you when you bring me a cadaver."

— David Russell

A cadaver cannot be saved. Bring problems to people who can fix them while there is still time to fix them.

The Carpenter Analogy

You are hired to pour a concrete driveway by the 30th. The homeowner is selling the house on the 1st.

The carpenters on the job site have been parking their trucks exactly where you need to pour concrete in two weeks.

The cadaver path: You say nothing. Two weeks pass. On the 30th, the driveway is not poured. You tell the site manager: "The carpenters were in my way."

It does not matter if you are technically right. You brought a cadaver. The deadline is gone. The sale is in jeopardy. And it is 100% your fault — because you could have said something two weeks ago and you chose not to.

The patient path:

"Two weeks early, you raise your hand: 'Hey, we're going to need to work here and the carpenters keep parking where we're going to need to work in two weeks. We're not there now, but that's going to be a problem.' Okay, it's been a week — they're still parking there. Does somebody own talking to them and getting them out of the way? Another week passes. We cannot begin because they're parked right in the way. And we've told you about this for two weeks now."

— David Russell

By documenting and communicating early, you give leadership a chance to move the trucks and save the timeline. You warn before it explodes.

The Project Coordinator Habit

Any time something is going to block the project — a deliverable that is late, a stakeholder who is not responding, a meeting that cannot get booked — your job is to surface it in writing, assign it an owner, and follow up. Do not absorb the delay silently. Document the chain of communication so that if the worst happens, you can show the timeline of when you flagged it.

3. Proactive vs. Reactive

The difference between an excellent Project Coordinator and a mediocre one often comes down to a single habit: working ahead.

Reactive Project Coordinator (wrong): Waits for the PM or EM to ask for the weekly deck. Scrambles Thursday afternoon. Delivers Friday morning at 9 a.m. — one hour before the 10 a.m. client call.

Proactive Project Coordinator (right): Builds the deck incrementally through the week. Delivers to the PM Wednesday night. Gives the EM time to pre-wire stakeholders Thursday. By Friday's call, nobody is seeing anything for the first time.

The reactive Project Coordinator creates a constant undercurrent of anxiety. The proactive Project Coordinator creates a constant undercurrent of confidence. Same skills, very different outcomes.

4. Navigating PortCo Politics

When Cortado walks into a Portfolio Company, we were hired by the PE firm. The people who work at the PortCo did not ask for us to be there.

"One of the worst things is when we get to the end of it and they ask the marketing guy, 'How are these guys doing?' and the guy is sad or upset... Why would he say we are doing a great job if we are justifying his termination? So much politics."

— David Russell

The marketing director is terrified that our analysis will prove he has been doing his job poorly, and that the PE firm will use that to justify letting him go. So what does he do? He books out his calendar. He sends you messy data. He is suddenly "too busy" for a half-hour interview.

This is not laziness. It is self-preservation. You need to understand the difference.

How a Project Coordinator Defuses PortCo Politics

You cannot force PortCo employees to trust us. But you can operate in ways that reduce their anxiety and bring them into the process instead of pushing them out of it.

Do not surprise them. If our analysis is going to surface something uncomfortable about their team's performance, the worst thing we can do is present it cold in a room full of people including their boss and the PE firm. Use pre-wiring (covered in Lesson 4) to give key stakeholders a chance to review findings privately before the big meeting.

Do not weaponize their data. When a PortCo employee hands us fragmented data because they are overwhelmed, we do not go to the PE firm and say "their data is a mess." We clean it, we note the extra effort internally, and we find a way to surface it that does not make the client look incompetent.

Acknowledge their expertise. These people have been running this business longer than we have been on the project. Treating them as obstacles rather than sources of institutional knowledge is both bad manners and bad analysis.

5. The Three-Corner Triangle

As a Project Coordinator on any Cortado engagement, you are managing pressure from three directions simultaneously. The triangle is not PE Firm / PortCo / Cortado — it is Seller / Client / Consultant.

flowchart TD
    Seller["Seller (Account Lead)\nBill · Dan · George\nWins the work · holds the relationship\nCommission on the line"]
    Client["Client\nPE Firm or PortCo management\nHas the pain · pays the check\nExpects delivery"]
    Consultant["Consultant\nStaff or 1099\nDoes the technical work\nTime being sold"]

    Seller <-->|"Relationship & promises"| Client
    Client <-->|"Deliverables & trust"| Consultant
    Seller <-->|"Scope & staffing"| Consultant

The Seller is the account lead who won the engagement — Bill, Dan, George. They made promises about what will be delivered and when. Their commission depends on the client being happy enough to buy again.

The Client may be the PE firm's deal team, or it may be the PortCo's management team, depending on who hired us and who we report to on this engagement. Not every Cortado client is a PE firm. Know who is actually paying the check.

The Consultant is doing the technical work. Their time was estimated by the Seller when scoping the deal, and that estimate may or may not have been realistic.

"Super important that you realize there are three angles that you need to worry about. It's not just do we deliver. It's not just the customer. You have the consultant whose time has been oversold because we underestimated because we wanted to get the business."

— David Russell

The Project Coordinator sits at the center of all three. You are tracking commitments the Seller made, protecting the Consultant's time from being consumed beyond what was scoped, and managing the Client's perception of progress. When one corner starts pulling too hard — a Seller who overpromised, a Client who keeps expanding scope, a Consultant who is slipping — your job is to surface it before it snaps.

Knowledge Check

Scenario

It is Tuesday. A PortCo VP has missed three consecutive deadlines to send you a critical sales territory map. Your big presentation to the PE deal lead is this Friday. The VP finally responds on Slack: "Sorry, dealing with a massive fire here. I'll get it to you Thursday night."

  1. If you accept this and wait until Thursday night — are you managing a patient or a cadaver? Why?
  2. Knowing that this VP might be dealing with internal anxiety about what our analysis will show, how can you follow up in a way that gets the data sooner without sounding like a robotic task-manager?
Discussion guide

1. Patient or cadaver? Cadaver. Thursday night delivery to a Friday 2pm meeting is less than 18 hours. Even if the data arrives at midnight, there is no time to run analysis, revise slides, or pre-wire the PE deal lead. The project manager and account lead have no opportunity to course-correct. The patient moment was two or three weeks ago when the first deadline slipped — that was the last point where Friday could have been saved. Accepting Thursday night does not manage the problem; it just delays learning that the problem is unsolvable.

2. How to follow up without sounding like a task robot: Lead with acknowledgment before the ask. Something like: "Totally understand — sounds like a rough week. Even a rough or partial version would help me start working. What would be the easiest format to send quickly?" This reduces the barrier (partial is OK), opens the door to earlier partial data, and signals you are trying to solve the problem together rather than chasing a checkbox. If you have any rapport with this VP, a brief Slack call is more effective than a written follow-up chain — it is harder to deflect a real conversation.

Continue to Lesson 4 — Tactical Operations