How to Rapidly Elevate a QA Tool’s UX: Lessons from the Goapi Redesign

1. Look Forward, Think Back, Quickly Grasp the Product

Goapi is a QA testing tool with high professional barriers; its complex business rules and jargon make it hard to understand. Early on, there was no analysis material, so designers had to proactively interview stakeholders and typical users to clarify product positioning, target audience, usage scenarios, and feature highlights, thereby gaining a clear product sense.

Indirect stakeholder interviews: low time and travel cost, fast way to learn about target users.

Direct user interviews: more concrete insights but higher cost.

After gathering this information, designers can reflect on future development possibilities, such as differentiating features based on product strengths or improving efficiency through targeted design strategies.

2. Join the Team, Adapt the Rhythm, Design What Fits the Moment

As a B2B tool, Goapi requires clear modules and smooth workflows to improve user efficiency. Early usability issues included unclear navigation, redundant steps, and poor fault tolerance. Limited resources and tight timelines forced front‑end developers to handle both page tweaks and new feature development.

Designers needed to balance existing user habits with new system learning costs, using iterative development and time‑boxed milestones to deliver value while keeping users involved throughout the process.

3. Break Boundaries, Collaborate Up and Down, Find Leverage Points for Team Efficiency

The Goapi team, a sub‑10‑person micro‑team with members transitioning from QA, initially lacked clear product concepts and user data, leading to repeated rework and wasted effort.

To address unclear requirements, a feedback group (WeChat, POPo) was created for the interaction side to collect and format user feedback, defining design problems and needs.

With clarified goals, the team drove design through milestones, delivering incremental improvements while continuously involving users, thus avoiding reliance on personal experience alone.

Remote work challenges were mitigated by moving designers into the business side and using agile, informal “turn‑around” discussions to quickly align on key issues, then documenting outcomes via email.

4. Tool Consolidation and Component‑Based Thinking Boost Design Efficiency

As Goapi grew, the need for faster, higher‑quality design support became critical. By analyzing recurring task scenarios across similar internal tools, the team identified reusable visual modules and built a Component Library 1.0, delivering standardized components to visual and development teams.

The component library reduced duplicated design and development effort, shortened project timelines, and ensured consistent, high‑quality output, allowing designers to focus on user experience rather than repetitive UI creation.

5. Summary

Effective product stewardship involves: (1) proactively stepping forward to understand business and users; (2) adjusting team rhythm to improve design efficiency and align with product goals; (3) stepping back after each iteration to extract reusable components, building a library that accelerates both design and development.

6. Appendix

Over six months, Goapi completed ecosystem enhancements and a full product experience overhaul, solving 80% of user‑reported issues. It now serves two‑thirds of internal QA users and multiple external paying customers, moving from “usable” to “easy‑to‑use”.