Engineering work continuity depends on more than keeping teams connected. When access to laboratories, integration facilities and specialized equipment is limited, organizations must decide which tasks can move forward, which require physical testing and how to adapt project plans without compromising technical objectives. NASA Goddard’s response to pandemic-related workplace restrictions illustrates practical ways engineering teams can keep technology development moving under constrained conditions.
Engineering work continuity starts with task flexibility
Many engineering activities depend on purpose-built facilities. Optical benches, hardware workshops and integration and test spaces cannot always be recreated at home. Rather than attempting to reproduce every laboratory setup, teams can identify portions of the work that are feasible in other environments and adjust sequencing accordingly.
One Goddard project was developing a relative position sensor for formation-flying spacecraft. The broader effort involved measuring extremely small alignment variations over a 100-meter laser light path, a scale that called for a large, complex optical bench. That work could not simply be transferred to a family room. However, a related technology—the design and validation of a wedge-shaped, three-dimensional optical target—could be tested on a smaller bench.
This distinction helped the team continue useful technical work while the full-scale test environment was unavailable. Project funding and labor were shifted toward the task that could proceed at the time, while computer-based design and component planning for the original effort continued. The lesson for engineering leaders is to separate a project into work packages with different facility requirements, rather than treating the entire project as either possible or impossible under changed conditions.
Match the test method to the available environment
Adapting a test does not mean claiming that a small-scale setup proves every aspect of a larger system. It means identifying what a particular test can validate and keeping that scope clear. A compact bench may support validation of an optical target, for example, but it does not replace a 100-meter test path when that path is needed to assess system-level performance.
That discipline is important in industrial automation, where commissioning, sensor calibration and control-system verification often involve both isolated component checks and integrated system tests. Teams can maintain progress by:
- Separating design from physical verification: Continue modeling, design reviews and parts planning while reserving facility-dependent validation for when suitable equipment is available.
- Defining what each test demonstrates: Record the setup, operating conditions and limitations so that component-level results are not mistaken for full-system qualification.
- Re-sequencing work deliberately: Advance tasks that can be completed safely and rigorously, while tracking tests that remain dependent on specialized facilities.
- Keeping requirements visible: Ensure that schedule changes do not obscure the original technical objectives or the evidence still needed to meet them.
These practices help technical decision-makers distinguish genuine progress from deferred verification. They also make it easier to resume facility-based work with a clear understanding of what has already been completed.
Plan around hardware, workspace and people
Remote engineering has practical limits. Some Goddard technologists brought instruments home and adapted available household workspaces, while others relied on colleagues’ workshops for hardware tasks. Space, equipment access and family responsibilities all affected what could be accomplished. These realities are relevant to any distributed engineering effort: a video call can support coordination, but it cannot substitute for the instruments, work area or hands-on access a task requires.
Project managers should therefore assess each task against its actual resource needs. Useful questions include:
- Does the work require specialized equipment or controlled laboratory conditions?
- Can part of the task be completed through analysis, design or documentation?
- Is there a safe and suitable alternative workspace, and are the necessary instruments available?
- Which dependencies must be resolved before hardware testing can resume?
Answering these questions early can reduce unproductive attempts to recreate unsuitable lab conditions and support realistic scheduling. It also helps teams allocate scarce equipment and specialist time where they are most needed.
Virtual collaboration can support complex design studies
Goddard’s Integrated Design Center normally conducted detailed mission and instrument studies in large, collaborative rooms. In anticipation of remote work, its team tested a virtual workflow using web conferencing, remote network access and collaboration tools. The group then carried out design studies remotely, coordinating multiple discussions and a large number of participants while maintaining its schedule.
The transferable insight is not that virtual meetings replicate every aspect of in-person engineering. Instead, remote collaboration can be effective when teams prepare the working environment before relying on it. That includes testing access, establishing how decisions and technical information will be shared, and planning for parallel meetings or interdependent work. For system integrators, similar preparation can support design reviews and coordination across engineering, operations and supplier teams, even when physical access to a shared facility is limited.
Use project governance to protect progress and quality
Flexible project management was central to the response. Internal research and development funding arrangements allowed teams to shift emphasis toward work that could proceed, while managers assessed the impact of disrupted laboratory access on schedules. This kind of flexibility is most useful when paired with transparent control of scope, resources and unresolved technical risks.
Organizations can apply the same approach by maintaining a current view of:
- Work completed and evidence produced.
- Tasks delayed because of facility, equipment or access constraints.
- Funding, labor and schedule changes made to accommodate those constraints.
- Tests or reviews still required before a design can be considered fully verified.
Clear records allow teams to adapt without losing traceability. They also help customers and stakeholders understand what a deliverable demonstrates—and what remains to be done.
Conclusion: adapt the route, preserve the objective
Engineering work continuity is not about forcing every activity into a remote format. It is about understanding which tasks depend on specialized environments, identifying meaningful work that can proceed elsewhere and adjusting plans without weakening verification. NASA Goddard’s experience shows the value of flexible task sequencing, appropriately scoped tests, prepared virtual collaboration and responsive project governance. For industrial automation teams, these principles can help sustain development and design work through disruption while keeping technical requirements and future validation firmly in view.