Skip to content

Method notes · 1 min read

How we estimate a task in hours

Every task in our catalogue carries an hours figure. Here is how we set it, and what makes us change it.

Start from the file

Each catalogue task names what you receive: a board paper, a model, a dashboard. We estimate the work needed to produce that file.

Meetings, reviews and drafts count when they are part of producing it. They are listed in the estimate, so you can see them.

Break the task into steps

A pricing model has four steps: collect the inputs, build the structure, test it with your finance team and write the notes.

Each step gets its own hours. The task total is the sum, rounded to the quarter hour.

  • Collect inputs: 3.00 h
  • Build the model structure: 6.00 h
  • Test with the finance team: 2.00 h
  • Write the notes: 1.00 h
  • Task total: 12.00 h

Illustrative example. Not a client engagement.

Check the estimate against the log

Every hour we work is logged. When a task has run before, we compare its estimate with the hours the team logged.

If the log shows a task needs more or fewer hours, we change the catalogue figure for future clients.

What changes an estimate during the work

Missing data, a new question from the board or a step added after the start can push a task past its estimate.

We tell you when a task reaches 80% of its hours and again at 100%. Extra hours go ahead once you approve them in writing.

What is not in the estimate

Software time is not counted in your hours. The estimate covers the work of the people on your team.

Put the method to work.

We reply within one business day.