InVision''s Complicated Legacy in Remote Work
InVision built one of the most celebrated remote-first company cultures in tech history. At its peak, with 800+ employees across 30+ countries and no offices, InVision was proof that a product design company could operate at scale without physical headquarters. It was a unicorn that validated distributed work before distributed work was mainstream. Its eventual closure in 2024 was a complicated lesson - one about product-market fit and competitive dynamics more than about remote work itself, but worth examining carefully for what it reveals about both the possibilities and the limits of remote culture.
InVision did not fail because it was remote. It failed because Figma disrupted its core prototyping market with a fundamentally superior product. Remote work culture cannot save a company from competitive displacement. But InVision''s remote work practices themselves were genuinely excellent and remain instructive.
What InVision Did Right for Remote Culture
Before its closure, InVision built remote work practices that became widely emulated:
- Documentation obsession: Every process, decision, and policy written in a searchable internal wiki
- Async video: Early adopter of Loom-style video updates, reducing the need for synchronous calls
- Manager training: Extensive program specifically teaching remote leadership practices
- Team offsites: Regular in-person gatherings that rebuilt social bonds in a distributed team
- Transparent communication: Company-wide visibility into strategy, product decisions, and financial metrics
The InVision Remote Work Handbook
InVision''s open-source remote work handbook became one of the most downloaded resources in distributed work history. Key principles included:
- "Over-communicate context" - assume nothing is obvious; explain the why behind every request
- "Default to transparency" - make information accessible rather than waiting to be asked
- "Document everything" - if it happened verbally and was not written down, it did not happen for the team
- "Respect timezone diversity" - no meeting should systematically disadvantage any timezone cohort
- "Trust by default" - assume good intentions in all text communication
What InVision''s Closure Teaches Remote Builders
The nuanced lesson from InVision''s end is not about remote work failure:
- Remote work is an organizational operating model, not a business model - it cannot substitute for product-market fit
- Even excellent culture cannot sustain a company against a superior product from a well-funded competitor
- The remote work practices InVision developed were genuine innovations that live on at dozens of companies built by InVision alumni
- The alumni network from highly distributed companies is particularly strong - remote workers build bonds through documentation and video that prove durable
Where InVision Alumni Took Remote Culture
Many of the practices InVision pioneered are now standard at companies built by its alumni:
- Async video updates as a default communication mode
- Structured manager training for remote leadership
- Explicit remote work handbooks as hiring and onboarding tools
- Regular team offsites as a cultural ritual
- Open financial communication with distributed teams
InVision proved that remote work at scale is possible. Its closure proved that remote work does not provide immunity from competitive forces. Both lessons matter for anyone building distributed teams today.