Question

To what degree do you care about your productivity?

I've been trying to understand how folks think about productivity; figured this would be the perfect group of people to ask.

I generally find myself caring about improving my productivity only when it comes to my core work; things I spend larger chunks of time doing. For me, that's primarily around dev work and email. I generally go for the most high-return fixes possible across two spectrums:

1/ Passive optimizations like learning keyboard shortcuts to navigate around in a code editor make me "feel" like I'm working faster, but realistically it's probably only saving me a few minutes per hour spent coding. It may not be a super tangible improvement, but it makes me feel faster.

2/ Direct improvements like spending two days figuring out continuous deployment consistently save me 15+ minutes every time I deploy new code for work. That's something I do at least once a day, every day. The return on time is super tangible and clear.

Would love to hear how you personally assess productivity and what things you do are top of mind when you consider making improvements.

Mentioned
#Alfred
Share
maguay's avatar
2 years ago

That division between passive optimizations and direct improvements feels like a great split.

For me, what you called passive optimizations are best at removing context switching. Keyboard shortcuts keep me from moving my hand to the mouse and finding a button I need. Tools like Alfred keep me from paging around to find the app I need. Text expanders, more than speeding up my typing per se, keep me from typing repetitive things that are annoying to keep entering, or help me remember things like HTML snippets that I'd otherwise forget. The danger is that you can go too far and essentially build a Rube Goldberg machine of little optimizations that take more time to figure out than they save.

Longterm, the biggest challenge to me is retraining myself what actual productivity is. At a certain level, replying to every email is being productive (say, when doing support for a new product). As the product matures and the volume increases, being productive is automating that (something that isn't worth the effort at smaller volumes). Then ideally as the company and team grows, your role changes and perhaps now being productive would mean answering no emails and instead focusing on broader team goals. That to me is the hardest thing to get right, to get myself to switch away from busywork that feels productive and then instead to focus on what's most impactful at the moment.

7 points
udara's avatar
@udara (replying to @maguay )
2 years ago

Thanks for the very thoughtful response!

I love the thinking around passive optimizations as short-term and direct improvements as long-term. That makes a lot of sense; when you're in a crunch the passive optimizations help you get through what's at hand, while the direct improvements are what come down the line once you qualify certain tasks as too repetitive and automate them.

4 points
osbennn's avatar
2 years ago

I feel the need to disambiguate here.

  • There's Productivity in its true, perfect form. It's an elusive ideal to strive for, one that involves both quantity and quality – and aspects of quality that yield benefits we might not have thought of before or even ever be aware of.

  • And then there's #productivity, the over-obsession that people and organizational structures often have with measurable output. This type of productivity is easily confused with machine-like efficiency. Often somewhat disconnected from the things that truly matter, these "proxy metrics" usually favor quantity as opposed to quality. They are definitely useful to a degree, especially when it comes to pleasing stakeholders whose sentiment matters to me, but I personally find myself resisting them.

So when you ask "how you personally assess productivity," it's a moving target, one that definitely keeps me up at night. What am I optimizing for?

4 points
qthdh's avatar
2 years ago

So after spending ~5 years reading, watching, trying, talking, writing about productivity, I came to the conclusion that productivity isn't a goal, it's a byproduct. And the more you think about it the less you are actually living it.

Today, I think things like POMODORO, GTD, typing faster, {{insert another productivity keyword here}} are just shiny things to keep your mind away from the real stuff.

3 points
maguay's avatar
@maguay (replying to @qthdh )
2 years ago

"productivity isn't a goal, it's a byproduct." <- that's perfect, I may have to quote you on that.

1 point
robertohanas's avatar
@robertohanas (replying to @qthdh )
2 years ago

Could you expand on productivity being a byproduct?
Would love to understand better what you mean.

1 point
What are the best platforms for community management?

We have 15k newsletter subscribers, and have around ~2k of them in a Slack group. We're starting to encounter issues in terms of community management - specifically, it's hard to pin content like c...

Any suggestions for a workaround to an Outlook calendar not syncing with Google Calendars?

Google lets you subscribe to a calendar using a URL - although when using an Outlook 365 Calendar link, events are copied over once, and then the syncing stops. This seems to be a relatively new is...

What's the best video conferencing app for internal discussions?

Three major considerations I have been using to evaluate the plethora of options available: 1. Effortless/non-intrusive: It shouldn't feel like a video call 2. Price: As this app would be complime...

The community for Alfred  power users.