System Upgrade Workbook System Upgrade
Executive Functioning Protocol v1.0
Operator Identification
01. System Diagnostics
Identify where your current "operating system" is experiencing lag. Rate each area from 1 (System Crash) to 5 (Peak Performance).
Task Initiation (Getting Started)
1 2 3 4 5
Organization (Finding Materials)
1 2 3 4 5
Planning (Prioritizing Tasks)
1 2 3 4 5
Observation Log
Describe a recent situation where your "system" failed. What happened?
The Mission
What is ONE big goal you'd achieve if your brain was running at 100%?
Module: Analysis
Secured Connection // 80% Power
02. Task Deconstruction
Big projects are "Overload Risks." Break them down into sub-routines (small steps) to prevent a system freeze.
Sample Routine
"Research Paper on WWII"
Find 3 primary sources (20 min)
Outline the main intro (15 min)
Write first 2 paragraphs (30 min)
Initialize Your Own Project
The "Overload" Project Name
Sub-Routines (Break it down) Time Est.
1
2
3
4
5
Module: Deconstruction
Optimizing Workflow // 92% Power
Brain Blueprint Infographic Core Command Center
Brain Blueprint
Strategic Overwatch
01. Quick Start
The 2-Minute Rule
If it takes less than 120 seconds, execute immediately. No scheduling required.
Body Doubling
Work while someone else is in the room. Presence increases focus frequency.
02. Data Sync
External Memory
Never store info in short-term RAM. Write it, type it, or voice-record it instantly.
Visual Cues
Place physical items (backpack, shoes, notes) in the direct line of sight for the next task.
03. Thermal Control
Pomodoro Pulse
25 mins of processing / 5 mins of system cooling. Prevents CPU burnout.
Environment Filter
Clear the workspace. A messy cache slows down processing speeds.
04. Fail-Safe
The Reboot
Feeling stuck? Change your physical location. Move from desk to kitchen to reset.
Emergency Checklist
Have 3 tiny steps ready for when focus fails. Just do Step 1 to restore power.
"Control the variables. Master the mission."
Signal Strength
Mission Status Log Mission Status Log
Weekly Executive Functioning Deployment
Week Of
___ / ___ / ___
Operator
Primary Mission Objective
Define your main focus or top priority for this specific week.
Mon
Focus Level
Protocol Check
Tue
Focus Level
Protocol Check
Wed
Focus Level
Protocol Check
Thu
Focus Level
Protocol Check
Fri
Focus Level
Protocol Check
Sat
Focus Level
Protocol Check
Sun
Focus Level
Protocol Check
End-of-Week Report
What worked? Where was the most system lag?
Next Week Initialization
One change to implement for better performance:
Unit: Self-Monitoring
System Integrity: Verified
Tactical Task Cards Tactical Task Cards
Quick-Reference Executive Functioning Modules
Instructions: Cut along the dashed lines. Keep these cards in your workspace, phone case, or wallet for immediate deployment when focus fails.
Protocol 01
Initiation Launch
Start a timer for 5 minutes. Do the absolute smallest step of the task. Just one.
Protocol 02
Cache Clear
Sweep your workspace. If it's not needed for the current mission, move it out of sight.
Protocol 03
External RAM
Distracting thought? Don't track it. Write it on a sticky note and park it. Return to mission.
Protocol 04
System Reboot
Total focus freeze? Physical reset: Stand up, 10 jumping jacks, and drink 8oz of water.
Protocol 05
Signal Filter
Place your phone in "Faraday Cage" mode (another room or a locked drawer) until Mission Complete.
Protocol 06
Time Box
Estimate time needed. Double it. That's your realistic mission window. Plan accordingly.
Custom Command
Custom Command
Unit: Tactical Tools
Hardware: Ready
Facilitator Field Manual Facilitator Field Manual
Brain Blueprint Bootcamp Implementation Guide
Mission Philosophy
This bootcamp reframes executive functioning (EF) challenges as "system optimizations" rather than character flaws. For a 15-year-old, this tactical, high-tech aesthetic reduces the stigma of "organization" and focuses on the power of strategic control over one's own cognitive environment.
01
System Upgrade Workbook
Deployment: Use during the initial 1-on-1 session.
Key Focus: Honest self-assessment. Encourage the student to find "bugs" in their system without judgment. Focus heavily on the "Task Deconstruction" section for an actual upcoming project.
02
Brain Blueprint Infographic
Deployment: Print as a poster or keep as a desktop wallpaper.
Key Focus: Visual cues. This serves as the "External RAM" mentioned in the strategies. It should be placed in the student's primary workspace (e.g., above their desk).
03
Mission Status Log
Deployment: Weekly check-in tool.
Key Focus: Self-monitoring. Review this together at the start of each session. Celebrate "High Focus" days and treat "Low Focus" days as data points for strategy adjustment.
04
Tactical Task Cards
Deployment: Mobile reference tool.
Key Focus: Task initiation. These are designed to break the "freeze" of ADHD or EF procrastination. Have the student pick their "Top 3" cards to carry daily.
Questioning Framework
Instead of "Why are you messy?"
"What part of your physical cache is creating the most lag right now?"
Instead of "Why haven't you started?"
"Is there a protocol error in the initiation sequence? Let's try Card 01."
Field Manual // Rev 1.0 Authorization: Counselor Class 1
Ignition Protocol Worksheet Ignition Protocol
Overriding System Freeze // Task Initiation v2.1
Mission Timer
00:10:00
Diagnostic Report: The Freeze
The hardest part of any mission is the first 10 minutes. When your brain sees a "Big Task," it triggers a freeze response. This protocol is designed to bypass that error and force a system start.
01
Pre-Flight Check
Clear the friction points. If your environment is messy, your RAM is full.
Phone in "Off-Site" Storage
Hydration/Fuel Levels Checked
Chrome Tabs/Social Feed Closed
Audio Focus Protocol Active
02
The 5-Minute Force-Start
Don't try to finish the project. Just commit to 300 seconds of "Low Power" effort.
Define Your Minimal Entry Point
What is the absolute smallest first step? (e.g., "Open document and write title")
What is the "ugh" feeling telling you? Acknowledge it, then commit to ignore it for 5 mins.
03
Ignition
The "Just One" Rule
If you can't start the task, do ONE thing related to it. Momentum is more important than speed. If you still want to stop after 5 minutes, you can—but you probably won't.
Set Timer 05:00
Unit: Task Initiation
All Systems: Go // No Go? -> Go
