InVision Freehand

Visual Design, Research, User Testing
After joining InVision during their pivot to Freehand—I was placed at the helm of designing 3rd-party integrations with the Integrations squad. Using newly-launched integrations as starting points, I guided the design of add-ons for Asana, Trello, and several others.

How do we expand our offerings significantly AND build them efficiently?

With the goal of shipping a new integration every sprint, I took a systems-based approach to design. Auditing each tool we planned to integrate with revealed continuity in general usage patterns, allowing us to define an MVP vision of how our integrations would likely be used across the board.

Freehand serves as a blank canvas for collaborative activities. 3rd-party integrations exist to fit within users’ existing tech stacks—providing whiteboard capabilities where none existed previously.

At InVision, we were our own users. Freehand sat at the core of our own tech stack and sought to make it valuable to every EPD organization in the market.

The ultimate vision for a 3rd-party PM integration is to provide a more immersive, collaborative real-time experience for any product team ritual.

After joining while the Jira integration was already in-flight, I supported the squad by following up with moderated user testing of heavy Jira users—many of whom were also virtual whiteboard users. Testing revealed positive impressions, highlighted areas of improvement, and perhaps most importantly—marketed Freehand to key users.

User Flows
A shared paradigm existed across each PM tool that we planned to integrate with. Knowing this, I maintained a consistent set of user flows for each subsequent integration.

Upon configuration, each integration would follow the same process: search Freehand’s library of add-ons, choose their preferred app, and complete a brief authorization flow.

Systemization I
The design work done for Jira would serve as a template for the design of the next integrations. I defined and iterated upon a card structure to account for various edge cases.

The resulting cards struck a balance between data density and visual appeal. The inherent design consistency benefitted engineering efforts and created an extremely efficient shipping cadence.

I also took ownership of the Google Calendar and Zoom integrations. Insights from the previously launched WebEx and MS Teams integrations informed the scope & user expectations.

Google Calendar
The Google Calendar integration enabled Freehand documents to be uploaded as “attachments” to calendar invites—effectively linking guests ahead of a meeting.

The Zoom integration allowed Freehand to be used live within a Zoom meeting without a user sharing a screen and a seperate link to the document. Meeting guests could collaborate in real-time during the call.

Within 4 months, my team shipped six robust integrations due to strong collaboration and a systems-based approach to design.

Unfortunately, these integrations saw very little to no external usage. I would attribute this to a lack of product marketing and general market awareness of Freehand.

Due to a company-wide RIF, progress on new integrations was postponed. Thankfully, this work would inspire InVision’s next initiative: native project management functionality.

© 2024