I redesigned how enterprise teams create their Master File documentation in Aibidia's TPDoc, turning a multi-section process into a single guided, progressive workflow that makes it clearer and faster to complete. Validated with 9 participants in prototype usability testing (Maze): 100% task completion, 8.8/10 usability score.
TL;DR
Opportunity: Creating a Master File spanned several sections, and there was room to make it clearer what to complete, in what order, and how far along you were. What I did: Designed a dedicated, guided workflow with chapter navigation, progress states, and in-tool document preview, giving teams a single, structured path from start to finished document. Impact: 100% task completion in prototype usability testing (Maze), 8.8/10 ease-of-use score, and strong early adoption feedback confirming users found it significantly clearer to navigate.
Master File preparation spanned multiple sections in TPDoc, without a single sequence, progress visibility, or a way to review the output in context. Teams often completed the final steps outside the tool.
Introduced a dedicated, progressive workflow with guided chapter navigation, completion states, and in-tool document preview, giving teams a clearer and more guided way to produce the document.
Customer interviews across several enterprise clients, competitive synthesis, internal product synthesis, and prototype validation with 9 participants (Maze).
End-to-end: research synthesis, interaction design, prototyping, usability testing. Close collaboration with PM and engineering on scope and delivery.
The full breakdown, research, workflow design, and product screens, is under NDA. Enter the password below to view it, or request access and I will share it directly.
Don't have the password? Request access