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

Why can't I see or trust what my team is doing?

You look at the board. You ask for updates. You still don't believe what you're seeing. That is not because your team is lying to you. It is because no one ever agreed on what 'visible progress' looks like — so everyone is reporting in their own private language, and you are left to guess at the translation. Here is what actually happens next: you stop trusting the gaps, so you check in more. They feel watched instead of trusted, so they share less — just the good news, just enough to satisfy you. Now the pipeline is less honest than before you started checking. You built the very problem you're trying to fix. You cannot control whether people are naturally transparent. You can control whether your team has agreed on where progress lives, how often it's reported, and what counts as stuck. That agreement does not exist yet. Make it exist. That is the whole task.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The team doesn't lack information about pipelines — they lack a made decision, so the page leans toward action over instruction.
How the two dials adapt to you →
What’s really going on

This is not a tool problem. It is an agreement problem. No one decided what 'on track' means, how often to report, or what happens when work stalls. You filled that silence with suspicion. Fix the agreement, and the pipeline becomes visible again. Call a meeting this week and decide the terms together.

🔒 What you’ll build togetherUnlock by starting
A moveCall a 30-minute meeting this week. Ask each person to say, in their own words, what 'on track' means for their work.
A moveChoose one place progress lives. Not three tools pieced together — one. Write down the choice where everyone can see it.
A moveSet a fixed cadence for updates — daily or weekly — and decide it now, out loud, not by drift.
A moveName what 'stuck' looks like and who hears about it first. Vague trouble stays hidden; defined trouble gets reported.
A moveStop pulling individuals aside for private status checks. Go to the agreed system for your answer instead — and if the system fails you, fix the system, not the person.
PractisePipeline Pact · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team agrees, within a week, on one place and one format for tracking progress.
  • Updates start arriving before you ask for them.
  • You stop guessing at intentions and start pointing to agreed facts.
  • Your team reports feeling checked against a standard, not watched by a suspicious boss.
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.