Case Study
Balancing Firmware Complexity at Scale
Designing a Platform for Secure, Scalable Device Fleets in the Age of AI
01. Overview
Building the foundation for modern firmware management
When I joined Peridio, the company had deep engineering talent but no design function. Over two years as the founding Head of Design, I built the design practice from scratch and helped shape the product, brand, and go-to-market strategy—working across a small, high-leverage team spanning engineering, sales, and executive leadership.
The problem we’re solving is one of the most complex—and historically under-designed—in modern hardware: firmware management at scale. As device fleets grow and AI workloads move to the edge, each device introduces unique hardware constraints, security implications, and lifecycle risks. Managing this manually quickly becomes unmanageable.
Create and manage firmware binaries
Group and version binaries into releases
Deploy releases across heterogeneous fleets
Monitor, recover, and iterate without downtime
This work sits on top of Avocado OS, our custom operating system and foundational layer for secure boot, monitoring, and lifecycle control—forming a cohesive ecosystem rather than a collection of tools.
02. My Role
Design leadership beyond traditional boundaries
I joined this project as Head of Design at an early-stage startup and have been deeply embedded across every function of the company.
Product & Engineering
- Led end-to-end UX and system design for the entire platform
Embedded with engineering—pair sessions, shared sprints, real-time design decisions
Shipped production front-end code to accelerate delivery and reduce handoff friction
Designed developer-centric interfaces informed by real firmware and embedded workflows
Marketing & Sales
Defined brand positioning, launch narratives, and the visual identity system
Designed white papers, one-pagers, and sales collateral that closed deals
Built interactive demos and live presentations for enterprise prospects
Led creative direction for industry events, the company podcast, webinars, and live streams
Leadership & Strategy
Designed investor pitch decks and fundraising materials used in capital raises
Co-led the NVIDIA Partner Program application—from narrative to approval
Operated as the connective layer between product, engineering, sales, and marketing
Helped translate complex technical capabilities into business narratives for executives and investors
This role required systems thinking, deep technical empathy, and the ability to move fluidly between strategy and execution.
03. Key Challenges
Designing for complexity that compounds over time
Challenge 1
Firmware complexity doesn’t scale linearly
As device fleets grow, each hardware SKU requires specialized firmware. Downgrades introduce security and compatibility risks. Failed updates must be detected and recovered gracefully.
Most existing solutions rely on manual processes, brittle scripts, or vendor-locked tooling. We needed a system that was safe, flexible, and future-proof.
Approach
We treated firmware as a first-class product:
Explicit modeling of binaries, releases, and deployment states
Clear separation between development, staging, and production
Guardrails for downgrade paths and failure recovery
Observability baked into the platform, not bolted on
Challenge 2
Designing for a highly technical, under-served audience
Our core users are firmware engineers, platform engineers, DevOps leads, and CTOs responsible for device fleets. This audience is deeply technical—but historically underserved by UX.
Approach
- Immersed myself in Linux, embedded systems, and maker culture
Learned directly from engineers inside the company (who mirror our users)
Designed interfaces that respect technical literacy while reducing cognitive load
Prioritized clarity, predictability, and trust over visual novelty
Challenge 3
Cross-functional alignment in a fast-moving startup
We needed to ship quickly, support real customer requirements, maintain strategic coherence across teams, and balance feature parity with long-term vision.
Approach
Heavy emphasis on communication over rigid process—async updates, weekly design reviews, open Figma files
Shared artifacts (specs, flows, decision logs) that kept every discipline aligned
Design used as the unifying language between engineering, sales, and leadership
Direct access to customers and prospects to validate decisions in real time
04. Process
Flexible structure for a fast-moving team
Product & Delivery
We operate with a lightweight agile model: weekly goal-setting and sprint planning, quarterly strategy alignment, Linear for task management, and high flexibility to respond to customer needs.
Speed mattered more than ceremony.
Design Methodology
I followed a Double Diamond approach:
- Explore and prototype early
- Share progress quickly
- Validate assumptions
- Refine continuously
Design artifacts were intentionally lightweight, enabling fast iteration.
Continuous Feedback Loops
We collect feedback from multiple sources:
Tooling
05. UX Strategy
Designing infrastructure that feels dependable
Clarity over cleverness
Infrastructure must be understandable at a glance.
Predictability builds trust
Especially when devices and data are at risk.
Design for failure, not just success
Recovery paths matter as much as happy paths.
Respect the user’s expertise
Reduce friction without hiding complexity.
Strategic Focus
- Make firmware workflows visible and controllable
- Reduce mental overhead as fleets scale
- Enable safe experimentation in dev, confidence in production
06. Business Impact
Unlocking value across the organization
Product & Platform
Established a scalable foundation for firmware and AI-ready devices
- Enabled secure, reproducible OS builds tailored to hardware
- Positioned Avocado OS as the backbone of the ecosystem
Sales & Marketing
- Clearer storytelling around a traditionally opaque problem
- Stronger demos and partner narratives
- Materials that resonate with both engineers and executives
Partnerships & Fundraising
Co-led NVIDIA Partner Program approval—expanding enterprise reach
Designed investor decks and fundraising materials used in capital raises
Translated deep-tech capabilities into narratives investors and partners understood
Approved into the NVIDIA Partner Program
I co-led the application process—designing the partner narrative, technical documentation, and presentation materials. Approval unlocked co-marketing opportunities, enterprise credibility, and direct access to NVIDIA’s AI and edge computing ecosystem.
07. Outcomes & Learnings
What Worked
Treating infrastructure as a design problem—not just an engineering one
- Deep technical empathy as a competitive design advantage
Using design as connective tissue across engineering, sales, and leadership
Writing production code to close the gap between design intent and shipped product
Fast feedback loops with customers over rigid internal process
Lessons Learned
- Firmware and platform UX require patience and precision
- Trust is the primary UX metric in infrastructure products
The best design decisions happen at the intersection of disciplines
Sometimes the most impactful design work is invisible—but foundational
“The most impactful design work doesn’t just improve interfaces—it bridges engineering, business, and customer needs into a product that scales.”