Member-only story
Breaking Out of the Table: Business Analysis for NoSQL Databases
As NoSQL databases become more common, BAs need to rethink traditional data practices. This article explores how to adapt analysis techniques for flexible data models.
Hey BAs, how are you all? If your brain’s been feeling a little too ‘relational’ lately, this one’s for you. You know the moment — you walk into a new project, expecting clean entity relationships and tidy table joins… and instead, you’re handed a sprawling blob of nested JSON. Yep, you’re not alone. The rise of NoSQL databases like DynamoDB is changing the game. And for us business analysts, that means it’s time to break out of the table.
In this article, I want to share what I’ve learned from real-world projects where traditional modelling techniques didn’t quite fit. We’ll go through what makes NoSQL different, what questions you should be asking, and how to adapt your analysis so it still delivers real value — no matter how the data is stored. Along the way, I’ll highlight insights on how BAs can lead in flexible, evolving data environments.
