• 4 min read •By Tiago Marques

The Hidden Dangers of Productivity Hype

I recently stumbled on a YouTube channel promoting an elaborate Obsidian workflow—diagrams, taxonomies, nested templates—with a Patreon attached. My gut reaction was: this is overengineering. Not because the ideas are bad, but because it’s not always clear whether all that structure genuinely supports thinking or just creates the appearance of insight.

I say this as someone who lived that lifestyle. A decade ago I devoured every article on the Asian Efficiency blog, cycled through countless note-taking apps, installed every Pomodoro timer and distraction-free writing screen I could find. If there was a system that promised to optimize how I worked or thought, I tried it.

Structure is a tool, not a cage

I used Obsidian for years and built an extensive PARA-style system for almost everything: journaling, monthly self-reviews, tracking progress on personal projects, structuring my engineering work, even scripting music practice sessions. I wouldn’t start any task without a plan or attend a meeting without pre-structuring my thoughts. I was getting things done, but I wasn’t enjoying the process—and I began to question why.

I even built a personal dashboard that pulled data from my watch, my practice sessions, and my activity logs across work and side projects—a single pane of glass for my own productivity. It felt like the ultimate system. Then I added a metric based on total hours worked per week across everything: my job, side projects, and music development. I was averaging well over 70 hours. The WHO and ILO consider 55 hours per week a serious health hazard, linked to a 35% higher risk of stroke and 17% higher risk of heart disease. That number was the wake-up call I needed to stop living inside the cage I’d built for myself.

The irony wasn’t lost on me. The system I’d built to support thinking had quietly become a prerequisite for it. If the structure wasn’t there, neither was the thinking. In a way it short-circuited my ability to just sit, reflect, and explore ideas freely.

When the system becomes the driver

Over time I noticed something deeper: the more I structured my vault, the more I constrained my intuition and intrinsic motivation. What was meant to support reflection turned it into a prerequisite-driven process: a pipeline of templates and reviews that had to be “fed” before any real thought could happen.

That’s the risk I rarely see acknowledged in the productivity space. People talk about the benefits of structure endlessly, but almost nobody talks about what happens when the structure starts driving you instead of the other way around. I’m fairly certain I’m not the only one who ended up there.

The joy of forgetting

When I started taking notes more sparingly, something unexpected happened. The anxiety of losing ideas was replaced by the joy of rediscovering them. Not every thought deserves to be captured immediately. Some need time to mature, to be forgotten and remembered again, reshaped by whatever you’ve lived through since.

Letting go of compulsive capture helped me relearn how to remember. It made me less dogmatic in how I process information and more inclined to think through problems only when they’re genuinely ready to be worked through, not because a template demanded it.

There’s a name for this in psychology: incubation. Letting ideas rest before consciously revisiting them often leads to richer, more original thinking. The note-taking orthodoxy, with its emphasis on capturing everything immediately, can actively work against that process.

Scarcity isn’t what it used to be

There’s a broader context worth acknowledging. A decade ago, the value proposition of dense personal knowledge bases was obvious: information was scattered, retrieval was hard, and the person who had it written down won. That scarcity justified elaborate systems.

Today, that equation has shifted. LLMs and modern search have made retrieval near-trivial for most technical knowledge. Dense notes on APIs, frameworks, and configuration details are redundant. What retains value is insight, synthesis, and perspective: the things that come from thinking, not from filing.

A rigid vault optimized for information scarcity can actually become a liability in an era of information abundance. The hours spent maintaining it would be better spent developing the kind of judgment and creative thinking that no retrieval system can replicate.

Systems should serve thinking, not replace it

None of this is an argument against note-taking, it’s a tool I still use, just more selectively. The argument is against letting any system dictate the process of thought itself.

Use structure for what it genuinely supports: capturing fleeting ideas that would otherwise be lost, planning work that benefits from a checklist, logging progress that future-you will thank you for. But don’t let the system become so elaborate that maintaining it crowds out the unstructured reflection where real insight happens.

Overengineering productivity can undermine the very goals it’s meant to serve. That’s not a warning I read somewhere. It’s something I lived.

Tiago Marques
Written by

Tiago Marques

Principal Data Analytics Engineer specializing in cloud data platforms, Databricks, Kimball dimensional modeling, and reliable BI architectures.