Practical writing about business systems, reliable information, responsible automation, and the work that should happen before a software decision is made.
The articles on this site are not shortened chapters from Know the Organization First. They use the same method to examine specific problems that systems professionals and business leaders encounter in their work.
Published articles
-
One Customer Record * Four Processes
A customer experiences one relationship. Inside the organization, four processes use the customer record for different work: Sales records the agreement, Operations delivers what was promised, Accounting records…
-
Trace the Work Before You Try to Fix It
A request for new software usually begins with a real problem. A team may be re-entering the same information, correcting invoices, rebuilding reports, or relying on one person…
-
Define the Requirements Before You Compare Tools
Once the organization understands how the work is actually performed, the next step is to define what the improved process must accomplish. Software evaluations often begin too soon,…
-
A Dashboard Cannot Fix an Undefined Measure
A dashboard can make information easier to see. It cannot decide what the information means. When leaders disagree with a report, the immediate request is often to change…
-
An Integration Moves Data. It Does Not Decide Which Data Is True.
An integration moves data from one place to another. That can remove manual entry, reduce delay, and make information available to the people and systems that need it.…
New articles will be added automatically as they are published. Book updates will also be shared on LinkedIn.