Say you need to reach a colleague, but you can’t get into your usual work account. You remember another way to send a message. Then you realize the contact details are stored inside that same account.
You have a second way to send the message. You still can’t reach the person. Both routes need something you can’t get at: their contact details.
That is a dependency. It is anything an activity needs in order to work. It might be a device, an account, a piece of information or another person’s help. You may barely notice it until it is gone.
You don’t need to watch every system you use. The useful question is where a break would cause a serious problem and leave you with no working alternative.
This module is for working adults looking at the everyday things their lives depend on, the ones they can realistically do something about.
What you’ll get from this module
In this module
By the end of this module, you’ll know which everyday dependencies deserve attention and how to plan a fallback: another way to manage if your usual route stops working. We’ll draw on research about the systems behind daily life, a design essay, accounts of maintenance and oversight, an outage report, and guidance on planning for interruptions. You’ll use these ideas to choose one situation from your own life and work through it. You’ll finish with a possible fallback or a clearly named gap, plus a reason to review your plan.
Ask Jing
Become a Jingius.
What sits behind a system that just works?
Design essay: technology that lets you focus on the task.
In 1991, Mark Weiser described a goal for computing: technology that fits into ordinary life without constantly asking for attention. He used reading as his example. You focus on the words, not on the paper carrying them.
That helps explain why tools that fade into the background are valuable. When you want to read a message or finish a task, the tool can help without becoming the thing you think about.
Why it matters: Weiser was making a case for how technology could fit into life. It is a useful starting point here. Technology in the background is a benefit. You can keep that convenience and still look closely at the few things whose loss would hurt.
Read the design essay on background computing.
Scholarly account: unnoticed by one person, maintained by another.
In 1999, Susan Leigh Star studied the systems that support everyday activity without needing to be rebuilt each time someone uses them. Think of plumbing, power lines or a shared filing system.
Star found that a system’s role depends on who you are and what you are doing. Something that quietly supports your work can be someone else’s whole job, or their daily headache. When it breaks, the support you rarely noticed suddenly becomes obvious.
Why it matters: This adds something to Weiser’s idea. A technology can disappear from your attention without disappearing from everyone’s. Your sense that a system “just works” may leave out the work that keeps it going.
Read the scholarly account of infrastructure.
Museum maintenance account: someone keeps the clock running.
A Science Museum account makes that difference concrete. In 2010, Alison Boyle reported that a member of the conservation staff wound the museum’s Wells clock by hand every day.
Visitors saw a working exhibit. Its keeper had a daily task. The clock’s age and familiarity did not mean it could be left alone. This report describes how that museum cared for the clock at the time.
Why it matters: The example also shows why people belong in the picture. What looks like a dependable device to its user may rely on someone else’s regular attention.
Read the museum’s account of winding the Wells clock.
Official oversight account: familiar systems still receive attention.
Maintenance is one kind of support. Oversight is another. The Federal Energy Regulatory Commission, a United States government body, says it approves and enforces mandatory reliability standards for the country’s main power grid.
Its undated explainer covers that grid and the commission’s role. It does not describe every local electricity service, or how other countries arrange things.
Electricity may need little of your daily attention while an institution gives it organized attention every day. These are two views of the same familiar service.
Why it matters: That oversight is no guarantee that your own supply will never go off. Knowing what the support covers, and what it doesn’t, shows you what may be left for you to handle.
Read the official electricity-reliability explainer.
Operator’s incident report: the tools needed for recovery also failed.
Facebook’s account of its outage on October 4, 2021 describes a maintenance command that cut off its backbone, the main network linking its data centers. That took down DNS, the system that turns internet names into addresses. The loss of DNS also broke the company’s own tools for investigating and fixing problems.
In the company’s own account, the tools it normally used to find and fix trouble depended on the part of the system that had gone down.
Why it matters: This shows why a second route may not be a usable backup. It can look separate while still needing the thing that failed. The made-up contact problem at the start has the same shape: another messaging route is no help if the contact details sit in the locked account.
Read the operator’s account of the October 4 outage.
Practitioner guidance: start with what needs to keep happening.
In 2010, Marianne Swanson and colleagues wrote a guide for the National Institute of Standards and Technology, a United States government agency. It explains how federal organizations should plan for interruptions to their information systems.
The guide starts with the activities a system supports and asks what would happen if the system stopped. How long can each activity wait? What does it need? What should come back first?
That order gives planning a purpose. A list of equipment tells you what you have. Linking each item to an activity, and to what happens if that activity stops, tells you what needs attention first.
The guide also describes talk-through exercises, where people discuss how they would respond to a situation, and writing down lessons to improve the plan. It calls for a review on a set schedule, or whenever something important changes.
Why it matters: These are practices for large organizations. The questions that carry over to this module are simpler: what needs to keep happening, what does it depend on, and would your planned response still work during the interruption?
Read the federal information-systems contingency guide.
What this means for you
Start with one thing you need to do. Look at what makes it possible. Then decide whether a gap in your backup matters enough to fix. You don’t need to turn every convenience into a project.
Look beyond the tool you normally notice
Name the activity in everyday words: reaching someone, getting to essential records, making a payment or finishing important work. Then ask what you need to do it.
Your first answer might be a device or a service. Look one step further. You may also need an account, an internet connection, a particular piece of information or help from someone else.
In the made-up contact problem, sending a message needs both a way to send it and the colleague’s details. Checking only the messaging service misses the information you need to use it.
Include the support you already get. The clock and the electricity accounts show that someone else may be keeping a familiar system working. Ask who provides that help, what it covers and what would happen if it changed.
Decide whether an interruption would leave you stuck
Choose one believable problem, such as losing access to an account or a support arrangement ending. Describe what you couldn’t do, and how long you could manage before the cost became too much.
Your real obligation sets how much time you have. If reaching your colleague can wait until your account is back, the interruption may be manageable. If you must reach them before then, you need another way.
Now look at your alternative. Is it there when you would need it? Do you know it works? Or does it need the same account, information or support that the interruption takes away?
Give the dependency attention when both of these hold. The cost would become too much before you could reasonably find another way to manage. And your alternative is missing, uncertain or depends on the same thing that could fail.
This brings the two questions together. How much would the interruption matter? Could you manage it? A serious cost matters more when your supposed backup would leave you stuck too.
If the cost is small and you have a working alternative, you can leave the system in the background. If a serious problem is outside your control, find help you can actually reach, or write down what your plan cannot cover.
An alternative you can’t afford doesn’t make you careless. Knowing whom to contact, and what stays unresolved, may be the useful result. You don’t have to buy another device or service to finish this exercise.
Check whether the fallback would work in that situation
Go back to the locked-account example. Before choosing a fallback, check what each option would still need.
| Possible fallback in the made-up example | What still needs checking? | What the answer changes |
|---|---|---|
| Another messaging route, with the contact details only in the locked account | Can you reach the details without that account? | If not, this route won’t solve the problem. |
| The contact details you need, kept somewhere suitable that you can reach | Can you get to them, and use a contact route you’re allowed to use in this situation? | If both are available, walk through the steps. Otherwise, write down what is missing. |
| Help from someone responsible for support | Can you reach that person without the blocked route, and what can they help with? | Include the help they can give and write down what they cannot cover. |
Keep only the minimum information you need, in a suitable place. Never put passwords, recovery codes or private details you don’t need into this worksheet.
A fallback only helps with the situation it can handle. A route that works when one account is locked may still need your device or your connection. It may not help if you lose those instead.
Walk through the plan without breaking the working system
Start by talking or writing through what you would do. Find the information you need, explain the steps and note anything you cannot confirm.
Never deliberately disrupt medical, safety-critical, employer-controlled or other people’s systems for this exercise. Where a professional plan covers a critical dependency, follow that plan. Try a small, reversible step only when it is safe and you are allowed to.
For the contact example, find the details you need and explain how you would reach them without your usual account. You don’t need to lock yourself out to discover that your plan still relies on that account.
Leave uncertain steps marked as gaps. Then choose a realistic next action, such as finding out what an authorized support contact can do. Writing down what you don’t yet know is more useful than assuming the missing step will work.
Review when something relevant changes, then stop
Your fallback depends on the circumstances you checked. Look at it again after a relevant change in access, price, terms, responsibilities or support, or after an outage or a workaround that failed.
Set a reminder that suits you so you don’t forget the plan. If something important changes before then, review it sooner.
For the gap you’ve chosen, write down one useful next action, or say clearly what you cannot resolve. Start with the gap that matters most and that you can realistically fix. Then stop.
You can keep using the conveniences that help you. Minor dependencies you can manage don’t need the same attention.
How about your daily life?
Think about an ordinary day or an upcoming obligation. Where would losing access leave you unable to do something that matters?
You might need to reach someone, get to a work record or make a payment. You could also choose an activity that depends on someone else’s support.
Write down situations you’d like to understand better. One good idea is enough. Add more if they help you choose.
| A situation in my daily life | What I would like to understand or improve |
|---|---|
| ____________________ | ____________________ |
| ____________________ | ____________________ |
Which situation would be most useful to explore now?
My chosen situation: ____________________
Choose something you depend on in everyday life and can realistically do something about. You can change your choice. Carry this situation into the exercise below. Choosing it doesn’t yet mean you need to act.
Plan a workable fallback
Start with your chosen situation. If you came straight here, choose an important everyday activity and something it depends on that you can realistically do something about. Begin with a written plan or a talk-through before trying any step.
Never deliberately disrupt medical, safety-critical, employer-controlled or other people’s systems. Where a professional plan covers a critical dependency, follow that plan. Any step you try must be safe, allowed, reversible and low-stakes.
Never write down passwords, recovery codes or private details you don’t need. Keep only the minimum information, stored somewhere suitable.
- Name the activity and what it needs. Write what you need to do. Name the service or device you use, then look at the access, information, supporting systems or people it needs.
Activity and what it depends on: ____________________ - Describe one plausible interruption or change. Say what you couldn’t do, what it would cost you and how long you could manage before the cost became too much.
Situation, consequences and time available: ____________________ - Decide whether the gap needs attention. Both conditions must hold. The cost would become too much before you could reasonably find another way to manage. Your alternative is missing, uncertain or depends on the same thing that could fail.
If the cost is small and an alternative works, stop here. If an important answer is unknown, write down what you need to find out before you treat the alternative as workable. If the serious problem is outside your control, find help you can reach or write down what your plan cannot cover.
Reason to act, stop or seek information or help: ____________________ - Choose a fallback or source of help that fits the problem. Explain why it would still be there during the interruption. Include how you would reach the information or the help you need. Check what this option depends on. Don’t assume a second route would keep working.
Alternative and what it still needs: ____________________ - Walk through it. Find the information and explain the steps. Try only a safe, allowed, reversible, low-stakes step, without breaking the working system. Write down what you checked and what remains uncertain.
Checked steps and unresolved gaps: ____________________ - Choose one next action and a reason to review the plan. Start with the gap that matters most and that you can realistically fix. If no practical alternative exists, write down that limit. Set a reminder that suits you.
Review sooner after a relevant change in access, price, terms, responsibilities or support, or after an outage or a failed workaround. Then stop the exercise.
Next action or what remains unresolved: ____________________
Reminder and reason to review sooner: ____________________
Ask Jing
Become a Jingius.
Your next step
You have finished when you have a short record of what the activity needs and a reason to stop, take one practical action or seek the missing information. For a gap you choose to fix, keep the fallback, or its unresolved limit, and the reason to review it with that record.
A note on the evidence
These sources do different jobs. Research and design writing explain how systems can fade from attention. The documented accounts show maintenance, oversight and what can happen when tools depend on the same system. The planning guide gives practices from large organizations. The outage account comes from the company itself, and the clock report describes maintenance in 2010.
Apply the ideas to your own consequences and the support you have. Knowing that an institution oversees a system doesn’t tell you whether your personal fallback will work.
How we prepared this module
This module brings together research, design writing, museum and regulatory accounts, an outage report, and guidance on planning for interruptions. A made-up contact problem shows how two routes can depend on the same thing. The written exercise helps you look at one everyday situation.
Sources
- Mark Weiser. (September 1991). The Computer for the 21st Century. Scientific American, 265(3), 94–104. Original magazine scan; p.94, opening and paragraph beginning “Such a disappearance”.
- Susan Leigh Star. (November/December 1999). The Ethnography of Infrastructure. American Behavioral Scientist, 43(3), 377–391. Published article, UCI-hosted scan; “Defining Infrastructure,” p.380; “Transparency,” p.381; “Becomes visible upon breakdown,” p.382.
- Alison Boyle. (August 20, 2010). Winding The Wells. Science Museum. Historical maintenance account; paragraph beginning “The daily job”.
- Federal Energy Regulatory Commission (FERC). (Undated). Reliability Explainer. Official explanatory page; Introduction and “FERC’s Role in Electric Grid Reliability.”
- Facebook Engineering. (October 5, 2021). More details about the October 4 outage. Engineering at Meta. Operator’s incident account; paragraphs beginning “This was the source of yesterday’s outage” and “All of this happened very fast”.
- Marianne Swanson, Pauline Bowen, Amy Wohl Phillips, Dean Gallup and David Lynes. (May 2010, updated November 11, 2010). Contingency Planning Guide for Federal Information Systems. National Institute of Standards and Technology (NIST), Special Publication 800-34 Rev. 1. Sections 3.2, pp.15–16; 3.5, p.27; 3.5.3, p.29; 3.6, p.31.
