Live data from Hacker News

The "Eisenhower matrix" productivity hack

bigthink.com

21–30 of 56 posts

Re: The "Eisenhower matrix" productivity hack

#22

This is not a productivity hack. It is how you're supposed to do things. Indeed, it is how most people on Earth accomplish every single task in their life whether they realize it or not. I wish I was morally bankrupt enough to be a productivity guru. I could, like, charge $50k to stand behind a podium in a hotel ballroom and spout nonsense at desperate people in an attempt to get them to buy my book and planners. It…

I could explain the basics of GTD to you in 30 seconds. It’s conceptually pretty easy. The idea of approaching it in a systematic, repeatable way is non-obvious, and I happily paid David Allen for his book to explain how to implement the simple ideas.

Re: The "Eisenhower matrix" productivity hack

#25
This seems like an out of context step in a multi-layered system.

Layer foo: Story arc. What story are you trying to tell when you get out of bed?

Layer bar: Things you have to do to make the story.

Layer baz: A weekly agenda which you execute on.

This is stupid simplistic. But the point is that different layers require different states of mind. As with writing and editing, you could do the first layer drunk, then the last layer sober.

Jumping straight to some list of things to act on doesn't work for me unless there is someone already taking care of the other layers. If all I have to do is walk in the office, look at the board, put the fries on the tray, and shout "order #23" then I'm good with that. Working from home, I have to do everything myself. The delegate box might as well be some goofy prize I get after I just do the thing myself.

Re: The "Eisenhower matrix" productivity hack

#26
I used to work for a Stephen Covey fan that had us think according to this quadrant. The main tension was between working ahead on important projects (doing quad 2 before it hits quad 1) without accidentally doing irrelevant quadrant 4 work instead. Staying in true quad 2 for most of the week was brain-burning.

It was fun to poke her about her quad 3 work becoming my quad 1. :) We were encouraged to help our managers prevent that from happening to us by building better systems (quad 2.) Low tolerance for recurring busywork.

Good lessons for this young employee from this framework being seriously applied in a team environment.

Re: The "Eisenhower matrix" productivity hack

#28
I think there are a few things to note to take the Eisenhower matrix from “oh, that’s a nice model” to really gain some serious value from it.

First of all, you need to really work with finding the most important goals for you in your context. Then you figure out what the most important things you could do to achieve this goal in for example the next two years.

Then you will realize you don’t have time to add these things on top of your current workload (like in Scrum, you don’t add new tasks to a sprint without removing other tasks). And when you’ve done that, it’s time to bring forth the Eisenhower matrix.

And in the light of what is truly important, sort your tasks according to the matrix. A key here is also to really think about the Important axis as not important in general but important that You do. Then your job is to delete or delegate enough to be able to fit the new tasks that are the most valuable to achieve your goal.

Also, in the article it says to do the non urgent important tasks after the urgent ones. I think this is really bad thinking. Instead, in the matrix you can see it tells you to plan these things. That’s what you should listen to. The things that are important but not urgent needs to be planned, otherwise they will never get done as there are always too much urgent things to do.

Re: The "Eisenhower matrix" productivity hack

#29
post #4

I’m to the point where if you can’t explain your point in a couple of paragraphs on a clickbaity title I’m gonna exit and then dismiss it as AI generated SEO slop and that’s what this feels like. Can anyone summarize?

Quoted: Here’s a breakdown: Do (urgent and important). Ng says these tasks are at the core of your job. They are the things you were hired to do and have an upcoming deadline attached to them. Make these your most important tasks. Decide (not urgent but important). These tasks are core to your job and goals, too, but their deadline is much further out. Decide if you have the time to advance them, but only after you’v…

As a software developer, I think I should be almost exclusively working in the top right (important, not urgent). If there is something I need to do urgently then I view this as someone (maybe me) screwing up.

It's also not obvious to me why "urgent, not important" gets handled any differently to "not urgent, not important", except that you have to be extra vigilant not to be distracted by the former.

Re: The "Eisenhower matrix" productivity hack

#30
I feel if there's more nuance on the urgency dimension than just "urgent" and "not urgent".

I judge problems in the urgency dimension by "what will happen if I don't do this?" Will my boss be angry at me? Will I get fired? Will there be fines (e.g. tax paid late)? Will a potentially incurable disease be detected too late if I delay this medical appointment? etc.

Two tasks due next week, one of which will officially miss a deadline but not much will happen if I do it a day later, vs. a tax deadline, I'd better work on the tax first, so if it happens that there isn't enough time to do both then at least I've done the one which would have the worst consequences for not doing it.

Post reply on HN