0 to 1: Designing a Smarter Way to Transfer Aviation Assets
B2B Enterprise SaaS Platform
Year
Project Type
Deliverables
Team
2025
Module: 0 to 1
End-to-end transfer flows
User journeys & flowcharts
MVP scope definition
UX requirements & logic
Integration Mapping
High fidelity designs
2 Product Designers
4 Developers
1 Project Manager
2 Business Analytics
1 Quality Assurance
Key Results
Transformed asset transfers into a faster, more reliable process.
We streamlined asset transfers by reducing manual work, minimizing errors, and improving traceability and compliance.
My Role
I shaped the design solution, aligned teams, and assessed its effectiveness.
As the Product Designer, I owned the UX strategy - translating complex aviation requirements into clear, intuitive workflows. I partnered with analysts, engineers, QA, and leadership to align teams, balance business goals with user needs, design scalable solutions within technical constraints, and measure the impact of the workflow changes.
Solution
Improving the Process of Aviation Asset Transfers.
To tackle the complexity of asset transfers, I turned a fragmented, manual process into one seamless, secure system powered by blockchain. Users can move large volumes of data with ease, follow clear, guided steps, and stay fully in control — all within a single platform.
Defining Requirements
I worked with the team to define requirements and integrate the new module.
40%↓
Data entry time
with bulk upload templates
35%↓
Data entry errors
100%
Auditable records through blockchain integration
Data Privacy & Sharing
Asset transfers involve sensitive data, so controlling access and visibility was critical. We designed role-based permissions to securely share or restrict data without compromising organizational privacy.
Example: If a transfer request involved confidential documents, we had to define granular permissions for who could view, approve, or reject access to that data.
Handling Transfers for Connected Assets
A key challenge was maintaining linked data integrity for parent-child assets, like aircraft and their installed parts. (e.g., engines, landing gear)
Example: If the main asset (Aircraft) is transferred, how do we handle the transfer of installed parts? Should they be included in the request, or handled separately? We worked closely with engineers and data architects to define a consistent, reliable approach.
Designing with Blockchain in Mind
Block Aero operates on blockchain infrastructure, which inherently affects how asset data is recorded, updated, and verified.
We had to consider how the transfer process would maintain data immutability, ensure transaction traceability, and prevent unauthorized modifications to asset records.
Key Areas
Personas
Integration Points
We identified how the new feature connects to existing platform workflows.
Next, we mapped all affected flows across the platform, pinpointing integration points with existing features like asset configuration, document management, and notifications.
Flowcharts
We visualized user flows to uncover blockers and define the foundation for the feature.
We mapped flowcharts and user journeys to spot friction points and improvement areas. This revealed blockers, gaps in requirements, and helped shape the first version of the user journey. While the flows would later evolve, the core foundation of the feature was laid during this phase.
Identifying user needs led to clear design opportunities:
Designing for Complexity & Scalability
To design a scalable solution, I broke down transfer flows by understanding who initiates the process and their needs.
Designing the Asset Transfer MVP meant finding the right balance between complexity and scalability. We mapped out key flows without overengineering edge cases, leaving space for future improvements based on real user feedback. I started by asking a simple question: Who is initiating the transfer, and why?
This helped us break the process down into three clear scenarios:
MVP Scenarios
We prioritized the MVP by grouping scenarios by risk, frequency, and impact, focusing on the most critical flows first.
We also found that owners typically initiate transfers, which helps centralize control and minimize data discrepancies. To prevent misuse, we proposed a flagging feature as a future enhancement, to be introduced only if needed based on user feedback.
Solution One
Clear separation of actionable requests to reduce cognitive overload.
Users can filter Transfer Requests to only those requiring action from their organization, reducing noise in shared data.
“My Pending Action” highlights approvals or executions needed, improving visibility for complex flows.
Installed asset configuration provides context for parts-only transfers, while unique Transfer Batch IDs group related transfers — essential for high-risk, bulk operations.
Solution Two
Designed for clarity, control, and reduced approval friction.
Full overview of transfer details, roles, organizations, and document status — solving visibility gaps in Recipient-initiated flows.
Inline document list enhances traceability, essential for high-risk transfers with large document sets.
Related Transfer Requests panel groups connected transfers for easier management.
Status indicators show real-time progress, reducing uncertainty during multi-party approvals.
Solution Three
Clear connection between asset data and transfer initiation
Outcome
We turned constraints into practical design decisions.
Working within constraints means staying practical and confident - sometimes making informed design decisions even without perfect data.
Next Up
Imagine trying to transfer ownership of an aircraft or its components along with thousands of related documents using only emails, spreadsheets, and stacks of paper.
For many aviation companies, that’s still the reality. It’s a process vulnerable to lost data, miscommunication, and costly mistakes.
Our goal was to make asset data transfers simple and reliable. Give users a single place to manage transfers, ensuring nothing gets lost along the way.
Maintenance of Aviation Assets
When Small Frictions Slow Big Operations
Dive In
How do you redesign a document workflow used hundreds of times a day?