The Rat Brain of Project Management

• Systems • By •

The Rat Brain of Project Management: A Simple System for Real Execution

If you had to teach project management to something that could only understand the basics—no abstractions, no complexity—what would remain?

Three things:

  • Capture
  • Digest (Process)
  • Execute

Why Simplification Wins

The concept is loosely inspired by behaviorist thinking, especially researchers like B. F. Skinner, who explored how behavior can be shaped through simple, repeatable systems.

Humans are more complex—but execution doesn’t improve with complexity.

It improves with clarity and repetition.

Step 1: Capture — Don’t Trust Your Memory

If it’s not captured, it doesn’t exist.

This is where most systems quietly break.

Ideas happen in motion:

  • Conversations
  • Meetings
  • Messages
  • Random thoughts

And unless they’re captured instantly, they disappear.

The Rule: One Input System

You don’t need more tools.

You need fewer decisions.

Bad systems look like this:

  • Notes app for ideas
  • Email for tasks
  • Slack for reminders
  • Calendar for “important things”

That’s not a system—that’s fragmentation.

Good systems look like this:

  • One inbox
  • One action
  • One habit

Examples:

  • Voice note → backlog
  • Meeting → transcript → tasks
  • Idea → single list

The tool doesn’t matter.

Friction does.

Step 2: Digest — Turn Chaos Into Decisions

Capture creates volume.

Processing creates direction.

And this is where most people rush—or skip entirely.

Why Processing Must Be Separate

Capture is reactive.

Processing is strategic.

If you mix them:

  • You think poorly
  • You prioritize poorly
  • You execute poorly

So you separate them.

What Happens During Processing

1. Define What It Actually Is

Is it:

  • A task (done today)?
  • A project (multi-step)?

If you can’t do it in a few hours, it’s not a task yet.

2. Break It Down

You can’t execute:

  • “Launch campaign”

You can execute:

  • Draft copy
  • Build landing page
  • Set up ads

Execution requires clarity.

Processing creates it.

3. Categorize Your Work

This is where awareness kicks in.

You start seeing patterns:

  • Too much admin
  • Not enough growth work
  • One project dominating everything

Categories create feedback loops.

4. Prioritize (Realistically)

Here’s the uncomfortable truth:

You will do less than you think.

Time is limited.

But attention is the real constraint.

So instead of asking:

  • “What can I do today?”

Ask:

  • “What deserves my focus today?”

5. Set Deadlines (and Expect to Be Wrong)

Most people underestimate:

  • Time
  • Cost
  • Complexity

A practical operator rule:

  • Things take 2–4x longer
  • Things cost 2–4x more

Planning for reality beats hoping for efficiency.

6. Delegate Early

Processing reveals capacity limits.

If everything stays on you:

  • Nothing scales
  • Everything slows

Ask:

  • Who else can do this?
  • Who should do this?

7. Define the Next Action

Every item must answer:

What happens next?

If it doesn’t, it stalls.

Examples:

  • “Email client”
  • “Review doc”
  • “Schedule call”

Simple. Clear. Executable.

8. Separate Your Horizons

Not everything belongs in “now.”

Create layers:

  • Active (this week)
  • Near-term (this month)
  • Long-term (6–18 months)

This reduces overwhelm without losing ideas.

Step 3: Execute — Only After You Decide

Execution is where people think work begins.

It doesn’t.

It begins after decisions are made.

Why Execution Feels Hard

Because most people:

  • Skip capture
  • Skip processing
  • Jump straight into action

That creates:

  • Rework
  • Misalignment
  • Wasted effort

What Good Execution Looks Like

When done properly:

  • You know what to do
  • You know why it matters
  • You know what comes next

So when something blocks you…

You don’t stop.

You switch.

The Real System: Flow, Not Control

This isn’t about rigid structure.

It’s about maintaining flow:

  • Capture keeps ideas alive
  • Processing gives them structure
  • Execution creates momentum

And momentum is what drives results.

Where Most Systems Break

1. Everything happens at once

Fix: Separate thinking from doing

2. Too many tools

Fix: Simplify inputs

3. Unrealistic planning

Fix: Assume longer timelines

4. No next step

Fix: Define the next action clearly

5. No delegation

Fix: Design around teams, not individuals

Where AI Actually Helps

AI is not the system.

It’s a multiplier.

Used correctly:

Capture

  • Transcribes meetings
  • Extracts tasks

Processing

  • Summarizes
  • Suggests structure

Execution

  • Drafts content
  • Automates workflows

Used incorrectly:

It just helps you stay disorganized faster.

Project management is not about tools.

It’s about sequence.

Capture → Process → Execute

Simple enough to follow.

Powerful enough to scale.

FAQs

What is the “rat brain” of project management?

A simplified three-step system—capture, process, execute—designed to make project management more consistent and actionable.

Why separate capture and processing?

Because they require different types of thinking. Combining them reduces clarity and effectiveness.

How do I know if something is a task or project?

If it can’t be completed in a few hours, it needs to be broken down into smaller tasks.

What is the biggest execution mistake?

Starting work before properly capturing and processing what needs to be done.

Do I need specific tools for this system?

No. The system works with any toolset. Simplicity and consistency matter more than software

Option 2
Need help aligning your tools, team, and execution? Email [email protected] to get started or Schedule a Call:

Schedule a Call

To go deeper into how systems like this scale into real execution environments, explore:
https://gabebautista.com/essays/systems/