Part II. Lesson 5. Think Like the Package.
You're not an engineer right now. You're a carton. Somebody just set you down on a conveyor, and you're about to ride it clear across a building you didn't design. What do you feel on the way?
Think like the package, before you draw a single line.
Long dimension forward, running in the direction of travel. You span a lot of rollers at once, sit flat, and ride stable.
Short dimension forward. Fewer rollers under you, so you can teeter, and your leading edge can dip into the gap before the next roller catches you.
The rule underneath it: at least three rollers in contact with the package at all times.
Thinking about the conveyor instead of the package. You draw a clean set of lines connecting the entry to the exit, and every line is technically correct, and you never once asked what the product feels going through it. The jams show up later, at the exact points you skipped.
Pick a padded mailer you've gotten in the mail. Put it on a roller conveyor in your head and push it forward. What happens when it reaches a curve? When the zone in front of it stops and the package behind it keeps coming? When it hits a transfer? You just found three reasons a polybag isn't a carton.
Tires, polybags, anything that isn't a standard carton, some consideration has to be made, because it can drive the whole solution in a direction you didn't plan for. The question I always ask is what percentage of your volume is this. Five percent or less, you probably don't design the whole system around it, you build an exception path. Twenty percent and you've got a different system entirely.

| Product | Length | Width | Height | Weight | % Volume | Product Use |
|---|---|---|---|---|---|---|
| Small Case | 8" | 6" | 4" | 3 lbs | 4% | Packaged food |
| Standard Case | 13" | 9" | 3" | 12 lbs | 78% | All clients |
| Tall Case | 10" | 8" | 14" | 18 lbs | 12% | Apparel client |
| Large Case | 22" | 15" | 7" | 28 lbs | 6% | Housewares |
Walk the list as the carton. Which one runs easy, which one is a handling risk, and which one you're flagging and why. Write a one or two sentence behavior read for each, in the package's voice where it helps.
Next: Which products should this system actually be built around?