The 7 Deadly Sins of Business Analysis (and What to Do Instead)
Key Takeaways
- Many business analysis failures aren’t random—they’re recurring, preventable patterns
- Defining the real problem (not just the requested solution) is the foundation of effective analysis
- Active listening and validation are critical to avoid assumptions and misaligned requirements
- Missing organizational context leads to incomplete or conflicting solutions
- Skipping process analysis results in solutions that fail in real-world workflows
- Resistance to change can limit innovation and prevent better approaches from emerging
- Analysis paralysis delays progress; iterative, just-in-time decisions improve outcomes
- Continuous learning and openness to feedback are essential to staying effective as a business analyst
- Simple habits and self-checks can significantly reduce costly mistakes and improve project success
Disclaimer: The views and opinions expressed in this article are those of the author and may not reflect the perspectives of IIBA.
After more than twenty years working in business analysis—teaching it, coaching it, and practising it—I’ve seen the same mistakes surface again and again, across projects of every size and organizations of every type.
The frustrating truth about these errors is that most of them are entirely preventable. They tend to share a common root: moving too fast when the moment calls for slowing down and doing the real work of analysis.
I call them the Seven Deadly Sins of Business Analysis.
More than once, I’ve had to ask forgiveness from my project manager, product owner, or fellow business analysis professionals. Bless me, for I have sinned!
The good news? If you’ve committed one of these business analysis sins, redemption awaits.
Deadly Sin #1: Lack of a Clear Problem
One of the most costly mistakes in business analysis is accepting a solution request and diving into requirements without first understanding the problem.
Often, stakeholders don’t fully understand the problem and offer a solution that doesn’t really fix it. We end up implementing temporary fixes while the root cause remains. Effective analysis work should always begin with a shared understanding of the problem we’re trying to solve.
Fortunately, there’s help. The antidote is to use a structured problem statement.
Pro tip: Before any work begins, use a structured problem statement: "The problem of _______, affects _______, the impact of which is _______, and a successful solution would _______." Describe what you think the problem is, list the stakeholders affected by the problem, and explain how the problem impacts them. End with what a successful solution would do.
Deadly Sin #2: Failure to Listen and Communicate
Business analysis professionals spend a great deal of time in conversation: interviews, workshops, walkthroughs, and reviews. But there’s a big difference between being present in a conversation and truly listening to what’s being communicated.
Stephen R. Covey said, “Most people do not listen with the intent to understand; they listen with the intent to reply." When we’re eliciting information from stakeholders, we need to focus on understanding what is said.
Don’t move forward with unvalidated assumptions, thinking you have the answers based on your own experience. Pause to hear what’s said and follow up on things that don’t make sense or contradict what you’ve learned. Once you’ve listened, translate what you hear into clear, concise requirements, then communicate them to your team.
Pro tip: When a stakeholder shares something significant, reflect on it before moving on: "What I'm hearing is _______. Is that right?" Ask follow-up questions that go deeper: "Tell me more about that. What does that look like in practice? What happens when that breaks down?" Being willing to change direction based on what you hear is central to the business analysis role.
Deadly Sin #3: Missing Context
Context is critical in business analysis. Understanding the circumstances surrounding an area of study is essential to developing a solution.
It’s entirely possible to document a beautiful, internally consistent set of requirements that are nonetheless wrong. This happens when analysis is conducted in isolation, without a full picture of who and what interacts with the system or process in question.
Departments get missed. External systems go unidentified. Regional variations, exceptions, or contractual constraints never make it onto the page. Requirements that look complete from one angle can create contradictions and breakdowns when they reach the rest of the organization.
Pro tip: Draw a context data flow diagram before writing a single requirement. It places the area of study at the centre and maps every external entity that gives or receives data for your project. Each entity represents a stakeholder to engage and a data flow to understand. What’s invisible in prose becomes visible in a diagram.
Deadly Sin #4: Omitting Process Analysis
Everything we do is a process, so it’s important to map the steps in how work actually flows. Requirements that describe what a system should do, without accounting for how work flows through the organization, are requirements waiting to fail.
Most people work in silos, understanding their own tasks without considering how changes affect the broader process. Decisions are often made without accounting for end-to-end impact.
When business analysis professionals skip process analysis, they design solutions for an idealized version of the organization rather than the real one. The result is a system that looks good on paper but breaks immediately in practice.
Pro tip: Before writing requirements, document the process from end to end. Map every step, every handoff, every approval, and every exception, including the informal ones. Pay special attention to the moments when someone says, "Well, when that happens, we usually just..." Those are gold. They reveal the real workflow, constraints, and requirements. A workflow diagram also surfaces broken steps before you accidentally automate them. Automating a broken process only makes it break faster!
Deadly Sin #5: Resisting Change
Everything I work on is a change for someone. Most of us don’t like change (unless it’s our idea). Over the course of your career, you’ll hear “We’ve always done it this way” more times than you can count.
Experience is an asset, but it can also be a liability if you’re not careful. The longer we’ve done something a particular way, the easier it becomes to mistake familiarity for correctness. New techniques get easily dismissed.
Business analysis professionals should be change leaders—champions of trying new things. We must embrace change and help others do the same, looking forward to what could be rather than back at what has always been.
Pro tip: Treat suggestions from others as data worth evaluating, regardless of where they come from. When you hear yourself defaulting to "We've always done it this way," pause and ask whether that’s still true, and whether it should be. A learning mindset doesn’t mean abandoning your expertise. It means staying open to the possibility that there may be a better way.
Deadly Sin #6: Analysis Paralysis
There’s never enough time or information for business analysis professionals! We always want to understand more.
When the pursuit of complete information prevents the delivery of any information, the project suffers, and the requirements that finally arrive are often no more accurate than earlier drafts would have been. The fear of being wrong is understandable. But waiting for certainty that never arrives is its own form of failure, and an expensive one.
We must become comfortable making decisions with the information we have at the time. Moving forward with what you know is a sign of leadership.
Pro tip: Iterative, just-in-time delivery of requirements isn’t a compromise; it’s best practice. Share early drafts. Use workshops to validate as you go. Make incremental decisions rather than waiting for a complete picture. The sooner you get feedback, the less costly the corrections. Progress builds trust, while extended silence builds anxiety. Be comfortable with rework as you learn more and need to adjust.
Deadly Sin #7: Lack of Continuous Learning
Business analysis is a discipline that evolves. The tools, techniques, and contexts we work in continue to change. A business analysis professional who stops learning, relying entirely on experience without curiosity for new approaches, gradually becomes less effective—often without even realizing it.
This sin often shows up subtly: feedback that gets acknowledged but not acted on, suggestions that get dismissed, professional development that keeps getting deprioritized.
Pro tip: Receiving feedback is a skill, and so is acting on it. If multiple people point to the same pattern—even gently—it’s worth taking seriously. Continuous learning doesn’t require a conference registration or a new certification. All it requires is the discipline to stay curious and the humility to accept that your current best may not be your only option.
The Path to Redemption
None of these sins dooms you to failure, and they aren’t solved by better software or bigger budgets. They’re addressed through discipline, humility, and a willingness to slow down when the work demands it.
A simple self-check before and during any project can make a meaningful difference:
- Did I define the real problem, not just the request?
- Did I truly listen, or did I simply collect confirmation?
- Did I draw the picture big enough to see all the stakeholders?
- Did I walk through the actual process before writing the requirements?
- Am I staying open to new approaches and to feedback I don't always love?
- Am I moving the work forward or waiting for perfection?
- Am I still learning? Am I open to new ideas, approaches, and designs?
These questions are simple, but they require ongoing commitment to ask them and answer them honestly.
The best business analysis professionals aren’t without sin. They build habits that make costly mistakes less likely.
Quick Reference: The 7 Sins and Their Antidotes
Sin #1 — Lack of a Clear Problem → Use a Structured Problem Statement
Sin #2 — Failure to Listen and Communicate → Practise Active Listening
Sin #3 — Missing Context → Draw a Context Diagram
Sin #4 — Omitting Process Analysis → Create a Workflow / Process Diagram
Sin #5 — Resisting Change → Embrace a Learning Mindset
Sin #6 — Analysis Paralysis → Practice Iterative, Just-in-Time Decisions
Sin #7 — Lack of Continuous Learning → Stay Curious, Act on Feedback
Feeling guilty? Find your path to redemption—and better practice—in the BABOK Guide.
About the Author
Heather Mylan-Mains, CBAP, MBA, CSM, Prosci, is a business analysis consultant, instructor, and speaker with over twenty years of experience. She helps teams and organizations do better analysis through clearer communication, stronger listening, and more human connection.
