Workstream Leads Need the Ball

If every meaningful decision returns to you, adding workstream leads can give you more people to coordinate without giving the team more ability to act.

The lead gathers information and recommends a decision. You decide; they implement it. Everyone is busy, but the same person still limits how many decisions the engagement can make.

I have found that, as work grows across several streams, the people leading those streams become central to the success of the whole engagement. They need to understand the wider purpose, make decisions, and support each other. They become a leadership team through the responsibilities they carry together.

A useful soccer analogy is the player receiving the ball. The coach prepares the team, establishes expectations, and helps players interpret what is happening. The player still needs room to act. Requiring permission for every pass would defeat the purpose of having capable players on the field.

Jürgen Klopp described the confidence behind his approach to leadership this way:

“

My confidence is big enough that I can really let people grow next to me, it’s no problem.

Engineering decisions have different consequences, and some require formal approval. The practical question is what a lead can genuinely decide, with what support, and where that authority ends.

Choose for judgment as well as technical depth

Technical expertise matters. A lead needs enough understanding to recognize consequential trade-offs, challenge assumptions, and know when specialist help is necessary.

Leading a workstream also involves making progress when the information is incomplete, explaining uncertainty without creating confusion, and keeping relationships productive under pressure. The strongest leads I have seen communicate proactively and create alignment across boundaries. They help other people act.

Look for evidence in ordinary work. Who makes a dependency visible before it causes delay? Who can explain why a decision matters to another team? Who changes their view when new evidence arrives? Who raises an uncomfortable issue clearly without making the discussion personal?

Do not limit the search to people who already hold a leadership title. Give promising people a bounded stretch, a clear source of support, and access to the context the role requires.

Equally, avoid assuming that your strongest specialist wants to coordinate a workstream. Discuss the work and its demands with them. Treat leadership as a responsibility to understand and support, rather than a reward that someone is expected to accept.

Build a leadership team across reporting lines

In a multi-workstream engagement, the people you coordinate may report to different managers. Delivery leadership does not automatically give you authority over staffing, performance reviews, budgets, or priorities outside the engagement.

Make those limits explicit. Agree the lead's remit with the people who control the relevant resources and commitments. If a person is assigned responsibility without enough capacity or authority, calling them accountable will not resolve the mismatch.

Then give the leads time together to work on the whole engagement. A meeting where each person reads their own status update is a weak substitute for that work.

Use the shared time to examine dependencies, conflicting priorities, emerging risks, and decisions that affect several streams. Ask what one workstream needs from another and whether local plans still add up to the outcome everyone agreed to deliver.

Share context early: a changed stakeholder priority, a concern about operability, or an assumption that may no longer hold. A lead who learns these things only after proposing a plan has to redo work you could have helped them avoid.

The aim is for leads to understand enough of the whole picture to make compatible decisions, including when you are absent.

Delegate an outcome with the means to achieve it

“Own this” can hide very different expectations. Clarify whether it means deliver an outcome, coordinate a discussion, or seek approval before doing anything consequential.

To make ownership concrete, work through these questions:

• What outcome does the lead own, and how will we recognize progress?
• Which decisions can they make independently?
• Who must be consulted before a decision, and who only needs to be informed?
• Which people, capacity, and specialist support are actually available?
• Which limits require approval or escalation?
• Who takes over when the lead is unavailable?

The resource question is particularly important. If every request for specialist time or a change in sequencing requires a new negotiation, the lead needs an agreed route to the person who can resolve it. Do not imply that you have delegated control over resources you do not possess.

Write down the answer where the affected teams can see it. The lead and the people they work with should have the same understanding. A private assurance from you will not help much if everyone else still expects your approval.

An illustrative ownership agreement

Consider a fictional integration workstream connecting two internal services. This example shows the level of clarity to aim for; the precise boundaries should fit your organization.

Outcome. The workstream lead owns delivering an agreed, supportable interface and coordinating the evidence needed for its acceptance.

Independent decisions. The lead can sequence the work within the agreed capacity, choose implementation details within existing architecture and security requirements, and resolve routine defects within the workstream.

Consultation. Changes to the shared interface require consultation with the consuming team and the designated architecture owner. Consultation has a named response expectation and a route for resolving disagreement, so silence does not become an indefinite veto.

Reserved decisions. Changes to committed external dates, additional spending, new security exceptions, or scope that affects another team's obligations go to the authorized decision owner. The lead brings the impact, options, and recommendation.

Resources. The agreement names committed engineering capacity, access to test environments, and the contact responsible for arranging specialist support. Any gap is recorded as a constraint rather than assumed away.

Visibility. The lead records consequential decisions and shares emerging risks through the agreed channel. Routine visibility does not create a new approval requirement.

Cover. A named deputy has access to the same context and knows which decisions they can make during an absence.

This agreement will need revision as the work changes. Its value is that it gives the team a shared starting point and makes gaps discussable.

Make escalation part of good judgment

A capable lead should know when to ask for help. Treating escalation as failure encourages people to hold problems until their options disappear.

Agree triggers early. Useful examples include a dependency that threatens another workstream's commitment, a decision outside the lead's authority, unresolved disagreement between accountable owners, or a risk that could affect security, service reliability, cost, or an external promise.

Define urgency as well as destination. An active production incident cannot wait for the next weekly leadership meeting. A reversible sequencing choice within the lead's remit usually can be made and recorded without interrupting everyone.

Keep the request for help practical: what decision is needed, by when, what happens if it waits, which options exist, and what the lead recommends. Where the situation is still developing, say what is known and what remains uncertain. Complete certainty should not be an entry requirement for getting support.

You have responsibilities in this arrangement too. Respond, find the right decision owner, or agree when an answer will come. Escalation that repeatedly disappears into a queue teaches people that the process cannot help them.

Stay close enough to coach

Delegation works best when the lead has access to your context and judgment without needing your permission for everything.

Meet regularly enough to understand the decisions ahead. Ask about assumptions, alternatives, dependencies, and the concerns they have not yet resolved. Share why you see a risk or prefer an approach. That gives the lead something reusable beyond the answer to today's question.

There will be times when urgency requires direct intervention. Make the reason clear, stabilize the situation, and return ownership deliberately afterward. Review the decision together when the pressure has passed. A necessary intervention should not silently become a permanent change in authority.

Allow different approaches where the outcome and constraints permit them. If you repeatedly replace a sound decision because you would have chosen differently, the team learns to wait for your preference. Over time, you can end up mistaking that learned caution for a lack of initiative.

Try the two week absence test

One question has become a useful check on whether ownership is real: if I were unavailable for two weeks, would this workstream continue making good decisions?

Use it as a tabletop exercise before relying on it in practice. Take the next few consequential decisions and ask:

• Who would make each decision, and does everyone affected know that?
• What context or access currently exists only with me?
• Which approval would wait, and who is the authorized backup?
• Could the lead obtain help or resolve a cross-team conflict?
• Would anyone feel obliged to interrupt my absence because the agreement is unclear?

A gap is useful information about the operating arrangement. Fix it by clarifying authority, sharing context, arranging cover, or securing the resource commitment that was missing.

Some decisions must wait for specific authorized people. Record those exceptions honestly. The test is about continuity within legitimate boundaries, not making every decision independent of governance.

What to change this week

Choose one workstream. Sit down with its lead and write the decisions they own, the resources they can rely on, and the situations in which they should seek help. Check that understanding with anyone whose authority or capacity the agreement depends on.

Then review one decision they recently brought to you. Could they have made it with better context or clearer authority? If so, change the arrangement before the next decision arrives.

The leadership team becomes stronger when its members can act together with confidence. Give them the context, support, and authority that make that possible. Then leave enough space for their judgment to develop.

Sources

1. Jürgen Klopp, Liverpool FC interview about leadership, Liverpool FC, 25 May 2019.