Case study 01 · Spring 2026
A single source of truth for Richard Group
Richard Group, a Chicago general contractor, kept project history scattered across spreadsheets and tools. Our team designed a Qualifications Database that lets marketing, business development, and operations find past projects and qualified people in seconds.
- Sponsor
- Richard Group, Chicago
- My role
- UX designer on an 8-person team
- Timeline
- January–May 2026
- Tools
- Figma, FigJam
What I did
- Collaborated on background research and competitive analysis to find market opportunities and shape product strategy.
- Designed accessible, high-fidelity prototypes in Figma.
- Wrote project documentation, design specifications, and design system components for a smooth handoff.
The problem
Proposal teams at Richard work on fast, unpredictable deadlines. The history they need to prove experience (project descriptions, costs, photos, subcontractors, and who worked on what) lived in many places at once.
Our interview with Richard’s Proposals and Marketing Manager surfaced the real cost:
- Some projects had no description, so staff searched or rewrote from scratch.
- No one could tell whether data was current, so everything got double-checked.
- The same information lived in several places, so people waited on each other to move forward.
How might we…
- help users trust the information shown without needing to double-check?
- connect related information to speed up workflows?
- show and find a project’s details quickly?
- help users spot gaps in information?
-
Understand the current process
Background research on CMS, CRM, and PIMS tools, a comparative analysis of about a dozen products, a proposal-manager journey map, and a stakeholder interview.
Comparative analysisJourney mapInterview -
Structure and sketch
Information architecture for projects, employees, and saved lists, then timed five-minute sketches for eight core screens and a full set of lo-fi wireframes.
IASketchingLo-fi wireframes -
Test and iterate
Weekly sponsor reviews shaped the mid-fi screens. Usability sessions with participants pointed to confusing search bars, unclear sort labels, and text that felt too small to scan.
Mid-fi prototypeUsability testing
Key screens
What changed from feedback
Designed for trust and speed
- The app opens straight to the Project Directory, with single sign-on through the firm’s Microsoft setup.
- A CSV import flow maps columns, flags conflicts, and highlights missing data.
- Tabs keep every open profile available, so cross-navigating never loses your starting point.
- Tiered admin permissions separate who can edit from who can view.
What I learned
Test with the people who’ll use it
Scheduling kept us from testing with Richard employees, so we tested with members of the public. It still caught real issues, including text too small to scan comfortably. That reinforced for me that accessibility checks belong in every round, and that domain experts catch problems general testers can’t.