Hello Analysts, today I want to share with you my reflection on one of the most impactful parts our role - Discovery 🧐

Many assume that the most critical phase of a project for a Business Analyst is during development, when requirements are implemented and validated.

But in my experience, the real challenge—and the most intellectually rewarding part—lies in the presales and discovery phases.

During discovery, the work goes far beyond gathering requirements. It’s about designing solutions that are tailored to unique business environments, identifying the root problems behind client requests, balancing business objectives with technical feasibility, and navigating ambiguity with clarity and structure.

This is also where Business Analysts can deliver the highest value—by shaping the direction of the solution before it’s built. When a BA is involved early, they can:
- Influence scope and priorities before they are locked in
- Ensure the real business problems are identified—not just the symptoms
- Help the client or internal stakeholders reframe their needs in terms of outcomes
- Facilitate early alignment between business, design, and technology
- Lay the foundation for smoother development and fewer change requests later
From a personal growth perspective, being involved in discovery sharpens your analytical thinking, stakeholder management, commercial awareness, and ability to operate in unfamiliar domains. It also exposes you to strategic decision-making, which is often limited in later project phases.

What I enjoyed the most is the variety and depth: each project introduces a new business model, operating context, ROI logic, and user behavior landscape. It feels like solving a unique puzzle every time.

How do you approach discovery? What techniques or mindsets have helped you deliver the most value in this early stage of a project ❓

#Discoveyphase #BusinessAnalysis #PresalePhase #BusinessAnalyst

🤖 How do you design processes in BPMN to effectively resolve business challenges?

At our meetup, “Process Automation with Camunda: A Systems Analyst’s Perspective,” we’ll tell you about designing processes in BPMN using Camunda 8, including architectural components, automating processes in FinTech, and its benefits and challenges.

Speaker: Viktoryia Filipava, Senior System/Business Analyst at Andersen with 10 years of experience. Domains: FinTech, Logistics, Telecom.

🎟 Register here

📅 Time: 18:30 (Minsk time)/17:30 (СEST)
🕒 Duration: 1 hour
🗣 Language: Russian
📍 Offline: Andersen’s office in Minsk
💻 Online: The link to the stream will be sent to your email specified in the registration form

Join Analysts Hub on LinkedIn:
📱 BA/SA: LinkedIn

See you at the meetup!

Bugs resolution as a BA/SA 🔭

Bugs resolution is a tricky task for a BA/SA. Intuitively, one might strive to fix them as quickly as possible without taking the time to look deeper. Simply rushing to fix the issue might lead to solving the wrong problem or working on something that brings no business value.

🧾 Here is a short checklist for handling bugs:

1. Identify the impact of the bug on valuable business operations
If possible, collect some metrics. For example, the number of users affected.

Remember: Labels like urgent, blocker or highest priority in your Jira task can be helpful if the problem is obvious and clearly critical. But if the situation is not clear, don’t rely on labels alone to support the prioritization.

2.Identify the root cause of the bug
It’s important to understand the root cause of the bug in order to find the best solution, rather than settle with a workaround that won’t cover all the edge cases.

3. Choose the best solution
Brainstorm and weigh your options. Depending on the business value, the most comprehensive solution might be worth some extra development time. In other cases, you should stick to the fastest workaround.

4. Do a blameless post-mortem analysis
You should reflect on the reasons the bug occurred and check if other parts of the product are at risk of similar issues. The key here is to create action items.

Community, how do you handle situations when business stakeholders come in strongly insisting that a particular bug is critical and needs to be fixed immediately❓

#BusinessAnalysis #SystemsAnalysis #RootCauseAnalysis #Prioritization #ProblemSolving #SoftwareQuality

🔥 Attention BA Community! 🔥

Our meetup “Process Automation with Camunda: A Systems Analyst’s Perspective” is starting very soon!

If you want to learn how to design BPMN processes effectively to solve business challenges using Camunda 8, don’t miss this event. We’ll cover architectural components, process automation in FinTech, as well as benefits and challenges.

⏱ Time: 18:30 (Minsk) / 17:30 (CEST)

Join us live online

Summer is a great time to enhance your skills 🔥

Let's figure out how to train analysts from scratch and see real progress.

At our meetup on August 14, Diana Krylovich – Senior System and Business Analyst at Andersen – will break down how to organize training of analysts: where to begin, how to explain complex topics in simple terms, and how to objectively assess progress.

We invite everyone, especially Middle+ level business and system analysts!

🎟 Register here

⏰ Time: 19:00 (Minsk time)/18:00 (CEST)
🕒 Duration: 1 hour
🗣 Language: Russian
📍 Offline: Andersen’s office in Minsk
💻 Online: The link to the stream will be sent to your email specified in the registration form

See you! 🙂