BEGIN:VCALENDAR VERSION:2.0 PRODID:-//hacksw/handcal//NONSGML v1.0//EN METHOD:PUBLISH BEGIN:VEVENT DTSTAMP:20260421T170318Z DESCRIPTION:Click for Latest Location Information: http://edw2018.dataversi ty.net/sessionPop.cfm?confid=121&proposalid=9550\n

NOTE: This sem inar continues to Friday morning.

\n

Most companies and gover nment agencies address data quality reactively after errors are made, and a s a direct result, suffer from bad data. To date, it has taken a special pe rson to challenge the status quo within his or her work team and address da ta quality by “getting in front” of the issues, making a huge i mprovement, and, in effect, showing the rest of the company what is possibl e. I call this person the “data provocateur.” I recently introd uced the term publicly (see for example, “Data quality should be ever yone’s responsibility.” in HBR), and many people have asked, &l dquo;How can I become a data provocateur?” This mini-boot camp provid es the answer. It aims to provide you with the skinniest possible set of ma terials needed to become an effective data provocateur and to empower and e mbolden you to move forward. An exemplary provocateur would be Bob Pautke a t AT&T I’ll go into detail about Bob’s thinking, his first steps, how AT&T built on his efforts, and the results he and AT&T o btained.

\n\n What is a “data provocateur?"\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


\nA four-step process for be coming a provocateur:

\n
    \n  Answer “Do I (we) have a data quality problem?”
    \n - The Friday Afternoon Measurement
    \n - Other impacts of bad data
    \n - Answering the question\n Clarify, document, and communicate customer needs. Step a: Name the most im portant customers (including required documentation)
    \n - Learn how they use the data (including required documentation); Conduct a customer needs workshop
    \n - Determine required features and quality requirements (including required documentation)
    \n - Prepare a customer requirements document discussion: Put yourself in the customer role. What would it take to complete such an analysis for yourself and your work team and communicate your requirements to a data creator?&nb sp;\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 “Get to the next level” 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\n DTSTART:20180426T141500 SUMMARY:The Data Provocateurs' Bootcamp DTEND:20180426T172959 LOCATION: See Description END:VEVENT END:VCALENDAR