Skills· Content & Editorial

    The Understanding Grid

    Takes a technical topic and explains it across multiple levels of understanding at once, from a layperson analogy to an expert summary, so you never have to reformulate the same explanation for different audiences again.

    writingstructuring

    Description

    Example scenario

    An AI consultant is preparing for a board meeting and needs to explain what Retrieval Augmented Generation (RAG) is and why the method matters for the company's strategy. She gives the skill the technical topic and the audiences involved. The skill delivers three explanation levels: a short elevator version for the first mention, a fuller version for the board meeting, and a technical deep dive for the IT team.

    Steps

    Every step shows who carries it out: icon, colour and label together indicate whether a person acts, whether it runs automatically, whether a result is produced, or whether an approval is required.

    01Person

    The technical topic, the audience with its prior knowledge, and the context for what the explanation is needed for are provided.

    02Automated

    03Automated

    04Result

    05Person

    Key
    PersonAutomatedResultApproval

    In use

    Technical topic or concept to be explained

    Required

    Audience(s) and their prior knowledge

    Required

    Context for what the explanation is needed for

    Required

    Desired levels of understanding

    Optional

    Maximum length per level

    Optional

    Industry context for suitable examples

    Optional

    Output

    Two to three explanation levels, each with a core statement in one sentence, a matching analogy, the reason for its relevance to the respective audience, and follow-up questions for deeper exploration.

    Skill Text

    # ASSIGNMENT
    You explain a technical topic for several audiences at once, each explanation understandable on its own without any loss of factual accuracy. The goal is a set of two to three explanation levels for the same topic, so the same thing never has to be reformulated from scratch each time.
    
    # INPUTS
    - Technical topic or concept to be explained (required)
    - Audience(s) with their respective prior knowledge (required)
    - Purpose of the explanation: presentation, training, content (required)
    - Desired levels of understanding: layperson, advanced, expert (optional)
    - Maximum length per level (optional)
    - Industry context for suitable examples (optional)
    
    # HOW THE EXPLANATION TAKES SHAPE
    
    **Extract the core.** First, determine what every audience absolutely needs to understand, compressed into a single sentence. Technical terms that appear at the layperson level are replaced with everyday language. The explanation always opens with the big picture, never with details.
    
    **Build the levels.** Starting from the core, the levels are developed from simple to complex, each understandable on its own, without requiring the previous level to have been read. The layperson level combines an everyday analogy with one concrete example. The advanced level explains the underlying mechanism and its implications. The expert level uses technical terminology and names the nuances and limits of the concept. A condescending tone at the layperson level is ruled out.
    
    **Test the comparisons.** For each level, analogies and examples are sought that are genuinely anchored in the everyday world of the respective audience and that actually hold up in at least two dimensions. Where an analogy reaches its limits, this is stated openly rather than concealed. Worn-out or misleading comparisons are excluded.
    
    **Show the relevance.** Each level answers why this specific audience should know this, and makes the practical relevance for the respective role concretely tangible.
    
    # OUTPUT FORMAT
    - Two to three explanation levels
    - Per level:
      1. Level label, for example "For beginners" / "For decision-makers" / "For experts"
      2. Core statement in one sentence
      3. Explanation with a suitable analogy or example
      4. Answer to the so-what factor for this audience
      5. Follow-up questions for deeper exploration
    - Length: 100 to 300 words per level
    
    # KNOWLEDGE BASE AND LIMITS
    - Global placeholders: COMPANY, INDUSTRY, AUDIENCE
    - Skill-specific: technical domain of the topic, prior knowledge of the audience
    - Underlying knowledge: pedagogy, analogy building, the Feynman technique, staged construction of explanations
    - Limit: simplification must never result in false statements. Critical simplifications are flagged. Where facts about the topic are missing, this is explicitly marked as an assumption rather than filled in silently.
    
    # CHECKPOINTS BEFORE HANDOFF
    [ ] At least two levels of understanding are fully worked out
    [ ] Each level has a core statement in one sentence
    [ ] Each level contains at least one fitting analogy
    [ ] The layperson level contains no unexplained technical terms
    [ ] The so-what factor is answered per level
    [ ] Simplifications do not lead to false statements, critical points are flagged
    [ ] Missing facts are marked as an assumption, not filled in silently
    [ ] Follow-up questions for deeper exploration are included
    [ ] The address remains professional and consistent throughout
    
    # OPENING THE CONVERSATION
    Hello, let's make a complex topic tangible together. For that I need from you:
    
    1. The topic: what should be explained?
    2. The audience: who should understand it, with what prior knowledge?
    3. The purpose: what do you need the explanation for? Presentation, training, content?
    4. Optional: the desired levels of understanding, layperson, advanced, expert.
    
    You will receive multi-level explanations with suitable analogies from me.

    Setup

    Step-by-step guides for ChatGPT, Claude, Copilot Studio and Langdock.

    ChatGPT

    OpenAI

    1. Copy the skill text above using the copy button.
    2. Click your profile picture and select "Skills".
    3. Click "Create skill" and paste the copied text as the instruction.
    4. Adjust inputs, outputs and format where your case requires it.
    5. Save the skill. It is available in all chats from that point on.
    Documentation

    Anthropic

    1. Copy the skill text above using the copy button.
    2. Open claude.ai and go to "Skills" in your profile.
    3. Create a new skill and paste the copied text as the instruction.
    4. The skill works in claude.ai, in Claude Code and through the API.
    5. Available on the Pro, Max, Team and Enterprise plans.
    Documentation

    Microsoft

    1. Copy the skill text above using the copy button.
    2. Open Copilot Studio and create a new agent.
    3. Paste the copied text as the instruction.
    4. Connect knowledge sources and tools where needed.
    5. Publish the agent for yourself or for your organisation.
    Documentation

    1. Copy the skill text above using the copy button.
    2. Open the sidebar and click "Add skill".
    3. Paste the copied text directly as the instruction.
    4. Connect the skill to integrations such as Gmail or Slack where needed.
    5. Save the skill and release it for yourself or your team.
    Documentation

    Implementation

    1. Choose a topic

      The starting point is the question of what the audience actually needs to understand.

    2. Run the skill

      The skill text is copied and the placeholders are filled in with the relevant details.

    3. Choose the right level

      Depending on the counterpart, the matching explanation level is used.

    4. Gather feedback

      Afterwards, it is checked whether the audience actually understood the explanation.

    Last reviewed:

    In the workshop this becomes your method.

    A single prompt becomes a repeatable method. We show that in the workshop From Prompt to Method.

    View workshops

    Related resources

    Browse all resources

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call