The tree died. Somebody paid to cut it down. The stump stayed. Cutting the tree was the urgent part. A leaning limb over a walkway gets a call the same day. A stump is only ugly, and ugly does not make next week's list. The person who approved that invoice knew. Standing right there with the chainsaw noise still in their ears, looking at the stump, telling themselves they'd get to it. Maybe the budget was short that month. Maybe grinding was another 300 bucks, and they were already over budget. So, we get an ugly stump to remind us of this failure. That was my site. So before this reads like me pointing at somebody else, I am constantly working with my team to stop these half-assed jobs from showing up. Sometimes deferring is the right call. Cash is real, and a stump is not a roof. What makes this one different is that it never came back to the list, and the person who signed it knew that when they marked the job done. Every unfinished job leaves a metaphorical stump. A pricing model with a poor follow-up call process. A hire nobody checked on after thirty days. A software rollout where you bought the licenses and quietly skipped the training because the vendor's onboarding week landed in the middle of a busy month. The stumps are what your team learns from. Close enough clears the bar, they say one thing and do another when it suits them, and every new hire figures that out in about a month without anyone having to say it. Few residents complain. Not many customers leave reviews, so be grateful for the ones who bother. Employees leave it out of the exit interview. They just decide this isn't for them and leave when something better comes along. So how do you keep half-assed jobs from becoming the norm? Start by defining done as the finished condition. Removing the tree closes the hazard. Restoring the landscape bed closes the job. This applies to more than landscaping, obviously. 🦉 Writing that definition down is the easy part. Getting it to hold when the budget is tight or when you have not visited the site in a while is a different problem. You can't outsource your standards, and your people are reading your actions, not your handbook. The inspections, the audits, the slow one-on-ones few want to sit through, all of it has to happen on a schedule, whether or not the week cooperates. There have to be consequences for missing the standard and rewards for beating it. Without those, the standard becomes one of those corporate slogans people learn to recite but never believe. So the next time you spot one of these stumps, hold off on the yelling. Look at the culture you built. You reap what you sow. Don't act surprised when you get exactly what you grew.