{"body":"A method is useful when it helps people notice what needs to change. A rigid sequence can do the opposite: it carries an early misunderstanding through increasingly polished work.\n\nI think of the work as a loop: frame a decision, connect the relevant knowledge, challenge the result and release with clear ownership. These are places to exercise judgment. They are not four steps that make judgment unnecessary.\n\n## One announcement, four different questions\n\nConsider the same illustrative pilot invitation used in the knowledge-object concept. Invited teams can try a campaign workspace; a general release date is unknown. An early draft announces that it will be “available to everyone next month.”\n\nFraming asks who needs to decide what. Connecting brings the pilot note and review rules into the draft’s context. Challenging exposes the unsupported audience and date. Release hands over a corrected message to the person who can approve publication.\n\nThe value is not a longer checklist. It is the ability to locate the problem. Here, better phrasing would not repair the draft. Its framing conflicts with the actual scope.\n\n## Why the arrows point back\n\nChallenge can send work back to the frame. Perhaps the intended audience was never agreed, or the brief asks for a claim that available evidence cannot support.\n\nRelease also creates feedback. If readers mistake an invitation for general access, their response is evidence that the original framing needs work. A released message is a commitment with an owner, not an end to learning.\n\n## What stays with people\n\nTools can help gather context, compare a draft with its sources and surface contradictions. Someone still has to decide whether the sources are appropriate, whether the trade-off is acceptable and whether the result should enter use.\n\nThis example is authored to explain the method. It is not a workflow running against a client system, and selecting a stage does not approve or publish anything.","context_url":"https://www.svenspoede.com/context.json","description":"Frame the decision, connect the relevant knowledge, challenge the draft and release with clear ownership. Feedback can change the frame at any stage.","lang":"en","markdown_url":"https://www.svenspoede.com/concepts/working-method/index.md","objects":[{"body":"A method is useful when it helps people notice what needs to change. A rigid sequence can do the opposite: it carries an early misunderstanding through increasingly polished work.\n\nI think of the work as a loop: frame a decision, connect the relevant knowledge, challenge the result and release with clear ownership. These are places to exercise judgment. They are not four steps that make judgment unnecessary.\n\n## One announcement, four different questions\n\nConsider the same illustrative pilot invitation used in the knowledge-object concept. Invited teams can try a campaign workspace; a general release date is unknown. An early draft announces that it will be “available to everyone next month.”\n\nFraming asks who needs to decide what. Connecting brings the pilot note and review rules into the draft’s context. Challenging exposes the unsupported audience and date. Release hands over a corrected message to the person who can approve publication.\n\nThe value is not a longer checklist. It is the ability to locate the problem. Here, better phrasing would not repair the draft. Its framing conflicts with the actual scope.\n\n## Why the arrows point back\n\nChallenge can send work back to the frame. Perhaps the intended audience was never agreed, or the brief asks for a claim that available evidence cannot support.\n\nRelease also creates feedback. If readers mistake an invitation for general access, their response is evidence that the original framing needs work. A released message is a commitment with an owner, not an end to learning.\n\n## What stays with people\n\nTools can help gather context, compare a draft with its sources and surface contradictions. Someone still has to decide whether the sources are appropriate, whether the trade-off is acceptable and whether the result should enter use.\n\nThis example is authored to explain the method. It is not a workflow running against a client system, and selecting a stage does not approve or publish anything.","boundary":"The same illustrative pilot announcement, explored as a working method.","id":"working-method","parts":[{"body":"Agree what should change for the audience and what a useful outcome would be.\n\nA pilot invitation and a general launch announcement are different tasks.","boundary":"A pilot invitation and a general launch announcement are different tasks.","example":"Invite the right teams to try the workspace. Do not promise a wider rollout.","id":"frame","label":"Frame","purpose":"Agree what should change for the audience and what a useful outcome would be.","related":["connect","challenge","release"],"source":"Example brief: eligible teams need to decide whether to join a campaign-workspace pilot.","summary":"Agree what should change for the audience and what a useful outcome would be.","title":"Name the decision before choosing the tool."},{"body":"Connect the brief, supported facts and review rules so they remain available when the draft changes.\n\nMore material is not automatically more context. Include what the decision depends on.","boundary":"More material is not automatically more context. Include what the decision depends on.","example":"Keep “invitation only” attached to the draft, alongside the unconfirmed general release date.","id":"connect","label":"Connect","purpose":"Connect the brief, supported facts and review rules so they remain available when the draft changes.","related":["frame","challenge"],"source":"The example brief, invitation-only pilot note and human review rule.","summary":"Connect the brief, supported facts and review rules so they remain available when the draft changes.","title":"Bring the necessary context into the work."},{"body":"Expose contradictions and missing support before fluency is mistaken for correctness.\n\nUnsupported wording can be rejected. Missing facts must be checked, not guessed.","boundary":"Unsupported wording can be rejected. Missing facts must be checked, not guessed.","example":"“For everyone” exceeds the pilot scope. “Next month” adds an unconfirmed date. Return both claims to the brief.","id":"challenge","label":"Challenge","purpose":"Expose contradictions and missing support before fluency is mistaken for correctness.","related":["connect","frame","release"],"source":"Example draft: “Launching for everyone next month.” Compare it with the example pilot note.","summary":"Expose contradictions and missing support before fluency is mistaken for correctness.","title":"Test the draft against what is known."},{"body":"Make a bounded handover: what is approved, who decides and what would trigger a revision.\n\nA tool can prepare the result. Publication remains a human decision, and later evidence can require a correction.","boundary":"A tool can prepare the result. Publication remains a human decision, and later evidence can require a correction.","example":"“Invited teams can now try the campaign workspace.” If readers mistake this for general access, revise the framing.","id":"release","label":"Release","purpose":"Make a bounded handover: what is approved, who decides and what would trigger a revision.","related":["challenge","frame"],"source":"Example review decision: use invitation-only wording; the responsible person approves publication.","summary":"Make a bounded handover: what is approved, who decides and what would trigger a revision.","title":"Put the result into use with an owner."}],"premise":"How does context become a decision someone can own?","relationships":[{"from":"frame","label":"defines what is needed","to":"connect"},{"from":"connect","label":"makes assumptions testable","to":"challenge"},{"from":"challenge","label":"supports a bounded decision","to":"release"},{"from":"challenge","label":"reframes when a claim fails","to":"frame"},{"from":"release","label":"returns feedback from use","to":"frame"}],"role":"Judgment in the loop","scene":"working-method","sources":[],"summary":"Frame the decision, connect the relevant knowledge, challenge the draft and release with clear ownership. Feedback can change the frame at any stage.","title":"A working method","type":"concept","updated":"2026-09-19","url":"https://www.svenspoede.com/concepts/working-method/"}],"plain":"A method is useful when it helps people notice what needs to change. A rigid sequence can do the opposite: it carries an early misunderstanding through increasingly polished work.\nI think of the work as a loop: frame a decision, connect the relevant knowledge, challenge the result and release with clear ownership. These are places to exercise judgment. They are not four steps that make judgment unnecessary.\nOne announcement, four different questions Consider the same illustrative pilot invitation used in the knowledge-object concept. Invited teams can try a campaign workspace; a general release date is unknown. An early draft announces that it will be “available to everyone next month.”\nFraming asks who needs to decide what. Connecting brings the pilot note and review rules into the draft’s context. Challenging exposes the unsupported audience and date. Release hands over a corrected message to the person who can approve publication.\nThe value is not a longer checklist. It is the ability to locate the problem. Here, better phrasing would not repair the draft. Its framing conflicts with the actual scope.\nWhy the arrows point back Challenge can send work back to the frame. Perhaps the intended audience was never agreed, or the brief asks for a claim that available evidence cannot support.\nRelease also creates feedback. If readers mistake an invitation for general access, their response is evidence that the original framing needs work. A released message is a commitment with an owner, not an end to learning.\nWhat stays with people Tools can help gather context, compare a draft with its sources and surface contradictions. Someone still has to decide whether the sources are appropriate, whether the trade-off is acceptable and whether the result should enter use.\nThis example is authored to explain the method. It is not a workflow running against a client system, and selecting a stage does not approve or publish anything.","template":"concept","title":"A working method","url":"https://www.svenspoede.com/concepts/working-method/"}