Individual judgment helps you interpret a situation. Systems thinking helps you examine the conditions that produced it. Bringing them together means checking both your explanation and the environment in which people act: information flows, incentives, dependencies, decision rights, and feedback.
A manager may correctly sense that a delivery plan is fragile while misunderstanding the cause. A team may identify the cause accurately while lacking the authority to change it. Better decisions require attention to both questions: What am I seeing? and What is shaping what happens?
This guide connects two projects by Denys Kostin. Intuition Management explores perception, intuition, and individual judgment. Paradigm Red explores organizational systems and System Shaping. Use the routes below to move from a personal assessment to a shared, testable explanation and a practical response.
Two questions for the same decision
What supports my judgment?
Start with the observation, your interpretation, and the uncertainty between them. “The supplier missed two integration tests” is an observation. “The supplier cannot deliver” is an interpretation that needs further checking. Ask which evidence would distinguish that explanation from alternatives.
Intuition can suggest what deserves attention. It does not establish that a conclusion is correct. The guide to expert judgment explains how to examine relevant experience, evidence, assumptions, and uncertainty before using an assessment.
What conditions shape the outcome?
Then examine how the work is organized. Does the reporting process conceal unfinished integration work? Are teams rewarded for starting tasks rather than completing usable outcomes? Who can resolve a shared dependency? A personal judgment can be mistaken; an organizational arrangement can also make accurate information hard to obtain or act on.
Start with systems thinking to examine relationships and recurring patterns. Where those patterns call for changes to feedback, incentives, or decision rights, the System Shaping framework provides a broader organizational perspective.
Where should you start?
These are prompts for choosing your next investigation, not a diagnostic test. Several conditions can be present at once.
| What you notice | What to investigate | Start here |
|---|---|---|
| You mainly notice evidence supporting your first impression. | How you search for and evaluate competing evidence. | Confirmation bias |
| Specialists hold different parts of the explanation. | How observations retain their context as people compare them. | Organizational sensemaking |
| People privately disagree but publicly endorse the plan. | Whether discussion protects independent assessments and dissent. | Groupthink in the workplace |
| After an outcome, everyone remembers having expected it. | Whether the original evidence and expectations were recorded. | Decision journal |
Example: a green dashboard and a worried specialist
This is a fictional delivery scenario. A programme dashboard reports that most tasks are complete. An experienced specialist says the release still feels unsafe. The sponsor sees caution; the specialist sees a familiar warning pattern.
Check the judgment. Ask the specialist to identify the observations behind the concern. Two critical interfaces have not been tested together. A comparable release failed at that boundary. The comparison is a reason to investigate, but it does not prove that this release will fail. Another possibility is that the current interfaces differ enough to make the comparison misleading.
Check the system. The team discovers that the dashboard counts completed component tasks without showing whether the components work together. Responsibility for integration is split between teams, and neither team can reserve the shared test environment. Those are conditions that require coordination and an explicit decision.
Choose a response. Name an integration owner, reserve the test environment, and make release approval depend on the relevant test evidence. Record the outstanding uncertainty and what result would change the decision. This is more useful than either dismissing the concern or treating the specialist’s confidence as sufficient proof.
Review what happened. If the test exposes a fault, examine whether the original reasoning was sound and whether the new coordination worked. If it does not, update the assessment. Either result can teach the team something; neither alone proves that every earlier judgment was good or bad.
A practical decision review
Use these questions with one real decision. The sequence is an editorial practice aid, not a validated assessment or a guarantee of a better outcome.
- Describe the signal. What did someone observe, when, and in what context? Separate that from the explanation attached to it.
- Test the interpretation. What else could explain the observation? What evidence would make you revise your view?
- Map the conditions. Which handoffs, incentives, delays, information gaps, or decision rights might be shaping the pattern?
- Compare independent views. Ask relevant people for their assessments before a senior person frames the answer. Preserve disagreement that could affect the decision.
- Choose a bounded action. Specify what will change, who owns it, and what evidence you need before making a larger commitment.
- Close the review. Record expectations and a review date. Check both the quality of the original reasoning and the effects of the action.
For a decision that has not yet been made, premortem analysis offers a structured way to examine plausible failure scenarios. Keep those scenarios separate from established facts and follow up on the assumptions that matter.
Choose a reading path
If you are starting with a personal judgment
Read systems thinking and intuition in management for the connection between personal interpretation and organizational context. Then use the expert judgment and confirmation bias guides above to make the assessment explicit and testable.
If you are starting with a team decision
Read the collective mind to explore how people connect knowledge and attention. Continue with organizational sensemaking when the difficulty is combining fragmented observations, or groupthink when agreement is suppressing inquiry.
If you need to change recurring conditions
Move to System Shaping when the same problem returns across decisions or teams. Use a decision journal alongside that work so changes in organizational conditions do not erase the record of what people originally expected.
Common questions
Are intuition and systems thinking the same?
No. Intuition can be a rapid impression or recognition. Systems thinking examines relationships and patterns across a situation. You can use an intuitive concern to begin a systems inquiry, while continuing to test the concern against evidence.
Does systems thinking make intuition accurate?
Not automatically. A systems explanation can also be incomplete or wrong. Make the proposed relationships explicit, look for contrary evidence, and review what actually happens. A persuasive diagram or a strong feeling is not enough on its own.
Should I work on my judgment or the organization?
Choose the smallest useful investigation within your authority. Clarify an uncertain assessment when the evidence is unclear. Address coordination or decision rights when people already understand a problem but cannot act on it. Often both need attention.
How are the two sites connected?
Both are projects by Denys Kostin. Intuition Management focuses on how people perceive and judge; Paradigm Red focuses on how organizational conditions shape action and change. This page provides a route between those perspectives without treating them as interchangeable.
Start with one decision: write down the observation, test your interpretation, and identify one organizational condition worth examining.