Operational values
Standards for better operational decisions.
StateWorks is being developed around a clear discipline: understand the evidence, establish the most defensible state and select the first justified action.
These values guide how we intend to reason, challenge and improve. They are decision standards, not guarantees, service levels or claims of operational perfection.
Evidence Before Assumption
Start with observable measurements, events, records, relationships and history. An isolated alert is an observation; it is not proof of a wider condition.
Ask: what does the available evidence actually support?
Understand Before You Suppress
Noise can be misunderstood evidence. Before reducing or suppressing a signal, examine what it is reporting, why it exists and which risk could be hidden.
Suppress only when the evidence supports doing so.
Improve, Don’t Just Maintain
Operational work should create useful learning or leave the environment in a better understood, more reliable or more manageable state.
Ask: what justified improvement can be made today?
Action Must Be Justified
Recommendations and automation should not outrun the evidence. Where the state is uncertain, the right first action may be to gather more evidence.
Evidence proves state; state determines whether action is warranted.
Observability Over Isolated Monitoring
Monitoring detects conditions. Operational understanding also requires dependencies, configuration, history and context to explain behaviour.
The objective is trustworthy understanding, not a larger alert count.
Vendors Are Evidence Sources, Not Truth
Platforms contribute signals, records and control surfaces. No individual product defines operational reality on its own.
Combine evidence and make platform limitations visible.
Make Decisions Defensible
A later reviewer should be able to see what evidence existed, which state was established and why a particular action was selected.
If the reasoning cannot be explained, it should be challenged.
Leave Systems Better Than You Found Them
Success is not measured by closing tickets or silencing alerts alone. It is measured by stronger evidence, clearer understanding and fewer avoidable failures.
Record the outcome and validate whether the change improved confidence.
What these values mean in practice
StateWorks will not recommend a platform, process or automation merely because it is available. It must improve the available evidence, make the state more defensible, make action safer or make the result easier to verify.
Beyond headline metrics
Measures should explain the outcome, not replace it.
Uptime, SLA attainment, alert volume, compliance percentages, ticket closure and automation results can all provide useful operational evidence. A headline measure does not, by itself, establish that the business service was protected, that the underlying state was understood or that the environment improved.
StateWorks considers the scope, population, completeness, age, exclusions, dependencies and business context behind each measure. The measure supports the operational state; it does not become the state merely because it fits neatly inside a monthly report.
| Headline measure | The operational question StateWorks asks |
|---|---|
| 99.99% uptime | Which service or transaction was measured, over what period, with which exclusions, dependencies, partial degradations and user impact? |
| 95% of SLAs met | Was meaningful action taken, was the service restored, did the condition recur and was the result verified? |
| Alert volume reduced | Was signal quality improved through correlation and engineering, or was visibility reduced through threshold changes or suppression? |
| Tickets closed | Was the underlying condition resolved, or did the workflow simply reach a closed status? |
| Compliance improved | Which population was assessed, how current was the evidence and which assets remained stale, offline, excluded, unknown or blocked? |
| Automation succeeded | Did the authorised action reach the intended state, and was the effect verified safely? |
StateWorks does not measure success by how much operational activity a service produces. It asks whether the evidence became clearer, the state more trustworthy, the first action more justified and the effect of that action verifiable.
Read the full PerspectiveOur reasoning discipline
Evidence → State → Action
Evidence establishes what can be defended. State determines whether intervention is warranted. The strongest defensible evidence pattern selects the first action focus, while exceptions and uncertainty remain visible for deliberate review.