Familiar patterns
Kept familiar terms and steps while simplifying the overall process.
Webiks
Designing across a complex, multi-application ecosystem
At Webiks, I owned design across nine applications in a complex ecosystem, from product strategy and user research to technical implementation and design systems.
Working across the ecosystem
The work extended beyond individual screens. Each design decision had to support multiple products, stakeholders, and technical teams moving in parallel.
I worked closely with cross-functional development teams and product managers to connect design decisions with technical execution, maintaining clarity and consistency across a large, interconnected product environment.
9
applications designed
6
development teams
20+
product managers
Reinventing communication equipment regulation
I led the design of a new way to register and regulate communication hardware. It replaces outdated methods by bringing technical data, compliance checks, and approvals into one clear workflow.
Product Problem & Approach
The new system had to replace a familiar process while making complex information clear for users with different roles and levels of expertise.
Hardware engineers shaped the work. I turned their input into improvements that served all users.
Progressive disclosure
Interface starts simple, then reveals technical detail when users need it.
Role-based design
Each person sees tasks and decisions relevant to their part of registration.
Scalable foundation
Built to grow with new hardware, rules, approval steps, and features.
Sanitized interface mockups
One map, three systems
The ecosystem connects three systems that manage map entities across the full timeline: planning, real-time operations, and past reviews.
The real time system was the flagship product: a real-time map serving thousands of high-profile users.
Before the redesign, it had splintered into separate tools. I brought it back into one flexible product.
Problem & Approach
The system is critical for planning and execution of missions. Before the redesign, it had become a patchwork of different designs built by separate teams.
Patchwork of designs
Built by separate teams with different approaches and no shared design language.
Critical for missions
Every function moved or changed has to be spot on.
One size fits none
Different functions need different tools: tables, monitoring, map views.
Sanitized interface mockup
User-configurable views
People choose which modules are visible and which stay hidden.
Modular architecture
Features built as independent pieces that plug in without disruption.
One system, many perspectives
A single adaptable platform replacing scattered tools.
Monitoring field systems in real time
I designed a dashboard for monitoring field-deployed systems: their status, temperature, services, components, and alerts.
It replaced scattered email-based reports that were constantly updated and circulated manually.
Problem & Approach
The core challenge was deciding what to show, how much detail to include, and how to lay it out.
The dashboard had to surface critical alerts without overwhelming users, while still giving them the full picture at a glance.
Centralized dashboard
Replaced many scattered tools and monitors with a single dashboard.
Alert-first design
Critical issues surface prominently so operators see problems before anything else.
Card vs. table
Toggle between a card grid for quick overview and a table view for detailed inspection.
Sanitized interface mockup
Raising the bar
I lifted the level of design and execution by pushing teams to adopt modern tools, work closer to implementation, and hold products to a higher standard.
Adopting new tools
Pushed new products and flexible teams to adopt React, design systems, and Storybook.
Hands-on approach
Worked directly on systems rather than just in Figma, closing the gap between design and implementation.
Pushing for quality
Advocated for redesigns of fragmented, messy systems to improve the overall product experience.
