UX CASE STUDY --- Space Manufacturing

Designing to replace the system running the AM production floor

0 downtime | 150+ daily users | 10 months | 3 person team

My role: UX Designer + PM + Product Owner

NOTE: due to NDA & ITAR restrictions, no images of the design are able to be shown.

TL;DR

Summary

Situation: Blue Origin was shutting down the system that ran its additive manufacturing floor, with a 10 month deadline

What I did: Led design, product, and delivery planning, and designed, built, and tested the replacement

Result: After I left, rollout finished on time with zero downtime, and the system now serves ~1000 users. Blue’s head of IT called an aspect of the design “the perfect solution for our use-case.”

Team Structure across AM customers and Operations

Problem


  • Blue Origin's Enterprise Technology team was disabling the software behind its additive manufacturing floor (building 450-2,000 engine parts a week), giving us 10 months to replace it. Without a replacement, the floor couldn't operate.

    Why it mattered:

    • Every engine part required ITAR compliance and full traceability

    • The old system let operators create custom versions of approved processes, so engineers couldn't tell which variation was followed

    • That inconsistency caused 5-10 anomalies a week, each requiring significant engineer time for root cause analysis, and made parts hard to trace

Role & Team


My role: UX Designer, PM, and Product Owner (title: Process Engineer II). I stepped into these roles because the project needed them and I understood both the system and its users.

Team of 3:

  • Me: design, product, and delivery (~50% of my time)

  • Machine programmer: fully dedicated

  • Software engineer: ~20% capacity

Users: 150+ daily users across 6 groups: operators, process and M&P engineers, managers, design engineers, post-processing, and AM engineers

Timeline: Sept 2024 notice → Feb 2025 handoff → July 2025 rollout

Process Flow

Approach


Research: I shadowed operators and interviewed 33 stakeholders (15 engineers, 12 operators, 3 managers, 3 maintenance), then audited the old system.

Key insight: Operators had built workarounds because the old process didn't fit their machines.

  • The old process required all 4 laser inputs, even on dual-laser machines, so operators made custom views

  • I built that need into the system with dynamic checklists that adapt to machine type: a dual-laser machine shows 2 laser fields, a quad shows 4

  • Result: operators get relevant inputs, and engineers get consistent data

Prioritizing and testing: I ranked every known weakness and fixed the high-priority ones for launch. Each section got a one-day side-by-side test in both systems before rollout.

1. Getting the right tools approved Standard enterprise tools couldn't support our relational data needs. I met with Enterprise Technology to show why, and Baserow was approved. Our front-end choice wasn't, so we built a custom React interface.

2. Almost no engineering capacity Our software engineer had ~20% availability and we had no extra budget. The machine programmer and I learned to code, cut every nice-to-have, and designed modular features with feature flags so we could ship incrementally as constraints changed.

Challenges


Solution


1. Operator checklist An 11-step checklist plus monitoring steps that adapts to machine type and locks inputs for consistent data. Built for gloved hands on the floor: large buttons, auto-save, and grouped tasks on one screen.

2. Anomaly system Anyone can submit an anomaly through a simple form. A triage team works it through analysis, containment, root cause, and closure on one dashboard. Team SPOCs meet twice a week to assign RCAs. Submitters can't edit the underlying data, which keeps records trustworthy.

Results & Impact


  • Zero production downtime. Rollout completed on time, following the plan I built.

  • Delivered on time, within the 10-month deadline.

  • 150+ users to around 1,000. The system now serves users across Engines, Lunar, and Alloy.

  • Better data: standardized QA checklists, fewer manual entry errors, improved anomaly traceability.

Baserow, the platform I advocated for, became Blue's central hub for additive manufacturing data, and our React interface is still in use.

What’s Next?


The React interface is still in use and continues to grow. The features we deferred to hit MVP are now being built:

  • Automations

  • Dashboards

  • Automated report generation for engineers

  • Customizable flows

“Nearly 1,000 people across the Engines, Lunar, and Alloy teams now collaborate on Baserow. Production data moved out of scattered spreadsheets into a single real-time hub. Customers have full visibility into production order status. All manufacturing sites share real-time data, with secure on-premise and air-gapped deployments.”
— Baserow founder, LinkedIn · One year post-launch

Reflection


I left the company before the system went live, as part of a company-wide reduction in February of 2025. However, my manager's reflection on the project success afterward stayed with me:

"The reason it succeeded on rollout was because of the way

you set up the project and the team for success."

I think about that a lot, because the outcome really wasn't determined at launch, it was determined months earlier, in how requirements were defined, how the team was structured around a shifting set of constraints, and how consistently users were treated as collaborators rather than recipients of something being built for them.