Stakeholder interviews, gap analysis, and writing requirements that engineering and business both stand behind — without ambiguity left for the sprint to resolve.
Current-state mapping, bottleneck identification, and future-state blueprints that are operationally realistic — not theoretical flowcharts that gather dust.
Turning raw operational data into the decision-supporting view leadership actually needs. SQL, Excel, Power BI — chosen by fit, not habit.
Bridging the translation gap between technical teams and business owners. Facilitating workshops where competing priorities surface and resolve.
Business case development, vendor evaluation, and change readiness assessment for organizations mid-transformation who need a steady analytical hand.
Product backlog refinement, user story writing, and sprint planning participation that keeps delivery aligned to business value — not just velocity.
Embedded with mid-market and enterprise clients across FinTech, logistics, and healthcare. Led end-to-end BA engagements from discovery through UAT sign-off. Reduced average requirements rework by 35% by introducing structured elicitation frameworks across three client accounts.
Anchored the BA function for a 3-year ERP migration affecting 1,200 users across six business units. Owned the requirements traceability matrix and facilitated 80+ workshops. Identified ₹12 Cr in annual process savings as a direct outcome of the current-state analysis.
Supported strategy and operations engagements for retail and BFSI clients. Built financial models and operational dashboards used in board-level presentations. Trained two junior analysts in structured elicitation and documentation practice.
Supported project teams in capturing functional specifications and coordinating between development and client teams. Built a personal documentation framework that was later adopted as the team standard.
I don't arrive with a template. Every engagement starts with a genuine attempt to understand what the organization actually needs — which is usually different from what was put in the brief.
My job is to ask the question that reveals the real constraint, document it so it can't be argued about later, and translate it cleanly enough that delivery teams can act on it without a translator.
The first priority is understanding — not fitting the problem into a methodology. I spend the early sessions listening, and only then reach for tools.
Assumptions left unstated become the cracks that projects fall into. I surface them in workshops and get them on record — agreed or challenged.
Deliverables are written for the next analyst who picks up the work in two years — not to fill a template or close a project phase.
When the path forward is unclear, I stay at the table. A good analyst doesn't hand off uncertainty — they reduce it until the team can move.
Whether you're scoping an engagement, evaluating fit for a project, or just want a conversation about a problem you're wrestling with — I'm easy to reach.