Talk it through with Aurelius
Why Is It So Hard to Hold Vendors Accountable?
You call it a vendor problem. It is not. You are describing a relationship with no fixed terms, then acting surprised when nothing holds. This is common when a team shares the work. One person implies something, another assumes it, a third fills the gap with hope. The vendor meets no single bar, because your team never agreed on one. Fix the agreement, not your temper. Say the number, the date, the standard — together, before you ever need to enforce it.
◆ How this problem reads on the two dials
GuidanceKnowledge
1:1 with AureliusWith others (a Pod)
The core idea — unspoken terms cause the failures you blame on vendors — needs little teaching, so most of the page pushes the team into the specific work of making terms explicit.
How the two dials adapt to you →What’s really going on
The vendor is not your problem. Your silence was. You never set clear terms, so now you have nothing firm to enforce. Stop reacting to broken promises. Go back with your team and write down, in plain words, what you expect — then hold each other to saying it out loud.
🔒 What you’ll build togetherUnlock by starting
A moveWrite down the three things that must happen every time, before your next vendor call.
A moveTurn every vague expectation in your head into a number — a deadline, a price, a response time.
A moveSay the consequence out loud to your own team before you ever say it to the vendor.
A moveReview your last five vendor complaints together. Find which ones trace back to a term nobody stated.
A movePick one vendor relationship this week and send a short, written agreement you both can point to.
PractiseName the Terms · a Pod of 4 · 30 min
What changes unlock by starting
- Your team agrees on what 'good enough' means before the vendor has to guess.
- Negotiations start from stated terms, not hurt feelings or memory.
- Fewer surprises, because expectations stop living only in someone's head.
- You catch a pattern of failure before it becomes a habit.
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.