Productivity tools

What productivity calculators are actually for

Productivity software is a crowded room and most of it solves the wrong problem. A calendar app does not stop a meeting being a waste of time. A to-do list does not tell you whether your sprint is realistic. The tools in this category sit one step before the planning app: they take a small set of honest inputs and turn them into a number you can argue with. How much is this meeting actually costing the business. How many working hours are left until the deadline once you take out weekends, your booked holiday, and the bank holiday nobody remembered. Whether the team has any chance of finishing the work it just committed to.

Every tool here uses the same pattern: numbers in, decision out, workings shown. Nothing is uploaded, nothing is stored, and the team on the other side of the meeting room does not need to know you used it.

Where the inputs come from

The quality of the answer depends entirely on the quality of the numbers you feed in. For the Meeting Cost Calculator, use fully loaded salary figures, not gross pay. A salary of 50,000 typically costs the employer somewhere between 65,000 and 80,000 once employer National Insurance, pension, software licences, desk costs, and benefits are layered in. If you are using the figure to push back on a recurring meeting, the loaded number is the honest one.

For sprint planning, the input that matters most is focus factor. Most teams overestimate it wildly. A senior engineer with line-management duties, on-call rotation, code review load, and a couple of hiring loops booked in is doing well to hit 50% on actual delivery work. Track a few sprints honestly before you trust the number you put in. The Sprint Capacity Planner will accept whatever you give it, but it cannot save you from optimism.

Deadline countdowns are the inverse: people overestimate how much time is left because they count calendar days, not working days. A six-week deadline announced in mid-December has substantially less working time in it than a six-week deadline announced in February. The Project Deadline Countdown Calculator strips out weekends, your non-working days, and any holidays you paste in, so the number on screen is the number you actually have.

Common mistakes

The first mistake is treating these as performance metrics. They are decision tools. A meeting cost ticker is not there to shame the participants, it is there to surface a question that nobody asks out loud: is this conversation worth the money it is burning. The point is the conversation that follows, not the number itself.

The second mistake is forgetting that focus time is not interchangeable with calendar time. Planning a Pomodoro session as if you have eight hours of clear runway, when in reality you have three hours of focus broken up by two standups and a one-to-one, will produce a plan that fails by mid-morning. Plan around the actual gaps, not the theoretical day.

The third mistake is rounding the wrong way. When you are estimating capacity, round person-days down and ceremony time up. When you are estimating cost, round salaries up and assumed productivity down. Optimism compounds quickly across a team of eight people and a six-week sprint, and the only place to absorb the slip is the bit at the end where everything was supposed to be tested.

More tools are on the way: a working-hours scheduler, a context-switch cost estimator, and a focus-block planner that respects existing meetings. If you only have time for one of these today, start with the Meeting Cost Calculator. It pays for itself in about ten minutes.