01
Pattern match
The question’s structure is compared with the 60-category question-style bank.
EXAMPLE CASE STUDY
OrganisationFinding the blind spot inside apparent team agreement
See how Pygar turns apparent agreement and stalled action into a precise examination of dissent, ownership, feasibility and psychological safety.
01 · ASK
The question as the user posed it
Pygar begins by preserving the user’s wording. Before any answer is formed, the engine separates the stated decision from its assumptions, constraints and missing evidence.
USER INPUT
Why do our leadership decisions repeatedly stall after the meeting even when everyone appears to agree?
WHAT THE OPENING FRAME HIDES
Visible agreement can conceal different interpretations of the decision, untested feasibility, unclear ownership or a meeting norm that makes dissent costly. Lack of follow-through is the symptom, not yet the cause.
HOW PYGAR DETERMINED THIS
The engine looks for compound choices, hidden thresholds, assumed causes and missing decision criteria. These signals reveal where the opening wording may be narrowing the available reasoning.
02 · CLASSIFY
How Pygar chose the reasoning route
The classifier does not decide what the user should do. It identifies the structure of the question and selects the reasoning family, depth mode and prompt set most suited to examining it.
ROUTE SELECTED FROM THE 60-CATEGORY BANK
Matched within Pygar’s 60-category question-style bank as Collective decision pattern. Family: Human and Relational Insight. Mode: Standard. The route examines decision design, execution conditions and human dynamics without assigning motives or ranking individuals.
02
Family route
The dominant reasoning demand selects a cognitive family and operating mode.
03
Prompt assembly
The route builds five independent briefs without determining the answer.
03 · DELIBERATE
Five independent perspectives
Every panel role receives the same classified question with a distinct reasoning brief. The roles work independently, so one convincing argument cannot silently shape the others.
5
isolated reads, each optimized for a different failure mode in human judgement.
Lead
Clarify the missionLocate the exact point where the decision stops moving: commitment, ownership, resourcing, dependency approval or the first handover. Define the observable action that would distinguish a completed decision from a shared intention.
Depth
Judge the contextThe recurring pattern may reflect a preference for strategic alignment over operational specification. Compare meetings that moved to action with those that stalled, looking at dissent, decision rights, dependencies, capacity and the precision of the first milestone.
Test
Stress-test the frameChallenge apparent consensus. If disagreement is delayed until implementation, the meeting may reward alignment language while material reservations remain unexamined. Ask what evidence would disconfirm the belief that everyone agreed.
Ground
Apply real constraintsInspect the decision record, named owner, committed capacity, dependency owners and first dated milestone. A choice without those elements may be directionally accepted but not executable.
Human
Check people and impactPeople may withhold challenge when status, safety or role ambiguity makes dissent costly. Improve the meeting system so that reservations can be raised without labelling individuals as resistant or inferring private motives.
04 · SYNTHESIZE
Where the panel converged and what remained unresolved
The synthesizer compares the five reads for agreement, contradiction, shared assumptions and missing evidence. A separate verification pass then checks whether the combined answer is clear, bounded and honest about uncertainty.
PANEL SYNTHESIS
What the five reads establish together
Treat the repeated stall as a decision-design problem before treating it as an accountability failure. Add a structured dissent round, confirm ownership and capacity, surface dependencies and record one observable first step before agreement is closed.
VERIFICATION PASS
What the answer must not conceal
The organisation still needs to identify where stalls concentrate and whether the same conditions appear across decision types. Any use of organisational patterns must remain cohort-safe and separate from private questions or individual records.
HOW PYGAR PRODUCED THIS
The engine preserves useful disagreement, prioritises findings supported across more than one read and keeps unsupported certainty visible. Verification can trigger a bounded second synthesis when the result is unclear or incomplete.
05 · REFRAME
Turn the findings into better questions
Pygar does not merely replace the user’s question. It shows how the frame changed, then offers three deliberate operations that can expose sharper evidence and unexplored lines of consideration.
WHAT CHANGED IN THE FRAME
The question moves from Why do people fail to follow through? to Which meeting and decision conditions produce apparent agreement without executable commitment?
CLARIFY
Make the decision and evidence threshold more precise.At which precise handoff do agreed decisions stop moving, and what owner, capacity or dependency was missing at that point?
WIDEN
Introduce a credible alternative or overlooked stakeholder.How do decisions that reach implementation differ from stalled decisions in the quality of dissent, ownership, resourcing and first-step definition?
DEEPEN
Probe the assumption most likely to change the decision.Whose risk or workload increases when a decision proceeds, and where in the meeting can that concern be raised without social or status cost?
REFINED QUESTION READY TO ASK
Which decision-design conditions cause leadership agreements to stall after the meeting, and how can we test whether structured dissent, explicit ownership, committed capacity, surfaced dependencies and a dated first milestone improve follow-through?
06 · DECIDE
Convert insight into accountable human action
Pygar finishes by making the next evidence-producing action explicit while protecting the human decision boundary. The engine expands judgement; it does not replace authority, context or responsibility.
WHAT THE USER CAN DO NEXT
A bounded action that produces evidence
Clarify the disputed behaviours and terms, collect dissent safely, then run a facilitated reset with named commitments, observable behaviours and a review date that tests whether the agreement is actually working.
HUMAN DECISION BOUNDARY
Where Pygar stops
Pygar can help the group ask a better shared question. Managers cannot use the result to open private questions, responses, Mirror records or Meta-Brain history, or to infer individual intent.
1
structured recommendation, tested against five perspectives and returned to the person or team accountable for the choice.
Continue with another case study
