Flowchart explaining various stages of work in a project, including preparation, execution, and additional unforeseen tasks.

Abi Handley shared the above image on LinkedIn from a web developer who, back in 2022, worked out all of the time they spent on a project. Unsurprisingly, as anyone who has ever led a project will know, it’s the “work to do the work” which takes the most time.

When you’re younger, enthusiasm, energy and naivety tend to get you to the end of a project. When you’re in your forties, like me, it’s process. This post talks about running a ‘postmortem’ but we insist on pre-mortems as well as retrospectives. We minimise ‘status update’ meetings, using tools such as Trello to track task completion and Loom to explain things that would take too long via email.

Additionally, some people seem to think that being ‘professional’ means not bringing your emotions to work. But emotion is what makes us human, and so acknowledging this and factoring it into to projects is one of the keys to running them successfully.

I had been aware during the project that there seemed to be a lot of “extra work”, but putting it down on paper highlighted the multitude of “invisible” tasks and challenges which every web development project has.

There were two common threads:

  • much of the work was the “work to do the work” rather than the “actual” work
  • most of the work was under- or un-estimated because it wasn’t the “actual” work

Source: Dave Stewart