Anyone that works with data downstream in an organization has seen things go...wrong, while upstream managers and business leaders are being held accountable. Whether it's a failure in process, or something technically goes wrong, working with data is not always easy. What happened? How can we prevent it from happening again? What's next?
This talk, given at the Portland Data Science Group on October 27, 2016, uncovers 4 common foibles of working with organizational data.
3. What’s up
tonight?
• Who I am and what I am doing here
• What does business reality look
like?
• Foible #1: Connecting silos
• Foible #2: Scheming the schema
• Foible #3: Ongoing integrity
• Foible #4: Making people care
4. Who is this person?
• Yes, Lars is my real name
• I am the Customer Data and
Insights Lead for Connective DX
• What the heck does that mean?
• I make sailors blush
• I love bulleted lists
5.
6. About Us:
• 19 years old
• 80 people strong
• 2 offices (Portland & Boston)
• 5 “Best Places to Work” awards
• Recognized by Forrester as a leading Digital Experience Agency
7. Experience
Strategy
Customer Data
& Insights
DX Strategy
& Roadmap
Technology Consulting
Data Consulting
Innovation
Analytics
Experience
Design
Customer Journey
Mapping
Content Strategy
Digital Experience
Design
Experience
Optimization
Technology
Platform & Systems
Consulting
Content Management
Application
Development
Global Content
Delivery
Mobile
Commerce
Digital
Enablement
DX7 Assessment
Tools & Frameworks
Product Acceleration
Training
& Education
Staffing
Connected Expertise
37. To Normal or to Not
Pros:
• Keeps data clean
• Is a best-practice
• It scales
Cons:
• Will cause table
bloat
• It’s exactly not easy
• It takes time
39. I have seen several examples of
PostgreSQL systems that were
built to be quick and easy, but had
some major performance issues as
they didn’t grow out of the Proof of
Concept phase.
If you are planning on success, plan
for scalability too.
42. Data Drift
Three major types:
Structural:
Changes at the
source.
Ex: Fields added,
deleted, or
changed
Semantic:
The meaning
changes.
Ex: Field itself
doesn’t change,
but what is in it
does
Infrastructure:
Changes in
platform and tech.
Ex: A new platform
is added or is
changed
Source: Girish Pancha
http://www.cmswire.com/big-data/big-datas-hidden-scourge-data-drift/