What should you do when technology fails?

History is basically one long study in “technology fails, doctrine survives.” Armies that kept functioning when the shiny tools broke relied on redundancy and simple procedures. Romans used standardized signals and runners; Napoleon’s staff system could pass written orders quickly; in WWII, when radios were jammed or damaged, units fell back to pre-briefed plans, phase lines, and messengers. Cold War doctrine hammered this: assume comms degradation and keep operating.

For everyday life, the transferable lessons are: 1) define a simple plan before you need it (meeting points, check-in times), 2) keep a written “commander’s intent” for your household (what matters most: safety, regroup, conserve), and 3) practice small drills (once a month: no phone navigation on a familiar route; one evening: run on lanterns only). Technology is great, but procedure is what keeps you calm.

Sources worth reading for mindset: US Army FM 3-0 (operations) for the concept of mission command; WWII accounts like Cornelius Ryan’s works for how plans and initiative mattered when things went sideways; and basic civil defense-era guidance on redundancy and continuity.

If you want practical backups without going full bunker, focus on small, high-ROI items:

- Power: a quality power bank (10–20k mAh) + short cables + a car charger. If you’re in storm country, a compact USB-C PD bank is a lifesaver.

- Light: headlamp beats flashlight. Keep one in the car and one at home with spare batteries (or rechargeable with a known charging routine).

- Navigation: paper map of your area + a simple compass. You don’t need to be an orienteer—just “north, major roads, landmarks.”

- Comms: a cheap battery AM/FM/weather radio can be more useful than people think during outages. If you’re coordinating with family, agree on a “text first, then call” rule since texts often go through easier.

- Carry: I’m a fan of a small “get-home” pouch in a backpack: water, snack, small notepad + pen, lighter, and a basic charging kit.

The key is not buying everything—pick a few items you’ll actually maintain. Gear that’s dead, empty, or buried in a closet is just expensive clutter.

In the service we were taught to expect comms to fail, plans to change, and batteries to die at the worst time. The fix wasn’t magic gear—it was habits.

My “normal life” version:

1) Stop, breathe, assess. Panic burns time.

2) Decide your immediate objective: get safe, get home, or get information.

3) Move to known points. If you’re driving and GPS dies, don’t improvise streets—get to a main road you recognize, then work from landmarks.

4) Use time windows. “If we’re separated, we meet at X by 1900, then Y by 2100.”

5) Write stuff down. Phones die; a pocket notebook doesn’t.

I’ve also learned that discipline beats motivation: recharge the power bank on a schedule (same day each week), keep the car above a certain fuel level, and store a headlamp where you can grab it in the dark.

People overthink this and buy gadgets to compensate for basic planning. If your entire life collapses because your phone battery dies, that’s not “technology failing,” that’s you failing to have a plan.

Priorities are simple: 1) safety, 2) information, 3) movement, 4) communication. But here’s the part everyone hates: you need pre-made decisions. Who do you contact? Where do you meet? What’s your route home without GPS? If you can’t answer those right now, no amount of “tactical” gear helps.

Also: stop treating the internet like a utility. Outages happen. Keep paper contacts, know two ways home, and have a flashlight that isn’t your phone. Basic adulting.

From a tech perspective, “failure” usually means loss of network, loss of positioning, or loss of power. The smart play is graceful degradation: keep a core capability alive when the fancy layer drops.

Examples:

- Navigation: offline maps (downloaded ahead of time) + paper map as the true last resort.

- Comms: assume voice calls fail before SMS; assume cellular fails before local mesh. Some people experiment with off-grid messaging devices, but for most folks, the best innovation is simply having multiple channels and a check-in plan.

- Power: diversify charging (wall, car, power bank). If you add solar, treat it as “nice to have,” not guaranteed.

The broader lesson from modern battlefields is that jamming and denial are normal. So in civilian terms: don’t put all your critical functions on one device, one app, or one battery.

Mechanized units assume stuff breaks constantly—tracks throw, sensors die, comms go out. Crews keep moving because they have immediate action drills and analog backups.

Translate that to daily life:

- Vehicle: keep your car in a “ready” baseline (fuel not near empty, a real spare if possible, tire pressure reasonable). When tech fails, the boring maintenance matters more than any screen.

- Route planning: like a driver in a convoy, know primary/alternate/contingency routes. Literally: two ways home, plus an “if bridges/traffic are bad” option.

- Paper copies: insurance/contact info written down. If your phone is dead, you still need numbers and details.

The most common failure isn’t EMP—it’s a dead battery, a cracked phone, or a car that wasn’t maintained.

At sea, you’re trained to expect system casualties: GPS glitches, radar issues, comms silence, power faults. Good watch teams revert to fundamentals—dead reckoning, visual bearings, logkeeping, and clear procedures.

For civilians, the “mariner mindset” is:

- Keep a log: even a small note of where you parked, last known direction, time, and key turns helps when you’re disoriented.

- Use environmental cues: sun position, major landmarks, and consistent reference points.

- Build redundancy: two independent ways to get information (radio + neighbor network, for example).

And most importantly: don’t wait until you’re stressed to learn basics. Practice when the consequences are low, like navigating a short trip without GPS and verifying with signs and landmarks.

Aviation trains for partial-panel flying: when instruments fail, you fly the airplane with what still works and you don’t chase broken indications. There’s a good everyday parallel.

When your tech fails:

- Don’t keep poking the device hoping it fixes itself while you drift into a worse situation (lost, low fuel, late).

- Stabilize first: pull over, find a safe spot, get oriented.

- Revert to basics: signs, highway numbers, physical maps, asking a person at a gas station.

Also: a printed list of key phone numbers and addresses is underrated. Pilots love checklists for a reason—memory is unreliable under stress.

From a training perspective, the best “what to do when technology fails” habit is building simple routines and stress tolerance. New recruits get taught to solve problems with limited tools and still communicate clearly.

A civilian checklist that works:

- Identify who depends on you and what “accountability” looks like (family check-in time, where to meet).

- Keep a minimal kit consistent: light, power, cash, and written contacts.

- Practice once in a while (even a short drill): run an errand without phone GPS, or turn your phone off for an evening and see what you actually miss.

If you’re worried about bigger emergencies, local community preparedness classes can be helpful—and they keep things grounded and safe.

The SF-ish answer isn’t secret gear, it’s priorities and simplicity. When tech fails, the first question is: do I need to stay put or move? Movement creates exposure; staying put can be safer if you’re already in a secure spot.

Practical baseline:

- Have a rally point plan with your people (two locations: primary and alternate).

- Keep a “get home” capability: shoes you can walk in, a little water, a small light, some cash, and a written address list.

- Learn basic navigation and observation: read terrain, know your area, pay attention to what you pass.

Also, don’t go playing commando during a storm or outage. If conditions are hazardous, the professional move is often to shelter, conserve, and coordinate.

Think in layers: immediate safety, short-term sustainment, then recovery.

When technology fails:

1) Make the situation safe: get out of traffic, avoid downed lines, don’t wander in the dark.

2) Stabilize basics: warmth, light, water, and information. A headlamp and a small radio cover a lot.

3) Communicate with a plan: preset check-in times and a meeting spot if messages don’t go through.

4) Navigate low-tech: keep a local paper map; learn major roads and landmarks; don’t be afraid to ask for directions.

5) Keep a small buffer: cash, fuel above a minimum, and a few shelf-stable meals.

If outages are frequent where you live, consider a simple home routine: charge banks, test lights monthly, and keep printed emergency contacts. Nothing extreme—just reliable.

One angle people miss: “technology fails” isn’t always accidental. It can be overload, cyber incidents, infrastructure fragility, or deliberate disruption. You don’t need to be paranoid, but you should assume partial outages will happen again.

Practical resilience is mostly social and informational:

- Know what sources you’ll trust when rumors fly (local emergency management channels, radio stations).

- Have a family communication protocol that doesn’t rely on a single platform.

- Keep key documents and contacts accessible offline.

And a caution: in outages, misinformation spikes fast. If you can’t verify something, treat it as unconfirmed and act conservatively—stay safe, conserve resources, and seek official guidance when available.

Engineers and logisticians live in the world of “the system is down, the mission continues.” The trick is reducing single points of failure.

Home and daily-life version:

- Power: have at least two independent ways to make light (headlamp + lantern) and charge a phone (bank + car). Label cables and keep them together.

- Water/food: not stockpiling, just a buffer. If the store POS systems go down, cash and a couple days of basics help.

- Mobility: keep a simple toolkit in the car and don’t run the fuel tank to fumes.

- Documentation: printed contacts, addresses, and a small list of account recovery steps stored safely offline.

Logistics is boring until it isn’t. A little organization prevents a lot of chaos.

I’m kind of new to this stuff, but I had GPS die on me once and it was embarrassing how lost I felt. Do you guys actually keep paper maps in the car, and where do you get ones that aren’t super outdated? Also, for a power bank, is 10,000 mAh enough for a couple days or should I go bigger?

I like the idea of a simple checklist. If anyone has a “minimum setup” list for a student budget, I’d appreciate it.

I’d frame it like a small-scale continuity plan: identify critical functions, define acceptable downtime, then add redundancy only where it matters.

For most people, critical functions are: (1) safety/shelter, (2) communication with family, (3) basic navigation/mobility, (4) access to money/identity, (5) credible information.

A clean approach:

- Pre-commit decisions (rally points, check-in schedule, who picks up who).

- Keep “offline state” tools (paper contacts, map, cash, a radio).

- Run a quarterly test: simulate a 6-hour phone outage and see what breaks in your routine.

This avoids the common trap: buying gear without validating the plan. A tiny tabletop exercise with your household is more valuable than a drawer of gadgets.

The robotics world has a concept that fits perfectly here: fail-safe and fail-operational behavior. When the high-end system can’t function, it should degrade to a simpler mode rather than stop entirely.

For personal tech:

- Set up offline capability intentionally (offline maps, downloaded docs, printed backups).

- Reduce dependency on single devices by splitting roles: one small flashlight instead of phone-only light, one paper map instead of phone-only navigation.

- Treat chargers/cables like “spares” in engineering—cheap to stock, expensive to lack.

Future tech will be more autonomous, but it will also be more complex. Your best hedge is keeping one layer of simple, manual capability that you can run without apps, accounts, or networks.