Share Bad Practices to Win a Prize
Update: The Community Summit was postponed to June 29 – July 2, 2020, due to the Coronavirus worldwide concerns. Whether you plan to attend in June or not, you have plenty of time to share with me a screenshot of badly-designed reports to win a prize (details below).
Are you going to the Community Summit (Power Platform Summit) in Barcelona? Join your Power Platform community in Barcelona to learn, network & engage – register here.
But most importantly (subjectively speaking) – I would really be glad to meet you in-person at my session on “Power BI Bad Practices – Learn from the mistakes of others”.
Here is my session abstract:
You can create beautiful Power BI dashboards in minutes, but it takes months or even years to learn how to create sustainable enterprise-grade dashboards that have a lasting impact on your organization. To accelerate the journey, we can learn faster from the mistakes of others and focus on bad practices rather than the good ones. Bad things are likely to imprint in us a powerful emotional memory that will not fade away so quickly. Ready to start? In this demo-packed session, we’ll share bad things that you can do in Power BI: Wrong Pie Charts and overused Treemaps; Missed data-prep opportunities; Flat tables and wrong models; and one big misconception that lead to ill-governed self-service BI practices. Join this session to imprint the bad things you should avoid doing in Power BI, and more importantly to enjoy the demos and have fun.
And here is the interesting part. Would you like to be featured in my session and get a spotlight for your work? Do you want to win Power BI demos worth $200? Share with me screenshots of badly designed Power BI reports that you improved (Please mask any confidential data) and I will feature them during my session and here in my blog with the appropriate credit. Here is how we can do it:
- Option 1: Tweet the screenshot of the report and tell your story. Make sure you include the hashtag #PBIBadPractices and @DataChant.
- Option 2: Send me by email (firstname.lastname@example.org) the screenshot.
- Option 3: Email me two screenshots of the report before and after. The “before” screenshot will represent how the report looked like when you started working on it. The “after” screenshot will show your improved version.
Note: You don’t need to attend the session in order to have your work featured.
The worst 10 reports that will be shared will earn their submitters with $200 credits to purchase demos in my shop.
If you have any recommendations for topics I should share in my session please let me know in the comments below.
I would add one more sin. Not think how the report will look like throughout the year – especially Jan/Feb. I learned it hard way this year when I saw that some of the calculations are not showing what I wanted/visuals where broken.
I had to add couple more Time Intelligent Columns, Upgrade my Data Sources(My SAP table only had CY &PY – but what you do in Jan – you compare 2019 Full Year to 2018 Full Year… and 2018 just has been archived) to include more years and finally update my YTD line chart which in January where a one dot instead of line.
One more thing… I had my YTD calculation as Year is Current Year and Month is Last Month which would be… 12.2020. No whatever you do, we should always simulate future dates (especially in terms of scalability and year change).
This is something cannot be found by testers/users because current version is fine and working. We need to be predictive/proactive in this case.