Most team conflicts aren't born from a disagreement. They're born from an expectation that was never said out loud.

You had it clear in your head. You assumed it was obvious to the other person too. It wasn't — and the cost of that gap doesn't show up as direct conflict. It shows up as quiet disappointment, as "I can't believe they didn't do it," as someone feeling judged by a rule they never knew existed.

These are the seven that almost never get said — and that should be said in the first week of any working relationship, not discovered three months later in the middle of a crisis.

1. What "good work" means to you. Not in general — in your team, in your style. Is it speed? Precision? Initiative? Every leader weighs these things differently, and no one guesses right on the first try.

2. When you expect people to decide on their own and when you expect them to check with you. Without this, people either check in on everything (and it frustrates you) or check in on nothing (and it frustrates you more). The problem isn't their judgment. It's that you never drew the line.

3. What makes you trust someone. Some leaders trust based on results. Others trust based on transparency, even when the result falls short. If your team doesn't know which one you are, they'll try to guess — and they'll get it wrong.

4. What happens when someone makes a mistake. Not in theory — in practice, with you. If your actual response and the response you preach don't match, your team will believe the real one, not the one you said in the values meeting.

5. How you want to be given bad news. Fast and unfiltered, or with context first. People who don't know this will sit on bad news until it's too late to act.

6. What "being available" means to you. Do you answer on weekends? Do you expect them to? Ambiguity here doesn't create flexibility — it creates anxiety, because no one knows whether they're falling short or not.

7. What you will never tolerate. Not the long list of rules — the actual red line, the one that genuinely costs someone your trust in a way that's hard to rebuild.

None of these seven are hard to say. What makes them difficult is that they need to be said before you need them — while there's still no tension, while they still feel like an onboarding conversation and not a correction.

The question isn't whether your team knows these seven things about you. It's how many of the seven you could answer right now, in one sentence, without having to think about it.

Want to map out yours before they cost you a hard conversation? Reach out or start with the leadership assessment.