mochary-method
Skill4 starsChanged 7 months agoMITView on GitHub
Matt Mochary's CEO coaching playbook. Covers personal productivity (Top Goal, Energy Audit, Zone of Genius), emotional regulation (Fear & Anger), team operations (meetings, DRIs, agreement tracker, OKRs), decision-making (RAPID, clean escalation, issue/proposed solution), feedback, hiring/firing, 1:1 format, and company culture. Use when coaching on leadership, structuring meetings, making decisions, giving feedback, managing performance, or running a startup operating system.
In this repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- problem-solvingSkill
- work-planSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
35 rules. About 0 are common, 35 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈35
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Use an accountability partner (text them your Top Goal each morning, confirm completion each evening)
- Distinctive: line 64
Check email only 2-3 times daily (batch processing)
- Distinctive: line 72
Write one thing you're grateful for each morning.
- Distinctive: line 85
When feeling fear: pause, check with someone NOT experiencing it
- Distinctive: line 89
Not a base emotion -- it's a cover for pain
- Distinctive: line 91
Don't project it outward. Sit with it.
- Distinctive: line 98
Check with a neutral party
- Distinctive: line 108
Check yourself: "Am I above or below the line right now?" If below, don't make decisions.
- Distinctive: line 120
5-minute rule: If a decision can't be reached in 5 minutes of discussion, escalate to RAPID framework.
- Distinctive: line 132
Critical rule: All meeting notes published company-wide.
- Distinctive: line 165
If a commitment can't be met, notify immediately -- don't wait until the deadline.
- Distinctive: line 214
Critical rule: NEVER deliver negative feedback via email, text, or voicemail.
- Distinctive: line 225
Only correct response to a compliment: "Thank you." Full stop.
- Distinctive: line 226
Never deflect, downplay, or over-explain.
- Distinctive: line 228
When you catch gratitude toward someone, communicate it to them.
- Distinctive: line 254
Use when a team is too large for easy consensus, or when 5-minute discussion doesn't resolve it.
- Distinctive: line 273
When escalating a decision:
- Distinctive: line 275
No spin, no politics, no "selling" your preferred outcome
- Distinctive: line 286
Open discussion: No proposal, brainstorm from scratch (slowest, highest buy-in)
- Distinctive: line 288
Default to #2 for most decisions.
- Distinctive: line 305
Ask: "What are the 3 most important issues for you to solve in the first 90 days?"
- Distinctive: line 306
Ask why they left previous roles (promoted out?
- Distinctive: line 314
Create comprehensive checklist + video of required knowledge
- Distinctive: line 318
Don't "cannonball" into a new leadership role -- spend initial weeks observing
- Distinctive: line 323
Document written PIP with milestones at 7-, 30-, 60-, 90-day marks
- Distinctive: line 332
Do NOT blame or criticize
- Distinctive: line 338
Create written policies for raises, promotions, compensation
- Distinctive: line 341
Every position at every seniority level has specific compensation + advancement criteria
- Distinctive: line 370
When together: Person A shares thoughts and feelings fully
- Distinctive: line 372
Only then present your response
- Distinctive: line 379
Create company wiki mandatory for all new hires
- Distinctive: line 392
Ask about their situation
- Distinctive: line 396
Ask for limited time: "10-minute introductory call"
- Distinctive: line 459
Team size rule: Don't exceed 6 people before PMF.
- Distinctive: line 467
Avoid equal splits in decision authority.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
The Mochary Method
Source: Matt Mochary, "The Great CEO Within" + open-source Mochary Method Curriculum
Matt Mochary coaches the top CEOs in Silicon Valley (Sam Altman, Brian Armstrong, Naval Ravikant). He open-sourced his entire method. This skill codifies it into modular components you can pull individually.
Component 1: Personal Productivity
Top Goal
The single most important habit in the method.
- Schedule 2 uninterrupted hours daily, early in the day
- Work ONLY on your single highest priority -- nothing else
- Calendar-block it. Treat it like an external meeting you can't move.
- Use an accountability partner (text them your Top Goal each morning, confirm completion each evening)
Why it works: External requests expand to fill all available time. Without a protected block, your most important work never happens.
Energy Audit
Print your calendar for the past 2 weeks. Color-code every hour:
- Green = you had MORE energy at the end than the start
- Red = you had LESS energy at the end
Target: 75-80% green time.
For red activities: delegate, eliminate, or restructure. If you can't eliminate, batch them into a single day so they don't contaminate green days.
Zone of Genius
Four zones (from Gay Hendricks):
| Zone | Definition | Action |
| Incompetence | Others are better than you | Delegate immediately |
| Competence | You're adequate, but others match you | Delegate |
| Excellence | You're better than most, BUT you don't love it | Dangerous -- delegate this too |
| Genius | Uniquely skilled AND you love it | Spend 75-80% of time here |
The trap is Zone of Excellence. You're great at it, people praise you for it, but it drains you. That's the zone to escape.
GTD (Getting Things Done)
Maintain these lists in a single trusted system:
- Next Actions -- priority tasks by context
- Waiting For -- items delegated to others (with dates)
- Someday/Maybe -- future possibilities
- Agenda -- topics for recurring meetings (one list per person/meeting)
- Projects -- multi-step serial tasks
- Goals -- vision and OKRs reference
Inbox Zero
- Check email only 2-3 times daily (batch processing)
- Sub-2-minute items: respond immediately
- Everything else: move to Next Actions list
- Process to empty every session
- Eliminates context-switching tax
Gratitude Practice
Write one thing you're grateful for each morning. Shifts baseline mindset. Mochary's claim: people perform best when having fun and feeling good about themselves.
Component 2: Emotional Regulation
Fear and Anger Give Bad Advice
The foundational Mochary principle. Never make decisions or take action while in fear or anger.
Fear:
- Grips you and leads to exaggerated predictions
- Makes you see worst-case as most likely
- When feeling fear: pause, check with someone NOT experiencing it
- They'll help you see the situation accurately
Anger:
- Not a base emotion -- it's a cover for pain
- Shifting from anger = acknowledging and FEELING the underlying pain directly
- Don't project it outward. Sit with it.
- Once the pain is felt, anger dissolves and clear thinking returns
Practice:
- Notice the emotion (name it)
- Pause -- do NOT act
- Breathe, feel the underlying sensation
- Check with a neutral party
- Only then decide
Conscious Leadership
From the Conscious Leadership Group (referenced heavily in the curriculum):
- Above the line: Open, curious, committed to learning
- Below the line: Closed, defensive, committed to being right
Check yourself: "Am I above or below the line right now?" If below, don't make decisions. Shift first.
Component 3: Meetings & Team Operations
Meeting Principles
- Pre-write everything. Anyone raising a topic writes it up BEFORE the meeting, including a proposed solution. No verbal-only agenda items.
- Writing over talking. Writing scales; spoken words are ephemeral. Written proposals circulated pre-meeting = 3x more productive meetings.
- Leader speaks LAST. Gather all opinions before revealing yours. Prevents anchoring bias.
- Silent input first. Have team write thoughts before anyone speaks. Captures introverted perspectives, prevents dominant voice bias.
- 5-minute rule. If a decision can't be reached in 5 minutes of discussion, escalate to RAPID framework.
Meeting Cadence (Recommended Weekly)
| Meeting | Purpose | Format |
| 1:1s | Coaching + accountability | See Component 4 |
| Leadership team | Cross-functional decisions | Issue/Proposed Solution |
| CEO open office hour | Accessibility | Drop-in |
| All-hands | Transparency + alignment | Updates + Q&A |
| Social event | Culture + connection | Informal |
Critical rule: All meeting notes published company-wide. Attendance should never be required for information access.
No-Meeting Days
- 1 day: no internal meetings
- 1 day: no external meetings
- 3 days: no meetings at all (aspirational target)
Arrive 15 min early to external meetings. Wrap internal meetings 5-10 min early.
DRI (Directly Responsible Individual)
Assign ONE person as DRI for every:
- Metric
- Goal
- Project
- Meeting
- Decision
Multiple owners = no owner. If six people are debating in Slack for three days, you don't have a DRI.
Areas of Responsibility (AOR)
Master document listing ALL company functions with designated DRI. Update as roles shift. Cross-train a backup for each critical role. No single points of failure.
Agreement Tracker
Impeccable agreements are:
- Precisely defined (not vague)
- Written (not verbal)
- Fully agreed to by all relevant parties
- Tracked with DRI + due date
If a commitment can't be met, notify immediately -- don't wait until the deadline. "Verbal agreements are not impeccable."
OKRs (Objectives & Key Results)
Structure: 3 objectives x 3 key results each. Cascade: Company -> Department -> Team -> Individual.
- Objective: "Where do we want to go?" (not necessarily measurable, inspirational)
- Key Result: "How do we know we're getting there?" (measurable, time-bound)
Implementation:
- Leadership brings ideas pre-meeting
- Better to let individuals create their own (increases emotional investment)
- Track quarterly via traffic-light system (Green/Yellow/Red)
- Review progress weekly
KPIs
- Track 5-6 most significant metrics
- Make visible to entire team (dashboard on screen)
- Include counter-metrics to prevent over-optimization
- Review regularly
Component 4: 1:1 Format & Feedback
1:1 Meeting Structure
The Mochary 1:1 is NOT a status update. It's coaching.
Format:
- Report's agenda first (their topics, not yours)
- Accountability check: Did you complete what you committed to?
- Coaching: What's the current health? What's going well? What's not going well?
- Issue/Proposed Solution: For anything not going well, present the issue + a proposed solution
- Commitments: What will you do before next 1:1?
The manager's job in a 1:1 is to LISTEN, not to direct.
Feedback Framework (Nonviolent Communication adapted)
Giving feedback:
- Ask permission -- "Can I share some feedback?"
- State the behavior -- facts only, no judgment ("When you arrived 10 minutes late to the client meeting...")
- State how it made you feel -- use actual emotions ("...I felt anxious and embarrassed")
- Share your story -- your interpretation ("My story is that the client thought we don't value their time")
- Make a specific request -- positive action ("Would you commit to arriving 5 minutes early to client meetings?")
- Confirm acceptance -- "Does that work for you?"
Critical rule: NEVER deliver negative feedback via email, text, or voicemail. Always in person or live video.
Seeking Feedback: The 4 A's
- Ask for it (regularly, proactively)
- Acknowledge it (repeat back what they said to confirm understanding)
- Appreciate it (thank them -- even if you disagree)
- Act on it (implement or explain why not)
Appreciation
- Only correct response to a compliment: "Thank you." Full stop.
- Never deflect, downplay, or over-explain.
- Reserve 1 hour weekly for intentional appreciation outreach.
- When you catch gratitude toward someone, communicate it to them.
Fact vs. Story Separation
Distinguish observable facts from interpretations:
- Fact: "You submitted the report on Thursday" (observable)
- Story: "You don't care about deadlines" (judgment)
Present facts first. Label stories explicitly as "my story is..." Reduces defensiveness, enables clearer problem-solving.
Component 5: Decision-Making
Issue / Proposed Solution Format
The standard unit of decision-making in the Mochary Method:
- Facts -- physical actions that have occurred, no judgment
- Story -- thoughts, opinions, interpretations
- Proposed Solution -- very specific action items with DRI + due date
Rule: You cannot say "I don't know." You must present a guess, phrased boldly. Discussion happens around a concrete proposal, not a blank page.
RAPID Framework (from Bain & Company)
Use when a team is too large for easy consensus, or when 5-minute discussion doesn't resolve it.
| Role | Responsibility |
| R (Recommend) | The person who proposed the issue and solution |
| A (Agree) | People whose input MUST be incorporated |
| P (Perform) | People who will execute the decision |
| I (Input) | Senior stakeholders whose departments are affected |
| D (Decide) | Final decision-maker |
Reversibility Principle
- Irreversible decisions: CEO decides. Take time, deliberate carefully.
- Reversible decisions: Delegate to reports. Decide quickly, iterate.
Most decisions are reversible. Default to speed.
Clean Escalation
When escalating a decision:
- Present facts without advocacy -- let the decision-maker choose
- No spin, no politics, no "selling" your preferred outcome
- Normalizes escalation and removes shame
- Format: "Here are the facts. Here are two options. Here are the tradeoffs. What do you want to do?"
Buy-In vs. Speed
Buy-in and speed of decision are inversely correlated.
Three methods (ranked by buy-in, lowest to highest):
- Decide -> Tell -> Answer questions (fastest, lowest buy-in)
- Straw man approach (optimal): Create proposal -> Share -> Invite feedback -> Discuss -> Decide
- Open discussion: No proposal, brainstorm from scratch (slowest, highest buy-in)
Default to #2 for most decisions. Use #1 only for trivial/reversible ones. Use #3 only for high-stakes, values-level decisions.
Avoiding Groupthink
- Have team write votes/thoughts BEFORE leader shares perspective
- Let junior staff speak and question first
- Titles influence answers -- neutralize hierarchy in decision sessions
Component 6: Hiring, Firing & People
Hiring
Sourcing: Contact your top 10 most talented people weekly. Ask each for 3 referrals. Document all candidates in ATS.
Interview focus:
- Ask: "What are the 3 most important issues for you to solve in the first 90 days?"
- Ask why they left previous roles (promoted out? recruited? fired?)
- Share a written 90-day roadmap of what the role requires -- confirm excitement
Rule: Hire only A-players who fit both job requirements AND culture. Keep pre-PMF team under 6.
Onboarding (More Critical Than Recruiting)
Most companies neglect this. Mochary's protocol:
- Create comprehensive checklist + video of required knowledge
- Schedule first day 2 hours after normal start (more people present)
- Assign a buddy for first 2 weeks
- Daily 15-minute check-ins with buddy
- Don't "cannonball" into a new leadership role -- spend initial weeks observing
Performance Improvement Plan (PIP)
For underperformers:
- Document written PIP with milestones at 7-, 30-, 60-, 90-day marks
- Weekly progress meetings
- Termination decision at 30 days if milestones missed
- Provides legal protection and small chance of improvement
Firing with Grace
- Publicly praise the person's contributions
- Take ownership: "I couldn't match your skills to our needs"
- Do NOT blame or criticize
- Absolve them of responsibility
- Help misaligned employees find better fits (if values diverge, facilitate exit)
Compensation & Politics Prevention
- Create written policies for raises, promotions, compensation
- Apply consistently -- never reward lobbying
- Implement Grade Level Planning (GLP) at 25-50 employees
- Every position at every seniority level has specific compensation + advancement criteria
- Visible to all staff
Component 7: Company Culture & Transparency
Culture Definition
By 30 employees, culture exists -- codify it, don't create it.
Method: Identify 3-5 non-leadership staff who exemplify desired behaviors. Name them and the specific behaviors. Those behaviors = your values.
Alternative (small teams): Complete: "You can make all decisions if you..."
Accountability + Coaching + Transparency
Three organizational requirements at every level:
| Pillar | Definition |
| Accountability | Declare destination (vision, OKRs, KPIs), action steps, and whether steps were taken |
| Coaching | Declare current health (good and not good). For the not good: issue + proposed solution |
| Transparency | Share all relevant info (positive and negative). "Our imaginations are much more powerful than reality" -- actual data prevents worse assumptions |
Conflict Resolution
- Meet each party separately first (build trust in private)
- Understand core issues without defensive posturing
- When together: Person A shares thoughts and feelings fully
- You summarize back until they say "that's right"
- Only then present your response
- Remain impartial -- goal is resolution, not victory
Documentation System
"If you do it twice, write it down."
- Create company wiki mandatory for all new hires
- One process documented per week minimum
- Link all processes to master spreadsheet
- Require 3 months of use before allowing modifications
- Prevents knowledge loss through turnover
Component 8: Sales & Fundraising
Sales: Build Trust First
Before pitching:
- Ask about their situation
- Listen actively -- reflect back their words
- At second meeting, reference first conversation details
- Be explicit: "Before discussing us, I want to understand your situation"
- Ask for limited time: "10-minute introductory call"
Sell Results, Not Features
Customers care about business results, not functionality. Focus on "why" (the vision). Paint the picture of the world where their desires are fulfilled via your product.
Three-Step Selling
- Build trust with prospect
- Identify customer's specific pain point
- Present solution to THAT pain
Sales Team Structure (Build ONLY at PMF)
| Role | Function |
| Qualifiers (SDRs) | Generate qualified leads (separate inbound from outbound) |
| Closers (AEs) | Close qualified deals |
| Farmers (CS) | Retention + upsell |
Growth bottleneck is usually lead generation, not salespeople. Scale team only after predictable lead gen.
Lead Generation: Seeds, Nets, Spears
- Seeds: Word-of-mouth, referrals, prior relationships (highest quality, slowest)
- Nets: Marketing-sourced -- events, SEO, ads (quantity over quality)
- Spears: Direct outbound -- email, LinkedIn (quality over quantity)
Fundraising: Relationship First
- Pick a partner investor, not just a firm
- Get 3-5 network introductions via email (stack in same week)
- Build personal trust/liking BEFORE discussing company
- Sell yourself, not the company
How to brag appropriately:
- Credit others' contributions
- Highlight hard work required
- Share personal vulnerability
- Emphasize noble mission
- Express gratitude
Component 9: Vision & Strategy
Ten-Year Vision Framework
Imagine dominant industry position and answer:
- What industry do you dominate?
- Who is your customer (real person, not company)?
- What customer pain do you solve?
- What makes your solution unique?
- What competitive moat/asset do you control?
Product-Market Fit
Know you've achieved it when:
- Long-term contracts (B2B)
- Second purchases / subscription renewals (B2C)
- High NPS
- Organic social sharing
Team size rule: Don't exceed 6 people before PMF. Premature scaling destroys startups.
Focus Principle
Greatest startup risk = resource fragmentation. Concentrate on fewer priorities with depth. Startups fail from diffusion, not slowness.
50/50 Partnership Warning
Avoid equal splits in decision authority. Deadlocks harm momentum and culture. One person must be the tiebreaker.
Quick Reference: When to Use What
| Situation | Pull This |
| "I'm overwhelmed / no time for important work" | Top Goal + Energy Audit |
| "I'm making a decision while stressed" | Fear & Anger + Conscious Leadership |
| "Meetings are unproductive" | Pre-write + Issue/Proposed Solution |
| "Nobody owns anything" | DRI + AOR + Agreement Tracker |
| "Team can't agree on a decision" | RAPID + Clean Escalation |
| "I need to give tough feedback" | Feedback Framework (NVC) |
| "Team member is underperforming" | PIP Protocol |
| "I need to fire someone" | Firing with Grace |
| "We need to define our culture" | Culture Definition method |
| "Conflict between team members" | Conflict Resolution steps |
| "Setting quarterly goals" | OKRs (3x3 cascade) |
| "I'm hiring" | 90-day roadmap + sourcing protocol |
| "Preparing for fundraising" | Relationship-first fundraising |
| "Building a sales team" | Seeds/Nets/Spears + PMF check |
| "Running a 1:1" | 1:1 Format (report's agenda first) |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

