Imported from sethmblack/paks-skills (idea-meritocracy-design/SKILL.md). Install upstream with npx skills add sethmblack/paks-skills --skill idea-meritocracy-design. Copyright stays with the author (MIT).

Idea Meritocracy Design

Design organizational decision-making systems where the best ideas win regardless of who they come from, using Ray Dalio's formula: Radical Truth + Radical Transparency + Believability-Weighted Decision Making.

When to Use

• Building or transforming organizational decision-making culture
• Request to "create an idea meritocracy" or "build a culture of radical transparency"
• Organization suffers from political dysfunction, hidden agendas, or decision-making by hierarchy
• Teams struggle to surface dissent or have productive disagreement
• Want to systematize how decisions are made and improve collective intelligence

Inputs

The Framework

Core Principle

An idea meritocracy is not democracy (all opinions equal) or autocracy (one person decides). It's a system where the best ideas win, weighted by the believability of the people offering them. This requires three components working together:

Idea Meritocracy = Radical Truth + Radical Transparency + Believability-Weighted Decision Making

Remove any component and the system fails:

• Without radical truth: People hide problems and withhold criticism
• Without radical transparency: Information asymmetry enables politics
• Without believability weighting: Bad ideas can win by volume or authority

Step 1: Assess Current State

Diagnose the current decision-making culture.

Questions to answer:

• How are decisions currently made? (By hierarchy? Consensus? Loudest voice? Unclear?)
• Where does information hide? (What do people know but don't say?)
• What happens when someone disagrees with leadership?
• How are mistakes handled? (Hidden? Blamed? Learned from?)
• Do the best ideas win, or do the best-positioned people win?

Common dysfunction patterns:

Step 2: Design Radical Truth Practices

Radical truth means saying what you really think, regardless of how uncomfortable it is.

Practices to implement:

1. Disagree openly: Create explicit expectation that disagreement is valuable
2. Say it to their face: Prohibit talking about people behind their backs
3. Reward problem-surfacing: Recognize people who identify issues early
4. Name the elephant: Create forums where uncomfortable topics must be addressed
5. Separate criticism from attacks: Teach how to critique ideas, not people

Implementation questions:

• What forums exist for disagreement? (If none, create them)
• What happens to someone who disagrees with leadership publicly?
• How quickly do problems get escalated vs. hidden?

Step 3: Design Radical Transparency Practices

Radical transparency means making almost everything visible to almost everyone.

Practices to implement:

1. Record meetings: Make discussions accessible for review and learning
2. Share decision rationale: Explain why decisions were made, not just what was decided
3. Open information: Default to sharing rather than restricting information
4. Visible feedback: Make performance feedback visible to relevant parties
5. Error logs: Track mistakes openly for collective learning

Boundaries (what NOT to make transparent):

• Personal information unrelated to work
• Information that would harm individuals without organizational benefit
• Legally protected information
• Competitive information that requires protection

Implementation questions:

• What information is currently hoarded?
• Who benefits from information asymmetry? (They'll resist)
• What infrastructure is needed? (Recording, documentation, access systems)

Step 4: Design Believability-Weighting Mechanisms

Believability weighting means opinions are weighted by competence, not authority or volume.

Components to implement:

1. Track record visibility: Make people's past performance in relevant domains visible
2. Reasoning requirement: Require people to explain why, not just what, they believe
3. Domain-specific believability: Someone believable in X isn't automatically believable in Y
4. Challenge high-believability disagreement: When credible people disagree, explore deeply
5. Update believability: Track record improves/degrades with demonstrated judgment

Believability assessment criteria:

Implementation questions:

• How will believability be measured and tracked?
• How will you prevent gaming of the system?
• How will you handle domains where no one has track record?

Step 5: Design Implementation Roadmap

Culture change is gradual. Implement in phases.

Phase 1: Foundation (Months 1-3)

• Leadership models the behavior (radical truth about themselves first)
• Create safe forums for disagreement (retrospectives, decision reviews)
• Begin documenting decision rationale
• Introduce the concepts and vocabulary

Phase 2: Practice (Months 3-6)

• Expand transparency practices
• Start tracking believability in specific domains
• Run believability-weighted decisions on lower-stakes issues
• Address resistance openly (using the new culture)

Phase 3: Integration (Months 6-12)

• Codify practices into standard operating procedures
• Build or adopt supporting tools
• Use the system for high-stakes decisions
• Continuously refine based on feedback

Phase 4: Maintenance (Ongoing)

• Onboard new people into the culture
• Regularly assess if the system is working
• Evolve practices as organization grows

Output Format

## Idea Meritocracy Design: [Organization/Team Name]

### Current State Assessment
**How decisions are made now:** [Description]
**Key dysfunction patterns identified:**
- [Pattern 1]: [Evidence]
- [Pattern 2]: [Evidence]

**Information flow problems:**
- [Where information hides and why]

### Radical Truth Design
**Practices to implement:**
1. [Practice]: [How it works] - [Who owns it]
2. [Practice]: [How it works] - [Who owns it]

**Expected resistance:** [What pushback to expect and how to address]

### Radical Transparency Design
**Information to make visible:**
| Information Type | Current State | Target State | Benefit |
|------------------|---------------|--------------|---------|
| [Type] | [Hidden/Limited] | [Visible to X] | [Why] |

**Boundaries (not transparent):**
- [What stays private and why]

### Believability-Weighting Design
**How believability will be assessed:**
- [Domain 1]: [How tracked]
- [Domain 2]: [How tracked]

**Decision-weighting mechanism:**
[How believability weights will be applied to decisions]

### Implementation Roadmap

**Phase 1 (Months 1-3): Foundation**
- [ ] [Action 1] - Owner: [Name]
- [ ] [Action 2] - Owner: [Name]

**Phase 2 (Months 3-6): Practice**
- [ ] [Action]
- [ ] [Action]

**Phase 3 (Months 6-12): Integration**
- [ ] [Action]
- [ ] [Action]

### Success Metrics
| Metric | Baseline | Target | How Measured |
|--------|----------|--------|--------------|
| [Metric] | [Current] | [Goal] | [Method] |

### Risk Mitigation
| Risk | Mitigation |
|------|------------|
| [Risk 1] | [How to address] |
| [Risk 2] | [How to address] |

Constraints

• Don't implement radical transparency without radical truth (transparency without psychological safety creates fear)
• Don't skip believability weighting (transparency + truth without weighting = chaos)
• Don't expect overnight change—culture shifts take 12-18 months minimum
• Don't ignore resistance—address it openly using the new principles
• Acknowledge that 20-30% of people may not adapt and may need to leave

Example

Input: "We're a 50-person startup. Decisions take forever because everyone has opinions and we try to reach consensus. But then after meetings, people complain in Slack DMs that they didn't really agree. How do we fix this?"

Output:

Idea Meritocracy Design: 50-Person Startup

Current State Assessment

How decisions are made now: Attempted consensus in meetings, but real opinions surface in back-channels afterward. Decisions drag on or get relitigated.

Key dysfunction patterns identified:

• Consensus paralysis: All opinions treated equally regardless of relevant expertise
• Hidden disagreement: People agree in meetings but express real views privately
• Back-channel culture: Slack DMs and hallway conversations hold the real information

Information flow problems:

• Real opinions hidden in public forums, expressed in private channels
• No visibility into who has expertise in what domain
• Decision rationale not documented, leading to relitigating

Radical Truth Design

Practices to implement:

1. "Speak now" rule: At end of each decision meeting, explicit question: "Does anyone disagree with this direction? Speak now or support the decision." - Facilitator owns
2. No back-channel complaints: If you disagree, say it in the meeting. DM complaints about decisions are a culture violation. - Leadership models
3. Disagree and commit: Once decision is made with open disagreement process, everyone commits. Track commitment. - Team leads own
4. Weekly "elephant naming": All-hands segment where uncomfortable topics must be raised. Anonymous submission, public discussion. - CEO owns initially

Expected resistance:

• "It's not safe to disagree publicly" - Address by leadership disagreeing with each other first, visibly
• "Some people are too harsh" - Establish norms for critique (attack ideas, not people)
• "Not everyone is comfortable speaking up" - Create async mechanisms (written disagreement option)

Radical Transparency Design

Information to make visible:

Boundaries (not transparent):

• Personal compensation details (share ranges, not specifics)
• Personal performance issues (between manager and individual until relevant to others)
• Confidential customer/partner information

Believability-Weighting Design

How believability will be assessed:

• Product decisions: Who has shipped similar features before? What were the outcomes?
• Technical decisions: Who has built similar systems? Track record of estimates vs. actuals
• Customer decisions: Who has direct customer exposure? Quality of past customer predictions
• Business decisions: Who has relevant business experience? Past judgment calls and outcomes

Decision-weighting mechanism: For significant decisions:

1. Identify the decision domain
2. Identify who has highest believability in that domain (track record + reasoning)
3. Solicit all opinions, but explicitly weight high-believability views
4. When high-believability people disagree, explore deeply before deciding
5. Document: "Decision X made. Key input from [names] due to their [relevant experience]."

Implementation Roadmap

Phase 1 (Months 1-3): Foundation

• Leadership team practices disagreement visibly - CEO
• Introduce "speak now" rule in all decision meetings - All managers
• Begin documenting decision rationale in shared system - Ops lead
• First "elephant naming" session - CEO facilitates
• Share this plan with entire company - CEO

Phase 2 (Months 3-6): Practice

• Create competency map (who knows what, based on what evidence) - HR lead
• Implement meeting recording or summary practice - Ops
• Run believability-weighted decisions on 3 medium-stakes issues - Leadership
• Address anyone violating "no back-channel complaints" - Managers
• Retrospective on what's working/not working - All hands

Phase 3 (Months 6-12): Integration

• Codify decision-making process into company operating system
• Use believability weighting for high-stakes decisions (strategy, hiring leads)
• Build or adopt tool for tracking believability by domain
• Incorporate into onboarding for new hires
• Assess culture change via survey, compare to baseline

Success Metrics

Risk Mitigation

Integration

This skill is part of the Ray Dalio expert persona. Use it when designing or transforming organizational decision-making systems. The idea meritocracy model is Bridgewater's distinctive contribution to organizational design, and while the full implementation is intense, the principles can be adapted to organizations of any size.