Coaching, impediments and purpose

Choose the support the person needs

Start by distinguishing missing knowledge, difficulty reasoning and missing authority. Someone who has never used a tool may need a demonstration and supported attempt. Someone who already understands the options but hesitates over a trade-off may benefit from questions about criteria and consequences.

A colleague’s experience can add useful examples when differences between contexts are discussed. None of these interventions alone resolves a decision requiring external authorization. Support should respond to observed need and available time.

During an incident requiring an immediate decision from the available authority, containment should not wait for a development conversation. Reasoning can be reviewed afterward, preserving a learning opportunity.

Coaching, mentoring and observable practice

A coaching conversation should help someone explore their reasoning when the decision belongs to them. Asking questions until the person gives an answer secretly chosen by the facilitator still directs the decision. If there is a recommendation, present it as such and explain its basis.

In mentoring, previous experiences can broaden options but do not guarantee the same result will recur. Connect support with observable practice. “Improve analysis” can become preparing two analyses and explaining assumptions, alternatives and limits against agreed criteria.

Then review the outcome and choose the next development opportunity. Training hours, satisfaction or downloaded documents inform aspects of the experience; they do not establish independent performance of the skill.

Give feedback and create usable autonomy

Useful feedback describes an observation and its effect instead of labeling the whole person. If someone interrupted three colleagues, discuss how to let contributions finish and how to observe change at the next meeting. Behavioral improvement needs practice opportunities and proportionate follow-up.

Autonomy also needs concrete conditions. Agree which decisions are delegated, their limits and escalation situations. If the leader changes every choice without explaining criteria, the team learns to await approval despite messages of trust.

Respecting choices within the mandate does not prevent intervention when a condition lies beyond it. A 5,000-euro investment limit does not allow the team to approve 6,500 euros independently; it enables recognition of the gap and a request for an appropriate decision.

Reserve capacity to develop competence

Learning consumes time from the learner and, where applicable, the person supporting them. Record whether an estimate already includes both to avoid omitting or double-counting hours. In a week with thirty available hours, twenty delivery hours and eight supported-practice hours leave two free hours.

If the eight already include three mentor hours and five learner hours, those components are not subtracted again. Delivery commitments should reflect the learning reserve. To reduce dependency on a specialist, combine explanation, practice and demonstration by another person instead of assuming transfer because a guide was sent.

If urgency requires specialist intervention, later revisit how to restore the learning opportunity without pretending it happened.

Turn an impediment into a decision

Describe the blocked outcome, impact and conditions before selecting a solution. “The process does not work” may hide different mechanisms. Working and waiting records help distinguish missing execution capacity from delayed authorization.

If eight of ten days are external waiting, doubling the team does not guarantee halving lead time. For a decision beyond team authority, prepare impact, options, an explicit request and when the decision matters. Involve whoever controls the constraint.

Escalation is more than an activity list or generic request for help. Priority between impediments should consider agreed criteria: restoring an unavailable service may take precedence over unblocking more deliveries with no imminent deadline.

Check resolution and address recurrence

Distinguish containing an effect, correcting a condition and preventing recurrence. Authorized containment can reduce impact while cause investigation continues. Closing a repair ticket does not prove the consumer can complete their request.

Define needed functional evidence and observe it under relevant conditions. If three teams use different configurations and only one confirmed operation, record that scope and follow up with the other two. Missing confirmation does not mean demonstrated failure.

When a leader’s personal intervention removes a blocker, examine whether the same rule will affect new requests. Agreeing policy, ownership and follow-up can reduce future dependency; making the leader’s personal contact the sole permanent route may perpetuate it.

Use shared purpose to choose

Purpose supports choice when it connects work to an observable outcome and explicit limits. Delivering eight screens does not explain which customer task should improve. Fewer calls may appear positive, but not if customers can no longer request help and take longer to resolve their problem.

Discuss outcomes with affected groups and expose costs and effects shifted between teams. Revisit incentives rewarding request transfer when the objective is end-to-end resolution. If a discovery changes expected usefulness, present it to whoever can revisit the business objective.

Authority to choose implementation does not imply authority to replace that objective. Preserving purpose requires learning and deciding; it does not require retaining a solution despite evidence.

Common pitfalls

Using coaching to hide an imposed decision; counting training as full delivery capacity; escalating without a concrete request; declaring resolution from ticket state alone.