Discover The QlikView Way
Matthew Stephen
Solutions Consultant
“How you gather, manage, and use information will determine whether you win or lose.”
1999
Agenda
• Business Discovery
– taking Business Intelligence to the next level
• Traditional Business Intelligence vs QlikView Business Discovery
• The Associative Experience
– discovery: a train of thought
• The Associative Model
– The secret to rapid development and adoption
Business Discovery
You have data
You have people
Your people have
questions
Business Discovery has the answers
Data Information Knowledge Understanding
Business Intelligence
Business Discovery
Shared
Understanding
BI Reality for Many Organisations
Difficultto use
Inflexible
Costly
Slow
Sales
Customer Product
Territory Time
The Challenge
IT Model Business Model
I.T.Maintain systems
The BusinessMaintain profitability
The Challenge
Between 70% to 80% of corporate business intelligence projects fail, according to research by analyst firm Gartner.
Image: jscreationzs / FreeDigitalPhotos.net
a) the business didn’t actually know what they wantedb) the business didn’t support the project properly c) Poor communication between these two groups
E.T.C
Traditional BI
ETL – Extract Load and Transform
EDW - Enterprise Data Warehouse
Data Model (Semantic/OLAP)
Presentation Layer
Stack
DW
E.T.C
Why A Traditional BI Stack?
ETL – Extract Load and Transform to create the data warehouse
EDW - Enterprise Data Warehouse single source of consolidated data
Data Model (Semantic/OLAP) make the data accessible to business users & OLAP cubes to make the model deliver acceptable query performance
Presentation Layer make the business insight visible
DW
But the problem with the stack is…
• Each level requires a separate tool (platform)
Image: jscreationzs / FreeDigitalPhotos.net
But the problem with the stack is…
Image: renjith krishnan / FreeDigitalPhotos.net
• Each tool requires a set of skills and a deployment regime
But the problem with the stack is…
Image: ddpavumba / FreeDigitalPhotos.net
• Which presentation tool?
But the problem with the stack is…
Image: scottchan / FreeDigitalPhotos.net
• Each tool adds to: complexity, time to value, cost, in-agility, frustration
But the problem with the stack is…
• A data warehouse requires an architecture
– Inman or Kimball or maybe both?
Image: jscreationzs / FreeDigitalPhotos.net
So what’s the QlikView Way?
E.T.C
QlikView does it all in one
But How?
• The Associative Model
– Removes the ‘relational’ complexity in a data warehouse
No need for complicated ETL
– Simple data model
No need for complex data warehouse architecture/methodology
– Removes the need for OLAP cubes
In memory model gives required speed
• Single fully functional presentation layer
– The Associative experience
Associative Analysis
my selection
associated
not associatedOpportunity
Associative Search
• Analysis: A train of thought
Q A Q A Q A
Demos
• Associative Analysis
– Green, white and grey in action
• The Associative Model
– Hub and spoke schema
– Removing complexity
– Enabling rapid development
What is Knowledge?
• “There are known knowns.
– These are things we know that we know.
• There are known unknowns.
– That is to say, there are things that we know we don't know.
• But there are also unknown unknowns.
– There are things we don't know we don't know. “
Donald Rumsfeld
What is Knowledge?
• There are known knowns.
– We can list these in standard (canned) reports
• There are known unknowns.
– We can find these in pivot tables
• But there are also unknown unknowns.
– We discover these with Business Discovery
QlikView can do all three
Thank you!
Recommended
