Technicians: Do You Have Enough Time?

Technicians: Do You Have Enough Time?. Why do I think about this question? As a technician, I must handle many daily tasks, such as requirement reviews, sy。

分享
Technicians: Do You Have Enough Time?
Photo by Jon Tyson on Unsplash

Why do I think about this question? As a technician, I must handle many daily tasks, such as requirement reviews, system design, design reviews, coding, integration, testing, and delivery. I feel like there’s never enough time.

Then I learned about the Eisenhower Matrix:

  • Important and urgent tasks: Go Go Go
  • Important but not urgent tasks: Planning
  • Not important but urgent tasks: Delegation
  • Not important and not urgent tasks: Putting aside

While these categories make sense, they didn’t help much in practice; I still needed to think and experiment independently.

What is the core of this question? To complete my work, I need to organize where I spend my time, categorize it, and take action to optimize efficiency.

Where does the time go when completing work?

  1. Doing my tasks — using my own time.
  2. Requesting others’ collaboration — using their time.
  3. Others seek my collaboration — using my own time.

The second part involves asking others for help. The focus should be on improving time use in parts 1 and 3 to optimize efficiency.

What is the biggest enemy when using my own time? Interruptions. Handling messages, emails, and colleagues coming to discuss matters causes countless interruptions. This is the core reason for my inefficiency in using my own time.

How to improve efficiency?

Photo by Benjamin Davies on Unsplash

Turn off any IM and email tools and learn to say no

How do we improve efficiency when others use their time? Using my own time can be self-controlled. When others use their time, it requires our cooperation, which we sometimes can’t control. For example, if someone comes to your desk, you can’t just refuse them, right? So, what to do then?

Why can’t we refuse? High-priority tasks (related to our role and job content), such as online bugs, must be responded to. But for non-high-priority tasks, why should we prioritize others and inconvenience ourselves?

Therefore, cooperate with colleagues reasonably:

  1. High-priority responses (immediate handling)
  2. Low-priority callbacks (not handled in real-time, dealt with after finishing own tasks)
  3. Unreasonable requests: Say No (agreeing to unreasonable requests is self-inconveniencing)

Do you have enough time? Do you always respond immediately when someone comes to your desk? Do you often say no?

文章索引

阅读更多

那些意外变成特性的 Bug:当代码漏洞改写计算史

那些意外变成特性的 Bug:当代码漏洞改写计算史

那些意外变成特性的 Bug:当代码漏洞改写计算史. 比起草台班子将错就错的神话,面对异常数据时的观测定力才是真的 社交网络上常年流传着一类爽文:某家公司的程序员把代码写崩了,结果不仅没被开除,这个 Bug 反而成了拳头产品,妥妥的爽文主角剧本。 最常被搬出来的有三个:Audio Hijack 写错试用期拯救公。

By huizhou92