Lesson 1 — Data Management Change Is Organizational + The Five Laws
Technology is an enabler, not the change
A platform can go live while the organization keeps the same unofficial spreadsheets, silo incentives, escalation habits and accountability gaps. Chapter 17 therefore judges meaningful change by changed behavior and organizational capability, not by deployment alone.
Five organizational shifts in the chapter introduction
| Shift | From | Toward | Why it matters |
|---|---|---|---|
| Accountability | vertical/silo accountability | horizontal accountability along the Information Value chain | data crosses functions, so responsibility cannot stop at department boundaries |
| Stewardship | local ownership only | shared stewardship | shared data requires shared decisions and collaboration |
| Information quality | niche concern / IT job | core organizational value | quality affects decisions, risk, operations and trust |
| Quality improvement | cleansing and scorecards | fundamental organizational capability | finding defects does not change the processes and behaviors that create them |
| Value evidence | data work treated as overhead | measure cost of poor DM and value of disciplined DM | evidence creates urgency and supports continued investment |
Exam trap: “System X is live” may be a milestone or enabling first step. A change vision must explain what the organization will do better because of it.
The Five Laws of Change
These are parallel principles, not ordered steps.
1. Organizations do not change; people change
Announcements, structures and systems become real only when individuals work differently. A stewardship policy is not adopted merely because it is published.
2. People do not resist change; they resist being changed
The source reframes arbitrary or imposed change. Participation, explanation and understanding increase the chance people will adopt changed responsibilities.
3. Things are the way they are because they got that way
Current practices often contain historical logic. A manual reconciliation may exist because an official report once failed during close. Learn what the old practice solved before removing it.
4. Unless there is push to change, things will likely stay the same
A better design does not sell itself. Some focused dissatisfaction, urgency, audit exposure, poor-data cost or other reason must make the status quo insufficient.
5. Change would be easy if it were not for all the people
Human reactions vary. Different people experience different losses, incentives, fears and confidence levels; technical mechanics are often simpler than the people-side transition.
Change Agents and VISION
Change Agents pay attention to people rather than only systems. They actively listen to employees, customers and stakeholders, surface problems early and help change execute more smoothly.
The source also emphasizes a clear VISION communicated vividly and repeatedly to build engagement, buy-in, backing and support when difficulties arise.
Retrieval checks
Q: A catalog is live, but teams keep unofficial spreadsheets and old stewardship paths. What is the source-faithful conclusion?
A: The technology delivery has not yet produced the organizational change Chapter 17 is concerned with.
Q: Leaders mock a legacy reconciliation and remove it without learning why it exists. Which law is most directly violated?
A: Things are the way they are because they got that way.
Source: pp. 541–542.