Home

Info

Spaces · 2026

Go To Spaces

Go To Spaces

Search

Healthcare

Cross-platform

Project Context

Go To was a lightweight navigation shortcut for Spaces, letting users jump directly to a channel, DM, or unread item without manually clicking through spaces and organizations to get there.

My Role

As Design Director, I partnered directly with engineering early to brainstorm and shape Go To's design rather than receiving it as a spec. I saw an opportunity for unreads to be included in the same interaction.

Title

Design Director

Go to

Navigate anywhere in Spaces

Go to

Navigate anywhere in Spaces

Go to

Navigate anywhere in Spaces

Problem

Spaces could span multiple organizations, each with its own set of spaces with channels, direct messages, and unreads. Getting from one area to another meant manually navigating through that structure every time, making it tedious with lots of unreads.

Spaces could span multiple organizations, each with its own set of spaces with channels, direct messages, and unreads. Getting from one area to another meant manually navigating through that structure every time, even when the
user already knew exactly where they wanted to go.

*

*

*

Org-level notifications only show a count, not content, due to privacy constraints

Org-level notifications only show a count, not content, due to privacy constraints

3 Unreads in Home Space

3 Unreads in Home Space

1 unread DM in Messages

1 unread DM in Messages

2 unreads in other Org

2 unreads in other Org

3 Unreads in Home Space

1 unread DM in Messages

2 unreads in other Org

3 Unreads in Home Space

1 unread DM in Messages

2 unreads in other Org

Contstraints

A full Activity feature, the more complete way to surface unreads across the app, wasn't feasible yet due to limited API resources. Go To could work as a meaningful stopgap without depending on that infrastructure.

Sandbox exploration

Process

The initial idea as just a simple way to jump to any destination, a channel, DM, or space, without manual navigation. While brainstorming, I saw unreads were a natural fit for the same interaction: the mental model of “I need to go to this channel” and “I need to see what I've missed” were close enough to solve together.

Since this wasn't meant to be a large surface like search, and was explicitly a stopgap on the way to a future Activity feature, we kept it entirely hotkey-driven rather than giving it persistent UI. After the planning conversation with the developer, I had a clear enough picture of how it should function to move straight into Figma.

command

⌘

G

Go to

Navigate anywhere in Spaces

Steve

2

Go to message

Referrals

1

Go to

Navigate anywhere in Spaces

Steve

2

Go to message

Referrals

1

Go to

Navigate anywhere in Spaces

Steve

2

Go to message

Referrals

1

Solution

Since it was meant to be fast and disposable, not a place people linger, Go To works as a command palette rather than a dedicated screen.

Go to

Navigate anywhere in Spaces

Billing Questions

2

Cardio Metro

Switch Organization

Marcus

1

Outcome

Go To checked the box of surfacing unreads until a full Activity feature could ship. While we didn't have usage data, we heard directly from the team and customers that it made navigating the app noticeably easier, which was meaningful to hear.

Reflection

I always find partnering early with engineering, talking through constraints and requirements together in the initial brainstorm, moves things faster and builds buy-in from both sides before any design work even starts. Go To wasn’t handed to me as a spec, it came out of a conversation, and that shaped how quickly and confidently we were able to ship.