Hola. Es espectacular el conjunto de enseñanzas del video y lo simple que lo hacéis. Con vosotros siempre se tiene algo así. Muchas gracias por todo lo que personas como yo estamos aprendiendo con vosotros.
Where I work we use the Faberge Organic Shampoo rule from the 70s TV commercials. An executive asks a question, and his or her direct reports will email 2 of their direct reports, who will email 2 of their direct reports, and so on and so on and so on ... and then the executive gets 4 different answers 3 weeks later. I think the 3-30-300 rule is MUCH better!
Admittedly it seems I'm 6 months late (life happens), but welcome Kurt Buhler! Your Data Goblins Blog helped me out greatly over the past couple years. I really appreciate how this content is presented. It's important to take the time to get to know what the users of a report want. Too often we get bogged down in getting the next report out only to find later that the people who wanted it don't use it. The information presented here shows that taking more time and care to create an effective report is better for everyone. I related so much to the "data dump" report. Keep up the fantastic work!
Wat een geweldige video weer. Toevallig was ik gisteren met een collega in gesprek over dit onderwerp en besloten we dat we hier iets mee zouden moeten gaan doen. Perfecte timing dus. Complimenten over de manier waarop je presenteert, rustig en af en toe wat herhaling om de boodschap nog duidelijker over te brengen.
It’s just incredible how you make easy to understand (not to do) what you should be focusing on when designing reports. Thanks @Kurt and @SQLBI for the insights. This is a video I’ll watch again and again
Amazing approach, Kurt! It's important to do not forget the main objective of the calculations that we put hard work on. If our internal or external customers are not able to gather the critical business information required, so our job wasn't done in the most efficient way! I wonder, is there any project, personal or not, that you are engaged in? I want to know people that are dived into this knowledge. Let me know if you have!
Really solid examples of action-based dashboard. Great work. I'm always refining my approach to understanding the action that clients take based on the data; I'm definitely bookmarking this video.
Excellent tutorial Kurt! Thanks to your clear guidance, it was easy to grasp how the reports could be more efficient and effective. Thank you for the content. Much appreciated!! Big fan of you guys :)
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.
More content like this! I loved one video from Curbal which explained the importance of identifying the screen size of users in order to choose the layout of the report
Fantastic video! Always easy to forget about the audience/customer! I will keep this practice in mind thankyou! Could you do a video about best canvas size? These examples all seem to use more pixels then default
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.
Great video. Thanks. My comment is that data analysts should be more confident and challenge those who ask for everything on one page if the mission is to inform people and make decisionsul using PBI. Often, more senior employees who don't know new technologies well enough request things in a format that's not practical and that has to change.
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.
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.
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.
Good video and and agree with idea in behind, but what about Power BI tool it self? Is it easy to learn? Is it clear with what to start learn Power BI? Is it intuitive and how many exceptions in functionality need to keep in mind when You start to use it. So what is 20/80 needed to know in Power BI to get in average knowledge? Can be applied rules like 3/30/300 to Power BI tool it self? Sorry for to much questions above but its not fair that to create something simple and easy to read by going through madness to create it.
What do you guys recommend on doing when the process is not too clear even to the business people, therefore they don't even know the questions they are trying to answer. Any tips?
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.
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.
"There is a difference between a report that looks nice and a report that is useful" I 100% agree.
Excellent video - one of the major problems for fast growing companies is ensuring good quality feedback and engagment
Hola. Es espectacular el conjunto de enseñanzas del video y lo simple que lo hacéis. Con vosotros siempre se tiene algo así. Muchas gracias por todo lo que personas como yo estamos aprendiendo con vosotros.
Where I work we use the Faberge Organic Shampoo rule from the 70s TV commercials. An executive asks a question, and his or her direct reports will email 2 of their direct reports, who will email 2 of their direct reports, and so on and so on and so on ... and then the executive gets 4 different answers 3 weeks later. I think the 3-30-300 rule is MUCH better!
😂 so true
Admittedly it seems I'm 6 months late (life happens), but welcome Kurt Buhler! Your Data Goblins Blog helped me out greatly over the past couple years.
I really appreciate how this content is presented. It's important to take the time to get to know what the users of a report want. Too often we get bogged down in getting the next report out only to find later that the people who wanted it don't use it. The information presented here shows that taking more time and care to create an effective report is better for everyone. I related so much to the "data dump" report. Keep up the fantastic work!
Wat een geweldige video weer. Toevallig was ik gisteren met een collega in gesprek over dit onderwerp en besloten we dat we hier iets mee zouden moeten gaan doen. Perfecte timing dus. Complimenten over de manier waarop je presenteert, rustig en af en toe wat herhaling om de boodschap nog duidelijker over te brengen.
Heel erg bedankt! Dit is ook iets dat ik persoonlijk heel belangrijk vind.
Great tips, grazie Kurt ! You bring SQLBI to a whole new level 👌😊
It’s just incredible how you make easy to understand (not to do) what you should be focusing on when designing reports. Thanks @Kurt and @SQLBI for the insights. This is a video I’ll watch again and again
Excellent video! My brain is buzzing with ideas as my team move towards PBI reporting. I'm going to show them this video
Muchas gracias Kurt. Excelente contenido!.
Me encantó el final: "Enjoy making reports"
Amazing approach, Kurt! It's important to do not forget the main objective of the calculations that we put hard work on. If our internal or external customers are not able to gather the critical business information required, so our job wasn't done in the most efficient way!
I wonder, is there any project, personal or not, that you are engaged in? I want to know people that are dived into this knowledge. Let me know if you have!
Really solid examples of action-based dashboard. Great work. I'm always refining my approach to understanding the action that clients take based on the data; I'm definitely bookmarking this video.
Excellent tutorial Kurt! Thanks to your clear guidance, it was easy to grasp how the reports could be more efficient and effective. Thank you for the content. Much appreciated!! Big fan of you guys :)
Sounds so simple but very useful and effective. Thank you.
Outstanding topic, real life business scenario, thank you very much for this video ❤
THis is very useful - thank you very much!
Thank you, Kurt, for sharing the video and article. Very well explained.
Very useful information for report developers. Thanks😊
This is gold; thank you so much, Kurt. I'm curious how you created the visualization at the bottom right, precisely the exclamation mark.
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.
excellent tutorial, thanks a lot
Good video, and you're a good presenter!
Thank you
Excelente,
Boas dicas, Parabéns!
fabulous summary of good report design, thank you!
Thank you Kurt, excellent rule to apply!
Good advice. i'll keep that in mind for my next power bi designs
Thanks very much for the great explanation and tips it was very informative
This is really good. Thank you for sharing.
More content like this! I loved one video from Curbal which explained the importance of identifying the screen size of users in order to choose the layout of the report
Thanks! Much, much more on the way :)
really great vdo. thx a lot
Congratulations, very good content!
Excellent.Thanks.👏👏👏👏
This is GOLD, thank you so much! :)
Thank you for such good content
Very Insightful!
Fantastic video! Always easy to forget about the audience/customer! I will keep this practice in mind thankyou! Could you do a video about best canvas size? These examples all seem to use more pixels then default
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.
Great insight, really helped me to learn new thing today :)
Another banger. Great job!
Realy useful, thank you!
Very good. Thanks
Great video. Thanks. My comment is that data analysts should be more confident and challenge those who ask for everything on one page if the mission is to inform people and make decisionsul using PBI. Often, more senior employees who don't know new technologies well enough request things in a format that's not practical and that has to change.
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.
Well done! 🙏
Five minutes in a report and I'm being asked if they can export it to Excel.
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.
Amazing tutorial, Kurt. Would you consider making the pbix available for download?
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.
Great video! Loved it ❤
Thanks 🥰
This is great! Question: How many main 'questions' should a report be able to answer or should it focus on?
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.
Good video and and agree with idea in behind, but what about Power BI tool it self? Is it easy to learn? Is it clear with what to start learn Power BI? Is it intuitive and how many exceptions in functionality need to keep in mind when You start to use it. So what is 20/80 needed to know in Power BI to get in average knowledge? Can be applied rules like 3/30/300 to Power BI tool it self? Sorry for to much questions above but its not fair that to create something simple and easy to read by going through madness to create it.
What do you guys recommend on doing when the process is not too clear even to the business people, therefore they don't even know the questions they are trying to answer. Any tips?
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.
Useful !
At 19.49, can you share what visual you used to design the left card panel please?
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...
anyone know what theme is used in this report?
Default theme that I just customized using some container and page formatting options.
Not all people are aware of AOP, could you please explain what is AOP?
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.
The faster u create the file the stringent deadline will become.💀💀