Our firm is shifting from legacy systems to a cloud-native architecture, and I’m struggling to define my exact boundaries. As a Business Analyst, should I be focusing more on the high-level digital strategy and ROI mapping, or should I be deep-diving into the technical requirements for the API integrations? I want to ensure I’m providing the most value during this enterprise-wide pivot.
3 answers
In my experience leading a FinTech overhaul in 2023, the BA role is the "glue" that prevents the strategy from crumbling. You should absolutely be involved in the high-level ROI mapping because you understand the business value better than the devs. However, don't ignore the technical requirements. A great BA in a digital transformation context ensures that the business objectives are actually feasible within the new technical constraints. I spent about 40% of my time on stakeholder alignment and 60% on technical documentation to ensure no gaps occurred during the migration.
That's a tough balance to strike! Are you currently using any specific frameworks like BABOK or Agile to manage this transition, or is the leadership team playing it by ear? Sometimes the lack of a formal roadmap makes it nearly impossible to define those boundaries you mentioned.
Focus on the "Why" before the "How." If the API integration doesn't serve a specific business goal identified in your digital strategy, it's just technical noise that wastes budget.
Exactly, Thomas! I’ve seen so many projects fail because they focused on the tech stack rather than the customer journey. Alignment is the most critical KPI for any BA.
Robert, we are actually using a hybrid Agile-Waterfall approach. It’s chaotic because the business wants the speed of Agile but the fixed-budget certainty of Waterfall. I find myself acting as a translator between the executive suite and the Scrum teams daily. It’s definitely a test of my negotiation skills and my ability to manage stakeholder expectations under pressure.