How complex operations actually break, and what to do about it
Written for people running operations where work crosses several functions and systems. Project delivery comes first, because that is where we concentrate. Earlier guides on service operations and systems integration are kept below.
These guides use the vocabulary of the operations they are written for. The underlying questions are the same ones an Architecture Sprint answers: who owns which state, how a decision propagates, and which system is the record.
Project delivery
Original BoRo thinking on why multi-project delivery gets harder to coordinate as it grows. Solar + BESS project delivery
Human Middleware in Project Delivery
How experienced people become the integration layer between engineering, procurement and construction.
Read guideCoordination Latency
How long does it take for one project decision to become operational reality?
Read guideEngineering Change Propagation
How an approved change should move through engineering, procurement, project controls, construction and commissioning.
Read guideFragmented Operational State
Why individually good systems can still produce an incoherent project operation.
Read guideProject Delivery Capacity
Why adding more projects can create disproportionate coordination overhead.
Read guideOperating models
What Field Service Management Is and When a Company Needs It
A guide to field service management for service, maintenance, and installation companies with field teams.
Read guideSpreadsheets vs Work Order Software: When It Stops Being Enough
Criteria to know when spreadsheets stop working for work orders, technicians, assets, SLA, parts, and administrative close.
Read guide7 KPIs for a Field Service Company
Useful field service indicators: preventive compliance, SLA, backlog, pending parts, work order close, and billing.
Read guideService operations
How to Manage Field Technicians Without Losing Traceability
How to coordinate technicians, routes, work orders, evidence, status, and SLA without depending only on messages or calls.
Read guideHow to Reduce the Time Between Service Visit and Invoice
How to connect technical close, evidence, parts, approvals, and ERP so billing does not reconstruct the visit.
Read guideHow to Control Preventive and Corrective Maintenance by Asset
How to organize preventive work, corrective work, history, failures, parts, evidence, and indicators by installed asset.
Read guideHow to Manage Elevator Maintenance Contracts Digitally
How to digitize contracts, calendar, elevators, work orders, logs, failures, parts, quotes, and history.
Read guideSystems and integration
How to Digitize Work Orders Without Replacing Your ERP
How to move work orders into a digital system connected to assets, technicians, evidence, and billing without replacing the ERP.
Read guideERP vs Field Service: Why They Do Not Solve the Same Problem
Differences between ERP and field service, and how to integrate them without duplicating data or forcing the operation.
Read guideHow to Integrate Defontana with a Field Service Operation
Criteria to connect Defontana with work orders, parts, evidence, ready-to-bill states, and operational reporting.
Read guide