Say you need to get a work record, but you can’t get into the account you normally use. You think of another way in, then realise it needs that same account.
Another way in only helps if you can use it when the usual one isn’t working. Two routes can have different names yet need the same account, device or person. That shared need is a dependency.
This module is for working adults looking at important activities and the access they depend on, as far as they can tell today.
What you’ll get from this module
In this module
By the end of this module, you’ll know how to spot something that several important activities depend on. You’ll look at when to accept that dependence, change it or rely on help. We’ll link a planning guide for organisations, an investigation into a bank failure and studies of getting back into accounts. Then you’ll choose a situation from daily life, make a small written map, and write down one decision or a question you still need answered.
Ask Jing
Become a Jingius.
What shared dependencies can tell you
Official planning guidance: begin with the activity.
Marianne Swanson and colleagues’ 2010 guide for the National Institute of Standards and Technology explains how to plan for problems with U.S. government computer systems. Its look at disruption starts with the activities a system supports and what happens when they stop.
The guide then links those activities to what’s needed to get them going again, including people, equipment, data and records. This gives the list of equipment a purpose: it shows which activities would stop if that equipment stopped working.
Why it matters: The guide is written for organisations. You can use its order of questions to think about your own situation: what needs to happen, what does it rely on, and what would getting it going again need?
Read the federal information-systems contingency guide.
A regulator’s investigation: two names can share one system they need.
The Financial Conduct Authority’s 2014 investigation looked at a banking failure in June 2012. It found that NatWest and Ulster Bank shared a batch scheduler. This put risk in one place, alongside other problems, including poor testing.
A batch scheduler organises processing work. Because the two banks shared it, a problem with that software could affect both. RBS had a separate scheduler, though the systems still depended on each other. The three banks weren’t using one identical system.
This shows why two different names don’t prove separate support. What matters is whether they need the same thing to work. The shared scheduler played a part in this failure alongside other problems.
Why it matters: The response matters too. The banks paid back customers who were affected and brought in extra staff and resources to help put things right. An organisation can do some of the recovery work and carry some of the losses. That response in the past doesn’t promise what another organisation will do for you.
Read the regulator’s banking incident notice.
A long-term study: helpers need to be reachable when you need them.
Leona Lassak and colleagues’ 2024 study compared four ways to get back into a study account. People were given different methods and asked to get back in after 6, 12 or 18 months.
Of the 97 people whose results were analysed, 21 of 21 using email and 24 of 29 using helpers they had chosen got back in. Other groups used text messages or questions about personal details. People were asked to get back in for the study; these weren’t real lockouts. The authors expected the study accounts to matter fairly little to people. Most were younger and well educated.
Some people said they forgot whom they had chosen as helpers. Others said their helpers didn’t reply or couldn’t get into their own email. Naming a helper didn’t make sure that person could help when needed.
Why it matters: A back-up way in can depend on remembering whom to contact and being able to reach them. The study compared ways of getting back in; it didn’t single out the effect of having more separate arrangements in someone’s life. The practical lesson is to count the effort of keeping a back-up working when you decide whether it helps.
Read the long-term account-recovery comparison.
An expert review of services: help needs a route you can use.
Eva Gerlitz and colleagues’ 2023 study reviewed 78 services, using accounts the researchers set up. They tested getting back in as if the second sign-in check needed for an account wasn’t available.
Some services offered support only to people already signed in, or to users of certain paid products. Someone locked out of the account could therefore struggle to reach the help on offer.
The researchers used the accounts for a short time and left them mostly empty. They weren’t watching people who had really lost access. They generally used a browser and the same network address as when they set up, but reinstalled the browser before trying to get back in. Those conditions could affect the help on offer. The findings describe the services as they were reviewed, not every organisation’s support today.
Why it matters: Knowing that an organisation offers help is only part of the picture. You also need to know what help it gives and how to reach it when your usual way in isn’t working.
Read the expert review of account-recovery support.
What this means for you
You can use these ideas to look at a small part of your own arrangements. Start with something you need to do. Work out what it depends on before you decide whether to change anything.
Name activities before listing tools
Write down an activity such as delivering work, making an important payment or getting a record you need. Beside it, name what you need to do it. Include an account, device, person or organisation where it applies.
Next, ask what getting that activity going again would need if you lost your usual access. What you use every day and what you need to recover may be different. Knowing the first doesn’t tell you the second.
Write down only names and what depends on what; don’t include passwords or other secret details for getting in. If you can’t name a dependency, write “unknown.” This stops a missing answer looking like proof that nothing else is needed.
Look for the point shared by several activities
Compare the activities you’ve listed. Do any need the same account, device, person or organisation? Pick one shared need and ask what getting it back would take. Does that answer lead back to the thing that isn’t working?
Say delivering work and getting a record both need the same account. Another way to the record still needs that account. In this made-up example, the second route hasn’t removed the shared dependency.
Now ask what would stop and what could carry on. Sharing an account isn’t enough reason on its own to change your arrangements. What matters is whether you could live with the interruption and whether a change would be worth the effort.
Use information you can look at today to check one link you’re unsure of, or leave it as unknown. Following just one more link keeps the task manageable. Your map may still miss longer chains of dependence.
Compare the interruption with the demands of changing it
Accepting a shared dependency can be a choice you make on purpose. You may be able to live with the interruption you found, or find that another arrangement needs more looking after than you can keep up.
To cut a dependency, a change must let a particular activity carry on without the shared point. Name that activity and ask whether a change you could make would really do this. Then count the effort of keeping the change working.
The helper study makes that effort concrete: you have to remember whom you chose, reach them, and find them able to help. More back-ups don’t on their own mean better support. Compare the interruption you want to deal with against the work a change would bring.
If the result would be unacceptable but you can’t keep up a change, write down that limit. You can ask for a clear answer or specific help while admitting you don’t yet have a back-up that works.
Delegate a responsibility you can describe
You may already rely on an organisation to do the recovery. Be specific about that help. What will the organisation do? How could you reach it without your usual access? What delay or loss would you still face?
The banks’ response shows that organisations can take on recovery work. The review of services shows why you also need a way to contact them that works. Check both the responsibility and the route to help.
If you can’t choose your work arrangements or take on more ongoing tasks, a question for the organisation responsible may be the useful result. Relying on help that’s clearly defined, or accepting a limit, can be a reasonable choice too.
Finish with one choice or one honest question
You don’t need a map of everything to finish. One activity is enough to start, with up to three if they help show something they share. Write down one choice and its reason.
If something unknown stops you choosing, write the question and who could answer it. You’ve finished this small review by naming what you still need to know. You haven’t assumed the problem is solved.
Keep the map where you can look at it. You can come back to the row it affects when one of your arrangements changes, then stop, rather than turning the exercise into a list of everything.
How about your daily life?
Which important activity would you like to understand better? Think about delivering work, making a payment or getting a record. You might also choose something that relies on another person’s help.
Write one or more situations. One suitable idea is enough.
| A situation in my daily life | What I want to understand |
|---|---|
| ____________________ | ____________________ |
| ____________________ | ____________________ |
Which situation would be most useful to explore now?
My chosen situation: ____________________
You can change your choice. Carry it into the exercise below; choosing it doesn’t mean you must change your arrangements.
Map one shared dependency
Start with your chosen situation. If you came straight here, choose one important activity and the support it needs today. You may add up to two related activities, but one is enough.
Write only names and what depends on what. Don’t include passwords or other secret details for getting in. Use “unknown” when you can’t confirm an answer, and work from information you can look at today.
- Describe the activity and its support. Fill in one row for each activity you chose. Include what normal use needs, what getting it going again would need, and the interruption you would face.
| Important activity | What it normally needs | What restarting it needs | Other activities needing the same thing | What stops; what can continue | Known or unknown |
|---|---|---|---|---|---|
| ____________________ | ____________________ | ____________________ | ____________________ | ____________________ | ____________________ |
| Optional: __________ | ____________________ | ____________________ | ____________________ | ____________________ | ____________________ |
| Optional: __________ | ____________________ | ____________________ | ____________________ | ____________________ | ____________________ |
- Mark a shared requirement and follow it once. Circle something that more than one activity needs. For one circled item, ask what getting it back would need. Mark any answer that leads back to the thing that isn’t working. Check one link you’re unsure of using information you can reach, or leave it as unknown. If you can’t find a shared need, write down that limit instead of making one up.
Shared requirement, what it depends on, or unknown: ____________________ - Choose what follows. Look at what would stop and whether you could live with that interruption. Compare this with the effort a change would take and what you could really keep up.
| Choice | When it fits | What to record |
|---|---|---|
| Accept | You can live with the interruption, or maintaining a change isn’t worthwhile for you. | I accept this shared dependency because __________. |
| Reduce | You can’t accept the consequence, and a feasible change would let the activity continue without the shared point. You can maintain that change. | I will change the dependency between __________ and __________; maintaining this requires __________. |
| Delegate | A named institution is better placed to do a specific part of recovery. Confirm what it will do, how to reach it and what remains your responsibility. | I rely on __________ for __________; I can reach it through __________; I still carry __________. |
| Unresolved for now | You still don’t know what something depends on or who is responsible. | I need to ask __________ whether __________. |
If you can’t choose the arrangement or keep up more tasks, write down a question for whoever is responsible, or a limit you accept. You don’t have to create a back-up to finish the exercise.
- Keep the result and stop. Save your small map with the choice and reason, or the question still open and where an answer might come from. If you like, come back to the row it affects when an arrangement changes.
Ask Jing
Become a Jingius.
Your next step
You have finished when your record shows the activities you looked at and one choice made on purpose or one unknown you named. It needn’t describe every dependency in your life.
A note on the evidence
The guidance is for organisations; the failure is about one particular bank. The studies look at particular ways of getting back into accounts and how services are set up. They offer useful distinctions without giving you a personal chance of disruption or a benefit from adding back-ups that holds for everyone.
How we prepared this module
This module links planning guidance for organisations, a regulator’s investigation and research on getting back into accounts. Made-up examples about work and records show shared dependencies. The written exercise helps you look at one small part of your arrangements and write down a choice or something you still need to know.
Sources
- Swanson, M., Bowen, P., Phillips, A. W., Gallup, D., and Lynes, D. (2010). Contingency Planning Guide for Federal Information Systems. National Institute of Standards and Technology (NIST), Special Publication 800-34 Rev. 1, updated November 11, 2010. Section 3.2, pp.15–16.
- Financial Conduct Authority (FCA). (2014). Final notice: Royal Bank of Scotland Plc, National Westminster Bank Plc, Ulster Bank Ltd. Final notice. Sections 2.15–2.16, p.4; 4.24–4.25, pp.12–13.
- Lassak, L., Markert, P., Golla, M., Stobert, E., and Dürmuth, M. (2024). A Comparative Long-Term Study of Fallback Authentication Schemes. ACM CHI 2024, Article 970, pp.1–19. Author-hosted published conference PDF; sections 3.1, 3.3, 3.6 and 4.1, pp.5–8.
- Gerlitz, E., Häring, M., Mädler, C. T., Smith, M., and Tiefenau, C. (2023). Adventures in Recovery Land: Testing the Account Recovery of Popular Websites When the Second Factor is Lost. Nineteenth Symposium on Usable Privacy and Security, pp.227–243. Published proceedings; introduction, p.228; sections 5.3, p.236, and 5.7, pp.237–238.
