Decision Making Under Pressure logo

Decision Making Under Pressure

Community
fatihguner
decision-making-under-pressure

Provides practical habits for making better decisions faster -- reframing problems before solving them, knowing when to stop deliberating, balancing intuition with analysis, resisting 'just this once' compromises, and breaking overthinking cycles. Use when facing a high-stakes choice with incomplete data, sensing that deliberation has become procrastination, noticing a pattern of deferred decisions, needing to explain decision-making rationale to a team, or recognising that overthinking is degrading output quality.

Overview

Publisherfatihguner
Repositoryforeman
Skill namedecision-making-under-pressure
Stars
63
Forks
10
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by fatihguner on GitHub. Read the source before you install it.

Installation

Install the Decision Making Under Pressure AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/decision-making-under-pressure
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/fatihguner/foreman.git /tmp/foreman
mkdir -p .claude/skills
cp -r /tmp/foreman/plugins/foreman/skills/decision-making-under-pressure .claude/skills/decision-making-under-pressure
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Decision Making Under Pressure in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Decision Making Under Pressure on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Decision Making Under Pressure is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

Decision-Making Under Pressure

TIMER. Every undecided decision carries a holding cost -- and most leaders dramatically underestimate it. Projects stall waiting for approval. Teams hedge because direction is unclear. Competitors move while deliberation continues. The holding cost is invisible because it appears on no balance sheet, but it compounds daily: in lost momentum, in eroded team confidence, in the narrowing of options that occurs while a leader searches for certainty that will never arrive. Clayton Christensen observed that the most dangerous phrase in a leader's vocabulary is "just this once" -- a phrase that makes ethical and strategic erosion feel costless. Thomas Davenport's research suggests that the question is rarely whether a leader has enough information to decide, but whether they have the courage to decide with the information they have.

The cognitive science of decision-making -- Kahneman's System 1 and System 2, the taxonomy of biases -- is covered elsewhere in this system. What follows is the applied practice: the daily habits that separate leaders who decide well under pressure from those who decide late, or not at all.


The Framework

Practical decision-making under pressure operates through six habits. They are not sequential; they are concurrent disciplines that reinforce each other over time.

Habit 1: Frame Before You Solve

Julia Binder and Michael Watkins's research reveals a consistent failure pattern: leaders and teams devote too little effort to examining and defining problems before attempting to solve them. Jumping to solutions feels productive. It rarely is. Problem-framing is the practice of viewing a situation through multiple lenses -- adjusting angle, aperture, and focus -- before committing to a solution path.

Three reframing techniques for daily use:

  • Stakeholder reframe. How does this problem look from the customer's perspective? The investor's? The newest employee's? Each perspective reveals constraints and opportunities invisible from the leader's vantage point.
  • Temporal reframe. What does this problem look like in six months? In three years? Decisions that feel urgent today often look different when projected forward. Equally, decisions that feel deferrable today may become irreversible if delayed.
  • Scale reframe. If this problem were ten times larger, how would you approach it? If it were trivial, would you still be deliberating? Scale shifts expose whether the decision difficulty is inherent to the problem or manufactured by the decision-maker's anxiety.

Peter Drucker's observation applies: the leader who takes pride in solving problems quickly may be solving the wrong problems. The leader who reframes first solves fewer problems -- but the right ones.

Habit 2: Apply the Importance-Frequency Matrix

Thomas Davenport's framework for deciding when to stop deliberating uses two variables:

Low ImportanceHigh Importance
High FrequencyCreate a rule or system; invest once, then automateDevelop a robust process; the recurrence justifies the effort
Low FrequencyDecide immediately; the cost of deliberation exceeds the value of optimisationGather perspectives, then decide within a defined time boundary

Most leaders over-deliberate low-importance decisions and under-invest in systems for high-frequency ones. The diagnostic question: "If I spent thirty more minutes on this decision, would the outcome materially improve?" If the answer is no, decide now.

Habit 3: Balance Gut and Data

Jennifer Jordan, Michael Wade, and Elizabeth Teracino's research identifies the intuition-analysis tension as one of seven tensions every leader must navigate. Overvaluing intuition produces decisions based on outdated heuristics and unexamined biases. Overvaluing data produces analysis paralysis and the illusion that sufficient information will eliminate uncertainty.

The practical balance:

  • Use intuition for: pattern recognition in familiar domains, rapid triage of low-stakes decisions, identifying which data to seek.
  • Use analysis for: high-stakes decisions where biases are likely operating, situations outside your domain expertise, decisions that will be difficult to reverse.
  • Use both for: any decision where your gut says one thing and the data says another. The disagreement itself is the most valuable signal -- it means either your experience is detecting something the data misses, or your biases are overriding evidence. Determining which requires deliberate examination, not default to either mode.

Habit 4: Widen Perspective Deliberately

Helen Lee Bouygues's research on critical thinking identifies three practices that guard against poor decisions:

  1. Question assumptions. Especially when stakes are high. "Why is this the best way forward?" and "What does the evidence actually say about our market expectations?" force the reasoning process to surface premises that may be unexamined.
  2. Verify logical coherence. Are the conclusions supported by the data, or are they supported by the narrative someone has constructed around the data? These are different things.
  3. Seek perspectives outside your circle. The inner circle shares your assumptions. Perspectives from different departments, different experience levels, and different professional backgrounds reveal blind spots that homogeneous consultation cannot.

Sabina Nawaz's six gut-check questions provide a structured version of this practice for new ideas: What stands out? What's missing? What would critics say? What would failure look like? What would customer-facing employees say? What shortcomings would please competitors?

Habit 5: Resist "Just This Once"

Christensen's observation deserves its own habit because the mechanism is subtle and the consequences are severe. The marginal cost of doing something wrong "just this once" always appears low. The full cost -- which includes the precedent set, the standard lowered, the integrity compromised -- is invisible at the moment of decision. Leaders who maintain their principles 100% of the time find it structurally easier than those who maintain them 98% of the time, because the 2% creates a negotiation with themselves that the 100% does not.

The practical application is precommitment: know where your lines are before you face pressure to cross them. Ethical boundaries decided in advance require no deliberation under pressure. Ethical boundaries decided in the moment are subject to every cognitive bias and rationalisation the human mind can produce.

Habit 6: Break Overthinking Cycles

Alice Boyes's research identifies a pattern: intelligent leaders are particularly prone to overthinking because their cognitive capacity allows them to generate more scenarios, more objections, and more complications than the problem warrants. The signals of overthinking: obsessing over the same options, generating diminishing returns on additional analysis, inability to commit despite adequate information.

Three circuit-breakers:

  • Notice the loop. The first step is recognising that you are cycling through the same arguments. Label it: "I am overthinking this."
  • Change cognitive mode. Engage in an absorbing, unrelated activity -- a puzzle, a walk, a conversation about something else entirely. This is not procrastination; it is allowing the subconscious processing that focused analysis suppresses.
  • Set a decision deadline. "I will decide by Thursday at noon" creates a forcing function. Share the deadline with someone else to make it binding. Open-ended deliberation is a failure mode, not a virtue.

Prompts

Prompt 1 -- Problem Reframing:

I am facing this decision: [describe the decision and context]. Before I solve it, help me reframe it. Apply three lenses: stakeholder reframe (how does this look from the perspectives of [list 3 stakeholders]), temporal reframe (what does this look like in 6 months vs. 3 years), and scale reframe (if this were 10x larger or trivially small). Then tell me: am I solving the right problem?

Prompt 2 -- Decision Speed Diagnostic:

Here are five decisions currently pending on my desk: [list each with a brief description]. For each, assess importance (high/low) and frequency (high/low) using the Davenport matrix. Then recommend: which should I decide immediately, which need a system, which deserve more deliberation, and which am I over-deliberating?

Prompt 3 -- Intuition vs. Analysis Arbitration:

My gut tells me [describe intuitive conclusion] about [decision]. The data suggests [describe analytical conclusion]. Help me determine whether my intuition is detecting a pattern the data misses or whether my biases are overriding evidence. Ask me the questions that would distinguish between these two explanations.

Prompt 4 -- Ethical Line Precommitment:

I am entering a high-pressure period: [describe context -- fundraising, acquisition, restructuring]. Before the pressure arrives, help me define my ethical precommitments. What are the "just this once" temptations most common in this type of situation? For each, help me articulate the line I will not cross and the reasoning behind it, so I don't have to reason under pressure.


Use Cases

Early-Traction Startup: Founder Paralysed by Pricing Decision A founder has spent three weeks analysing pricing models for a product launch. Every model has trade-offs. No model is clearly superior. The importance-frequency diagnostic reveals this is a high-importance but low-frequency decision -- it deserves deliberation but within a bounded timeframe. The temporal reframe reveals that the pricing decision is reversible within 90 days. The founder sets a 48-hour decision deadline, shares it with their co-founder for accountability, and selects the model that best aligns with their positioning thesis. Three months later, they adjust pricing based on real customer data -- data they would not have if they had spent another three weeks deliberating.

Growth-Stage Company: VP Avoiding a Restructuring Decision A VP knows that one of three engineering teams needs to be reorganised. The decision will disappoint people, so the VP gathers "just a little more data" -- for the fourth consecutive month. The holding cost diagnostic reveals: two projects are stalled because team boundaries are unclear, three engineers have started interviewing at other companies due to uncertainty, and cross-team collaboration has degraded. The VP applies the six gut-check questions to each restructuring option, sets a one-week decision deadline, and communicates the decision with transparent reasoning. Morale dips briefly; the stalled projects resume within two weeks.

Scale-Stage CEO: Resisting "Just This Once" in a Partnership Deal A CEO is negotiating a distribution partnership with a larger company. The partner's legal team inserts a clause that requires sharing customer data in ways that conflict with the company's privacy commitments. The partner's head of BD says, "We can work around this informally -- just sign the contract as-is and we'll handle the data question later." The CEO, having precommitted to data privacy as a non-negotiable line, declines without deliberation. The partner respects the boundary and revises the clause. Had the CEO not precommitted, the "just this once" logic -- "it's our biggest deal, we'll fix it later" -- would have been persuasive in the moment.


Anti-Patterns

  1. Decisiveness Theatre. Making rapid decisions ostentatiously to signal leadership confidence, without reframing or perspective-gathering. Speed without discernment is recklessness branded as decisiveness.

  2. Data as Procrastination. Requesting additional analysis not because it would change the decision but because it defers the discomfort of committing. The tell: the decision-maker cannot articulate what specific data point would change their mind. If no data point would change the outcome, the decision is ready to be made.

  3. Consensus as Decision-Making. Treating universal agreement as a prerequisite for action. Consensus-seeking is a legitimate collaboration tool. Consensus-requiring is a mechanism for distributing blame and avoiding accountability. Clarify before any meeting whether the process is consultative (I will hear all views and then decide) or democratic (the group will vote).

  4. Post-Hoc Rationalisation Disguised as Intuition. "My gut told me" is sometimes a legitimate report of pattern recognition and sometimes a retroactive justification for a decision made on emotion. The difference: genuine intuition can be examined and its reasoning reconstructed; post-hoc rationalisation collapses under questioning.

  5. The Reversibility Blind Spot. Treating all decisions as equally permanent. Many business decisions are highly reversible -- pricing, feature prioritisation, team assignments -- and deserve fast, low-deliberation treatment. Irreversible decisions -- equity grants, market exits, key hires -- deserve the full reframing and perspective-gathering protocol. Applying the irreversible protocol to reversible decisions is a common source of organisational paralysis.


By Stage

StageFocusKey Difference
Early TractionSpeed over precisionNearly every decision is reversible because the company is small and fast-moving. The primary risk is not making a wrong decision but making no decision. The importance-frequency matrix should bias toward "decide immediately" for most choices.
GrowthProcess installationDecision volume exceeds one person's capacity. The leader's task shifts from making every decision to building decision-making systems (for high-frequency issues) and teaching the reframing and deliberation habits to the leadership team.
ScaleDecision delegation and ethicsAt scale, the leader makes fewer decisions directly and more decisions about how decisions should be made. Ethical precommitment becomes organisational, not personal -- codified in policies, not just personal convictions. The "just this once" risk multiplies as more people face pressure to cut corners.

Output Template

markdown
# Decision Analysis: [Decision Description]

## Problem Frame
- Initial framing: [how the problem was first presented]
- Stakeholder reframe: [alternative perspective]
- Temporal reframe: [how it looks at different time horizons]
- Scale reframe: [what changes at different magnitudes]
- Revised framing: [the problem as it should actually be solved]

## Davenport Classification
- Importance: [High/Low]
- Frequency: [High/Low]
- Recommended approach: [Decide now / Build system / Bounded deliberation / Seek perspectives]

## Intuition-Analysis Check
- Gut says: [intuitive conclusion]
- Data says: [analytical conclusion]
- Reconciliation: [which to trust and why]

## Decision
- Choice: [what was decided]
- Reasoning: [transparent logic]
- Reversibility: [how and when this can be revisited]
- Ethical check: [any "just this once" pressures resisted]

## Communication Plan
- Who needs to know: [stakeholders]
- What they need to understand: [the reasoning, not just the outcome]
- When: [timing]

Related Skills

  • Thinking, Fast and Slow -- Kahneman's dual-process theory provides the cognitive science behind why intuition and analysis sometimes conflict; this skill provides the daily practices for managing that conflict.
  • VUCA Framework -- Classifies the type of uncertainty in which pressured decisions occur, which informs which decision habit to prioritise.
  • Eisenhower Matrix -- The urgent-versus-important distinction complements the importance-frequency matrix for triaging which decisions demand immediate attention versus scheduled deliberation.
  • Evaluating and Deciding -- Provides the structured criteria-weighting and margin-of-safety methods that complement the reframing and speed habits described here.
  • Stoic Emotional Mastery -- The Stoic practice of pausing before assenting to impressions provides the philosophical foundation for Habit 6's overthinking circuit-breakers.
  • Psychological Safety -- Teams that lack psychological safety suppress dissenting perspectives, directly degrading the leader's ability to gather the diverse input good decisions require.

Frequently asked questions

What does the Decision Making Under Pressure AI skill do?

Provides practical habits for making better decisions faster -- reframing problems before solving them, knowing when to stop deliberating, balancing intuition with analysis, resisting 'just this once' compromises, and breaking overthinking cycles. Use when facing a high-stakes choice with incomplete data, sensing that deliberation has become procrastination, noticing a pattern of deferred decisions, needing to explain decision-making rationale to a team, or recognising that overthinking is degrading output quality.

Why use Decision Making Under Pressure on TypingMind?

Because you install it once and use it with any model. Decision Making Under Pressure is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Decision Making Under Pressure in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/decision-making-under-pressure. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Decision Making Under Pressure?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Decision Making Under Pressure?

As many as you like. As long as a model supports skills, you can use Decision Making Under Pressure with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Decision Making Under Pressure AI skill free?

Yes. It is published on GitHub by fatihguner under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇