WP004

Business Timelines

Why flow beats hierarchy when you're trying to understand a business

Core Question: If an org chart tells you who reports to whom, what tells you how work actually moves, and why does that matter more?

Explore This Paper

Different ways to understand the ideas in WP004.

WATCH

Video Overview

0:50

A narrated visual brief showing why flow reveals what hierarchy hides.

Read transcript

WP004 — Business Timelines

Business Timelines

If an org chart tells you who reports to whom, what tells you how work actually moves, and why does that matter more?

An organization chart shows who reports to whom. A business timeline shows how work actually moves. Follow one customer, job, hire, or invoice from the moment it enters the business until it leaves, and the hidden delays become visible.

List the steps in their real order. Mark who actually touches each one. Then circle the step that only one person can complete. That ordinary-looking step is often the constraint quietly holding the whole business together.

The step everyone skips mapping is almost always the step quietly holding the whole business together.

Sketch your own timeline for one normal job this week. List every step, mark who touches it, circle the one only one person can do.

Download transcript
LISTEN

Audio Brief

0:50

A locally generated narration introducing business timelines.

Read transcript

WP004 — Business Timelines

Business Timelines

If an org chart tells you who reports to whom, what tells you how work actually moves, and why does that matter more?

An organization chart shows who reports to whom. A business timeline shows how work actually moves. Follow one customer, job, hire, or invoice from the moment it enters the business until it leaves, and the hidden delays become visible.

List the steps in their real order. Mark who actually touches each one. Then circle the step that only one person can complete. That ordinary-looking step is often the constraint quietly holding the whole business together.

The step everyone skips mapping is almost always the step quietly holding the whole business together.

Sketch your own timeline for one normal job this week. List every step, mark who touches it, circle the one only one person can do.

Download transcript

Visual Overview

The operating chain and the point where work waits.

ANY NORMAL JOB, FOLLOWED START TO FINISH Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 ? Step 9 Step 10 ONE STEP ONLY ONE PERSON CAN DO Ten steps here. Different count in your business. Different step circled. The method is the same: list the steps, mark who touches each, find the one.

Key Ideas

  • The step everyone skips mapping is almost always the step quietly holding the whole business together.
  • Primary signal: Flow Over Hierarchy.
  • Pattern: explorer method.

▣   Field Exercise

Sketch your own timeline for one normal job this week. List every step, mark who touches it, circle the one only one person can do.

Core Question

If you followed one job from first contact to final payment, which step would you struggle to explain in detail?

READ ONLINEBusiness TimelinesOpen full paper +

Why This Matters

Most businesses have an org chart somewhere, even an informal one. Almost none have a timeline. That’s a gap worth closing, because hierarchy tells you very little about where a business is actually stuck. Flow tells you almost everything.


Why Timelines, Not Org Charts

An org chart answers “who’s in charge of what.” It’s useful for a lot of things. It is nearly useless for one specific question that matters more than most owners realize: where does work actually get stuck?

A timeline answers that question directly. It follows one piece of work, a customer, a job, a hire, from the moment it enters the business to the moment it exits, and shows every hand it passes through along the way. Org charts are static. Timelines move. Most businesses are better understood in motion.

The Example Timeline

:::diagram wp004-diagram.svg ::: Here’s a simple one, the kind almost any business could sketch in five minutes:

Customer has a need, then searches or asks around, then finds the business, then makes contact, then gets a quote, then the work gets scheduled, then the work gets delivered, then an invoice goes out, then payment comes in, then, sometimes, a referral follows.

Ten steps. Nothing complicated about any single one. But laid out this way, a few things become visible that weren’t visible before. Where does the business lose time. Where does the business lose people who almost became customers but didn’t. Which step has exactly one person capable of doing it.

That last question is usually the most important one, and it’s almost never visible until the timeline is actually drawn out.

Other Timelines Worth Mapping

The customer journey is the obvious one, but it’s far from the only one worth mapping.

A hiring timeline. From “we need someone” to that person’s first productive week. Most businesses can tell you roughly how long this takes. Very few can tell you which specific step eats the most time, or why.

A product or inventory timeline. From order placed to item in hand, or from raw material to finished job. Especially useful anywhere physical goods or materials move through the business.

An onboarding timeline. Not hiring, but what happens after someone starts. The gap between “hired” and “actually useful” is often much longer than owners expect, and almost always undocumented.

Different businesses will care about different timelines. The technique stays the same regardless of which one you’re mapping.

How to Build One

This doesn’t require software or a consultant. Three steps, done honestly, get you most of the way there.

First, list the steps in order, for one normal case, not the exception. The goal is the typical path, not the edge case that happens once a year.

Second, mark who touches each step. Not who’s supposed to. Who actually does it, today, in practice.

Third, look for the step only one person can do. Not the step one person happens to be doing right now. The step where, if that person vanished tomorrow, the whole thing would stop cold.

That third step is usually the answer to a question the owner didn’t know they were asking.

What the Timeline Usually Reveals

The step everyone skips mapping is almost always the same step that’s quietly holding the whole business together, or holding it back. It’s rarely the step that looks the busiest. It’s the step that looks the most ordinary, the one nobody thought to question because it’s simply “how it’s always been done.”

This mirrors something worth naming plainly: the constraint in a business is rarely where the owner is looking. It hides inside whichever box has one person’s name jammed into it, unquestioned, because nobody ever laid the whole chain out end to end to see it.

A timeline is a cheap way to find that box. Cheaper than software. Cheaper than a new hire. It just takes sitting down and being honest about what actually happens, step by step, instead of what’s supposed to happen.

Close

Org charts are easy to draw and mostly decorative. Timelines are a little more work and considerably more useful. If you’ve never mapped one for your own business, a normal Tuesday is enough of a starting point.

If you map it and find a step that only you can do, that’s not a flaw. It’s just the next thing worth looking at.

Let’s take a look.


The Explorer Method

Observe  →  Listen  →  Map  →  Find Patterns  →  Experiment

Learn the Method