Meysam Sarabadani

Blog|📚 Book|Story of an Advisory|Playbooks|Team Audit|Ask Playbook|About|Newsletter

OPERATIONAL FRAMEWORKS & MENTAL MODELS

Leadership Playbooks & Mental Models

A visual, interactive reference of the core operational frameworks I repeat daily to Tech Leads, Product Managers, and executives.

PLAYBOOK 01 • HIGH-VELOCITY CULTURE

The High-Velocity Paradox & The No-Sulk Protocol

Read Full Essay
The 4-Quadrant High-Velocity Leadership Paradox
01. TOUGHER

Uncompromising on Standards

Never rubber-stamp a fragile architecture, ambiguous PRD, or missed follow-up just to keep the room comfortable. Quality is non-negotiable.

02. NICER

Scalpel on the Problem, Warmth to the Human

Directness is never an excuse for hostility or arrogance. Dismantle flawed assumptions ruthlessly while treating the teammate across from you with genuine care.

03. MORE FLEXIBLE

Fierce in Debate, Fluid in Ego

Fight hard for your thesis, but the second better data surfaces—or a decision is locked—pivot immediately. Care about getting it right, not being right.

04. THICKER-SKINNED

Zero Ego Latency

At high speed, feedback comes fast and unvarnished. If a blunt review sends you into a 3-day sulk, your ego latency is a bottleneck. Extract the signal and move.

Interactive Matrix: The Kindergarten vs. The High-Velocity Arena
Click a scenario below
Kindergarten / Playground Reaction

The Silent Treatment: DMs go cold, routing messages through a 3rd party, freezing each other out.

High-Velocity Arena Standard

Intense debate in the room anchored on data, followed by an immediate relational reset once decided.

Leader Intervention Protocol:

24-Hour No-Sulk Protocol: If two teammates go radio silent after a clash, put them on a direct call within 24 hours to clear the air.

PLAYBOOK 02 • CORE PILLARS

The Three Non-Negotiables of Scalable Systems

Read Full Essay
PILLAR 01

Radical Transparency

Kill Toxic Politeness

Superficial harmony is not respect. Calling out a broken architecture or unrealistic timeline directly is how you protect the team from public failure.

PILLAR 02

Strategic Thinking

The Discipline of an Empty Calendar

If your calendar is 100% tactical firefighting, you aren't leading. Protect uninterrupted blocks to view the system from 20 feet up and ruthlessly kill low-impact work.

PILLAR 03

Extreme Ownership

Unlocked by Extreme Delegation

Zero finger-pointing outward. Empower your engineers with end-to-end delegation, while holding ultimate accountability when an outcome falls short.

PLAYBOOK 03 • EXECUTION & FOLLOW-UP

The Handoff Trap & The 4-Step Escalation Ladder

Read Full Essay
Framework: The Passive Mindset vs. True Ownership
The Handoff Trap ('I Did My Part')
  • When hitting a blocker:Sends an email or tags a ticket, then waits indefinitely.
  • Definition of 'Done':“I did my part and dropped the message, my job is finished.”
  • Unclaimed/Orphaned problems:Steps over them because “it’s not in my formal job description.”
  • Measurement of Success:Output & task completion (checkbox mentality).
True Ownership ('Own The Finish Line')
  • When hitting a blocker:Switches channels proactively: pings Slack, hops on a 5-min call, or sets up a huddle.
  • Definition of 'Done':“The job is only done when the solution is shipped and verified.”
  • Unclaimed/Orphaned problems:Grabs them off the floor, drives alignment, and carries them across the finish line.
  • Measurement of Success:Outcome & delivered business impact.
Cheatsheet: The 4-Step Communication Escalation Ladder
Step 1Hour 0

Initial Async Request

Send the structured email or Jira ticket to establish context and clear deliverables.

Step 224h No-Reply

Direct Chat Ping (Slack / Teams)

If no response within 24 hours, don't send another email. Ping them directly in real-time chat.

Step 348h No-Reply

5-Minute Quick Sync or Desk Drop-In

If chat stalls, grab 5 minutes on their calendar or walk over to sync face-to-face.

Step 4Blocked Path

10-Min Alignment Huddle / Escalation

Gather all decision-makers into a single room or call to unblock dependencies decisively.

PLAYBOOK 04 • CONSTRUCTIVE FRICTION

We’re Not Selling Ice Cream: Constructive vs. Toxic Friction

Read Full Essay
✓ Constructive Friction (Amplify This)

Rooted in Intellectual Honesty and uncompromising standards. When a Tech Lead rejects an ambiguous PRD or two engineers debate database throughput trade-offs—that isn't a bug; it is the feature.

✕ Toxic Friction (Crush Immediately)

Stemming from turf wars, fragile egos, silent nodding in meetings followed by hallway complaining, or post-meeting sulking. When people fight to win an argument rather than build a better system, crush it on sight.