The Data Manifesto (What We Value More)
The Problem
Your team ships solutions but nobody uses them. You have comprehensive documentation but nobody reads it. Everyone works in silos—data engineers build pipelines nobody asked for, analysts build reports engineers don't know about, business teams duplicate work because they can't find existing solutions. You hire for individual brilliance and wonder why team output is mediocre. There's no shared agreement on what matters. It's like a restaurant where everyone cooks different dishes with no menu—chaos. You need a manifesto: a clear statement of values that guides every decision. Without it, everyone optimizes for different things and the team pulls in 47 directions.
The Principle
Create a Data Manifesto—what you value MORE THAN other things. Inspired by Agile Manifesto format. Example: "We value Usage and Re-use MORE THAN building another solution. We value Working across teams MORE THAN doing everything ourselves. We value Usable metadata MORE THAN comprehensive documentation." The "more than" is critical—you're not saying documentation is bad, you're saying usability matters more. The magic happens when the manifesto guides daily decisions. Someone proposes a new report? First question: "Can we use or enhance an existing one?" That's the manifesto at work. Print it. Post it. Reference it in meetings. Make it the cultural north star.
3 Steps to Take Action
- 1
**Workshop the Values** Gather your team (or team leaders if large org). Ask: "What behaviors do we want MORE of?" Common themes that emerge: - Usage/re-use over building new - Collaboration over silos - Usability over comprehensiveness - Customer satisfaction over output volume - Simplification over accumulation Debate and prioritize. Pick 4-6 value pairs. Format: "We value X MORE THAN Y" (both are good, but X matters more).
- 2
**Draft and Socialize the Manifesto** Write it up: "Data & Analytics Manifesto We are committed to [your mission]. Through this work, we have come to value: - Usage and re-use MORE THAN building another solution - Working across teams MORE THAN individual optimization - Usable metadata MORE THAN comprehensive documentation - Customer satisfaction MORE THAN ticket velocity That is, while there is value in the items on the right, we value the items on the left more." Get team feedback. Refine. Get leadership buy-in.
- 3
**Operationalize the Manifesto** Make it real: - Print poster-size, hang in team areas - Reference in meetings: "Does this align with our manifesto?" - Add to onboarding materials - Use in decision-making: "Which option better reflects our values?" Examples in practice: - New report proposal? First check: can we re-use existing? (manifesto: re-use over building) - Analyst stuck? First action: ask peer team for help (manifesto: collaboration over silos) Review quarterly: Are we living the values? Where are we falling short? Goal: Manifesto becomes how decisions get made, not just words on wall.
💡 Inspired By
Agile Manifesto format. Data Manifesto concept from Walk the Catwalk presentation. a Fortune 10 healthcare company's values-driven cultural transformation.
This is what Analytics Pitfalls & Principles is about: people helping people.
In Practice
A Fortune 5 healthcare company's analytics org had 200+ people across 8 teams. Each team operated independently. Data engineers built pipelines without talking to analysts. Analysts built reports without checking what existed. Business teams had no idea what was available. VP called team-wide session: "What should we value?" 4-hour workshop. Emerged with Data Manifesto: "Usage and re-use over building another report. Working end-to-end with peer teams over individual team optimization. Usable metadata over comprehensive metadata. Solution and customer satisfaction over ticket velocity." They printed it poster-size, hung in every team area. Started referencing in meetings: "Does this align with our manifesto?" New report proposals required: "Did you check existing solutions first?" (re-use value). Cross-team collaboration became expectation, not exception. Six months later: report count down 40% (re-use), solution usage up 85% (focus on what matters), team satisfaction up (working together felt better). The manifesto became the culture.
