Product design built in partnership with founders, engineers, and internal teams.
UX / Design System Discovery
Services
A difficult customer journey and an inconsistent interface can appear to call for the same solution: redesign it. But the visible screens rarely explain the whole problem, especially when different teams, products, and codebases have shaped the experience.
Truesight examines how people use the product and how teams design and maintain it. We turn that discovery into a practical brief for UX improvements, interface work, and design systems, so the next investment addresses the problems that matter.
01 // 05
Understand what users and teams need before committing to the rebuild.
UX and design system discovery establishes what an experience needs to do and what the organization needs to support it. The work examines both sides of the interface: the tasks customers are trying to complete and the patterns, components, decisions, and handoffs behind what they see. Looking at those together helps distinguish a usability problem from a production problem and identify where they overlap.
This is useful before a redesign, during a product expansion, or when teams are considering a shared design system. It can also provide direction when an existing component library has fallen out of step with the live product. An organization may have substantial design work already available but lack a reliable picture of what is used, what works, and what should be carried forward.
We establish that picture before committing to a detailed design or implementation plan. The output is a prioritized set of findings, experience requirements, and recommendations for the next phase. Interface production, component development, and broader remediation can then be scoped against the findings rather than assumed at the start.
Duration
3–5 weeks
Engagement
Team size
Founder to Enterprise
Focus
User Experience + Design System Planning
02 // 05
The screens show the symptoms. The next brief needs the causes.
A customer has to enter the same information twice to complete a familiar task. Similar controls behave differently in separate parts of the product. A designer finds several versions of a component and cannot tell which one reflects the live experience. Engineering has already solved part of the problem in code, but the design files still point to an older approach.
Those gaps affect both the customer and the people delivering the work. Users have to relearn patterns or ask for help. Designers redraw elements they cannot confidently reuse. Developers resolve interaction details during implementation, and reviewers discover inconsistencies late enough to create another round of changes. Each team may be doing careful work within its own area while the overall experience becomes harder to navigate and maintain.
A full redesign can look attractive under those conditions, but its scope is difficult to judge without understanding the current experience. Some patterns may be worth preserving. Others may reflect deeper issues with the task flow, information structure, or ownership of shared components. Before approving a rebuild or another library, leaders need to understand which problems are affecting users, which are slowing delivery, and what the next phase should actually include.
03 // 05
Turn the current experience into a clear brief for what comes next.
We review the live experience, available user feedback, design files, and relevant implementation context with the people responsible for them. The scope centers on agreed journeys and product areas so the investigation remains useful and manageable. Where direct user research or testing is needed, we define the questions, access requirements, and appropriate methods rather than treating internal opinion as customer evidence.
We connect the findings to the decisions ahead: which journeys need attention, which patterns should be standardized, what existing work can be reused, and where ownership or documentation is missing. Recommendations are prioritized by user impact, delivery friction, and dependencies. The resulting brief helps the team scope design and development with a clearer understanding of both the experience and the system supporting it.
UX Research & Journey Mapping
Review available research and map priority user tasks, pain points, and information needs. Plan or conduct focused interviews and testing where included in the agreed scope.
Usability & Interface Audits
Evaluate agreed journeys for clarity, consistency, interaction problems, and accessibility concerns. Distinguish findings supported by user evidence from observations that need further validation.
Design System Audits & Component Inventories
Review the patterns, components, tokens, and documentation in use across design and implementation. Identify duplication, gaps, and differences that make reuse or maintenance difficult.
UX & Design System Implementation Roadmaps
Translate findings into experience requirements and a prioritized plan for design, component work, documentation, and ownership. Define dependencies and a sensible starting scope for the next engagement.
“One of the things that impressed me about Garrhet was how much he understood beyond design. We could talk about user experience, marketing, business strategy, or photography, and he'd always bring something useful to the conversation. He's driven, knows his stuff, and has a real ability to connect with people. I think that combination makes him particularly valuable when you're trying to build something from the ground up.”
05 // 05
The next phase starts with evidence, priorities, and fewer unanswered questions.
Leadership can evaluate a more specific investment. Instead of approving a general redesign, the organization can see which journeys need work, which inconsistencies affect delivery, and which existing assets remain useful. Different levels of effort can be discussed against an explicit set of findings. That makes the scope easier to explain and helps avoid replacing working parts of the experience simply because they sit inside an older product.
Design and engineering share a clearer account of the current state and the work ahead. Teams know which patterns are candidates for reuse, where design and implementation differ, and which decisions need an owner. A brief can address those dependencies before production begins. Estimation and handoffs have a stronger foundation because fewer basic questions are left for the next team to discover midway through the build.
The discovery also establishes a reference for evaluating subsequent changes. User needs, recurring friction, and system gaps are documented, so future work can be reviewed against the problems it was intended to solve. Discovery alone does not remove those problems; the improvements come through implementation and testing. Its value is giving that work a sound direction, with a clearer basis for what to preserve, improve, and measure.
Scope the right work before rebuilding.
Start with the experience your customers use and the tools your team works with today. We'll help identify what is getting in the way and turn those findings into a practical plan for the next design and development phase.
Single Projects
Focused work with a defined outcome.
For organizations that need to solve a specific problem, build something new, or move an important initiative across the finish line.
For organizations that need to solve a specific problem, build something new, or move an important initiative across the finish line.
Starting at
$7,500
Defined scope
Clear project outcome
Senior-led strategy and design
Documentation and handoff
Ongoing Sprints
Senior-level support that stays with the work.
For organizations with evolving priorities that need ongoing strategy, design, development, creative leadership, or implementation capacity.
For organizations with evolving priorities that need ongoing strategy, design, development, creative leadership, or implementation capacity.
Starting at
$4,500/m
Reserved Truesight capacity
Ongoing prioritization
Senior creative direction
Flexible related workstreams