@@ -0,0 +1,89 @@
1++++
2+
3+title = "Privacy Messaging"
4+date = "2023-04-07"
5+
6+[taxonomies]
7+grant_type = ["Proposal"]
8+grant_category = ["Other"]
9+
10+[extra]
11+image = ""
12+description = "Communicating Urbit's unique privacy potential"
13+reward = "4 Stars"
14+assignee = ["~dibnyt-wisfyn"]
15+champion = ["~poldec-tonteg"]
16+grant_id = "P0257"
17+completed = false
18+canceled = false
19+
20++++
21+
22+# Overview #
23+
24+The goal of this work is to improve Urbit’s appeal to potential developers by highlighting and communicating its unique privacy potential.
25+
26+## Initial Insights
27+
28+ - Urbit is currently focused on attracting developers who will build the apps that bring users to the platform
29+ - Even some currently active developers don’t fully understand the full offering of Urbit
30+ - Urbit isn’t inherently private - it’s “privacy prone”
31+ - Urbit OS does so much for developers that they can add in features for almost nothing - privacy is one of those features
32+
33+# Work Summary #
34+
35+## Research
36+
37+ - Interviews to examine and understand current state of Urbit’s offering
38+ - Explore where Urbit wants to go in the future
39+ - Interviews to examine what developers are creating and motivations for coming to the platform
40+ - Determine what related offerings are being missed by existing developers
41+
42+## Development
43+
44+ - New messaging strategy and copywriting based on research
45+ - Incorporate growth strategy to target the ideal developers and grow our developer base in sync with Urbit’s theory of change
46+ - Exploration of ideal implementation - comms channels, structure, media formats
47+ - Rounds of feedback internally and externally (developers) to improve messaging
48+
49+## Implementation
50+
51+ - Messaging strategy presented internally to guide thinking for Urbit Foundation, Tlon, and other established developers
52+ - Messaging incorporated to assets presented to new and potential developers - (website and videos)
53+ - Potentially guidance verging on curricula - opportunity to incorporate into Hoon School
54+
55+# Guiding Principles #
56+
57+ - Overall - Develop a shared language around Urbit’s privacy features that both supports Urbit Foundation’s vision for the future and speaks to the practical implications for developers
58+ - Research - Ensure project success by making sure all stakeholder viewpoints are heard and considered from the earliest stages in the process
59+ - Development - Strive to approach communications in a way that feels interactive and engaging
60+ - Implementation - Identify and collaborate with the individuals within Urbit Foundation that need to greenlight any actions early on in the process
61+
62+# Growth Framework #
63+Through attracting new developers, deepening understanding, or a combination of both we can see three general types of growth:
64+
65+ - Attract new developers with a basic understanding of Urbit features
66+ - Expand capabilities of existing developers
67+ - Attract new developers interested in novel implementations of Urbit OS
68+
69+# How This Can Support Future Work #
70+
71+Privacy is one of many features that Urbit offers. This means that this project can model and test an approach to messaging replicable across all aspects of Urbit. The goal is to create something that is not solely top-down (led by Urbit Foundation) or bottom-up (led by 3rd party developers). Rather we want to support both the vision of Urbit and the motivations of developers and meet somewhere in the middle.
72+
73+# Timeline and Compensation #
74+
75+Timeline: Approximately 10 weeks
76+
77+ - Stakeholder Identification ~ .75 wks
78+ - Interview Prep + Scheduling ~ .75 wks
79+ - Internal + External Interviews ~ 2 wks
80+ - Analysis & Reframing ~ 1 wks
81+ - Ideation & Feedback ~ 2.5 wks
82+ - Development & Implementation ~ 3 wks
83+
84+Reward: 4 Stars
85+
86+# Summary #
87+
88+While the underlying technology behind Urbit is incredible, the current messaging strategy is not focused enough on the value that tech brings to our core audience. This hinders conversion of new developers to the platform and limits the capabilities of existing developers.
89+By addressing this issue (starting with the topic of privacy), this work will be invaluable in helping Urbit grow. Additionally, it will model a systematic yet flexible process of working with stakeholders—both internally and externally—that can be used to improve messaging across any number of topics.