Ops Command Center

v3.2.1

Working With Me

A guide to how I operate, communicate, and collaborate. Designed to accelerate our work together.

Key Operating Parameters

Decision Threshold

60%

Confidence needed increase

Response Time

Same Day

Slack messages increase

Detail Orientation

9%

Strategic focus increase

Engagement Peak

30-90

Days optimal increase

Who I Am (The Short Version)

Core operating principles

I'm a strategic operator who lives at the intersection of vision and execution. I see patterns others miss, move faster than most people are comfortable with, and care deeply about building systems that work—not maintaining them. I'm direct to a fault, logic-driven, and energized by hard problems with real stakes.

My mind toggles constantly between 30,000-foot strategy and ground-level tactics. I can't stay at either altitude for long. I'm a builder and a teacher—I clarify my own thinking by explaining it to others. I commit fast at 60% confidence and iterate from there.

Operating Altitude Pattern

Strategy

30,000 ft

Tactics

Ground Level

Strategy

Back up

Toggle between levels frequently. Linear explanations at one altitude lose me.

Schedule & Availability

CST timezone, typically work until ~7pm

Daily Rhythm

Mornings: Sacred

Deep work, highest-impact tasks. Least communicative.

Afternoons: Interactive

Better for meetings and calls. More responsive.

Weekly Rhythm

Monday
Planning & Prep
Tuesday
Meeting Day
Wednesday
Deep Work
Thursday
Meeting Day
Friday
Close Out

Meeting Philosophy

Meetings are for urgent situations or extremely complex problems that need real-time, multi-person hashing out. Everything else can go async.

Required:
  • • Clear objective (not "sync" or "discuss")
  • • Expected outcome (decision/change/action)
  • • Materials sent in advance
Pet Peeves:
  • • "Update me" meetings
  • • No agenda or clear outcomes
  • • Hour meetings that should be 15 min

Communication Protocol

Channel selection and response expectations

Urgent + Important

Text

Response: ASAP

Everything else

Slack

Response: Same day

External parties

Email

Response: < 24 hours

Complex/visual

Loom

Response: Async

How I Process

  • Text over video - I read faster than I watch
  • BLUF (Bottom Line Up Front) - lead with the point
  • Under a page is ideal. Use headers to scan.
  • Haven't heard back in 24h? Just bump me.

What Loses Me

  • Lengthy background before the point
  • Repetition - once is enough
  • Excessive hedging or disclaimers
  • Salesy language or manipulation

Decision Framework

The Step-Back Method & 60% Rule

1

Back Up

Gather info, understand context, pros & cons

2

Build Matrix

Evaluate risk, ROI, maintainability, fit

3

Reach 60%

Sufficient confidence - no need for certainty

4

Execute

Move forward with feedback loops

5

Iterate

Rapid refinement and course correction

The 60% Rule

"If you're 60% confident and have feedback loops in place, move forward. Waiting for certainty is a decision to not decide."

Confidence Required 60%
0% Decision Point 100%

When You Need a Decision From Me

The problem (clearly framed)
2-3 options with tradeoffs
Your recommendation and reasoning
What you've ruled out and why

Don't just bring the problem—bring your thinking.

Collaboration Dynamics

Team fit and working style

Best Fit

  • People who match my pace
  • High-performers who don't need hand-holding
  • Direct communicators who push back with reasoning
  • Comfortable with ambiguity and iteration
  • Low ego, high competence

Challenging Fit

  • Slow decision-makers
  • People who require extensive process
  • Those who need validation before acting
  • Chronic pessimists
  • Micromanagers

Trust

How to build and maintain it

Earn It

  • Deliver what you commit to
  • Bring solutions, not just problems
  • Be direct - no guessing needed
  • Own mistakes, fix systems
  • Demonstrate sound judgment
  • Push back with reasoning

Lose It

  • Say one thing, do another
  • Hide problems until they explode
  • Require constant hand-holding
  • Make emotional vs logical appeals
  • Be consistently slow without reason
  • Surprise me with things I should know

Energy Management

What fuels vs depletes operational capacity

Energizers

  • Complex strategic challenges
  • High autonomy with clear objectives
  • Novelty - new problems
  • Visible progress & rapid feedback
  • Intellectual sparring
  • Building from nothing

Drains

  • Routine, repetitive work
  • Extensive emotional labor
  • Meetings that should be emails
  • Micromanagement
  • Bureaucracy without value
  • Forced consensus-building

Signs I'm Running Low

More terse than usual Visible impatience Withdrawing from interactions Sharp, unexpected criticism

Strengths to Leverage

Core capabilities

Strategic Pattern Recognition

Spots connections and opportunities others miss

Root Cause Analysis

Gets to the real problem, not the symptom

Systems Thinking

Designs frameworks that scale

Speed

Decides and moves quickly, biases toward action

Translation

Bridges vision and execution seamlessly

Teaching

Clarifies complex concepts through explanation

Known Blind Spots

Areas where I need support

Detail Retention

medium

Operates at strategic altitude, may miss granular details

Patience with Slow Processing

high

May move faster than comfortable for others

Emotional Attunement

medium

Logic-first, may miss emotional undercurrents

Follow-through on Maintenance

low

Builder not operator - designs but resists maintaining

Quick Reference Card

If you need... Do this...

Urgent response

Text me

A decision

Slack with options + your recommendation

To escalate

Slack (customer, employee, strategic impacts)

To give feedback

Direct, data-backed, challenge reasoning

To book time

Tue/Thu PM, send agenda in advance

To share bad news

Slack immediately, one line, no disclaimers

To show me something

Loom it

To update me

Async message, not a meeting

To teach me something

Send resources, let me explore, sandbox

To pitch an idea

Lead with problem, show ROI, give me a role

This is a living document. If something here isn't working or doesn't match reality, tell me.