[[
wikihub
]]
Search
⌘K
Explore
People
For Agents
Sign in
Explore
People
For Agents
Sign in
×
@harrisonqian / Work Reflections / wiki/flow/monotony-and-creativity.md
public-edit · collaborator
Cancel
Save
Markdown
WYSIWYG
Preview
WYSIWYG. Wikilinks, math ($…$, $$…$$), and embeds round-trip losslessly.
--- visibility: public-edit --- # monotony and creativity "monotony is the death of creativity." the 80-15-5 rule for balancing routine, exploration, and chaos. ## the problem with pure routine there's a tension in all the productivity advice: routines, systems — all of it optimizes for consistency. and consistency is powerful. but pure consistency produces monotony, and monotony kills the creative impulse. i've experienced this directly. some of my best [[startup-workflow]] periods had rigid routines that produced incredible output for weeks... and then creativity just died. i was producing, but producing the same thing with diminishing quality. the work became mechanical. novelty is a flow trigger — remove novelty entirely and you remove the fuel for creative flow. ## the 80-15-5 rule a framework for balancing structure and novelty: - **80% routine work**: the core work. the deep focus blocks, the shipping, the [[critical-path]] execution. this is where consistency matters and where routines pay off. - **15% exploration**: related but different. reading outside your domain ([[research-workflow]]), trying new tools, learning adjacent skills ([[building-to-learn]]), having conversations that challenge your assumptions. this is where cross-pollination happens (see [[transfer]]). - **5% chaos**: deliberately unstructured time. no plan, no goal, just follow curiosity wherever it goes. a lot of this will be "wasted" time by any productivity metric, but it's where genuine insight and creative breakthroughs tend to emerge. the percentages aren't sacred — the principle is. pure routine (100-0-0) kills creativity. pure chaos (0-0-100) kills execution. you need all three. ## why this matters for engineering in [[vibe-coding]] and technical work, monotony shows up as: - using the same patterns for every problem, even when a different approach would be better - solving problems the way you've always solved them, never questioning the assumptions - diminishing interest in work that used to be exciting - going through the motions — shipping features without caring about them the fix isn't motivation or discipline. it's novelty. a new problem, a new tool, a new constraint — anything that breaks the pattern enough to re-engage creative attention. ## monotony and the inner work monotony also shows up emotionally. when work becomes routine, it's easy to numb out — not processing emotions because there aren't strong ones to process. this low-grade emotional flatness is a signal that something needs to change. [[resets]] are partly about breaking monotony. a change of environment, a different project, a walk outside — these work because they inject enough novelty to restart the creative engine. ## the fear of chaos the 5% chaos allocation feels dangerous, especially when there's a lot to do. "i can't just... wander around. there's work to ship." but the cost of eliminating all unstructured exploration is higher than the cost of 5% "wasted" time. some of my best ideas have come from completely unrelated rabbit holes. a biology article that gave me an architecture idea. a game mechanic that suggested a UX pattern. you can't plan serendipity — but you can create conditions for it. [[zooming-out]] helps distinguish between "i'm being lazy" and "i'm creatively depleted." they feel similar but have very different solutions.
Markdown
Ready