Katie Tomasello

Design system & research templates

Giving the team shared building blocks instead of blank pages

Our design system was out of date, so designers rebuilt components and research documents from scratch on almost every project. I created reusable research templates and helped rebuild and organize the component library, alongside teammates who each added the elements their projects needed. Delivery time dropped from weeks to days.

Role
Templates creator, library contributor
Team
Product design team
Scope
Design system, research templates
Platform
Figma, Pega, customer web
Buttons
SubmitSave for laterCancel
Status
CurrentPast dueCharged off
Steps
Inputs
Payment amount
$0.00
Payment date
MM/DD/YYYY
Colors
An illustrative recreation. The company's actual library isn't shown.

Impact

Weeks → days

to deliver new designs

3

research templates the team reused

1

shared library everyone added to

Challenge

The design system hadn't kept up with what we were shipping. Designers rebuilt buttons, forms, and layouts for each project, and some teammates spent weeks recreating elements by hand. Research had the same problem. Every journey map, competitor analysis, and persona started from a blank page and looked different from the last one.

What I built

Three research templates, so every project started from the same structure.

Customer journey map. Stages, actions, feelings, pain points, and opportunities in one layout.
Competitor analysis. The same rating criteria and takeaways for every review.
Standardized persona. Background, goals, frustrations, and habits in a consistent format.

Illustrative recreations of the templates.

Rebuilding the library

I also helped design and organize components for Pega and the customer-facing brand, from buttons and inputs to status tags and step indicators. It was a team effort. Teammates built other elements, and the library grew with real project work.

How the team kept it growing

Whenever someone built a new element for their project, it went into the shared library.

  1. 1. Design
    • Build what the project needs
  2. 2. Review
    • Check it against the system
  3. 3. Add
    • Publish it to the library
  4. 4. Reuse
    • The next project starts there

Results

New work started from shared pieces, so designers spent their time on the problem.

Weeks → days

Time to deliver new designs

Consistent research

Every project used the same templates

Reflection

What I learned: a system stays useful only when adding to it is easy. What I'd do differently: write short usage guidance for each component and track which ones teams actually use.

More of my work

  1. 1

    Charge-off payment plans

    Simplifying payment plans for agents and customers

    Read →
  2. 2

    Repaying after repossession

    Helping customers understand and resolve what they still owe

    Read →
  3. 3

    AI customer service assistant

    Giving a collections chatbot a voice customers trust

    Read →
  4. 4

    All work

    Every project, plus additional work and experiments

    See all →
Click the image to zoom