In my last year at Viasat I led a project to evaluate whether Aerodocs could work in other industries like rail or maratime. Research with quality assurance, training, technical publications and certification teams showed the editor still felt too technical for new users.
I designed concepts that simplified content editing and brought it closer to consumer-grade software, and I helped assess product-market fit and technical feasibility. The result was a clear answer: the cost of development and the barriers to entry in new verticals were too high. That finding helped the company decide to double down on its aviation software offering, including inflight entertainment.
The challenge. Aerodocs had been shaped for years by the needs of one large airline customer. As the product matured, we saw potential in other industries with similar documentation needs. Before investing, we needed to know whether the product could work for new users and whether the business case held up.
My role. Lead Designer and member of the Product Core Team. I ran user research, interaction flows, lowand high-fidelity prototypes, and validation loops, and coordinated with managers across Viasat departments to understand needs outside flight operations.
What we learned
Testing with internal and external users showed that editing was still too technical
____________________
Two menus. Separate Insert and Edit menus were slow and frustrating.
Mismatched mental models. Inserting into the table of contents worked differently from inserting any other content.
Technical look and feel. Changing colours and outlines around text added barriers. Complex manuals. Editing manufacturer manuals (such as Boeing’s) needed new content types, and authors had to keep a valid XML structure without knowing XML or what could be inserted where.
Aerodocs still required some understanding of valid XML structures
Key design decisions
____________________
Contextual menus removed the Insert and Edit split. Tools appear only when the user needs them.
Guidance built into the interface. Text, thumbnails, examples and descriptions anticipate the next action.
Fewer clicks with keyboard shortcuts.
Help for complex documents. The editor guides authors to do the right thing while keeping valid XML behind the scenes.
Concept explorations for inserting content
Concept explorations for editing content
Result
Lack of product-market fit
__________
The experiment showed there was no strong product-market fit: software development costs and the barriers to entering new verticals outweighed the opportunity. That evidence helped Viasat pivot its strategy and double down on aviation, including inflight entertainment, instead of spreading investment across new industries.
More on Aerodocs
Detailed examples of Aerodocs design work
__________
Aerodocs Platform
Go to case study
Go to case study