Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why doesn't my team trust my 'consultations' anymore?

You already decided. Then you called a meeting and asked for opinions. Your team gave them, watched you ignore them, and understood what happened. They are not confused. They are accurate. The decision itself is not the wound. People accept decisions they disagree with all the time. What they do not accept is being asked to perform participation they were never given. That is the part you need to own, plainly, without softening it. This is fixable, but not by apologizing for the outcome. It is fixed by telling the truth about the process — now, and every time after. Call a decision a decision. Call a consultation a consultation. Let the words match the thing.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The concept (naming the gap between stated and real process) is simple and teachable fast; the hard part is the team-facing conversation and behavior change, which needs direct coaching.
How the two dials adapt to you →
What’s really going on

They stopped trusting the process because you ran one that didn't exist. You asked for input you had no intention of using. The fix is not a better speech — it is to stop calling decisions consultations, or start actually consulting. Choose one, and tell them which.

🔒 What you’ll build togetherUnlock by starting
A moveName it to your team plainly: 'I called that a consultation. It wasn't one. That's on me.'
A moveBefore your next meeting, label it out loud as Decide, Consult, or Co-decide — and mean it.
A moveIf you run a real consultation, bring at least one decision you are genuinely willing to change. If you can't name one, it's not a consultation.
A moveAsk your team directly: 'Where else have I done this?' Then sit still and let them answer.
A moveStop using the word 'input' for meetings where no input will change anything. Call it an announcement instead.
PractiseName the Process · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team can predict, before the meeting starts, what kind of process they're walking into
  • Fewer silent meetings — people speak because they believe it might matter
  • You stop paying the hidden cost of being quietly discounted in every future 'consultation'
  • A working vocabulary your pod can use to call out the gap before it becomes a pattern

Related problems

One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.