Listen to Direct Action Briefings on Spotify, Apple Podcasts, Amazon Music, or YouTube.

The network is down. The city still has to serve residents. The workaround cannot become the next system failure. 

That is the pressure.

Email is unavailable.

Online payments are unavailable.

Shared drives cannot be reached.

Resident service systems are down.

Departments cannot confirm application status, account balances, inspection history, service requests, previous communications, or normal transaction records.

Information technology and cybersecurity personnel are isolating systems and beginning recovery.

But residents are still arriving.

Phones are still ringing.

Deadlines are still approaching.

Time-sensitive services still exist.

Department heads want direction.

Elected officials want to know what remains available.

The public does not experience the incident as a network architecture problem.

The public experiences it as a city that suddenly cannot answer, confirm, process, schedule, receive, or explain.

That is where the operating pressure begins.

Someone proposes the obvious workaround:

Give every department paper forms.

Start spreadsheets on disconnected computers.

Write everything down.

Let staff accept transactions and enter them later.

Keep the counters moving.

It sounds practical.

It sounds responsive.

It may also create duplicate transactions, inconsistent verification, conflicting commitments, missing documentation, privacy exposure, unequal service, and weeks of reconciliation after the network returns.

The outage is the active problem.

The uncontrolled workaround can become the next one.

That is where Tactical Resolution fits.

Tactical Resolution is used when a problem has crossed the line from something that can wait into something that is actively interfering with the objective.

The city cannot postpone the outage.

The city also cannot restore every system immediately.

It needs a temporary stabilization move that protects essential service delivery without pretending every normal transaction can be completed safely outside the system.

The objective is not to recreate the entire city government on paper.

The objective is to keep the services that cannot wait moving through the narrowest responsible temporary path.

CISA warns that ransomware incidents can severely disrupt business processes and leave organizations without the data needed to operate and deliver mission-critical services. GAO has reported that state, local, tribal, and territorial organizations have been particularly targeted and that attacks can have devastating effects on vital government operations and services. NASCIO placed cybersecurity and risk management first among state chief information officers’ 2025 policy and technology priorities.  

This is not a distant technology issue.

It is an operating-control problem.

The city must stabilize the interference.

It must not overcorrect the system.

━━━━━━━━━━━━━━━━━━━━

The Leadership Trap

The leadership trap is treating continuity as permission to bypass every normal control.

That trap feels reasonable.

Residents are waiting.

Staff want to help.

Department heads want counters open.

Elected officials want the city to appear responsive.

Nobody wants to tell a resident that the system is unavailable and the transaction cannot be completed.

So leaders feel pressure to replace the unavailable system with human effort.

Take the payment.

Accept the application.

Schedule the inspection.

Record the service request.

Change the mailing address.

Promise the account adjustment.

Write down the details.

Enter everything when the system returns.

Keep moving.

The first problem is that not every service has the same risk.

Receiving a document is not the same as approving it.

Recording a request is not the same as completing it.

Taking a payment is not the same as confirming how that payment should be applied.

Accepting an application is not the same as verifying that the application is complete, timely, correctly associated with the property, or ready for review.

Scheduling an inspection is not the same as confirming the permit status, inspection sequence, prior correction, or inspector availability.

The second problem is that departments may create different workarounds.

Finance builds one spreadsheet.

Development services builds another.

Resident services starts a paper log.

Public works accepts requests through voicemail.

The clerk’s office stamps documents.

Utility billing writes account information on temporary forms.

Each department is trying to protect service.

But the city is no longer operating through one controlled record.

It is operating through multiple temporary realities.

That creates the leadership trap.

The city believes it is preserving service because activity continues.

But the actual operating record is beginning to split.

One resident receives a stamped receipt.

Another receives an email promise from a personal device.

Another is told to return later.

Another has information written on a loose form.

Another is entered into a department spreadsheet.

Another transaction is accepted without enough information to reconcile it correctly.

The counter looks active.

The city feels responsive.

The record is becoming less reliable by the hour.

Tactical Resolution does not tell the city to stop serving residents.

It tells the leader to contain the outage’s effect without allowing the temporary fix to spread beyond control.

A temporary workaround is still an operating decision.

It needs limits.

It needs ownership.

It needs communication.

It needs cleanup.

It needs a point where the city checks whether the workaround is still helping or has started creating more damage.

━━━━━━━━━━━━━━━━━━━━

What Usually Happens Under Pressure

The network interruption begins early in the morning.

Some employees cannot log in.

Others can log in but cannot reach shared systems.

Email becomes unreliable.

The payment portal stops responding.

Development services cannot access permit files.

Utility billing cannot see complete account histories.

Resident services cannot confirm the status of open requests.

The inspection team cannot pull normal schedules or previous notes.

The city clerk’s staff cannot access shared document folders.

Information technology tells departments to stop trying to reconnect until the incident is assessed.

That instruction is necessary.

It also leaves the operating departments exposed.

City hall is already open.

Residents begin arriving.

One resident says today is the last day to submit a document.

Another wants to prevent a utility interruption.

A contractor wants confirmation that a permit application was received.

A property owner wants to know whether an inspection is still scheduled.

A resident wants to report a road hazard.

Another wants to update account information.

Phones start filling with the same question:

What can the city still do?

The first report reaches senior leadership.

The network is down.

Information technology is working the problem.

No estimated restoration time is available.

The city manager asks department heads to identify essential services.

That is reasonable.

Then the improvisation begins.

A department director tells staff to start writing requests on paper.

Another creates a spreadsheet.

Another tells employees to use personal notebooks temporarily.

Someone prints blank copies of an old form.

Someone else tells residents that everything will be entered later.

A supervisor asks whether employees can use personal email accounts.

A department starts promising callbacks once the systems return.

The public information officer receives different descriptions from different departments.

One department says it is open.

Another says it is partially open.

Another says it is accepting documents but not processing them.

Another says staff can complete transactions manually.

Now the city has two active problems.

The network outage is disrupting service.

The response to the outage is beginning to fragment the service path.

That is the point where leadership has to intervene.

Not by shutting down everything.

Not by allowing everything.

By defining the minimum service continuity move that keeps essential work moving without creating an uncontrolled record the city cannot reliably rebuild.

━━━━━━━━━━━━━━━━━━━━

Field Note: Continuity Is Not the Same as Completion

A city can continue receiving residents without pretending it can complete every transaction.

That distinction matters.

During a network outage, leaders often combine three different actions:

Receiving information.

Verifying information.

Completing the transaction.

Those actions are not the same.

The city may still be able to receive a time-sensitive document.

It may not be able to confirm the resident’s full record.

It may be able to record that a service request was submitted.

It may not be able to promise when the request will be assigned.

It may be able to provide a controlled receipt.

It may not be able to confirm final posting, approval, balance, scheduling, or closure.

That is not poor service.

That is honest service under constraint.

The problem begins when staff are pressured to make the temporary process look identical to the normal process.

They cannot.

The normal process is unavailable.

The city needs a controlled continuity path, not a performance that suggests nothing has changed.

The field note is simple:

Stabilize the services that cannot wait. Hold the services that cannot be completed responsibly. Document the exception.

Do not promise completion when the city can only confirm receipt.

Do not accept information that cannot be protected or reconciled.

Do not create five temporary records for one city.

Do not let every department invent its own definition of essential service.

Do not allow the temporary workaround to continue unexamined because the counter appears to be moving.

The goal is not normal service.

The goal is controlled continuity.

━━━━━━━━━━━━━━━━━━━━

Scenario: The Assistant City Manager and the Paper Workaround That Started Spreading

Renee is the assistant city manager for a mid-sized city.

She oversees resident services, department coordination, continuity planning, and operational reporting to the city manager.

At 7:20 on a Tuesday morning, the chief information officer calls her.

The city has detected suspicious activity across several systems.

Information technology has isolated parts of the network while the cybersecurity team assesses the incident.

Employees are being told not to reconnect devices, use removable media, or create new digital workarounds without authorization.

Email is unavailable.

The online payment portal is unavailable.

Shared drives are inaccessible.

Utility billing cannot see complete customer records.

Development services cannot access permit documents.

Resident services cannot see open service requests.

Inspection staff cannot pull the normal schedule or previous inspection notes.

Public works dispatch can still receive calls, but it cannot enter requests into the normal system.

No reliable restoration time is available.

The city manager gives Renee a clear objective:

Keep essential resident services moving without interfering with the technical response or creating a second operational failure.

By 8:15, city hall is open.

Residents begin arriving.

At the utility counter, one resident says a payment must be made today.

At development services, a contractor says the submission date matters for a project schedule.

A resident calls about a fallen limb blocking part of a neighborhood road.

Another caller wants confirmation that an inspection is still happening.

A property owner wants to know whether the city received documents sent the previous afternoon.

A department head asks whether staff should accept every transaction manually and enter it later.

The pressure builds quickly.

Staff do not want to turn residents away.

Supervisors want to show initiative.

Department directors want to avoid a public backlog.

The public information officer needs one accurate statement for the city website, social channels, local media, elected officials, and the public call line.

Then Renee learns that several departments have already started improvising.

Utility billing has created a paper payment intake form.

Development services is stamping application packets.

Resident services has started a handwritten request log.

Public works is tracking calls on a spreadsheet stored on an isolated laptop.

One supervisor has told staff to take names and numbers on personal notepads.

Another has promised residents that all transactions will be completed once the system returns.

Everyone is trying to help.

The response is also beginning to spread.

Renee can see the next failure forming.

A resident could make a payment that staff cannot correctly associate with the account.

A permit packet could receive a date stamp without enough information to determine whether it was complete.

An inspection could be scheduled without visibility into permit status or previous corrections.

A resident service request could be captured twice through two departments.

Sensitive information could be written on unsecured paper.

Different residents could receive different treatment depending on which counter they reach.

Staff could make commitments that the city cannot verify after restoration.

When the systems return, departments could spend days trying to determine what was received, promised, processed, duplicated, or lost.

The obvious first instinct is to either stop every manual process or allow every department to continue.

Both choices are too broad.

Stopping everything protects the record but abandons time-sensitive resident needs.

Allowing everything protects visible activity but fractures control.

Renee needs a narrower move.

She brings the department heads together for a short operational call.

Information technology owns the technical response.

The operating departments will not create new digital systems or reconnect unauthorized equipment.

Renee’s responsibility is service continuity.

She sets the operating standard:

The city will establish one temporary service-continuity path for predefined, time-sensitive resident needs.

Departments may receive only the transactions specifically authorized through that path.

Receiving a request does not mean the city has completed, approved, posted, scheduled, or closed it.

Transactions that require unavailable records, verification, account history, approval authority, or protected system access remain paused.

Every accepted item goes into one controlled temporary record.

Every resident receives the same explanation of what the city has accepted and what it has not yet completed.

The city will issue one public service-status message.

Department directors will reassess the temporary process at defined intervals.

Cleanup and reconciliation ownership will be assigned before the first temporary transaction is accepted.

This is not a full solution.

The network is still down.

The city is still constrained.

Residents still cannot receive normal service.

But the interference is contained enough for essential work to continue without letting the workaround become a citywide free-for-all.

That is Tactical Resolution.

━━━━━━━━━━━━━━━━━━━━

The Problem Path

The active problem is the network outage.

But naming the outage is not enough.

Renee has to identify how the outage is interfering with the city’s objective.

The city’s objective is not simply to keep doors open.

The objective is to provide essential resident service with enough control that the work can be trusted, completed, and reconciled later.

The outage interferes with that objective by removing access to records, verification, communication, transaction history, scheduling, and normal documentation.

The weak problem path is broad improvisation.

A department sees a resident need.

Staff create a paper form.

Another department creates a separate log.

Another accepts information through voicemail.

Another starts making commitments that depend on records nobody can see.

The city appears to be moving.

The operating picture becomes less reliable.

The stronger path is narrow stabilization.

Identify which services truly cannot wait.

Separate receiving from completing.

Define which transactions can be accepted responsibly.

Pause the transactions that depend on unavailable information.

Use one controlled temporary record.

Explain the limits honestly.

Set the next review point.

Assign the cleanup before the backlog grows.

That does not restore the system.

It reduces the outage’s interference enough for the city to maintain essential service without creating unnecessary second- and third-order damage.

━━━━━━━━━━━━━━━━━━━━

The Blockage

The blockage is not only the unavailable technology.

The blockage is the city’s inability to verify and preserve one reliable operating record.

That distinction matters.

A city can lose network access and still retain leadership control.

It loses control when every department starts creating its own temporary truth.

The temporary records may all be created in good faith.

They may still conflict.

One department may define a document as received.

Another may define the same document as incomplete.

One employee may promise a future posting date.

Another may tell the resident the city cannot accept the transaction.

One staff member may collect extensive personal information.

Another may collect only a name and phone number.

One department may keep a clean log.

Another may rely on handwritten notes.

The blockage becomes fragmented control.

The city no longer has one answer to these questions:

What did we accept?

What did we promise?

What requires verification?

What remains paused?

Who owns the temporary item?

What will happen when the system returns?

What does the resident believe happened?

That is why simply telling people to use paper is not a Tactical Resolution.

Paper is a medium.

It is not a control.

The leader still has to decide what the temporary path is allowed to do, what it is not allowed to do, who owns it, and when it will be reviewed.

━━━━━━━━━━━━━━━━━━━━

The Decision Point

Renee has three possible reactions.

The first is to wait for information technology to restore the network before making an operating decision.

That is too slow.

The outage is already interfering with resident services.

The city has moved past the point where the issue can be postponed.

The second is to authorize a blanket manual workaround.

That is too broad.

It may keep visible activity moving, but it creates major risk across documentation, fairness, verification, privacy, commitments, and reconciliation.

The third is to stabilize the interference through a limited continuity path.

That is the Tactical Resolution move.

Renee does not claim that city services are normal.

She does not promise that every transaction can be completed.

She does not force staff to recreate unavailable systems through memory and paper.

She defines a narrow operating lane.

The lane exists for services where delay would create meaningful resident or city consequence.

The lane accepts only the information the city is authorized and prepared to control.

The lane gives residents a consistent explanation.

The lane documents every exception through one controlled record.

The lane has an owner.

The lane has limits.

The lane has a review point.

The lane has a cleanup requirement after restoration.

That is not the full Tactical Resolution process.

It is the correct leadership recognition.

The problem is active.

The city must act.

The action must remain controlled.

━━━━━━━━━━━━━━━━━━━━

The Next Movement

The next movement is not to hand every department a stack of paper.

It is to establish enough continuity to protect the services that cannot wait.

Renee directs each department to identify only the resident needs that would create meaningful harm, deadline exposure, public-safety consequence, or service failure if they were not received during the outage.

She separates services into three temporary categories.

The first category includes services the city can still receive and document responsibly.

The second includes services where the city can record the resident’s need but cannot complete the transaction until system access returns.

The third includes services that must remain paused because completion depends on unavailable records, protected information, account history, approval, or verification.

The categories do not replace normal policy.

They give the city a controlled way to describe its operating condition.

The public information officer issues one service-status message based on the same categories.

Department staff receive the same internal language.

Residents hear what the city can do, what it cannot do, and what the temporary receipt actually means.

Renee assigns a continuity owner for each participating department.

She also assigns a central reconciliation lead who will coordinate the temporary records after restoration.

The temporary process is reviewed at scheduled intervals.

If a new service becomes time-sensitive, leadership can decide whether it belongs inside the continuity lane.

If the workaround begins producing conflicting records, privacy concerns, inconsistent treatment, or unmanageable volume, the city narrows or pauses it.

The outage remains active.

But the city has stopped the workaround from spreading without control.

That is the next movement.

━━━━━━━━━━━━━━━━━━━━

Consequence Chain

If the city does nothing, the immediate consequence is service paralysis.

Residents cannot submit time-sensitive information.

Departments cannot record urgent needs consistently.

Phones continue filling.

Public frustration rises.

Elected officials receive complaints without a clear operating picture.

The second-order consequence is trust damage.

Residents do not know whether the city is unavailable, partially operating, or simply unable to explain what is happening.

Staff give different answers.

One department appears open while another appears closed.

The public begins making repeated calls because the first answer does not feel reliable.

But overcorrection creates a different consequence chain.

If the city authorizes broad manual processing, the immediate consequence is fragmented documentation.

Each department creates its own temporary record.

The second consequence is inconsistent service.

Residents receive different answers, requirements, receipts, and commitments.

The third consequence is reconciliation burden.

When systems return, staff must determine which transactions were valid, incomplete, duplicated, pending, or incorrectly promised.

The fourth consequence is operational rework.

Employees may need to contact residents again, reconstruct missing information, reverse incorrect entries, resolve duplicate requests, or explain why the temporary promise cannot be fulfilled.

The fifth consequence is accountability loss.

Leadership may not be able to reconstruct who accepted an item, what was communicated, what authority was used, or where the temporary record went.

The sixth consequence is public trust damage.

The city may restore the network but still face weeks of inconsistent service because the workaround damaged the record.

The temporary fix does not become dangerous because it is temporary.

It becomes dangerous when it is broad, unclear, unowned, or allowed to operate without review.

━━━━━━━━━━━━━━━━━━━━

Better Read

The better read is not:

“The network is down, so everything must stop.”

The better read is:

“The network is down, so we must identify which essential services can continue through a controlled temporary path.”

The better read is not:

“Everyone should use paper until the system returns.”

The better read is:

“Only specifically authorized transactions should enter the temporary path, and the city must define exactly what that path can and cannot complete.”

The better read is not:

“We will enter everything later.”

The better read is:

“Before accepting the transaction, we need to know how it will be controlled, owned, reconciled, and explained.”

The better read is not:

“Keep the counters moving.”

The better read is:

“Keep essential service moving without destroying the record required to finish the work.”

That is the shift.

Tactical Resolution is not about creating the fastest workaround.

It is about creating the minimum effective stabilization move that protects the current objective while controlling what the move could damage.

━━━━━━━━━━━━━━━━━━━━

How This Fits the Direct Action System

C S A helps Renee read the full operating field before choosing the response.

The issue is not only that the network is unavailable.

The full field includes resident needs, department capacity, time-sensitive services, public communication, privacy exposure, records control, verification gaps, staff improvisation, elected-official pressure, reconciliation burden, and public trust.

That cleaner read feeds DEPN.

DEPN helps Renee decide what kind of movement the problem requires.

Tactical Resolution is the correct move because the outage is already interfering with the objective and cannot be postponed, but a limited containment action is still available.

Pro sharpens the risk read.

Renee has to see what happens if the city does nothing and what the workaround could damage if it spreads too broadly.

T M C protects direction, ownership, communication method, temporary limits, and follow-through.

The departments need one operating message, not five interpretations.

A L C matters after restoration.

The city needs to capture what services were disrupted, what temporary controls worked, where confusion appeared, what records required reconstruction, and what should change before the next incident.

The tool stays central.

Tactical Resolution stabilizes the active interference.

The larger Direct Action System makes sure the stabilization move is informed, controlled, communicated, reconciled, and improved after the operation.

━━━━━━━━━━━━━━━━━━━━

The Point

The city does not lose control because the network goes down.

It loses control when the temporary response fragments the operating record.

That is the point.

The city still has to serve residents.

Staff still need direction.

Departments still need a way to receive time-sensitive work.

The public still needs accurate status.

But continuity does not mean every transaction continues normally.

It means the city identifies what must move, what can move responsibly, what must pause, and what temporary control protects the work until normal systems return.

Tactical Resolution prevents two failures.

Waiting too long while the outage continues interfering with service.

Overcorrecting through a broad workaround that creates more damage than the outage required.

The temporary move is not the final fix.

It is controlled stabilization.

It protects the objective.

It limits collateral damage.

It preserves the ability to clean up and continue later.

━━━━━━━━━━━━━━━━━━━━

A Practical Field Exercise

Use this recognition-level check before the next network outage, system interruption, public-counter failure, or manual workaround spreads across the organization.

This is not the full Tactical Resolution worksheet.

It is a practical way to improve the read before temporary action becomes uncontrolled action.

1. Name the Essential Service

What resident need cannot safely wait?

Is there a deadline?

Is there a public-safety consequence?

Is there a meaningful service impact?

Is the city protecting the resident, the city’s obligation, or both?

Do not call every transaction essential.

If everything is essential, the temporary process will immediately become the full process.

━━━━━━━━━━━━━━━━━━━━

2. Separate Receiving From Completing

What can the city still receive?

What can it verify?

What can it actually complete?

What must remain pending until the normal record is restored?

This distinction protects staff from making commitments they cannot support.

It also gives residents a more honest explanation.

━━━━━━━━━━━━━━━━━━━━

3. Test the Workaround

What could the temporary action damage?

Could it create duplicate transactions?

Could it expose protected information?

Could different departments treat residents differently?

Could staff make commitments without enough information?

Could the city lose the ability to reconstruct what happened?

A workaround should not be approved only because it moves visible volume.

It should be inspected for the damage it can transfer elsewhere.

━━━━━━━━━━━━━━━━━━━━

4. Name the Temporary Limit

Which services are included?

Which services remain paused?

Who can authorize an exception?

What does the temporary receipt mean?

When does the temporary process stop?

A workaround without limits spreads.

Once it spreads, different employees begin using it for different purposes.

━━━━━━━━━━━━━━━━━━━━

5. Assign the Return Work

Who owns reconciliation?

Who enters accepted transactions after restoration?

Who checks for duplicates?

Who confirms what residents were told?

Who closes the temporary record?

Who reports what failed?

If no one owns the return work, the city has not stabilized the problem.

It has moved the problem into the future.

━━━━━━━━━━━━━━━━━━━━

What Leaders Should Watch For

Every Department Creates Its Own Temporary Log

Local initiative can feel helpful.

Multiple uncontrolled records create conflicting operating truth.

The city needs a controlled continuity record, not scattered notes.

━━━━━━━━━━━━━━━━━━━━

Staff Start Promising Completion Without Verification

Employees want to reassure residents.

A promise made without records, approval, or verification may create a larger service failure after restoration.

━━━━━━━━━━━━━━━━━━━━

“We Will Enter It Later” Becomes the Entire Plan

Later is not a control.

Leadership still needs ownership, documentation, limits, reconciliation, and a review point.

━━━━━━━━━━━━━━━━━━━━

Receiving and Completing Become Blurred

A stamped document may confirm that something was received.

It may not confirm completeness, approval, posting, scheduling, or final status.

Residents and staff need that difference stated clearly.

━━━━━━━━━━━━━━━━━━━━

The Public Message Is Cleaner Than the Operation

A city may announce that services remain available while departments are applying different temporary processes.

Public messaging must reflect operating reality.

It should not create confidence the city cannot support.

━━━━━━━━━━━━━━━━━━━━

The Workaround Continues After the Original Need Changes

Temporary processes can become familiar quickly.

Once staff adapt, the workaround may continue even after systems return or the risk changes.

That is why the city needs reassessment and a clear stopping point.

━━━━━━━━━━━━━━━━━━━━

Why This Matters for Public-Sector Leaders

Public-sector leaders operate under a different service pressure.

A private business may close a transaction path temporarily.

A city still has residents arriving with needs tied to housing, utilities, property, safety, inspections, public works, records, payments, applications, and community services.

The leader cannot treat the network outage as an information technology issue alone.

Technology owns technical containment and recovery.

Operational leadership owns the service consequences created by the loss of those systems.

That means public-sector leaders have to balance several pressures at once:

Resident access.

Fairness.

Documentation.

Privacy.

Staff capacity.

Public communication.

Elected-official expectations.

Service continuity.

Future reconciliation.

Public trust.

The city is expected to keep operating.

It is also expected to remain accountable for what it accepts, promises, processes, records, and communicates.

That is why broad improvisation is dangerous.

Every uncontrolled workaround creates a new place where accountability can break.

A resident may receive an answer but no reliable follow-through.

A staff member may record the need but not transfer ownership.

A department may preserve activity while losing documentation.

A temporary solution may solve the counter pressure while creating weeks of back-office failure.

The leader’s responsibility is not to preserve the appearance of normal operation.

It is to preserve essential service with honest limits and operating control.

That is Tactical Resolution.

━━━━━━━━━━━━━━━━━━━━

Where Tactical Resolution Fits

This is where Tactical Resolution fits.

It helps leaders act when an active problem is already interfering with the objective and can no longer be postponed.

It does not tell the leader to solve the entire root problem immediately.

It helps the leader stabilize the interference enough for the objective to continue.

It does not replace judgment.

It protects judgment from two weak reactions:

Waiting while the active problem keeps causing damage.

Overcorrecting through a response that creates unnecessary second- and third-order effects.

In this scenario, the network outage is already interfering with public service.

Identify and Postpone is no longer enough.

The city needs action.

But a controlled service-continuity lane is still possible.

That means the city does not yet need to treat every operating service as unavailable or authorize an uncontrolled bypass across the entire organization.

A full Tactical Resolution application goes deeper than this article.

Inside the DEPN training path, leaders learn how to identify the exact interference point, evaluate collateral risk, select the minimum effective containment move, assign cleanup, communicate temporary limits, reassess the result, and know when another DEPN strategy is required.

This article teaches the recognition.

The course teaches the execution.

━━━━━━━━━━━━━━━━━━━━

What to Practice This Week

Look at one temporary workaround currently operating in your department.

It does not need to involve cybersecurity.

It could be a paper intake process.

A temporary spreadsheet.

A manual approval.

A shared inbox.

A temporary staffing arrangement.

A service counter exception.

A backup scheduling process.

Ask:

What active problem is this workaround stabilizing?

What objective does it protect?

What could the workaround damage if it spreads?

What is the limit of the temporary action?

Who owns cleanup and reconciliation?

When will leadership check whether it still works?

Do not assume temporary means harmless.

Do not assume activity means control.

Do not assume someone will clean it up later.

Inspect the workaround before it becomes the next operating failure.

━━━━━━━━━━━━━━━━━━━━

Final Thought

The network outage does not have to become a records failure.

The city has to control the temporary response before every department starts building its own version of continuity.

Residents still need service.

Staff still need a path.

Departments still need direction.

The public still needs accurate information.

But the city cannot protect those needs by pretending the normal systems are still available.

Some services can continue.

Some can only be received.

Some must remain paused.

The leader’s job is to know the difference.

Tactical Resolution is not the permanent fix.

It is the disciplined move that reduces active interference while preserving the organization’s ability to recover, reconcile, and continue.

Keep essential services moving.

Limit the workaround.

Protect the record.

Assign the cleanup.

Check the result.

The outage is already active.

The temporary response does not need to become the next failure.

━━━━━━━━━━━━━━━━━━━━

Start where you are.

Use the Public Sector Direct Action Starter Sheet before you react, authorize a workaround, promise a public answer, shift staff, bypass a control, or make the next public-service decision under pressure.