04Information architecture

A simplified connection process

Untangling a page that tried to be a setup flow, an overview, and a workspace, without splintering the experience.

Role
Lead designer
Team
Cross-team feature

V1 prototype in Figma

↓↓
Clicks & session time
+
Completion rate
Support requests

The challenge

Funnel's file import feature made users hop between several similar pages to complete a single goal. The same pages morphed depending on the phase, and two pages, owned by different teams, displayed the same things. The whole flow was incredibly complicated.

The idea

Three simplifications: merge the two duplicate pages under a single owner; uncouple the connection flow, the overview and the workspace; and make pages that users revisit stay static, so they could always find what they needed.

The scope

Too big to ship at once. I broke it into smaller, independently valuable pieces we could release incrementally without disrupting other surfaces.

The process

I walked through Funnel screen by screen, capturing hundreds of screenshots to ground the user journeys I drew up. Then I deconstructed the feature, built a prototype of the target state, and user-tested it against the existing flow to surface more friction. I sliced the design into independent GitHub issues and kept the engineering team close throughout so we shipped with shared conviction.

My workspace in FigJam

Launch & conclusions

The first slice landed with an immediate, measurable drop in clicks and session time. By the time the full initiative shipped, the experience had been transformed: completion rate up, support tickets down, abandoned sessions down. We even got unsolicited positive feedback from customers.

Reflections

Ambitious, long-term targets broken into achievable steps beat narrow point-fixes. Every slice paid for itself, and the cumulative outcome was a step-change in the feature.

Outcome

Dramatic reduction in clicks and session time, higher completion rate, fewer abandoned sessions, plus unsolicited customer praise.