keepcalculator

06 Numbers and Powers

Things That Must Happen: A Practical Checklist

Card No. 06·84088 · Updated · Standard formula, shown below

This article answers the question “Things that must happen?” directly: it depends entirely on the context, but in general, certain foundational steps are non-negotiable for any project, goal, or process to succeed. Whether you are planning a wedding, launching a product, or organizing a move, there is a core set of actions that must occur in order to avoid failure. Below, we break down what those universal requirements are, how to identify them for your specific situation, and how to ensure you don’t miss the critical ones.

What “Must Happen” Means in Different Contexts

The phrase “things that must happen” is vague on purpose; it’s a prompt for listing prerequisites. In project management, these are called critical success factors — the elements without which the project will fail. In everyday life, they are the non-negotiable steps you cannot skip. For example:

  • Planning a trip: you must book transportation, arrange accommodation, and ensure your passport is valid.
  • Starting a business: you must register the entity, open a bank account, and set up accounting.
  • Writing a book: you must outline, draft, revise, and edit — in that order.

The common thread is that these are necessary conditions, not optional extras. Identifying them early saves time and prevents last-minute crises.

How to Identify the Non-Negotiables

You can’t know what must happen unless you systematically break down your goal. A simple method is the reverse planning technique:

  1. Start with the end result — what does “done” look like?
  2. Work backward and list every step that logically precedes the final state.
  3. Ask “If I skip this, will the outcome still be acceptable?” If the answer is no, it’s a must.
  4. Order the steps by dependency — some things cannot happen before others.
  5. Assign a deadline to each must-do item.

For instance, if you’re baking a cake, you must preheat the oven before you put the batter in. That’s a dependency. If you skip it, the cake won’t bake properly. The same logic applies to nearly any multi-step process.

Common Mistakes When Listing “Musts”

People often confuse must-haves with nice-to-haves. A must-have is something that directly affects the outcome; a nice-to-have improves it but isn’t essential. For example, when planning a birthday party, a cake is a must-have if the tradition matters, but a specific flavor is a nice-to-have. Other common mistakes include:

  • Overlooking dependencies: You can’t send a newsletter before you have subscribers.
  • Ignoring external constraints: Permits, approvals, or other people’s schedules may be non-negotiable but outside your control.
  • Assuming linear progress: Some tasks can be done in parallel, but others require sequential completion.

A good rule of thumb: if a step is required by law, by physics, or by the definition of the outcome, it’s a must. Everything else is a preference.

Safety and Accuracy Considerations

For instance, in cooking, a food item must reach a safe internal temperature (e.g., 165°F / 74°C for poultry) — that’s a non-negotiable. In construction, a permit must be obtained before structural work begins. Always check official guidelines for any activity that involves health, safety, or legal compliance.

Alternatives to the Linear Task List

Not every set of “musts” is a simple checklist. Sometimes you have a critical path — a sequence of dependent tasks that determines the project’s duration. Other times, you have a decision tree where the next step depends on an outcome. For those cases, a simple division isn’t enough; you may need a Gantt chart or a project management tool. However, for most personal and small-team goals, a linear list with a pace calculation works surprisingly well. The key is to be honest about which tasks are truly mandatory and which are just desirable.

Frequently Asked Questions

What if I have more tasks than days?

For example, if you have 30 tasks and 3 days, you need 10 tasks per day — that’s likely impossible unless each task is very short. Prioritize ruthlessly and move optional items to a “later” list.

How do I know if a task is truly a “must”?

Ask yourself: “If I skip this, will the final result be unacceptable or impossible?” If yes, it’s a must. If the result would still be fine, it’s optional. You can also check for dependencies — if another task cannot start without it, it’s a must.

What’s the difference between a “must” and a “should”?

A “must” is a hard requirement — without it, the project fails. A “should” is a best practice or a quality improvement. For example, in a recipe, adding salt is a must for flavor, but garnishing with parsley is a should. The distinction is subjective but critical for prioritization.

How accurate is the “1 hour per task” assumption?

It’s a rough average. Some tasks take 10 minutes, others take 10 hours. For better accuracy, replace the “1” in the expression with your average task duration in hours.

What if my tasks are not independent?

If Task B can only start after Task A finishes, the simple division still works for pacing, but you must also account for the order. For dependent tasks, use a project management tool that shows the critical path, or manually sequence the tasks and then apply the pace calculation to each phase.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →