It took ten minutes to suggest moving the button. What happens before we can send the next batch?

The drawing is finished. The change is not.

Imagine a desk lamp. Its button is on the shade, where a hand has to reach up to find it. Put the button on the base and the lamp may feel easier to use. The suggestion fits in a sentence. The visible edit fits in a few millimetres of a drawing.

The next person cannot assemble a sentence. They need a base with an opening in the right place, an internal route that belongs to the revised arrangement, and a sample that someone has checked. The person preparing the batch needs a setup that holds the new version. The person packing it needs the right insert and reference. The customer needs the right instructions.

The object has barely changed. The agreement around it has started moving.

This workshop is a fictional teaching model, not a record of my product history, a production quotation or an industry benchmark. Its lamp is not a guide to modifying a real electrical product. The invented tasks and durations make one relationship visible: a change travels through the things that depend on the previous version.

Some days contain work. Other days contain waiting.

The default batch takes thirty elapsed working days. Using five working days per week, that is the six-week shadow in the title.

The first day is review. The ten-minute suggestion and drawing edit sit inside it; they are not an extra task added before the clock begins. Four days go into building and checking a sample. Then the sample is ready, and the supplier’s slot is not. Ten working days pass before preparation can begin.

Later, the revised bases have been made and a pilot has been assembled and checked. A pilot is the small trial group before the next batch. Another five working days pass before the production slot opens.

Those two waits occupy fifteen working days. They add no labour effort in this deliberately limited model. The ruler still lengthens, because readiness can be blocked by availability as well as by unfinished work.

Set both waits to zero. The batch becomes ready after fifteen working days. Its active effort remains twenty person-days. The same work has a shorter calendar around it.

Twenty days of work can fit inside thirty days of time

A person-day means one person’s working day of effort. Twenty person-days means twenty days of one person’s work, shared across the people assumed in this scenario. It says nothing here about fees, wages or measured factory productivity.

Some of that work happens together. Once the sample is checked, a separate person can prepare the instructions, photographs and packing references while the supplier slot is still unavailable. Once the pilot is checked, a support colleague can prepare answers to the questions the changed product may bring.

The instruction cards belong beside the main ruler. Adding their three days and support’s two days directly to its end would count parallel time as if it happened afterwards.

They still matter. Packing and release require both sets of information as well as the revised assembly setup. If one of those branches finished later, release would have to wait for it. Parallel does not mean optional.

The same change meets a different moment

Switch to One workshop prototype. The lamp keeps its size. The button makes the same movement. The schedule needs only review and a checked sample: five elapsed working days and five person-days of effort.

There is no next production batch in that scenario. There is no batch setup, supplier booking, packing release or support branch to satisfy. The shorter shadow does not prove that those tasks were waste. It tells us that this moment carries fewer obligations.

That distinction matters when someone asks, “Why can we do this in the workshop this week, but not send the revised batch this week?” The proposal can be identical while the promises attached to it are different.

Read the objects, then inspect their prerequisites

A dependency is something that must happen first. The sample needs the reviewed change. Revised bases need the supplier slot. The pilot needs the revised bases. Packing and release need the assembly setup, references and support preparation.

Select a task, then open What must happen first? The model shows its actual prerequisites and their finishing days. A solid edge marks the chain that currently determines release. Work or Waiting changes emphasis only; it does not remove inconvenient tasks from the calculation.

The shadow is a time ruler, not a simulated cast shadow. Every division means one working day. A five-day prototype occupies the same scale as a thirty-day batch. Moving either wait changes the ruler and its result together. The title stays attached to the default fictional story; the live number tells the truth about the settings you chose.

What the model leaves outside the frame

Every task begins when its latest prerequisite finishes. Roots begin at zero. The final release task determines completion. Active effort is the sum of the included tasks’ person-days. The scheduler assumes separate people are available for the instruction and support branches; it does not try to allocate a limited workforce between competing jobs.

Weekends, public holidays, existing backlog outside the two explicit waits, rework, formal compliance and actual supplier performance are outside this model. Supplier waiting means waiting to begin a bounded preparation task; it is not a shipping guarantee. A real electrical product would require expertise and obligations this fictional object does not represent.

The old-position view reads No change proposed. It means no change project has been created. It does not suggest that an existing manufacturing business has no work or costs.

A small change travels through everything that already depends on the old version.

Keep looking around the workshop

In Build One. Now Build a Thousand., the object stays familiar while the promise grows. In The Museum of Almost, inspect fictional attempts and the evidence that changes the next decision. Each workshop stands on its own; together they ask what an idea needs before it can reach another person.