Skip to main content

principles-based-thinking

Codify and apply core principles to make consistent decisions across diverse situations rather than relying on rules or intuition

Source facts

Repository
lev-os/agents
Last source activity
March 7, 2026 at 00:14
Detected SKILL.md language
English
Stars
23
Forks
2

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
principles-based-thinking
description
Codify and apply core principles to make consistent decisions across diverse situations rather than relying on rules or intuition
# Principles-Based Thinking **What**: A decision-making approach where you explicitly document fundamental beliefs and values as principles, then systematically apply them to situations rather than deciding case-by-case based on intuition or rigid rules. **When to use**: When facing recurring decision types, building organizational culture, or operating in complex domains where rules are too rigid but pure intuition is inconsistent. **Introduced by**: Ray Dalio in "Principles: Life and Work" (2017), though concept has ancient philosophical roots ## Core Mechanism **The hierarchy:** 1. **Principles**: Fundamental truths about how the world works or what you value ("Truth over harmony," "Pain + Reflection = Progress") 2. **Application**: Map situation to relevant principles 3. **Decision**: Let principles guide action consistently **Key insight**: Decisions become reproducible and improvable. Document principles, refine them based on outcomes, apply systematically. ## When to Apply **Use principles-based thinking when:** - Making repeated decisions of similar types - Building organizational culture or team norms - Operating in complex domains where simple rules fail - Scaling decision-making beyond yourself - Wanting consistency across time and people **Skip if:** - Truly one-off decisions with no pattern - Domain has clear optimal rules that cover all cases - Situations too simple to warrant principle development - Speed matters more than consistency ## Execution Steps ### 1. Capture Principles from Experience After significant decisions or failures, ask: "What principle should guide similar situations?" Write it down explicitly. ### 2. Make Principles Falsifiable Avoid vague platitudes. "Hire slow, fire fast" is better than "Value people." Specific enough to be wrong. ### 3. Test for Conflicts Identify where principles tension exists. Example: "Move fast" vs. "Quality first." Articulate how you resolve the tradeoff. ### 4. Create Principle Library Organize by domain: Hiring, Product, Communication, etc. Make searchable and accessible. ### 5. Apply Systematically When facing decision, ask: "Which principles apply here?" Refer to documented principles, don't rely on memory or mood. ### 6. Refine Based on Outcomes If principle led to bad outcome, update it. Treat principles as hypotheses, not dogma. ### 7. Share and Align For organizations: Make principles explicit and shared. Enables scalable decision-making and cultural alignment. ## Real-World Applications **Bridgewater Associates (Dalio)**: ~200 documented principles govern everything from meetings to hiring to investment decisions. Enables consistency at scale (1,500+ employees). **Amazon Leadership Principles**: 16 principles (Customer Obsession, Bias for Action, etc.) used in hiring interviews, performance reviews, strategic decisions. **Personal Finance**: "Spend below income," "Invest in index funds," "Maintain 6-month emergency fund" guides thousands of micro-decisions without re-deciding each time. **Code Review**: "Optimize for readability," "Prefer composition over inheritance," "Write tests first" guides review feedback consistently across team. ## Key Indicators **Signs of effective principles-based thinking:** - Decisions feel consistent over time - New team members can predict decisions - Conflicts surface as principle tensions (discussable) - Principles evolve based on empirical feedback **Red flags:** - Principles too vague to guide action ("Be excellent") - Principles contradict without resolution mechanism - Principles stated but not applied - No updates despite failures ## Common Mistakes **Vague principles**: "Quality matters" doesn't guide tradeoffs. "Ship working software over perfect documentation" does. **Treating principles as absolute**: Real world has tensions. "Transparency" sometimes conflicts with "Confidentiality." Need hierarchy or context conditions. **Too many principles**: If you have 50 principles, you have none. Focus on core 5-15. **Principles as PR**: Stating principles for external audience rather than internal decision-making. ## Related Frameworks **Complementary**: Decision Trees, Mental Models, First Principles Thinking, Values Clarification **Contrasting**: Case-by-case judgment, Strict rules-based systems, Pure intuition **Sequential**: Experience decision/outcome → Extract principle → Document → Test in new situations → Refine ## Scoring Criteria **Practitioner Weight**: 9/10 — Dalio built one of world's largest hedge funds explicitly using this approach; Amazon's principles are core to their execution **Clarity & Executability**: 8/10 — Concept is clear; execution requires discipline to document and apply consistently **Proven ROI**: 8/10 — Demonstrated at organizational scale (Bridgewater, Amazon); enables consistent culture and scalable decision-making **Novelty**: 7/10 — Codifying principles is somewhat novel; the underlying idea of principled thinking is ancient **Cross-Domain Applicability**: 9/10 — Applies to personal decisions, organizational culture, engineering practices, product strategy, investing **Total Score**: 41/50 (Tier 1: Canonical)
View on GitHub