Heel erg bedankt! Dit is ook iets dat ik persoonlijk heel belangrijk vind.

😂 so true

Thanks! Much, much more on the way :)

Yes challenging users is important, I agree. There needs to be push and pull to achieve a result that's more well-sculpted to a possible solution in the "problem space". It's also how better learning and understanding happens, I think.

Thanks David, indeed I typically use 1080 x 1920 for desktop in most scenarios, unless A4 or Letter is required. It's good you ask, I should mention / discuss this in a future video.

Thank you Victor, the visualization in the bottom-right is a table that uses conditional formatting to display an icon. You can control it in the format settings for tables: Cell Elements> Series: Select your column > Icons: Enable > Style: Scroll down and select the style you like, this one uses X / ! / check. There's also other approaches to do this with custom icons, but this is how I achieved the result in this example.

Export to Excel is regularly a part of the conversation (*edit to fix spelling). It's a big topic, and it's possible that it is a defined endpoint in the user journey. That's why you have things like "Live Connected Tables". For instance: 1. Users might get an overview that they're on target 2. Breakdown to see which customers and areas are off 3. Use drillthrough to get details-on-demand for those customers; i.e. see at a material level what products are off. -- It's perfectly valid if a user prefers to do this in Excel. -- They can use live connected tables or analyze-in-excel to get that data and focus only on those customers (instead of playing where's waldo with numbers and wasting time to get that info). So the report still served a purpose and delivered value. They don't have to use the report for the entire process to get their answers if it doesn't work best for their needs or preferences.

We have the PDF available, but we will make this PBIX available after some other articles which will explain certain techniques that are used, here, otherwise it might be difficult to understand (and deconstruct) how certain things are done, and we don't want to confuse anyone. I also need time to convert this thin report example (which uses my "Data Goblins Dataset") to a thick report example that has some baked-in sample data.

That's a very good question, and a space that I personally like to occupy. One assumes in this space that the business has self-awareness that they don't understand the problem space or process, which is already a very good step. There needs to be some kind of workshopping or investigative phase where you work collaboratively with some business subject matter experts to define the process, scope, and problem, before discussing how one might address this. I personally believe that unless you're already heavily embedded in the business, you can only achieve this with regular engagements with business or even witnessing/participating in the process -- i.e. leaving the data for a bit to see things from the user / customer's point of view.

It always depends, there's no one answer to that. Generally, you want to try to focus on 2-3 key problems or questions per report page, but this is more of a "gut thing" than a "brain thing" if you get my meaning. I generally try to focus in on a single concrete business process.

New card visual and line chart. There are three charts that are part of the same group. The slicer is the new slicer button visual. Note that the "new" visuals are in preview, because they still have some issues and are under active development. They have more flexibility to achieve "elegant" designs, however, I also find that they take a very long time to format...

AOP stands for "Annual Operating Plan", and it's a common annualised business target for measuring performance. In this example, it's used as a target that the business defines at the beginning of the year for their different customers, regions, and product types. Throughout the year, (in this example) the business updates their AOP with monthly forecasts (FCST) that might adjust that target to better reflect the current context.