Draft: this text has not been reviewed by the owner and may change before publication.
Adding up: cost, working hours and elapsed time
When you map a process you end up with figures on many blocks: hours of work, costs, durations, waits. It is natural to add them all up, but they do not all add the same way.
- 12 min read
Working hours and costs sum: every hour worked and every cost incurred counts, whether the steps run one after another or side by side. Elapsed time does not. Steps in a sequence add, steps side by side take as long as the longest one, and waiting time sits on the clock without costing any work. This part explains the difference with two small examples and a lens you can use to read your own map. It gives no advice. What to do with the picture is up to you.
What adds up: working hours and cost
A working hour is an hour someone spends working. A cost is an amount spent: wages, materials, a supplier's invoice, a carrier's fee. Both are things you give up when a step happens.
Both sum, whatever the shape of the process. Order does not matter, and neither does what runs at the same time. Three people working in parallel for 2 hours each is 6 working hours. Those same three people working one after another is also 6 working hours. The cost of 6 hours is the same in both cases.
This is why working hours and costs follow the work, not the calendar. If a step happens, its hours and its costs count. If a step is skipped, they do not. How the steps are arranged does not change them.
Two cautions. First, working hours are not the same as the time a step takes on the clock. A step where two people work for 3 hours takes 3 hours of elapsed time and uses 6 working hours. Second, the amounts are only as good as the figures you enter. They are plan figures, directional estimates, not an accounting record. Wages, a carrier's fee and a guess about materials can sit in the same sum, but that sum is a rough size, not a ledger.
What does not add up: elapsed time
Elapsed time is the time on the clock from the start of a job to its finish. Three rules cover most of it.
- Steps in sequence add. If step B starts when step A ends, the elapsed time is A plus B.
- Steps in parallel take the longest. If two steps run side by side, the clock moves at the pace of the slower one. The faster one finishes and waits.
- A join waits for the slowest arrival. Where branches come back together, for example when welding needs both the cut steel and the hinges, the next step cannot start until the last of them arrives.
Put together, the overall time of a chain is the length of the longest path through it. Some people call this the critical path. The name does not matter. What matters is that a short branch beside a long one adds nothing to the clock. It can be cheap, expensive, busy or idle. The clock follows the long one.
Illustration to come
Waiting is on the clock but not in the hours
Part 5 described two clocks: working time and waiting time. Here is how they behave when you add things up.
A delay is time that passes while nobody is working on the job. Paint curing, a carrier carrying, a customer thinking, a supplier's lead time, an approval sitting in someone's inbox. A delay belongs on the path, because the job cannot move on until it is over. But it costs no working hours. Nobody is working.
So a path has two parts: time spent working and time spent waiting. Their sum is the elapsed time. Only the first part shows up in working hours. A path can be mostly waiting and still use very little work.
Why the difference matters
Here is one way to read it. You might read a map as holding two different questions, and the answers do not always point to the same place.
- If you shorten a step that is not on the longest path, working hours or cost may change, but the clock does not. The long branch is still setting the pace.
- If you shorten something on the longest path, the clock moves. It moves until another branch becomes the longest, and then that one sets the pace.
That is a lens, not a recommendation. Whether a faster clock is worth anything, or whether a lower cost is, is for you to decide. Some waiting is built in and some is welcome. A map only lets you see which question you are asking: where does the money and work go, or where does the time go?
Worked examples
Northline Fabrication and Maple Street Bakery are invented for illustration. The figures are not data.
A gate at Northline Fabrication
Northline makes custom steel gates. One gate goes through six steps. Cutting and prepping the steel runs at the same time as ordering the hinges. Welding needs both. Labour is counted at 40 per hour, an assumed figure. Other costs are the steel, the hinges, powder coating and the carrier.
| Step | People × hours | Working hours | Cost (labour + other) |
|---|---|---|---|
| Quote and confirm | 1 × 2 | 2 | 80 |
| Cut and prep | 2 × 4 | 8 | 320 + 200 steel = 520 |
| Order hinges | 1 × 2 | 2 | 80 + 90 hinges = 170 |
| Weld | 1 × 6 | 6 | 240 |
| Finish | 1 × 4 | 4 | 160 + 60 coating = 220 |
| Ship | 1 × 2 | 2 | 80 + 70 carrier = 150 |
| Total | 24 | 1,380 |
Nothing in this table cares about order. Cut and prep could run before or after ordering hinges, and the totals would be the same: 24 working hours and about 1,380.
The clock is different. Say a working day is 8 hours, so 2 hours of work is a quarter of a day. Delay is waiting time in days.
| Step | Work (days) | Delay (days) | Starts at | Ends at |
|---|---|---|---|---|
| Quote and confirm | 0.25 | 1 (customer signs off) | 0 | 1.25 |
| Cut and prep | 0.5 | 0 | 1.25 | 1.75 |
| Order hinges | 0.25 | 3 (supplier lead time) | 1.25 | 4.5 |
| Weld | 0.75 | 0 | 4.5 (waits for hinges) | 5.25 |
| Finish | 0.5 | 1 (curing) | 5.25 | 6.75 |
| Ship | 0.25 | 2 (carrier) | 6.75 | 9 |
Cut and prep and order hinges both begin at day 1.25. Cutting is done by day 1.75, but the hinges arrive at day 4.5, so welding starts at 4.5. The cutting branch has 2.75 days of slack, in the sense that it could take that much longer without changing the finish date.
Illustration to come
The gate is ready to leave on day 9. On the longest path, work is 2 days (0.25 + 0.25 + 0.75 + 0.5 + 0.25) and delay is 7 days (1 + 3 + 1 + 2). Work and waiting together make 9 days.
You might read this in several ways. The 8 hours of cutting are the largest single block of working hours, yet they sit on the short branch. If cutting took a full day instead of half a day, its hours and cost would probably rise, and the ship date would not move. The hinge branch, which is 2 hours of work and 3 days of waiting, is what sets the pace. If the hinges were already on the shelf, that branch would shrink to almost nothing, and the cutting branch would take over as the longest. Whether any of that matters is for the people at Northline to say.
A special-order cake at Maple Street Bakery
A customer orders a birthday cake. Baking and decorating run in sequence. The box supplier delivers in parallel. Both feed the final boxing step. Times here are in hours.
| Step | Work (h) | Delay (h) | Starts at | Ends at |
|---|---|---|---|---|
| Take the order | 0.5 | 0 | 0 | 0.5 |
| Bake the layers | 2 | 3 (cooling) | 0.5 | 5.5 |
| Decorate | 3 | 0 | 5.5 | 8.5 |
| Order boxes | 0.5 | 6 (supplier delivers) | 0.5 | 7 |
| Box and label | 1 | 0 | 8.5 (waits for both) | 9.5 |
Working hours sum to 7 (0.5 + 2 + 3 + 0.5 + 1). That includes the half hour spent ordering boxes, even though that branch is not on the clock's longest path.
The clock is 9.5 hours. The bake, cool and decorate branch takes 8 hours from the order. The box branch takes 6.5. Boxing begins when the slower of the two is done. The supplier's 6-hour wait is a long delay, but it sits beside an even longer one, so it adds nothing to the finish time. On the longest path, work is 6.5 hours and delay is 3 hours (the cooling).
Illustration to come
Flour, eggs and the cash in the till are stocks here as well, and the baker knows them well. They are not part of this table.
On the map
On the map
This section describes what Ursa Major does today.
- Duration and delay are separate entries. On an ordinary process block you enter a duration and a delay as two figures. The roll-up reads each one on its own, along the connections between blocks. Steps in sequence add. Where connections join, the longest incoming path is used. Blocks that are not connected to each other run in parallel, so the result is the longest path.
- A block linked to a child canvas uses the larger of its own figure and the longest path inside the child canvas. It does not add them.
- A total that includes both. Duration and Delay summaries each calculate their own longest path, which may differ. Total duration does not add those two maxima; it follows one coherent path containing both execution and waiting. They are calculated when you run Parse.
- Blanks and loops. A figure you have not entered counts as zero in the calculation, and the result lists what was counted as zero. If blocks are connected in a loop, with the last block leading back to an earlier one, the path through them has no end. The blocks in the loop, and everything after them, are shown as unknown, and so is the total for the canvas. The map does not guess a number for a loop.
- Units. You enter durations and delays in minutes, hours, days or weeks. Days and weeks are turned into hours through the workspace's work-time settings (hours per day, days per week), which cannot be edited in the app yet; where they are missing, the figure is reported as unavailable rather than guessed.
- Cost and working time follow the figures, not the path. Costs come from the amounts you enter on blocks and from the resources you assign to them. Amounts are added only when they share the same cost class, currency and exact basis; fixed and variable amounts are totalled separately, and unclassified amounts join neither. The app does not convert between currencies. Time you assign from people and other resources is set against what each has available on the Resources page. Neither depends on which branch is longest.
Reflect
Questions to sit with
- In one process you know well, which steps run side by side? When one of those branches finishes early, what does it do while it waits?
- If you list the waits in that process (curing, approvals, supplier lead times, a customer deciding), how much of the elapsed time do they account for, compared with the time spent working?
- When you think about speeding up a process, do you tend to look first at the costly steps or at the long ones? Are they the same steps?