[01]Case studySupply Chain Performance
I redesigned fragmented supply-chain reporting into a hierarchy-aware investigation system—helping teams move from the KPI that changed to the driver behind it.
Complex operations do not need another dashboard. They need a clearer path to a decision.
[02]Case studyInventory Efficiency
I reconstructed an exception-first workflow that helps retail supply-chain planners detect low- and overstock risk, compare the relevant context, and move toward action.
Inventory risk should surface before it becomes an operational fire.
[03]Case studySupplier performance
I redesigned a legacy supplier scorecard into a comparison-ready reporting workflow—making KPI health, trends, and validation easier to review and discuss.
Supplier performance needs shared evidence, not another static score.
[01]Behind the interface
I connect product strategy, visual systems and interaction design to make complex products and workflows clearer—what people see, how things behave and what they can do next.
[02]Practice threads
[03]How I work
Calm, curious, collaborative, and rigorous—especially where a complex system needs human judgment, not just another screen.
Begin where the pressure is: what someone needs to understand, defend, choose, or move forward.
Give complexity a visible order—signals, exceptions, context, and a path to the next action.
Make the idea real enough to evaluate, while keeping the trade-offs and people in view.
[04]Recommendations
Jesal brings care for the community and a practical instinct for making complex work move! Through DesignX he stays close to the people in the room while still pushing the work toward a clearer decision.
DesignX · Founder & community collaborator
Head of Design at EQ Bank
Jesal sees both the product detail and the wider system it has to live inside — exactly the judgment SeaLab needs when the work spans product and operations.
SeaLab · Founder & CXO
Jesal asks the questions that make an idea concrete, useful, and easier to trust!
Rare Days · VP of Design & Mentor
Jesal brings structure to dense product problems without losing the people using the system! That balance is rare in NielsenIQ work that is both analytical and deeply human.
NielsenIQ · Design Buddy & Lead Designer
Jesal makes the complex parts understandable, intentional, and ready to act on!
NielsenIQ · UX Leader & Mentor
Sample testimonial copy for layout preview—not approved or supplied by the people shown.
[05]Fixed-scope Sprint
The Sprint is one way to start: clarify one critical workflow through a focused prototype and implementation plan. Website, product, design-system and other workflow enquiries are assessed separately. Production builds and integrations need their own scope and quote.
One way to work together
Starting fee, plus applicable taxes. Seven business days from confirmed kickoff and receipt of required inputs.
Discuss your workflowBest fit
A report is hard to interpret, a quote stalls at a handoff, or an AI-assisted step needs human review. Choose one problem, with a decision-maker and examples you can share.
Outputs
A focused review of your source examples and a map of the decision, information and handoffs. One focused interactive prototype with realistic states, implementation notes and a next-step recommendation.
[06]Sprint FAQ
The Sprint fits one recurring reporting, product-workflow or AI-assisted decision problem with a clear business consequence. A decision-maker needs to participate and share examples we can review. Website, brand and other broader projects are assessed and scoped separately.
A focused source review, a workflow and decision map, one focused interactive prototype with realistic states, implementation notes and a next-step recommendation. It covers one primary workflow and one consolidated review round. Production code, deployment, backend integration, data architecture, security certification, legal/compliance advice and complete product or website builds are outside the Sprint.
A decision-maker, access to people who use the workflow, and examples you can share, such as a report, form or current process. Scope, agreement and start conditions are confirmed before kickoff. The seven-business-day timeline begins from confirmed kickoff and receipt of required inputs.
The Sprint ends with the prototype, implementation guidance and a recommendation for what to do next. You can use the handoff with your team; further design, production engineering, integrations or ongoing support need a separate scope and quote.
[07]Career conversations
For roles, teams, and problems where careful systems thinking makes a difference.
