Definition
Number of working days between move completion and relocated team returning to pre-move productivity baseline.
The Measurement Gap
Measurement Gap and Decision
The Measurement Gap
Traditional move management tracks move cost (labor, materials, IT setup), move duration (start to finish), and move volume (number of seats relocated). These are process metrics. None measures the business impact of the disruption. The productivity cost of a move is absorbed into general business operations and attributed to "settling in" or "transition": unmeasured categories that allow the real cost to remain invisible.
AI-optimized move planning can reduce physical move time and coordination overhead, but it cannot eliminate the human adjustment period. Different teams recover at different rates depending on workspace configuration, adjacency to collaborators, IT readiness, and familiarity with the new environment. Without MPID, move planners treat all moves as equivalent disruptions and cannot learn which factors accelerate or delay recovery.
The Decision It Supports
MPID tells FM and workplace strategy leadership what each move actually costs in productivity terms, not just logistics terms. High MPID values point to specific bottlenecks (IT setup delays, poor wayfinding, broken adjacencies) that can be addressed before the next move. The metric also provides ROI data for move-reduction strategies: if the average MPID is 12 working days, every avoided move saves 12 days of team productivity disruption.
Formula
Plain Language
Measure the team's productivity proxy for 20 working days before the move to establish a baseline. After the move, measure the same proxy daily. MPID equals the number of working days until the 5-day rolling average returns to 90% of the baseline.
Formal Notation
$$MPID = \min{d : Rolling5d_productivity(d) \geq 0.9 \times Baseline_productivity}$$
Variable Definitions
| Variable | Definition | Unit |
|---|---|---|
| Rolling5d_productivity(d) | 5-day rolling average of the productivity proxy on day d post-move | Proxy-specific |
| Baseline_productivity | Average of the same proxy over 20 working days pre-move | Proxy-specific |
| d | Working day count after move completion | Working days |
Units: Working days. Expected range: 5-15 for typical office moves. Values above 20 indicate systemic issues beyond normal adjustment. Track per move and per team type to identify patterns.
Proposed formula, pending validation pilots.
At a Glance
Decision Supported
What is the actual productivity cost of a move?