The work library
Work across operations, data, software and service design, with evidence and limits for each example.
All work
Filter by kind, problem or state
15 entries in the collection.
No entries match this filter yet.
Back to the complete collection| Entry | Kind / state | Where / years | Evidence | Problem families |
|---|---|---|---|---|
| The whole book of business on one mapCase study | build running | Purchasing and operations 2026 | reported | Reporting and visibility, Account coverage, Custom applications, Data management |
| A bilingual pump form and the fleet workflow behind itCase study | build running | Purchasing and operations 2026 | reported | Reporting and visibility, Field to office, Custom applications, Data management, Configuration and integration |
| Business metrics and reporting platformCase study | build running | Purchasing and operations 2026 | reported | Purchasing, Reporting and visibility, Data management, Custom applications |
| Rebuilding purchasing controls during an ERP migrationCase study | career career | Purchasing and operations January 2026 to present | reported | Purchasing, Operations and audits, Ongoing improvement |
| A personal workspace that answers from my own records and links to the sourceCase study | build running | independent April 2026 to present | measured | Business knowledge, Custom applications, Data management, Configuration and integration |
| A website built around services and their evidenceLibrary entry | build prototype | independent 2026 | reported | Websites, Business knowledge |
| Document checks that bind claims to a sourceLibrary entry | build running | independent 2026 | reported | Business knowledge, Data management |
| A filing-research foundation with dated sources and verification checksLibrary entry | build prototype | independent 2026 | none | Business knowledge, Data management |
| A marine service business designed around a permanent per-hull recordLibrary entry | design design | independent 2026 | none | Field to office |
| An ERP's behavior mapped for the people and the agents who had to use itLibrary entry | method archived | Purchasing and operations 2026 | none | Business knowledge |
| Read-only ERP checks with explicit missing-source resultsLibrary entry | build running | Purchasing and operations 2026 | reported | Reporting and visibility, Data management, Ongoing improvement |
| A price baseline that refuses to invent a savingLibrary entry | build running | Purchasing and operations 2026 | reported | Purchasing, Reporting and visibility, Data management |
| Order logistics and AP/AR across a distribution order bookLibrary entry | career career | Distribution logistics January 2024 to December 2025 | reported | Purchasing, Reporting and visibility, Operations and audits, Data management, Configuration and integration |
| 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.