{"id":747,"date":"2026-08-04T20:24:12","date_gmt":"2026-08-04T20:24:12","guid":{"rendered":"https:\/\/torreyowens.com\/staging\/?page_id=747"},"modified":"2026-08-05T22:00:27","modified_gmt":"2026-08-05T22:00:27","slug":"raven","status":"publish","type":"page","link":"https:\/\/torreyowens.com\/staging\/raven\/","title":{"rendered":"Raven"},"content":{"rendered":"\n
\n
\"\"<\/figure>\n\n\n\n
\n
\n
\n

Enterprise SaaS<\/p>\n<\/div>\n\n\n\n

\n

Design System<\/p>\n<\/div>\n\n\n\n

\n

Surveillance<\/p>\n<\/div>\n<\/div>\n\n\n\n

Building a Scalable Design Foundation<\/h3>\n\n\n\n

Created a unified design system that brought consistency, scalability, and efficiency to FLIR Raven and future enterprise products.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n
\n
\n

Overview<\/h2>\n<\/div>\n\n\n\n

What was this engagement?<\/p>\n<\/div>\n\n\n\n

FLIR Raven is a web-based site planning platform used by enterprise organizations to design and manage complex security deployments.<\/p>\n\n\n\n

As the product evolved over many years, the interface became increasingly inconsistent. Different teams solved similar problems in different ways, creating duplicate patterns, inconsistent interactions, and unnecessary complexity.<\/p>\n\n\n\n

Rather than simply redesigning screens, our objective became establishing a shared design language that could scale across Raven and future Teledyne products.<\/p>\n\n\n\n

\n
\n

I led UX Design.<\/p>\n\n\n\n

\n
\n

Role<\/p>\n\n\n\n

Lead UX Designer<\/p>\n<\/div>\n\n\n\n

\n

Duration<\/strong><\/strong><\/strong><\/p>\n\n\n\n

12 mos<\/p>\n<\/div>\n\n\n\n

\n

Responsibilities<\/p>\n\n\n\n

UX Research \u2022 Information Architecture \u2022 UI Design \u2022 Design System \u2022
Component Library \u2022 Interaction Design \u2022 Developer Collaboration<\/p>\n<\/div>\n\n\n\n

\n

Collaborators<\/strong><\/p>\n\n\n\n

Product Management \u2022 Engineers \u2022 Google \u2022 UX<\/p>\n<\/div>\n\n\n\n

\n

Deliverables<\/strong><\/strong><\/strong><\/p>\n\n\n\n

Enterprise Design System \u2022 Figma Component Library \u2022 Interactive Prototypes \u2022 Storybook React Components \u2022 Design Specifications \u2022 Developer Handoff<\/p>\n<\/div>\n<\/div>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\n
Go to product website \u2192<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\n
\n

The Challenge<\/h2>\n<\/div>\n\n\n\n

How do you redesign a product without redesigning it over and over again?<\/p>\n<\/div>\n\n\n\n

The Raven platform had been evolving for years. New features had been added by different teams, at different times, to solve different customer needs. Over time, those individual decisions created a larger problem.

\u2022 Buttons behaved differently
\u2022 Forms followed different layouts
\u2022 Tables used different spacing
\u2022 Navigation patterns changed between workflows<\/mark>

None of these issues were catastrophic on their own, but together they increased cognitive load for users and slowed product development. The redesign wasn\u2019t simply about creating a more modern interface. It was about creating consistency.<\/p>\n\n\n\n

One insight quickly became clear. Users didn\u2019t need more information. They needed better context. That realization shaped everything that followed.<\/p>\n\n\n\n


<\/p>\n<\/div>\n\n\n\n

\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n
\"\"<\/figure>\n\n\n\n\n\n
\n
\n
\n
\n

Discovery<\/h2>\n<\/div>\n\n\n\n

How did we understand the inconsistencies?<\/p>\n<\/div>\n\n\n\n

Before designing new screens, we audited the existing product. We cataloged recurring interface patterns, navigation models, layouts, typography, form controls, and reusable components.<\/p>\n\n\n\n

Instead of asking, \u201cHow should this screen look?\u201d We asked,

\u201cWhat patterns already exist?\u201d
\u201cWhat works?\u201d
\u201cWhat creates friction?\u201d<\/mark>

This inventory became the foundation for every design decision that followed.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\"\"<\/figure>\n\n\n\n\n\n
\n
\n
\n
\n

Framing<\/h2>\n<\/div>\n\n\n\n

Organizing the patterns.<\/p>\n<\/div>\n\n\n\n

Rather than redesigning each screen independently, we identified the core building blocks that appeared throughout the application.

Those patterns became reusable design primitives.

By separating components from individual pages, we created a system that allowed future features to inherit consistent behaviors instead of introducing new variations.<\/p>\n\n\n\n

One insight quickly became clear. Users didn\u2019t need more information. They needed better context. That realization shaped everything that followed.<\/p>\n\n\n\n


<\/p>\n<\/div>\n\n\n\n

\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n\n\n
\n
\n
\n
\n

Design System<\/h2>\n<\/div>\n\n\n\n

Building a shared language.<\/p>\n<\/div>\n\n\n\n

The design system became much more than a UI kit. It established common rules for spacing, typography, colors, icons, interaction states, accessibility, and reusable components.

Designers could move faster.

Developers could build with greater consistency.<\/mark>

Product teams could introduce new functionality without reinventing existing patterns.<\/mark>

Rather than treating every project as a blank canvas, the system provided a shared foundation.<\/p>\n\n\n<\/div>\n<\/div>\n\n\n\n\n\n

\n
\n
\n
\n

Application<\/h2>\n<\/div>\n\n\n\n

Bringing the System to Life.<\/p>\n<\/div>\n\n\n\n

The design system moved beyond documentation once it was applied throughout Raven.<\/p>\n\n\n\n

Core workflows\u2014including navigation, search, forms, tables, and settings\u2014were rebuilt using shared components and consistent interaction patterns. As new features were introduced, they naturally inherited the same visual language and behaviors instead of creating new variations.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The result was a product that felt cohesive, predictable, and easier to navigate, while giving designers and developers a common foundation for future enhancements.<\/p>\n\n\n<\/div>\n<\/div>\n\n\n\n\n\n

\n
\n
\n
\n

Impact<\/h2>\n<\/div>\n\n\n\n

What changed?<\/p>\n<\/div>\n\n\n\n

The redesign improved more than visual consistency. Teams gained a common vocabulary for discussing interface decisions and developers spent less time recreating components. Design reviews shifted from debating individual pixels to solving user problems. Most importantly, Raven established a scalable foundation that could support future growth across Teledyne products. Success wasn\u2019t measured by how many components we created. It was measured by how much easier it became to build the next feature.<\/p>\n<\/div>\n\n\n\n

\n
\n