{
  "schema": "vedokrok.public-item.v1",
  "release_id": "MHC-RPUB-20260920-75ad787a",
  "url": "/knowledge/protect-improvement-time-from-recurring-operational-work",
  "id": "MHC-D-RESEARCH-1016",
  "version": "0.1.0",
  "title": "Protect improvement time from recurring operational work",
  "summary": "Keeping the queue moving and reducing tomorrow's queue are different jobs.",
  "kind": "protocol",
  "body": "Identify recurring operational work that leaves the system essentially unchanged and grows with demand. Measure its burden, then agree protected capacity for a specific lasting improvement. Do not label every unpleasant task as toil or assume that buying another automation tool removes the underlying work.",
  "limits": [
    "Google's published allocation target is not a universal optimum. Maintain essential coverage and examine individual overload; a comfortable team average can hide it."
  ],
  "topics": [
    "work-05-transferable-expertise"
  ],
  "intents": [],
  "source_ids": [
    "RS-A2A2F68EE5E28711"
  ],
  "evidence": [
    {
      "claim": "Google SRE defines toil as recurring operational work with little enduring value and uses explicit allocation limits to protect engineering work.",
      "source_id": "RS-A2A2F68EE5E28711",
      "role": "supports",
      "note": "Not all repetitive or disliked work is toil, and Google's allocation target is an organizational policy rather than a universally optimal percentage.",
      "locator": "Toil Defined; Why Less Toil Is Better"
    }
  ],
  "use_when": [
    "Recurring support tasks consume the time needed to make those tasks less necessary."
  ],
  "avoid_when": [
    "Google's published allocation target is not a universal optimum. Maintain essential coverage and examine individual overload; a comfortable team average can hide it."
  ],
  "example": "Repeated manual export corrections consume support time. A validated input rule removes one recurring cause instead of merely making the correction checklist prettier.",
  "check": "Protected time produces a measurable reduction or a clear finding that the attempted improvement did not help.",
  "steps": [
    "Track a representative period of hands-on recurring work separately from elapsed waiting time.",
    "Agree a local capacity boundary and choose one improvement that could reduce the recurring burden.",
    "Check actual workload after the change, including maintenance and exception handling."
  ],
  "sources": [
    {
      "id": "RS-A2A2F68EE5E28711",
      "title": "Eliminating Toil",
      "url": "https://sre.google/sre-book/eliminating-toil/"
    }
  ],
  "relations": [
    {
      "from": "MHC-D-RESEARCH-1016",
      "to": "MHC-D-RESEARCH-1015",
      "type": "useful_with",
      "url": "/knowledge/agree-what-reliability-loss-will-pause-ordinary-changes"
    }
  ],
  "collections": [
    {
      "id": "RC-D7E536E5F014E0EC",
      "title": "Turn experience into expertise someone else can use",
      "url": "/collections/turn-experience-into-expertise-someone-else-can-use"
    }
  ]
}