HomeWorkLifecycle Intelligence

Red Hat partners · renewals & pipeline

Sole designer6 months to ship · still evolving

Lifecycle Intelligence

A partner-facing view of renewals, pipeline, risk, and growth for a wide Red Hat partner audience — built to answer “where should I look?” instead of dumping every number on the page.

  • PartnersWide audience across renewals and risk
  • 6 viewsStructured around real decisions
  • What matters first
  • Filters
  • Next steps
Summary: where to focus, and what to do next

The hard parts

  • I helped structure Summary, Performance, Pipeline, Risk, Growth, and related views so the big numbers earned their place.
  • I untangled how filters should work: what’s global, what sticks, and how people can see what’s on.
  • I dialed back the noise so status, urgency, timing, and action weren’t fighting for the same badge.
  • I pushed recommendations toward real next steps: which account, why it matters, and what to do.
  • Definitions kept changing while we were already designing screens.
  • Filters didn’t behave the same way everywhere, and that showed up in charts, tables, and exports.
  • Everyone wanted every signal on screen. Equal weight made the important stuff hard to find.
  • Internal shorthand made sense to us and almost no one else outside the room.
  • Start with the decision the person needs to make, not with every field the database can return.
  • Empty states, errors, and tooltips aren’t decoration. They’re how people learn the product.
  • If the same pattern behaves differently on every page, the product still feels unfinished, even when each screen looks polished.
Performance: how bookings stack up over time
Filters: a calmer way through a messy control set

Want to talk about this work?

Happy to walk through the tradeoffs, the edge cases, or how I’d approach something similar.