Here's a pattern I've seen in almost everyone I've coached: the harder someone works on their productivity system, the more susceptible they are to fake work.
Fake work looks legitimate. It's on your task list. It takes real effort. It fills a full day. You end the week feeling like you accomplished something.
It also never produces anything.
What Fake Work Actually Is
At Asian Efficiency, we define work simply: it's only real if it advances an outcome. Busyness isn't work. Motion isn't progress.
Fake work sits in a specific category that's easy to mistake for the real thing: it's backstage preparation that never graduates to front stage output.
The backstage/front stage distinction is useful here. Front stage is what you actually deliver — the article, the presentation, the shipped feature, the closed deal. It's what an audience or customer experiences. Backstage is everything that makes the front stage possible: research, planning, preparation, organization, practice.
Backstage work is real and necessary. But it's only real when it's in service of an actual front stage output.
Fake work is backstage that disconnects from front stage entirely. You're doing legitimate-looking tasks — organizing a project folder, reading industry articles, refining your workflow, updating your template library — but none of it connects to something you'll actually deliver. The prep loops. More research, more planning, more organizing. You're busy the whole time and nothing ships.
The treadmill analogy is fairly accurate: real energy expenditure, zero forward movement.
Why Productive People Are Most at Risk
This is the part that's easy to miss. Fake work doesn't happen because someone is lazy or unfocused. It tends to happen to people who are genuinely disciplined and organized — because those are exactly the people who have built sophisticated systems for managing and processing tasks.
The trap: when you have a well-organized task system, moving tasks around, updating project statuses, adding new items, and refining your workflow feels productive. It uses the same mental motions as real work. It gives you the same sense of accomplishment. It's just not connected to output.
The more your system resembles an actual working environment — task managers, project folders, Notion databases, elaborate filing structures — the easier it is to spend a full day working in the system instead of doing the thing the system was built to support.
One example: a client who had spent three weeks setting up the perfect content pipeline before writing a single piece of content. Beautiful system. Carefully organized. Zero output.
The Filter
The fix is a filter question, and you have to ask it regularly — ideally daily.
For every task you're about to work on: Is this helping me get to front stage, or is it just keeping me busy?
The answer isn't always obvious. Some backstage work is genuinely necessary and time-sensitive. Research that directly informs a decision you need to make today is real work. Research that's vaguely interesting but isn't connected to anything you're currently building is probably fake.
The key is the word connected. Can you trace a direct line from this task to a specific front-stage output that's actually happening in the near term? If yes, it's probably real. If the connection is vague, distant, or hypothetical — “I'll use this eventually” — it's likely fake.
A few specific versions of fake work to watch for:
Over-preparing. There's a version of every creative or professional task where preparation is legitimate. But there's also a version where more research, more planning, and more refinement becomes a way to avoid the fear of actually starting. One more article, one more template, one more draft. The output never comes because the preparation never ends.
System maintenance as the job. Your task manager is a tool to support the work, not the work itself. If you're spending significant time organizing, tagging, reorganizing, and maintaining your productivity system, the system has become the thing — not what it was built to support.
Meetings about the work. Discussing what you're going to do, planning how you'll approach it, checking in on progress — all of these have legitimate roles. They also can expand to fill the available time, particularly in teams, until the week is full of conversations about work and short on actual work.
Learning instead of doing. Reading, taking courses, watching tutorials — all valuable when connected to an immediate application. When it becomes a general activity disconnected from anything you're currently building, it's fake.
The Front Stage Check
The practical version of staying out of this trap: keep your front stage commitments visible and review them often.
What are you actually trying to ship this week? This month? What will exist in the world that doesn't exist now? Write those things down somewhere you see regularly.
Then, before you decide how to spend your time, look at that list. Ask whether what you're about to do connects to it.
This is a version of what AE calls “compass before clock” — direction before tasks. You need to stay connected to where you're trying to go or everything looks equally valid. When everything looks equally valid, fake work wins by default, because fake work is usually easier than real work.
The goal isn't to eliminate all backstage work. It's to keep the backstage in service of the front stage — and notice when it isn't.
One thing to try: Write down the three front-stage things you're committed to delivering this month. Then look at your task list. For each item, ask whether it connects to one of those three things. Anything that doesn't connect is a candidate for cutting or deferring.
