Why Anveshna exists
Anveshna started from a simple observation: the hardest problems in an organisation are rarely technical. They are about ownership, trust and how people actually behave under pressure — and those are solvable with the right approach.
The journey
My path into this work started in engineering and quality — specifically vehicle testing and launch quality, where a single missed defect has a real, visible cost. TODO-CONFIRM: add exact years and the specific point where the shift from technical to people-focused work happened, once confirmed.
That background shapes how Anveshna works now: diagnose before prescribing, and judge an idea by whether it holds up on the shop floor, not just in a workshop room.
Credentials
TODO-CONFIRM: add confirmed credentials, certifications or qualifications here once provided.
Collaborators
TODO-CONFIRM: add any named collaborators, institutions or co-facilitators here once confirmed and agreed.
Ready to start a conversation?
A short, no-pressure call to understand where you are, before anything is proposed.