> For the complete documentation index, see [llms.txt](https://docs.deepwork.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepwork.studio/teams-departments/awareness.md). # Awareness ## Key principles for external communication * Only promise what you can deliver, in any message. Then aim to over-deliver. * Always put others on a pedestal, not ourselves. * Always be nice, friendly and seek opportunities for collaboration * Always use non-violent communication * 100% educational, valuable or entertaining content. No sales or attention-seeking. * Lasting relationships: Share quality over quantity. * Usage of simple language to convey useful information. ([Hemingway Editor](https://hemingwayapp.com/) can help) * Observe emerging social dynamics and build awareness strategies on the existing behaviors as long as they are in alignment with our goals. ## Educational goal We want to transform the tech industry to be more conscious of good and human-focused design. Share learnings, design approaches, zero-cost tools, and a novel perspective. ## Long term goal In two years' time, Deep Work's social media presence would be the go-to place to gain knowledge regarding design, web3, and healthy work-life balance space. Thanks to its simple-to-understand and helpful content that provides great value to our audiences. Convincing others to work with us is not the priority of Awareness. Rather, it is to educate, make others follow along, and lift them up. ## Design Files {% embed url="" %} ## Target audiences #### Top 3 🏢 Well funded teams/enterprise 💻 Small technical teams 🎨 Designers and Freelancers #### Also important 🎓 Academics, graduate students 🌐 Web3 noobs ## Content format 🗻 Images 🎙️ Audio 📄 Text ▶️ Videos ## Current Channels ### Twitter Spaces Every two weeks episode with a conversation on a topic. Involving two people who lead the conversation and potentially a guest. **Why**: Ephemeral audio conversations are easy to consume on-the-go, and seem scarcer than podcasts (which is an over-saturated medium). Podcasts might become more interesting once we can ensure that 100% of our content is valuable. ### Twitter Several times per week, Deep Work is posting short format educational content from client work and processes. **Why:** Twitter is where crypto people hang out and where we have the largest community of followers so far. ### Instagram On the same days, we post content through Instagram. **Why:** Instagram makes it easy to present visual content like case studies. Many design people consume educational content through Instagram. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.deepwork.studio/teams-departments/awareness.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.