A working paper, not a blog

Most pages explaining a measure give you a formula and stop. You are left holding a definition you cannot use.

So every piece is built around a worked example with real numbers, set out so you can redo it against your own.

What we publish

Three pieces a week, on monday, wednesday, friday.

Five sections in rotation: fundamentals, metrics and maths, lean tools, case walkthroughs, and simulation and what if. A piece belongs to one of them.

The standard

Every piece has to clear all five of these before it runs.

1. A worked example with real numbers. Not a formula with letters in it. A reader has to be able to follow the arithmetic and reproduce it.
2. A point of view. A summary of an encyclopedia entry is not worth anybody's time and they can already find one. If a piece has nothing to argue, it does not run.
3. Nothing asserted that was not checked. Where a figure is illustrative it says so in the block it sits in. Where it comes from somewhere, the source is named in the sentence.
4. No sales pitch at the end. There is no call to action under a piece on this site, and no field in the system to put one in. A link goes in where it genuinely helps a reader, in the writer's own words, and nowhere else.
5. One named byline, on one beat. A name and the subject that name covers, which is what a byline is for. See who writes it.

Corrections

Corrections are made on the piece, with the date. Write to editor@processmgr.com.

Who publishes this

Process Daily is published by ProcessMgr, an independent publisher covering process improvement practice and the software that supports it. Some of the vendors written about across its titles are commercial partners of the publisher, and that is set out on the disclosure page. It is stated there in plain language rather than buried, because a reader deciding whether to trust a number should not have to go looking for the reason not to.