BEGIN:VCALENDAR VERSION:2.0 PRODID:-//hacksw/handcal//NONSGML v1.0//EN METHOD:PUBLISH BEGIN:VEVENT DTSTAMP:20260308T034514Z DESCRIPTION:Click for Latest Location Information: http://edw2019.dataversi ty.net/sessionPop.cfm?confid=126&proposalid=10512\n

NOTE: This seminar is continued from Thursday afternoon.

\n

Most companies and government a gencies address data quality reactively after errors are made, and as a dir ect result, suffer from bad data. To date, it has taken a special person to challenge the status quo within his or her work team and address data qual ity by “getting in front” of the issues, making a huge improvem ent, and, in effect, showing the rest of the company what is possible. I ca ll this person the “data provocateur.” I recently introduced th e term publicly (see for example, “Data quality should be everyone&rs quo;s responsibility.” in HBR), and many people have asked, “Ho w can I become a data provocateur?” This mini-boot camp provides the answer. It aims to provide you with the skinniest possible set of materials needed to become an effective data provocateur and to empower and embolden you to move forward. An exemplary provocateur would be Bob Pautke at AT&am p;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 obtaine d. 

\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

A four-step process for becoming a provocateur:

\n
    \n  Answer “Do I (we) have a data quality problem?”\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?  ;\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 “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:20190322T083000 SUMMARY:The Data Provocateurs' Bootcamp DTEND:20190322T114459 LOCATION: See Description END:VEVENT END:VCALENDAR