02 / 08Systems

Break it into parts

A term paper due in six weeks sits on a list as one line. So does "plan the team offsite" at work, or "move apartments" at home. A line that size has no first step, so it waits. Breaking it into parts turns one large thing into many small ones, each small enough to start today. Find three sources. Draft the section on causes. Book the van. Call the venue about Saturday. The parts also show what was missing. A paper needs a bibliography. A move needs a new address on every account. Neither shows up until someone lists the parts. This lesson breaks a large job down level by level, until every piece is something a person can finish in one sitting.

In five minutesWrite one stalled task at the top of a page. Under it, write three parts that would finish it. Circle the one you can do in under an hour today, and start it.

Method · Work breakdown structure  /  Philosophy · Engineering

↺From last time · From notes to a system

Answer these from memory before you start. Tap to check.

What turns a pile of notes into a system?

Three things: the notes as parts, the links between them, and a purpose question they help answer. Without the purpose, links multiply and say nothing.

Why label a link instead of just drawing a line?

A bare line says two ideas relate. A label says how: causes, is an example of, contradicts. Choosing the label is a decision about the relationship, and that decision is what gets learned.

What does a note with no links tell you?

Either its link has not been found yet, or it does not serve this question. Give it a link or set it aside. An unlinked note is rarely found again.

01Where it comes from

René Descartes published the Discourse on Method in 1637. In Part Two he describes a winter in Germany spent alone with his thoughts, when he set himself four rules in place of the many precepts of logic [1]. The second rule was to divide each difficulty into as many parts as it needed. The third was to start with the simplest and climb by steps to the complex. The fourth was to review so completely that nothing was left out. Three centuries later, project managers built the same idea into a tool. The US Defense Department and NASA described the PERT/COST system in a guide of June 1962, and its 1963 supplement reports a program's cost and schedule "at several levels of the work breakdown structure" [2]. NASA's current handbook calls the structure "a product-oriented family tree" of everything a project must deliver [3]. In psychology, Richard Catrambone tested what happens when worked examples group their steps under labeled subgoals [4].

Also called Breaking a problem down, problem decomposition, WBS, task breakdown, subgoals, Descartes's rules.

Divide each difficulty

The second, to divide each of the difficulties under examination into as many parts as possible, and as might be necessary for its adequate solution.

René Descartes, Discourse on the Method of Rightly Conducting the Reason Part Two · tr. John Veitch

Descartes is listing four rules he chose in place of the long rulebook of school logic, on the condition that he keep them without exception. The second carries a limit inside it. Divide into as many parts as possible, but only as many as the solution needs. A breakdown has a purpose. It stops when each part can be solved. The third rule then orders the parts, simplest first.

Read it in full: A Discourse on Method, Part Two

Leave nothing out

And the last, in every case to make enumerations so complete, and reviews so general, that I might be assured that nothing was omitted.

René Descartes, Discourse on the Method of Rightly Conducting the Reason Part Two · tr. John Veitch

The fourth rule is the check that makes the second one safe. Dividing a problem risks losing a piece in the cracks. A complete list, reviewed as a whole, catches it. Project managers ask the same question of a breakdown: do the parts at each level add up to everything above them? The next lesson turns that review into a written checklist.

Read it in full: A Discourse on Method, Part Two

02The method

Work breakdown structure

  1. Write the whole job at the top as a finished result: "Paper on the 1918 flu, submitted" or "Team moved into the new office."
  2. Under it, list the three to seven parts that together make the whole.
  3. Ask of the list: if every part were done, would the whole be done? Add whatever is missing.
  4. Break each part again the same way, until each piece is one sitting's work, two hours or less.
  5. Name every piece as a result with a verb: "Draft section 2", not "Section 2".
  6. Mark which pieces wait on others. Start with one that waits on nothing.

03An example

What it looks like done

Worked on Moving to a new apartment by the end of the month

Topic

  • Moved into the new apartment by the 30th, with every account at the new address.

I. Packing done by the 27th

  • A. Supplies
  • 1. Pick up 20 boxes from the grocery store, Saturday
  • 2. Buy tape and two markers
  • B. Pack room by room
  • 1. Books and winter clothes, this week
  • 2. Kitchen last, on the 28th

II. Moving day booked

  • A. Reserve the van for the 29th
  • B. Ask two friends to help, and confirm by text on the 25th

III. Addresses changed

  • A. Bank, phone, payroll at work
  • B. Mail forwarding
  • C. Renter's insurance at the new address

IV. Old place handed back

  • A. Clean and photograph each room
  • B. Return the keys and ask about the deposit

Check against the topic

  • If I to IV were all done, would the move be done? No. Nothing covers internet at the new place.
  • Added III. D. Schedule the internet install for the 30th.
  • First piece that waits on nothing: I. A. 1, the boxes.

04Try it · 25 minutes

For a class

Take your next paper, project or exam. Write the finished result at the top of an outline page. Split it into four to six parts, then split each part until every piece fits one study session. Put a check by a piece that waits on nothing, and do it today. If there is time, read Descartes's four rules near the end of Part Two. About 25 minutes.

Open it in the reader: A Discourse on Method, Part Two

For work and life

Pick a project that has stalled: a report, a hire, a move, a repair at home. Write the finished state at the top. Break it into parts, and each part into pieces small enough for one sitting. Give every piece a verb. Then test each level: if all of these were done, would the level above be done? Each no is a missing piece.

The blank page for this is in the Systems workbook.

05Where it goes wrong

  • Splitting by week, not by result. "Week 1, week 2" hides what each week has to produce. Split by the things that must exist when the job is done, then put them on a calendar.
  • Pieces still too big. "Write the paper" as a piece is the whole job again. Keep splitting until the first move is obvious.
  • Missing parts. A list can look complete and still leave out the bibliography or the change of address. Check every level against the one above it.
  • Too much detail too early. Breaking parts due in two months into ten-minute steps takes time, and the plan will change. Detail the next two weeks and leave later parts coarse.

06Research

What research has measured

Labeling the steps by their purpose

Shown that worked examples which group steps under a label for their purpose help learners solve new problems that need changed steps.

The numbers and sources
Effect
Across four experiments, a label for a group of steps in worked examples helped learners form subgoals, measured by problem solving and by talk-aloud protocols. Abstract labels worked better than labels tied to surface features [4]. In a semester-long programming course, subgoal instruction raised quiz scores, and fewer students dropped or failed. Average exam scores were not significantly better [5].
Population
600 college students learning probability, across four experiments [4]. 265 students in an introductory programming course [5].
Caveats
Learners in these studies studied examples someone else had already split into steps. Breaking down a project of your own is related, and was not what they tested. The semester-long study found no average gain on exams [5].

07Check yourself

Answer from memory first. The next lesson asks these again.

When do you stop breaking a piece down?

When it fits one sitting and the first move is obvious. Descartes's second rule holds the same limit: as many parts as the solution needs, and no more.

Why test each level against the one above it?

Splitting can drop a piece into the cracks. Asking whether all the parts would finish the whole catches the missing bibliography or change of address before the deadline does.

Why name each piece as a result with a verb?

"Section 2" leaves the action open every time you look at it. "Draft section 2" says what to do, and how to tell when it is done.

Sources
  1. Descartes R. Discourse on the Method of Rightly Conducting the Reason, and Seeking Truth in the Sciences. Veitch J, trans. 1850. https://www.gutenberg.org/ebooks/59
  2. US Department of Defense, National Aeronautics and Space Administration, PERT Coordinating Group. Supplement No. 1 to DOD and NASA Guide, PERT Cost Output Reports. March 1963. https://www.mosaicprojects.com.au/PDF-Gen/DOD_and_NASA_Guide_PERT_Cost_Output_Reports.pdf
  3. National Aeronautics and Space Administration. NASA Work Breakdown Structure (WBS) Handbook. NASA/SP-2016-3404/REV1. 2018. https://ntrs.nasa.gov/citations/20180000844
  4. Catrambone R. The subgoal learning model: Creating better examples so that students can solve novel problems. Journal of Experimental Psychology: General. 1998;127(4):355-376. https://doi.org/10.1037/0096-3445.127.4.355
  5. Margulieux LE, Morrison BB, Decker A. Reducing withdrawal and failure rates in introductory programming with subgoal labeled worked examples. International Journal of STEM Education. 2020;7:19. https://doi.org/10.1186/s40594-020-00222-7

MVIII puts the day in front of you each morning. Get MVIII