---
title: "\"Know Your Customer\" - Host a data workshop"
---

[![Screen Shot 2020-06-28 at 11.15.20 AM](https://www.kkrasnowwaterman.com/hs-fs/hubfs/Screen%20Shot%202020-06-28%20at%2011.15.20%20AM.png?width=519&name=Screen%20Shot%202020-06-28%20at%2011.15.20%20AM.png)](https://www.kkrasnowwaterman.com/)

 

# "Know Your Customer" - Host a data workshop

Posted by [K Krasnow Waterman](https://www.kkrasnowwaterman.com/professional/author/k-krasnow-waterman) on Sat, Apr 26, 2008 @ 16:04 PM

- [Tweet](https://twitter.com/share)

Recently, I was invited to facilitate a workshop to learn about customer data uses, flows, and needs. It was an interesting idea, so I agreed.

"Know your customer" has become a hackneyed phrase in fairly short order. One of the post-9/11 bundle of laws, intended to gain anti-terrorism assistance from the public, was a "know your customer" mandate requiring financial institutions to better understand who their customers are and where their money comes from. Like many things we do in this automated life, it seems to have quickly lost its meaning in favor of a single massive data collection effort...like when my bank of many years -- which has seen my entire transition from debt to net worth through both my business acounts and the deposit of every paycheck -- asks me for id.

The workshop was intended to provide an opportunity for a fairly large group of data architects to hear a group of customers talk about their business day and tasks; how they interact with each other; and what they want. It was my job to draw them out over the course of two days, to find slices of life to talk about and elicit tremendous detail. It was expected that we would have an accelerated opportunity to gather needed data elements and identify system access requirements.

With facilitation, the customers opened up about their work lives. They described a tremendous amount of human interaction to obtain information. They described phoning folks in other parts of the organization to find out information they wanted. We, the folks with strong information technology orientation, thought we were making a break-through, identifying systems to which these customers could or should get access.

What happened next was unexpected. Wen we sought to validate these system access requirements, the customers repeatedly and politely told us we misunderstood. They repeatedly explained that they liked to get information in this unautomated fashion. They liked the opportunity conversation gave them to get context -- group meaning of terms, background for the way information is gathered, information that's inappropriate for permanent records, and other related information.

Since then, I've been thinking about what it really means to know your customer. As the provider of services, it's not enough to learn your customer's business. And, it's not enough to spend time in their space and observe them at work. You need to do those things but, in the end, if you really want to give them what they want, sometimes you just need to ask.

 

 Topics: [technology for business managers](https://www.kkrasnowwaterman.com/professional/topic/technology-for-business-managers), [technology b2b customer service](https://www.kkrasnowwaterman.com/professional/topic/technology-b2b-customer-service)

### Subscribe by Email

### Latest Posts

### Browse by Tag

- [access control (4)](https://www.kkrasnowwaterman.com/professional/topic/access-control)
- [accountability (3)](https://www.kkrasnowwaterman.com/professional/topic/accountability)
- [analytics (2)](https://www.kkrasnowwaterman.com/professional/topic/analytics)
- [b2b customer service technology (1)](https://www.kkrasnowwaterman.com/professional/topic/b2b-customer-service-technology)
- [big data (2)](https://www.kkrasnowwaterman.com/professional/topic/big-data)
- [business collaboration (1)](https://www.kkrasnowwaterman.com/professional/topic/business-collaboration)
- [copyright (1)](https://www.kkrasnowwaterman.com/professional/topic/copyright)
- [cyber-security (1)](https://www.kkrasnowwaterman.com/professional/topic/cyber-security)
- [data mining (2)](https://www.kkrasnowwaterman.com/professional/topic/data-mining)
- [data protection (2)](https://www.kkrasnowwaterman.com/professional/topic/data-protection)
- [digital evidence (1)](https://www.kkrasnowwaterman.com/professional/topic/digital-evidence)
- [digital rights (2)](https://www.kkrasnowwaterman.com/professional/topic/digital-rights)
- [DRM (1)](https://www.kkrasnowwaterman.com/professional/topic/drm)
- [eDiscovery (3)](https://www.kkrasnowwaterman.com/professional/topic/ediscovery)
- [entrepreneur (3)](https://www.kkrasnowwaterman.com/professional/topic/entrepreneur)
- [FOAF (1)](https://www.kkrasnowwaterman.com/professional/topic/foaf)
- [forensics (3)](https://www.kkrasnowwaterman.com/professional/topic/forensics)
- [global outsourcing (1)](https://www.kkrasnowwaterman.com/professional/topic/global-outsourcing)
- [identity management (2)](https://www.kkrasnowwaterman.com/professional/topic/identity-management)
- [information management (1)](https://www.kkrasnowwaterman.com/professional/topic/information-management)
- [information security (3)](https://www.kkrasnowwaterman.com/professional/topic/information-security)
- [Internet Week (2)](https://www.kkrasnowwaterman.com/professional/topic/internet-week)
- [IWNY (2)](https://www.kkrasnowwaterman.com/professional/topic/iwny)
- [knowledge discovery (1)](https://www.kkrasnowwaterman.com/professional/topic/knowledge-discovery)
- [knowledge discovery for litigation (3)](https://www.kkrasnowwaterman.com/professional/topic/knowledge-discovery-for-litigation)
- [law about technology (5)](https://www.kkrasnowwaterman.com/professional/topic/law-about-technology)
- [legaltech (4)](https://www.kkrasnowwaterman.com/professional/topic/legaltech)
- [privacy (4)](https://www.kkrasnowwaterman.com/professional/topic/privacy)
- [privacy technology (5)](https://www.kkrasnowwaterman.com/professional/topic/privacy-technology)
- [public policy (4)](https://www.kkrasnowwaterman.com/professional/topic/public-policy)
- [risk management (2)](https://www.kkrasnowwaterman.com/professional/topic/risk-management)
- [semantic web (1)](https://www.kkrasnowwaterman.com/professional/topic/semantic-web)
- [social graph (1)](https://www.kkrasnowwaterman.com/professional/topic/social-graph)
- [software development (2)](https://www.kkrasnowwaterman.com/professional/topic/software-development)
- [software development cost (1)](https://www.kkrasnowwaterman.com/professional/topic/software-development-cost)
- [startup (2)](https://www.kkrasnowwaterman.com/professional/topic/startup)
- [technology (4)](https://www.kkrasnowwaterman.com/professional/topic/technology)
- [technology b2b customer service (2)](https://www.kkrasnowwaterman.com/professional/topic/technology-b2b-customer-service)
- [technology b2c (1)](https://www.kkrasnowwaterman.com/professional/topic/technology-b2c)
- [technology for business managers (17)](https://www.kkrasnowwaterman.com/professional/topic/technology-for-business-managers)
- [technology for lawyers (12)](https://www.kkrasnowwaterman.com/professional/topic/technology-for-lawyers)
- [technology implementing law (13)](https://www.kkrasnowwaterman.com/professional/topic/technology-implementing-law)
- [technology innovation (12)](https://www.kkrasnowwaterman.com/professional/topic/technology-innovation)
- [technology management (6)](https://www.kkrasnowwaterman.com/professional/topic/technology-management)
- [virtual world (1)](https://www.kkrasnowwaterman.com/professional/topic/virtual-world)

Copyright © 2007 [Login](https://www.kkrasnowwaterman.com/Login.aspx)