Lean for Beginners: Cannabis · Lesson 3 of 10 · Week of October 26
Clone to counter: mapping the flow
In Lesson 1 you asked how much of a batch's life is spent being worked on. This lesson gives you a way to answer. You draw the whole path one product takes, from the first step to the person at the counter, and you write down how long it spends being worked on and how long it spends waiting.
By the end of this lesson you can:
- say what a value stream is and why drawing one shows you things a meeting never will;
- map one product through your area and the steps on either side of it;
- split the time into working time, required waiting and other waiting;
- find the longest wait, and the handoff that caused it.
You need Lessons 1 and 2 first. This one uses the three kinds of activity (value-adding, required, waste) and the habit of looking before you fix.
What a value stream is
A value stream is every step it takes to get one product to the customer, including the waiting between steps. Not the steps in the procedure manual. The steps that actually happen, in the order they happen, with the time each one takes.
Here is a cannabis value stream for flower, from the first step to the shelf:
- Cultivation: mothers, clones, veg, flower, harvest call.
- Post-harvest: harvest, dry, buck, cure, trim, grade, weigh the lot, lab sample, vault hold, release.
- Packaging and fulfillment: pull the released lot, pack and label, tag, vault, pick the order, manifest, deliver.
- Retail: receive and accept, back-of-house storage, stock the floor, list on the menu, sell.
Manufacturing sits beside this path. Some flower becomes extract, infused products or pre-rolls, and that product follows its own stream through extraction, post-processing, testing and fill. The method below works the same way for either one.
Notice that every arrow between two areas is a handoff, and every handoff is somebody's customer. That's where this lesson spends most of its time.
Why draw it
Each team in an operation can usually tell you how long its own steps take. Almost nobody can tell you how long the product takes to get through all of them, because the time lives in the gaps between teams and no one owns a gap.
A drawn map fixes that in three ways. It shows the waiting, which no procedure lists. It shows the handoffs, where one team's output sits until the next team is ready. And it gives everyone the same picture, so the argument shifts from "your area is slow" to "this is where the batch sat."
How to map one product
- Choose one product. One strain and batch, or one SKU, or one order. Not a department and not "everything we make."
- Walk the whole stream first, then draw from the customer back. Take a quick walk door to door, the way Rother and Shook describe it in Learning to See. Then go back to the customer, who is whoever receives your work next, and work upstream, drawing by hand in pencil. It keeps your attention on what the customer needs, not on what your area happens to do.
- Write the step, who does it, and what it hands off. One box per step. Use what you see, not what the procedure says. If the procedure and the floor disagree, write down the floor.
- Write two times for each step. The working time: how long someone actually works on it, or how long it's in a process that has to take that long, like dry and cure. And the waiting time before it: how long the product sat before this step started.
- Take the times from records first. Tote cards, scale logs, lab dates and the tracking system already hold most of them. Where there's no record, watch it once and write down what you saw.
- Draw a triangle between steps where product waits, and write how long and how much.
- Mark each wait. Is it required, like the test hold? Or is it just sitting?
The printable map in the task below has boxes for a handful of steps and a wait between each, so you can do this on one page.
Common mistakes
- Mapping the whole company at once. You'll never finish, and nobody will recognize the result. One product.
- Drawing the procedure, not the floor. The map is only useful if it's what really happens.
- Trusting a system average. Rough numbers are fine for a first pass, but time one real batch yourself. One real batch beats a smoothed number. You can average later.
- Fixing while you map. The rule from Lesson 2 still holds: write it down, keep walking.
- Mapping only your own area. Include the step before and the step after. The biggest waits are often right at your doorstep.
The arithmetic
Once the map is drawn, three numbers tell you what you have.
- Lead time, door to door: from the first step to the last. How long the product takes to get through.
- Working time: the time the product is being worked on, plus time in a process that has to take that long, like dry and cure. Some people count only hands-on time. Pick one way and use it every time you map.
- Waiting time: everything else. Split it into required waiting (the test hold) and other waiting.
The share of lead time that is working time is the part the customer would pay for. In most operations it's smaller than people expect, which is exactly why the map is worth drawing.
An example, with made-up numbers. Suppose a lot takes 20 days from harvest to release. Dry and cure take 14 of them. The test hold takes 4, and the lot waits 2 days in the vault after its results come back. Working time is 14 days. Required waiting is 4. Other waiting is 2. So in this slice of the stream, 14 of 20 days, or 70%, is working time, and the 2 days of other waiting are the part you can attack. Across a whole stream from clone to counter, the share that is working time is usually much smaller. These numbers are invented to show the arithmetic. Yours will be different, and they are not a benchmark.
Notice what the example doesn't ask you to do. It doesn't ask you to shorten dry and cure, and it doesn't ask you to skip the test hold. It points you at the two days nobody was working on the lot and nothing required it to sit.
Knowledge check
Five questions, graded for you. Sign in to take the check, save your progress and count this lesson toward your certificate. Sign-in opens on Monday, October 12.
Sign in to take the check
Your task: map one product
- Choose one batch or order in your area, ideally one that has already finished, so the records exist.
- Fill in the map with your area's steps, plus one step before it and one after.
- For each step write who does it, the working time and the waiting time before it. Use records where you can.
- Mark each wait R (required) or O (other).
- Add it up: lead time, working time, required waiting, other waiting.
- Circle the longest O. Write down which handoff it sits at. Don't fix it yet.
Open the printable map
Your floor, your data. What you write on a worksheet stays with you. It is paper, and nothing you write on it reaches this site. If you talk about your floor in public, keep it general: leave out license numbers, batch or package IDs, supplier and customer names, and any number your employer treats as confidential.
Sources
Where the facts in this lesson come from. Facts last checked October 1, 2026. If you find one that is out of date or wrong, tell me.