So Tableau vs Power BI or Power BI vs Tableau, even the ordering seems to get some people fired up. In the last two years I’ve been in the middle of this debate and have picked a definite side, however I have actually done an in-depth review of both products (against my requirements). So if you will let me I’ll try to provide my views on this and hopefully they won’t come across too one-sided.
As you may or may not know my passion is in Data Management primarily within the IT Service Management – a field that I have worked extensively in for the last 15 years. I have spent the last three of those years working primarily within a Cherwell organisation, throughout this time I have worked to understand and appreciate the business drivers of reporting and Data Analysis finally as part of a serice review I have been able to express and articulate the vision of a truely 3D Service Catalogue that works to maximise value at all levels. The mesh structure of the catalogue is handled transparently in the background while the customer and workers do not need to be aware. The reporting layer for this is phenomenial and suddenly the Service Catalogue is becoming an asset as opposed to something you have to try and get value out of. This will reinvent the way we work and how we deliver products and services.
Excitingly we are now also going to be adding service cart functionality another huge step forward for customers and a giant leap for reporting. All delivered with Power BI and a great reporting team.
I’ll be speaking about our work and the development on Wednesday 18-Apr-2018 and I hope to see you all there!
Since October 2017 the pace of development has really ramped up already 2018 looks like it is going to be another bumper year. The focus of the year is very definitely going to be about the transition from old fashioned Adaptive Intelligence – I prefer “Adaptive Intelligence” to Artificial Intelligence.
Two main topics currently seem to be dominating my world.
- When will BI be declared dead!
- Which platform should I be betting the farm on?
So my head is spinning more than a little after this week. I’ve had a data strategy meeting with whom and for what purpose I genuinely do not know. Then three or four separate data model development meetings then reviewed my teams work… All of this has made me feel it is time to share my design philosophy and how I go about building Power BI reports.
I use a four step process and for my personal opinion that fits the product best, the key thing to remember is that you do not always have to go forward, I’m a huge believer in emergence and emergent behaviours, BI is a prime emergence environment
Emergent behavior is behavior of a system that does not depend on its individual parts, but on their relationships to one another. Thus emergent behavior cannot be predicted by examination of a system’s individual parts.
In other words as reports develop and value is shown addition relationships or correlations become clear. This understanding is what drives my design principles, hopefully even if you disagree you will appreciate some of the ideas and can incorporate them into your own modelling principles.
By dividing the report creation process into four distinct stages expectations and delivery gateways established, typically you should try to sign off each stage before moving forward, but you have to accept the reality that emergence willl often move you backwards, that is fine and must be accepted, pushing on regardless to the recipie for disaster.
This is quite common issues as you start to go forward in Power BI, so I’ll try and scope it out for you guys.
A client has five or six data sources coming together to produce a Power BI report, due to the nature of the data sources they return a “now” state so trending is a challenge, typically to set trending up we would set up a snapshot. In this data model data is coming in from a range of services not all of which are in SQL some data is coming directly from products as well. The net result is that snapshotting would be complex and ultimately remove the benfit of using Power BI and the Mashup engine. Instead Patrick spelled it all out in a Guy in a Cube Video. Now we didn’t need to do all of this, but something went “ping” and suddenly I had a vision of the future. We could use the integrated SharePoint with the App space to host a SharePoint List and then use the SharePoint List to bring the data back.
That’s dumb, why would I want to do it all this way, SharePoint isn’t going to hold the data I need!
The biggest benefit of using this method is that quickly and easily trends can be set up based on complex “unrelated” data.
Watch this space as I’ll keep adding to it as we find things out about using the mechanism after all there isn’t really a short cut to setting up a trend and getting real world data.