work

get in touch

kt.

Password required

This work is protected due to confidentiality agreements and is only intended for professional viewing.

To request access, please email kyletizio2@gmail.com.

Strategy planning in motion

An improved view switcher

Experience architecture

Cross-product integrations

Interaction design

Concept testing

Workflow optimization

I led the design of an improved view switcher that helps product managers move easily between different planning views without losing momentum.

Our goal was to make planning feel continuous, even as the view changes.

increase in view switches per session

reduction in view-setup support tickets

146

grouped view sets created in first 4 weeks

It feels like I’m moving through my plan now, not starting over each time.

– Customer (PM)

context

PMs build roadmaps by moving through multiple views of the same data.

Prioritization for what matters

Boards for structure

Roadmaps for timing

When switching between those pages resets filters or breaks context, planning slows down. Trust drops.

For many users, the workaround to maintaining separate saved views was bookmarking alternate pages just to stay oriented.

the missing link

Different views were powerful on their own but we were missing a way to transition between those pages and keep data persistent.

what we built

We shipped an improved view switcher that treats views as different lenses on the same plan, rather than separate destinations.

Users can now create groups of related views that maintain filters, scope, and selections without having to start over.

The switch between prioritization, roadmap, kanban, and other styles of views is now intuitive and connected.

outcomes

The experience improved by reframing views as connected perspectives rather than separate tools.

146

grouped view sets created in the first 4 weeks post-launch

Early adoption confirmed the demand but it didn't tell us whether the experience was an actual improvement.

We tracked two additional signals to measure real impact.

We compared average view switches per session across a 60-day window before and after launch. Users with access to grouped views switched 15% more frequently, suggesting that we'd made the transition between views feel safer.

VIEW SWITCHES PER SESSION

1.8

before launch

2.3

after launch

60-day average, Looker

We also worked with CS to track support tickets tagged to view switching, filtering, and configuration (also before and after launch).

SUPPORT TICKETS RELATED TO VIEW SETUP

before launch

after launch

4-week average, Zendesk

A 25% reduction in view-setup tickets. For a lean CS team, fewer recurring tickets means more time for higher-value conversations with customers.

This felt like one of the clearest support wins we’ve had.

– CS Manager

how we got there

Our customers flagged their difficulties clearly to us through our Ideas portal. Even experienced PMs hesitated to switch views because they feared losing their setup.

customer votes related to switching between views

We used submitted ideas, customer outreach, and ticket themes to focus our research on the highest-friction moments.

usability sessions

with a focus on user reaction to two different approaches

support tickets analyzed

filtered by keywords + categorized into themes

We worked with active customers to pinpoint where view switching forced rework and broke momentum.

Our Customer Success team helped us to map a common setup journey and confirmed what we’d been hearing. Users didn’t feel confident until the very end. Even then, it felt fragile. The experience fell short for seasoned users and was even more uncertain for new ones.

Across our conversations, one theme was consistent. View switching was treated as a risk, not a convenience.

I know what I want to do next. I just don’t want to rebuild my setup to get there.

– Active customer

comparing approaches

We ran moderated prototype sessions to compare approaches for switching through and adding connected views.

Across sessions, persistent tabs tested better. Keeping views visible reduced uncertainty. Users navigated more confidently, scanned faster, and rarely had to pause to rediscover where a view lived.

A tabbed layout (left) kept related views visible, while a dropdown (right) stored them in a single control.

It feels like one plan, not a bunch of different screens.

– customer

a late challenge

The team's decision wasn’t purely about usability. It was also about product philosophy.

In a founder-led enterprise tool, patterns reflect long-standing mental models and a conservative approach to change. While tabs performed better in testing, there was still a desire to keep views clearly separated.

We shipped a compromise: tabs for those who wanted quicker switching across related views, and the dropdown as the default for consistency with existing controls and navigation.

reflection

Enterprise software is rarely a clean “before and after.” Every change lives inside permissions, legacy workflows, edge cases, and the reality of teams who can’t afford disruption.

We shipped the solution that we could support end-to-end. It wasn't the most dramatic redesign but the data tells us it moved the needle.

If I were to push this forward in a v2, I'd advocate for making tabs the default based on what we saw in testing. I'd also want to explore whether grouped views could be auto-suggested based on a team's usage patterns.