LEARN. PRACTICE. GROW.Delegation changes the work, not every authority
A colleague prepares an intervention plan, but the mandate excludes execution authorization. While the lead is absent, a stakeholder requests just an OK. Message brevity does not reduce the decision’s effect. The colleague can continue permitted preparation and refer authorization to the designated substitute with context and options. Status should remain pending until a decision exists. Before delegating, also specify stop conditions: in the example, correcting test data is permitted, but encountering actual data requires stopping and consulting the owner. Knowing the technique is insufficient. For a first complete cycle, agree an initial outcome review and criteria for seeking help. Follow risk points without approving every sentence or taking the whole task back whenever a question appears. Support and autonomy can therefore coexist, with responsibility proportionate to the agreed scope.
Make commitment conflicts decidable
Two business areas request top priority within the same window. Confirming both transfers the contradiction to the people executing work. If the local agreement assigns the decision to the service owner, the Team Lead gathers consequences, alternatives, and dependencies for that decision. A local three-item active limit is not a universal Kanban rule. In the exercise, policy requires treating existing work before admitting urgency. Relabeling an item as waiting does not finish the work or free the person. Check whether interruption is technically possible and which commitment would move. When the team accepts a task only if access arrives by Tuesday, report the condition, owner, and deadline. A received message is not confirmed access. Keep concrete follow-up so the dependency does not disappear between different teams’ boards. Compare reports using stable definitions of what each item represents.
Participation and feedback with evidence
A colleague speaks little in English meetings but sends useful risks beforehand. Calling her disengaged ignores available evidence and presumes intent. Discuss the expected contribution and ask which format supports participation; do not infer preferences from nationality. The aim is getting relevant information into decisions. Also avoid assessing a week solely by ticket count when someone spent agreed time on training or support. Record the contribution and observe its result without creating fictional tickets to compensate for the count. If the team disagrees between a short meeting and written updates, it can try a reversible option with a deadline, participation rules, and evidence of timely blocker detection. The experiment should not remove necessary urgent channels. At review, compare observed effects with the objective instead of declaring the lead’s preference the winner. Neither meeting attendance nor speaking frequency alone establishes professional value.
Coordination exercise and English handover
Prepare a 25-minute session with a Team Lead, service owner, and delegated colleague. Use the uncovered-window and competing-urgency cases. During the first five minutes, each role identifies facts, conditions, and decisions within its authority. For ten minutes, negotiate a proposal showing coverage, additional effort, and affected commitments. In the next five, introduce an informal authorization request outside the mandate. In the final five, produce an English handover and compare records. An original example is: Import finished; reconciliation is pending. Marta will check totals by 14:00 UTC and report differences. The rubric observes whether the person distinguishes completion from pending verification, respects boundaries, assigns follow-up ownership, and explains capacity units. This session was designed but has not been conducted with human participants. The previous lesson’s Python model confirms only synthetic data, not the quality of actual negotiation.
Import finished; reconciliation is pending.
Marta will check totals by 14:00 UTC and report differences.
Execution authorization remains with the designated service owner.“Consider changing the window” authorizes analysis; it does not establish a decision to “execute Friday”. Confirm the decision before publishing that commitment.
Common pitfalls
Treating urgency as authority; silence as agreement; ranking people by speaking; confusing preparation with authorization.
Related topics: Working agreements · Feedback and development
Coordination makes explicit what was decided, what needs confirmation, and who can resolve the next gap.
Reference: Effective delegation · Atlassian Team Playbook, GitLab leadership handbook, Google SRE, Kanban Guide May2025 and DORA five-metric model; inspected 2026-10-01