Enterprise Systems · Product Leadership · Requirements & Scope · Delivery Management
Bell Flight
Leading design, requirements, and delivery for a complex enterprise platform used to search and review technical aircraft documentation.
Overview
Bell needed to modernize an aging internal platform used by employees across the organization to search for and review technical aircraft documentation. What appeared to be a straightforward search and PDF-viewing experience was supported by a complex network of systems, integrations, and highly specific requirements.
The project required rebuilding the experience while navigating technical dependencies, strict security constraints, multiple stakeholder groups, and a fixed delivery timeline.
My Role
I served as both product designer and business analyst on a roughly 10-person delivery team, working alongside the project lead and technical lead to guide the engagement. I owned the UX work while also gathering requirements, writing stories in Azure DevOps, creating and maintaining a Gantt chart, and helping manage scope, priorities, and delivery across the team.
I participated in onsite discovery sessions, facilitated stakeholder conversations, and stayed embedded with engineering throughout delivery. As scope and technical dependencies evolved, I also helped manage priorities, document risks and decisions, and keep stakeholders aligned on what could realistically be delivered within the timeline.
Approach
I started by understanding how different users searched for and consumed technical documentation, then translated those needs into a simpler search and viewing experience. The interface itself needed to feel straightforward even though the systems behind it were not.
As development progressed, my role expanded beyond design. I worked closely with engineering to clarify stories and requirements, tracked risks and dependencies through a RAID process, and helped communicate the impact of new scope to stakeholders. When requests threatened the timeline, I worked with the team and product owners to determine what needed to ship and what could be deferred.
Outcome
Despite significant technical complexity and changing scope, the team successfully launched the core experience within the committed timeline. We did not deliver every requested feature, but we delivered the capabilities users needed most and replaced an outdated platform with a more modern foundation.
The project also became one of my clearest examples of operating beyond traditional product design, balancing UX, requirements, stakeholder management, scope decisions, and delivery leadership to help a complex project reach the finish line.