Building While Leading: Player-Coach Craft Leadership
How I operated as both a hands-on builder and a system-level leader to elevate product quality across a complex eSIM platform
UX Craft
B2B Systems
Complexity
A complex system grew fast, but without intentional design
Within the eSIM management ecosystem, the product had already grown in scope:
Multiple user types (clients, sales, operations)
Complex workflows (ICCIDs, package generation, troubleshooting)
Data-heavy interfaces (tables, filters, alerts)
However, the way the system evolved created a gap:
The product was functional, but not intentionally designed.
Most interfaces were initially built by developers, optimized for delivery speed rather than usability or system coherence.
Repetition without consistency across the product
From a distance, everything “worked.”
But inside the experience:
No consistent navigation logic across flows
No clear hierarchy in data-heavy tables
Actions and decisions buried inside dense screens
No progressive disclosure in complex flows (e.g. package generation)
Repeated patterns implemented differently across modules
This created friction not only for users, but for teams building on top of the system.
The product lacked a shared language.
My role: Player + Coach
Instead of separating leadership from execution, I operated in both layers:
As a Player (Hands-on)
Designed key flows end-to-end
Rebuilt complex interactions (filters, tables, request flows)
Introduced progressive disclosure in critical journeys
Defined structure for multi-step operations
As a Coach (System Builder)
Established a scalable design system
Standardized interaction patterns across modules
Defined UX principles for complex dashboards
Enabled the team to build consistently without rethinking every screen
UX craft decisions that matter the most
This was not about visual polish. It was about deep product craft.
1. Progressive Disclosure in Complex Flows
The package generation flow was previously overwhelming:
All inputs exposed at once
No guidance on sequence or dependencies
I restructured it into staged steps:
Input → Validation → Pricing → Confirmation
This reduced cognitive load and made the flow predictable.
2. Data-Heavy Table Optimization
The system relied heavily on large datasets (hundreds of items).
Key improvements:
Clear column hierarchy based on decision priority
Sticky actions and bulk operations
Advanced filtering aligned with real use cases
Inline actions instead of navigation-heavy workflows
3. Multi-Persona Navigation System
Instead of building separate tools for each team, I designed a unified system that adapts to different personas:
Sales → pricing, comparison, proposal generation
Operations → troubleshooting, alerts, filtering
Clients → eSIM management, usage control
One platform, multiple perspectives
4. Design System for Scale
To prevent future fragmentation:
Defined reusable components for tables, filters, forms
Standardized interaction patterns
Created consistency across modules
This reduced ambiguity for both designers and developers.
Unified workflows and improved system-wide consistency
Transformed fragmented interfaces into a coherent system
Reduced cognitive load in complex workflows
Enabled multiple teams to operate within the same platform
Improved speed and consistency of future development
Most importantly:
The product shifted from “built features” to a designed system.
Leading through UX craft, not distance from the work
This experience shaped how I approach leadership:
Craft is not something you delegate. It is something you model.
By staying close to execution while building systems, I was able to influence both the quality of the product and the way the team works.
© Ahmed Ramadan 2026
