top of page

What’s Below the Redline? Making Delivery Commitments Credible

Nov 14
6 min read

A credible delivery commitment requires leaders and teams to confront uncomfortable tradeoffs while they still have options.


A quarterly planning or PI Planning event can produce objectives, schedules, and a board full of dependencies. By the end, everyone may have a clear picture of what the organization intends to deliver. Whether the organization can honor that commitment requires a closer look.


As a SAFe Practice Consultant, I look for four things: clear prioritization, owned dependencies, leadership participation, and an honest confidence vote. I pay particular attention to the conversations people hesitate to have. Those conversations often reveal the difference between a plan people have accepted and a commitment they believe they can deliver.


Have the uncomfortable prioritization discussion now


During planning, I ask: "What's below the redline?" The redline is the boundary between the work the team is committing to and the work that sits outside available capacity.


In one planning session, I asked that question. The product manager's eyes widened. The architect started to stutter. Within a minute, two positions were on the table. The architect wanted the line visible so everyone could see what would not get done. The product manager did not want the plan to show that everything could not be accomplished.


That was the conversation the room had been avoiding. It was also the most valuable one we had that day, because it happened while we could still change scope, sequencing, and capacity. I would rather have that hard discussion during planning than two weeks before delivery.


At the planning event, we still have options. Close to delivery, those choices become more constrained and their consequences more immediate.


The redline exposes differences in expectations. A leader may consider an item essential even though the team has placed it outside available capacity. Another program may depend on work we have deferred. A stakeholder may have already communicated a date the delivery team never agreed to meet.


Work below the line may still be valuable. Leadership, teams, and stakeholders need to understand what is included and excluded. If something moves above the line, we need an explicit decision about what moves below it or what additional capacity becomes available.


Patrick Lencioni’s The Five Dysfunctions of a Team connects the avoidance of productive conflict with weaker commitment. His model describes how preserving harmony can suppress debate and how a lack of clarity and agreement undermines commitment. The redline discussion gives people an opportunity to challenge priorities and understand the decision. [1]


Understand the impact of falling short


Once that boundary is visible, I ask: "If everything doesn't get done, what's the impact?"


A regulatory obligation, a customer commitment, an internal improvement, and an exploratory capability can appear in the same plan. Their consequences differ, and those differences should influence delivery decisions.


This discussion can also expose dependencies that were easy to overlook. Something that appears optional within one team's plan may enable another program's critical milestone.


Understanding the impact gives teams a stronger basis for making tradeoffs during execution. It helps leadership recognize where intervention may be required. A commitment becomes more credible when the people making it understand the consequences behind it.


Give dependencies owners who acknowledge them


Identifying a dependency is only the beginning. I want to know who owns it, when it is needed, and whether the people expected to fulfill it have agreed to that expectation.


That is why integration partners belong in planning. When delivery depends on DevSecOps, centralized QA, or penetration and performance testing teams, their availability can determine whether the plan is achievable. A development team may have the capacity to finish its work while the organization lacks an available test environment, integration window, or security review slot.


Each important dependency needs an owner who can confirm the commitment, communicate changes, and help resolve issues. A name on a board provides limited assurance if that person has never acknowledged the expectation.


Involve leadership while decisions can still change


Leaders can sometimes see dependencies and competing demands across programs that individual teams cannot. Several initiatives may be competing for the same specialists. Milestones may conflict across programs. One outcome may need to take precedence over another.


That perspective is most valuable while the plan is being formed. Early involvement lets leaders clarify business consequences, resolve competing priorities, and address constraints teams cannot resolve themselves. It also makes leadership accountable for the conditions delivery requires. If the plan depends on a staffing decision, a priority change, or support from another organization, that responsibility should be visible.


How leaders participate matters as much as whether they attend. People need to be able to explain why a plan is at risk without feeling they are challenging the leader's authority.


Protect the confidence vote


The confidence vote is the moment each participant rates, usually on a scale of one to five, how confident they are that the team can deliver the plan. In my experience, it is often shortened or dropped when time runs short. The vote often disappears because the facilitator is not prepared to manage the conflict it may expose.


Skipping the vote does not remove the doubt. It sends the doubt into delivery.


These discussions require a skilled facilitator who can surface disagreement, keep the focus on the plan, and guide the group toward a decision or an adjustment.


I treat a low score as an opportunity to understand what may prevent delivery. I ask people to explain the concern behind the number, keep the focus on the plan rather than the person, and guide the group to a decision or an adjustment.


By this point, participants have examined the objectives, capacity, dependencies, and risks. Their judgment about whether the plan is achievable is valuable information, and we need enough time to hear it and act on it.


Listen beyond the score


During the vote, I pay attention to more than the number. I notice hesitation. I notice the person who looks toward a senior leader before voting. I notice when someone changes their score after a more influential person speaks.


Those observations do not establish what someone is thinking. They signal that there may be more to discuss. A lower vote may reveal an unresolved dependency, an unrealistic capacity assumption, or a concern that never reached the main conversation.


Amy Edmondson’s research across 51 work teams in a manufacturing company found that psychological safety was associated with learning behavior. Her study did not test confidence voting as a predictor of delivery. For planning, it provides a useful foundation for considering how the environment affects people’s willingness to raise concerns and acknowledge uncertainty. [2]


Watch how hierarchy shapes the vote


A confidence vote can reflect pressure to agree. If a senior leader expresses strong confidence first, others may hesitate to offer a different judgment. The result can look reassuring while concealing real uncertainty.


One practical approach is to have participants choose their votes independently and reveal them together. Then make space for people to explain lower scores, and address the concern before asking anyone to reconsider.


Leaders can help by acknowledging their own uncertainty and welcoming information that challenges the plan. Their response teaches the room how safe it will be to speak up next time. The facilitator keeps the discussion on the conditions required for delivery and makes sure the person who raised a concern does not become the problem.


Make room for the signals a call can hide


I miss this about collocated teams. In person, you could see hesitation, notice a glance between colleagues, or pick up a conversation after the formal discussion. There was also a sense of accountability in making a commitment with the people who would depend on it in the room.


On a call, those signals are easier to miss. Virtual planning requires more deliberate participation. Silence needs a follow-up. Dependency owners need to acknowledge their commitments out loud. People need a clear opportunity to explain concerns. Independent voting and explicit discussion help surface judgments that might otherwise stay hidden.


Build confidence on shared understanding


At the end of planning, everyone should understand what sits above and below the redline, what happens if important work slips, who owns each dependency, and where uncertainty remains. Leadership should understand the decisions and support required to make delivery possible.


The uncomfortable discussion belongs here, while there is still time to act.


I use a modified PI Planning event spreadsheet to support these conversations across two days of planning spread over two weeks. The structure helps, but the value comes from the discussions and decisions it enables.


If you are seeing a recurring gap between planning confidence and delivery results, start with NBD Consulting Services’ AAMP Delivery Performance Diagnostic. The diagnostic helps you examine the conditions behind delivery performance and identify where to focus improvement.





About the Author


Duane L. Nicholson is the founder and Chief Transformation Officer of NBD Consulting Services, a Fractional Executive & Strategic Advisor, and a SAFe Practice Consultant (SPC). He helps organizations strengthen technology delivery, align investment priorities, and turn transformation strategy into measurable outcomes. His experience includes work with DTCC, Experian, Amgen, Toyota Financial Services, and Pacific Life.


References


[1] Patrick Lencioni. The Five Dysfunctions of a Team. Jossey-Bass, 2002. See The Table Group’s overview of the model. Read the model overview


[2] Amy Edmondson. “Psychological Safety and Learning Behavior in Work Teams.” Administrative Science Quarterly, volume 44, issue 2, 1999, pages 350 to 383. Read the research

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page