Business continuity tool · 2025
MRM
A working product built for an internet shutdown.
- Context
- Product Owner · Designer · Engineer
- 01
- ~40 active users
- 02
- Built during shutdown
- 03
- Local-network operation
- 04
- Used until connectivity returned
Problem
During the first days of war in Iran, internet access disappeared and the company could not rely on its normal cloud tools. Work stopped because coordination itself depended on connectivity.
Approach
I reduced the problem to its operational essentials and built a local-network tool that did not depend on the public internet. The priority was continuity and low-friction adoption, not a broad feature set.
Outcome
Approximately 40 people used MRM during the shutdowns until internet service returned, allowing essential work and coordination to continue.
Key product decisions
A working product built for an internet shutdown.
- 01
Constraint-led scope
Every feature had to justify itself against one question: does this help the team keep working without internet?
- 02
Familiar over novel
Under pressure, adoption matters more than feature sophistication. The interaction model stayed direct and recognizable.
- 03
Local resilience
The product removed dependence on public cloud availability for the essential coordination path.
My scope
- Problem framing under operational pressure
- Rapid scope and workflow design
- End-to-end product implementation
- Deployment and adoption for a 40-person team