Scrum in Design & Preconstruction!

The Design Team That Got Forced Into Time Scales When They Needed Creative Autonomy

There is an integrated project delivery team working on a complex medical building. Designers. General contractor. Trade partners. All on boarded together. Conditions of satisfaction established. Vision aligned. Cluster groups formed. Meeting schedules set. And the team uses IPD best practices. Break the project into milestones. Pull plan to those milestones using Mural. Transfer plans into V Planner for tracking. Use Last Planner system for weekly work planning. Track percent plan complete. Coordinate across clusters. Everything by the book. And the construction team loves it. Sees sequences clearly. Understands handoffs. Coordinates work. But the designers struggle. Feel pressured. Anxious. Constrained. Because Last Planner forces them into time scales. Weekly commitments. Rigid schedules. And design does not work that way. Creative people procrastinate by necessity. Need iterative thinking time. Cannot commit to finishing complex work in fixed weekly increments when the creative process requires flexibility. So every week, designers make commitments they cannot keep. Fall behind on percent plan complete. Feel like failures. Meanwhile construction team wonders: why cannot designers just commit and deliver like trades? Do they not care? Are they incompetent? No. They are being forced into a system designed for construction execution. Not design creation. Last Planner works brilliantly for sequential construction. But design is not sequential. It is iterative. Requires autonomy. Needs creative freedom. Cannot be locked into weekly time boxes without destroying the process. So designers suffer. Projects delay. Coordination fails. And everyone blames designers. When the real problem is the system. Last Planner is wrong tool for design. Scrum is the right tool. Because Scrum gives designers what they need: small autonomous teams, iterative sprints producing minimum viable products, burn down charts tracking progress without rigid time commitments, and freedom to be creative within structure. Apple uses Scrum. Google uses Scrum. Intel uses Scrum. Why? Because complex creative work requires Scrum’s flexibility. Construction must learn this lesson. Must stop forcing designers into Last Planner time scales. Must start using Scrum in design clusters. So designers can thrive instead of suffer. And projects can succeed instead of delay.

Here is what happens when construction forces designers into wrong systems. A cluster group gets formed on an IPD project. Mechanical systems design. Five designers. One lead. Assigned to develop HVAC, plumbing, and fire protection for the entire building. They pull plan the work. Identify milestones. Break sequences down. Commit to weekly deliverables. And immediately struggle. Because mechanical coordination is iterative. Cannot commit to finishing ductwork routing in Week 3 when structural changes in Week 2 might require complete redesign. Cannot promise equipment selection by Week 5 when owner input in Week 4 might change everything. Cannot lock into rigid timelines when design inherently requires flexibility to respond to discoveries. So designers make commitments hoping nothing changes. Then things change. Always. And commitments fail. Percent plan complete drops. Construction team gets frustrated. Designers feel inadequate. And the cycle repeats. Week after week. Designers committing. Changes happening. Commitments failing. Trust eroding. Until the cluster group stops functioning. Designers withdraw. Stop participating. Make vague commitments. Protect themselves from weekly failures. While construction team labels them as unreliable. Uncooperative. Unprofessional. When the truth is: the system failed them. Last Planner works for construction because construction is sequential. Concrete before steel. Steel before decking. Decking before MEP. Clear sequences. Predictable handoffs. But design is not sequential. It is iterative. Loops back constantly. Discovers constraints requiring redesign. Receives input changing direction. And forcing it into sequential weekly commitments destroys the creative process designers need to produce excellent work.

The real pain is designers who procrastinate by necessity getting punished for it. Research shows creative people procrastinate differently than non-creative people. For construction workers, procrastination is avoidance. Delaying work you should start. But for designers, procrastination is incubation. Letting ideas develop subconsciously. The longer they delay starting, the more creative solutions emerge. Because their brains are working on problems even when they are not consciously designing. So forcing designers to commit to starting tasks in Week 2 and finishing in Week 3 eliminates the incubation time that produces excellent design. Forces them to start before ideas mature. Finish before creativity peaks. And produce mediocre work under artificial time pressure. Meanwhile if you give designers autonomy within sprints to decide when to start tasks and how to sequence work, they optimize their creative process naturally. Incubate ideas. Start when ready. Produce excellence. This is why Scrum works for designers. It gives structure without rigidity. Provides deadlines (sprint reviews) without micromanaging daily or weekly work. Trusts autonomous teams to manage their own creative process. And produces better results faster than Last Planner’s rigid weekly commitments. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

What Scrum Actually Is and Why Designers Need It

Scrum is where you get small teams working in short time durations with a list of prioritized tasks. Teams move items from backlog to in-progress to complete as fast as possible. That is the simple version. More precisely: Scrum has three roles, five events, and three artifacts. The three roles are product owner (represents voice of customer, sets vision and priority), scrum master (servant leader helping teams succeed within sprints), and development team (cross-functional people who build the product with necessary skills and quality control). The five events are sprint (fixed duration container for completing backlog items), sprint planning (meeting where team decides which backlog items to tackle this sprint), daily scrum (quick coordination meeting moving items from left to right on the board), sprint review (presenting minimum viable product and getting feedback), and sprint retrospective (team asks how to do better next sprint). The three artifacts are product backlog (all tasks representing customer vision and priorities), sprint backlog (specific items committed for this sprint with capacity buffers), and product increment (sum of completed work adding value through defined-done criteria).

Applying this to IPD design clusters transforms how teams work. Each cluster becomes a Scrum team. The cluster lead becomes product owner representing customer voice and setting priorities. A Scrum master helps the team succeed (could be GC coordinator or senior designer who knows Scrum). The designers become development team executing the work. In sprint planning, the team decides which design tasks to tackle this week or two-week sprint. During daily scrums, they coordinate quickly moving items across the board from backlog to in-progress to complete. At sprint review, they present minimum viable design increment to other clusters and customers for feedback. At retrospective, they figure out how to work faster and better next sprint. This gives designers autonomy within structure. They control how they sequence work within sprints. When they start tasks. How they collaborate. What they tackle first. All within a framework that ensures progress toward deadlines without micromanaging creative process.

Why Last Planner Fails Designers

Last Planner forces designers into time scales that destroy creative process. Weekly work planning requires commitments to specific tasks in specific weeks. This works for construction because trades know their sequences. Know their production rates. Can predict accurately. But designers cannot predict accurately when creative work is iterative. A mechanical designer might plan to route ductwork in Week 3. Then structural coordination in Week 2 reveals conflicts requiring complete redesign. So the Week 3 commitment fails. Not because the designer is incompetent. But because design is discovery. You cannot know what you will discover until you design. Cannot commit to finishing before you start. Cannot predict how long creative problem-solving takes. So Last Planner’s weekly commitments set designers up for failure. Create anxiety. Destroy trust. And produce mediocre work rushed to meet artificial deadlines.

Scrum solves this by giving designers sprint-level commitments instead of task-level commitments. The team commits to producing a minimum viable product by sprint review. How they get there is up to them. Which tasks they tackle in which order. When they start each item. How they sequence creative work. All autonomous decisions within the development team. This respects the creative process. Allows incubation. Enables iteration. And produces better results because designers work when ready instead of when scheduled. The constraint is the sprint review deadline. Must show progress. Must demonstrate value. But the path to that progress is flexible. And that flexibility is what creative work requires.

Signs Your Design System Is Wrong

Watch for these patterns that signal you are forcing designers into construction systems instead of design systems:

• Designers consistently miss weekly commitments and percent plan complete drops because Last Planner’s rigid time scales do not accommodate iterative creative processes requiring flexibility and incubation
• Design teams withdraw from coordination meetings or make vague commitments to protect themselves from weekly failures caused by forcing sequential thinking onto non-sequential work
• Construction teams label designers as unreliable or uncooperative without recognizing the system is wrong not the people because Last Planner works for construction but fails for design
• Designers feel anxious pressured and constrained by weekly work planning when they need autonomy and creative freedom to produce excellent work through iterative discovery
• Projects delay despite IPD structure because design coordination fails when designers cannot commit accurately to work that requires discovery before definition
• Trust erodes between designers and construction teams because Last Planner creates failure cycles where designers commit then change then fail while construction judges instead of supporting

These are not designer problems. These are system problems. Last Planner is the wrong tool for design. Scrum is the right tool. And continuing to force designers into Last Planner because “that is what we always do in IPD” guarantees mediocre results and frustrated teams.

How to Implement Scrum in IPD Design Clusters

Keep most of IPD structure. Still do conditions of satisfaction defining what winning looks like. Still do teaming and onboarding aligning vision and goals. Still organize into cluster groups for functional work. Still create overall master plan with milestones (preferably using Takt planning not CPM). Still coordinate across clusters. But instead of using Last Planner for weekly work planning within clusters, use Scrum. Each cluster becomes a Scrum team with product owner, scrum master, and development team. Start each sprint (one or two weeks) with sprint planning meeting where the team decides which backlog items to tackle. Hold daily scrum meetings (15 minutes) where team coordinates and moves items across the board from backlog to in-progress to complete. End each sprint with sprint review presenting minimum viable design increment to other clusters and customers. Follow with sprint retrospective where team improves process.

Use visual boards (physical or digital like Hoylu) with four columns: product backlog (all tasks for this cluster), sprint backlog (items committed for this sprint), in-progress (work currently happening), and complete (finished items). Track progress with burn down charts showing how quickly the team completes work without rigid weekly commitments. This gives designers the autonomy they need while maintaining structure construction requires. Designers control their creative process. Construction sees progress through sprint reviews. Everyone wins because the system matches the work instead of forcing work into wrong system.

Why You Never See Flow Without Comparing Swim Lanes

Here is a critical insight about Takt planning that most people miss. Last Planner creates pull plans for individual swim lanes. Great for sequencing that lane. But you never see flow unless you can compare swim lanes together. Flow means trades moving rhythmically from area to area maintaining consistent crew counts and production rates. But if each swim lane is planned separately, you cannot see whether trades flow between lanes. Cannot visualize stagger and throughput. Cannot identify where crews stack or starve. Takt planning solves this by showing all swim lanes together with color highlighting showing trade progression. You see mechanical flowing from Zone 1 to Zone 2 to Zone 3 across multiple levels. See where they stack with electrical. See where sequences need adjustment. This is genius. You standardize what you can (flow rhythm crew counts) so you can focus on what you cannot (owner changes and inevitable chaos). Same principle applies to design. Use Scrum to standardize creative process within clusters so you can focus on coordination across clusters and response to customer feedback instead of micromanaging daily or weekly task completion.

Never Change Schedules to the Left Only to the Right

Imagine a center dot with arrow going right and arrow going left. Left means dissolving logic, making schedules less accurate, faking information to fit boxes, falsifying data. Never go left. Ever. Right means improving schedules, getting closer to 100% accuracy, refining detail, aligning with reality. Always go right. Change schedules anytime as long as changes make them more correct. Examples of going right: aligning CPM with Takt plan, updating Takt for impacts, reflecting time impact analysis, doing pull plans, refining from level 2 to level 3 to level 4 detail, daily level 5 coordination. All legitimate changes making schedules more accurate. If you establish baseline and change it with more accurate information, reestablish baseline with owner or team through zero-dollar change order documenting updates. This is crucial. Never falsify. Always refine. Change schedules constantly to improve accuracy. Just never change them to reduce accuracy or hide reality.

The Challenge

Stop forcing designers into Last Planner systems designed for construction execution. Start using Scrum in design clusters giving designers the autonomy and creative freedom they need to produce excellent work. Learn Scrum. Learn IPD. Combine them properly. Keep IPD structure (conditions of satisfaction, teaming, clusters, master plan, milestones, and coordination). Replace Last Planner within design clusters with Scrum (product owner, scrum master, development team, sprint planning, daily scrums, sprint reviews, retrospectives, and burn down charts). Give designers structure without rigidity. Deadlines without micromanagement. Progress tracking without rigid weekly commitments. And watch design quality improve while coordination improves and trust builds between designers and construction teams.

As Felipe Engineer teaches through Scrum training: teams that decide and act on issues within five hours have dramatically higher success rates. Scrum enables this by creating small autonomous teams empowered to make decisions quickly without bureaucracy. Last Planner requires weekly coordination reducing autonomy and slowing decisions. So use Scrum for design. Use Takt for construction flow. Combine them in IPD structure. And create projects where designers thrive creating excellence while construction teams execute with flow. Both succeeding because systems match the work instead of forcing work into wrong systems. On we go.

Frequently Asked Questions

What are the three roles, five events, and three artifacts in Scrum?

Three roles: product owner (customer voice and priority setter), scrum master (servant leader helping team succeed), development team (cross-functional builders). Five events: sprint, sprint planning, daily scrum, sprint review, retrospective. Three artifacts: product backlog, sprint backlog, product increment.

Why does Last Planner fail for design work when it succeeds for construction?

Last Planner forces weekly time commitments that work for sequential construction with predictable production rates. Design is iterative requiring creative incubation and flexibility to respond to discoveries, rigid weekly commitments destroy the creative process designers need to produce excellent work.

How do you implement Scrum within IPD design clusters?

Keep IPD structure (conditions of satisfaction, teaming, clusters, master plan, milestones). Replace Last Planner within clusters with Scrum teams having product owner, scrum master, and development team using sprint planning, daily scrums, sprint reviews, and burn down charts instead of weekly work planning and percent plan complete.

Why do creative people procrastinate and how does Scrum accommodate this?

Creative people procrastinate for incubation—letting ideas develop subconsciously before starting work produces better solutions than starting immediately. Scrum gives sprint-level deadlines with autonomy to decide when to start tasks within sprints respecting creative process while maintaining progress.

What does “never change schedules to the left only to the right” mean?

Left means falsifying data or reducing accuracy (never do this). Right means improving accuracy through refinement, alignment with Takt, impact updates, pull planning, or adding detail (always acceptable). Change schedules constantly to improve accuracy but never to hide reality.