That's good advice but to put it in practice, one would need to know how to "bucketify" your tasks. What are the buckets you use by default? Coding, email, meetings? Or identification, understanding, execution?
Hey Miko, I bucket based on big function and then small function within it. Email, conding and meeting are big functional bucket. Then within email bucket, i bucket by small function starting with identifying emails that need reply, just an fyi email, and spam. Then i go through each email in need reply bucket and send them out. This way i dont have to context switch between reading email that are in different buckets.
Yes, this is true. I think this is one of the reason why people feel so stressed and get little done in a day.
About listening to music while working though, I enjoy listening to music while working - while working on the stuff that is within my "flow state". If I`m working on something that's outside of my flow region - I prefer silence.
I`ll go one step further and say that the senior leadership rarely cares about doing the things right by the human nature (or psychology). Its all about efficiency - perceived efficiency not true efficiency.
Thanks, Bill for sharing that experience. I think music in the flow state prevents us from getting out of the flow state and helps minimize distraction. And to your point, music can be a distraction when you are trying to get into the flow state.
Also, I do agree about your point on perceived efficiency. I think it is because perceived efficiency can be easily measured with some metrics like the line of code written or the number of bugs fixed or the number of features shipped while completely ignoring the quality of work and time spent on it. That said, I also believe that we are the only ones who can help set the right metrics for measuring efficiency and move it from perceived to actual.
That's good advice but to put it in practice, one would need to know how to "bucketify" your tasks. What are the buckets you use by default? Coding, email, meetings? Or identification, understanding, execution?
Hey Miko, I bucket based on big function and then small function within it. Email, conding and meeting are big functional bucket. Then within email bucket, i bucket by small function starting with identifying emails that need reply, just an fyi email, and spam. Then i go through each email in need reply bucket and send them out. This way i dont have to context switch between reading email that are in different buckets.
How that helps
Interesting strategy. Thanks for sharing!
Yes, this is true. I think this is one of the reason why people feel so stressed and get little done in a day.
About listening to music while working though, I enjoy listening to music while working - while working on the stuff that is within my "flow state". If I`m working on something that's outside of my flow region - I prefer silence.
I`ll go one step further and say that the senior leadership rarely cares about doing the things right by the human nature (or psychology). Its all about efficiency - perceived efficiency not true efficiency.
Thanks, Bill for sharing that experience. I think music in the flow state prevents us from getting out of the flow state and helps minimize distraction. And to your point, music can be a distraction when you are trying to get into the flow state.
Also, I do agree about your point on perceived efficiency. I think it is because perceived efficiency can be easily measured with some metrics like the line of code written or the number of bugs fixed or the number of features shipped while completely ignoring the quality of work and time spent on it. That said, I also believe that we are the only ones who can help set the right metrics for measuring efficiency and move it from perceived to actual.