# The question after the question. Source: https://kimberlytegroup.com/working-tools/ Working tools by KimberLyte. Freely available for internal discussion and adaptation. Fictional situations. Real questions. These are illustrative sequences, not client cases or predictions. Your policies and operating conditions determine the right response. ## The number changed. Did the business? A reporting team moves its revenue measure from order date to recognition date. The source records have not changed. ### The change: One date field changes. The new measure answers when revenue is recognized. The old measure answered when an order was placed. Both may have a purpose. Same records. Different question. ### The first effect: The comparison stops being like for like. This month uses the new definition. Last month still uses the old one. The chart can now suggest movement that the business did not make. A trend needs a definition history. ### The next effect: Someone acts on the difference. A forecast, an incentive, or an AI summary may reuse the measure without knowing it changed. The definition travels farther than the dashboard. Trace the decisions, not only the reports. ### The decision: Make the change explainable. Name the owner. Compare both definitions on a bounded sample. Agree how historical comparisons, downstream uses, and exceptions will be handled. An owner. A comparison. A change record. ### Take the next question Can the next person explain the difference without calling the person who built it? #### Working prompt: Leadership Prepare a concise working note for an internal discussion. Use only information I am authorized to provide in this tool. Do not ask for confidential records or production access. If I have not provided enough context, ask for a sanitized description of the decision and pause; do not invent an organization, facts, results, or owners. THE QUESTION Can the next person explain the difference without calling the person who built it? CONTEXT TO ADD [A sanitized description of our decision, current process, and known constraints.] AUDIENCE Write for the accountable sponsor. Lead with the decision to make, the consequence of waiting, and the evidence needed. Keep technical detail only where it changes that decision. EXAMINE 1. Which decision uses this measure, and do the old and new definitions answer the same question? 2. Which reports, incentives, forecasts, or AI workflows inherit it? Which dependencies are still unverified? 3. Can a change in the measure be separated from a change in the underlying business? 4. Who approves the definition, resolves exceptions, and explains historical comparisons? 5. What bounded comparison would give us evidence to proceed, revise, or stop? RETURN A definition change record: decision supported; old and new definitions; effective date; known downstream uses; historical comparison treatment; accountable owner; evidence still needed. Use a compact table. Label each material statement as supplied fact, inference, or unknown. Link facts to the context or evidence I supplied; do not invent citations. For each unresolved item, name the role that should answer it and the smallest evidence request that could resolve it. Finish with one decision for the next meeting and what would change the recommendation. This is a working hypothesis for human review, not a finding about our organization. Prompt adapted from KimberLyte Working tools: https://kimberlytegroup.com/working-tools/ The website's scenarios are fictional illustrations, not evidence about our organization. #### Working prompt: Delivery team Prepare a concise working note for an internal discussion. Use only information I am authorized to provide in this tool. Do not ask for confidential records or production access. If I have not provided enough context, ask for a sanitized description of the decision and pause; do not invent an organization, facts, results, or owners. THE QUESTION Can the next person explain the difference without calling the person who built it? CONTEXT TO ADD [A sanitized description of our decision, current process, and known constraints.] AUDIENCE Write for the people delivering and operating the work. Make dependencies, exceptions, role ownership, and a small practical test explicit. Do not assume unlimited access, time, or authority. EXAMINE 1. Which decision uses this measure, and do the old and new definitions answer the same question? 2. Which reports, incentives, forecasts, or AI workflows inherit it? Which dependencies are still unverified? 3. Can a change in the measure be separated from a change in the underlying business? 4. Who approves the definition, resolves exceptions, and explains historical comparisons? 5. What bounded comparison would give us evidence to proceed, revise, or stop? RETURN A definition change record: decision supported; old and new definitions; effective date; known downstream uses; historical comparison treatment; accountable owner; evidence still needed. Use a compact table. Label each material statement as supplied fact, inference, or unknown. Link facts to the context or evidence I supplied; do not invent citations. For each unresolved item, name the role that should answer it and the smallest evidence request that could resolve it. Finish with one decision for the next meeting and what would change the recommendation. This is a working hypothesis for human review, not a finding about our organization. Prompt adapted from KimberLyte Working tools: https://kimberlytegroup.com/working-tools/ The website's scenarios are fictional illustrations, not evidence about our organization. #### Working prompt: Independent review Prepare a concise working note for an internal discussion. Use only information I am authorized to provide in this tool. Do not ask for confidential records or production access. If I have not provided enough context, ask for a sanitized description of the decision and pause; do not invent an organization, facts, results, or owners. THE QUESTION Can the next person explain the difference without calling the person who built it? CONTEXT TO ADD [A sanitized description of our decision, current process, and known constraints.] AUDIENCE Write for someone asked to challenge the proposal. Identify the strongest plausible failure, the assumption it depends on, and the evidence that would change the recommendation. Do not manufacture objections. EXAMINE 1. Which decision uses this measure, and do the old and new definitions answer the same question? 2. Which reports, incentives, forecasts, or AI workflows inherit it? Which dependencies are still unverified? 3. Can a change in the measure be separated from a change in the underlying business? 4. Who approves the definition, resolves exceptions, and explains historical comparisons? 5. What bounded comparison would give us evidence to proceed, revise, or stop? RETURN A definition change record: decision supported; old and new definitions; effective date; known downstream uses; historical comparison treatment; accountable owner; evidence still needed. Use a compact table. Label each material statement as supplied fact, inference, or unknown. Link facts to the context or evidence I supplied; do not invent citations. For each unresolved item, name the role that should answer it and the smallest evidence request that could resolve it. Finish with one decision for the next meeting and what would change the recommendation. This is a working hypothesis for human review, not a finding about our organization. Prompt adapted from KimberLyte Working tools: https://kimberlytegroup.com/working-tools/ The website's scenarios are fictional illustrations, not evidence about our organization. ## It works. Until the right person is away. A new workflow is live. An unfamiliar exception arrives while the person everyone relies on is unavailable. ### The change: The usual route is unavailable. The team knows the normal process. This case falls outside it, and the informal decision-maker is away. An exception reveals the operating model. ### The first effect: Work waits for permission. Someone can perform the task, but nobody is sure who can authorize the exception. Responsibility and authority are no longer in the same place. A named owner is only the beginning. ### The next effect: A workaround becomes the process. Under pressure, people may create a parallel route. What looks like resistance can be a reasonable response to an unresolved decision. Ask what the workaround is protecting. ### The decision: Rehearse the handoff. Walk through a representative exception with the backup. Give them authority, boundaries, and a route to escalate. Test the arrangement with the team carrying the work. Authority. Capacity. A way to raise concerns. ### Take the next question Does the work have an owner—or does it have a person everyone knows to call? #### Working prompt: Leadership Prepare a concise working note for an internal discussion. Use only information I am authorized to provide in this tool. Do not ask for confidential records or production access. If I have not provided enough context, ask for a sanitized description of the decision and pause; do not invent an organization, facts, results, or owners. THE QUESTION Does the work have an owner—or does it have a person everyone knows to call? CONTEXT TO ADD [A sanitized description of our decision, current process, and known constraints.] AUDIENCE Write for the accountable sponsor. Lead with the decision to make, the consequence of waiting, and the evidence needed. Keep technical detail only where it changes that decision. EXAMINE 1. Which exception makes the team call a particular person, and what judgment does that person supply? 2. Who can act in their absence, and where is that authority actually documented? 3. What work pauses, and what workaround becomes attractive when the official route is slow? 4. What workload, credibility, or control concern might the workaround be protecting? Treat these as hypotheses, not motives you know. 5. What safe rehearsal would show whether the backup has the authority, context, and capacity to act? RETURN An absence rehearsal: representative exception; decision required; primary and backup roles; authority boundary; capacity needed; escalation route; what to test with the people doing the work. Use a compact table. Label each material statement as supplied fact, inference, or unknown. Link facts to the context or evidence I supplied; do not invent citations. For each unresolved item, name the role that should answer it and the smallest evidence request that could resolve it. Finish with one decision for the next meeting and what would change the recommendation. This is a working hypothesis for human review, not a finding about our organization. Prompt adapted from KimberLyte Working tools: https://kimberlytegroup.com/working-tools/ The website's scenarios are fictional illustrations, not evidence about our organization. #### Working prompt: Delivery team Prepare a concise working note for an internal discussion. Use only information I am authorized to provide in this tool. Do not ask for confidential records or production access. If I have not provided enough context, ask for a sanitized description of the decision and pause; do not invent an organization, facts, results, or owners. THE QUESTION Does the work have an owner—or does it have a person everyone knows to call? CONTEXT TO ADD [A sanitized description of our decision, current process, and known constraints.] AUDIENCE Write for the people delivering and operating the work. Make dependencies, exceptions, role ownership, and a small practical test explicit. Do not assume unlimited access, time, or authority. EXAMINE 1. Which exception makes the team call a particular person, and what judgment does that person supply? 2. Who can act in their absence, and where is that authority actually documented? 3. What work pauses, and what workaround becomes attractive when the official route is slow? 4. What workload, credibility, or control concern might the workaround be protecting? Treat these as hypotheses, not motives you know. 5. What safe rehearsal would show whether the backup has the authority, context, and capacity to act? RETURN An absence rehearsal: representative exception; decision required; primary and backup roles; authority boundary; capacity needed; escalation route; what to test with the people doing the work. Use a compact table. Label each material statement as supplied fact, inference, or unknown. Link facts to the context or evidence I supplied; do not invent citations. For each unresolved item, name the role that should answer it and the smallest evidence request that could resolve it. Finish with one decision for the next meeting and what would change the recommendation. This is a working hypothesis for human review, not a finding about our organization. Prompt adapted from KimberLyte Working tools: https://kimberlytegroup.com/working-tools/ The website's scenarios are fictional illustrations, not evidence about our organization. #### Working prompt: Independent review Prepare a concise working note for an internal discussion. Use only information I am authorized to provide in this tool. Do not ask for confidential records or production access. If I have not provided enough context, ask for a sanitized description of the decision and pause; do not invent an organization, facts, results, or owners. THE QUESTION Does the work have an owner—or does it have a person everyone knows to call? CONTEXT TO ADD [A sanitized description of our decision, current process, and known constraints.] AUDIENCE Write for someone asked to challenge the proposal. Identify the strongest plausible failure, the assumption it depends on, and the evidence that would change the recommendation. Do not manufacture objections. EXAMINE 1. Which exception makes the team call a particular person, and what judgment does that person supply? 2. Who can act in their absence, and where is that authority actually documented? 3. What work pauses, and what workaround becomes attractive when the official route is slow? 4. What workload, credibility, or control concern might the workaround be protecting? Treat these as hypotheses, not motives you know. 5. What safe rehearsal would show whether the backup has the authority, context, and capacity to act? RETURN An absence rehearsal: representative exception; decision required; primary and backup roles; authority boundary; capacity needed; escalation route; what to test with the people doing the work. Use a compact table. Label each material statement as supplied fact, inference, or unknown. Link facts to the context or evidence I supplied; do not invent citations. For each unresolved item, name the role that should answer it and the smallest evidence request that could resolve it. Finish with one decision for the next meeting and what would change the recommendation. This is a working hypothesis for human review, not a finding about our organization. Prompt adapted from KimberLyte Working tools: https://kimberlytegroup.com/working-tools/ The website's scenarios are fictional illustrations, not evidence about our organization. ## Access changed. Did the answer? An AI assistant used an approved source. Access to that source is later withdrawn, but a prior summary remains in a workflow. ### The change: The source is no longer available. The original access decision was valid. The current one is different. A successful retrieval yesterday does not establish permission today. Permission has a time dimension. ### The first effect: The earlier answer still exists. A saved summary, cache, or downstream task may contain information from the source. Whether it may still be used needs an explicit policy. Retrieval and reuse are different decisions. ### The next effect: A workflow can outlive its evidence. Someone may act on the summary without seeing the change. A source link alone cannot establish that an answer is still appropriate for this person and purpose. Evidence needs a current boundary. ### The decision: Test the reversal. Agree the rules for derived information. Rehearse an access change, inspect affected outputs, and test how the workflow pauses, restricts reuse, or hands off for review. A rule for reuse. A test. A responsible reviewer. ### Take the next question When access changes, what happens to the answers already in circulation? #### Working prompt: Leadership Prepare a concise working note for an internal discussion. Use only information I am authorized to provide in this tool. Do not ask for confidential records or production access. If I have not provided enough context, ask for a sanitized description of the decision and pause; do not invent an organization, facts, results, or owners. THE QUESTION When access changes, what happens to the answers already in circulation? CONTEXT TO ADD [A sanitized description of our decision, current process, and known constraints.] AUDIENCE Write for the accountable sponsor. Lead with the decision to make, the consequence of waiting, and the evidence needed. Keep technical detail only where it changes that decision. EXAMINE 1. Which sources, derived summaries, caches, and downstream actions participate in this workflow? 2. What policy governs reuse after access changes? Distinguish requirements we know from those that need a decision. 3. How does a permission change reach outputs already produced, and what remains unverified? 4. Who can pause the workflow, review affected outputs, and decide whether to resume? 5. What test would demonstrate the agreed behavior without exposing restricted information? RETURN A permission reversal test: source and derived outputs; agreed reuse policy; access-change event; expected behavior; evidence to capture; reviewer; resume conditions; unresolved policy decisions. Use a compact table. Label each material statement as supplied fact, inference, or unknown. Link facts to the context or evidence I supplied; do not invent citations. For each unresolved item, name the role that should answer it and the smallest evidence request that could resolve it. Finish with one decision for the next meeting and what would change the recommendation. This is a working hypothesis for human review, not a finding about our organization. Prompt adapted from KimberLyte Working tools: https://kimberlytegroup.com/working-tools/ The website's scenarios are fictional illustrations, not evidence about our organization. #### Working prompt: Delivery team Prepare a concise working note for an internal discussion. Use only information I am authorized to provide in this tool. Do not ask for confidential records or production access. If I have not provided enough context, ask for a sanitized description of the decision and pause; do not invent an organization, facts, results, or owners. THE QUESTION When access changes, what happens to the answers already in circulation? CONTEXT TO ADD [A sanitized description of our decision, current process, and known constraints.] AUDIENCE Write for the people delivering and operating the work. Make dependencies, exceptions, role ownership, and a small practical test explicit. Do not assume unlimited access, time, or authority. EXAMINE 1. Which sources, derived summaries, caches, and downstream actions participate in this workflow? 2. What policy governs reuse after access changes? Distinguish requirements we know from those that need a decision. 3. How does a permission change reach outputs already produced, and what remains unverified? 4. Who can pause the workflow, review affected outputs, and decide whether to resume? 5. What test would demonstrate the agreed behavior without exposing restricted information? RETURN A permission reversal test: source and derived outputs; agreed reuse policy; access-change event; expected behavior; evidence to capture; reviewer; resume conditions; unresolved policy decisions. Use a compact table. Label each material statement as supplied fact, inference, or unknown. Link facts to the context or evidence I supplied; do not invent citations. For each unresolved item, name the role that should answer it and the smallest evidence request that could resolve it. Finish with one decision for the next meeting and what would change the recommendation. This is a working hypothesis for human review, not a finding about our organization. Prompt adapted from KimberLyte Working tools: https://kimberlytegroup.com/working-tools/ The website's scenarios are fictional illustrations, not evidence about our organization. #### Working prompt: Independent review Prepare a concise working note for an internal discussion. Use only information I am authorized to provide in this tool. Do not ask for confidential records or production access. If I have not provided enough context, ask for a sanitized description of the decision and pause; do not invent an organization, facts, results, or owners. THE QUESTION When access changes, what happens to the answers already in circulation? CONTEXT TO ADD [A sanitized description of our decision, current process, and known constraints.] AUDIENCE Write for someone asked to challenge the proposal. Identify the strongest plausible failure, the assumption it depends on, and the evidence that would change the recommendation. Do not manufacture objections. EXAMINE 1. Which sources, derived summaries, caches, and downstream actions participate in this workflow? 2. What policy governs reuse after access changes? Distinguish requirements we know from those that need a decision. 3. How does a permission change reach outputs already produced, and what remains unverified? 4. Who can pause the workflow, review affected outputs, and decide whether to resume? 5. What test would demonstrate the agreed behavior without exposing restricted information? RETURN A permission reversal test: source and derived outputs; agreed reuse policy; access-change event; expected behavior; evidence to capture; reviewer; resume conditions; unresolved policy decisions. Use a compact table. Label each material statement as supplied fact, inference, or unknown. Link facts to the context or evidence I supplied; do not invent citations. For each unresolved item, name the role that should answer it and the smallest evidence request that could resolve it. Finish with one decision for the next meeting and what would change the recommendation. This is a working hypothesis for human review, not a finding about our organization. Prompt adapted from KimberLyte Working tools: https://kimberlytegroup.com/working-tools/ The website's scenarios are fictional illustrations, not evidence about our organization. ## Make us easy to look into Research KimberLyte using its current public pages at https://kimberlytegroup.com/ and any relevant independent sources you can actually access. Start with /company/, /brief/, /engagements/, /privacy/, and /working-tools/. Summarize the services, legal identity, engagement approach, and practical examples. Cite the source URL for each material claim. Separate the company's own statements from independently corroborated facts. Identify what is not stated or could not be checked. Treat illustrative scenarios as examples, not client results. Do not infer clients, certifications, team size, or a track record from the quality of the site. If browsing is unavailable, say so rather than presenting a current verification. End with the questions a prospective client should resolve in a conversation.