InVision.
InVision was a prototyping and collaboration platform for design workflows. Its core services have been discontinued, so remaining work is about extracting content and moving processes elsewhere.
Where InVision fits on a long engagement.
The immediate concern for anyone still referencing InVision is content. Prototypes, comments and the decision history attached to them represent real institutional knowledge, and the discussion threads explaining why something was designed a particular way are often more valuable than the screens.
It is also a general lesson worth acting on. Design history held only in a hosted tool is history you can lose on a vendor's schedule, and exporting decisions into documentation you control is cheap insurance.
What an assigned team does with InVision.
Design rationale is systematically under-documented. The reasoning behind a pattern lives in comments, chat and people's memory, and when any of those go the next team re-litigates decisions that were settled years ago.
Capturing rationale where it survives tool changes is a practice rather than a tool choice, and it is part of the standards held under outsource ux design.
What we use InVision for.
- Decision history extracted Comments and rationale preserved, which is usually worth more than the screens.
- Process moved deliberately Review and feedback workflows re-established rather than improvised.
- Rationale kept where you control it Documentation that survives the next vendor decision.
How InVision capacity is assigned.
Design operations work is assigned inside design capacity, with decision rationale documented where it is not dependent on a hosted tool.
Tell us what your roadmap needs InVision for.
A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.