Fake Work
Fake Work
Fake work is any activity that looks like progress but does not produce anything real. I find it actively draining.
What fake work looks like
- Meetings about meetings
- Documents that exist to justify other documents
- Branding exercises with no delivery attached
- Long planning cycles with no shipping
- Reorganizations that rearrange the same problems
- Busywork that fills a calendar and moves no metric
It often looks busy. That is the trick. Output volume is not the same as outcome volume.
The test I use
Would anyone notice if this activity stopped? If the honest answer is no, it is fake work.
The second test: is there a shipped artifact at the end? If not, the activity is either reflection (fine) or theatre (not fine).
Why it frustrates me
Because I am execution-first and ROI-driven. Fake work wastes the two things I value most: time and momentum. It also corrodes morale. People know when they are doing fake work. Doing it for long makes them weaker, not stronger.
Where it creeps in
- Agencies that sell process instead of outcomes
- Startups stuck in endless planning
- Design communities optimizing for craft portfolios
- Teams that confuse activity with progress
I am careful to keep Duodode on the other side of this line. The agency sells outcomes, not motion.
How it connects
Fake work is the functional cousin of Fluff and Performative Business Talk. It is the opposite of Build and Ship. See also Low-Value Activity.
Related
Fluff · Performative Business Talk · Low-Value Activity · Execution Over Talk · Build and Ship