Pull Planning Homework

Pull Planning Homework: The Best Sessions Are Won Before Anyone Walks in the Room

The best pull plan sessions are won before anyone walks in the room.

Here is the deal. I have watched too many pull plans turn into guessing sessions. Trade partners standing at the board, making up durations on the spot, committing to handoffs they have not actually thought through. That is not planning. That is improvising with sticky notes, and the sequence built from that improvisation rarely survives contact with the actual work.

The Pain of a Room Full of Guesses

Picture a typical pull plan session run without preparation. A facilitator asks the mechanical trade how long their rough in will take in a given zone. Someone glances at the milestone, does quick mental math, and offers a number that sounds reasonable but was never actually derived from a real breakdown of the activities involved. The structural trade is asked what they need before they can issue a foundation plan, and the honest answer requires knowing exactly which upstream deliverable they depend on and who owns it, information that nobody in the room has actually confirmed before the meeting started.

Every one of those on the spot answers becomes a sticky note on the board, and the board looks complete once the session ends. But a schedule built from guesses is not a schedule. It is a collection of plausible sounding commitments that nobody actually verified before agreeing to them. When the plan starts to slip, and it does, the root cause traces back to a duration that was never real or a dependency that was never actually confirmed, both of which could have been caught before the session ever started if anyone had done the work of preparing first.

The Failure Pattern

The failure pattern is treating the pull plan session itself as the place where planning happens, rather than as the place where already completed planning gets connected across disciplines.

A pull plan session has a specific, narrow purpose. It exists to take each discipline’s own understanding of their work and link it to every other discipline’s understanding, creating a sequence that reflects real dependencies rather than an assumed order. That purpose only works if every discipline arrives already knowing their own deliverables, their own workflow, and their own needs. When trades instead use the session itself as the place to first figure out their own scope and durations, the session collapses into two jobs happening simultaneously, individual planning and cross discipline coordination, and doing both at once produces worse results at both than doing either one properly.

They Didn’t Fail the System

When a pull plan session produces a schedule that falls apart within the first few weeks, the instinct is to blame the trades for bad estimates or poor commitment. They should have known their durations better. They should have thought this through.

Before reaching that conclusion, ask what those trades were actually given before walking into the room. If nobody structured an expectation that each discipline arrive with their deliverables, workflow, and needs already worked out, then asking for accurate durations and honest dependencies on the spot is asking people to do serious analytical work under social pressure, in front of every other trade, in real time. That is not a fair test of anyone’s planning ability. It is a structural setup that all but guarantees the numbers that come out will be optimistic, vague, or simply invented to keep the session moving.

What Pull Planning Homework Actually Requires

Before the session, every discipline prepares three specific things, and each one answers a different question that the pull plan session depends on already being answered.

Deliverables define the condition of satisfaction for each handoff, the specific, concrete output that discipline is responsible for producing and passing to the next trade. This is not a vague description of scope. It is a precise statement of what “done” actually means for that handoff, because a pull plan sequence only holds together if every trade agrees on what completion actually looks like at each interface point.

Workflow lists the actual activities that discipline will perform to produce each deliverable, along with realistic durations for each one. This is where the guessing problem gets solved directly. A duration produced by actually breaking work into its component activities and thinking through how long each one genuinely takes is a fundamentally different number than a duration offered on the spot in front of a room full of people waiting for an answer. The first number is honest. The second number is a social compromise between accuracy and the pressure to keep the meeting moving.

Needs identify exactly what that discipline requires from others, and precisely who must provide it. This is the piece most frequently skipped in unprepared pull plans, because it requires each trade to think backward from their own work to the specific upstream deliverables they depend on, and to know exactly which other discipline owns each of those deliverables. A structural engineer who has done this homework walks in already knowing they need the preliminary wall and foundation analysis before they can issue the foundation plan, and they know exactly who owes them that analysis. That specificity changes the entire conversation.

Why Preparation Changes the Conversation Itself

When a trade shows up to the board having already done this homework, the pull plan session stops being a place to figure things out and becomes a place to connect things that are already figured out. The structural engineer who already knows their dependency and who owns it is not guessing when that conversation comes up. They are confirming, negotiating a specific date, and locking in a commitment that both sides can actually stand behind.

This shift matters because it changes what “commitment” actually means in the room. A commitment made after genuine preparation is a real promise, backed by an actual understanding of the work involved. A commitment made on the spot, without preparation, is closer to a hope, offered because the format of the meeting requires an answer and nobody wants to be the person holding up the session. Both look identical on the board as a sticky note with a duration written on it. Only one of them is likely to actually hold once the work begins.

The Sequence Only Holds When the Inputs Are Real

Pull planning works by starting from the milestone and working backward, each discipline defining what they need from the trade before them in the sequence. That backward logic is powerful, but it only produces a reliable schedule if every discipline’s inputs into that logic are real. A sequence built from honest durations and confirmed dependencies holds because it reflects how the work actually happens. A sequence built from optimistic guesses and unconfirmed assumptions about who owes what to whom looks identical on the board but will not survive the first week of real execution, because the underlying logic it was built from was never true in the first place.

This is exactly why the homework matters more than the session itself, even though the session is what everyone remembers and what looks impressive on a wall covered in color coded sticky notes. The sticky notes were never the magic. The magic is the preparation that made those notes trustworthy, the conversation that happens once trades arrive already knowing their own work, and the promises made between people who have done the thinking necessary to make those promises honest.

How to Actually Complete the Homework

Review the phase being pulled and understand the overall scope of work involved before attempting to break down individual activities. Think through all table work, major activities, and approximate durations for the discipline’s own scope, building a genuine understanding before translating it into specific line items. For each activity, identify exactly what is needed and from whom, rather than leaving dependencies vague or assumed. List activities working backward from the final milestone, since pull planning logic flows in reverse from the goal rather than forward from the start.

Be brief. Each activity and each need should fit on a three by three inch sticky note, forcing genuine clarity rather than vague, paragraph length descriptions that sound thorough but communicate nothing precise. Focus on the work and handoffs relevant to other disciplines, not an exhaustive internal breakdown that nobody else in the room actually needs to see. During the meeting, place notes in the planning line linking each activity to the milestone, keeping the visual logic of the sequence intact as it gets built collaboratively. And as a team, work backward through the board, negotiating and committing to additional needs as they surface in real time, because even the best preparation will not eliminate every cross discipline conversation, it simply ensures those conversations start from real information instead of guesses.

Signals Your Team Is Improvising Instead of Planning

Look for these patterns in your own pull plan sessions:

• Trades offering durations on the spot without any visible reference to a prior breakdown of their own activities
• Dependencies discovered for the first time during the session rather than identified in advance
• Commitments made under visible social pressure to keep the meeting moving rather than genuine confidence in the number
• A schedule that looks complete on the board but starts slipping within the first few weeks of execution
• No expectation set in advance that trades should arrive having already thought through their own deliverables and needs

Each of these signals a pull plan built on improvisation rather than preparation, and that gap is exactly what Pull Planning Homework is designed to close.

Prepare Before the Next Session

Here is your challenge. Before your next pull plan session, send every discipline the homework requirement explicitly. Deliverables. Workflow. Needs, with names attached. Do not let the session be the first time anyone thinks through their own scope. Let it be the place where already prepared work gets connected into a sequence everyone can actually trust.

Jason Schroeder puts the whole philosophy in four lines: plan the work, work the plan, respect the people, improve every day. The sticky notes were never the magic. The preparation is. Do the homework, and watch the sequence actually hold.

On we go.

FAQ

How much time should a trade partner spend on this homework before a pull plan session?
The time investment scales with the complexity of the phase being pulled, but even a modest amount of deliberate preparation, reviewing the scope, listing major activities with honest durations, and identifying key dependencies, produces dramatically more reliable commitments than arriving with no preparation at all. The goal is genuine thought, not exhaustive documentation.

What happens if a trade partner shows up without having done the homework?
Their commitments in that session are far more likely to be guesses rather than honest estimates, and the resulting schedule inherits that unreliability at exactly the points where that trade’s work connects to everyone else’s. Facilitators should treat homework completion as a genuine prerequisite for a session producing a trustworthy schedule, not an optional nicety.

How specific should the “needs” section actually be?
Specific enough to name both what is needed and exactly who owns providing it, not a general acknowledgment that dependencies exist. The structural engineer example in this practice, knowing precisely that they need the preliminary wall and foundation analysis and knowing exactly which trade owes it to them, is the level of specificity that actually changes the quality of the conversation during the session.