{
  "schema": "vedokrok.public-item.v1",
  "release_id": "VEDOKROK-SEL-5d86e1b23401e578",
  "url": "/knowledge/allow-for-the-response-delay-before-adjusting-again",
  "id": "MHC-D-RESEARCH-0184",
  "version": "0.1.0",
  "title": "Allow for the response delay before adjusting again",
  "summary": "Impatience can become part of the feedback loop.",
  "kind": "principle",
  "body": "Identify the delay between an action and its observable effect. Set a suitable review point and monitor leading information where appropriate, rather than repeatedly escalating because an immediate outcome has not moved.",
  "limits": [
    "Waiting is not appropriate when a safety signal requires immediate action. Delays are uncertain and should be investigated, not invented to defend a failing intervention."
  ],
  "topics": [
    "project-delivery"
  ],
  "intents": [],
  "source_ids": [
    "meadows-leverage-points"
  ],
  "evidence": [
    {
      "claim": "A stock changes through the difference between its inflows and outflows; delayed responses can destabilize repeated adjustments.",
      "source_id": "meadows-leverage-points",
      "role": "supports",
      "note": "Claim basis: technical_definition. Claim limit: The examples are simple models, not calibrated predictions of a complex organization.\nSource access: selected_html_passages; accessed on: 2026-09-17; inspected sections: [\"Stocks and flows; delays relative to rates of change\"].\nSource note: A classic systems essay, not new experimental evidence. No universal ranking of intervention effectiveness is inferred for the reader's situation.\nAgent release review: Checked the named definitions in the May 2025 Kanban Guide, LEI and Meadows. Non-manufacturing examples are editorial applications. The text preserves safe-stop, ownership and contextual boundaries.",
      "locator": "Stocks and flows; delays"
    }
  ],
  "use_when": [
    "You keep changing a control before the previous change could have affected the result."
  ],
  "avoid_when": [
    "Waiting is not appropriate when a safety signal requires immediate action. Delays are uncertain and should be investigated, not invented to defend a failing intervention."
  ],
  "example": "A workflow change needs several days for existing items to pass through. Reversing it every afternoon can make the observed pattern harder to interpret.",
  "check": "Has enough relevant process time passed to judge the previous adjustment?",
  "published_at": "2026-11-12T18:37:40Z",
  "review": {
    "kind": "agent",
    "label": "Agent editorial and scoped source review",
    "reviewed_at": "2026-11-12T18:37:40Z"
  },
  "knowledge_origin": {
    "release_id": "MHC-RPUB-20261112-20287590",
    "corpus_commit": "20287590ddd3999b7492df232822b6a0f7d114b1",
    "manifest_sha256": "2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95",
    "projection_sha256": "2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0",
    "published_at": "2026-11-12T18:37:40Z"
  },
  "editorial_overlay": null,
  "editorial": null,
  "notices": [],
  "sources": [
    {
      "id": "meadows-leverage-points",
      "title": "Leverage Points: Places to Intervene in a System",
      "url": "https://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/"
    }
  ],
  "relations": [],
  "collections": [
    {
      "id": "RC-MHC-PRACTICE-PROJECT-DELIVERY",
      "title": "Practical project checks",
      "url": "/collections/practical-project-checks"
    }
  ],
  "topic_hubs": [
    {
      "id": "project-delivery",
      "title": "Project delivery",
      "url": "/topics/project-delivery"
    }
  ],
  "solution_packs": []
}
