Jesal Chitalia — About my work
Updated September 2026
Who I am
I’m an AI Product Designer and Design Engineer building decision-ready systems. I turn complex workflows into clear, interactive products by combining product strategy, visual systems, art direction, and agent-assisted building.
I work with teams facing dense workflows, unclear handoffs, high-stakes information, or AI-assisted systems that still need human judgment.
How I think
What do you notice first when a product is difficult to use?
I look for the decision under the screen: where the burden lands, what context is missing, and what someone must remember, reconcile, or infer before they can move forward. Good product design makes relationships visible and reduces unnecessary cognitive load.
How I work
What do you delegate to AI—and decide yourself?
I use AI and agents to help turn voice, research, source context, critique, and rough ideas into structures I can inspect. They accelerate making; they do not replace my responsibility for framing, tradeoffs, taste, or final judgment.
What does working with you look like?
I explore broadly, make the system visible, then converge with the people closest to the work. Voice notes, visual maps, prototypes, documentation, decision records, and review loops help preserve intent between an early idea and a usable result.
What I’ve built
What changed your mind on a project?
The useful shift is often not a cleaner screen on its own, but a better way for a team to make a decision. The Inventory Efficiency work reorganized fragmented reporting into an issue-detection and investigation workflow. The Vendor Scorecard made supplier performance, comparison, and validation easier to inspect in one shared path.
For a focused engagement, the Decision-Ready Systems Sprint is how I help clarify one difficult workflow, prototype the critical interaction, and define what should be built next.
Experience and history
Across enterprise B2B SaaS, mobile product teams, agency work, and independent practice, the through line is the same: make complex information easier to understand, use, and act on. For the detailed timeline and role context, read my resume.
How I manage design systems
When do you reuse, extend, or create a component?
I start with the repeated decision and behavior—not a library for its own sake. I reuse a stable pattern when it already carries the right intent. I extend it when the underlying behavior is shared but the context needs a clear, documented variation. I create something new only when the workflow has a genuinely new job to do.
A useful system includes more than components: it preserves visual language, interaction contracts, source context, and the decisions behind them. The goal is to reduce rework and cognitive load without flattening exploration.