OE1-4.4 Project & Time Management

What this is and why it exists

Two scheduling methods appear together in every syllabus and differ in one thing that matters. One assumes you know how long tasks take. The other admits you do not.

Choose by how novel the work is, and the choice becomes obvious rather than arbitrary.

The vocabulary

• Network diagram — a picture of tasks and the dependencies between them.
• CPM — the critical path method, which assumes known task durations.
• PERT — a variant using optimistic, most likely and pessimistic estimates for each task.
• Critical path — the longest path through the network, which sets the project duration.
• Float — how long a task can slip without delaying the project.
• Urgent — needing attention now.
• Important — contributing to something that matters.
• Time management matrix — sorting work by urgency against importance.
• Urgency addiction — treating urgency as if it were a measure of value.

The mental model

Start with the network, because both methods share it. List the tasks, and for each one say which tasks must finish before it can start. Draw that as a diagram and the structure becomes visible. Which work can run in parallel, and which is stuck behind something else.

The critical path is the longest chain through that network, and it is the concept to internalise. Its length is the shortest possible duration of the project. Every task on it delays the whole project if it slips, by exactly the amount it slips. Everything not on it has float, meaning it can slip by some amount and cost nothing.

That single idea changes how effort is allocated. Attention spent speeding up a task with two weeks of float buys nothing at all. The same attention on a critical task shortens the project. Drawing one network by hand is what makes this concrete, and it is worth the hour.

The two methods differ only in how durations are handled. The critical path method takes one number per task, which is fair when the work is familiar and has been done before. Construction of a known kind fits.

The other method takes three numbers: an optimistic case, a most likely case and a pessimistic one. From those it forms a weighted estimate and, more usefully, a measure of how uncertain each task is. That suits novel work where a single confident number would be a fiction.

Notice what the extra effort buys. Not a more accurate schedule, but an honest statement of how uncertain the schedule is. A project that finishes on the estimated date is unusual; a project whose uncertainty was understood is manageable.

The human aspects are what the network diagram does not show. They are the item most likely to be skipped and most likely to matter. People do the tasks. They are on more than one project, they leave, and they are unwell. They also tell you a task is on schedule until the week it is due. A schedule that assumes uniform availability is describing a project nobody is working on.

Then the same subject at personal scale, and the matrix here is the most portable idea in the topic.

Sort work along two axes: urgent or not, important or not. Four quadrants follow, and each behaves differently.

Urgent and important is crisis work. It has to be done, and a life spent entirely here is exhausting and reactive.

Important and not urgent is the quadrant that matters. Planning, prevention, learning, building relationships, maintaining things before they break. None of it announces itself, so it is the quadrant that gets squeezed out, and squeezing it out is what creates tomorrow's crises.

Urgent and not important is the trap. Interruptions, most notifications, other people's deadlines arriving as your emergencies. It feels productive because it is busy.

Neither urgent nor important is waste, and it is usually the quadrant people can already see.

Urgency addiction names the failure mode: treating how urgent something feels as a measure of how much it matters. Urgency is loud and importance is quiet, so the loud thing wins by default. Living entirely in the urgent quadrants produces the sensation of a full day and very little that lasts.

The honest limitation is worth stating with the technique. No system survives a genuinely overloaded week. If everything is urgent and important, the problem is the amount of committed work, and no matrix fixes that. It is a prioritisation tool, not a capacity tool, and mistaking one for the other is why people conclude that time management does not work.

What you should now be able to explain or do

Draw a network from tasks and dependencies. Identify the critical path and the float, and say where effort is worth spending. Choose between the two methods by how novel the work is, and say what the three-estimate version buys. Say what a schedule leaves out about people. Sort work into the four quadrants and name the failure mode and the technique's limitation.

Check yourself