BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN
METHOD:PUBLISH
BEGIN:VEVENT
DTSTAMP:20260420T123932Z
DESCRIPTION:Click for Latest Location Information: http://edw2019.dataversi
 ty.net/sessionPop.cfm?confid=126&proposalid=10246\n<p>NOTE: This seminar co
 ntinues to Friday morning.</p>\n<p>Most companies and government agencies a
 ddress data quality reactively after errors are made, and as a direct resul
 t, suffer from bad data. To date, it has taken a special person to challeng
 e the status quo within his or her work team and address data quality by &l
 dquo;getting in front&rdquo; of the issues, making a huge improvement, and,
  in effect, showing the rest of the company what is possible. I call this p
 erson the &ldquo;data provocateur.&rdquo; I recently introduced the term pu
 blicly (see for example, &ldquo;Data quality should be everyone&rsquo;s res
 ponsibility.&rdquo; in HBR), and many people have asked, &ldquo;How can I b
 ecome a data provocateur?&rdquo; This mini-boot camp provides the answer. I
 t aims to provide you with the skinniest possible set of materials needed t
 o become an effective data provocateur and to empower and embolden you to m
 ove forward. An exemplary provocateur would be Bob Pautke at AT&amp;T. I&rs
 quo;ll go into detail about Bob&rsquo;s thinking, his first steps, how AT&a
 mp;T built on his efforts, and the results he and AT&amp;T obtained.&nbsp;<
 /p>\n<div>&nbsp;</div>\n\n	What is a &ldquo;data provocateur&quot;?\n
 Why do data quality problems arise? (Answer: The rising middle manager)\n
 The hidden data factory\n
 Provocateur defined, with a special emphasis on soft skills\n
 Discussion: Can you fill the role?\n\n<p>A four-step process for becoming a
  provocateur:</p>\n<ol>\n
 &nbsp;Answer &ldquo;Do I (we) have a data quality problem?&rdquo;\n	\n
 The Friday Afternoon Measurement\n		Other impacts of bad data\n
 Answering the question\n	\n	\n
 Clarify, document, and communicate customer needs. Step a: Name the most im
 portant customers (including required documentation)\n	\n
 Learn how they use the data (including required documentation); Conduct a c
 ustomer needs workshop\n
 Determine required features and quality requirements (including required do
 cumentation)\n
 Prepare a customer requirements document discussion: Put yourself in the cu
 stomer role. What would it take to complete such an analysis for yourself a
 nd your work team and communicate your requirements to a data creator?&nbsp
 ;\n	\n	\n
 Make improvements to close the gaps. Quality improvement and the scientific
  method-the quality improvement cycle discussion: Can you do this work?\n
 Summarize the results. What success looks like presenting results, building
  support to &ldquo;Get to the next level&rdquo; discussion: Any questions a
 bout what is required? Wrap up and next steps - a promise to yourself: Make
  a list of the steps you propose to take in the next ten, 30 and 60 days.\n
 </ol>\n
DTSTART:20190321T141500
SUMMARY:The Data Provocateurs' Bootcamp
DTEND:20190321T172959
LOCATION: See Description
END:VEVENT
END:VCALENDAR