Complex workflows
Audit, compliance, customer operations, and other products where users need to understand what happened and decide what to do next.
Personal operating system · v2026
Berlin ↔ India · 52° N / 20° N
Chandrika — officially Sanapati Chandrika
I came to product design through computer science, operations, and banking. Now I untangle complex systems and shape them into products people can understand, trust, and actually enjoy using.

BERLIN · NEW ROOTS

INDIA · FIRST HOME

ALWAYS CURIOUS

Product designer
Probably asking “why?”
Field note #27
If it feels complicated, the design is not finished yet.
Audit, compliance, customer operations, and other products where users need to understand what happened and decide what to do next.
Human review, clear system status, correction paths, and safeguards against treating machine confidence as a substitute for judgement.
I turn interviews and usability observations into explicit product decisions, then show what changed and why.
Reusable components and consistent interaction patterns that help teams move faster without losing clarity or craft.
Path to product design
Each step added a different lens: technical, operational, human, and craft.
Technical foundation
Systems and execution
Trust and service
Research and craft
Shipped B2B AI work
Working principles · 03
Quiet reminders for when the work gets complicated and the answer is not obvious.
01 · clarity over cleverness
Design that needs a user manual has already failed.
02 · listen harder
Good research asks uncomfortable questions — and sits with the silence.
03 · both, always
Systems thinking — and then humanity.
Design community · Vienna, Austria
Three days of fresh perspectives, generous conversations, and the kind of questions that follow you home.

What stayed with me
"The room was full of people who see the world differently, and I left seeing it differently too."




