QUEST ADVISINGText Max (210) 880-5690How do I get my team to do what they said they would?
For the owner of a $5M to $15M company whose team's promises keep slipping.
Monday, in the truck, your estimator says, "I'll have the bid out Friday." Friday afternoon comes and there is nothing. So at nine that night you are at the kitchen table, writing it yourself.
Most promises that slip were loose when they were made. Nobody said who, what and by when, and nobody said it back. And when one slips, you usually take it back or let it go. Either way the team learns the promise was optional, and that it comes back to you.
This page shows the two moments where your team's promises break, when they are made and when they slip, and what to do at each. None of it means buying software or turning into the boss everyone is scared of.
If you want to talk about your own team with Max Kozlovsky, the advisor behind Quest, start a conversation. It starts with fifteen minutes. Max reads it himself. Nothing to prepare.
"I'll get to it" had no name, no day, and nobody said it back.
It slipped, you finished it yourself, and the team learned it would land on you.
You like him, so the short conversation about Friday never happened.
What a slipped promise costs you
One owner said it this way: "Where I can't ever connect the dots is getting them to do it." You hired good people. You told them what you needed. The bid still sat there on Friday.
The first cost is your nights. Owners describe the same pattern: when the team stalls, they do it themselves "because we can get it done faster," and then resent it.
The second cost is what the team learns. Each time you finish it, the team learns the date did not really count. Next week's promise comes out a little looser than this one, and nobody says so.
The third cost lands on your best people. While the talk waits, the people who keep their word cover for the ones who don't. Putting it off is normal. A 2026 survey of HR leaders by Leadership IQ found that "two-thirds of their managers regularly avoid or delay giving critical feedback."
Four ways owners try to hold people accountable
Most of what comes up on Google for this is written for managers with a boss above them, often by people selling HR software. This page is for the owner. Each one below made sense at the time.
A tougher speech. You pull everyone in and say it has to change. It works for a week or two, and then Friday comes around again.
A new tool or system. Owners try EOS, a project app, a whiteboard of who owes what. A tool can show who promised what, but it cannot make the promise clear or have the talk for you.
Checking on everything yourself. It catches the misses. It also means nothing moves until you ask, and you start to wonder what you are paying them for.
Doing it yourself because it is faster. Tonight it is faster. Over a year it teaches the team to wait for you.
For who helps with what, see Who to hire between $5M and $50M.
Owners, in their own words
If one promise on your team keeps slipping and you want to talk it through, start a conversation with Max, or text him.
The two moments a promise breaks
When the promise is made
A promise someone can keep has one name, one thing and one day, and the person can say it back in his own words. "I'll get to it" is not a promise. "Mike sends the bid by Friday at noon" is.
Saying it back matters. In 2015 Gallup reported that "only about half of employees strongly agree that they know what is expected of them at work." Hearing it back is how you find out before Friday instead of after.
The limit: it feels a little formal the first few times, at the end of a meeting or in a truck.
Before it is due, and when it slips
Look before the day, not after. A quick "Still good for Friday?" in the middle of the week gives him room to say no while there is still time to fix it.
When it slips anyway, have the short conversation instead of taking it back. What was the promise, what happened, and what is the new day. Then it stays his, not yours.
The limit: looking before is not checking on everything. It is one question about one promise, while the answer can still change something.
When it slips, sort the miss
Not every miss is the same, and the fix depends on which one it is.
Could not. He did not have the skill, or had too much on his plate. That is fixable with training, help, or fewer promises at once.
Did not know it was his. The promise was never clear. That one is yours to fix, at the moment it is made.
Does not want to. Max's words on this: "Everyone can grow. The question is how far, how fast, and people only grow if they want to."
Caring about someone and being clear with him are not opposites. "But I love the kid," one owner said, about a young man he knew was not right for the job. Whether he fits the job is a different question from whether he is a good person.
The limit: when he does not want to, no system fixes it.
Where it breaks, and what keeps it
| Where the promise breaks | What keeps it |
|---|---|
| "I'll get to it" | One name, one thing, one day |
| You assumed he heard it | He says it back in his own words |
| Nobody asks until Friday | You look before it is due |
| You finish it that night | You have the short conversation, and it stays his |
| Every miss gets the same speech | You sort it: could not, did not know, or does not want to |
One promise, followed through a week
This promise is made up, and so is the company. Here is one week of it, with a plain note on what was missing each day.
- Monday, in the truck: "I'll have the bid out Friday."No time of day, and nobody said it back.
- Wednesday: nobody asks how it is going.Nobody looked before it was due.
- Friday at four: the bid is not done.No early word that it would slip.
- Friday night: the owner writes it himself at the kitchen table.The miss came back to him, and the talk never happened.
- The next Monday: same estimator, new promise, "I'll get to it."The team learned the last one was optional.
It starts with fifteen minutes. At the end you both know if it is worth sitting down for longer.
Before the next promise
These work on the next promise anyone makes you.
Can he say it back, with a day? If he can't put it in his own words with a date, it is not a promise yet.
Did anyone look before it was due? One question in the middle of the week costs less than a late night at the end of it.
Who finished the last thing that slipped? If it was you, the team has learned it comes back to you.
Is it could not, did not know, or does not want to? Each one has a different fix, and one of them is yours.
Have you had the conversation you are putting off? If a name came to mind, that is the one to have this week.
Where an advisor fits, and the limit
Max asks until you can see where your promises break, and he checks your thinking on the person you have been avoiding. He does not manage your team or chase the promises. If one person cannot do the job, that is a hire or training. If the habit is taking it back, only you can change that.
The short version
- Most promises that slip were loose when they were made. One name, one thing, one day, said back.
- Look before it is due, not after.
- When it slips, have the short conversation instead of finishing it yourself.
- Sort the miss: could not, did not know it was his, or does not want to.
- Caring about him and being clear with him are not opposites.
This page is useful even if you never talk to Max. If you want to, start a conversation, or text him.
Questions owners ask
I've told them a hundred times. Why don't they just do it?
Telling them is not the same as hearing them promise it back. Usually the promise had no day, or the last one slipped and came back to you, so this one felt optional. Start with the next promise, not the last hundred.
Isn't it faster to just do it myself?
Tonight, yes. Over a year it teaches the team that a missed date ends with you finishing it. The short conversation costs more time once and less every time after.
I don't want to be the boss everyone's scared of. How do I push without the drama?
Being clear is not being harsh. One owner described a team "scared to take a step, because every time they take a step, it's just like, don't do that." Ask for one day, look once before it, and talk about the promise, not the person.
He's a good guy and he's been with me for years. What do I do when it's him?
Sort it first: could not, did not know it was his, or does not want to. The first two you can fix together. Whether he fits the job is a separate question from what he is worth as a person, and you can care about him and still be clear with him.
Do I need software or a system like EOS for this?
Some owners find a tool helps them see who promised what. It cannot make the promise clear or have the talk for you. Fix those two first, then use whatever tool works for you.
Can Max hold my team accountable for me?
No. It is your team, and the promises are made to you. Max helps you see where your promises break and checks your thinking on the people involved.
A promise that keeps slipping? Say what is going on.
Text Max or start a conversation, and say in your own words which promise keeps slipping.
If it is not a fit, he says so and that is the end of it, no follow-up.
You hear back typically the same day, or early the next. Nothing to prepare.