COVID-19 changed the speed at which construction companies had to adopt technology. Building magazine’s listing for Data in a crisis: Innovating at speed presents the pandemic as a break from the sector’s previous adoption pattern and argues that the industry would not simply return to its old pace. That is a historical thesis, not proof that every emergency-era change survived.
The practical lesson is more durable: a crisis makes data useful only when it shortens the distance between a signal, a decision, an experiment and a scaled response. McKinsey’s April 22, 2020 guidance, published in Digital strategy in a time of crisis, similarly called for more frequent data reviews, rapid learning and quick expansion of digital initiatives that demonstrate value.
![Construction Project Management & Estimating for Beginners: [2 in 1] From Estimates to Execution - Mastering Project Bids, Estimating Techniques and Management Essentials for New Professionals](https://m.media-amazon.com/images/I/511FzD120CL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
What the Building comment establishes—and what it does not
A pandemic-era argument about adoption speed
Building magazine lists Data in a crisis: Innovating at speed as a comment within its digital-construction coverage. The listing frames its central idea around COVID-19 accelerating technology adoption in construction and changing expectations about how quickly companies can innovate.
That framing matters because construction technology is often discussed as a gradual modernization program: select a platform, train people, connect systems and improve processes over time. A crisis reverses the order. Teams first confront an urgent operational problem, then look for a workable digital response, often with less time for a perfect specification or a long implementation cycle.
#1 Best Overall
The evidence boundary
The accessible listing does not preserve the comment’s author, publication date, full text or specific examples. It therefore cannot support claims about a named contractor, project, software product, cost saving or measured adoption rate. No statistic or attributable quotation from the comment is available. Any detailed case study presented as if it came from that article would go beyond the evidence.
The phrase “no going back” should consequently be read as the comment’s stated prediction or thesis. It does not establish that every organization kept its emergency tools, that all projects became digital, or that construction has reached a uniform new normal.
Why a crisis changes the economics of innovation
Urgency compresses the decision cycle
In normal conditions, a company can postpone a technology decision while it compares vendors, writes a business case and waits for a planned rollout. A crisis makes delay itself costly. Managers need current information about work, people, money and risk while the situation is changing. A modest tool that produces dependable information today can be more valuable than a sophisticated system that will not be ready for months.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThis does not mean that quality, security or procurement controls disappear. It means they must be proportionate to the decision. A temporary dashboard used to coordinate a rapidly changing work plan needs clear ownership and access controls, but it does not need every feature of an enterprise platform before anyone can use it.
Distributed work exposes information gaps
When people cannot rely on being in the same office, site cabin or meeting room, informal knowledge becomes harder to share. Decisions that once travelled through conversation need a visible record: what changed, who decided, which data was used and when the decision will be reviewed. Digital workflows are valuable here not because they are fashionable, but because they preserve a common operating picture when circumstances are unsettled.
Experiments become a management capability
A crisis also lowers the tolerance for untested assumptions. Teams can try a narrowly defined change, observe whether it improves a decision and either adjust it or stop. McKinsey’s April 22, 2020 recommendations put this learning loop at the centre of crisis response: review data more often, learn quickly from experiments and scale initiatives that work.
The operating model for data-led crisis decisions
“Innovating at speed” is not a single software feature. It is a set of management habits that connect evidence to action. The following model translates the crisis-era guidance into construction operations without claiming that these practices were described in the Building comment itself.
Rank #2
| Practice | What changes | Questions to ask | Typical failure |
|---|---|---|---|
| Increase review cadence | Information is checked on a schedule suited to the volatility of the decision rather than a fixed monthly ritual. | Which indicators can change a decision this week? Who reviews them, and at what threshold? | A dashboard is refreshed frequently but nobody has authority to act on it. |
| Run focused experiments | A team tests one process change with a defined outcome, owner and time box. | What is the smallest safe trial? What result would justify continuing, changing or stopping it? | The trial has no baseline, so enthusiasm is mistaken for evidence. |
| Scale what works | A successful local practice receives the training, integration and governance needed for wider use. | Is the result repeatable on another project, and what conditions made it succeed? | A pilot is copied everywhere without checking different contracts, sites or data quality. |
| Keep a decision record | Teams record the signal, decision, owner, date and next review point. | Could another manager understand why this choice was made? | People remember the action but not the assumptions behind it. |
A step-by-step playbook for innovating at speed
1. Start with decisions, not tools
List the decisions that become time-critical during disruption. Examples might include whether a work package can proceed, whether a resource should be moved, whether a forecast needs to be re-baselined or whether a safety control is being followed. For each decision, name one accountable owner and the latest point at which information is still useful.
Then write the minimum evidence required. A small, reliable dataset is preferable to a large collection of fields that arrive late or are interpreted differently by each project. Define terms such as “complete,” “delayed” and “at risk” before building a report.
2. Establish a review rhythm that matches volatility
McKinsey’s crisis guidance specifically emphasized more frequent data reviews. Apply that principle selectively. A rapidly changing operational risk may warrant a daily check; a cash-flow trend may need a weekly review; a longer-term capability decision may remain monthly. The cadence should follow how quickly the underlying condition can change, not how often a meeting has traditionally occurred.
Every review should answer three questions: what changed, what decision follows and when will the decision be revisited? If a meeting only displays numbers, it is reporting rather than a decision forum.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
3. Make the data trustworthy enough to act on
Speed without trust creates faster arguments. Assign an owner to each critical field, document its source and show its last update. Where information is incomplete, label it as provisional instead of presenting a false precision. Keep a short list of known data-quality issues and give each one a remediation owner.
Access should follow the work. People need the information required for their role, while commercially sensitive, personal or safety-related data needs appropriate restrictions. A crisis is not a reason to copy confidential files into uncontrolled channels.
4. Run a bounded experiment
Choose one process and define the trial before it starts. A useful experiment statement has five parts:
- Problem: the decision or delay the change is intended to improve.
- Intervention: the specific workflow, report or communication change being tested.
- Owner: one person responsible for coordinating the trial.
- Measure: an observable result, such as elapsed decision time, completion reliability or the number of unresolved hand-offs.
- Time box: a review date and a rule for continuing, modifying or stopping.
Keep the trial small enough to reverse safely. A project team can test a new hand-off or status routine without making it a company-wide standard. Record what happened, including an unsuccessful result; negative learning prevents another team from repeating the same experiment.
Recommended Free Tools
5. Decide whether the result deserves scale
McKinsey’s recommendation to scale initiatives that work requires more than a positive anecdote. Check whether the result can be reproduced by another team, whether it depends on an unusually capable individual and whether the supporting data is available elsewhere. Review the effect on training, contractual obligations, cybersecurity, integration and workload before expanding it.
Scaling can be staged. Move from one project to a small group, then to a standard process with documented ownership. Preserve a route for exceptions: a method that works on a predictable project may need adjustment on a complex or highly regulated one.
6. Turn the emergency routine into normal governance
When the immediate crisis eases, decide which practices should remain. Keep the faster review cycle only where it improves decisions; otherwise it becomes administrative noise. Retire duplicate reports, consolidate definitions and assign long-term ownership. The point of “no going back” is not permanent emergency mode. It is retaining the ability to learn and respond quickly without waiting for another emergency.
What construction data belongs in the decision loop?
The exact data mix depends on the project and contract, but a practical design starts with decisions and then maps the smallest useful inputs to them. The examples below are operating categories, not products or claims about the Building comment.
| Decision area | Useful information to bring together | Possible review question |
|---|---|---|
| Work progress | Reported completion, planned sequence, constraints and approved changes. | Which activity is most likely to affect the next commitment? |
| Resources | Labour availability, critical materials, equipment status and access constraints. | Where will a shortage create the greatest downstream effect? |
| Cost and forecast | Committed cost, forecast-to-complete, variations and payment status. | Has a new condition changed the forecast or the required approval? |
| Safety and quality | Observed hazards, corrective actions, inspections and unresolved non-conformances. | Which issue needs intervention before the next work stage? |
| Stakeholder coordination | Open decisions, information requests, design changes and responsibility dates. | Which unanswered question is blocking another party? |
Do not combine these streams merely to create a larger dashboard. Bring them together when their relationship changes a decision—for example, when a resource constraint changes the sequence or when a design decision changes the forecast. A focused view is easier to validate and more likely to be used.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to tell whether speed produced value
Adoption alone is not an outcome. A team may open a dashboard every day and still make decisions no faster. Measure the chain from signal to action:
- Signal latency: how long it takes for a material change to become visible to the person who can respond.
- Decision latency: the time between a validated signal and an assigned decision.
- Learning rate: how quickly an experiment reaches a documented keep, change or stop decision.
- Repeatability: whether another project can use the practice without the original team’s informal knowledge.
- Data reliability: the share of critical fields that are current, defined and traceable to an owner.
Set a baseline before changing the process where possible. Compare like with like, and record external conditions that could explain a change. These measures are evaluation tools, not evidence that the pandemic-era initiatives achieved any particular result.
Common failure modes and recovery steps
Tool-first procurement
Symptom: a platform is selected before the decision and data definitions are clear. Recovery: pause configuration, identify the highest-value decision and remove fields that do not support it.
Free tools Windows power users keep installed
One-click scans. No signup required.
Dashboard overload
Symptom: users receive many indicators but cannot tell which require action. Recovery: give each alert an owner, threshold and response; move background information to a separate view.
Permanent pilot status
Symptom: an experiment appears successful but remains dependent on one enthusiastic team. Recovery: test it with another project, document the method and decide explicitly whether to scale or stop.
Fast decisions with weak controls
Symptom: urgent sharing creates conflicting versions, privacy exposure or an untraceable approval. Recovery: establish a controlled source, role-based access, version naming and a lightweight approval record.
Returning to old habits after the crisis
Symptom: review frequency falls, lessons disappear and duplicate manual work returns. Recovery: retain only the routines that improved a defined decision, give them permanent owners and review their value at a normal operating interval.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsWhat “no going back” should mean now
The strongest defensible interpretation of the Building listing is not that every emergency workaround became permanent. It is that the crisis demonstrated a different expectation: construction organizations can change digital processes faster when leadership gives a clear decision target, reviews evidence frequently and treats learning as part of operations.
Whether that expectation endured varies by organization and has not been established by the listing itself. A responsible post-crisis approach therefore combines ambition with verification. Preserve the ability to see a changing situation, test a response and scale what proves useful; remove the controls and reports that add effort without improving a decision.
That is the lasting value of innovating at speed: not permanent urgency, but a repeatable way to convert data into action when conditions change.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
