I Built Systems to Avoid Doing the Work
2 min read · May 10, 2026
TL;DR
An autoethnographic exploration of over-engineering, behavioral friction, and system design. This essay critiques the paradox of building hyper-optimized productivity systems that ultimately alienate the user from their core execution tasks.
For the last few months, I kept believing my problem was discipline.
So I did what felt productive:
I built systems.
I made Notion dashboards.
Habit trackers.
Daily operating systems.
Work logs.
Execution frameworks.
Everything looked organized.
But most days, I still wasn’t doing the actual work that mattered.
And I think I finally understood why.
The problem wasn’t laziness.
It was friction.
More specifically:
my systems still required me to think before starting.
/ /My Daily Schedule
Every task sounded abstract.
“Work on case study.”
“Do outreach.”
“Polish portfolio.”
None of those are actions.
They’re categories.
So instead of executing, I stayed stuck in loops of:
planning, optimizing, restructuring, and preparing.
Ironically, I was using systems to avoid uncertainty.
Because the real work
- reaching out to startups, doing UX audits, building proof publicly
- felt emotionally heavier than organizing my life.
There’s a certain comfort in refining systems.
You feel productive without risking failure.
But recently, I started simplifying everything.
Instead of:
“Do a UX audit”
I wrote:
Open one startup website
Find one UX issue
Write two lines
That tiny shift changed something.
Because momentum doesn’t come from motivation.
It comes from reducing the resistance to starting.
I also realized something else:
I kept drifting toward creative work whenever I avoided difficult work.
Editing videos.
Building visual identities.
Creative direction.
Designing systems.
I called it “soul work.”
And while it genuinely matters to me,
sometimes I was using it as an escape from the uncomfortable work that could actually change my future.
So now I’m trying to build differently.
Less optimization.
More execution.
Less “perfect workflow.”
More:
audits
outreach
case studies
shipping thoughts publicly
Hi I’m currently a 19-year-old BCOM. student from Calcutta trying to move toward product design, startups, & eventually an MS HCI path.
I don’t know exactly where this leads yet.
But I think documenting the process while becoming is more valuable than pretending to have figured it all out afterward.
So this is probably the beginning of that archive.
DHANYAWAD
- Arnav! ッ
ッ
Design isn't about Aesthetics, it's about Storytelling, evoking emotions and driving actions