Archive for the 'Productivity' Category

A Common Mistake Company-Oriented Managers Do

I frequently hear this - “Fill up your time sheet before xxx date because it affects the company’s billing to the clients”. Now, this is fine, looking from the company’s perspective. However, even though all employees know what is good for the company will eventually trickle down as benefits for them, usually in the form of higher pay or bonus, it’s still not as enticing and you’ll find employees are not 100% motivated to fill in their time sheet. Weekly reminder emails will still need to be sent out.

Fact: people are an emotional and self-centered lot. Given a logical and emotional explanation, people tend to react more profoundly to an emotional one, especially if it is related to themselves. Managers should capitalize on this to get things done. Rather saying how filling up the time sheet will help the company’s billing, an emotional reasoning would be something along the lines of how time sheet can improve a consultant’s review and visibility, by tracking the amount of work done over time and by filling them up by xxx date is useful because you’d still remember it.

Gets exactly the same thing done, but I bet if you pitch it the latter, it’ll work better. Try it.

GTD by David Allen

Love it.

Need help focusing on work?

Here are 18 Ways to Stay Focused at Work. Simple and straightforward. One thing I’ve noticed though, a lot of these “how to”s really focus on IT oriented jobs, I mean it’s all about email, IM, listening to music (which assumes you’ll be sitting in front of a computer) and use shortcuts for frequently used programs. Is it because IT people tend to have problem focusing? Or is it because most jobs nowadays involve computers?

Something to think about.

Management issues in the IT

It seems that managing knowledge workers ain’t that easy. Problem is, managers still don’t see this. They think it’s a stroll in the park when it’s more like jungle tracking in the Amazon. Just after the post about pitfalls of technical leadership, an article titled How NOT to lead geeks came to my attention. Again, issues highlighted really do connect with me, and based on discussions among friends, they are a common problem. Of course, that’s not to say bad management is alien in other fields, but I think geeks are less forgiving when it comes to incompetency (sorry if I ruffle your feathers). Working with computers where precision, speed and correctness is the rule, we just can’t stand bad managers :).

Really.
On a more general note, I just remembered a Harvard Business school article I got from their newsletter, aptly titled Why Your Employees Are Losing Motivation that I’d love to share right now. It does hit all the nails on a more general note, listing out 3 key reasons (yes, just 3!) why people work. I’ll just quote the article:

  • Equity: To be respected and to be treated fairly in areas such as pay, benefits, and job security.
  • Achievement: To be proud of one’s job, accomplishments, and employer.
  • Camaraderie: To have good, productive relationships with fellow employees.

It goes on to elaborate that all 3 must be met. For example,

  • having only good relationship won’t keep your stomach full
  • getting well paid but doing work that does not give a sense of achievement guarantees high turnover
  • challenging work, excellent colleagues but no respect is also a sure way to lose an emplyee

It’s because managers fail to provide or underestimate the importance of these 3 factors that employees lose the drive to work, even quit. I’ll let you read the whole article for more info. Ironic how these problems looks so simple, yet the common manager hasn’t a clue about why the underlings leave.

Technical leadership pitfalls

Here’s a cheat list from InfoQ, which quotes an article from Hacknot, which was passed to me by a colleague a few days back. I’ve been meaning to post it here but it slipped my mind until I read it again today. It details an eerie similarity to real world scenarios I’ve come across.

  • Mistake #0: Assuming the team serves you
  • Mistake #1: Isolating yourself from the team
  • Mistake #2: Employing hokey motivation techniques
  • Mistake #3: Not providing technical direction and context
  • Mistake #4: Fulfilling your own needs via the team
  • Mistake #5: Focusing on your individual contribution
  • Mistake #6: Trying to be technically omniscient
  • Mistake #7: Failing to delegate effectively
  • Mistake #8: Being ignorant of your own shortcomings
  • Mistake #9: Failing to represent the best interests of your team
  • Mistake #10: Failing to anticipate
  • Mistake #11: Repeat mistakes others have already made
  • Mistake #12: Using the project to pursue your own technical interests
  • Mistake #13: Not maintaining technical involvement
  • Mistake #14: Playing the game rather than focusing on the target
  • Mistake #15: Avoiding conflict
  • Mistake #16: Putting the project before the people
  • Mistake #17: Expecting everyone to think and act like you
  • Mistake #18: Failing to demonstrate compassion

If you’re even remotely related to technical leadership, please, do yourself and your team a favour by reading through the article. Be warned, it’s long so make sure you have about 20 minutes to burn (read: do not start if you have work)

A sentence to sum up GTD

Jason Womack: The “writing it down-getting it done� link

“What if,� I started asking, “I could forget about something for now, and then be reminded of it when appropriate?�

Now that, is the ultimate goal of GTD (in my humber opinion) and why I use a PDA. Anytime anything pops up, I just right them down and set an alarm. Every few days, these short tasks and appointments get reviewed. Granted, this is a very over-simplification but it’s these basics that helped me so much.

Next Page »