Don’t create a sense of urgency, foster a sense of purpose.
Kimber Lockhart
3K129

I agree with foster a sense of purpose over creating a sense of urgency, although the example of what it can achieve seems little one sided. Why does having a sense of purpose mean I have to stay late to make a change that will make things easier for a potential customer, or do a couple of iterations over the weekend? Surely we need to do things between 9–5 with a sense of purpose too.

A sense of purpose can take many guises that do not necessarily require you working more hours, i.e.

  • taking ownership of a task or issue and seeing it through to resolution
  • assisting a colleague become more familiar with the code base / systems allowing them to progress their understanding and to get more involved.
  • putting forward your case for or against a change, feature or new idea.

I see the latter as quite important as I will always argue for what I feel is best for the project (and I expect my colleagues to do the same from their positions) and if I ever stop doing that then I will have lost my sense of purpose and it’s probably time to move on.

A single golf clap? Or a long standing ovation?

By clapping more or less, you can signal to us which stories really stand out.