Building a single report can be an uphill battle, especially when the requirements are vague. Where do you even start when the list of report requests is in the dozens--or even hundreds?

While the demand for new in-house Power BI reports can spike for any number of reasons, the need to tackle report development in "bulk" is especially common when organizations migrate from a legacy reporting system into Power BI. Companies sometimes make this transition as a standalone project, or as part of a larger ERP Migration. Either way, the resulting workload can be hard to digest.

What steps can an organization take to minimize the time required to build each report? How do we untangle "needs" from the "wants" without letting anything critical slip through the cracks? Is there a way to validate the reports if a data migration is delayed? What strategies can we employ to keep track of the workload and ensure transparency into the process? (Hint: it's definitely not an Excel workbook)

Lenore will share key lessons learned from her experiences working on similar "bulk reporting" projects, both internally, as a former reporting "SME" (subject matter expert) and externally, as a current BI consultant who supports similar transitions.

Key topics will include:
- Best practices when preparing for a future data or reporting migration
- How investing the effort into certain Power BI features, such as templates, shared semantic models, and deployment pipelines can pay long-term dividends.
- Strategies for leveraging related Microsoft technologies, such as Power Automate and Azure DevOps, to streamline requirements gathering efforts and cut down on administrative burden.