0-to-1 product · client engagement
An education brand and digital platform I led from initial brand direction through product structure, user experience, visual design, and a reusable design system — translating an education-business concept into a cohesive, launch-ready product. Built for a client.
HikmahEdu needed to exist as a credible, coherent institution online — not just a website. I led the 0-to-1 build: brand positioning and identity, product and information architecture, UX and visual design, a design system that bridged brand and code, and the platform itself. The distinctive work is the design-to-engineering system that turned brand decisions into maintainable interface primitives.
Led the full 0-to-1 as designer and engineer for the client: product ideation, brand development, UX architecture, visual direction, design-system design, technical decisions, application development, and launch. I was not handed finalized Figma — I produced the direction and carried it through to a shipped platform.
Content & Administrative Layer (CMS)
↓
Content Models & APIs
↓
Application & Rendering Layer
↓
Reusable Design System (tokens → components)
↓
Public Website, Profiles & Member Experiences
↓
Analytics, SEO & External IntegrationsA CMS-driven content layer feeds typed content models through a rendering layer built on a reusable design system. The system separates content configuration from presentation, so non-technical authors can publish without engineering involvement.
The most valuable work was bridging brand and code. Brand decisions were encoded as a token layer that downstream components consumed directly:
This is what keeps a brand-driven site from becoming unmaintainable — a flexible visual system expressed as deterministic engineering primitives.
Context: Editorial flexibility and visual consistency pull in opposite directions.
Decision: A token-and-primitive design system: authors compose within constrained, on-brand components rather than free-form layouts.
Tradeoff: Less per-page creative freedom, in exchange for a site that stays coherent and maintainable as it grows.
Context: The site must serve both visitors and content administrators.
Decision: A CMS-driven content-model layer that separates content configuration from application code.
Tradeoff: Up-front modeling investment, in exchange for authors publishing without engineering.
Context: Everything can't ship at launch.
Decision: A defined launch scope with membership and monetization deferred to a roadmap, keeping the first release achievable.
Tradeoff: Deferred revenue features, in exchange for a credible, shoppable launch sooner.
Carried an ambiguous idea through implementation: product ideation, business requirements, brand development, UX architecture, visual direction, technical decisions, application development, content-system design, deployment, and stakeholder communication — communicating fluently across technical and non-technical concerns.
A cohesive, launch-ready brand and platform where brand strategy became design tokens, design tokens became reusable components, and those components became a maintainable, CMS-driven site — demonstrating 0-to-1 product ownership, design engineering, and product strategy end to end.