Applied End-to-End Flow  /  Applied End-to-End Flow: Team  /  Implementation Guidelines

Implementation Guidelines

Companion reference for Applied End-to-End Flow: Team.

By Curtis Hibbs and Joshua Barnes

A team can recognize its delivery problems and still struggle to choose what to change. Several problems compete for attention, some decisions belong elsewhere, and improvement must fit alongside work already promised.

Use this reference after the diagnostic chapters of Applied End-to-End Flow: Team to choose and carry through a first improvement. Bring your Chapter 7 constraint finding, your diagnosis of the barrier affecting the team most, and your amplifier check. First check who can act and whether a team condition is preventing improvement from holding. Then choose the relevant starting move from Chapter 9 and carry it through the improvement process in Chapter 8.

The guidance applies to software and other kinds of delivery. Read intake, verification, handover and evidence of use in the terms of your team’s work.

Find Your Starting Point

Bring forward the phrase from Chapter 7’s locating exercise, section 7.4: your waypoint, the named constraint, and its control class. Read it alongside your barrier diagnosis and amplifier check. These findings answer different questions:

Finding	How it guides the choice
Waypoint	Where does the constraint sit in the team’s work and surrounding system? Use the boundary tests you completed to check whether a move assumes a capability, such as visible work, that the team has not established.
Named constraint	What specifically is limiting delivery? Keep the improvement focused on that obstruction.
Control class	Who has authority to change this constraint? This determines whether the move needs team action, a partner or escalation. The waypoint alone does not settle authority.
Barrier	What kind of problem is affecting the team most? This selects the starting direction: outcome anchoring, improving flow or repairing feedback.
Amplifier	Is a team condition preventing improvement from holding? If so, addressing it becomes the first improvement, as explained in the next section.

For example, Delivery Edges / release authority (external) describes a team whose finished work waits on a release decision it cannot make. Own Mechanics / verification latency (team) describes a team whose own verification work limits finishing. Both experience delay, but their first moves need different people and different authority.

If you have not completed the locating exercise, do that before choosing a move. Use its boundary tests and supporting observations; a painful incident or an attractive practice does not establish your team’s position. When review shows that work is now waiting somewhere different, repeat the exercise before continuing with the old diagnosis.

The three control classes translate into different actions:

• Team-controlled: choose a change within the team’s actual authority and available capacity. Name who will do the work and what result you will examine.
• Jointly controlled: involve the other party before changing the shared arrangement. Agree what each side will do and what evidence you will review together. If agreement stalls, record what remains unresolved and take the request to whoever can settle it, using the escalation approach below.
• Externally controlled: prepare an evidence-backed request for whoever can change the constraint, using the escalation record below. Continue improving the work your team controls while that request is considered.

Check authority against the real decision, not the apparent size of the change. Altering a required approval or a mandated intake rule can belong elsewhere even when the work to alter it looks small.

Check What Could Undo the Improvement

Before choosing a barrier-specific move, revisit the four team amplifiers defined in Chapter 2 and applied in Chapter 9, section 9.5. They make the barriers harder to address and can undermine an improvement after it begins:

• Trust Erosion: commitments no longer seem credible. Start with small commitments the team can keep. Where commitments outside the team were broken, record what was promised, what happened and its effect on the work. Take that evidence to the people who can change the arrangement, using the escalation record below.
• Accountability Avoidance: improvement items have no one responsible for carrying them through. Where this is a habit of leaving actions unassigned, name an owner for the work. If accepting ownership exposes people to punishment, record the condition and seek a change from those who control it; repeatedly asking for a volunteer does not address that problem.
• Micromanagement Creep: repeated oversight adds waits and interrupts decisions. Make the work and its risks visible, and document what the checkpoints cost alongside the protection they provide. Take a proposed checkpoint change to whoever has authority to decide it.
• Burnout Accumulation: improvement arrives as another demand on an exhausted team. Make existing commitments and unplanned work visible, then size the improvement to real capacity. Where mandated demand exceeds that capacity, take the recorded gap to the people who control the demand.

Use recent improvement attempts and current commitments as evidence for this check. You do not need to try the new barrier-specific move and watch it fail first. If you have no evidence that one of these conditions is preventing follow-through, proceed with the barrier-specific move and check again at review.

When one of these conditions is preventing improvement from holding, make addressing it your first improvement. Use the ownership and review process below. Return to the barrier-specific move once a small improvement holds from one review to the next, even if the condition has not disappeared.

Choose Your First Move

The book diagnoses three barriers: Alignment Drift, Choked Flow and Broken Feedback. Use the one affecting the team most to find the relevant starting move below, then carry that direction through VAP. If that diagnosis is still unclear, return to Chapters 3-6 before choosing. The Three Barriers provides a framework overview.

Check the starting direction against your locating exercise. For these moves, the practical readiness question is whether the team can see the work it is carrying. A finding of Invisible Work means establishing that picture first. Making work visible is the first half of the Choked Flow move and a prerequisite for outcome anchoring or reliable feedback. A team further along still checks that its picture of the work is trustworthy. The specific constraint and its control class then determine the scope and people needed.

When Alignment Drift Dominates

Priorities change, requirements get reinterpreted, or work waits for someone who can settle a decision. The starting move is outcome anchoring: identify the result each item is meant to serve and the person who can settle whether it satisfies that intent.

Apply this first to work already in progress. Unanswered questions there are consuming capacity now. Record the unanswered question, when it was asked, and any resulting wait or rework. Keep the conversation about what the work needs, rather than about who failed to provide it.

This move requires visible work. If the team cannot list what it is carrying, establish that picture first. Where intake is mandated, make unanswered questions visible and seek the necessary decision; the team’s diagnosis does not grant it authority to reject the work.

Chapter 9, section 9.2, develops the move and its escalation path.

When Choked Flow Dominates

Work accumulates faster than it finishes, queues remain unexplained, or delivery depends on one overloaded person. The starting move is seeing everything, then finishing before starting.

Bring planned work, incidents, requests and informal commitments into one trustworthy picture on the team’s delivery board or equivalent shared work view. Once the work is visible, defer new starts where your team has that authority and direct the available capacity toward finishing existing items. For a blocked item, record what it is waiting for, who can release it, and how long it has waited.

The useful result is a change in how work moves. A complete board helps the team decide what to start and what to finish; maintaining the board alone does not reduce the queue. If imposed intake prevents the team from controlling starts, use the recorded load and waits to support a decision by the people who control that intake.

Chapter 9, section 9.3, develops both halves of this move.

When Broken Feedback Dominates

Reports look healthy while recurring problems remain, or the team collects results that never affect a decision. The starting move is making one loop tell the truth.

Choose one result the team needs to understand and trace its feedback all the way through: what was delivered, what happened when it was used, who examined that evidence, and what changed as a result. For example, counting support tickets closed answers a different question from checking whether the same problem returns. Name the person who will act on the observation.

Here too, work must be visible before the team can read the feedback reliably. Check who controls the measurement and the decision it informs. A new number with no decision attached remains another report.

Chapter 9, section 9.4, covers the full move, including misleading measures and feedback delayed by external gates.

Carry the Move Through

The starting moves give you a practical direction. The Value Acceleration Process (VAP), applied at team level in Chapter 8, turns that direction into an agreed result, a discovery session, and selected improvement work. The direction can change as discovery and execution reveal more about the problem.

Choose where to run that process before arranging new meetings. Chapter 8’s mini-VAP is VAP fitted to a team’s retrospective: focused discovery and recurring improvement review happen there, with execution between meetings. It uses the same three phases described below, with a smaller scope. It does not omit agreement on the result, discovery, ownership, execution or review.

Use that existing rhythm when it can accommodate the problem and the necessary participants. If the constraint crosses a team boundary, involve the people who experience or control it. If their participation or the attention the problem needs cannot fit the retrospective, arrange a dedicated session using the same process. A small meeting cannot substitute for the participation the work requires.

For example, outcome anchoring suggests examining missing answers on work in progress. The improvement you want might be less rework caused by unresolved intent. Agree how to recognize that result, then use discovery to examine what prevents it. The execution owner selects the work from the resulting backlog. Completing an anchoring exercise alone would not establish that rework improved.

Keep VAP’s three phases distinct:

• Before discovery, Measurable Outcomes establishes the result. Agree what should improve, how you will recognize that improvement, and which stakeholders need to participate. Describe the result before committing to a particular solution.
• During Visual Discovery, participants examine obstacles and opportunities. Use a visual of the problem space to help them look beyond the most familiar complaint, and admit outcome-relevant items to the improvement backlog. The team canvas in the Team Focusing Visual Reference is a starting resource for that preparation. Before discovery ends, name the execution owner, schedule review dates and name the steering group’s initial membership.
• After discovery, Actionable Output puts the backlog to work. The execution owner orders it, selects the next item, delegates and oversees the work or bounded experiment, and brings its evidence to review. Results inform the next decision and the backlog that follows.

The steering group reviews the evidence and decides what continues, changes or stops. At team level, the team can perform that role for work within its authority. Even then, identify who will participate in the reviews. Decisions beyond the team need the people who hold that authority, and membership can change as the work develops.

The execution owner is accountable for keeping that mechanism operating. The person assigned an improvement item is responsible for carrying out that item. One person may perform both jobs, but naming the execution owner does not assign every piece of work.

Before an item starts, make its assignee, scope, available capacity and evidence of success explicit. Put active improvement work on the team’s delivery board so that it competes visibly with other commitments. At review, examine what happened and decide whether to stop, adjust, or continue. Use the complete VAP reference for the execution and review procedure.

Judge progress against the agreed result: fewer waits, less rework, or feedback that changed a decision, depending on the problem. Chapter 9 provides no fixed completion deadline for a first move. Use scheduled reviews to examine the evidence and agree the next bounded step. When the evidence points to a different constraint, repeat the locating exercise before choosing the next move.

Keep External Constraints Visible While You Adapt

An escalation should give the recipient something specific to decide. Describe the constraint, its observed effect on delivery, the change you propose, and the authority needed. Separate observations from estimates. Where a checkpoint protects against risk, examine that protection alongside the delay it creates.

Track the request and its supporting evidence so that it can be followed up. Chapter 8, section 8.6, provides a simple escalation record: constraint, date raised, audience, proposed action, response and status. This tracks the request; it does not replace the explanation and evidence you send. Keep it visible, review outstanding requests and follow up. A request sent once and forgotten leaves the team with no account of what remains unresolved.

While a decision is pending, look for a part of the problem your team can change. If incomplete handovers create avoidable returns, improve what you send. If work repeatedly waits on the same external decision, sequence the work you control so fewer items accumulate behind it. If each side lacks visibility of the other’s work, improve coordination with the people across that boundary. Record the remaining cost so that a workaround does not make the underlying problem disappear from view.

Recognize When Improvement Is Stalling

Look at the work and the decisions it produces:

• The first move keeps expanding. Return to the constraint and choose a smaller piece that can produce useful evidence within available capacity.
• The board improves, but finishing does not. Examine whether starting behavior, waits or completion conditions have changed. Visibility is useful when it affects those decisions.
• An action returns at every review without progress. Check its scope, assignee, capacity and blocker. Another discussion cannot supply missing time or authority.
• A change is implemented but never evaluated. Return to the result you agreed to examine. Installing a practice does not establish that it helped.
• The original constraint has moved. Repeat the Chapter 7 locating exercise before continuing to optimize the old problem.

Use the evidence to choose the next move. It may support continuing the change, altering it, stopping it, or taking a better-supported request to someone with the authority to act.

Further Reference

• The Value Acceleration Process explains the complete discovery, execution and review mechanism.
• The Team Focusing Visual Reference provides the team canvas and an overview of its four zones. Use it to prepare for discovery.
• Applied End-to-End Flow: Team provides the diagnostic chapters, locating exercise and complete starting moves behind these guidelines.

---

Curtis Hibbs and Joshua Barnes are co-creators of Effective Enterprise AI and Applied End-to-End Flow, and co-authors of Applied End-to-End Flow: Enterprise. Their work combines enterprise diagnosis, value-delivery mechanics, and practical intervention patterns across strategy, portfolios, value streams, and teams.