+2 -2

Data/Data Culture.md

reviewed

··· 9 9 - Data is fundamentally a collaborative design process rather than a tool, an analysis, or even a product. [Data works best when the entire feedback loop from ideation to production is an iterative process](https://pedram.substack.com/p/data-can-learn-from-design). 10 10 - [To get buy in, explain how the business could benefit from better data](https://youtu.be/Mlz1VwxZuDs) (e.g: more and better insights). Start small and show value. 11 11 - Run *[Purpose Meetings](https://www.avo.app/blog/tracking-the-right-product-metrics)* or [Business Metrics Review](https://youtu.be/nlMn572Dabc). 12 12 - - Purpose Meetings are 30 min meetings in which stakeholders, engineers and data align on the goal of a release and what is the best way to evaluate the impact and understand its success. Align on the goal, commit on metrics and design the data. 13 13 - - Business Metrics Review is a 30 to 60 minutes meeting to chat and explore key metrics and teach how to think with data. 12 12 + - Purpose Meetings are 30 min meetings in which stakeholders, engineers and data align on the goal of a release and what is the best way to evaluate the impact and understand its success. Align on the goal, commit on metrics and design the data. 13 13 + - Business Metrics Review is a 30 to 60 minutes meeting to chat and explore key metrics and teach how to think with data. 14 14 - Value of clear goals and expectations. Validate what you think your job is with your manager and stakeholders, repeatedly. 15 15 - [While the output of your team is what you want to maximize, you'll need some indicators that will help guide you day-to-day](https://data-columns.hightouch.io/your-first-60-days-as-a-first-data-hire-weeks-3-4/). Decide what's important to you (test coverage, documentation missing, queries run, models created, ...), and generate some internal reports for yourself. 16 16 - [Data teams should be a part of the business conversations from the beginning](https://cultivating-algos.stitchfix.com/). Get the data team involved early, have open discussions with them about the existing work, and how to prioritize new work against the existing backlog. Don’t accept new work without addressing the existing bottlenecks, and don’t accept new work without requirements. **Organizational [[politics]] matter way more than any data methods or technical knowledge**.

+1 -1

Governance.md

reviewed

··· 11 11 - [Democratic Mediums](https://medlabboulder.gitlab.io/democraticmediums/). A directory of patterns for decision, deliberation, and noise. 12 12 - [Metagovernance Project](https://metagov.org/). An interdisciplinary research collective that builds standards and infrastructure for digital self-governance. 13 13 - [CommunityRule](https://communityrule.info/). A governance toolkit for great communities. 14 14 - - [Verses](https://verses.xyz/). 14 14 + - [Verses](https://verses.xyz/). 15 15 - [[Decentralized Autonomous Organizations]]