5 min de lectura
Delegate without lowering the bar: letting go without letting quality slip
Many leaders delegate the task but not the standard, and end up reviewing the same work twice. Adrián Gómez explains how to let go without lowering the bar.
Adrián Gómez
COO · 4 Nov 2026
Índice de contenidos
Letting go of the task without letting go of the bar
Delegating sounds simple and rarely is. Many leaders learn to hand out tasks, but not the standard those tasks must meet. The result is a busy team and a leader still reviewing every deliverable as if nothing had actually been delegated.
- Delegating the task without delegating the standard forces you to review the same work twice.
- A leader who doesn't let go of the bar isn't really letting go of time either.
- A team matures when it can decide without asking, not when it executes without thinking.
The delegation that ends in double review
We see managers who hand off a whole project and then rewrite every delivery because "it didn't come out the way I would have done it". The problem isn't the team's quality, it's that nobody ever defined what "done well" meant before starting.
That constant correction costs more time than doing it yourself, and it also sends a quiet message: around here, nobody decides except the boss.
- Deliverables that come back corrected without anyone explaining the real standard.
- Follow-up meetings that turn into line-by-line rewriting.
- Teams that stop proposing because it's going to be changed anyway.
The standard lives in the prior conversation, not in the final correction
Our reading is that the standard isn't protected by correcting at the end, it's protected by agreeing the criteria at the start. Delegating well begins with a clear conversation about the expected outcome and which limits are non negotiable.
“Delegating doesn't lower the bar, it hands it over before the work starts.”
— Adrián Gómez
COO at People & Play
Done that way, the final review becomes the exception, not the habit.
Three moves to delegate without losing quality
You don't need to let go all at once. You need a sequence that hands over judgement before tasks.
- Agree the outcome before the method
- Describe what a job well done will look like, not only what has to be delivered.
- Leave the how open, leave the what and the why very clear.
- Define the threshold that requires asking again
- Mark in advance which decisions the person can take alone and which need consultation.
- Without that threshold, everything seems to deserve a question, or nothing does.
- Review the criteria, not rewrite the outcome
- If something doesn't meet the standard, explain why before fixing it.
- Rewriting without explaining teaches dependence, not judgement.
Questions before delegating the next key task
Before delegating the next important project, it is worth asking:
- Does the person know what an excellent outcome looks like, or only the deadline?
- Which decisions can they make without consulting me, and which not?
- How many times have I rewritten a deliverable without explaining why it didn't meet the standard?
- Am I delegating the task, or only delegating the heavy lifting?
- What would happen if I reviewed nothing this week before it gets delivered?
Delegate like passing the ball, with a plan behind it
Delegating well doesn't lower the standard, it multiplies it, because it stops depending on one person reviewing everything.
If you want to build a delegation system that sustains quality without the leader reviewing every delivery, let's talk. It usually starts by agreeing the criteria before the task.