Here are the 5 things we do over 90 days:
We audit your daily layout to make the system useful and understandable. We remove everything unnecessary, focusing purely on the essential elements of your energy, focus, and baseline data.
We cut out the habits and dependencies that drain you. We do not compromise or manipulate the process with temporary fixes. The system is completely honest—we permanently close the doors so you never waste mental energy negotiating with yourself again.
We build your daily non-negotiables. We link your physical movement directly to your creative and strategic work so they stop fighting for your time. This structure is built to be aesthetic in its clarity, enduring, and long-lasting—never a short-term trend.
We isolate the gaps between tasks where procrastination happens. We build quiet, neutral, and unobtrusive environmental routines that shift your brain into deep focus instantly. The habits respect your environment and run automatically, regardless of your mood.
We run the routine until the new architecture becomes automatic, innovative, and irreversible. We set up your personal data dashboard to monitor your continuous throughput. You are left with a simple, functional structure that runs itself.
JONAS LARSSON // HUMAN OPERATING SYSTEMS
JONAS LARSSON // THE 3-MONTH BLUEPRINT
I only take on full-system projects.
Here are the five things we do over 90 days.
[01] READ THE CURRENT ARCHITECTURE
Before changing anything, we understand how your life currently operates.
We map energy, movement, attention, environment, obligations, transitions and recovery—not to judge or optimize, but to reveal what is already running.
Most people do not have a motivation problem. They have inherited architecture.
[02] REMOVE WHAT DOES NOT CARRY LOAD
We identify habits, commitments, ambitions, dependencies and environments that consume energy without creating meaningful output.
We remove.
Not because minimalism is the goal—but because unnecessary complexity makes good systems fragile.
[03] DESIGN THE LOAD-BEARING STRUCTURE
We define the smallest number of elements required to support the life you actually want.
Movement. Work. Recovery. Relationships. Creation.
The structure must survive ordinary weeks—not exceptional ones.
[04] TEST UNTIL IT STOPS REQUIRING WILLPOWER
Nothing is adopted because it sounds good.
We prototype. Adjust. Remove. Rebuild.
If the system depends on discipline, it is not finished.
[05] HAND OVER THE KEYS
At the end of 90 days, the goal is not improvement.
The goal is ownership.
You leave with:
Operating principles
Constraints
Baseline metrics
Maintenance rhythm
Architecture
No ongoing dependency.
No subscription.
No motivation.
A system designed to continue without me.
jonas larsson
how it works
I redesign and build human operating systems.
The work is architectural, not motivational.
I take on full-system engagements only.
01
WE READ WHAT IS ACTUALLY RUNNING
Not what you intend. What you do.
A normal week, examined without judgment.
This is the site analysis. Nothing gets designed until we know what the ground supports.
Good design makes a product useful. Good design makes a product understandable.
02
WE REMOVE WHAT BREAKS IT
Anything that repeatedly collapses the system is identified and removed.
No workarounds. No temporary fixes. Permanent decisions.
Good design is honest.
03
WE BUILD THE NON-NEGOTIABLES
A small set of daily actions that hold regardless of mood, energy, or circumstance.
Not goals. Load-bearing structure.
Built to last, not to impress.
Good design is long-lasting.
04
WE MAKE THE SYSTEM VISIBLE
The operating system gets a live dashboard.
Your data. Your architecture. Running from day one.
When you can see it, it exists differently than when it only lives in behavior.
Good design is aesthetic. Good design is thorough down to the last detail.
05
WE TEST IT UNDER PRESSURE
A system that only runs in optimal conditions is not architecture. It is decoration.
We introduce friction. We watch where it holds and where it doesn’t.
Then we reinforce.
Good design is thorough down to the last detail.
jonas larsson
how it works
I redesign and build human operating systems.
The work is architectural, not motivational.
I take on full-system engagements only.
01
READ THE CURRENT ARCHITECTURE
Before changing anything, we understand how your life currently works.
We map energy, movement, attention, environment, obligations and recovery. Not to judge, but to reveal what is running.
Most people do not have a motivation problem. They have inherited architecture.
02
REMOVE WHAT DOES NOT CARRY LOAD
We identify habits, commitments and dependencies that consume energy without producing output.
We remove.
Not because minimalism is the goal — but because unnecessary complexity makes good systems fragile.
03
DESIGN THE LOAD-BEARING STRUCTURE
We define the smallest number of elements required to support the life you actually want.
Movement. Work. Recovery. Relationships. Creation.
The structure must survive ordinary weeks — not exceptional ones.
04
TEST UNTIL IT STOPS REQUIRING WILLPOWER
Nothing is adopted because it sounds good.
We prototype. Adjust. Remove. Rebuild.
If the system depends on discipline, it is not finished.
05
BUILD THE DASHBOARD
The operating system gets a visual architecture — live, yours, running from day one.
Not a document you receive. A system you inhabit.
When you can see it, it exists differently than when it only lives in behavior.
jonas larsson
how it works
I redesign and build human operating systems.
The work is architectural, not motivational.
I take on full-system engagements only.
Five things. Ninety days.
01
THE ARCHITECTURE NOW
Before changing anything, we understand how your life currently operates.
We map energy, movement, attention, environment, obligations and recovery. Not to judge, but to reveal what is already running.
Most people do not have a motivation problem. They have a design problem.
02
WE REMOVE THINGS
We identify habits, commitments, ambitions, dependencies and environments that consume energy without creating meaningful output.
We remove it.
Unnecessary complexity makes good systems fragile.
03
WE BUILD
A small set of daily actions that hold regardless of mood, energy, or circumstance.
Movement. Work. Recovery. Relationships. Creation.
The structure must survive ordinary weeks, not exceptional ones.
04
WE TEST IT
A system that only runs in optimal conditions is not architecture. It is decoration.
We prototype. Adjust. Remove. Rebuild.
If the system depends on discipline, it is not working.
05
WE MAKE IT VISIBLE
The operating system gets a live dashboard.
Your data. Your architecture. Running from day one.
When you can see it, it exists.