Coming soonDainvo Productivity. Soon a full email client and productivity space, written in Go to stay light and fast.See what's coming →
Dainvo

Everyday planning

Make a backup plan for the obstacle you can already see

Prepare a practical backup plan for one likely obstacle: choose when to switch, test the alternative, and tell people what changes before you get stuck.

Dainvo EditorialOctober 24, 20264 min read

An illustrated map shows a golden detour branching around a wooded hill and rejoining a road beyond a roadworks barrier. Text: Have another way ready.

You've reserved Saturday morning to submit an application. The form needs a reference number from someone who hasn't replied. Your plan says "finish application," but it doesn't say what you'll do if the number is still missing.

A useful backup plan answers that specific question while you still have time to choose. It can be small: a different way to complete part of the work, an agreed change to the deadline, or a clear point at which you stop and contact someone.

In the public description of her October 23 Short, How to ADHD's Jessica McCabe discusses having your own way home from a party, so leaving needn't depend on another guest. ADHD coach Paula Engebretson explores anticipating obstacles in her public podcast summary about planning for what could go wrong. These are practical creator suggestions, not evidence that a particular planning method treats ADHD.

The ideas raise a useful everyday question: if one part of your plan falls through, is the alternative actually available?

Pick one obstacle you have reason to expect

Choose something concrete. A missing reply, unreliable connection or unavailable room gives you a condition you can check. "Everything might go wrong" doesn't tell you what to prepare.

Use evidence from this task or a similar attempt. Perhaps the person supplying the number usually replies within three working days, and you've allowed one. Perhaps the venue has already warned you that its Wi-Fi is unreliable.

Start with the obstacle that would prevent the useful result. You don't need a catalogue of every possible inconvenience. If you've spent longer imagining failures than preparing the work, narrow the exercise to one known dependency and return to the task.

Suppose you're running a small community workshop on using a website. The room's internet connection is uncertain. The useful result is that attendees understand the sequence and can try it later. A live demonstration is one way to achieve that result.

Check whether the fallback depends on the same thing

Opening the website on a second laptop won't solve a venue-wide internet outage. A recording stored only in the cloud may fail for the same reason.

For this workshop, locally saved screenshots could show the sequence without internet access. You could print a short handout if the session also needs to work without a screen. Choose what the audience can actually use, including any accessibility requirements.

There are still limits. Screenshots cannot reproduce hands-on practice, and a handout cannot replace every kind of demonstration. Decide what the fallback preserves and what it leaves out before promising that the session can continue unchanged.

Apply the same check elsewhere. If your backup reviewer is on the same leave dates as the first person, you still have a gap. If both copies of a document need the same account login, the second copy won't help when access is the problem.

Choose a clear point for switching

"I'll change plans if necessary" leaves the decision until you are already stuck. Write a condition you can observe and a next action you can take.

For example: "If the room's connection fails the test at 09:45, I'll use the downloaded screenshots for the 10:00 workshop."

That time is an example, not a standard buffer. Allow enough time for the particular switch. Printing material may need a decision the previous day; opening an already tested file may take a minute.

For the application, the condition could be: "If the reference number hasn't arrived by Thursday lunchtime, I'll ask the administrator whether I can submit the other sections first." That is a request to confirm an option. It doesn't assume that partial submission is allowed or that a deadline will move.

Keep the condition beside the task, meeting details or materials you'll use. Our meeting preparation checklist covers the broader final checks before a session.

Prepare only what makes the alternative usable

Turn the fallback into a short preparation task. Download the screenshots. Check that they open with Wi-Fi off. Put the contact number somewhere you can reach without the failing service.

A dry run can reveal a missing step: the file exists, but the font is too small for the room; the replacement person is available, but hasn't received the brief. Deal with the specific gap while there is time.

Set a limit on the preparation. A short workshop may justify a few clear screenshots. Producing a second complete course for a possible connection problem would create a much larger job.

If the fallback needs more time, money or help than you have, change the original plan. An alternative that requires an unavailable budget or someone else's unconfirmed agreement is still a proposal.

Tell people what changes

When a fallback affects someone else's expectations, explain it plainly. For the workshop: "The connection isn't reliable today, so I'll demonstrate from saved examples. We won't be able to practise on the live site together."

For a missed dependency, name the decision you need: "The reference number is still outstanding. Can I submit the completed sections now, or should we agree another date?"

Updating your own calendar doesn't change an agreement with another person. If the obstacle creates a wider deadline clash, use the approach in managing projects with competing deadlines to compare the work, available time and options.

Sometimes the right choice is to pause or cancel. Don't use a backup plan to conceal a missing essential requirement or commit to work you cannot deliver.

Leave yourself one usable note

For the next task with a predictable obstacle, write:

I want to complete: ___ The dependency I'm checking is: ___ If ___ happens by ___, I'll ___ Before then, I need to prepare or confirm: ___ The person who needs to know is: ___

After the attempt, keep the part that helped and remove unnecessary preparation. If the fallback keeps becoming the normal way you work, revise the main plan around what is actually available.

You can leave the rest of the day alone. One prepared alternative is enough for this experiment.

More Dainvo resources for choosing the right daily planning workflow.

Esc to close