MENTAL MODEL · M3518

Privacy by Design

SystemsHigh supportSystems Theory

Included

Version 1.0.0 · Updated 2026-07-30

CORE DEFINITION

Privacy protection should not be an afterthought (Privacy by Policy), but should be embedded as a default setting in the architecture, processes, and code from the first day of system design. Scaffold role: intrinsic essence. Any critical attribute (such as security, quality, privacy), if not 'intrinsic' at the design stage, is often futile to rely on post-hoc regulation.

SCAFFOLDING EFFECT

psychology

Reduce cognitive load

Intrinsic essence. Any critical attribute (such as security, quality, privacy), if not 'intrinsic' at the design stage, is often futile to rely on post-hoc regulation.

anchor

Anchor fast decisions

If privacy is an afterthought, it is costly and prone to omissions; if it is embedded as a default in the architecture and processes from the beginning of system design, it is naturally compliant and worry-free.

MINIMUM ACTION

In progress 0/5

Practice this model in one real situation:

Set privacy as the default at project initiation
Minimize data collection
End-to-end default protection
Transparent and auditable
Built-in throughout the lifecycle rather than patched on.

Check to track your progress (stored locally)

Learning progress0%

account_treeGenealogyexpand_more

menu_bookReferencesexpand_more

Source support: Explicit

link
en.wikipedia.orghttps://en.wikipedia.org/wiki/Privacy_by_designZH · Explicit
verified

RELATED MODELS