Skip to main content

Analyst’s Edge

Search This Blog

Contact

Get link
Facebook
X
Pinterest
Email
Other Apps

Get in Touch

Have questions, feedback, or collaboration ideas? I'd love to hear from you!

You can reach me at: 📧 email2.chetna0510@gmail.com

Get link
Facebook
X
Pinterest
Email
Other Apps

Comments

Post a Comment

Have thoughts or questions? I’d love to hear from you, drop a comment below!

Popular Posts

McKinsey-Bennett 9-S Strategy Framework

Every organisation strives for clarity, cohesion, and competitive advantage. Yet even the best-laid plans can stumble when internal elements lack alignment. The McKinsey-Bennett 9-S Framework provides a roadmap for diagnosing and fixing gaps between strategy and execution. An outgrowth of McKinsey’s classic 7-S model, the 9-S framework adds two critical dimensions Synergy and Strategic Performance to ensure that collaboration and results don’t fall through the cracks. In this blog post, we’ll explore each of the nine components in depth, see how they interact, and look at real-world examples that illustrate how companies use the 9-S approach to drive meaningful change. 1. Strategy The set of guiding choices and action plans an organisation adopts to achieve long-term goals and sustain a competitive advantage. Key Questions: What market position are we aiming for? Which customer needs do we serve, and how? How will we allocate resources to win? Example: A mi...

Why Business Analysts Should Document "What We Won’t Do"

As Business Analysts (BAs), we often pour our energy into discovering, documenting, and refining what a system should do. But here's a critical element that often goes unnoticed and undocumented: what the system won't do. This simple practice can be the difference between a smooth project and a frustrating one derailed by misunderstandings, scope creep, and rework. The Importance of Documenting "Out of Scope" 1. Prevents Scope Creep Scope creep happens when new features or changes are added to a project without proper evaluation, approval, or impact analysis. Documenting what is not included sets clear boundaries. It becomes your first line of defence when stakeholders try to slide in new requests mid-project. Example: In a customer portal redesign project, the team agreed to improve the login experience and dashboard UI. Midway, a stakeholder asked, "Why aren’t we also adding a chatbot for customer support?" Having an "Out of Scope" section tha...

Common Mistakes New Business Analysts Make (And How to Avoid Them)

Stepping into the role of a Business Analyst (BA) is both exciting and overwhelming. You get to solve problems, communicate with different teams, and contribute to building something valuable. But let’s be honest — at the beginning, it can feel like you’ve walked into a room full of unspoken rules. When I started my BA journey, I made mistakes. Lots of them. But those mistakes helped me learn faster and become better at my job. In this blog, I want to share the most common mistakes I’ve seen (and made) as a new Business Analyst, and how you can avoid them. 1. Assuming the Requirements Are Clear One of the biggest traps for a new BA is assuming that if something was said once, or written down, it must be clear to everyone. Spoiler alert: it's not. Even a single sentence like “Allow users to log in with social media” can mean different things to different people. Which social platforms? How should the data be handled? What happens if the login fails? What to do instead: Ask cl...

Powered by Blogger

2025 Analyst’s Edge. All rights reserved.