Airlines run on accurate, up-to-date documentation, but their authors were stuck in an archaic XML editor with a steep learning curve and email-based review cycles. As lead designer from 2014 to 2020, I set the product vision and led the redesign into a cloud platform where authors and reviewers collaborate in real time, with audit-proof history and a clear viewer for pilots, cabin crew and ground staff. 
The challenge. Airlines need a reliable, secure platform to create, manage, distribute and view complex operational and technical documents. Aerodocs was used by thousands of airline professionals across some of the world’s largest carriers, and the team had to re-architect the product while keeping it dependable for critical, regulated content.
My role. Lead Designer and member of the Product Core Team, working with about 50 developers, product owners, project managers and business analysts. I owned product vision and strategy, business and competitor analysis, user research, interaction flows, prototyping and validation, and I used systems thinking to improve how the core team worked. 
Thanks to its ease of use, a Middle Eastern flag carrier adopted Aerodocs as its document editor not just for flight operations but across the company, including finance and human resources.
Aerodocs structure document editor before re-design, 2014. 

The new re-designed Aerodocs

How we got there
________________________
Discovery with users and internal experts across six personas (flight ops managers, technical writers, subject matter experts, pilots, cabin crew and ground staff) surfaced three insights: 
One easy platform. Airlines use many tools for different document types, and specialist knowledge caused delays in every revision cycle. 
Collaboration drives decisions. Teams wasted time sending PDFs by email for review and approval. 
Audit-proof records. Airlines must keep every revision, discussion and regulation reference. The technical writer’s experience map showed most pain sat in collaboration, planning and scheduling.
Technical writer persona

Aerodocs persona: Airline technical writer

Typical document review process
Key design decisions
Our principle was to hide the technology so people could focus on content.
_____________________________________________________________________________________
1. In-line editing in place of a form-heavy XML editor, so authors write rather than operate a tool.

2. Real-time authoring, comments and tasks between authors and reviewers, replacing email review cycles.
3. Revision control and activity history, so unapproved content is never distributed, with shared, reusable content and links to regulations that save time in audits.
4. A new web and native viewer that syncs automatically and keeps annotations across revisions and devices.
5. A KPI dashboard that gives flight operations managers visibility into documentation status.
The outcome
Ease of use drove adoption beyond the original audience
_________________________________________________________________
A major Middle Eastern flag carrier rolled Aerodocs out as its document editor across the company, from flight operations to finance and human resources, giving every department consistent, accurate documentation and improving operational efficiency.
More on Aerodocs
___________________________
Aerodocs: Testing a New Market​​​​​​​
Go to case study
New Design Language
Go to case study​​​​​​​
↑Back to Top