Read a sample: 1. Lead With a Duty of Care
The launch meeting is nearly over when someone asks for one more field on the registration form.
The marketing team wants to promote a fictional community fitness program called Harbor Steps. Visitors will be able to register for an introductory session and receive information about future classes. The form already asks for a name, an email address, and a preferred session time. A colleague suggests adding a question about health conditions so the team can tailor its follow-up messages.
The suggestion is well intentioned. It may also create a problem the team has not prepared to handle.
Who would read the answers? Would they go into the email platform, a spreadsheet, an agency’s campaign report, or all three? Does the person completing the form understand why marketing is asking? Could a broad question invite details that the program cannot use appropriately? Is there another way to help participants identify accessibility or accommodation needs without placing private details in a general marketing system?
None of these questions requires the marketing leader to become a privacy lawyer. They do require the leader to notice that a seemingly small campaign decision can create responsibilities beyond the campaign itself.
That is the starting point for this book. Leading customer-information practices means making deliberate choices about what the team asks for, where information goes, who can use it, and what happens when the original purpose is over. It also means recognizing when the team needs technical, operational, or legal expertise before moving forward.
The goal is not to make marketing timid. It is to make the work more considered, more accountable, and easier to explain.
Marketing teams often talk about customer information as an asset. That description has a practical purpose: information can help a business understand demand, provide relevant communications, and serve people more effectively. But the asset belongs to a relationship. It may reveal something about a person’s circumstances, preferences, habits, or concerns.
A customer who supplies an email address to receive a class reminder may not expect that address to become part of an unrelated advertising audience. A person who asks about an accommodation may expect a response from someone able to help, not broad visibility across an agency account. Even when a use seems useful to the organization, it can feel surprising or intrusive to the person described by the information.
Those expectations are not always obvious or uniform. A familiar customer may welcome a tailored suggestion; another person may find the same message unsettling. Leaders cannot remove every possibility of discomfort. They can, however, ask what the customer was trying to accomplish and whether the proposed use fits that context.
Duty of care, as used in this book, is a practical leadership commitment. It means treating customer information with attention proportionate to its context and possible consequences. It is not a claim that every organization has the same legal duty, or that following these pages guarantees compliance. Applicable obligations depend on facts, location, industry, relationships, and current law. A qualified privacy professional can help interpret those obligations for your situation.
The operational commitment belongs to you even when legal questions are referred elsewhere. You can ask what the team collects, challenge an unnecessary field, assign an owner to a shared file, and make sure a concern reaches the right specialist. You do not need perfect legal certainty before beginning that work.
Return to Harbor Steps. The team’s immediate goal is straightforward: fill introductory sessions and help interested people learn about the program. Yet the campaign contains several decisions that can easily be mistaken for routine production details.
First is collection. The proposed health-conditions field may collect information more sensitive than the team needs for registration. Even the existing session preference can reveal something in context. A choice of a specialized class, for example, may suggest a circumstance that the person has not directly stated. Context matters more than a field label alone.
Second is purpose. An email address may be useful for sending a session confirmation. The team might also want to send future promotions or create an advertising audience. Those are distinct uses, and a leader should not assume that permission or an appropriate basis for one automatically covers the others. What the form says, what choices it offers, and which rules apply all deserve attention.
Third is access. A coordinator may need registration details to prepare a session. A designer creating social posts probably does not need a list of individual registrants. An agency analyst may need campaign results without needing people’s accommodation requests. The convenient answer—give everyone access to the same export—can expose more information than each role needs.
Fourth is movement. The form may send information into a registration tool, which passes it to an email platform. A staff member may download a spreadsheet for an instructor. An agency may receive a file for reporting. Each handoff can create another copy, another set of permissions, and another question about who is responsible.
Fifth is time. A list that is useful before the introductory session may remain in a shared folder long after the team has stopped using it. Keeping everything indefinitely can make future reviews and customer requests harder. Deleting too quickly, without considering operational needs or applicable obligations, can also create problems. Retention calls for a reasoned decision, not an automatic preference for either keeping or deleting.
Finally, there is response. Someone may ask to…