Common Struggles
The fifteen places students reliably get stuck, and what actually unsticks them
This is the file to read before week one. Most of what follows is not a content problem — it is a prior-belief problem. Students arrive with intuitions from other courses that are actively wrong here, and the fix is usually to surface the wrong intuition rather than to explain the right answer again.
Each entry gives the struggle, why it happens, the diagnostic that catches it early, and the intervention that works.
1. The forward and backward pass (Chapter 14)
The struggle. Students follow a worked example perfectly, nod, and then cannot do one unaided a day later. This is the single most reliable failure in the book.
Why. Watching a procedure creates a fluency illusion. The forward pass in particular looks trivial — take the maximum of the predecessors' early finishes — and the difficulty only appears at a merge node under time pressure.
Diagnostic. At the start of the session after you teach it, hand out a six-activity network and give them eight minutes. Do not preview it. The score distribution will tell you exactly where you are.
Intervention. Repetition by hand with feedback, and nothing else. Appendix B exists for this — twenty problems with full solutions. Assign 1–8 immediately, work two of them in class with students at the board, and require the rest before the exam. Do not let them use software until they can do it on paper. A student who reaches for Microsoft Project at this stage learns to operate a tool rather than to read a schedule, and the difference shows up two years later when they cannot tell that a consultant's schedule is nonsense.
2. Free float versus total float (Chapter 14)
The struggle. Students compute total float correctly and then either think free float is a synonym or produce it by a rule they cannot explain.
Why. Total float has an intuitive story ("how late can this be without hurting the project"). Free float's story ("without delaying any successor") requires holding two nodes in mind at once.
Intervention. Teach it on a network where they differ and the difference matters — a chain feeding a merge node, where the first activity has four days of total float but zero free float, so using its float pushes work onto somebody else. Then ask the question that makes it stick: "whose float did you just spend?" That question also sets up the float-ownership discussion, which is where the real professional content lives.
3. Markup versus margin (Chapters 12 and 13)
The struggle. A 10% markup is a 9.09% margin. To get a 10% margin you must mark up 11.11%. Students believe they understand this and then get it wrong on an exam.
Why. It is arithmetic they learned in a different context (retail) where the distinction was never enforced, and the numbers are close enough at small percentages that the error hides.
Diagnostic. Two questions, five minutes, at the start of the session after Chapter 12. Ask both directions.
Intervention. Make them build a small estimate to a target margin rather than applying a markup. The moment they have to solve backward, the distinction becomes real. Then show the money: on a $40M cost of work, confusing the two is roughly a $400,000 error, which is most of a project's profit.
4. Cost-to-complete versus cost-to-date (Chapter 28)
The struggle. Asked to forecast, students extrapolate spend rate — "we're 60% through the money, so we're 60% done." The chapter's threshold concept says the opposite.
Why. Every other course they have taken measures progress by consumption. Nothing in their experience has separated what you have spent from what it will take to finish.
Intervention. Give them a cost report where the two answers diverge sharply and let them produce the wrong forecast in public. Then work the unit-rate method on the same data. The gap between the two numbers does the teaching. Follow it immediately with the diagnostic question that generalizes: "how much work is left, and what is it going to cost at the rate you are actually achieving?"
5. That a change order's cost is not the cost of the work (Chapter 31)
The struggle. Students price the added scope correctly and stop. Impact, disruption, resequencing, and lost productivity are invisible to them.
Why. They have never watched a crew get pulled off a task and put back on it. Nothing in the classroom makes the cost of interruption tangible.
Intervention. The measured-mile exercise, worked on real productivity numbers. Then the reverse exercise — put them on the owner's side and ask them to challenge an impact claim that has no substantiation. Students who have argued both sides stop treating impact as either free money or imaginary.
6. Float ownership (Chapter 14)
The struggle. Students grasp float as a calculation and are baffled by it as a contested asset. "Who owns the float?" produces silence.
Why. It is the first place in the book where a technical answer and a commercial answer diverge, and where the contract, not the arithmetic, decides.
Intervention. Pose it as a scenario, not a concept: the owner's late decision consumes eight days of float, then the contractor's subcontractor consumes the remaining four and the project goes late. Who pays? Let them argue. Then show that the contract has a clause about it and that different contracts answer differently. The lesson is not the answer — it is that there is no universal answer, which is uncomfortable and correct.
7. "Substantial completion" as a determination rather than a date (Chapter 40)
The struggle. Students treat it as a milestone on a bar chart.
Why. Every other date in a schedule is a date.
Intervention. Hand them a project state — punch open, systems tested but the fire alarm not certified, owner training not done — and ask whether substantial completion has been achieved and who decides. Then list what the determination triggers: warranty start, transfer of care and custody, cessation of liquidated damages, retention reduction. Once they see that a single determination moves that much money, the distinction sticks.
8. Confusing quality assurance with quality control, and both with inspection (Chapter 23)
The struggle. The three words get used interchangeably, and the chapter's central argument — that inspection finds defects while a system prevents them — collapses.
Intervention. The responsibility matrix, built with the class rather than presented. Have them place the contractor's QC, the design team's observation, the owner's rep, the testing laboratory, the special inspector, and the building official onto the same activity. The confusion is usually about who, not what, and the matrix resolves it.
9. Reading a set of drawings (Chapter 7)
The struggle. Students can look at a sheet and cannot interrogate a set. They do not know that the answer to their question lives on another discipline's drawing.
Why. There is no substitute for having held a real set, and most students never have.
Intervention. Get a real (or redacted) drawing set and project manual into the room. Nothing else works as well. Failing that, use Appendix K and run the chase-a-detail exercise: from a plan, through a section callout, to a detail, to the specification section that governs the material — and time them. Then have them find something that appears on only one discipline's drawings.
10. Cash flow versus profit (Chapters 32 and 34)
The struggle. "If every job is profitable, how can the company be short of cash?" Students find this genuinely counterintuitive.
Why. Profit is the only financial concept most of them have been taught, and it is an accounting opinion about the future rather than a fact about Friday.
Intervention. Build the cash-flow model together on the board, month by month, with retention held and receipts lagged. The moment the cumulative line goes negative on a profitable job, the concept lands. Then the company-level version in Chapter 34: a firm reporting a profit every quarter while becoming insolvent.
11. Believing the numbers in the book are real
The struggle. Students leave thinking they know what concrete costs.
Why. The figures are internally consistent and confidently presented, because they have to be for the arithmetic to teach anything.
Intervention. Say it in week one and repeat it monthly. Then make it operational: assign one exercise where they have to find a real current price for something and compare it to the book. The gap is the lesson. What they should leave with is Chapter 11's hierarchy — own historical data first, current market quotes second, published data adjusted third.
12. Treating the owner, architect, or subcontractor as an adversary
The struggle. Students absorb the book's realism about competing incentives and convert it into cynicism.
Why. The case studies are full of conflict, because that is where the teaching is.
Intervention. Point at the specific design choice: Pri Sethi gave the verbal go-ahead on CO #14 and she was acting reasonably. So was the assistant superintendent who built it. Nobody in that story is a villain, and it still cost $43,650. Run at least one case study from the other party's seat — the owner's rep defending a budget to a board, or the subcontractor deciding which general contractor gets their A-crew. Chapter 19's section written from the subcontractor's side of the table is the best single reading for this.
13. Safety as compliance (Chapter 24)
The struggle. Students learn the Focus Four, pass the questions, and leave believing safety is a rulebook administered by a safety department.
Why. Every prior exposure to safety in their lives has been rules and signage.
Intervention. This is serious enough to have its own file — see safety-teaching-guide.md. The
short version: run the scaffold near-miss investigation as a role-play, and make the argument over
whether to write down finding three the centrepiece. Then, every time the class recommends
acceleration in a later exercise, ask who is going to be on a scaffold in three weeks. Repetition in
context is what converts the idea from a slogan into a habit.
14. The Willow Street project drifting
The struggle. A student falls two deliverables behind in week six and never recovers, because the later deliverables depend arithmetically on the earlier ones.
Why. It is the only cumulative assignment most of them have, and the dependency is not obvious until it bites.
Intervention. Two things, both structural. Grade complete/incomplete/revise weekly from week two so drift is visible immediately. And publish a known-good version of the takeoff, the estimate, and the schedule at a defined point, so a student whose numbers were weak can still do the controls work on sound inputs. This is not charity — it mirrors how a real project hands off, and it prevents one bad fortnight from destroying a semester.
15. "I read it and it seemed obvious"
The struggle. The book is readable. Its threshold concepts are stated plainly, and plain statement produces a feeling of understanding that is not understanding.
Why. Fluent text is processed fluently, and fluency is mistaken for mastery. This is the single most general problem in the whole course.
Diagnostic. The best one available: ask a student to explain a threshold concept to another student, in their own words, with an example that is not the book's. The failure is immediate and obvious to both of them, which is why it works.
Intervention. Use the fifteen threshold concepts as your recurring assessment spine — in discussion, on both exams, and in the final. And tell students explicitly, in week one, that the smoothness of reading forward is the feeling of learning nothing, which is why the book is full of retrieval prompts and spaced reviews they will want to skip.
A note on the mixed cohort
If your class contains both traditional CM undergraduates and people who have worked in the trades, you have an asset. The craft students will find Part II obvious and Part VI opaque; the traditional students will be the reverse.
Seat them together deliberately and structure working sessions so they must explain things to each other. The craft student explaining why a form cycle governs a concrete frame, and the CM student explaining what cost-to-complete means, is worth more than either explanation from you — and it rehearses exactly the conversation both of them will be having on a job site for the rest of their careers.