I'm Naveen Kishore, an engineering-trained product designer focused on making complicated digital products easier to understand and use.
I enjoy problems most designers avoid — dense, regulated, multi-stakeholder systems where the real work happens before any screen gets designed. For Hospital OS, that meant mapping 11 operational domains, 42 departments and 443 real workflows before proposing a single interface.
Because I understand both design and implementation, I can collaborate closely with engineers, evaluate technical constraints and communicate product decisions beyond static screens.
01Product discovery
Understanding users, business goals, technical constraints and the actual problem before designing screens.
Hospital OS — 19 vendors and 42 departments researched before a screen existed. Ntɛm — two starting assumptions killed by the market data.
02Information architecture
Structuring dense products, workflows and content so people can understand where they are and what to do next.
Ntɛm — a merchant-partitioned order model that makes failure isolation and per-store tracking structural rather than engineered.
03Interaction design
Turning complex tasks into clear flows, states and interaction patterns that remain usable at scale.
Ntɛm — four adaptive routing models resolved into one plain-language question the customer can actually answer.
04Functional prototyping
Using high-fidelity prototypes and front-end implementation to test how product decisions behave in practice.
Ntɛm — three React apps sharing one live order object. Building it surfaced a flow bug the diagram had hidden.
