Time and estimates  ·  3 min read

Most tasks work best at half a day to three days. That is small enough to estimate well, finish this week, and review in one sitting. Bigger than a week, split it. Smaller than an hour, it is probably a checklist item inside a bigger task.

A three-task PERT estimate with expected values and rangesBest / likely / worst, in daysResearch 2 / 3 / 63.3 ± 0.7Design 3 / 5 / 95.3 ± 1.0Build 5 / 8 / 158.7 ± 1.7Project17.3 days, likely 15.3–19.4Expected = (best + 4 × likely + worst) ÷ 6.
Small enough to review. Big enough to matter.
1Time and estimates

Why size matters

Big tasks hide problems. A two-week task looks "in progress" for ten days. You find out it went the wrong way on day nine.

Big tasks are hard to review. A reviewer facing two weeks of work skims. Mistakes get through.

Big tasks are hard to estimate. Estimates for long, vague work are often wrong by half or more.

2Time and estimates

The sweet spot: half a day to three days

  • You can picture the whole thing.
  • It finishes before priorities change.
  • One review covers it.
  • If it goes wrong, you lose days, not weeks.
3Time and estimates

How to split big work

Split by deliverable. "Website" becomes homepage, pricing page, about page.

Split by stage. "Pricing page" becomes outline, draft, design, build.

Split by audience or case. "Help articles" becomes one per common question.

Split by risk. Do the uncertain part first, as its own task. "Test whether the import works with large files."

4Time and estimates

Example

Too big: "Launch the spring campaign" (3 weeks).

Split:

  1. Write the creative brief (0.5 day)
  2. Draft landing page copy (1 day)
  3. Design the landing page (2 days)
  4. Build and test the page (2 days)
  5. Write three emails (1.5 days)
  6. Make four social images (1 day)
  7. Set up tracking (0.5 day)

Each one can be reviewed against a clear brief.

5Time and estimates

When a task is too small

"Send the file to Sam" is a step, not a task. Group tiny steps into a checklist inside a bigger task. Otherwise your list fills with noise.

6Time and estimates

Each piece needs a done check

A small task without a done check is still vague. Add one line: "Done when the page works on Chrome, Safari and iPhone."

7Time and estimates

Estimate the pieces

The PERT calculator adds up best, likely and worst cases for each piece into an honest range.

8Time and estimates

Small tasks, quick reviews

In M-Tracker, each piece is a task with its own brief and done checks, under a project. Each one gets a first review when it is finished, so problems show up on day two, not week three. No screenshots and no activity tracking.

How M-Tracker helps

Where M-Tracker fits

M-Tracker gives every task a clear brief and every finished piece of work a first review, in plain words, before it reaches the manager. No screenshots, no scores.

Try M-Tracker free14-day trial. No credit card. No employee surveillance.

How a task moves through M-Tracker: brief, work, review, improve, then the manager1BriefResult, audience,must include, due.Files and linksattached.2WorkThe person does itand attaches whatthey made.3ReviewM-Tracker comparesthe work with thebrief. One plainparagraph.4ImproveThey fix what ismissing while it isfresh.5ManagerSees work thatalready passed itsown test.No screenshots. No scores. The person sees the review first.
FAQ

Questions people ask

What about research that cannot be split?

Timebox it: "Two days to find three options." The output is the three options.

Does this apply to agile teams?

Yes. Stories that fit in a few days flow better through a sprint.

Copyright © 2020 – 2026 M-Tracker. All Rights Reserved. Privacy Policy