this repo has no description
:memo:
+16
-18
+3
-3
Asynchronous Communications.md
+3
-3
Asynchronous Communications.md
···
4
4
- Every question asked in an internal Slack is a policy failure.
5
5
- [Asynchronous environments allows for self discovery without interruptions](https://snir.dev/blog/remote-async-communication/):
6
6
- You can keep on your flow without waiting for someone to give you details.
7
-
- You can get into "deep focus" session without context switching that allows for better [[productivity]].
7
+
- You can get into "Deep [[Focus]]" session without context switching that allows for better [[productivity]].
8
8
- You can work whenever, since you are not dependent on anyone immediately.
9
9
- You'll have written records of everything.
10
-
- [Async communication](https://protocol.almanac.io/docs/async-work-ezPny9x7Q50QISL4UIUhB3PoURV0lgxP) takes more time but it enable better thinking.
10
+
- [Async communication](https://protocol.almanac.io/docs/async-work-ezPny9x7Q50QISL4UIUhB3PoURV0lgxP) takes more time but it enable better thinking. Learn to [[Asking Questions | ask better questions]] and [[Writing | write requests]].
11
11
- The 4 components of a [great asynchronous message](https://protocol-labs.gitbook.io/launchpad-curriculum/launchpad-learning-resources/protocol-labs-network/os-stewardship#sync-comms):
12
12
1. Enough information to cover all follow-up questions.
13
13
2. A deadline. When do you need a response by? How urgent is it? Which task is being blocked right now?
···
16
16
17
17
## Resources
18
18
19
-
- - [Manifesto for Async Software Development](http://asyncmanifesto.org/)
19
+
- [Manifesto for Async Software Development](http://asyncmanifesto.org/)
+1
-14
Data/Data Culture.md
+1
-14
Data/Data Culture.md
···
78
78
- [Data ownership is a hard problem](https://www.linkedin.com/posts/chad-sanderson_heres-why-data-ownership-is-an-incredibly-activity-6904107936533114880-gw8n/). Data is fundamentally generated by services (or front-end instrumentation) which is managed by engineers. CDC and other pipelines are built by data engineers. The delineation of ownership responsibilities is very rarely established, with each group wanting to push 'ownership' onto someone else so they can do the jobs they were hired for.
79
79
- [Becoming a data-driven organization is a journey, which unfolds over time and requires critical thinking, human judgement, and experimentation](https://hbr.org/2022/02/why-becoming-a-data-driven-organization-is-so-hard). Fail fast, learn faster.
80
80
- [Start small. Don't try to wrangle data for the entire company until you have the tools and process down for one team](https://data-columns.hightouch.io/your-first-60-days-as-a-first-data-hire-weeks-3-4/).
81
-
- [For Product Analytics, start small (ant iterate), stay small (limit metrics and dashboards), and keep it simple (you can explain the metric in plain language)](https://twitter.com/0xferruccio/status/1501983388399325191).
82
-
83
-
[[Sharing Data Insights(httpslocallyoptimistic.compostshare-your-data-insights-to-engage-your-colleagues)]]
84
-
85
-
### Slack Template
86
-
```md
87
-
![Chart]()
88
-
89
-
💡**One sentence summarizing the insights.**
90
-
📝 Some extra information that might be useful.
91
-
🔍 Dig deeper on link.com!
92
-
93
-
_Questions, concerns? Thread on!_ 🧵
94
-
```
81
+
- [For Product Analytics, start small (ant iterate), stay small (limit metrics and dashboards), and keep it simple (you can explain the metric in plain language)](https://twitter.com/0xferruccio/status/1501983388399325191).]
+12
-1
Sharing Data Insights(httpslocallyoptimistic.compostshare-your-data-insights-to-engage-your-colleagues).md
Data/Sharing Data Insights.md
+12
-1
Sharing Data Insights(httpslocallyoptimistic.compostshare-your-data-insights-to-engage-your-colleagues).md
Data/Sharing Data Insights.md
···
8
8
3. **What caught my eye?** Share a chart or a related resource!
9
9
4. **What if I want to know more?** A **link to additional information** can be valuable for people who have time for more than a quick scan and want to understand how you developed the insight, or do some of their own related exploration.
10
10
5. **What if I have a question?** Explicitly **inviting questions** and responses is crucial. It’s the best part of sharing an insight! This is where you get to learn about things your colleagues know that you don’t, or what they’re curious about but has not yet risen to the level of becoming a data request from them.
11
-
6. **What if posting this prompts a whole bunch of follow-up questions, or exposes incorrect assumptions?** If you have hit on something that’s interesting to a lot of people there likely will be questions that spin off, new ways to slice the data you’re looking at, or assumptions you have made that need to be corrected.
11
+
6. **What if posting this prompts a whole bunch of follow-up questions, or exposes incorrect assumptions?** If you have hit on something that’s interesting to a lot of people there likely will be questions that spin off, new ways to slice the data you’re looking at, or assumptions you have made that need to be corrected.
12
+
13
+
### Slack Template
14
+
```md
15
+
![Chart]()
16
+
17
+
💡**One sentence summarizing the insights.**
18
+
📝 Some extra information that might be useful.
19
+
🔍 Dig deeper on link.com!
20
+
21
+
_Questions, concerns? Thread on!_ 🧵
22
+
```