Catalog
concept#Governance#Product#Architecture

Bounded Rationality

Concept describing cognitive and informational limits in decision processes.

Bounded rationality describes cognitive and informational limits on human decision-making that prevent optimal choices.
Established
Medium

Classification

  • Medium
  • Organizational
  • Organizational
  • Intermediate

Technical context

Product management tools (e.g. roadmap boards)Governance and decision documentation systemsAnalytics and experimentation platforms

Principles & goals

Accept cognitive and informational limits as a design premise.Prefer simple, robust rules over complex optimization.Favor iterative validation over long-lived assumptions.
Discovery
Enterprise, Domain, Team

Use cases & scenarios

Compromises

  • Overreliance on simplified rules can amplify bias.
  • Unclear satisficing criteria cause arbitrary prioritization.
  • Lack of validation can cement wrong decisions long-term.
  • Document explicit assumptions and validate by priority.
  • Use clear satisficing thresholds instead of hidden heuristics.
  • Use iterative experiments to quickly reduce uncertainties.

I/O & resources

  • Available data and assumptions
  • Stakeholder goals and constraints
  • Time and resource constraints
  • Documented decision rules and priorities
  • List of validating experiments or measures
  • Traceable rationales for trade-offs

Description

Bounded rationality describes cognitive and informational limits on human decision-making that prevent optimal choices. It explains how satisficing, heuristics, and simplified models shape decisions in organizations and product design. The concept helps to create realistic decision frameworks and practical prioritization rules.

✔

  • Enables faster, practically deployable decisions.
  • Reduces analysis paralysis via clear satisficing criteria.
  • Improves governance through realistic decision frameworks.

✖

  • Does not yield optimal solutions, only acceptable compromises.
  • Requires good heuristics; poor heuristics create systematic errors.
  • May lead to inconsistent decisions if not documented.

  • Decision lead time

    Time from problem identification to final decision.

  • Number of iterations to validation

    How many iteration cycles were required to validate assumptions.

  • Conformity to satisficing criteria

    Share of decisions meeting defined satisficing thresholds.

Product prioritization in a SaaS startup

Team uses satisficing rules to decide with limited user data.

Governance design in a public agency

Formal decision paths simplified to reduce cognitive overload.

Architecture decision in a microservices project

Simplified assumptions enabled iterative decisions instead of perfect planning.

1

Raise awareness of cognitive limits in the team.

2

Define satisficing criteria and simple heuristics.

3

Design decision processes to allow short validation loops.

4

Document outcomes and institutionalize learning loops.

⚠️ Technical debt & bottlenecks

  • Undocumented decision heuristics in code and processes.
  • Outdated assumptions not revalidated.
  • Missing instrumentation to measure decision quality.
information-accessdecision-authoritydocumentation
  • Using simplified rules as a permanent excuse for missing data.
  • Adopting poor heuristics without monitoring.
  • No validation: assumptions are never tested.
  • Belief that simple rules are always safer.
  • Underestimating systematic biases.
  • Lack of traceability in delegated decisions.
Basics of decision analysis and heuristicsStakeholder facilitation and communication skillsExperience with iterative validation methods
Need for quick decisions with incomplete informationTransparency requirements for governance and traceabilityEconomic and time constraints
  • • Limited data availability and quality issues
  • • Time pressure in decision cycles
  • • Limited cognitive capacity of decision makers