Picture of Matt Girardi

Matt Girardi

Copy email

Product Designer | Design Systems Advocate

Designer by day, gamer and chef by night. I design with systems thinking, user empathy, and the occasional snack break.

Detroit, MI

Windows / Mac

Available for work

Matt Girardi

Copy email

Product Designer | Design Systems Advocate

Designer by day, gamer and chef by night. I design with systems thinking, user empathy, and the occasional snack break.

Detroit, MI

Windows / Mac

Available for work

Picture of Matt Girardi

LocalHop: Event Management

LocalHop: Event Management

What if we could turn fragmented event tools into one flexible, mobile-friendly system that makes it easy for libraries to create, manage, and report events with confidence?

Role

Product Designer

Timeline

2023 — 2025

Outcome

Rolled out to all LocalHop clients, helping secure new contracts and reduce user confusion.

Thanks to

Courtney Bordeaux for research support and user insights. Steve Moore, Shawn Chapiewski, and Brian Davidson for dev collaboration. And last but not least, every librarian who tested early versions and shared candid feedback.

Challenge At Hand

How might we give librarians one clear system to manage events, connect with patrons, and grow library visits?

RESEARCH

Figuring Out What Librarians Needed

Every library run's events in very different ways. Some just wanted a quick way to post to their calendars, while others needed full registration, group check-ins, and detailed reporting. But every librarian we spoke to shared the same pain: managing events in real time was harder than it should be.

Research Goals

My research focused on how libraries actually run events and why managing them felt so hard in real time. By tracking feedback and testing with librarians, I aimed to find the biggest pain points and guide the redesign toward simpler, more collaborative, and mobile-friendly tools.

⏱️

Librarians need simpler real-time tools

Managing events as they happen was the most consistent frustration. Features were buried, slow to use, or not designed for quick action during live events.

⏱️

Librarians need simpler real-time tools

Managing events as they happen was the most consistent frustration. Features were buried, slow to use, or not designed for quick action during live events.

🧩

Librarians need simpler real-time tools

Managing events as they happen was the most consistent frustration. Features were buried, slow to use, or not designed for quick action during live events.

🧩

Librarians need simpler real-time tools

Managing events as they happen was the most consistent frustration. Features were buried, slow to use, or not designed for quick action during live events.

📱

Librarians need simpler real-time tools

Managing events as they happen was the most consistent frustration. Features were buried, slow to use, or not designed for quick action during live events.

📱

Librarians need simpler real-time tools

Managing events as they happen was the most consistent frustration. Features were buried, slow to use, or not designed for quick action during live events.

Pain Points by the Numbers

I pulled together insights from surveys, interviews, and testing to figure out where things were breaking down. The same issues kept showing up— too much friction, not enough clarity, and a clear need for better real-time use, teamwork, and mobile support.

85%
85%

Struggled to locate key features in LocalHop

Struggled to locate key features in LocalHop

50 Participants / Survey

28 avg
28 avg

Clicks required to create a single event

Clicks required to create a single event

Usability Testing

78%
78%

Don't actively use LocalHop while hosting events

Don't actively use LocalHop while hosting events

User Interviews

80%
80%

Said multiple staff manage events

Said multiple staff manage events

79 Participants / Survey

4 of 5
4 of 5

Found patron registration confusing

Found patron registration confusing

20 Participants / Usability Testing

50 avg
50 avg

Events hosted per month

Events hosted per month

User Interviews

100%
100%

Want a mobile version of LocalHop

Want a mobile version of LocalHop

User Interviews

"We avoid using LocalHop during events— it’s too slow and clunky."
"We avoid using LocalHop during events— it’s too slow and clunky."

— Library Staff, User Interview

DEFINE

Defining Personas: How Libraries Run Events

We developed two primary personas from our research to ground our use cases. To build a tool that truly worked for libraries, we knew it had to be an easy to use in real time, flexible enough for both simple and complex events, and supportive of multiple staff working together.

Balancing Users and Business

The redesign balanced real librarian needs with LocalHop’s business goals by making event management simpler, faster, and easier to adopt. While librarians gained clearer workflows, mobile access, and confidence in daily use, LocalHop benefited from reduced support costs, stronger client retention, and a platform better positioned to compete in the event management space.

IDEATION

Blueprints for Better Events

Taking what we learned from our research, we brainstormed ways to make event management simpler and more flexible for libraries. Ideas ranged from lightweight calendar posting to robust registration dashboards, mobile check-ins, and team collaboration features. We ran Crazy 8’s to sketch out flows, drawing inspiration from tools like Eventbrite, Google Calendar, and even airline check-in systems. The intersection of our ideas became a streamlined, mobile-friendly event dashboard that could flex between quick setups and complex reporting needs.

Market Research:
Shaping LocalHop’s Direction

I compared competitors like Eventbrite, Cvent, and Google Events to uncover gaps: too complex, too expensive, and not built for librarians’ real-time needs. This research guided LocalHop’s focus on simplicity, collaboration, and mobile support.

Opportunities

📚

Own the library niche

Build a platform purpose-made for libraries, not corporate events, with workflows tuned to their day-to-day needs.

📚

Own the library niche

Build a platform purpose-made for libraries, not corporate events, with workflows tuned to their day-to-day needs.

🔗

Consolidate scattered tools

Bring event creation, registration, check-ins, and reporting into one clean, intuitive system.

🔗

Consolidate scattered tools

Bring event creation, registration, check-ins, and reporting into one clean, intuitive system.

🤝

Simplify collaboration

Support multiple staff working together on the same events without friction.

🤝

Simplify collaboration

Support multiple staff working together on the same events without friction.

🧩

Make reporting effortless

Bring event creation, registration, check-ins, and reporting into one clean, intuitive system.

🧩

Make reporting effortless

Bring event creation, registration, check-ins, and reporting into one clean, intuitive system.

🤝

Simplify collaboration

Support multiple staff working together on the same events without friction.

🧩

Make reporting effortless

Bring event creation, registration, check-ins, and reporting into one clean, intuitive system.

USER FLOWS & WIREFRAMES

Making Event Management Simple

After defining the core features, I mapped out user flows to show how librarians would move through event creation, registration, check-ins, and reporting. The goal was to reduce friction and clicks at every step, consolidating scattered tools into one clean path. Instead of juggling multiple screens, the flow focused on a single dashboard that adapts to both quick "one-shot" events and more complex events with registrations and attendance tracking.

Laying the Groundwork

Taking inspiration from tools like Facebook Events and Google Calendar, I reworked LocalHop’s event creation flow to be simpler, faster, and less overwhelming. By applying progressive disclosure, complex details like registration and capacity settings were tucked away until needed, allowing librarians to focus on getting an event live quickly without distraction.

TESTING

What Worked, What Didn't

I ran multiple rounds of testing to validate the redesign. The second round focused on event creation and the unified dashboard, with in-person sessions at my local library and remote tests across new, returning, and first-time users. Early issues were fixed, but new pain points surfaced around registration clarity and real-time use.

Testing - Round 1

Pain Points

  • Event creation took too many clicks (avg 28)

  • Users struggled to locate check-in tools

  • Patron registration was confusing

  • Dashboard navigation felt cluttered

  • Reporting steps weren’t clear

Testing - Round 2

Issues Resolved

  • Event creation took too many clicks (avg 28)

  • Users struggled to locate check-in tools

  • Patron registration was confusing

  • Dashboard navigation felt cluttered

  • Reporting actions weren’t clear

New Pain Points

  • Some users confused by ticket creation

  • Multi-staff permissions required more clarity

  • Desire for more customization in event setup

VISUAL DESIGN

Creating a Design System

To support the redesign, I built a unified design system for LocalHop and Cynerge’s internal products. Starting with foundations like color, typography, and spacing, I created reusable components that brought consistency, simplified design, and sped up development.

Checkout my case study on the Canopy Design System

View Case Study

Visual Enhancements

The visual updates went beyond aesthetics, reinforcing the new UX with clearer hierarchy and easier scanning. By applying progressive disclosure and Gestalt principles, the design reduced cognitive load and grouped related actions. The result was an interface that felt simpler, faster, and more intuitive for librarians.

FINAL OUTCOME

LocalHop 2.0

LocalHop 2.0

Streamlined for Every Event

Streamlined for Every Event

One streamlined flow takes librarians from creating an event to managing it in seconds, with faster setup, a unified dashboard for every task, and simpler workflows that save time at every step.

📅 Quicker Creation – Create an event without filling out every detail up front. Add or adjust settings later directly from the dashboard.

🎛️ Unified Dashboard – Manage everything from one place. All event settings and tasks stay on the same page, so you never have to jump between screens.

Faster Workflows – Common tasks like check-ins, registrations, and reporting now take fewer clicks and less time, letting librarians focus on running events instead of managing software.

Task-based Layout

The new task-based layout breaks complex event management into clear, focused actions. Modals like “Edit Event” and “Create Ticket” keep tasks lightweight, so librarians can make updates without leaving their flow.

📝 Focused Editing – Event details can be updated quickly in a dedicated modal without navigating away.

🎟️ Simplified Ticketing – Creating tickets is streamlined into one clear form, cutting down confusion and extra clicks.

🔄 Stay in Flow – All key actions happen in context, reducing page switching and keeping librarians oriented.

Guest Management & Reporting

Attendance is at the heart of library events, from day-to-day management to state funding reports. The new design brought attendance tools into one clear screen, making it easier to check in guests, manage groups, and export accurate data in seconds.

👥 Centralized Attendance – View and manage all attendees from one screen.

📊 One-Click Exports – Instantly generate reports formatted for state requirements.

📝 Simpler Tracking – Group check-ins and edits reduce confusion and errors.

IN THE WORKS

Mobile Experience

Librarians aren’t hauling around laptops for Story Time or knitting groups. They need something that works in the moment. So I focused on making the mobile experience simple and fast— easy check-ins, quick edits, and guest tracking; without all the extra stuff that just gets in the way during a live event.

Event Creation

Event creation on mobile is just as fast as desktop— two taps and you’ve got a draft. All it needs is a title. From there, librarians can fine-tune settings before the event goes live. The mobile flow mirrors desktop, so no matter where they are, they’re working with the same tools, just trimmed down for speed.

Real-Time Event Management

I designed a unified mobile flow that makes key tasks, like scanning tickets, fast and intuitive. By removing the need for extra hardware and keeping tools in one place, librarians can manage live events easily from their phones.

Designed for Both Admins & Patrons

I designed the mobile experience to serve both library staff and their patrons. Admins needed real-time control, while also seeing what end users experience when browsing or registering for events. This dual perspective helped create a more empathetic and unified platform.

Continuity Was the Priority

Every interaction— whether you're editing an event or signing up for one, follows the same patterns. I prioritized consistency across layouts, navigation, and visual styling to reduce confusion and create trust. This unified approach made the platform feel like one seamless system, not two separate tools.

REFLECTION

What I Learned

Having completed the LocalHop redesign, I left with two key takeaways:

  1. Simplifying complex workflows requires more than cleaner visuals. It takes user research, iterative testing, and a flexible system to support different needs.

  2. Building a design system is as much about collaboration as it is about components.

Although I was the only designer, I had to learn how to clearly communicate design decisions with developers and product managers while making sure the solution worked in real libraries. I realized that trade-offs are inevitable, but documenting choices and aligning around user pain points helped the team stay focused. Running in-person tests at a local library and remote sessions with new and longtime users reminded me that context matters: the best design is the one that holds up in the real world. Although the process was full of problem-solving, I’m proud of the final product and the confidence it gave librarians using it.

Having completed the LocalHop redesign, I left with two key takeaways:

  1. Simplifying complex workflows requires more than cleaner visuals. It takes user research, iterative testing, and a flexible system to support different needs.

  2. Building a design system is as much about collaboration as it is about components.

Although I was the only designer, I had to learn how to clearly communicate design decisions with developers and product managers while making sure the solution worked in real libraries. I realized that trade-offs are inevitable, but documenting choices and aligning around user pain points helped the team stay focused. Running in-person tests at a local library and remote sessions with new and longtime users reminded me that context matters: the best design is the one that holds up in the real world. Although the process was full of problem-solving, I’m proud of the final product and the confidence it gave librarians using it.

Measurable Results

Reduced Support Tickets

Support tickets related to event creation dropped significantly post-launch, giving our support team more breathing room.

Reduced Support Tickets

Support tickets related to event creation dropped significantly post-launch, giving our support team more breathing room.

Fewer Feature Requests

The new event tools addressed many long-standing gaps, which led to fewer reactive asks from users.

Fewer Feature Requests

The new event tools addressed many long-standing gaps, which led to fewer reactive asks from users.

Easy for librarians

Feedback showed librarians felt more confident using the redesigned mobile experience

Easy for librarians

Feedback showed librarians felt more confident using the redesigned mobile experience

Interested in working together?
Shoot me an email!

Copy email

© 2025 Matt Girardi.

Thanks for scrolling. All rights reserved.

© 2025 Matt Girardi.

Thanks for scrolling. All rights reserved.