Come on in
Loading image…

Life

The Great Office Productivity Scam

When an office worker invents a productivity system to impress his boss, the whole team becomes brilliantly efficient at looking busy—and accidentally discovers what getting work done really means.

HHarshit Shukla4 min read0 thoughts
Loading image…
Loading image…

The Great Office Productivity Scam

At 9:03 on Monday morning, Nikhil announced that he had discovered the future of work.

He announced this in the office WhatsApp group, where everyone was already online but nobody had yet begun working.

Nikhil: Team, I’ve developed a revolutionary productivity framework. It will transform how we work.

Priya: Will it fix the printer?

Nikhil: It is bigger than the printer.

Priya: Nothing is bigger than the printer. It has been broken since Diwali.

Nikhil ignored this. He had watched two motivational videos, read the title of a business book, and purchased a notebook with the word FOCUS embossed on the cover. In corporate terms, he was now a thought leader.

His boss, Mr. Bhatia, loved productivity. He loved it so much that he scheduled meetings to discuss why there was not enough time to do the work discussed in meetings.

When Nikhil presented his new system, Bhatia leaned forward.

“Tell me more.”

“It’s called the P.E.A.K. Method,” Nikhil said, writing on the whiteboard.

“Prioritise. Eliminate. Automate. Keep improving.”

There was a pause.

“What do we automate?” asked Priya.

“Everything repetitive.”

“Can we automate the meetings?”

Bhatia frowned. “Let’s not get carried away.”

Nikhil had expected questions. He had prepared a slide deck with seventeen slides, three pie charts, and a stock photograph of a mountain climber who looked deeply unhappy to be involved.

He explained that every employee would have a daily dashboard, hourly progress updates, colour-coded tasks, and a five-minute end-of-day reflection.

“Finally,” Bhatia said, “a culture of accountability.”

By Tuesday, the office had become a museum of productivity.

People walked quickly while holding notebooks. They typed furiously into blank documents. They scheduled meetings titled “Deep Work Alignment” and “Strategic Thinking Sync.” One employee spent forty minutes designing a dashboard to track how many minutes he spent updating the dashboard.

At 11:00, Nikhil sent a reminder:

P.E.A.K. check-in: Please update your progress status.

Priya replied with a green tick.

“What have you finished?” he asked.

“Updating my progress status.”

“Excellent momentum.”

By Wednesday, Bhatia was delighted. The dashboards showed that the team was 94% productive.

Nobody knew what the remaining 6% was, but everyone suspected it was the printer.

Then came the client presentation.

The client wanted a simple report that was already two weeks late. Unfortunately, the team had become so busy documenting its work that nobody had actually completed it.

Nikhil opened the dashboard. Every task was green.

He opened the shared folder. Every document was a draft.

He opened the report.

The first page said: Insert executive summary here.

The second page said: Chart to be added after data validation.

The third page was a photograph of the mountain climber.

For the first time in his professional life, Nikhil wished the mountain climber would come down and finish the report.

“Where is the final version?” Bhatia demanded.

Nikhil swallowed. “We have achieved excellent process visibility.”

“The client asked for a report, Nikhil. Not a documentary about the process of making a report.”

The team sat in silence.

Then Priya raised her hand.

“I have the original data. I can finish the report in two hours if everyone stops updating their dashboards and helps me.”

Bhatia looked as though she had suggested communicating by carrier pigeon.

“Can we do that?”

“Yes,” Priya said. “It’s called working.”

For the next two hours, something extraordinary happened. Nobody held a meeting about the work. Nobody changed a task colour. Nobody sent a motivational quote.

They checked the numbers, divided the sections, corrected mistakes, and asked each other actual questions. Nikhil discovered that Priya's spreadsheet was better than his entire framework. Another colleague caught a calculation error. Bhatia, after several uncomfortable minutes, called the client and negotiated an extra hour.

At 4:17 p.m., the report was sent.

The client replied: “Looks good. Thank you.”

Four words. No confetti. No certificate. No photograph of a mountain.

Nikhil stared at the email.

“That’s it?” he asked.

Priya nodded. “That’s generally how completing a task works.”

The next morning, Bhatia called an emergency meeting.

Nikhil arrived with his notebook, three pens, and the expression of a man preparing to defend a thesis.

“I’ve reviewed our approach,” Bhatia began. “We need fewer dashboards and more results.”

Everyone looked at him.

“Also,” he added, “the printer is working again.”

Nobody spoke. Some achievements are too large for applause.

Nikhil quietly crossed out P.E.A.K. Method 2.0 on his notebook.

He did not abandon organisation entirely. He kept a short task list, blocked time for difficult work, and asked for help before a small problem grew teeth. He even retained one dashboard, mostly because Priya said it was useful when it contained real information.

A month later, Bhatia asked him to explain the secret behind the team's improved performance.

Nikhil considered giving a speech about systems thinking, operational excellence, and the transformative power of colour-coded accountability.

Instead, he said, “We spend less time proving we're busy and more time doing the work.”

Bhatia nodded slowly.

“Excellent. Can you make a slide deck about that?”

Nikhil looked at Priya.

Priya looked at the printer.

The printer, wisely, remained silent.


The lesson

Being busy is not the same as being useful.

We can spend entire days organising our work, talking about our goals, tracking our progress, and polishing the appearance of productivity—without moving one meaningful step forward.

Good systems should make useful work easier, not become extra work themselves. Measure what matters. Keep the tools that help. Question the rituals that merely look impressive.

And if your productivity dashboard is more complete than the project it tracks, it may be time to close the dashboard.

Preferably before someone schedules a meeting to discuss it.

What’s the funniest example of “looking busy” you’ve seen? Share it in the comments—names may be changed to protect the innocent, and the printer.

Ask Claude or ChatGPT about this story
0 thoughts

A little conversation.

Be the first to leave a thought.

Visit the writer’s space
0 followers