Intrenion

Analytical Assessment and Decision Reconstruction Prompt

Christian Ullrich
Last updated: 2026-02-08

This prompt outlines a disciplined approach to working with messy organizational material. It separates analytical assessment from decision reconstruction. Unstructured notes, meeting fragments, or documents are first stabilized by distinguishing the situation, the assessment, and the consequences if no decision is made. Only after this separation does the prompt reconstruct the decision statements required for execution to proceed. The goal is to prevent situations, assessments, consequences, and commitments from being mixed up or substituted for one another.

Prompt

Prompt

Begin with exactly one sentence in English acknowledging these instructions, then detect the language of the user’s input material and write all following output in that detected language.

General instructions:

• Use the user-provided material as the sole source.
• Assume inputs are messy, incomplete, or contradictory.
• Do not search the web.
• Avoid explanations of concepts unless explicitly asked.
• Do not use en or em dashes in sentences or headers; hyphens are acceptable.
• Do not use thematic breaks.
• When producing Situation, Assessment, Consequence, or Decisions, write each section as a list of bullet points.
• In those sections only, each bullet point must consist of exactly one complete sentence.
• Create as many bullet points as make sense for the content.
• For all other responses, answer conversationally unless explicitly instructed to generate structured output.
• Write in a precise, factual style without rhetorical language.
• Apply only the rules relevant to the section requested by the user, while keeping all general formatting and language constraints (“General instructions”) in force.
• German translation 1: Situation = Ausgangslage, Assessment = Einordnung, Consequence = Konsequenz; Describe = Ansprechen, Assess = Beurteilen, Conclude = Folgern; Decisions = Entscheidungen
• German translation 2: “We decide” = “Wir entscheiden, dass”; “because this gives us” = “weil dadurch”; “instead of” = “, statt”; “and accept that” = “, und akzeptieren, dass”; “without” = “ohne”

Connecting the worlds:

• Note that Structured Analytical Assessment and Decision Clarity serve different purposes.
• Structured Analytical Assessment is used to describe and analyze a situation without creating binding commitments.
• Decision Clarity reconstructs the decision statements required for execution to proceed, based on the material produced so far.
• User-provided note structure, headings, or section labels must not be trusted as correct classification and must be treated as provisional input that may require reclassification.

Workflow:

• Typical use starts with unstructured notes, fragments, or meeting materials in any format.
• This material is first stabilized through a Structured Analytical Assessment to separate the situation, the assessment, and the consequences.
• Decision Clarity is then applied to the stabilized material to reconstruct the decision statements required for execution to proceed.
• Inputs may be corrected, expanded, or revised at any point, and earlier outputs may be replaced or regenerated.
• You treat the current conversation context as the working material unless explicitly told otherwise.
• If the user skips or reverses steps, adapt to the current input rather than enforcing a sequence.

Structured analytical assessment:

• The approach separates three different types of statements, not activities or text formats.
• The Situation describes a problem or condition as it appears. It states the case, where it occurs, the extent, and the observable effects, without explaining causes or proposing actions. The goal is a clear definition and delimitation.
• The Assessment analytically examines the situation. It identifies causes, relationships, constraints, limitations, and alternatives, and evaluates relevance and impact, without making a decision.
• The Consequence derives the effects of the assessment for the situation by making explicit what becomes unavoidable, unstable, or constrained if no decision is made, without selecting a course of action or assigning ownership.
• In the Consequence section, prefer formulations that begin with “Without …” to anchor each statement explicitly in the absence of a decision.
• The Situation, Assessment, and Consequence correspond to the three modes of thinking described as Describe, Assess, and Conclude.
• The three types of statements must remain separate so that description, analysis, and consequence are not collapsed into each other.
• Create the section requested by the user: Situation, Assessment, or Consequence, and omit any section that does not apply.
• Organize the content independently and logically, even if the notes are unsorted or contradictory.
• Separate content from other levels of thinking on your own, and mentally shift it rather than mixing it.
• If a statement describes observable conditions, place it in Situation; if it explains causes, constraints, or relationships, place it in Assessment; if it states what becomes unavoidable, unstable, or constrained in the absence of a decision, place it in Consequence.

Decision reconstruction:

• Generate only as many decisions as there are distinct, unavoidable commitments in the material, and do not create additional decisions to improve coverage, balance, or completeness.
• Generate a list of decisions for the selected topic, choose the number yourself, and include only items that are meaningfully distinct from all previously created items.
• Each item must contain exactly one sentence and no subheadings.
• Each sentence must start with the phrase “We decide” in the output language.
• Each sentence must express a fundamental trade-off instead of an indecision, a trivial choice, or a general good-practice statement.
• When multiple plausible alternatives or downsides exist, choose the single alternative and downside that most meaningfully constrain behavior in practice.
• If a concrete downside is not explicitly stated in the input, infer the most likely real-world cost of the choice based on typical organizational, political, or governance constraints, preferring loss of enforceability, authority, closure, or conflict resolution power over generic variability, quality differences, or user behavior drift.
• Each decision must either reduce options, commit resources, exclude alternatives, accept a risk, or create a meaningful constraint.
• In each sentence, after stating the decision, add a short benefit clause introduced with the phrase “because this gives us” in the output language, explaining why this option is chosen with a concrete operational effect in the Situation.
• After the benefit clause in the same sentence, include the phrase “instead of” in the output language to state what attractive or plausible alternative is rejected clearly.
• The “instead of” clause must name a concrete, executable alternative action, process, or governance setup that could plausibly be chosen, not an outcome, effect, intention, preference, abstract standard, or any restatement, negation, or mirror of the benefit clause.
• After the “instead of” clause in the same sentence, add a short consequence clause that states what downside is accepted, using the phrasing “, and accept that” in the output language, followed by a concrete negative outcome.
• The downside must logically result from the selected option and must not still hold if the alternative were chosen.
• Avoid soft or vague verbs such as ensure, promote, support, enable, improve, or similar phrasing that describes intentions rather than hard choices.
• Avoid universally agreeable statements or management platitudes.
• Each decision must be operational and specific enough that someone could take concrete action based on it.
• For any subsequent review rounds after your initial output, when I mark a specific decision item with feedback or a change request, you must adjust only that item and copy all other items from the previous version verbatim.

Classification review

Structured notes often appear more precise than they are. A second pass checks whether statements truly belong to their assigned categories and exposes ambiguity created by premature structure. It preserves the analytical separation between description, analysis, and consequence.

Prompt

Reproduce “SECTION” and move any statements that do not belong there, briefly explaining each move.

Listening questions

This prompt generates listening questions to guide attention before a meeting. The questions help focus on situations, assessments, consequences, and decisions as they appear, without forcing structured note-taking. They are not meant to be fully answered during the discussion; brief annotations are sufficient. The goal is to make commitments and decisions easier to notice.

Prompt

Generate listening and attention-guiding questions for a meeting or topic.

• Do not search the web.
• Do not use en or em dashes; hyphens are acceptable.
• Do not use thematic breaks.
• Use active voice.

Purpose and use:

• These questions are not meant to be fully answered during the meeting.
• They are used before the meeting to guide the note-taker on what to listen for.
• Notes taken during the meeting can be messy, fragmented, and unstructured.
• The questions should help the user notice when situations, assessments, consequences, or decisions are stated or implied.

Output:

• Generate around ten questions.
• Do not add commentary, explanations, or extra formatting.
• Output only the questions, each on its own line.

Question requirements:

• Each question must be concrete and trigger-based, not abstract.
• Questions must focus on what to notice when something is said or implied, not on how to document it.

Scope:

• The questions should together cover the full scope of the topic, not cluster around a single angle.
• The questions should work even when statements are indirect, political, or left unsaid.

Input variables:

• Answer in the LANGUAGE language.
• Project title (context only): PROJECT_TITLE
• Project description (context only): PROJECT_DESCRIPTION
• Meeting title (primary focus): MEETING_TITLE
• Meeting notes (primary focus): See below.

Meeting description

The project/meeting description is an explicit, non-binding overview intended solely to provide shared orientation before a meeting. It may include tentative goals, assumptions, preferences, or partial ideas, but none of these are treated as facts or decisions. Its sole purpose is to make it easier to notice and challenge implicit commitments, not to justify or predecide outcomes.

Prompt

Write a project/meeting description for the “TBD”, based on the answers to the project/meeting overview questions below.

1. What is this project/meeting about in one plain sentence, without justification or solution language?
   • TBD…
2. What problem or situation triggered the project/meeting to exist?
   • TBD…
3. What outcome or change is the project/meeting meant to produce if it works as intended?
   • TBD…
4. What are the main areas, dimensions, or aspects the project/meeting needs to address?
   • TBD…
5. What constraints, limits, or conditions shape the project/meeting environment?
   • TBD…
6. What assumptions are currently being made about how the project/meeting will work or what will be true?
   • TBD…
7. What feels unclear, unstable, or potentially conflicting in the project/meeting as it is currently understood?
   • TBD…

Classical note structure

1. Situation

1. What condition exists, and how is it observed?
2. Where does it occur, and who or what is affected?
3. When did it emerge, and how has it evolved?
4. What concrete effects are visible now?

2. Assessment

1. What causes or drivers could explain this condition?
2. What constraints or dependencies matter?
3. What plausible alternative explanations exist?
4. Why does this matter for the organization?

3. Consequence

1. What becomes unavoidable if no decision is made?
2. What risks or losses increase over time?
3. What options or degrees of freedom will close?

4. Decisions

1. Which decisions do participants believe were made or implied?

Reworking notes

Prompt

Begin with exactly one sentence in English acknowledging these instructions, then detect the language of the user’s input material and write all following output in that detected language.

General instructions:

• You are given an existing document whose structure, headings, and sequencing must be ignored and treated only as raw material for the target format.
• Your task is not to improve, evaluate, or rewrite the content, but to transform it into structured notes that separate different types of statements so that later analytical assessment and decision reconstruction are possible.
• Use the user-provided material as the sole source.
• Do not add new ideas, assumptions, or recommendations.
• Do not optimize language or argue for correctness.
• Do not generate decisions.
• Do not explain concepts or methods.
• Do not use en or em dashes; hyphens are acceptable.
• Write each section as bullet points.
• Each bullet point must be exactly one complete sentence.
• Create as many bullet points as required by the material.
• Each bullet point must be placed under the section whose guiding question it directly answers, and bullets must not be placed in a section unless they clearly answer one of that section’s questions.
• The questions under each section are fixed and must not be changed, added to, removed, merged, or rephrased.
• If a sentence mixes multiple types of thinking, split it into multiple bullets and place each in the correct section.
• If the source material contradicts itself, capture both sides in separate bullets.
• If something sounds like a recommendation, treat it as decision-relevant material, not as a decision.
• German translation: Situation = Ausgangslage, Assessment = Einordnung, Consequence = Konsequenz; Describe = Ansprechen, Assess = Beurteilen, Conclude = Folgern; Decisions = Entscheidungen

Output structure:

1. 1. Situation
   2. What condition exists, and how is it observed?
   3. Where does it occur, and who or what is affected?
   4. When did it emerge, and how has it evolved?
   5. What concrete effects are visible now?
2. 1. Assessment
   2. What causes or drivers could explain this condition?
   3. What constraints or dependencies matter?
   4. What plausible alternative explanations exist?
   5. Why does this matter for the organization?
3. 1. Consequence
   2. What becomes unavoidable if no decision is made?
   3. What risks or losses increase over time?
   4. What options or degrees of freedom will close?
4. 1. Decisions
   2. Which decisions do participants believe were made or implied?