Hien Phan
Hien Phan
WorkAI craftWritingAbout
WorkAI craftWritingAbout

Apps

SpeakEn
Back to Writing

How I Stopped Being Busy and Started Building

This post details my struggle with 'fake productivity' – feeling busy but not productive – and how I implemented a ruthless prioritization framework to focus only on tasks that directly lead to shipping or revenue.

December 15, 2024•4 min read•Hien Phan
Indie Hacking
mvp
productivity
bootstrapped

Day 187: My 'Fake Productivity' Confession: How I Stopped Chasing Busywork and Started Shipping What Matters

My to-do list was a monster. It was overflowing, a chaotic mess of tasks that made me feel perpetually busy. But here's the kicker: being busy didn't mean I was actually making progress.

I was drowning in busywork. Things like tweaking website copy for the tenth time, organizing my digital files, or researching the "perfect" productivity app.

These felt productive, sure, but they weren't moving my solo SaaS projects any closer to shipping or generating revenue. This cycle led to burnout and stalled momentum.

A cluttered desk with a long to-do list and a stressed-looking person

The problem was clear: I was mistaking activity for accomplishment. I needed a way to cut through the noise and focus on what truly mattered.

The "Impact-Effort Matrix for Solopreneurs"

I developed a simplified prioritization framework, something I call the "Impact-Effort Matrix for Solopreneurs." It’s not fancy, but it’s incredibly effective for cutting out the fluff.

The core idea is to evaluate every potential task based on three key criteria:

  1. Customer Value: Does this directly improve the experience or solve a problem for my users?
  2. Revenue Generation: Will this directly lead to more sales or a higher customer lifetime value?
  3. Essential Learning: Is this task critical for validating a core assumption or learning something vital for the product's direction?

If a task doesn't strongly hit at least one of these, it's out.

How It Works in Practice

Let's break it down. Imagine you've a task like "design a new logo."

  • Customer Value: Does a new logo really improve the customer experience? Probably not significantly, unless the current one is actively harming it.
  • Revenue Generation: Will a new logo directly increase sales? Unlikely, unless it’s part of a major rebranding that’s already validated.
  • Essential Learning: Are you learning something crucial about your customer's needs by designing a new logo? Almost certainly not.

So, "design a new logo" would likely be a "ditch" task.

Now consider "implementing a key feature requested by multiple beta users."

  • Customer Value: High. It directly solves a problem for your users.
  • Revenue Generation: High. Happy users are more likely to pay and stay.
  • Essential Learning: Moderate. You learn if your implementation meets their needs.

This task passes the test with flying colors.

A simple 2x2 matrix showing Impact vs. Effort, with tasks categorized

I learned to be ruthless. If a task didn't directly contribute to shipping a feature, fixing a bug that impacts users, or generating revenue, it was relegated to the "someday/maybe" pile, or often, just deleted.

This meant saying no to things that felt good but didn't drive the business forward. It was tough at first, like breaking a habit.

Shipping What Matters

By adopting this framework, my focus shifted dramatically. My to-do list became shorter, but my actual output increased.

I started shipping features that users were asking for, which in turn led to more positive feedback and a clearer path to monetization. The constant feeling of being busy but unproductive vanished, replaced by a sense of genuine progress.

A person celebrating with a laptop, symbolizing successful shipping

The key takeaway here is simple: focus on impact, not just activity.

For you, this means asking yourself for every task: "Does this directly help me ship, or does it help me make money?" If the answer is no, find a way to cut it. Your time and energy are your most valuable assets as a solopreneur. Use them wisely to build products that matter.

Previous

My Failed Attempts at Automation (and What Finally Stuck)

Next

What I Learned from My First Sales Call

Hien Phan
Hien Phan

Full-stack engineer shipping production-grade web systems. Real apps, real stack.

Navigate

  • Work
  • Writing
  • About
  • Contact

Live apps

  • SpeakEn

Reach out

harrisonphan5@gmail.com

Saigon, Vietnam
Product-minded teams. AI-native product work welcome. Remote-friendly. Based in Vietnam (GMT+7).

© 2026 Hien Phan. All rights reserved.

Built with Next.js · TypeScript · SQLite · self-hosted KVM