DEV Community

Ben Halpern
Ben Halpern

Posted on

Which unproductive activities are typically mistaken for productivity?

Latest comments (62)

Collapse
 
scrabill profile image
Shannon Crabill

To-do lists, to some degree.

I am a fan of bullet journaling. I also do not get how overly elaborate, Instagram-worthy to-do lists or notes help with productivity.

Collapse
 
marekgebka profile image
Marek Gebka

I think that sometimes people jump straight into creating a lot of pretty useless artefacts/documents like timetables and such. Also meetings, meetings, meetings.

Collapse
 
murkrage profile image
Mike Ekkel

Not taking frequent breaks to stand up. It took me quite some persuasion to get my boss to understand that me standing up to stretch and clear my head once an hour is actually improving my productivity! It helps me stay focussed throughout the day instead of hitting a wall at 2:30PM after which I just can't get anything done.

Collapse
 
danjconn profile image
Dan Conn

Good point! There is something to be said for doing things for the hell of it, only to find the hugely beneficial later.

Collapse
 
jmfayard profile image
Jean-Michel 🕵🏻‍♂️ Fayard

Trying to be productive instead of trying to be effective.
Learn the difference:
If you can resolve more jira tickets in a single day, you are being more productive.
If you learn to choose what are the right things to work on, that will have the biggest impact on your project, you are being effective.
It's mostly about getting into the habit of asking "why is this thing important?"

Collapse
 
mrcoro profile image
Aan Kunaifi

Reading just a documentation without implementing it, seriously even you read it day & night you still gonna forget everything #cmiiw

Collapse
 
sigje profile image
Jennifer Davis • Edited

Crunch weeks (longer than 40 hour work weeks) for many weeks. Check out this great presentation about the 8 productivity experiments you don't need to replicate slideshare.net/flowtown/rules-of-p... (not my presentation) Great visualizations, graphs you can share with your peers and management to show the loss of productivity. We've got over 100 years of experiments and we keep cycling through the cult of >40 hour work weeks for getting stuff done.

Collapse
 
deadcoder0904 profile image
Akshay Kadam (A2K)

Multi-tasking 🤷‍♂️

Focusing on only one task is the key. "The One Thing" is a good book that touches the topic :)

Collapse
 
aswathm78 profile image
Aswath KNM

emails, IM's

Collapse
 
6temes profile image
Daniel

Devops.

Collapse
 
victorjperez profile image
Victor Perez

I've found todo lists are an easy trap for time wasting. If you spend more time organizing your todo list than doing actual work, you're probably not using them effectively.

Collapse
 
peksapro profile image
Krzysztof Peksa

Multitasking.

Collapse
 
timoteoponce profile image
Timoteo Ponce

Refactoring code without a goal

Collapse
 
kspeakman profile image
Kasey Speakman

Packaging up code for reuse, when you don't have any current plans to reuse it. It takes effort to just solve your problem. But then it takes a separate effort to take that solution and package it for reuse. If the code never gets reused, then the latter is wasted effort.

Collapse
 
cmondorf profile image
Christian Mondorf

Tidying up. There's a productive and an unproductive way to do this.

This unproductive way consists in making piles and putting stuff out of sight, but not actually dealing with it.

The productive way is like a triage and results in throwing away and getting rid up a lot of unproductive stuff.

The difference is the second way unburdens your mind whereas the first just pushes the burden under the proverbial rug, but doesn't actually rid you of it.

Some comments may only be visible to logged-in visitors. Sign in to view all comments.