What this site is for

a plain statement of what I've found, and what I won't claim

This site exists to help you get better at something specific: seeing where the time goes in work you do over and over.

Not faster people. Not more tools. Just an honest look at how long things actually take, and why — which turns out to be a question almost nobody can answer, including the people running the process.

The tools cost nothing to use. The mapping costs the attention of people who do the work, and that is the real price — there is no version of this where the understanding arrives without the effort. If you take the method and never speak to me, that's a success.

What I've found

Most of the time, nobody is working. Map a recurring process end to end and you'll usually find that one to five percent of the elapsed time is somebody actually doing something. The rest is the thing sitting, waiting for a person, an approval, a system, or a decision. That ratio surprises everyone the first time, including me.

Your team isn't slow. This is the part worth saying out loud in front of them. The work doesn't spend its life with people — it spends it between them. Everyone could work twice as fast and the number would barely move. That's not an excuse; it's a relief, and it points you somewhere useful.

Say which numbers you actually know. Some are observed, some are guessed, some are verified against timestamps. Label them, and write down what you expect before you pull the logs. A number with its origins attached survives a meeting that a confident number won't — and it's the difference between a method and a sales pitch.

There's more in the tools and the guides: how to split delay you own from delay nobody was watching, why a long wait quietly creates rework two steps later, why cutting queues makes things finish sooner without making more of them, and why a fully improved process still isn't all green. But those three are the ones worth knowing before you do anything else.

What this won't do

It won't price your improvement. Every dollar figure in these tools is what your process costs to run — hours, at your rate, at your volume. Not what it costs to measure. Not what it costs to fix. Not a fee. When a diagnostic quietly includes the cost of the person selling it, the numbers stop being worth trusting.

It won't mix estimates into facts. Cost of delay, quality escapes, breach exposure — those are modelled from published research, not your ledger. They're shown separately and never folded into your run cost.

It won't pretend all your delay is flow. Sometimes most of it isn't. Telling you which part this can't explain is what makes the part it can explain believable.

It won't always tell you to keep the work in-house. Sometimes the honest read is that a partner does it better. A method that can only reach one conclusion isn't a method.

It won't promise you a perfect process. There isn't one. The loop doesn't end in a finished map; it ends in the habit of counting again, because next quarter's demand will make something else the biggest wait.

It won't hide the misses. When people run this and it doesn't hold up, I publish that too. Otherwise you'd have no way to judge whether any of it is real.

Try it right now

You don't need the tools for the first step. Two questions:

**How many are open right now?
How many finish in a week?**
Divide the first by the second. That's how long each one really takes.
Does that work for your business?

Fifteen seconds, no software. If the answer bothers you, everything else here is free and waiting.

And then tell me how it went

Genuinely — especially if it didn't work. One process, mapped honestly, with a result either way is worth more to me than a hundred people agreeing with the idea.

don.woodward@dewood.org

Don Woodward · CISSP · C|EH · ITIL Expert

None of the underlying thinking is mine: Little's Law, Reinertsen on cost of delay, George on process cycle efficiency, Hubbard on estimating things you think you can't, and Deming, Ohno and Goldratt behind all of it. What's new is pointing it at security and business operations, where almost nobody has.