{ "schema_version": "core-reviewed-term-ai-handoff-v1", "version": "core-reviewed-term-ai-handoff-v1", "contract_status": "preview", "distribution": "per_term_read_only_ai_handoff", "no_write_operations": true, "canonical": { "url": "https://core.yogoq.com/en-US/core/5w1h", "slug": "5w1h", "locale": "en-US" }, "summary": { "schema_version": "core-reviewed-term-summary-v1", "term_id": "f9e61d11-c057-5354-a75f-5510c66cb2fa", "canonical_slug": "5w1h", "canonical_url": "https://core.yogoq.com/en-US/core/5w1h", "locale": "en-US", "display_name": "5W1H", "english_name": null, "abbreviation": null, "short_definition": "5W1H is a decision tool for turning problem clarity into a concrete question map.", "quality": "reviewed", "publication_status": "published_reviewed", "version": "core-reviewed-term-summary-v1", "last_reviewed_at": "2026-05-14T00:00:00.000Z", "sources_count": 2, "limitations_key": "core-trust-policy-v1-2026-06-22" }, "content": { "definition": { "key": "definition", "title": "一言でいうと", "text": "5W1H is a decision tool for turning problem clarity into a concrete question map.", "items": [] }, "formula": null, "boundary": null, "usage": [ { "key": "meaning", "title": "意味", "text": "5W1H defines the working structure used when a problem statement is vague and the team must separate who, what, when, where, why, and how before choosing a solution. In 5W1H, the important work is not the template itself; the page states the decision boundary, required evidence, owner, and review cadence. Used well, 5W1H turns vague discussion into an auditable management choice and exposes trade-offs before resources are committed.", "items": [] }, { "key": "usage", "title": "役立つ場面", "text": "5W1H changes decisions by making problem clarity visible before commitments are made. It helps leaders decide whether to start, stop, resize, or resequence work based on evidence rather than meeting momentum. It reduces rework because assumptions, owners, and review points are explicit enough to challenge.", "items": [ "5W1H changes decisions by making problem clarity visible before commitments are made.", "It helps leaders decide whether to start, stop, resize, or resequence work based on evidence rather than meeting momentum.", "It reduces rework because assumptions, owners, and review points are explicit enough to challenge." ] }, { "key": "usage", "title": "使い方のポイント", "text": null, "items": [ "Define the decision, owner, and time horizon before filling in the question map.", "Separate evidence from opinion so the tool supports judgment instead of decorating a preferred answer.", "Record assumptions and review dates because problem clarity changes as the operating context changes.", "Use the output to choose a management action, not merely to produce a document.", "Retire or revise the tool when the decision boundary no longer matches the work." ] } ], "misunderstandings": [ { "key": "misunderstandings", "title": "判断するときの注意点", "text": "The main risk is false precision: a neat question map can hide weak evidence or political assumptions. Check whether the tool is describing reality or merely rationalizing a decision that has already been made. If the output does not change a priority, owner, resource level, or review date, the analysis is probably too soft.", "items": [ "The main risk is false precision: a neat question map can hide weak evidence or political assumptions.", "Check whether the tool is describing reality or merely rationalizing a decision that has already been made.", "If the output does not change a priority, owner, resource level, or review date, the analysis is probably too soft." ] }, { "key": "misunderstandings", "title": "よくある誤解 / 落とし穴", "text": null, "items": [ "5W1H is not the decision itself; it is a structure for making and reviewing the decision.", "More detail is not automatically better. For 5W1H, the useful level is the one that changes a management action.", "A one-time workshop is not enough; the value comes from keeping the artifact current while the decision is live." ] } ], "examples": [ { "key": "examples", "title": "最小例", "text": "A leadership team uses 5W1H because a problem statement is vague and the team must separate who, what, when, where, why, and how before choosing a solution. They draft the question map, name one accountable owner, and list the evidence that would change the recommendation. During the 5W1H review, one assumption proves weak, so the team narrows the scope and schedules a follow-up review. The 5W1H decision record now shows the action taken, the risk accepted, and the signal that would trigger a change.", "items": [] } ], "comparisons": [ { "key": "comparisons", "title": "似ている言葉との違い", "text": "Issue tree | Breaks a problem into logic branches | 5W1H checks whether the basic operating facts are complete RACI matrix | Assigns decision roles | 5W1H clarifies the situation before ownership is assigned Scope | Defines what is in and out | 5W1H supplies the facts used to draw that boundary", "items": [ "Issue tree | Breaks a problem into logic branches | 5W1H checks whether the basic operating facts are complete", "RACI matrix | Assigns decision roles | 5W1H clarifies the situation before ownership is assigned", "Scope | Defines what is in and out | 5W1H supplies the facts used to draw that boundary" ] } ], "faq": [ { "question": "What decision should 5W1H support?", "answer": "5W1H should support a specific management choice: what to do, who owns it, what trade-off is accepted, and when the choice will be reviewed." }, { "question": "How detailed should the question map be?", "answer": "5W1H should be detailed enough to expose assumptions, ownership, and evidence gaps, but not so detailed that the team stops making decisions." }, { "question": "How often should 5W1H be updated?", "answer": "Update 5W1H when material evidence changes, when ownership changes, or when the review cadence says the decision must be revisited." } ] }, "sources": { "source_refs": [ "concept:5w1h:en-US", "concept:5w1h:ja-JP", "concept:five-ws-and-one-h:en-US", "concept:five-ws-and-one-h:ja-JP", "manual_merge_map:next-exact-duplicates-2026-04-28" ], "visible_sources": [ { "label": "Principles of Management (OpenStax)", "url": "https://openstax.org/details/books/principles-of-management", "kind": "tier_s" }, { "label": "Wikipedia reference: 5W1H", "url": "https://en.wikipedia.org/wiki/Five_Ws", "kind": "supplemental" } ] }, "related_terms": [ { "topic_id": "04977a76-1418-5883-be32-c0c37e58ac32", "canonical_slug": "scope", "canonical_url": "https://core.yogoq.com/en-US/core/scope", "title": "Scope", "relation_type": "used_together" }, { "topic_id": "0a61b3e0-9651-5d4e-aafe-1045319955af", "canonical_slug": "priority", "canonical_url": "https://core.yogoq.com/en-US/core/priority", "title": "Priority", "relation_type": "used_together" }, { "topic_id": "4f50d00a-56e6-5150-a628-e54d19dd1040", "canonical_slug": "agenda", "canonical_url": "https://core.yogoq.com/en-US/core/agenda", "title": "Agenda", "relation_type": "related" } ], "quality": { "quality": "reviewed", "publication_status": "published_reviewed", "source_count": 2, "last_reviewed_at": "2026-05-14T00:00:00.000Z", "trust_policy_version": "core-trust-policy-v1-2026-06-22" }, "limitations": { "policy_version": "core-trust-policy-v1-2026-06-22", "professional_advice_boundary": "reference_only_not_professional_advice", "text": "This page is reference information for research and learning. For accounting, legal, finance, health, security, or other individual decisions, confirm against primary sources or qualified professionals.", "items": [ "Public pages support general understanding and practical context; they are not professional advice for individual cases.", "Fast-changing information such as regulations, accounting standards, prices, product specs, and legal requirements should be checked against primary sources before final decisions.", "Even when AI-assisted drafting or audit is used, publication relies on quality gates and human-readable evidence." ] } }