PRODUCT OVERVIEW

TSR Tech is a B2B software platform that helps enterprise clients streamline complex technical operations and system integrations. The new MVP module I designed was built specifically to capture an emerging market segment of mid-to-large enterprises struggling with fragmented workflows across legacy systems. This module enables technical operations teams to connect disparate data sources, automate routine integration tasks, and maintain visibility across their entire technical infrastructure from a single unified dashboard.

GOALS

Launch a market-ready MVP within three months. The business needed to move fast to capture an emerging B2B opportunity before competitors entered the space.

Validate core user workflows before engineering investment. I needed to prove that the proposed solution actually solved real enterprise pain points through targeted research and testing.

Design for technical complexity without overwhelming users. The module had to handle intricate backend processes while presenting a learnable, intuitive interface to operations teams.

Establish a scalable design foundation for future features. This MVP would set the visual and structural language for the entire product line moving forward.

Align cross-functional teams around a shared vision. With tight timelines and multiple departments involved, everyone needed clarity on priorities and trade-offs.

Reduce enterprise client onboarding friction. The design had to make setup and initial configuration fast enough to demonstrate value in the first user session.

MY ROLE

Responsibilities. As Lead Product Designer, I owned the entire design process from initial stakeholder alignment through final developer handoff. I conducted all user research, built information architecture, designed the complete UI in Figma, facilitated usability testing sessions, and created detailed documentation for the engineering team to ensure accurate implementation.

Collaboration. I worked directly with the VP of Product to define scope and business requirements, partnered with two backend engineers to understand technical constraints and API limitations, coordinated with the customer success lead to identify target enterprise users for research interviews, and presented design iterations to the executive team at three major milestone checkpoints throughout the project.

USER RESEARCH

Enterprise teams waste hours switching between disconnected systems. Operations managers reported spending up to 30% of their week manually transferring data between platforms that should communicate automatically.

Onboarding complexity is the primary barrier to adoption. Technical leads expressed frustration with tools that required weeks of configuration before delivering any visible value to their organization.

Trust in automation requires visible system status. Users needed constant confirmation that integrations were running correctly and immediate alerts when something failed, rather than discovering errors days later.

Different user types need different levels of detail. Junior operators wanted simple task-based interfaces, while senior technical leads demanded access to underlying logic and configuration options.

DESIGN PROCESS

I started the first month by facilitating alignment workshops with product leadership and engineering to map out hard technical constraints and non-negotiable business requirements. I then conducted twelve remote interviews with target users at six different enterprise organizations, asking them to walk me through their current workflows and pain points in detail. This research informed three distinct user personas and a comprehensive journey map that highlighted critical friction points in existing solutions. Moving into month two, I translated these insights into detailed user flows that visualized every step from initial setup through daily operations. I created low-fidelity wireframes in Figma that focused purely on information hierarchy and navigation logic, which I tested with five users through moderated remote sessions to validate the foundational structure before investing in visual design. In the final month, I selected and customized an open-source component library to establish visual consistency, then built high-fidelity screens for every major workflow and edge case. I constructed an interactive Figma prototype that simulated the complete user experience, which I tested with eight enterprise users to catch usability issues before handoff. The final two weeks were dedicated to organizing design files, documenting component specifications, annotating interaction details, and walking the engineering team through implementation priorities.

KEY DESIGN DECISIONS

Progressive disclosure for complex configuration settings. Instead of overwhelming users with every option upfront, I designed a stepped configuration wizard that revealed advanced settings only after core setup was complete, reducing cognitive load during critical first-use moments.

Real-time status indicators on every integration card. I added persistent visual feedback showing connection health, last sync time, and error states directly on the dashboard, eliminating the need for users to dig into logs to confirm everything was working.

Template-based setup flows for common integration patterns. Rather than forcing users to build every integration from scratch, I designed pre-configured templates for the five most common use cases identified in research, cutting average setup time from 45 minutes to under 10 minutes.

Contextual help embedded in the workflow. I positioned explanatory tooltips and inline documentation exactly where users encountered technical concepts, tested to ensure they answered questions without cluttering the interface or interrupting task completion.

TOOLS USED

Figma, FigJam, Zoom, Google Sheets, Loom

TIMELINE

This project ran for three months from initial stakeholder kickoff in January 2026 to final developer handoff in March 2026.

THE PROJECT

Challenges

Balancing technical depth with interface simplicity. The module needed to expose complex backend functionality to power users while remaining approachable for less technical team members, requiring careful layering of information and progressive interface complexity.

Designing without existing brand guidelines. TSR Tech had no established design system or visual identity for this new product line, forcing me to build foundational UI standards while simultaneously solving workflow problems under tight deadlines.

Limited access to end users during research phase. Enterprise buyers were easier to reach than the actual day-to-day operators who would use the tool, requiring creative recruitment strategies and longer lead times to schedule research sessions with the right participants.

Scope pressure from competing business priorities. Product leadership initially wanted to include advanced analytics and custom reporting in the MVP, which would have made the three-month deadline impossible without sacrificing core workflow quality.

Outcomes

Launched the MVP on schedule with zero timeline slippage. The module went live exactly three months after project kickoff, meeting the aggressive market entry deadline set by executive leadership.

Validated design through testing with 21 total enterprise users. Across low-fidelity and high-fidelity testing rounds, I gathered feedback from operations teams at 11 different organizations, ensuring the design solved real problems.

Reduced average integration setup time by 78%. Template-based flows and simplified configuration cut the time required to connect a new system from 45 minutes down to approximately 10 minutes based on final usability tests.

Achieved 4.6 out of 5 average usability score in final testing. Eight participants rated task completion ease, interface clarity, and overall satisfaction, with the majority rating the experience as excellent or very good.

Established a reusable component library with 47 documented elements. The UI kit I built for this MVP became the foundation for three additional product modules launched in the following quarters.

Secured contracts with four enterprise clients in the first month post-launch. The sales team used interactive prototypes during the final weeks of design to close deals before the product was even fully built, validating market demand.

KEY METRICS

78% reduction in setup time. Users went from spending 45 minutes configuring a new integration to completing the same task in under 10 minutes using the template-based flow.

4.6 out of 5 usability rating. Final round testing participants gave the interface high marks for clarity and ease of use across both simple and complex workflows.

100% on-time delivery. The project met every milestone deadline across the three-month timeline, from research completion to wireframe approval to final developer handoff.

WHERE WE ARE

The MVP module is now live and actively used by eight enterprise clients managing over 200 active system integrations. The customer success team reports that onboarding time for new clients has dropped significantly, and support tickets related to setup confusion are down compared to earlier TSR Tech products. The design system I established for this module has been adopted across the broader product portfolio, and engineering teams reference the component library for consistency on new features. Product leadership has greenlit the next phase of development, which will add the advanced analytics and reporting capabilities that we intentionally deferred from the initial release.

FUTURE IMPROVEMENTS

Add bulk editing capabilities for managing multiple integrations simultaneously. Power users managing dozens of connections need faster ways to update settings across groups rather than editing each one individually.

Build role-based permission controls to support larger enterprise teams. Organizations want to limit configuration access to senior technical staff while allowing junior operators to monitor status and run routine tasks.

Introduce AI-powered error diagnosis and suggested fixes. When integrations fail, users currently have to troubleshoot manually, but machine learning could analyze common failure patterns and recommend solutions.

Design a mobile companion app for monitoring on the go. Operations teams want to receive alerts and check system health from their phones without needing laptop access.

Create custom dashboard views so users can prioritize what matters most. Different roles care about different metrics, and personalized layouts would reduce time spent navigating to relevant information.

Expand template library to cover 15 additional integration patterns. Research identified many more common use cases beyond the initial five, and pre-built templates for these would further reduce setup friction.

Implement automated health checks that proactively catch issues before they cause downtime. Rather than waiting for integrations to fail, the system could run preventive diagnostics and alert users to potential problems early.