Bringing privacy by design into leadership decisions

01

Make privacy an approval question

A security review alone does not answer whether collecting information is appropriate. A well-protected database may still contain unnecessary details or support an unexpected use. Ask the project owner to draw a simple data flow from collection through sharing and deletion. Identify affected people, not just system users: a tool may capture customers, employees or bystanders. NIST's Privacy Framework offers a voluntary structure for managing these risks; it does not itself certify compliance with every law.

02

Give teams decision criteria

Add privacy questions to procurement and project reviews while design choices are still changeable. Require a named owner for unresolved issues and confirm that public descriptions match how the system will actually operate.

• Explain the specific purpose for each sensitive data field.
• Consider whether less detailed or aggregated information would work.
• Define access, retention and deletion responsibilities, including vendors.
• Test how a person can correct information or change an available preference.

03

Example: a customer feedback form

A proposed survey asks for a full birth date, home address and detailed purchase history even though the team only needs to understand delivery satisfaction. Leadership can approve a simpler design with a transaction reference and optional contact route. This reduces unnecessary exposure and makes the request easier to explain. Record the decision and revisit it if the team later proposes using responses for a different purpose.

Continue with your next step

Related guides on this topic