How to make sure your reports don’t collect cobwebs.

Three ways requirements gathering fails:

  • It doesn’t happen.

  • It only happens in the form of a support ticket (i.e. “Build this report for me”)

  • The data person asking the questions has no idea what to ask.

Three ways report documentation fails:

  • It doesn’t happen.

  • Only a small part of the process is documented but then never updated

  • The data person writing the documentation has no idea what to document.

Before you solve technical problems you have to solve process gaps. Requirements gathering and documentation are two thorns on the side of every data team I’ve worked with.

So, yesterday I sat down with my friend Ahmad for a Data Roundtable conversation to offer practical tools and perspective on how we solve these chronic issues.

If you want a long-term and strategic view of business intelligence reporting, this webinar is for you.

Watch the reply here:

Data Roundtable - Power BI Leadership

I’m glad you are here,

Sawyer

Previous
Previous

What is a data platform?

Next
Next

Data and Digital Transformation in the Northern Woods of Michigan