Work: ongoing improvement
Work across operations, data, software and service design, with evidence and limits for each example.
All work
Filter by kind, problem or state
4 entries: ongoing improvement.
No entries match this filter yet.
Back to the complete collection| Entry | Kind / state | Where / years | Evidence | Problem families |
|---|---|---|---|---|
| Rebuilding purchasing controls during an ERP migrationCase study | career career | Purchasing and operations January 2026 to present | reported | Purchasing, Operations and audits, Ongoing improvement |
| Read-only ERP checks with explicit missing-source resultsLibrary entry | build running | Purchasing and operations 2026 | reported | Reporting and visibility, Data management, Ongoing improvement |
| Operations, billing and staffing for a service business with 500 active membersLibrary entry | career career | Service operations January 2022 to January 2024 | reported | Purchasing, Reporting and visibility, Operations and audits, Configuration and integration, Ongoing improvement |
| Rules, gates and deployment for a fleet of AI agentsCase study | method running | independent 2026 | measured | Method, Ongoing improvement |
How this list is kept honest
Every entry carries a dated source review. A running system, evidence of use and a measured outcome are separate things. The entry states which ones the record supports.
Related and superseded repositories are grouped into the work they support. Adopting or configuring an existing tool is described as that contribution; a fork is not evidence of original authorship.
Career statements are my own account, checked against my records. Engineering checks and synthetic demonstrations establish only the behavior they actually exercise.