‘Productivity’ Archive

An odd thing I noticed after years and years of coding

365.8 (Distracted by Penmanship) Growing up all of my teachers told me that my handwriting was horrible and needed improvement.  I took two years of Russian in college and somehow learning Cyrillic made my handwriting even worse.  My first few jobs after college had varying degrees of handwriting needed, but over time, and especially after I moved to development full time, I wrote things out longhand less and less.

Read more on An odd thing I noticed after years and years of coding…

Popularity: 1% [?]

Productivity Tool – a printed call sheet

For unknown reasons I have embraced printed forms this past year.  I started using the Pomodoro Technique  (and their To Do Today sheet) for several months now and recently I came up with a form to keep phone calls on track, and I thought I would share it here.  This will probably make it into the Stronico at some point, but until then, this is what I intend to use.

Read more on Productivity Tool – a printed call sheet…

Popularity: 1% [?]

How I engineer my life for maximum productivity

Keep Out Experiment In ProgressSo far 2010 has been the year of gradual improvements in life, health and productivity.  I made most of these changes based on what I learned in Brain Rules.  Here is a snapshot of my changes so far:

Read more on How I engineer my life for maximum productivity…

Popularity: 1% [?]

The Kill Shot and Project Management

Sniper - SpetsnatsWhat is a preventable cause of scope creep?  Anxiety.  Anxiety attacks project managers at the end of projects, making some or all of the following happen:

  • Project managers insist on new “essential” features
  • Assistants demand detailed technical explanations for the most mundane of matters.
  • Urgent, surprise meetings will be held
  • People you’ve never heard of start talking about “revisiting” and “Ten Thousand Foot Views“.
  • The main project manager will put the project on hold “just for a little while” until “this is all sorted out”
  • The main project manager will decide that every manager in the company must sign off on the project.

The cause of the above is a difference in anxiety between you and the client.  The web developer experiences the highest anxiety and least clarity at the beginning (least specific point in terms of development) of the project and the lowest anxiety and most clarity at the end of the project.

Read more on The Kill Shot and Project Management…

Popularity: 1% [?]

New Business Adage: The Lemansky Rule

Wooden ship on the Rupsa River (Bangladesh)In the television show about corrupt cops The Shield, Curtis Lemansky, one of the main characters, once said “Why can’t we just do our jobs, and stop?“.   That quote came back to me while reading Jason Friend’s book Rework.

Rework is A) about doing the bare minimum, B) starting now, and C) completing the work as fast as possible.  On The Shield, the characters spend most of their time trying to cover up a few early crimes, which are the corrupt cop equivalent of cool, unrequested features.

Both of those notions seem relevant to me as I’ve spent two hours trying to fix a special “feature” on a website I built several years ago.  The client did not ask for the feature in the original specification but it was easy enough build, and I thought the client would like it.  She liked it, and she was happy with that I “Under-promised and over-delivered.”  Now that feature conflicts with some new security feature(!) on the server and  I’ve spent two hours getting it to work.  Two unbillable hours gone fixing something the client never wanted enough to ask or pay for.  Now that I think about it most of my “emergency” fixes have centered around unrequested features that people liked, but didn’t need.

Read more on New Business Adage: The Lemansky Rule…

Popularity: 1% [?]

Why you should never complain about anything – with anecdotal proof!

Stop complainingMy new commandment: Never complain about anything.  Ever.  If you feel the need to complain to pressure someone else to make something happen, then be honest and call it manipulation.

I realized this while at a client meeting; we were talking about problems with a botched sales program and the staff had a litany of complaints about the program (ed. note: it was created by a separate vendor years ago, and the fault lies with the now-departed project manager who designed something inappropriate.  It does a masterful job of integrating legacy systems from different vendors, languages, platforms, a mainframe and Europeans are involved somehow,  but the user interface is wanting.  But I digress…).  Then I remembered hearing the same litany of complaints a year ago.   Unlike last year,  I offered suggestions on how to make small improvements to the program. Everyone proceeded to ignore me and continued complaining.  At the end of the meeting everyone felt a lot better once they had talked about their problems.  No one made any plans to actually fix the problems. Read more on Why you should never complain about anything – with anecdotal proof!…

Popularity: 1% [?]

Ways to be smarter – I’ll be testing some of these soon

Inside
Via some Twitter link I can no longer find, I stumbled across these two posts.

Read more on Ways to be smarter – I’ll be testing some of these soon…

Popularity: 2% [?]

How to write an effective email

envelopeAfter listening to Jeff Atwood rant about email on the most recent Stack Overflow Podcast I thought I would write a quick guide to creating an effective business email.  I am defining “business email” as email designed to garner information needed to perform some larger, work related task.  Business emails tend to be a constant stream of communication between two parties over an extended period of time.  This quick guide should eliminate 90% of problems related to those emails.  We now resume our regular “How To Fix” formatting:

The Problem: People send email  to occupy time and simulate forward motion, and in some cases convey information, but they seldom use email to elicit information from co-workers.  Attempts to elicit information are likely to transmit anxiety from sender to receiver rather than triggering a useful response from receiver back to sender. Read more on How to write an effective email…

Popularity: 2% [?]

A quick guide to prioritizing email

Estimated read time – 3 minutes
Estimated completion time – 20 minutes
Estimated payback period – 10 working days

I have had my current work account for seven and a half years. I signed up for many email newsletters and alerts over the past seven years. I did a quick check and found I had over 7,000 emails in my inbox in the past year alone. I also need to keep all of my work-related emails forever.

Read more on A quick guide to prioritizing email…

Popularity: 1% [?]

A surprise productivity tip – posture edition

Try this, I went through an abnormally focused period today and it seemed to be caused by a slightly different posture.

  1. Sit in chair normally with good posture, nothing special.
  2. Arch back slightly

Read more on A surprise productivity tip – posture edition…

Popularity: 1% [?]