Trying to understand what makes a good business analyst
Some conversations at work pushed me to think about moving toward a business analyst career, but I’m still trying to understand what actually defines a “good” BA. People keep mentioning problem-solving and facilitation, but I’m unsure how much of that can be learned or improved through courses. My background is mostly in operations, and while I deal with procedures and process gaps, I’ve never formally done requirements gathering. Anyone with experience—how did you figure out what skills mattered most before committing to any program or training?
17 Views
.png)

Early on, many people feel unsure about which skills matter first, and that’s normal. A strong BA usually uses a mix of structured analysis, clear communication, and adaptable planning, especially in agile environments where things shift quickly. When I needed a grounding point, a helpful resource was the AgileBA certification because it breaks down the BA role inside agile teams and explains why certain skills matter more than others. It doesn’t just list theory but shows how requirement work, stakeholder input, and iterative delivery connect in practice. For someone with an operations background, it can provide clarity on how to turn everyday problem-solving into defined BA techniques. If you want a program that’s practical and structured, this one gives a strong foundation.