Digital workplace: from emergency fix to something sustainable

A few weeks have passed since the mass shift to remote work began. The initial shock has passed. Most companies have found some way to keep operating - some better, some worse. Now the next question begins: is this temporary until the lockdown ends, or is this the new reality for an indefinite period?

Nobody knows the answer. But regardless of the answer, it makes sense to move from emergency mode to a more sustainable configuration.

What separates emergency mode from sustainable

Emergency mode is when the solution was assembled in a few days based on whatever was available. Some people on work laptops, some on personal ones. Three different messengers because nobody agreed on one. A VPN that drops periodically. Meetings without structure that run long. Decisions made on calls that are not written down anywhere.

Sustainable mode is when tools are chosen deliberately, processes are adapted for distributed work, and people know what to do and where.

The transition between the two does not happen automatically. It requires an explicit decision.

What needs to be reconsidered

Communication tools. One tool for synchronous communication (video calls, chats), one for asynchronous exchange (documents, tasks). Not seven different ones out of habit. The specific choice is not critical - what matters is that it is singular.

Task management. If tasks live in email and in the manager's head - that works in an office where you can walk over and ask. In remote work it does not. Tasks need to be visible in a tool, with an owner and a status.

Documenting decisions. Agreements made on a call need to be recorded somewhere. This feels like unnecessary work until something is lost for the third time in a row.

Device security. If employees are working from personal devices, this needs to be acknowledged and a decision made: either provide corporate devices, or introduce minimum requirements for personal ones (updated OS, antivirus, disk encryption).

Working rhythm. The office rhythm does not transfer to remote work well. An explicit agreement is needed on when people are available, where and how to signal problems, and how regular meetings are run.

What not to do right now

Do not launch a major infrastructure transformation in the middle of uncertainty. Changing the data platform, moving to a different email service, starting a large cloud migration project - these are things that require a normal context.

Right now it is better to stabilise what exists, remove the most painful friction points, and document what needs to be done systematically - in a plan that gets executed later.

A simple diagnostic question

Ask yourself: if I needed to hire a new employee today and onboard them fully remotely - could they work independently after a week, relying only on what is documented?

If the answer is no - that is exactly what needs to be fixed first. Not because of the crisis. For normal operational resilience.