<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Home on Superbloom</title>
    <link>https://superbloom.design/</link>
    <description>Recent content in Home on Superbloom</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <atom:link href="https://superbloom.design/feed.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Join Us As A Coach</title>
      <link>https://superbloom.design/community/our-support/coaches/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/community/our-support/coaches/</guid>
      <description>&lt;p&gt;If you enjoy mentoring and supporting teams working on public interest technology, we’d love to hear from you!&lt;/p&gt;
&lt;p&gt;Superbloom has been offering coaching since it was founded in 2014. Initially, we focused on UX/UI/product related topics. We now offer a broader array of topics – from communications, project management, community management, and fundraising, to graphic design, branding, documentation, and conference presentations.&lt;/p&gt;
&lt;p&gt;We’re currently accepting applications for paid coaches. Read on to see if it might be a fit for you.&lt;/p&gt;
&lt;h2 id=&#34;our-coaching-partners&#34;&gt;Our coaching partners&lt;/h2&gt;
&lt;p&gt;At the moment, most teams we work with are funded by the &lt;a href=&#34;https://prototypefund.de/&#34;&gt;Prototype Fund&lt;/a&gt;, a program of the German Federal Ministry of Education and Research (BMBF).&lt;/p&gt;
&lt;h3 id=&#34;about-the-prototype-fund&#34;&gt;About the Prototype Fund&lt;/h3&gt;
&lt;p&gt;The Prototype Fund supports individuals and small teams in testing ideas and developing open source tools and applications in tech that benefits the public interest. Topic areas often include civic tech, open data, IT security and software infrastructure.&lt;/p&gt;
&lt;p&gt;Each six-month Prototype Fund round supports 25 projects, each of which receive up to &lt;strong&gt;four hours&lt;/strong&gt; of coaching from Superbloom. Generally teams opt for &lt;strong&gt;two 2-hour sessions&lt;/strong&gt;, but the projects are allowed to use their four hours of coaching how they prefer. &lt;/p&gt;
&lt;p&gt;The Prototype Fund is based in Berlin, Germany and the program is conducted in German. However, if you don’t speak German, nearly all teams are happy to be coached in English.&lt;/p&gt;
&lt;h2 id=&#34;what-were-looking-for&#34;&gt;What we’re looking for&lt;/h2&gt;
&lt;p&gt;Deep practical experience on a wide variety of open-source, civic tech, and/ or public interest tech projects, in any capacity:&lt;/p&gt;
&lt;div class=&#34;container container--columns columns-3&#34;&gt;
  &lt;div class=&#34;columns&#34;&gt;
  &lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Development&lt;/li&gt;
&lt;li&gt;Design&lt;/li&gt;
&lt;li&gt;Community work&lt;/li&gt;
&lt;li&gt;Communications&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Fundraising&lt;/li&gt;
&lt;li&gt;Academic research&lt;/li&gt;
&lt;li&gt;Listening skills&lt;/li&gt;
&lt;li&gt;Reliability and trustworthiness&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;&lt;strong&gt;We are especially looking for coaches who:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Can coach in languages other than English&lt;/li&gt;
&lt;li&gt;Are based in EMEA, Asia, and Oceania time zones&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;sessions&#34;&gt;Sessions&lt;/h2&gt;
&lt;p&gt;As a coach, you should be prepared for each session to be different from the last. Some projects come with a long list of discussion points. Others have a very specific project query. Still others need more assurance or help with organising their project. We provide tools and training to guide you in structuring many different types of sessions.&lt;/p&gt;
&lt;h2 id=&#34;time-commitment-and-booking-system&#34;&gt;Time commitment and booking system&lt;/h2&gt;
&lt;p&gt;Generally, you will coach up to four hours/month, often less.&lt;/p&gt;
&lt;p&gt;We use a booking system, &lt;a href=&#34;https://cal.com&#34;&gt;cal.com&lt;/a&gt;, where teams can book time slots with coaches. As a coach, you need to set several time slots as “free,” though they may not necessarily be booked for a session. We’ll remind you to update your availability periodically. Projects generally book a week or two in advance.&lt;/p&gt;
&lt;p&gt;You will need to make blocks of at least 90 minutes available for booking at a CET friendly time.&lt;/p&gt;
&lt;h2 id=&#34;live-or-remote&#34;&gt;Live or remote?&lt;/h2&gt;
&lt;p&gt;For the most part, sessions are held remotely. Prototype Fund sessions may also take place in Berlin if both the coach and the team are based there.&lt;/p&gt;
&lt;h2 id=&#34;rates&#34;&gt;Rates&lt;/h2&gt;
&lt;p&gt;We offer all coaches a rate of $90 per hour. You are paid for the time you spend coaching and writing up notes. If applicable, we will also reimburse local transportation costs to a maximum of $20 per day.&lt;/p&gt;
&lt;p&gt;You may, of course, coach on a volunteer basis if you prefer. Let us know what works best for you.&lt;/p&gt;
&lt;h3 id=&#34;our-coaching-team&#34;&gt;Our coaching team&lt;/h3&gt;
&lt;p&gt;Our coaching team is made up of current Superbloom team members, past Superbloom collaborators, and people from our wider network. You can check out some of our current coaches &lt;a href=&#34;about/people/#coaches&#34;&gt;here&lt;/a&gt;. This is a program that we hope to grow over the coming years as it continues to be a successful model for projects. Relationships started during coaching sessions often lead to follow-on collaborations.  If you have ideas of folks who would be good to connect with as coaches, we welcome suggestions.&lt;/p&gt;
&lt;h2 id=&#34;next-steps&#34;&gt;Next steps&lt;/h2&gt;
&lt;p&gt;If you’d like to join our coaching team, please email &lt;a href=&#34;mailto:coaching@superbloom.design&#34;&gt;coaching@superbloom.design&lt;/a&gt;. We’d like to know:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What do you feel you can offer teams?&lt;/li&gt;
&lt;li&gt;Why are you interested in coaching?&lt;/li&gt;
&lt;li&gt;What languages do you speak, and what time zone are you in?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We’ll get in touch to arrange a short interview. If we decide it’s a good fit, we need a bio, photo, a list of your interests/specialities, a web link, time zone, and languages spoken. Then we will set you up with a contract, then connect you with a team member for an intro/onboarding session. We do most of the coordination around teams/sessions in a channel in our Slack, so we would also ask you to join Slack.&lt;/p&gt;
&lt;p&gt;If you are unsure about whether this is a fit for you, you are welcome to shadow a session or two to learn more. Write us at &lt;a href=&#34;https://www.notion.so/10355d7356e747f8b17ca78b4ae5028e?pvs=21&#34;&gt;coaching@superbloom.design&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Mentoring Packages for Funders &amp; Fiscal Hosts.</title>
      <link>https://superbloom.design/community/our-support/funders/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/community/our-support/funders/</guid>
      <description>&lt;section class=&#34;page-section--inner section-hero img-right&#34;&gt;
  &lt;div class=&#34;page-section--content&#34;&gt;
    &lt;h3 id=&#34;we-incubate-values-driven-practitioner-movements-through-fiscal-sponsorship&#34;&gt;We incubate values-driven practitioner movements through fiscal sponsorship.&lt;/h3&gt;
&lt;p&gt;Superbloom leverages fiscal sponsorship as a tool to support the growth and maturity of the digital rights and Internet Freedom communities, with a focus on human-centered research and design. Projects can seek and receive tax-exempt contributions and grant support without delay, bypassing the costly, burdensome and lengthy process of creating a free-standing organization with its own infrastructure.&lt;/p&gt;
&lt;p&gt;Since 2014, Superbloom has operated as a remote, international team. We work with diverse types of funding, including US Government, European Commission, and foundation grants, and offer various contracting options to fit the needs of our fiscally sponsored projects in the US and internationally.&lt;/p&gt;

  &lt;/div&gt;
  
  &lt;div class=&#34;page-section--img&#34;&gt;
    &lt;img class=&#34;sectionpic&#34; src=&#34;https://superbloom.design/images/about-us/illustration-lego.svg&#34; alt=&#34;Illustration of placing a lego piece.&#34; /&gt;
  &lt;/div&gt;
  &lt;/section&gt;

&lt;h1 id=&#34;what-is-the-accompaniment-youve-dreamed-of-for-your-grantees-investees-and-fsps&#34;&gt;What is the accompaniment you’ve dreamed of for your grantees, investees, and FSPs?&lt;/h1&gt;
&lt;p&gt;As a US 501(c)3 nonprofit, we’ve been providing practical and strategic support for public interest, open source, and nonprofit tech projects for almost 10 years.&lt;/p&gt;
&lt;p&gt;We know the field, and we’re here to help.&lt;/p&gt;
&lt;h1 id=&#34;what-we-offer&#34;&gt;What we offer&lt;/h1&gt;
&lt;p&gt;Starting from these three building blocks, we create an accompaniment program that fits you and your projects. We take a collaborative approach to building the coaching and mentoring offering that your teams really need.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Targeted 1:1 problem-solving sessions focused on the needs of your projects.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;“Ask Me Anything”&lt;/em&gt; sessions with a panel of coaches: teams bring your questions and we work on them together.&lt;/li&gt;
&lt;li&gt;Reusable tool and template creation for your program.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We also offer coaching for individual teams. If you’re an independent project, see Coaching and Mentoring from Superbloom.&lt;/p&gt;
&lt;h1 id=&#34;who-we-work-with&#34;&gt;Who we work with&lt;/h1&gt;
&lt;p&gt;We work with funders and fiscal hosts who support public interest, open source, and nonprofit tech projects.&lt;/p&gt;
&lt;p&gt;Some of our past and current partners include:&lt;/p&gt;
&lt;p&gt;[Partner grid from main page, but ONLY PARTNERS THAT ARE FUNDERS]&lt;/p&gt;
&lt;p&gt;Here’s what we keep in mind as we support teams:&lt;/p&gt;
&lt;div class=&#34;container container--columns columns-1&#34;&gt;
  &lt;div class=&#34;columns&#34; role=&#34;group&#34; aria-label=&#34;Our work&#34;&gt;
    &lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Privacy first.&lt;/li&gt;
&lt;li&gt;Security-aware.&lt;/li&gt;
&lt;li&gt;Generous with credit.&lt;/li&gt;
&lt;li&gt;Centering marginalized voices.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Open-source whenever possible.&lt;/li&gt;
&lt;li&gt;Lifting, supporting, and growing the community.&lt;/li&gt;
&lt;li&gt;Abstaining from unnecessary data collection.&lt;/li&gt;
&lt;li&gt;Transparent and mindful about any use of AI.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;
If this sounds like you, too, we may be a good match. Write to us and let’s get to know each other.
&lt;h1 id=&#34;our-topics&#34;&gt;Our topics&lt;/h1&gt;
&lt;p&gt;We have supported teams with these topics and more. If you’re looking for a specific topic you don’t see here, &lt;a href=&#34;mailto:coaching@superbloom.design&#34;&gt;just ask us&lt;/a&gt;! We can source the expertise from our broad network of technologists, funders, and mentors.&lt;/p&gt;
&lt;div class=&#34;container container--columns columns-3&#34;&gt;
  &lt;div class=&#34;columns&#34;&gt;
  &lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;UX design + product strategy&lt;/li&gt;
&lt;li&gt;Interface design&lt;/li&gt;
&lt;li&gt;Illustration + visual design&lt;/li&gt;
&lt;li&gt;User research&lt;/li&gt;
&lt;li&gt;Information architecture&lt;/li&gt;
&lt;li&gt;Writing + communication&lt;/li&gt;
&lt;li&gt;Accessibility&lt;/li&gt;
&lt;li&gt;Branding&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Data handling&lt;/li&gt;
&lt;li&gt;Naming&lt;/li&gt;
&lt;li&gt;Conference presentations&lt;/li&gt;
&lt;li&gt;Governance&lt;/li&gt;
&lt;li&gt;Team dynamics&lt;/li&gt;
&lt;li&gt;Workflows&lt;/li&gt;
&lt;li&gt;GDPR + privacy&lt;/li&gt;
&lt;li&gt;Workshop + facilitation design&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Documentation&lt;/li&gt;
&lt;li&gt;Licensing&lt;/li&gt;
&lt;li&gt;Fundraising + sustainability&lt;/li&gt;
&lt;li&gt;Narratives + framing&lt;/li&gt;
&lt;li&gt;Open source community dynamics&lt;/li&gt;
&lt;li&gt;Open processes&lt;/li&gt;
&lt;li&gt;Design tooling&lt;/li&gt;
&lt;li&gt;Usability&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;
&lt;h1 id=&#34;our-coaches&#34;&gt;Our coaches&lt;/h1&gt;
&lt;p&gt;We select coaches who have a deep expertise in tech topics, a talent for sharing and explaining knowledge, and a wide, up-to-date professional network.&lt;/p&gt;
&lt;p&gt;Each coach has extensive training and onboarding to ensure that they provide teams with a smooth, efficient experience.&lt;/p&gt;


&lt;div class=&#34;cards coaches&#34;&gt;
  
  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/lisa-baird\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Lisa Baird&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGKpr9j45tNfFkOup29&amp;#43;/gQEAAD//zhNCIqHpcA&amp;#43;AAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/lisa-baird_tone_hu_a5fa93d2b41af163.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Lisa Baird&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGI5d&amp;#43;4cGxsby4EDB5iYmAABAAD//ylIBMvM4knZAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/lisa-baird-b_w_hu_b560cf6609d782b8.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/lisa-baird/&#34;&gt;lisa baird&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/johanna-barnbeck\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Johanna Barnbeck&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGKpTJ/HxMHFws/xX0ORERAAAP//GAoC&amp;#43;9ASF8MAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/johanna-barnbeck_tone_hu_13f97a9fa8e120d.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Johanna Barnbeck&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGKZPHkyDw8Pi5CQkLCwMCAAAP//F9ICVacX6c8AAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/johanna-barnbeck_bnw_hu_bbf840d279488a24.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/johanna-barnbeck/&#34;&gt;johanna barnbeck&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/tori-boeck\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Tori Boeck&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGIpLVjP&amp;#43;fkpi7m&amp;#43;qJIAPyAAAP//JkMEOlT5MQAAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/tori-boeck_tone_hu_2da78cbdf743447d.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Tori Boeck&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGJ2d3fn5&amp;#43;dnsba2ZmFhAQQAAP//D3IBx&amp;#43;o/unUAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/tori-boeck-b_w_hu_dfa79f2e1c71e0f4.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/tori-boeck/&#34;&gt;tori boeck&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/victory\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Victory Brown&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGKpSJxmLfaOiYv5rxrfZ0AAAAD//yGuBOZu17r/AAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/victory-brown_tone_hu_a0daa8492cda2bc1.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Victory Brown&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGKpr69/8OAB08ePH1&amp;#43;/fg0IAAD//z1xCbj2yXaVAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/victory-brown-b_w_hu_f7533ef620108155.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/victory/&#34;&gt;victory brown&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;design researcher&#34;&gt;
    design researcher
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/georgia\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Georgia Bullen&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGIpLtz078c3Ftfv26X4/gECAAD//zg0B6QjMzv2AAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/georgia_tone_hu_dee64dda1e13c690.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Georgia Bullen&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGJZsGABJycno6Oj4&amp;#43;/fvwEBAAD//yFxBbXO4XC&amp;#43;AAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/georgia_bw_hu_17397bb2b3338513.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/georgia/&#34;&gt;georgia bullen&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;executive director&#34;&gt;
    executive director
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/ann-marie\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Ann Marie Carrothers&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGJpzl8owP6HRZb7u5YcOyAAAP//IWkEHZcc/qEAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/ann-marie-carrothers_tone_hu_7a02c6e210a613cb.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Ann Marie Carrothers&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGIxNzfn4uJikZKS4uPjAwQAAP//CwYBRCcP5ZMAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/ann-marie-carrothers-b_w_hu_ac7966b3de113f89.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/ann-marie/&#34;&gt;ann marie carrothers&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;lead, public privates&#34;&gt;
    lead, public privates
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/pooja\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Pooja Channaveerappa&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGLZ2DTpz8&amp;#43;fLPz87GKCvIAAAAD//zFQBRXvx1KDAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/poojay-tone_hu_656a8a1296546bba.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Pooja Channaveerappa&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGJpbW39//8/y&amp;#43;/fvxkZGQEBAAD//zy2B4m2W5zMAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/poojay-b_w_hu_bd37dd070d0cad3e.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/pooja/&#34;&gt;pooja channaveerappa&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/jan\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Jan Dittrich&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGK5NWvq5RcsLDdZ1F4yfAIEAAD//zMIBq&amp;#43;pc7r0AAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/jan-dittrich_tone_hu_f912c02037a49ef2.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Jan Dittrich&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAHklEQVR4nGJJSUn5LyMj84dFVlaWgZubmwEQAAD//zG8A/xeMkX6AAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/jan-dittrich-bnw_hu_36c352e75257c46d.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/jan/&#34;&gt;jan dittrich&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;design researcher&#34;&gt;
    design researcher
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/meag-doherty\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Meag Doherty&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAH0lEQVR4nGIpjJ78X0qK/z/j8S2n/2tyv/0PCAAA//9JxwkLyi47IgAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/meag-doherty_tone_hu_bc0df48c5c48e3bf.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Meag Doherty&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGIJCgqys7Nj8vX1/f//PyAAAP//HOMFm6uiVAYAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/meag-doherty-b_w_hu_94c2357527737b40.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/meag-doherty/&#34;&gt;meag doherty&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/ame\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Ame Elliott&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGJxD1juo8/AEix0SejFd0AAAAD//xwaBOo/&amp;#43;j0tAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/ame-elliott-duotone_hu_d264a6d23843d619.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Ame Elliott&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGKxsLAwNjZm1NbWZmRkBAQAAP//EBkBywT8c1oAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/ame-elliott-b-w_hu_3076c5640fb50617.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/ame/&#34;&gt;ame elliott&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;senior fellow&#34;&gt;
    senior fellow
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/memo-esparza\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Memo Esparza&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGLJjpnFxi/AYsx8Q4npOyAAAP//GAQDuKRNrIkAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/memo-esparza_tone_hu_a2b7aed40100579.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Memo Esparza&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGKRlJRUU1NjZmJiYmBgAAQAAP//B/8Ay4RB&amp;#43;88AAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/memo-esparza-b_w_hu_f1a2014d9ffd06fe.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/memo-esparza/&#34;&gt;memo esparza&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/laura-gaetano\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Laura Gaetano&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGLJy1zF/usji7&amp;#43;VIOcfZkAAAAD//yggBR52nPOlAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/laura-gaetano_tone_hu_5a930ead2f683d2d.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Laura Gaetano&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAHElEQVR4nGLZvHnz06dPmT59&amp;#43;vT9&amp;#43;3dAAAAA//9FnwqKSlVw7AAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/laura-gaetano-b_w_hu_5cea726fa7644eef.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/laura-gaetano/&#34;&gt;laura gaetano&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/allen-gunn\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Allen Gunn&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGKZMuHQjyf3WMR&amp;#43;PhJmvA4IAAD//zmbB4UKrAkeAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/allen-gunn_tone_hu_f3531261e0ef05b1.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Allen Gunn&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAHElEQVR4nGK5e/funTt3WE6dOrVnzx5AAAAA//9G6AnGQgceywAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/allen-gunn-b_w_hu_dd5c4e1d8669c744.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/allen-gunn/&#34;&gt;allen gunn&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/sumana\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Sumana Harihareswara&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGKJj1umLfydRZfntQ33M0AAAAD//yF2BPLf07huAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/sumana-harihareswara_tone_hu_399d6934840cf35f.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Sumana Harihareswara&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAHElEQVR4nGLZtm3b06dPWc6ePXvjxg1AAAAA//9DNAnJ0fWyMQAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/sumana-harihareswara-b_w_hu_7f48a77e19fc9d1e.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/sumana/&#34;&gt;sumana harihareswara&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/kj-hepworth\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;K J Hepworth&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAH0lEQVR4nGKZUDzz/&amp;#43;P3TP9ZeAR4GFzU2RkAAQAA//9LmQYRpfqzbAAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/kj-hepworth-tone_hu_9023ee26c0fde047.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;K J Hepworth&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGIpKytjYWFhUVJS&amp;#43;vv3LyAAAP//GVIE1EW5yt0AAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/kj-hepworth-b_w_hu_b3e8fbaf36ffe1b5.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/kj-hepworth/&#34;&gt;k j hepworth&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/dan-hon\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Dan Hon&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAH0lEQVR4nGIpSZ3/X15B5D&amp;#43;TgeB7Bi5eLgZAAAAA//87jAUhyVd4XQAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/dan-hon_tone_hu_5f0ff89aa15ccf25.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Dan Hon&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGLZv38/Jycn04ULF9jZ2QEBAAD//yh9BOSKhM4MAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/dan-hon-b_w_hu_6ca1424b5ca591d.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/dan-hon/&#34;&gt;dan hon&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/justina-leston\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Justina Leston&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGIpzF7Jzs7CeGr3pQ9f/gACAAD//yRVBtQZLdy6AAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/justina-leston_tone_hu_45297f813434932b.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Justina Leston&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGJZsGABHx8fi46Ozv///wEBAAD//yDqBZRWrQMrAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/justina-leston-b_w_hu_eabc420f146f8ea4.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/justina-leston/&#34;&gt;justina leston&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/geoffrey-macdougall\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Geoffrey MacDougall&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAH0lEQVR4nGLpa9n2X0CQ6z&amp;#43;L3P8nDOwMogyAAAAA//9ETwYXts0qAQAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/geoffrey-macdougall_tone_hu_71b5cee5bac3f815.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Geoffrey MacDougall&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGLJzs6WlJRkevv27devXwEBAAD//yWkBzm5eoxdAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/geoffrey-macdougall-b_w_hu_c5d46d5585fc83c1.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/geoffrey-macdougall/&#34;&gt;geoffrey macdougall&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/julia-racsko\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Júlia Racskó&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGJJz9rAxcHM4mQmKC7KAQgAAP//Fj4CXNuOCbAAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/julia-racsko-duotone_hu_a2e12006cc103178.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Júlia Racskó&#34;
      src=&#34;data:image/jpeg;base64,/9j/2wCEACgcHiMeGSgjISMtKygwPGRBPDc3PHtYXUlkkYCZlo&amp;#43;AjIqgtObDoKrarYqMyP/L2u71////m8H////6/&amp;#43;b9//gBKy0tPDU8dkFBdviljKX4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;P/AABEIAAIAAgMBIgACEQEDEQH/xAGiAAABBQEBAQEBAQAAAAAAAAAAAQIDBAUGBwgJCgsQAAIBAwMCBAMFBQQEAAABfQECAwAEEQUSITFBBhNRYQcicRQygZGhCCNCscEVUtHwJDNicoIJChYXGBkaJSYnKCkqNDU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6g4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV1tfY2drh4uPk5ebn6Onq8fLz9PX29/j5&amp;#43;gEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoLEQACAQIEBAMEBwUEBAABAncAAQIDEQQFITEGEkFRB2FxEyIygQgUQpGhscEJIzNS8BVictEKFiQ04SXxFxgZGiYnKCkqNTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqCg4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV1tfY2dri4&amp;#43;Tl5ufo6ery8/T19vf4&amp;#43;fr/2gAMAwEAAhEDEQA/AL1FFJTA/9k=&#34; data-src=&#34;https://superbloom.design/images/drawing-ii-salon_hu_ded13f4cfbfb9c92.jpg&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/julia-racsko/&#34;&gt;júlia racskó&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/schirin-lucie-richter\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Schirin Lucie Richter&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGKpyV0i&amp;#43;OslCxfLPzkFGUAAAAD//yiQBPB0nxliAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/schirin-lucie-richter_tone_hu_d015bbec5d4df4bf.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Schirin Lucie Richter&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGJWVVXl5ORkYWdn19XVBQQAAP//B/IBLi8oJ94AAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/schirin-lucie-richter-b_w_hu_4505d105fcab615b.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/schirin-lucie-richter/&#34;&gt;schirin lucie richter&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/romain\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Romain Robert&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGJJSljGz/qbxZPvGsvPT4AAAAD//yHdBZyaJiFRAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/romain-robert-tone_hu_c155c2b90eba6f5e.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Romain Robert&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAIElEQVR4nGLZu3fv/3fv3v1jDAwM/P/x48d/gAAAAP//ckAMxxlFTloAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/romain-robert-b_w_hu_c409f76d78e2b45f.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/romain/&#34;&gt;romain robert&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/jon-rogers\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Jon Rogers&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGIpK1jHys7GEmDMys3NBggAAP//FusCU8hpVhUAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/jon-rogers_tone_hu_a2e7f5a82ebd7d1d.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Jon Rogers&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGJpa2v7&amp;#43;/cvCwcHx79//wABAAD//zRVB6TuZV8HAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/jon-rogers-b_w_hu_71707a1c6713aad.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/jon-rogers/&#34;&gt;jon rogers&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;professor of design and creative technology, northumbria university&#34;&gt;
    professor of design and creative technology, northumbria university
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/saptak\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Saptak S&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGJZmlHJxcHEJM32ieH/f0AAAAD//xsJBLKyyDBQAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/saptak-s_tone_hu_a8c210a09a9d9831.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Saptak S&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGLx9fUVExNjYmRkZGVlBQQAAP//DacBQqwiXq0AAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/saptak-s-b_w_hu_b49149c005bc2e9f.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/saptak/&#34;&gt;saptak s&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/abhishek\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Abhishek Sharma&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGLpK5n7h0uYxdpM6vlPHkAAAAD//yYcBTg&amp;#43;uUxjAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/abhi_tone_hu_139ee33c04c7befb.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Abhishek Sharma&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAH0lEQVR4nGKZPXv2f3Fx8f9M379/Z/j//z8DIAAA//9V2gn9S/OvbAAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/abhishek-sharma-b_w_hu_3c474648262868b8.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/abhishek/&#34;&gt;abhishek sharma&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;senior designer&#34;&gt;
    senior designer
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/lisa\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Lisa Steingräber&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGKpKNvGy/6PxUBTUJSPGRAAAP//HxQDTxKG5VQAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/lisa-steingraber_tone_hu_df8e579cc7854a7.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Lisa Steingräber&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGI5fPjwhw8fmFhZWbm5uQEBAAD//zWdBVBRGT2NAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/lisa_s_b_w_hu_fb9a7cd49417ebe2.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/lisa/&#34;&gt;lisa steingräber&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;ux designer &amp;amp; innovation consultant&#34;&gt;
    ux designer &amp;amp; innovation consultant
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/matt\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Matt Stempeck&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGIJiV7D8P8/iyPjKTaW/4AAAAD//ycJBXdjJLjjAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/matt_tone_hu_14941c89c2c9d954.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Matt Stempeck&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAH0lEQVR4nGKZOGHC35&amp;#43;/fjIyuri4/GVgYGAEBAAA//9W6gdru2MmRAAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/matt-stempeck-b_w_hu_db8759d32e2684f7.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/matt/&#34;&gt;matt stempeck&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;curator, civic tech field guide&#34;&gt;
    curator, civic tech field guide
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/rocio-armillas-tiseyra\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Rocío Armillas Tiseyra&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGIJiV7NyvSfRZyfkYXxPyAAAP//GmUDlEFWF4AAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/rocio-armillas-tiseyra-duotone_hu_b4072923f7fff14b.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Rocío Armillas Tiseyra&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGJRkNNiZmJiEdDSZP7zHxAAAP//Ck4C2bBuOIAAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/prime_capybara_74131_robotic_llama_-creative_-test_f81c318e-d34d-4082-8188-8c7a06cabff6_1_hu_681e770b3f4ebb70.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/rocio-armillas-tiseyra/&#34;&gt;rocío armillas tiseyra&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/bernard\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Bernard Tyers&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAH0lEQVR4nGIpLtz0/99/BgYWU/7n/9nZWRkAAQAA//9NHAbYxpPaaAAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/bernard-tyers_tone_hu_183a8fce4814e785.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Bernard Tyers&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAH0lEQVR4nGLZt2/fB2FhYUaWu3fv/n/27BkDIAAA//9TJgm11A3izwAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/bernard-tyers-b_w_hu_286e0fb556529d84.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/bernard/&#34;&gt;bernard tyers&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;user researcher &amp;amp; interaction designer, sane ux design&#34;&gt;
    user researcher &amp;amp; interaction designer, sane ux design
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/james-vasile\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;James Vasile&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAH0lEQVR4nGLpbdryj4OdmZGJ5csrBl3&amp;#43;DwyAAAAA//86SQXpmwyvGwAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/james-vasile_tone_hu_eb8e4131875ce20f.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;James Vasile&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGJJSkri5ORkYmVlZWdnBwQAAP//D4QBbPowY0IAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/james-vasile-b_w_hu_f76b94010d2f05fc.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/james-vasile/&#34;&gt;james vasile&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/nimisha\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Nimisha Vijay&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGLJSZzPyMrGkqB07xWDICAAAP//GtcD3FVM3yoAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/nimisha-vijay-tone_hu_3562f074991ab06b.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Nimisha Vijay&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGKZMmWKvLw8Mxsb28ePHwEBAAD//x5wBQZUUeLnAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/nimisha-vijay-b_w_hu_25339899e2d8c533.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/nimisha/&#34;&gt;nimisha vijay&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/veszna\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Veszna Wessenauer&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAH0lEQVR4nGKZ2Lf//&amp;#43;cH9/8zsf7&amp;#43;yiAtxMQACAAA//9j2wi5SWN82gAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/vezna_tone_hu_77f6d3db778028f7.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Veszna Wessenauer&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGLu6OgQFBRk&amp;#43;vr164cPHwABAAD//yksB4D0e4dOAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/veszna_bw_hu_7a957138534cc8ad.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/veszna/&#34;&gt;veszna wessenauer&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;senior program manager&#34;&gt;
    senior program manager
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/molly\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Molly Clare Wilson&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGJpS5/8X0iayV3t5/2nXwEBAAD//ylfBtKoWMKgAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/molly_tone_hu_240579f172eaaa7.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Molly Clare Wilson&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGJpaGiwtbVlunfv3s&amp;#43;fPwEBAAD//yubB8OavCvFAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/molly-wilson-b_w_hu_8b74124b446a190d.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/molly/&#34;&gt;molly clare wilson&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;senior designer &amp;amp; researcher&#34;&gt;
    senior designer &amp;amp; researcher
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/an-xiao-mina\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;An Xiao Mina&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGKpK1z27&amp;#43;cPFnXO1&amp;#43;L8XwABAAD//zO9BsJqfvI1AAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/ax-mina-duotone_hu_40d2cd6b0f197e3b.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;An Xiao Mina&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAHElEQVR4nGK5cvLY1x8/WU6cPnPrzn1AAAAA//9IIgpG34kEWAAAAABJRU5ErkJggg==&#34; data-src=&#34;https://superbloom.design/images/image-3-_hu_820b55a703d7d81f.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/an-xiao-mina/&#34;&gt;an xiao mina&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/tin-geber\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Tin Geber&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGI5vP7AocvfmT5&amp;#43;&amp;#43;ikrygIIAAD//0AvB9fmGh28AAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/tin-geber-duotone_hu_7c1449874f09575e.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Tin Geber&#34;
      src=&#34;data:image/jpeg;base64,/9j/2wCEACgcHiMeGSgjISMtKygwPGRBPDc3PHtYXUlkkYCZlo&amp;#43;AjIqgtObDoKrarYqMyP/L2u71////m8H////6/&amp;#43;b9//gBKy0tPDU8dkFBdviljKX4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;Pj4&amp;#43;P/AABEIAAIAAgMBIgACEQEDEQH/xAGiAAABBQEBAQEBAQAAAAAAAAAAAQIDBAUGBwgJCgsQAAIBAwMCBAMFBQQEAAABfQECAwAEEQUSITFBBhNRYQcicRQygZGhCCNCscEVUtHwJDNicoIJChYXGBkaJSYnKCkqNDU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6g4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV1tfY2drh4uPk5ebn6Onq8fLz9PX29/j5&amp;#43;gEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoLEQACAQIEBAMEBwUEBAABAncAAQIDEQQFITEGEkFRB2FxEyIygQgUQpGhscEJIzNS8BVictEKFiQ04SXxFxgZGiYnKCkqNTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqCg4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV1tfY2dri4&amp;#43;Tl5ufo6ery8/T19vf4&amp;#43;fr/2gAMAwEAAhEDEQA/AJwowOBS7R6D8qB0FLUlH//Z&#34; data-src=&#34;https://superbloom.design/images/tg-pfp_hu_3fe1cd1c7f691b94.jpg&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/tin-geber/&#34;&gt;tin geber&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;coach&#34;&gt;
    coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/tara-kelly\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Tara Kelly&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGLJSVn898cPFnvp938&amp;#43;fQQEAAD//zdvCJFoFVbSAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/tara-kelly-duotone_hu_2f3d30f1c52b9e76.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Tara Kelly&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGK5evXq06dPmdXV1S9fvgwIAAD//z2xCCQ2PcNkAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/tara-kelly-crop-b-w_hu_bb74ba599610da52.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/tara-kelly/&#34;&gt;tara kelly&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;communications lead&#34;&gt;
    communications lead
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/alicja-peszkowska\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Alicja Peszkowska&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAGklEQVR4nGJpyFvAx/KTRUX0HyMDCyAAAP//IKID3pkkw1AAAAAASUVORK5CYII=&#34; data-src=&#34;https://superbloom.design/images/alicja-peszkowska-duotone_hu_2de28d08f4b14e06.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Alicja Peszkowska&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAHklEQVR4nGIpLS2N&amp;#43;/TpkwQLGxubhYiICCMgAAD//0DVBTv21rRLAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/alicja-peszkowska-b-w_hu_4f46707c0aeb11b.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/alicja-peszkowska/&#34;&gt;alicja peszkowska&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;program manager, coaching &amp;amp; community&#34;&gt;
    program manager, coaching &amp;amp; community
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;article class=&#34;card card--people clickable&#34; onclick=&#34;window.location.href=&#39;\/about\/people\/jamie\/&#39;&#34;&gt;
  &lt;div class=&#34;image-wrapper&#34;&gt;
    &lt;img class=&#34;image lozad asterisk card__asterisk&#34; alt=&#34;Jamie Tomasello&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAG0lEQVR4nGLZ0DFz500OFrH31wOkBAEBAAD//y8gBctWvw/NAAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/jamie-tomasello-duotone_hu_bd8cb92aea1c1267.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;img class=&#34;image lozad&#34; alt=&#34;Jamie Tomasello&#34;
      src=&#34;data:image/jpeg;base64,iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAYAAABytg0kAAAAHklEQVR4nGKuqKhYoq6u/piZnZ29kZmZ2QIQAAD//zGgBEJhmOB5AAAAAElFTkSuQmCC&#34; data-src=&#34;https://superbloom.design/images/jamie-tomasello-b-w_hu_650b92f99a7d50d9.png&#34;
      width=&#34;280&#34; height=&#34;265&#34;&gt;
    &lt;/div&gt;
  &lt;h3 class=&#34;title card__title&#34;&gt;&lt;a class=&#34;name&#34; href=&#34;https://superbloom.design/about/people/jamie/&#34;&gt;jamie tomasello&lt;/a&gt;&lt;/h3&gt;
  &lt;h4 class=&#34;peopletitle&#34; data-default-title=&#34;senior fellow, coach&#34;&gt;
    senior fellow, coach
  &lt;/h4&gt;
&lt;/article&gt;

  &lt;/div&gt;


&lt;p&gt;Contact us at &lt;a href=&#34;mailto:coaching@superbloom.design&#34;&gt;coaching@superbloom.design&lt;/a&gt; for more information about pricing and structure. We look forward to talking more with you!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Our story</title>
      <link>https://superbloom.design/about/story/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/story/</guid>
      <description>&lt;div class=&#34;container&#34;&gt;
  &lt;div class=&#34;hero--action-5&#34;&gt;
    &lt;div class=&#34;hero--content&#34;&gt;
      &lt;h5 class=&#34;hero--header&#34; tabindex=&#34;0&#34;&gt;
        Our mission is to change who technology serves
      &lt;/h5&gt;
      &lt;section class=&#34;text&#34;&gt;
        &lt;p class=&#34;actiontext&#34; tabindex=&#34;0&#34;&gt;
          By prioritizing human-centered design, community-based research, and knowledge sharing, we’re shaping a collective online future where everyone has the knowledge, network, and tools they need to thrive.
        &lt;/p&gt;
        &lt;p class=&#34;actiontext&#34; tabindex=&#34;0&#34;&gt;
          
        &lt;/p&gt;
        &lt;p class=&#34;actiontext&#34; tabindex=&#34;0&#34;&gt;
          
        &lt;/p&gt;
      &lt;/section&gt;
      &lt;button class=&#34;button&#34;  onclick=&#34;window.location.href=&#39;\/work&#39;&#34;&gt;Learn about our approach &amp;gt;&lt;/button&gt;
    &lt;/div&gt;
    &lt;img class=&#34;hero--actionpic&#34; src=&#34;https://superbloom.design/images/our-story/illustration-match.svg&#34; alt=&#34;Striking a match.&#34;&gt;
  &lt;/div&gt;
&lt;/div&gt;
&lt;div class=&#34;container&#34;&gt;
  &lt;div class=&#34;hero--action-6&#34;&gt;
    &lt;div class=&#34;hero--content&#34;&gt;
      &lt;h4 class=&#34;hero--header&#34; tabindex=&#34;0&#34;&gt;
        From Simply Secure to Superbloom
      &lt;/h4&gt;
      &lt;section class=&#34;text&#34;&gt;
        &lt;p class=&#34;actiontext&#34; tabindex=&#34;0&#34;&gt;
          In 2022, we surveyed our community and discovered we had outgrown our Simply Secure name and branding. Through the same collaborative design process we champion with our partners, we landed on a new direction that conveys the breadth of our current work, as well as our values, practice, and growth: Superbloom: Changing Who Technology Serves.
        &lt;/p&gt;
        &lt;p class=&#34;actiontext&#34; tabindex=&#34;0&#34;&gt;
          Our vision is a world where everyone has the knowledge, network, and digital tools needed to enrich their lives. As Superbloom, we’re leveraging design as a transformative practice to shift power in the tech ecosystem to center people and their needs. We’re building and supporting a community focused on shaping our collective online future.
        &lt;/p&gt;
        &lt;p class=&#34;actiontext&#34; tabindex=&#34;0&#34;&gt;
          
        &lt;/p&gt;
      &lt;/section&gt;
    &lt;/div&gt;
    &lt;img class=&#34;hero--actionpic&#34; src=&#34;https://superbloom.design/images/our-story/illustration-hammering.svg&#34; alt=&#34;Hammering a nail.&#34;&gt;
  &lt;/div&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>Our Support</title>
      <link>https://superbloom.design/community/our-support/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/community/our-support/</guid>
      <description>&lt;div class=&#34;tabs&#34; role=&#34;tablist&#34;&gt;
&lt;input type=&#34;radio&#34; name=&#34;tab&#34; data-tab=&#34;fiscal-sponsorship&#34; class=&#34;tab tab-1 visually-hidden&#34; id=&#34;tab-controler-1&#34;  checked&gt;
&lt;label for=&#34;tab-controler-1&#34; id=&#34;tab-label-1&#34; role=&#34;tab&#34; aria-posinset=&#34;1&#34;&gt;fiscal sponsorship&lt;/label&gt;
&lt;div class=&#34;tab-content tab-content--fiscal-sponsorship&#34; role=&#34;tabpanel&#34; aria-labelledby=&#34;tab-label-1&#34;&gt;
  &lt;section class=&#34;page-section--inner section-hero img-right&#34;&gt;
  &lt;div class=&#34;page-section--content&#34;&gt;
    &lt;h3 id=&#34;superblooms-fiscal-sponsorship-program-is-an-ecosystem-of-projects-united-by-shared-values-shared-infrastructure-and-collective-impact&#34;&gt;Superbloom’s fiscal sponsorship program is an ecosystem of projects, united by shared values, shared infrastructure, and collective impact.&lt;/h3&gt;
&lt;p&gt;Too often, critical momentum on innovative projects run by small teams is lost to organizational overhead. The fiscal sponsorship model can help remove that friction.&lt;/p&gt;
&lt;p&gt;Superbloom leverages fiscal sponsorship to support the growth, development, and maturity of initiatives working to change who technology serves, with a focus on human-centered research and design-driven approaches.&lt;/p&gt;
&lt;p&gt;Since 2014, Superbloom has operated as a distributed, international team embedded in the communities we support. We work across diverse funding environments, including public and government funding, philanthropic grants, and individual donors, and provide flexible structures that support projects working across jurisdictions.&lt;/p&gt;
  &lt;/div&gt;
  &lt;div class=&#34;page-section--img&#34;&gt;
    &lt;img class=&#34;sectionpic&#34; src=&#34;https://superbloom.design/images/coaching/illustration-match.png&#34; alt=&#34;Illustration of striking a match&#34; /&gt;
  &lt;/div&gt;
  &lt;/section&gt;
&lt;h4 id=&#34;what-is-a-fiscally-sponsored-project&#34;&gt;What is a fiscally sponsored project?&lt;/h4&gt;
&lt;p&gt;Our fiscally sponsored projects are independent initiatives that operate within a shared ecosystem of public-interest work. Projects can leverage Superbloom’s fiscal sponsorship network to connect and collaborate, and to fundraise together, strengthening each other.&lt;/p&gt;
&lt;p&gt;As a California nonprofit corporation with a 501(c)(3) designation from the IRS, Superbloom provides the legal, financial, and operational infrastructure that enables projects to operate, access funding, and grow without the need to establish a standalone nonprofit organization. Projects benefit from Superbloom’s charitable status, governance, and support structures, while remaining independently led and responsible for their direction, delivery, and budget.&lt;/p&gt;
&lt;p&gt;Superbloom is responsible for stewardship, compliance, and fiduciary oversight, with support from our Board and team. In parallel, project leads are responsible for managing their work effectively, delivering on their objectives, and ensuring funds are budgeted and used appropriately.&lt;/p&gt;
&lt;p&gt;By operating within this shared framework, projects can reduce operational overhead, move more quickly, and contribute to a broader collective of aligned initiatives, strengthening both individual impact and the wider ecosystem.
&lt;br /&gt;&lt;/p&gt;
&lt;h3 id=&#34;active-fsps&#34;&gt;Active FSPs&lt;/h3&gt;
&lt;div class=&#34;image-grid&#34; style=&#34;gap: 2px; max-width: 100%;&#34;&gt;
  &lt;a href=&#34;https://chaoss.community/kb/local-chapters/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/CHAOSS-Africa.png&#34; alt=&#34;CHAOSS Africa&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;CHAOSS Africa&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://civictech.guide/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/Civic-Tech-Field-Guide.png&#34; alt=&#34;Civic Tech Field Guide&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Civic Tech Field Guide&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://www.dataumbrella.org/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/Data-Umbrella.png&#34; alt=&#34;Data Umbrella&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Data Umbrella&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://www.empathyintech.com/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/Empathy-In-Tech.png&#34; alt=&#34;Empathy In Tech&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Empathy In Tech&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://frameshifter.org/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/frameshifter.png&#34; alt=&#34;Frameshifter&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Frameshifter&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://platform.coop/about/icde/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/ICDE.png&#34; alt=&#34;Institute for the Cooperative Digital Economy&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Institute for the Cooperative Digital Economy&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://measurementlab.net&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/Mlab-logo-extended-blue.png&#34; alt=&#34;Measurement Lab&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Measurement Lab&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://namesake.fyi&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/namesake.jpg&#34; alt=&#34;Namesake&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Namesake&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://www.pitalumni.org/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/PIT-Network-Alumni.png&#34; alt=&#34;PIT Network Alumni&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;PIT Network Alumni&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://publicprivates.com/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/Public-Privates.png&#34; alt=&#34;Public Privates&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Public Privates&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://rankingdigitalrights.org&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/rdr-logo-blue.png&#34; alt=&#34;Ranking Digital Rights&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Ranking Digital Rights&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://realml.org&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/realml-logo-full-midnight-2.png&#34; alt=&#34;REAL ML&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;REAL ML&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://theupskillinglabs.org&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/USLLogo.png&#34; alt=&#34;The Upskilling Labs&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;The Upskilling Labs&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a  target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/fsp/SEA.png&#34; alt=&#34;Studio for Emergent Action&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Studio for Emergent Action&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
&lt;/div&gt;
&lt;br /&gt;
&lt;h4 id=&#34;why-does-superbloom-support-fiscally-sponsored-projects&#34;&gt;Why does Superbloom support fiscally sponsored projects?&lt;/h4&gt;
&lt;p&gt;We developed fiscally sponsored projects to strengthen and sustain public-interest work in digital rights and responsible technology. Too often, important initiatives are slowed down or constrained by the time, cost, and complexity of setting up independent organizations. Our fiscal sponsorship model removes that friction by providing shared infrastructure, governance, and support, allowing practitioners to focus on the work itself.&lt;/p&gt;
&lt;p&gt;At the same time, it brings these initiatives into a connected portfolio, where they can learn from one another, collaborate, and contribute to a broader ecosystem. Rather than focusing solely on individual projects, the goal is to drive collective impact by strengthening resilience, accountability and effectiveness across the field.&lt;/p&gt;
&lt;br /&gt;
&lt;h4 id=&#34;what-services-does-superbloom-provide-to-fiscally-sponsored-projects-and-what-is-the-fee-structure&#34;&gt;What services does Superbloom provide to fiscally sponsored projects, and what is the fee structure?&lt;/h4&gt;
&lt;p&gt;Superbloom provides the operational infrastructure behind each project, including HR, people operations, and financial management. &lt;a href=&#34;https://superbloom.design/learning/resources/Superbloom_Fiscal_Sponsorship_2026-02_Overview.pdf&#34;&gt;See our services brochure&lt;/a&gt; for full details on our administrative offerings and fees.&lt;/p&gt;
&lt;br /&gt;
&lt;h4 id=&#34;what-do-we-look-for-in-fiscally-sponsored-projects&#34;&gt;What do we look for in fiscally sponsored projects?&lt;/h4&gt;
&lt;p&gt;Superbloom’s overall mission is to transform the current design paradigm in tech by centering the needs of people. We believe technology design is integral to the open source movement and should be leveraged to affect societal change.&lt;/p&gt;
&lt;p&gt;We support projects that advance digital rights and responsible technology, grounded in strong practitioner leadership and a clear path to impact. We are particularly interested in work that is shaped by real-world challenges and brings a clear perspective on power, accountability, and how technology is designed, governed, or experienced. We also support work that goes beyond tool-building, spanning research, policy, education and practice that shifts how technology operates in the public interest.&lt;/p&gt;
&lt;p&gt;Our portfolio is intentionally curated. We prioritise projects that not only succeed individually but also strengthen our wider ecosystem of practice, working collectively toward more usable, secure, and accountable technology systems.&lt;/p&gt;
&lt;br /&gt;
&lt;h4 id=&#34;what-are-the-expectations-for-a-fiscally-sponsored-project-at-superbloom&#34;&gt;​​What are the expectations for a fiscally sponsored project at Superbloom?&lt;/h4&gt;
&lt;p&gt;As a fiscally sponsored project, you are responsible for your work and maintaining healthy relationships with the community. This includes managing your budget, delivering on your objectives, and ensuring the project is run effectively.&lt;/p&gt;
&lt;p&gt;As a steward, Superbloom supports you with operational infrastructure, compliance, and strategic guidance, but project leadership and accountability sit with you. Fiscal sponsorship is a collaborative partnership, grounded in trust, shared values, and clear responsibilities on both sides.&lt;/p&gt;
&lt;br /&gt;
&lt;h4 id=&#34;how-does-my-project-apply-for-fiscal-sponsorship&#34;&gt;How does my project apply for fiscal sponsorship?&lt;/h4&gt;
&lt;p&gt;If your project aligns with our mission and you’re interested in learning more, please get in touch by completing &lt;a href=&#34;https://superbloom.design/fiscal-sponsorship-interest/&#34;&gt;this form&lt;/a&gt;. A member of our Fiscal Sponsorship Project team will follow up in due course. We are currently reviewing applications on a quarterly basis.&lt;/p&gt;
&lt;br /&gt;
&lt;h4 id=&#34;how-does-superbloom-hold-and-manage-public-interest-funding&#34;&gt;How does Superbloom hold and manage public-interest funding?&lt;/h4&gt;
&lt;p&gt;As a US 501(c)(3) public charity, Superbloom operates within the legal and regulatory frameworks that govern non-profit organizations. This means there are clear boundaries on how funds can be used and what activities we can support. For example, Superbloom does not engage in or support political campaign activity, including contributions to candidates or coordination with electoral campaigns.&lt;/p&gt;
&lt;p&gt;We also do not act as a passive conduit for funds. All funding received is stewarded under Superbloom’s charitable mandate, with responsibility for ensuring it is used in line with its intended public-interest purpose. This includes financial oversight, governance, and compliance managed by our board and team.&lt;/p&gt;
&lt;br /&gt;
&lt;p&gt;&lt;button class=&#34;button clickable&#34; aria-label=&#34;Donate&#34;&gt;&lt;a class=&#34;&#34;
href=&#34;https://superbloom.design/fiscal-sponsorship-interest/&#34; &gt;Express Interest in Fiscal Sponsorship&lt;/a&gt;
&lt;/button&gt;&lt;/p&gt;

    &lt;/div&gt;

&lt;input type=&#34;radio&#34; name=&#34;tab&#34; data-tab=&#34;coaching&#34; class=&#34;tab tab-2 visually-hidden&#34; id=&#34;tab-controler-2&#34; &gt;
&lt;label for=&#34;tab-controler-2&#34; id=&#34;tab-label-2&#34; role=&#34;tab&#34; aria-posinset=&#34;2&#34;&gt;coaching&lt;/label&gt;
&lt;div class=&#34;tab-content tab-content--coaching&#34; role=&#34;tabpanel&#34; aria-labelledby=&#34;tab-label-2&#34;&gt;
  &lt;section class=&#34;page-section--inner section-hero img-right&#34;&gt;
  &lt;div class=&#34;page-section--content&#34;&gt;
    &lt;h2 id=&#34;we-offer-tailored-coaching-for-individuals-and-teams-working-on-open-source-and-public-interest-technology&#34;&gt;We offer tailored coaching for individuals and teams working on open-source and public interest technology.&lt;/h2&gt;
&lt;p&gt;Our pragmatic approach to capacity-building gives you tools and techniques to dramatically improve the impact of your work. We focus on collaborative goal-setting and take a human-centered approach to helping you help your community.  Our experienced coaching team covers all global time zones and works in at least 15 languages.&lt;/p&gt;
  &lt;/div&gt;
  &lt;div class=&#34;page-section--img&#34;&gt;
    &lt;img class=&#34;sectionpic&#34; src=&#34;https://superbloom.design/images/community/illustration-paintbrush.png&#34; alt=&#34;Illustration of striking a match&#34; /&gt;
  &lt;/div&gt;
  &lt;/section&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
  &lt;div class=&#34;container container--columns&#34;&gt;
  &lt;div class=&#34;columns&#34;&gt;
  &lt;strong&gt;Are you a funder or a fiscal host? Let’s design a custom program to support your teams.&lt;/strong&gt;
&lt;button class=&#34;button clickable&#34; aria-label=&#34;Donate&#34;&gt;&lt;a class=&#34;&#34;
href=&#34;https://superbloom.design/community/our-support/funders&#34; &gt;Learn more&lt;/a&gt;
&lt;/button&gt;
  &lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;br /&gt;
&lt;section class=&#34;page-section--inner &#34;&gt;
  &lt;div class=&#34;page-section--content&#34;&gt;
    &lt;h2 id=&#34;we-help-you-with-the-human-aspects-of-tech&#34;&gt;We help you with the human aspects of tech&lt;/h2&gt;
&lt;p&gt;From product design to community governance, from fundraising to communication, from naming and branding to information architecture: &lt;strong&gt;we help your project connect with the real world.&lt;/strong&gt;&lt;/p&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;How do people find, use, figure out, and learn about your project?&lt;/li&gt;
&lt;li&gt;How does your team work together and keep your project going?&lt;/li&gt;
&lt;li&gt;How does your project flourish in society and create change?&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;p&gt;We’re here to provide you with customized support for these questions and more. &lt;a href=&#34;#coaching-topics&#34;&gt;See all topics we cover&lt;/a&gt;.&lt;/p&gt;
  &lt;/div&gt;
  &lt;/section&gt;
&lt;section class=&#34;page-section--inner section-flex img-right&#34;&gt;
  &lt;div class=&#34;page-section--content&#34;&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;h2 id=&#34;what-we-do&#34;&gt;What we do&lt;/h2&gt;
&lt;p&gt;We work with &lt;strong&gt;projects&lt;/strong&gt;, &lt;strong&gt;teams&lt;/strong&gt;, &lt;strong&gt;organizations&lt;/strong&gt;, &lt;strong&gt;companies&lt;/strong&gt;, &lt;strong&gt;fiscal hosts&lt;/strong&gt;, and &lt;strong&gt;funders&lt;/strong&gt;. We offer:&lt;/p&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Targeted 1:1 problem-solving sessions focused on your needs.&lt;/li&gt;
&lt;li&gt;“Ask Me Anything” sessions with a panel of coaches: you bring your questions and we work on them together.&lt;/li&gt;
&lt;li&gt;Reusable tool and template creation for your group or team.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;p&gt;Are you a funder or fiscal host? We design &lt;a href=&#34;funders/&#34;&gt;collaborations with funders&lt;/a&gt; in the public interest technology space, offering grantee accompaniment to help support and enhance their impact. &lt;a href=&#34;funders/&#34;&gt;We design custom coaching programs to support your teams.&lt;/a&gt;&lt;/p&gt;
  &lt;/div&gt;
  &lt;div class=&#34;page-section--img&#34;&gt;
    &lt;img class=&#34;sectionpic&#34; src=&#34;https://superbloom.design/images/coaching/illustration-match.png&#34; alt=&#34;Minimalist line drawing of hands striking match&#34; /&gt;
  &lt;/div&gt;
  &lt;/section&gt;
&lt;section class=&#34;page-section--inner section-flex img-right&#34;&gt;
  &lt;div class=&#34;page-section--content&#34;&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;h2 id=&#34;our-approach&#34;&gt;Our approach&lt;/h2&gt;
&lt;p&gt;Our coaching and mentoring is &lt;a href=&#34;https://superbloom.design/work/&#34;&gt;informed by our values&lt;/a&gt; every step of the way.&lt;/p&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;&lt;span&gt;&lt;strong&gt;We help you serve your community&lt;/strong&gt;, using methods from human-centered and human-rights-centered design.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;strong&gt;We collaborate to create the sessions that work for you&lt;/strong&gt;. We build your capacity, showing you the way and creating reusable resources.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;strong&gt;We are practitioners, just like you&lt;/strong&gt;. We aren’t afraid to roll up our sleeves and pick up tools when that’s what you need.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;strong&gt;We triage, prioritize, and focus&lt;/strong&gt;. We help you get things done when time and resources are limited.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;strong&gt;We center your community’s privacy and security needs&lt;/strong&gt; and threat model. We use secure and open-source tools wherever possible.&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
  &lt;/div&gt;
  &lt;div class=&#34;page-section--img&#34;&gt;
    &lt;img class=&#34;sectionpic&#34; src=&#34;https://superbloom.design/images/coaching/illustration-postit.png&#34; alt=&#34;Minimalist line drawing of hands writing on post-it note&#34; /&gt;
  &lt;/div&gt;
  &lt;/section&gt;
&lt;section class=&#34;page-section--inner &#34;&gt;
  &lt;div class=&#34;page-section--content&#34;&gt;
    &lt;h2 id=&#34;coaching-topics&#34;&gt;Coaching topics&lt;/h2&gt;
&lt;p&gt;We offer coaching on these topics and more. If you don’t see what you need, &lt;a href=&#34;mailto:coaching@superbloom.design&#34;&gt;get in touch&lt;/a&gt;! We can find the right people to work with you.&lt;/p&gt;
&lt;div class=&#34;container container--columns columns-3&#34;&gt;
  &lt;div class=&#34;columns&#34;&gt;
  &lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;UX design + product strategy&lt;/li&gt;
&lt;li&gt;Interface design&lt;/li&gt;
&lt;li&gt;Illustration + visual design&lt;/li&gt;
&lt;li&gt;User research&lt;/li&gt;
&lt;li&gt;Information architecture&lt;/li&gt;
&lt;li&gt;Writing + communication&lt;/li&gt;
&lt;li&gt;Accessibility&lt;/li&gt;
&lt;li&gt;Branding&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Data handling&lt;/li&gt;
&lt;li&gt;Naming&lt;/li&gt;
&lt;li&gt;Conference presentations&lt;/li&gt;
&lt;li&gt;Governance&lt;/li&gt;
&lt;li&gt;Team dynamics&lt;/li&gt;
&lt;li&gt;Workflows&lt;/li&gt;
&lt;li&gt;GDPR + privacy&lt;/li&gt;
&lt;li&gt;Workshop + facilitation design&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Documentation&lt;/li&gt;
&lt;li&gt;Licensing&lt;/li&gt;
&lt;li&gt;Fundraising + sustainability&lt;/li&gt;
&lt;li&gt;Narratives + framing&lt;/li&gt;
&lt;li&gt;Open source community dynamics&lt;/li&gt;
&lt;li&gt;Open processes&lt;/li&gt;
&lt;li&gt;Design tooling&lt;/li&gt;
&lt;li&gt;Usability&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;
&lt;br /&gt;
&lt;p&gt;If you need something you don’t see here, let us know at &lt;a href=&#34;mailto:coaching@superbloom.design&#34;&gt;coaching@superbloom.design&lt;/a&gt;, and we’ll connect you with the right people.&lt;/p&gt;
  &lt;/div&gt;
  &lt;div class=&#34;page-section--img&#34;&gt;
    &lt;img class=&#34;sectionpic&#34; src=&#34;https://superbloom.design/images/coaching/illustration-hammering.png&#34; alt=&#34;Minimalist line drawing of hands hammering nail&#34; /&gt;
  &lt;/div&gt;
  &lt;/section&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;section class=&#34;page-section--inner &#34;&gt;
  &lt;div class=&#34;page-section--content&#34;&gt;
    &lt;h2 id=&#34;our-partners&#34;&gt;Our partners&lt;/h2&gt;
&lt;p&gt;Our current and past coaching partners include individual projects, foundations, funders, and fiscal hosts. (In fact, we’ve coached over 300 projects since we were founded in 2014!). Projects we&amp;rsquo;ve coached include:&lt;/p&gt;
  &lt;/div&gt;
  &lt;/section&gt;
&lt;section class=&#34;page-section--inner &#34;&gt;
  &lt;div class=&#34;page-section--content&#34;&gt;
    &lt;div class=&#34;image-grid&#34; style=&#34;gap: 2px; max-width: 100%;&#34;&gt;
  &lt;a href=&#34;https://prototypefund.de&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/partners/PrototypeFund-P-Logo.png&#34; alt=&#34;Prototype Fund&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Prototype Fund&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://www.mozilla.org/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/partners/mozilla-logo.png&#34; alt=&#34;Mozilla&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Mozilla&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://prereview.org/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/partners/prereview-logo.webp&#34; alt=&#34;PREreview&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;PREreview&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://measurementlab.org/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/partners/mlab-logo.png&#34; alt=&#34;M-Lab&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;M-Lab&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://www.turing.ac.uk/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/partners/turing-project.png&#34; alt=&#34;The Turing Way project at The Turing Institute&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;The Turing Way project at The Turing Institute&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://awana.digital/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/partners/MAPEO.webp&#34; alt=&#34;Awana Digital&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Awana Digital&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
  &lt;a href=&#34;https://helpfulplaces.org/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34; style=&#34;text-decoration: none; color: inherit;&#34;&gt;
    &lt;figure class=&#34;grid-item&#34;
      style=&#34;margin: 0; padding: 20px; display: flex; flex-direction: column; align-items: center; justify-content: center;&#34;&gt;
      &lt;div style=&#34;height: 200px; display: flex; align-items: center; justify-content: center;&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/images/partners/helpful-places-logo.webp&#34; alt=&#34;Helpful Places&#34; loading=&#34;lazy&#34;
          style=&#34;max-width: 100%; max-height: 100%; width: auto; height: auto;&#34;&gt;
      &lt;/div&gt;
      &lt;figcaption class=&#34;grid-item-name&#34; style=&#34;text-align: center; margin-top: 10px;&#34;&gt;Helpful Places&lt;/figcaption&gt;
    &lt;/figure&gt;
  &lt;/a&gt;
&lt;/div&gt;
  &lt;/div&gt;
  &lt;/section&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;section class=&#34;page-section--inner &#34;&gt;
  &lt;div class=&#34;page-section--content&#34;&gt;
    &lt;h2 id=&#34;our-coaches&#34;&gt;Our coaches&lt;/h2&gt;
&lt;p&gt;Our coaching team has deep professional experience in many different verticals related to design, research, strategy, product, fundraising, and sustainability. &lt;a href=&#34;https://superbloom.design/about/people/#coaches&#34;&gt;Find out more about our coaches here&lt;/a&gt;.&lt;/p&gt;
  &lt;/div&gt;
  &lt;/section&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;section class=&#34;page-section--inner &#34;&gt;
  &lt;div class=&#34;page-section--content&#34;&gt;
    &lt;h2 id=&#34;get-in-touch&#34;&gt;Get in touch&lt;/h2&gt;
&lt;p&gt;To learn more about our coaching offerings or to &lt;a href=&#34;coaches/&#34;&gt;discuss joining us as a coach&lt;/a&gt;, write &lt;a href=&#34;mailto:coaching@superbloom.design&#34;&gt;coaching@superbloom.design&lt;/a&gt; and one of our coaching team will get back to you.&lt;/p&gt;
&lt;div class=&#34;container container--columns&#34;&gt;
  &lt;div class=&#34;columns&#34;&gt;
  &lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Georgia Bullen, Executive Director&lt;/li&gt;
&lt;li&gt;Nicola Pratt, Project Coordinator&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Molly Wilson, Learning Lead&lt;/li&gt;
&lt;li&gt;Victory Brown, Community Building Lead&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;
  &lt;/div&gt;
  &lt;/section&gt;

    &lt;/div&gt;

&lt;/div&gt;

</description>
    </item>
    
    <item>
      <title>Superbloom Board and Governance Overview</title>
      <link>https://superbloom.design/about/board/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/board/</guid>
      <description>&lt;div class=&#34;container&#34; id=&#34;action-3&#34; role=&#34;group&#34; aria-label=&#34;Hero section&#34;&gt;
  &lt;div class=&#34;hero--action-3&#34;&gt;
    &lt;div class=&#34;hero--content hero--actioncontainer&#34;&gt;
      &lt;h2 class=&#34;hero--header&#34; tabindex=&#34;0&#34;&gt;
        
      &lt;/h2&gt;
      &lt;section class=&#34;text&#34;&gt;
        &lt;p class=&#34;actiontext&#34; tabindex=&#34;0&#34;&gt;
          Superbloom Design is a US 501c3 and is governed by a Board of Directors. The Board of Directors works in a voluntary capacity to support the organization in driving impact against its strategic goals. The Board of Directors has the fiduciary responsibility to ensure the financial health of the organization, maintain strong operational practices, and remains in compliance with its legal obligations. Superbloom also has an Advisory Council which is comprised of experts from the ecosystem who provide strategic advice to the Superbloom Board and team.
        &lt;/p&gt;
        &lt;p class=&#34;actiontext&#34; tabindex=&#34;0&#34;&gt;
          
        &lt;/p&gt;
        &lt;p class=&#34;actiontext&#34; tabindex=&#34;0&#34;&gt;
          
        &lt;/p&gt;
      &lt;/section&gt;
    &lt;/div&gt;
    &lt;img class=&#34;actionpic&#34; src=&#34;https://superbloom.design/images/our-work/illustration-knitting.svg&#34; alt=&#34;Two hands knitting.&#34;&gt;
  &lt;/div&gt;
&lt;/div&gt;
&lt;!-- Board Criteria &amp; FAQs 
&#34;Using design as a transformative practice to shift power in the tech ecosystem, Superbloom applies a holistic approach and views design as an intervention opportunity to center people and their needs. Its vision is a world where everyone has the knowledge, network, and digital tools needed to enrich their life. It works to build and inform technology, resources and programs that protect people&#39;s dignity, safety and privacy. It leverages practices from human rights, systems thinking, service design and threat modeling to help teams design technology and services that are responsible, respectful, and inclusive. It has a proven history of partnering with critical organizations in the ecosystem to dig into user experience challenges and needs, evaluate the service design of their offerings, and provide recommendations for improvement.&#34;

--&gt;
&lt;!-- ## About a non-profit governance

The Board of Directors is the governing body of a non-profit. Individuals who sit on the board are responsible for overseeing the organization’s activities. Board members meet periodically to discuss and vote on the affairs of the organization. Its Board is different from its management team because governance is high level: strategy, oversight, accountability. Management is the day-to-day operations of a non-profit. The Board, as a governing body, focuses on the organization’s mission, strategy, and goals; staff members are responsible for the implementation of the mission. Learn more about [nonprofit governance](https://www.councilofnonprofits.org/running-nonprofit/governance-leadership/good-governance-policies-nonprofits) from the National Council of Nonprofits. --&gt;
&lt;h2 id=&#34;current-board&#34;&gt;Current Board&lt;/h2&gt;
&lt;!-- ADD CURRENT PEOPLE WIDGET - Superbloom Board Members --&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/jackie/&#34;&gt;Jacqueline Lu&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/jasmine/&#34;&gt;Jasmine McNealy&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/erika-owens/&#34;&gt;Erika Owens&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/adriana-valdez-young/&#34;&gt;Adriana Valdez Young&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;h2 id=&#34;current-advisory-council&#34;&gt;Current Advisory Council&lt;/h2&gt;
&lt;!-- ADD CURRENT PEOPLE WIDGET - Superbloom Advisory Board --&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;http://www0.cs.ucl.ac.uk/people/A.Sasse.html&#34;&gt;Angela Sasse&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/benlaurie&#34;&gt;Ben Laurie&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://craphound.com/&#34;&gt;Cory Doctorow&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/gdanezis&#34;&gt;George Danezis&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://wendy.seltzer.org/&#34;&gt;Wendy Seltzer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.linkedin.com/in/dorothy-chou-647a0b4/&#34;&gt;Dorothy Chou&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.reset.tech/people/&#34;&gt;Ben Scott&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/scout/&#34;&gt;Sara &amp;ldquo;Scout&amp;rdquo; Brody&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;h2 id=&#34;board-make-up-and-selection-criteria&#34;&gt;Board make-up and selection criteria&lt;/h2&gt;
&lt;p&gt;The Superbloom Board of Directors is made up of experts in the public interest technology space who apply a critical lens to technology, and believe that design is a lever for changing who technology serves. Board Members bring a diverse, socio technical range of expertise in areas such as technology, design, organizational management, privacy and security, open source, human rights, digital rights, communications, fundraising, and social change. Its Board has a strong interest in stewarding and connecting its network with the organization and provides credibility in a given context and/or discipline.&lt;/p&gt;
&lt;p&gt;The following criteria are employed when selecting new Board members:&lt;/p&gt;
&lt;h4 id=&#34;practitioners-and-established-leaders&#34;&gt;Practitioners and established leaders&lt;/h4&gt;
&lt;p&gt;The Board should include both practitioners and established leaders: Superbloom’s Board of Directors has established leaders and decision-makers within their organizations and fields. Established leaders provide a crucial view and the ability to get things done. This view is balanced by members who are working practitioners, leading from the ground. Their views and experiences guide Superbloom to prioritize realistic action that’s informed by needs for the communities we serve.&lt;/p&gt;
&lt;h4 id=&#34;culture-add-vs-culture-fit&#34;&gt;Culture add vs culture fit&lt;/h4&gt;
&lt;p&gt;When we talk about “fit”, we gravitate toward candidates who are like us: people who fluently speak our language (figuratively and literally), who represent ideas we resonate with, and with whom we are comfortable. Superbloom’s growth and stability depends on including different cultural backgrounds on its Board; each with different perspectives and ideas.&lt;/p&gt;
&lt;h4 id=&#34;profile-vs-potential&#34;&gt;Profile vs potential&lt;/h4&gt;
&lt;p&gt;Just as Board members bring their profile and experience to Superbloom, it invests in the potential and growth of its Board members by providing access to global conversations and a broader community of colleagues.&lt;/p&gt;
&lt;h4 id=&#34;established-vs-atypical-title-and-education&#34;&gt;Established vs atypical title and education&lt;/h4&gt;
&lt;p&gt;Systems of power from the global north and western culture tend to prioritize hierarchical positions (executives) and specific formal education (doctorates). This prioritizes western cultural tendencies, and excludes the more democratic view of expertise that it support in its values including different skillsets and backgrounds.&lt;/p&gt;
&lt;h2 id=&#34;expectations&#34;&gt;Expectations&lt;/h2&gt;
&lt;p&gt;The Board’s remit includes:&lt;/p&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Support Superbloom’s mission, purpose and long-term strategy&lt;/li&gt;
&lt;li&gt;Work with the interests of the non-profit to ensure the organization is well managed and on a sound financial footing&lt;/li&gt;
&lt;li&gt;Oversight of Superbloom programs&lt;/li&gt;
&lt;li&gt;Oversight of Executive Director&lt;/li&gt;
&lt;li&gt;General mentorship for leadership, staff, and fiscally sponsored project leads&lt;/li&gt;
&lt;li&gt;Attend meetings, provide strategic input and guidance, accountability on leadership&lt;/li&gt;
&lt;li&gt;Understand and obey governing documents and laws&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;h2 id=&#34;commitment&#34;&gt;Commitment&lt;/h2&gt;
&lt;p&gt;Its Board members commit to approximately one hour-long Board meeting per month, one Annual Board meeting, and when applicable, vote on the information provided. In addition, its Executive Director may call upon Board members for ad hoc 1:1 guidance or small group meetings on specific topics. The Board also has a Secretary who reviews and approves meeting minutes, and a Treasurer who reviews and signs-off on taxes and other financial documents.&lt;/p&gt;
&lt;h2 id=&#34;more-information&#34;&gt;More information&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/work/&#34;&gt;About Our Work&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/#board-of-directors&#34;&gt;Current and Previous Board Members&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/funding/#funding-history&#34;&gt;History of Financial Support&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Funding</title>
      <link>https://superbloom.design/about/funding/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/funding/</guid>
      <description>&lt;div class=&#34;tabs&#34; role=&#34;tablist&#34;&gt;
&lt;input type=&#34;radio&#34; name=&#34;tab&#34; data-tab=&#34;support-us&#34; class=&#34;tab tab-1 visually-hidden&#34; id=&#34;tab-controler-1&#34;  checked&gt;
&lt;label for=&#34;tab-controler-1&#34; id=&#34;tab-label-1&#34; role=&#34;tab&#34; aria-posinset=&#34;1&#34;&gt;support us&lt;/label&gt;
&lt;div class=&#34;tab-content tab-content--support-us&#34; role=&#34;tabpanel&#34; aria-labelledby=&#34;tab-label-1&#34;&gt;
  &lt;p&gt;&lt;button class=&#34;button clickable&#34; aria-label=&#34;Donate&#34;&gt;&lt;a class=&#34;&#34;
href=&#34;https://www.every.org/superbloom?suggestedAmounts=50%2C100%2C250%2C500%2C1000&amp;amp;theme_color=424faa&amp;amp;utm_campaign=donate-link#/donate&#34; &gt;Donate to support our work.&lt;/a&gt;
&lt;/button&gt;&lt;/p&gt;
&lt;br /&gt;
&lt;h2 id=&#34;we-rely-on-your-support-to-create-broad-impact&#34;&gt;We rely on your support to create broad impact.&lt;/h2&gt;
&lt;br /&gt;
&lt;p&gt;Support at any level enables us to build and connect our community, promote leadership through fellowships and sponsorships, and develop resources to help change who technology serves.&lt;/p&gt;
&lt;p&gt;Superbloom is a registered US 501(c)3 nonprofit. We work with &lt;a href=&#34;https://www.every.org/superbloom?suggestedAmounts=50%2C100%2C250%2C500%2C1000&amp;amp;theme_color=424faa&amp;amp;utm_campaign=donate-link#/donate&#34;&gt;Every.org&lt;/a&gt; to accept tax-deductible charitable donations by credit card, Venmo, PayPal, bank transfers, stock donations, and DAF pay. Your donation is made to Every.org, a tax-exempt US 501(c)3 that gifts unrestricted funds to Superbloom Design on your behalf. Superbloom Design will honor any designations detailed in the donation information. Donating via Every.org means that we receive every cent of your donation. A donation acknowledgement letter is sent for all donations over $75.&lt;/p&gt;
&lt;p&gt;For other methods of payment (ACH/Wire) see more information below, and reach out to us for support via email: &lt;a href=&#34;mailto:donations@superbloom.design&#34;&gt;donations@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Your kind and generous support of Superbloom enables us to continue to change who technology serves.&lt;/p&gt;
&lt;p&gt;&lt;button class=&#34;button clickable&#34; aria-label=&#34;Donate&#34;&gt;&lt;a class=&#34;&#34;
href=&#34;https://www.every.org/superbloom?suggestedAmounts=50%2C100%2C250%2C500%2C1000&amp;amp;theme_color=424faa&amp;amp;utm_campaign=donate-link#/donate&#34; &gt;Donate now.&lt;/a&gt;
&lt;/button&gt;&lt;/p&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;h4 id=&#34;additional-options&#34;&gt;Additional options&lt;/h4&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;&lt;strong&gt;ACH/Wire&lt;/strong&gt;: Please email &lt;a href=&#34;mailto:donations@superbloom.design&#34;&gt;donations@superbloom.design&lt;/a&gt; for wire/ACH instructions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Check&lt;/strong&gt;: Please make checks payable to Superbloom Design, and please email &lt;a href=&#34;mailto:donations@superbloom.design&#34;&gt;donations@superbloom.design&lt;/a&gt; for our mailing address for checks.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Wise&lt;/strong&gt;: Wise allows us to accept direct deposit payments in a variety of currencies (e.g. Euros, GBP, and more). If you would like to donate via Wise, please email &lt;a href=&#34;mailto:donations@superbloom.design&#34;&gt;donations@superbloom.design&lt;/a&gt; and we can share a currency-specific link.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.paypal.com/ncp/payment/TAJ4KKJ3B32ZN&#34;&gt;&lt;strong&gt;PayPal&lt;/strong&gt;&lt;/a&gt;: Every.org accepts PayPal as a payment method, but you can also give directly to us on Paypal if you would like.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://opencollective.com/superbloom/donate?interval=oneTime&amp;amp;amount=20&amp;amp;name=&amp;amp;legalName=&amp;amp;email=&#34;&gt;&lt;strong&gt;Open Collective&lt;/strong&gt;&lt;/a&gt;: Open Collective is a platform focused on increasing openness, transparency, and support in grassroots fundrasing. Superbloom and our fiscally sponsored projects are on Open Collective, if you would like to leverage the platform to support our work.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;

    &lt;/div&gt;

&lt;input type=&#34;radio&#34; name=&#34;tab&#34; data-tab=&#34;transparency&#34; class=&#34;tab tab-2 visually-hidden&#34; id=&#34;tab-controler-2&#34; &gt;
&lt;label for=&#34;tab-controler-2&#34; id=&#34;tab-label-2&#34; role=&#34;tab&#34; aria-posinset=&#34;2&#34;&gt;transparency&lt;/label&gt;
&lt;div class=&#34;tab-content tab-content--transparency&#34; role=&#34;tabpanel&#34; aria-labelledby=&#34;tab-label-2&#34;&gt;
  &lt;br /&gt;
&lt;h2 id=&#34;financial-transparency&#34;&gt;Financial transparency&lt;/h2&gt;
&lt;br /&gt;
&lt;p&gt;Superbloom is supported through individual donations, collaborative projects, event sponsorships, grants and awards from an array of nonprofit and corporate organizations in the U.S. and Europe. We strive for transparency and independence in all of our financial relationships. To ensure independence and integrity, we ask ourselves the following before applying to a project, accepting an invitation to collaborate on a project, or accepting a grant award or donation:&lt;/p&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Are the organization’s intentions transparent and do they align with our core values?&lt;/li&gt;
&lt;li&gt;Is the program or project beneficial to the communities it’s intended to serve? Are those communities involved in the work itself?&lt;/li&gt;
&lt;li&gt;Does this project or program have proper processes and safeguards in place to ensure it will not do harm in the form of mishandling data, dark patterns, or targeting vulnerable populations?&lt;/li&gt;
&lt;li&gt;Will the project further our overall mission?&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;p&gt;Finally, we accept support contingent upon the following non-negotiables:&lt;/p&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Superbloom does not accept funding that places our team, partners, community members, or mission at risk.&lt;/li&gt;
&lt;li&gt;Superbloom does not accept funding that compromises our relationships with partners, community members, stakeholders, or networks.&lt;/li&gt;
&lt;li&gt;Superbloom does not accept funding that compromises our organizational independence, including funding that may influence programmatic priorities.&lt;/li&gt;
&lt;li&gt;Superbloom does not accept funding that poses a risk to our reputation. This statement was adapted under CC-BY license from Access Now.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;

    &lt;/div&gt;

&lt;input type=&#34;radio&#34; name=&#34;tab&#34; data-tab=&#34;funding-history&#34; class=&#34;tab tab-3 visually-hidden&#34; id=&#34;tab-controler-3&#34; &gt;
&lt;label for=&#34;tab-controler-3&#34; id=&#34;tab-label-3&#34; role=&#34;tab&#34; aria-posinset=&#34;3&#34;&gt;funding history&lt;/label&gt;
&lt;div class=&#34;tab-content tab-content--funding-history&#34; role=&#34;tabpanel&#34; aria-labelledby=&#34;tab-label-3&#34;&gt;
  &lt;!---## Current funding partners:

&lt;section class=&#34;table-wrapper&#34;&gt;
  &lt;table class=&#34;table-grid&#34;&gt;
    &lt;tr class=&#34;row&#34;&gt;
      &lt;td class=&#34;cell&#34;&gt;&lt;img src=&#34;https://superbloom.design/images/about-us/otf-logo.svg&#34; alt=&#34;Open Technology Fund&#34;&gt;&lt;/td&gt;
      &lt;td class=&#34;cell&#34;&gt;&lt;img src=&#34;https://superbloom.design/images/about-us/reset-logo.svg&#34; alt=&#34;Reset Network&#34;&gt;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr class=&#34;row&#34;&gt;
      &lt;td class=&#34;cell&#34;&gt;&lt;img src=&#34;https://superbloom.design/images/about-us/pf-logo.svg&#34; alt=&#34;Reset Network&#34;&gt;&lt;/td&gt;
      &lt;td class=&#34;cell&#34;&gt;&lt;img src=&#34;https://superbloom.design/images/about-us/mozilla-logo.svg&#34; alt=&#34;Reset Network&#34;&gt;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr class=&#34;row&#34;&gt;
      &lt;td class=&#34;cell&#34;&gt;&lt;img src=&#34;https://superbloom.design/images/about-us/usable-logo.svg&#34; alt=&#34;Reset Network&#34;&gt;&lt;/td&gt;
      &lt;td class=&#34;cell&#34;&gt;&lt;img src=&#34;https://superbloom.design/images/about-us/ai-logo.svg&#34; alt=&#34;Reset Network&#34;&gt;&lt;/td&gt;
    &lt;/tr&gt;
  &lt;/table&gt;
&lt;/section&gt; --&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;h3 id=&#34;2022&#34;&gt;2022&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;3x3 Design&lt;/li&gt;
&lt;li&gt;Alfred P. Sloan Foundation&lt;/li&gt;
&lt;li&gt;Arebyte Gallery&lt;/li&gt;
&lt;li&gt;Aspiration Technology&lt;/li&gt;
&lt;li&gt;Atlantic Council of the United States&lt;/li&gt;
&lt;li&gt;Calyx Institute&lt;/li&gt;
&lt;li&gt;Chan Zuckerberg Initiative&lt;/li&gt;
&lt;li&gt;Code for Science and Society&lt;/li&gt;
&lt;li&gt;Common Knowledge&lt;/li&gt;
&lt;li&gt;Consumer Reports&lt;/li&gt;
&lt;li&gt;Interaction Design Association&lt;/li&gt;
&lt;li&gt;Internews Network&lt;/li&gt;
&lt;li&gt;LAFT&lt;/li&gt;
&lt;li&gt;Least Authority GmbH&lt;/li&gt;
&lt;li&gt;Luminate Projects / Reset Tech&lt;/li&gt;
&lt;li&gt;Marigold Strategies&lt;/li&gt;
&lt;li&gt;National Endowment for Democracy&lt;/li&gt;
&lt;li&gt;Newkinco&lt;/li&gt;
&lt;li&gt;Northumbria University&lt;/li&gt;
&lt;li&gt;Okthanks&lt;/li&gt;
&lt;li&gt;Open Collective Foundation&lt;/li&gt;
&lt;li&gt;Open Technology Fund&lt;/li&gt;
&lt;li&gt;Radio Free Europe / Radio Liberty&lt;/li&gt;
&lt;li&gt;Reset Tech&lt;/li&gt;
&lt;li&gt;Software Acumen Limited&lt;/li&gt;
&lt;li&gt;TechCongress&lt;/li&gt;
&lt;li&gt;The Future Laboratory&lt;/li&gt;
&lt;li&gt;Tides Foundation&lt;/li&gt;
&lt;li&gt;University of Berkeley&lt;/li&gt;
&lt;li&gt;University of Omaha&lt;/li&gt;
&lt;li&gt;University of Vermont&lt;/li&gt;
&lt;li&gt;Webrecorder Software&lt;/li&gt;
&lt;li&gt;World Wide Web Foundation&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2021&#34;&gt;2021&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Alfred P. Sloan Foundation&lt;/li&gt;
&lt;li&gt;Amnesty International&lt;/li&gt;
&lt;li&gt;Aspiration Technology&lt;/li&gt;
&lt;li&gt;Code for Science and Society&lt;/li&gt;
&lt;li&gt;Coil Technology&lt;/li&gt;
&lt;li&gt;Common Knowledge&lt;/li&gt;
&lt;li&gt;Consumer Reports&lt;/li&gt;
&lt;li&gt;Furtherfield&lt;/li&gt;
&lt;li&gt;Interaction Design&lt;/li&gt;
&lt;li&gt;International Women’s Media Foundation&lt;/li&gt;
&lt;li&gt;Internews Network&lt;/li&gt;
&lt;li&gt;LEAP&lt;/li&gt;
&lt;li&gt;Least Authority&lt;/li&gt;
&lt;li&gt;Luminate Projects / Reset Tech&lt;/li&gt;
&lt;li&gt;Mozilla Corporation&lt;/li&gt;
&lt;li&gt;Mozilla Foundation&lt;/li&gt;
&lt;li&gt;National Endowment for Democracy&lt;/li&gt;
&lt;li&gt;New Venture Fund&lt;/li&gt;
&lt;li&gt;Omidyar Network India Advisors Private Ltd&lt;/li&gt;
&lt;li&gt;Open Source Collective: Digital Infrastructure Fund&lt;/li&gt;
&lt;li&gt;Open Source Collective: Samsung NEXT&lt;/li&gt;
&lt;li&gt;Open Tech Fund&lt;/li&gt;
&lt;li&gt;PEN America&lt;/li&gt;
&lt;li&gt;Prototype Fund&lt;/li&gt;
&lt;li&gt;Python Software Foundation&lt;/li&gt;
&lt;li&gt;Public Office&lt;/li&gt;
&lt;li&gt;Radicle Foundation&lt;/li&gt;
&lt;li&gt;Reset Tech&lt;/li&gt;
&lt;li&gt;TechCongress&lt;/li&gt;
&lt;li&gt;The Future Laboratory&lt;/li&gt;
&lt;li&gt;Tides Foundation&lt;/li&gt;
&lt;li&gt;University of Dundee&lt;/li&gt;
&lt;li&gt;University of Omaha&lt;/li&gt;
&lt;li&gt;Webrecorder Software Foundation&lt;/li&gt;
&lt;li&gt;Wicked Co-op&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2020&#34;&gt;2020&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Amnesty International&lt;/li&gt;
&lt;li&gt;Aspiration Technology / Reset Tech&lt;/li&gt;
&lt;li&gt;CoBox Cloud Cooperative&lt;/li&gt;
&lt;li&gt;Code for Science and Society&lt;/li&gt;
&lt;li&gt;Coil Technology&lt;/li&gt;
&lt;li&gt;Furtherfield&lt;/li&gt;
&lt;li&gt;Interaction Design Association&lt;/li&gt;
&lt;li&gt;Internews Network&lt;/li&gt;
&lt;li&gt;Luminate Projects / Reset Tech&lt;/li&gt;
&lt;li&gt;Mozilla Corporation&lt;/li&gt;
&lt;li&gt;National Endowment for Democracy&lt;/li&gt;
&lt;li&gt;New American Foundation&lt;/li&gt;
&lt;li&gt;Northumbria University&lt;/li&gt;
&lt;li&gt;Open Tech Fund&lt;/li&gt;
&lt;li&gt;Prototype Fund&lt;/li&gt;
&lt;li&gt;Python Software Foundation&lt;/li&gt;
&lt;li&gt;Samsung Next&lt;/li&gt;
&lt;li&gt;University of Amsterdam&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2019&#34;&gt;2019&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Adobe&lt;/li&gt;
&lt;li&gt;Amatus GMBH&lt;/li&gt;
&lt;li&gt;Betterplace Lab&lt;/li&gt;
&lt;li&gt;Center for Tech Cultivation&lt;/li&gt;
&lt;li&gt;Code for Science &amp;amp; Society&lt;/li&gt;
&lt;li&gt;Front Conference&lt;/li&gt;
&lt;li&gt;HRX Veranstaltungen GmbH&lt;/li&gt;
&lt;li&gt;Medieninnovationszentrum Babelsberg&lt;/li&gt;
&lt;li&gt;Mozilla&lt;/li&gt;
&lt;li&gt;OCCRP&lt;/li&gt;
&lt;li&gt;Omidyar Network&lt;/li&gt;
&lt;li&gt;Open Tech Fund&lt;/li&gt;
&lt;li&gt;Prototype Fund&lt;/li&gt;
&lt;li&gt;Ruhr University&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2018&#34;&gt;2018&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Adobe&lt;/li&gt;
&lt;li&gt;A-F Digital Solutions&lt;/li&gt;
&lt;li&gt;Betterplace Lab&lt;/li&gt;
&lt;li&gt;Biz to Buttons&lt;/li&gt;
&lt;li&gt;Cerner Corporation&lt;/li&gt;
&lt;li&gt;Clearleft&lt;/li&gt;
&lt;li&gt;Ford Foundation&lt;/li&gt;
&lt;li&gt;Internet Society&lt;/li&gt;
&lt;li&gt;Internews&lt;/li&gt;
&lt;li&gt;Invoice2Go&lt;/li&gt;
&lt;li&gt;Omidyar Network&lt;/li&gt;
&lt;li&gt;Open Technology Fund&lt;/li&gt;
&lt;li&gt;Prototype Fund&lt;/li&gt;
&lt;li&gt;SamsungNext&lt;/li&gt;
&lt;li&gt;HERE Deutschland&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2017&#34;&gt;2017&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Ford Foundation&lt;/li&gt;
&lt;li&gt;Least Authority&lt;/li&gt;
&lt;li&gt;Mozilla&lt;/li&gt;
&lt;li&gt;OTF&lt;/li&gt;
&lt;li&gt;Peerio&lt;/li&gt;
&lt;li&gt;Prototype Fund&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2016&#34;&gt;2016&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;CFR&lt;/li&gt;
&lt;li&gt;DeepMind Tech&lt;/li&gt;
&lt;li&gt;Google&lt;/li&gt;
&lt;li&gt;OTF&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2015&#34;&gt;2015&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Dropbox&lt;/li&gt;
&lt;li&gt;Google&lt;/li&gt;
&lt;/ul&gt;

    &lt;/div&gt;

&lt;/div&gt;

</description>
    </item>
    
    <item>
      <title>MozFest 2026: Maybe the Wildest Thing Tech Can Do Is Nurture What&#39;s Already Growing</title>
      <link>https://superbloom.design/learning/blog/mozfest-2026-maybe-the-wildest-thing-tech-can-do-is-nurture-whats-already-growing/</link>
      <pubDate>Mon, 16 Nov 2026 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/mozfest-2026-maybe-the-wildest-thing-tech-can-do-is-nurture-whats-already-growing/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/55645294461_e84c947f8b_c_hu_b712ac388e140f52.jpg&#34; width=&#34;740&#34; height=&#34;494&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Conferences and festivals love a theme. It gives us something to rally around and a common thread connecting our conversations and experiences. This year&amp;rsquo;s &lt;a href=&#34;https://www.mozillafoundation.org/en/festival/&#34;&gt;MozFest&lt;/a&gt; theme was &amp;ldquo;Wilding&amp;rdquo;, a word that hints at the sins of extractivist technologies while leaving plenty of room for interpretation.&lt;/p&gt;
&lt;p&gt;As Superbloom Design&amp;rsquo;s in-house participation strategist and Program Manager for Coaching &amp;amp; Community, I found myself thinking about what Wilding might mean for my work supporting people building public-interest technology.&lt;/p&gt;
&lt;h2 id=&#34;making-room&#34;&gt;Making room&lt;/h2&gt;
&lt;p&gt;MozFest is busy. Events, pre-events, post-events, side events, hangouts, and meetings fill your schedule, with no shortage of things to do or people to meet.&lt;/p&gt;
&lt;p&gt;As a mother of a young child, I don&amp;rsquo;t often travel alone for work, so I wanted to make the most of this trip. I decided to go beyond the official program and make room for unexpected conversations and encounters. As it often turns out, those moments were some of the most valuable.&lt;/p&gt;
&lt;p&gt;One came at a side event hosted by the &lt;a href=&#34;https://civictech.guide/&#34;&gt;Civic Tech Field Guide&lt;/a&gt;, a longstanding archive of civic and public-interest technology. The room brought together people who remembered a time when &amp;ldquo;new technologies&amp;rdquo; were widely seen as tools for liberation and democratic change.&lt;/p&gt;
&lt;p&gt;Daniel Mackisack, who now leads the initiative, recalled being in Cairo during the so-called Arab Spring. People didn&amp;rsquo;t need social media to know others opposed the regime, he observed. They could simply look out of their windows and see it for themselves.&lt;/p&gt;
&lt;p&gt;Yet the Arab Spring became a funding myth about technology&amp;rsquo;s power to bring about democracy. We gave technology disproportionate credit for political change that was ultimately driven by people. And perhaps that is something we&amp;rsquo;re still too quick to forget in pursuit of the next spectacular solution.&lt;/p&gt;
&lt;h2 id=&#34;product-community-fit&#34;&gt;Product-community fit&lt;/h2&gt;
&lt;p&gt;Another highlight was the &lt;a href=&#34;https://www.youtube.com/watch?v=ClWpc04fb74&#34;&gt;Mozilla Foundation Incubator Showcase&lt;/a&gt;, where four of the 10 grantees Superbloom supports through its coaching program presented their projects.&lt;/p&gt;
&lt;p&gt;Opening the showcase, Mozilla Foundation CEO Nabiha Syed, in conversation with Anil Dash of &lt;a href=&#34;https://anti.tech/&#34;&gt;AntiTech&lt;/a&gt;, spoke about the human side of technology and what she called &amp;ldquo;product-community fit&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;She reflected on how people are beginning to understand what&amp;rsquo;s at stake and ask more fundamental questions: Is this technology worthy of our time and attention? And how do we make sure we&amp;rsquo;re building technology that actually serves us?&lt;/p&gt;
&lt;p&gt;Doubt is growing, and understandably so. But doubt alone doesn&amp;rsquo;t tell us what to build instead.&lt;/p&gt;
&lt;p&gt;Product-community fit goes beyond understanding a product&amp;rsquo;s users. Communities are made up of relationships: between people, institutions, the infrastructure and funding they depend on, and the land, energy and resources that technology draws on. A product needs to make sense within those relationships, too.&lt;/p&gt;
&lt;p&gt;That means paying attention to the people already trying to bring about change: activists, organizers and others working towards more just and sustainable futures. And it means understanding what they need to succeed, rather than assuming we already know.&lt;/p&gt;
&lt;p&gt;This is where Superbloom&amp;rsquo;s work comes in.&lt;/p&gt;
&lt;p&gt;Our coaching program connects public-interest technology teams with &lt;a href=&#34;https://superbloom.design/about/people/#coaches&#34;&gt;experienced practitioners&lt;/a&gt; who help them navigate challenges that funding alone can&amp;rsquo;t solve.&lt;/p&gt;
&lt;p&gt;A good idea, a working product and sufficient funding all matter. But none guarantees that something will be useful to people.&lt;/p&gt;
&lt;p&gt;Collectives, a project supported by Germany&amp;rsquo;s &lt;a href=&#34;https://www.prototypefund.de/en&#34;&gt;Prototype Fund&lt;/a&gt;, offers a good example of this.&lt;/p&gt;
&lt;p&gt;The project began as a dashboard for left spaces using Nextcloud to organize. Early in its first funding round, the team was introduced to Nextcloud&amp;rsquo;s core team. It turned out both were planning a dashboard.&lt;/p&gt;
&lt;p&gt;Rather than duplicate the work, the Collectives team changed direction. Nextcloud continued developing its dashboard, while Collectives focused on a wiki tool that became the Nextcloud Collectives app.&lt;/p&gt;
&lt;p&gt;Maybe that&amp;rsquo;s what product-community fit means: understanding where a project belongs, who it serves and when to change direction. Through conversations with others working on similar problems, the Collectives team found a place for its work within something bigger, reaching users beyond those originally imagined.&lt;/p&gt;
&lt;p&gt;Sometimes the most useful thing you can do is bring the right people together.&lt;/p&gt;
&lt;h2 id=&#34;what-learning-takes&#34;&gt;What learning takes&lt;/h2&gt;
&lt;p&gt;But our coaching program does something else, too. It connects people with experience to share with those who could use it, giving them space to ask questions, exchange ideas, and work through problems together.&lt;/p&gt;
&lt;p&gt;At lunch during MozFest, I had a conversation about the difference between handing someone a list of resource links and actually helping them learn.&lt;/p&gt;
&lt;p&gt;Learning is embodied, relational and contextual. It doesn&amp;rsquo;t happen simply by giving people access to resources, recordings, toolkits or standardized training programs.&lt;/p&gt;
&lt;p&gt;It also takes reflection. When you&amp;rsquo;re busy delivering a project, it&amp;rsquo;s easy to keep moving without questioning whether you&amp;rsquo;re still heading in the right direction. In the &lt;a href=&#34;https://publications.jrc.ec.europa.eu/repository/handle/JRC123629&#34;&gt;Cynefin framework&lt;/a&gt;, sensing is part of responding to complexity: paying attention to what&amp;rsquo;s happening, learning from it and adjusting as you go.&lt;/p&gt;
&lt;p&gt;And sometimes learning means realizing that the direction you originally chose isn&amp;rsquo;t the right one. That&amp;rsquo;s not necessarily a failure, as it can mean you&amp;rsquo;ve learned enough to make a better decision.&lt;/p&gt;
&lt;p&gt;Which brings me back to Wilding.&lt;/p&gt;
&lt;p&gt;In ecology, rewilding means restoring the conditions that let ecosystems recover and thrive, rather than trying to control every outcome. I think there&amp;rsquo;s something useful in that idea for our field. It also fits our name. A superbloom happens when the right conditions come together and an entire landscape bursts into flower.&lt;/p&gt;
&lt;p&gt;Maybe our work isn&amp;rsquo;t always about coming up with something new. Sometimes it&amp;rsquo;s about making room for what we can&amp;rsquo;t fully plan: relationships, curiosity, collective learning and unexpected possibilities.&lt;/p&gt;
&lt;p&gt;A colleague recently told me it&amp;rsquo;s worth revisiting old conversations if the questions are still relevant. Not every idea needs to be new to be useful.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s what I&amp;rsquo;m taking away from MozFest.&lt;/p&gt;
&lt;p&gt;We spend a lot of time talking about what technology can do, and less time thinking about the people who build it, use it, question it and help others make sense of it.&lt;/p&gt;
&lt;p&gt;Creating the conditions for those people to succeed shouldn&amp;rsquo;t be a radical idea. But when technology moves faster than our ability to understand its consequences, perhaps it&amp;rsquo;s more important than ever.&lt;/p&gt;
&lt;p&gt;Maybe nurturing teams to reframe or improve existing solutions is the wildest thing we can do.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;Superbloom provides coaching support to grantees of the Prototype Fund, Mozilla Foundation Incubator, and Interledger Foundation. If you are interested in learning more about this, please email Alicja at &lt;a href=&#34;mailto:alicja@superbloom.design&#34;&gt;alicja@superbloom.design&lt;/a&gt;&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Call for Expressions of Interest: AI Community Feedback Partners</title>
      <link>https://superbloom.design/learning/blog/call-for-expressions-of-interest-ai-community-feedback-partners/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/call-for-expressions-of-interest-ai-community-feedback-partners/</guid>
      <description>&lt;p&gt;&lt;em&gt;New York State | Applications open October 1 - October 19, 2026&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;summary&#34;&gt;&lt;strong&gt;Summary&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;We’re inviting NYC- and NYS-based community organizations to partner with &lt;a href=&#34;https://superbloom.design&#34;&gt;Superbloom Design&lt;/a&gt; and &lt;a href=&#34;https://helpfulplaces.com&#34;&gt;Helpful Places&lt;/a&gt; on a &lt;strong&gt;bilingual (English/Spanish) community-led workshop series&lt;/strong&gt; exploring how AI shows up in civic life and what transparency and accountability should look like in practice.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re looking to collaborate with at least 3 organizations in NYC and 1 organization in Upstate New York to run the bilingual workshops/co-design sessions from &lt;strong&gt;October 2026 to March 2027&lt;/strong&gt;. The workshops will serve as a space for participants to share lived experiences and priorities, increasing their confidence and agency, while directly contributing to a policy framework. Partner organizations and workshop participants will help co-create a Civic Feedback Framework for AI Transparency that informs the next version of open standards for AI governance.&lt;/p&gt;
&lt;p&gt;Each partner organization will &lt;strong&gt;organize and host 2 sessions, recruit participants, and provide bilingual co-facilitation,&lt;/strong&gt; to ensure the work is accessible, community-led, and grounded in trust and local relationships.&lt;/p&gt;
&lt;p&gt;This project is supported by the &lt;strong&gt;LUCHA Equity Fund&lt;/strong&gt;, an initiative from New York State that is powered by Hispanic Federation.&lt;/p&gt;
&lt;h3 id=&#34;who-were-looking-for&#34;&gt;Who we’re looking for&lt;/h3&gt;
&lt;p&gt;Community-based organizations, groups, or cooperatives located in New York State that:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;have deep relationships with Latino communities impacted by civic systems and public service providers&lt;/li&gt;
&lt;li&gt;can recruit participants and host bilingual (Spanish/English) sessions&lt;/li&gt;
&lt;li&gt;want to explore power, rights, and lived experience in relation to AI/automation/emerging technologies&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;key-requirements-for-this-engagement&#34;&gt;Key requirements for this engagement&lt;/h3&gt;
&lt;p&gt;We are looking for partners who can commit to the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Identify and provide a bilingual co-facilitator to work directly with our team&lt;/li&gt;
&lt;li&gt;Host 2 community workshops or co-design sessions&lt;/li&gt;
&lt;li&gt;Recruit at least 20+ participants for each session&lt;/li&gt;
&lt;li&gt;Support accessibility/translation needs&lt;/li&gt;
&lt;li&gt;Share structured feedback on curriculum design and the Civic Feedback Framework for AI Transparency&lt;/li&gt;
&lt;li&gt;Can contract with Superbloom for deliverables-based service&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;what-is-provided&#34;&gt;What is provided&lt;/h3&gt;
&lt;p&gt;Superbloom will provide the following support to each selected partner:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;$25,000 stipend (for staff time, materials development, bilingual support, co-facilitation of 2 sessions, and participant outreach)&lt;/li&gt;
&lt;li&gt;Facilitation toolkit + co-design support&lt;/li&gt;
&lt;li&gt;Scheduling and comms support&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;timeline&#34;&gt;Timeline&lt;/h3&gt;
&lt;h4 id=&#34;2026&#34;&gt;2026&lt;/h4&gt;
&lt;p&gt;&lt;strong&gt;Oct 10&lt;/strong&gt;&lt;br&gt;
&lt;br&gt;
Expression of Interest Form opens. Submissions will be reviewed and partners selected on a rolling basis until October 19, 2026.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Oct 19&lt;/strong&gt;&lt;br&gt;
&lt;br&gt;
Expression of Interest form closes.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;During Oct&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Superbloom team evaluates submissions for interest, eligibility, and fit. Superbloom will contact selected submissions for an introductory conversation and next steps.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Oct - Dec 2026&lt;/strong&gt;&lt;br&gt;
&lt;br&gt;
Superbloom issues contracts to selected partners. Partners onboard to project and host the first round of workshops.&lt;/p&gt;
&lt;h4 id=&#34;2027&#34;&gt;2027&lt;/h4&gt;
&lt;p&gt;&lt;br&gt;
&lt;strong&gt;Jan &amp;amp; Feb&lt;/strong&gt;
&lt;br&gt;
&lt;br&gt;
Selected partners host a second round of workshops.
&lt;br&gt;
&lt;br&gt;
&lt;strong&gt;During Feb&lt;/strong&gt;
&lt;br&gt;
&lt;br&gt;
Partners provide feedback on the Civic Feedback Framework for AI Transparency.
&lt;br&gt;
&lt;br&gt;
&lt;strong&gt;Mar 15&lt;/strong&gt;&lt;br&gt;
&lt;br&gt;
Civic Feedback Framework for AI Transparency is published. Project ends.&lt;/p&gt;
&lt;h3 id=&#34;about-us&#34;&gt;About us&lt;/h3&gt;
&lt;p&gt;Changing who technology serves. Superbloom Design is a US 501(c)3 nonprofit organization, founded in 2014 at the intersection of digital design and human rights. We leverage design as a transformative practice to shift power in the tech ecosystem. We apply a critical lens to technology development, and view design as an intervention opportunity to center people and their needs. &lt;br&gt;
&lt;br&gt;
We collaborate closely with others in the space to grow the community focused on shaping our collective online future. Our vision is a world where everyone has the knowledge, network, and digital tools needed to enrich their lives. In addition to our core work, we have a growing fiscal sponsorship program. Learn more about our work at &lt;a href=&#34;https://superbloom.design/work/&#34;&gt;superbloom.design/work/&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;how-to-apply&#34;&gt;How to apply&lt;/h3&gt;
&lt;p&gt;Fill out the Expression of Interest form at the following link: &lt;a href=&#34;https://forms.superbloom.design/s/cmuleocg400f101nutu2f4cym&#34;&gt;https://forms.superbloom.design/s/cmuleocg400f101nutu2f4cym&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Deadline: October 19, 2026, 6pm ET&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The form should take about 10-15 minutes to complete. Submissions will be considered on a rolling basis, and we reserve the right to close this process early due to high submission volume. Superbloom will only contact organizations/groups that we’d like to move forward in the selection process.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Convocatoria de expresiones de interés: Organizaciones asociadas para la retroalimentación comunitaria sobre la IA</title>
      <link>https://superbloom.design/learning/blog/convocatoria-de-expresiones-de-inter%C3%A9s-organizaciones-asociadas-para-la-retroalimentaci%C3%B3n-comunitaria-sobre-la-ia/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/convocatoria-de-expresiones-de-inter%C3%A9s-organizaciones-asociadas-para-la-retroalimentaci%C3%B3n-comunitaria-sobre-la-ia/</guid>
      <description>&lt;p&gt;&lt;em&gt;Estado de Nueva York | Solicitudes abiertas del 1 de Octubre al 19 de Octubre de 2026&lt;/em&gt;&lt;/p&gt;
&lt;h1 id=&#34;introducción&#34;&gt;Introducción&lt;/h1&gt;
&lt;p&gt;Invitamos a organizaciones comunitarias de la ciudad y del estado de Nueva York a colaborar con &lt;a href=&#34;http://superbloom.design/&#34;&gt;Superbloom Design&lt;/a&gt; y &lt;a href=&#34;https://www.helpfulplaces.com/&#34;&gt;Helpful Places&lt;/a&gt; en una serie de talleres bilingües (inglés/español) dirigidos por la comunidad que explorarán cómo aparece la IA en la vida cívica y cómo deberían ser, en la práctica, la transparencia y la rendición de cuentas.&lt;/p&gt;
&lt;p&gt;Buscamos colaborar con al menos 3 organizaciones de la ciudad de Nueva York y 1 organización del norte del estado de Nueva York para realizar los talleres y sesiones de co-diseño bilingües de octubre de 2026 a marzo de 2027. Los talleres serán un espacio para que las personas participantes compartan sus experiencias vividas y sus prioridades, fortaleciendo su confianza y su capacidad de acción, a la vez que contribuyen directamente a un marco regulatorio. Las organizaciones aliadas y las personas participantes ayudarán a co-crear un Marco Cívico de Retroalimentación para la Transparencia de la IA, que servirá de base para la próxima versión de los estándares abiertos de gobernanza de la IA.&lt;/p&gt;
&lt;p&gt;Cada organización aliada organizará y será sede de 2 sesiones, reclutará participantes y ofrecerá co-facilitación bilingüe, para garantizar que el trabajo sea accesible, dirigido por la comunidad y basado en la confianza y en las relaciones locales.&lt;/p&gt;
&lt;p&gt;Este proyecto cuenta con el apoyo del LUCHA Equity Fund, una iniciativa del estado de Nueva York impulsada por Hispanic Federation.&lt;/p&gt;
&lt;h1 id=&#34;a-quiénes-buscamos&#34;&gt;¿A quiénes buscamos?&lt;/h1&gt;
&lt;p&gt;Organizaciones comunitarias, grupos o cooperativas ubicadas en el estado de Nueva York que:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Tengan relaciones sólidas con comunidades latinas afectadas por los sistemas cívicos y los proveedores de servicios públicos&lt;/li&gt;
&lt;li&gt;Puedan reclutar participantes y organizar sesiones bilingües (español/inglés)&lt;/li&gt;
&lt;li&gt;Quieran explorar el poder, los derechos y las experiencias vividas en relación con la IA, la automatización y las tecnologías emergentes&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id=&#34;requisitos-fundamentales-para-este-proyecto&#34;&gt;Requisitos fundamentales para este proyecto&lt;/h1&gt;
&lt;p&gt;Buscamos organizaciones aliadas que puedan comprometerse a lo siguiente:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Identificar y proporcionar una persona co-facilitadora bilingüe que trabaje directamente con nuestro equipo&lt;/li&gt;
&lt;li&gt;Organizar 2 talleres comunitarios o sesiones de co-diseño&lt;/li&gt;
&lt;li&gt;Reclutar al menos 20 participantes para cada sesión &lt;/li&gt;
&lt;li&gt;Apoyar las necesidades de accesibilidad y traducción&lt;/li&gt;
&lt;li&gt;Compartir retroalimentación estructurada sobre el diseño del currículo y el Marco Cívico de Retroalimentación para la Transparencia de la IA&lt;/li&gt;
&lt;li&gt;Contratar con Superbloom por servicios basados en entregables&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id=&#34;qué-ofrecemos&#34;&gt;¿Qué ofrecemos?&lt;/h1&gt;
&lt;p&gt;Superbloom proveerá lo siguiente  a cada organización seleccionada:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;$25,000 (para tiempo del personal, desarrollo de materiales, apoyo bilingüe, co-facilitación de 2 sesiones y alcance comunitario para reclutar participantes)&lt;/li&gt;
&lt;li&gt;Kit de herramientas de facilitación y apoyo en co-diseño&lt;/li&gt;
&lt;li&gt;Apoyo con la programación de fechas y las comunicaciones&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id=&#34;calendario&#34;&gt;Calendario&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;2026&lt;/strong&gt;&lt;br&gt;
&lt;br&gt;
&lt;strong&gt;Oct 10&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Se abre el formulario de expresión de interés. Las solicitudes se revisarán y las organizaciones aliadas se seleccionarán de forma continua hasta el 19 de Octubre de 2026 (si le interesa, le recomendamos enviar su solicitud pronto).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Oct 19&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Se cierra el formulario de expresión de interés.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Durante Oct&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;El equipo de Superbloom evaluará las solicitudes según el interés, la elegibilidad y la afinidad con el proyecto. Superbloom se comunicará con las organizaciones seleccionadas para una conversación introductoria y los próximos pasos.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Oct - Dec 2026&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Superbloom emite los contratos a las organizaciones seleccionadas. Las organizaciones seleccionadas se integran al proyecto y realizan la primera ronda de talleres.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2027&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Jan &amp;amp; Feb&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Las organizaciones seleccionadas realizan una segunda ronda de talleres.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Durante Feb&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Las organizaciones seleccionadas comparten su retroalimentación sobre el Marco Cívico de Retroalimentación para la Transparencia de la IA.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Mar 15&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Se publica el Marco Cívico de Retroalimentación para la Transparencia de la IA.
Concluye el proyecto.&lt;/p&gt;
&lt;h1 id=&#34;quiénes-somos&#34;&gt;Quiénes somos&lt;/h1&gt;
&lt;p&gt;Cambiar a quién sirve la tecnología. Superbloom Design es una organización sin fines de lucro 501(c)(3) de EE. UU., fundada en 2014 en la intersección entre el diseño digital y los derechos humanos.&lt;/p&gt;
&lt;p&gt;Usamos el diseño como una práctica transformadora para redistribuir el poder en el ecosistema tecnológico. Aplicamos una perspectiva crítica al desarrollo de la tecnología y tratamos el diseño como una oportunidad de intervención para poner en el centro a las personas y sus necesidades. Colaboramos con otras personas y organizaciones aliadas para hacer crecer la comunidad dedicada a darle forma a nuestro futuro digital colectivo. Nuestra visión es un mundo en el que todas las personas tengan los conocimientos, las redes y las herramientas digitales necesarias para enriquecer sus vidas. Además de nuestro trabajo principal, contamos con un programa de patrocinio fiscal en crecimiento.&lt;/p&gt;
&lt;p&gt;Conozca más sobre nuestro trabajo en &lt;a href=&#34;https://superbloom.design/work/&#34;&gt;superbloom.design/work/&lt;/a&gt;&lt;/p&gt;
&lt;h1 id=&#34;cómo-solicitar&#34;&gt;Cómo solicitar&lt;/h1&gt;
&lt;p&gt;Complete el formulario de expresión de interés en el siguiente enlace: &lt;a href=&#34;https://forms.superbloom.design/s/cmuleocg400f101nutu2f4cym&#34;&gt;https://forms.superbloom.design/s/cmuleocg400f101nutu2f4cym&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;Deadline: 19 de Octubre de 2026, 6pm ET&lt;/p&gt;
&lt;p&gt;Completar el formulario debería tomar entre 10-15 minutos.&lt;/p&gt;
&lt;p&gt;Las propuestas se evaluarán de forma continua, y nos reservamos el derecho de cerrar el proceso antes de lo previsto debido al elevado volumen de solicitudes. Superbloom solo se comunicará con las organizaciones o grupos que deseemos avanzar a la siguiente etapa del proceso de selección.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Design Researcher</title>
      <link>https://superbloom.design/community/opportunities/f2026-design-researcher/</link>
      <pubDate>Fri, 25 Sep 2026 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/opportunities/f2026-design-researcher/</guid>
      <description>&lt;h4 id=&#34;the-project&#34;&gt;&lt;strong&gt;The project&lt;/strong&gt;&lt;/h4&gt;
&lt;p&gt;Superbloom is working on a grant-funded project to deliver a bilingual (English/Spanish) community co-design project. Our goal is to help New Yorkers better understand and respond to AI use in civic life. This role will lead the workshop design and curriculum/facilitation materials in partnership with our multi-organizational team and 4-5 community-based organizations. Overall the goal is to run 8+ multilingual workshops/co-design sessions reaching approximately 150 participants between October 2026 and March 2027 to co-design a Civic Feedback Framework for AI Transparency. The Framework will offer practical methods communities and organizations can use to gather input and translate it into clear recommendations about AI transparency.&lt;/p&gt;
&lt;h4 id=&#34;the-role&#34;&gt;&lt;strong&gt;The role&lt;/strong&gt;&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;You’ll lead workshop design and curriculum development. You are responsible for survey design, partnership onboarding and engagement, and data collection.&lt;/li&gt;
&lt;li&gt;You’ll work closely with the team, project partners, and the community partner organizations, to deliver 8+ community workshops and reach 150+ participants.&lt;/li&gt;
&lt;li&gt;You’ll synthesize learnings from the workshops and develop grant outputs, including a Civic Feedback Framework for AI Transparency, to make the insights understandable and actionable by the project team.&lt;/li&gt;
&lt;li&gt;You’ll support the development of communications assets and content (such as blog posts, learning resources, etc) needed for curriculum development and grant reporting.&lt;/li&gt;
&lt;li&gt;This is a 30+ hours/week, benefits eligible, grant-funded position with a base annual salary range of $60,000-$80,000 (pro-rated for the duration of the engagement). The position will start as soon as the position is filled and will run through March 2027.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;about-us&#34;&gt;&lt;strong&gt;About us&lt;/strong&gt;&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Changing who technology serves.&lt;/em&gt; We are a US 501(c)3 nonprofit organization, founded in 2014 at the intersection of digital design and human rights. We leverage design as a transformative practice to shift power in the tech ecosystem. We apply a critical lens to technology development, and view design as an intervention opportunity to center people and their needs. We collaborate closely with others in the space to grow the community focused on shaping our collective online future. Our vision is a world where everyone has the knowledge, network, and digital tools needed to enrich their lives. In addition to our core work, we have a growing fiscal sponsorship program. We work internationally, with team members spanning from the US-West Coast to Central Europe.
Learn more about our &lt;a href=&#34;https://superbloom.design/work/&#34;&gt;work&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;about-you&#34;&gt;About you&lt;/h3&gt;
&lt;h4 id=&#34;requirements&#34;&gt;Requirements&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;You have demonstrable experience working on community-based and/or civic engagement projects.&lt;/li&gt;
&lt;li&gt;You have demonstrable experience designing and facilitating workshops, focus groups, seminars and/or other types of community events.&lt;/li&gt;
&lt;li&gt;You have experience with curriculum development and creating learning content for a broad audience.&lt;/li&gt;
&lt;li&gt;You have working proficiency in Spanish and English. You are confident in everyday conversation and are able to conduct outreach and workshops in both Spanish and English.&lt;/li&gt;
&lt;li&gt;You are based in New York (City or State) and are available for a 30+ hours/week position during US-Eastern work hours. We expect this position will mainly be remote, with in-person attendance required for scheduled meetings and workshops.&lt;/li&gt;
&lt;li&gt;You have experience with human-centered, participatory, or interview-based research (specifically field research).&lt;/li&gt;
&lt;li&gt;You are able to write clear, concise, and engaging research synthesis to be read by a broad non-technical audience.&lt;/li&gt;
&lt;li&gt;You work well independently and in collaboration with a fully remote, distributed team.&lt;/li&gt;
&lt;li&gt;You have excellent project team communication and meeting facilitation skills.&lt;/li&gt;
&lt;li&gt;You are comfortable advocating for yourself and your work to make sure that you’re getting what you need to be successful.&lt;/li&gt;
&lt;li&gt;This position is hybrid, working from home and in public community spaces. You may be required to walk, bend, kneel, and stand, and will require sitting for extended periods of time.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;nice-to-have&#34;&gt;Nice to have&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Proficiency with graphic/visual design tools (e.g. Adobe Suite, Canva, Figma, etc).&lt;/li&gt;
&lt;li&gt;Familiarity with New York Latino communities and Latino nonprofit organizations.&lt;/li&gt;
&lt;li&gt;Knowledgeable about one or more of the following areas: open source software, civic technology, urban and smart city technologies, internet freedom, tech criticism and activism, human rights.&lt;/li&gt;
&lt;li&gt;Comfortable with collaborative work tools (we currently use Notion, Slack, Miro, and Google Suite).&lt;/li&gt;
&lt;li&gt;Comfortable with exploring and evaluating new tools.&lt;/li&gt;
&lt;li&gt;Comfortable in cross-cultural communication, e.g. experience with international work or remote work culture.&lt;/li&gt;
&lt;li&gt;Aware of best practices around informed research consent, safeguarding confidential research information, and anonymizing participant data.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;additional-information&#34;&gt;Additional Information&lt;/h3&gt;
&lt;p&gt;We’re committed to providing a fair and accessible application process. If you need any adjustments or alternative formats, please email us at &lt;a href=&#34;mailto:jobs@superbloom.design&#34;&gt;jobs@superbloom.design&lt;/a&gt;. As a human-centered design organization, we promise that a member of our team will be reviewing your application. In return, we ask that applications center your authentic work and ideas.&lt;/p&gt;
&lt;p&gt;Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa at this time.&lt;/p&gt;
&lt;p&gt;You are based in New York (City or State) and are available for a 30+ hours/week position during US-Eastern work hours. We expect this position will mainly be remote, with in-person attendance required for scheduled meetings and workshops.&lt;/p&gt;
&lt;h3 id=&#34;how-to-apply&#34;&gt;How to Apply&lt;/h3&gt;
&lt;p&gt;If you think you’d like to be a part of our team, please complete the application form in its entirety. Applications will be considered on a rolling basis, and we reserve the right to close this process early due to high applicant volume.&lt;/p&gt;
&lt;p&gt;After an initial application review, SBD’s hiring process will most likely involve one to two rounds of interviews and we are aiming to hire as soon as possible.&lt;/p&gt;
&lt;button class=&#34;button clickable&#34; aria-label=&#34;Donate&#34;&gt;&lt;a class=&#34;&#34;
    href=&#34;https://superbloom.design/design-researcher-fall2026&#34; &gt;Apply&lt;/a&gt;
&lt;/button&gt;
</description>
    </item>
    
    <item>
      <title>What If Trust Was Infrastructure? A New Design Frontier for Social Media</title>
      <link>https://superbloom.design/learning/blog/what-if-trust-was-infrastructure-a-new-design-frontier-for-social-media/</link>
      <pubDate>Thu, 04 Jun 2026 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/what-if-trust-was-infrastructure-a-new-design-frontier-for-social-media/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/cosmin-andrei-buzamat-b1fmtyfpk4q-unsplash_hu_49e108cf16fdc1f9.jpg&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;entering-the-atmosphere&#34;&gt;Entering the Atmosphere&lt;/h2&gt;
&lt;p&gt;I went to &lt;a href=&#34;https://atmosphereconf.org/&#34;&gt;ATmosphereConf 2026&lt;/a&gt; in Vancouver, not really knowing what to expect. I assumed ATProto and “the Atmosphere” were just Bluesky, but decentralized — I was very wrong.&lt;/p&gt;
&lt;p&gt;I came away with a list of design problems I hadn’t thought to ask before, and others I hadn’t imagined could be solved. In hindsight, that makes sense — many of the assumptions shaping today’s social platforms were baked in long before ATProto existed.&lt;/p&gt;
&lt;p&gt;What feels most interesting now isn’t necessarily what’s already been built in the &lt;a href=&#34;https://atproto.com/guides/glossary#atmosphere&#34;&gt;Atmosphere&lt;/a&gt; (much of which intentionally mirrors familiar Web 2.0 experiences), but what the protocol’s underlying primitives make possible to design in the future.&lt;/p&gt;
&lt;h2 id=&#34;atproto-primitives&#34;&gt;ATProto Primitives&lt;/h2&gt;
&lt;p&gt;ATProto’s base layer, built on personal data repositories and federated networking, is often described as analogous to the open web. Just as anyone with a computer and an IP address can permissionlessly host a website, anyone can run a Personal Data Server (PDS) and participate in the network.&lt;/p&gt;
&lt;p&gt;The key inversion, though, is that the web is location-addressed: data lives at a URL tied to a server. ATProto is identity-addressed: data lives at an at://username/&amp;hellip; URI tied to a person rather than a machine.&lt;/p&gt;
&lt;p&gt;The protocol also has a two-layer architecture. One layer governs “speech” with the servers, repositories, and federated infrastructure where people publish and store data. In theory, anyone can participate by running their own infrastructure, much like hosting a website on the open web.&lt;/p&gt;
&lt;p&gt;The second layer governs “reach”, which relays, feed generators, and other indexing and discovery services that determine how content is surfaced and distributed across the network. These systems function somewhat like search engines or recommendation layers, shaping visibility rather than hosting the underlying data itself. Some of the key primitives powering this include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://atproto.com/specs/did&#34;&gt;Decentralized Identitifiers (DIDs)&lt;/a&gt;: not a login, a persistent cryptographic identity you can digitally carry around. It&amp;rsquo;s your handle, your relationships, your history, which potentially one could issue for themselves.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://atproto.com/guides/data-repos&#34;&gt;Signed Records&lt;/a&gt;: tamper-evident, self-authenticating data owned by the creator. Our data carries proof of who made it wherever it travels with provenance.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://atproto.com/guides/labels&#34;&gt;Labels&lt;/a&gt;: composable, subscribable, multi-party metadata on any content, meaning anyone can annotate anything, and users can choose whose annotations they trust.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://atproto.com/guides/streaming-data#firehose&#34;&gt;The Firehose&lt;/a&gt;: a real-time stream of all public activity as a raw signal, and users can decide what to listen to. This is what makes third-party apps and new kinds of research and moderation tools possible.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://atproto.com/specs/lexicon&#34;&gt;Lexicons&lt;/a&gt;: synonymous with open schemas, they can be any record type, defined and queryable by anyone. This includes posts, mentions, and likes, as well as scientific papers, code packages, journalist bylines, and moderation votes.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://atproto.com/guides/glossary#app-view&#34;&gt;AppViews&lt;/a&gt;: different “lenses” over the same underlying data, and what people may miss at first is that &lt;strong&gt;Bluesky is just one AppView&lt;/strong&gt;. A science publishing tool is another. A newsroom feed aggregator is another.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;open-science-in-the-atmosphere&#34;&gt;Open Science in the Atmosphere&lt;/h2&gt;
&lt;p&gt;During the workshops I attended on the Open Science track, something clicked, and it wasn’t just one product per se. It was the realization that it was not just lexicons but any record type–a specimen observation, a dataset, a method–defined by anyone, queryable by anyone. &lt;br&gt;
&lt;br&gt;
It was my first real encounter with modular science: the idea that research doesn’t have to take the form of a single, monolithic paper, but can instead be broken into smaller, interoperable pieces, each independently citable. It brought clarity to a shift that has been quietly unfolding in science for some time.&lt;/p&gt;
&lt;p&gt;But scientific credibility currently resides in journals, where publishers like Nature wield immense power to decide what matters and what doesn’t. The data, citation record, and reputation: all of it accrues inside systems the researcher doesn’t own or control. &lt;br&gt;
&lt;br&gt;
Presenters made the point that reproducibility and citation have become afterthoughts bolted onto the publishing workflow that hasn’t fundamentally changed in decades. The epidemic of “sloppification” flooding preprint servers due to the use of LLMs is, of course, hard to ignore. The infrastructure of scientific credibility is captured and inseparable from the platforms that host it, as is the case with journalist credibility.&lt;/p&gt;
&lt;p&gt;This is why &lt;a href=&#34;https://atproto.science/&#34;&gt;atproto.science&lt;/a&gt; is so provocative to me. The idea that a researcher’s DID could function as a persistent scholarly identity is a new thing. A researcher’s contributions and citations that are now owned by an institution or a publisher would instead be theirs. &lt;br&gt;
&lt;br&gt;
And notably, they could use something like &lt;a href=&#34;https://octosphere.social/&#34;&gt;Octosphere&lt;/a&gt; or &lt;a href=&#34;https://layers.pub/&#34;&gt;Layers&lt;/a&gt;, which leverage labels for disaggregated peer review or layered annotations from their trusted communities across various scientific domains.&lt;/p&gt;
&lt;p&gt;At Atmosphere, there was a lot of discussion around how much was being built, and all these efforts seemed to be answering in different ways the question of how researchers build credibility when credibility itself is decentralized.&lt;/p&gt;
&lt;h2 id=&#34;moderation-in-the-atmosphere&#34;&gt;Moderation in the Atmosphere&lt;/h2&gt;
&lt;p&gt;In my opinion, moderation is where ATProto becomes genuinely wondrous and provocative. On most social media platforms, moderation is a black box. Something goes wrong, content disappears, accounts are suspended, and users are left wondering why. The design and operation of governance here is typically mysterious and vague: there&amp;rsquo;s no architecture for disagreement, no surface for appeals, and most importantly, no way to build something different. We all must abide by the platform&amp;rsquo;s rules or leave.&lt;/p&gt;
&lt;p&gt;Ostensibly, ATProto&amp;rsquo;s approach is different. Since labels are an open primitive–composable, subscribable, detachable from any single authority–moderation finally becomes a design surface rather than an opaque platform decree from on high. Anyone can run a labeling service. Communities can define their own standards. Users can subscribe to the labelers they trust. So, the question isn&amp;rsquo;t &amp;ldquo;what does the platform allow?&amp;rdquo;, instead it’s &amp;ldquo;whose judgment do you want to subscribe to?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Recognizing the possibility to visibilize and empower human moderation became the most exciting thing I witnessed–not necessarily any single product. &lt;a href=&#34;https://blackskyweb.xyz/&#34;&gt;Blacksky&lt;/a&gt; built its building moderation tooling, &lt;a href=&#34;https://blackskyweb.xyz/introducing-acorn-community-infrastructure-that-grows-with-you/&#34;&gt;Acorn&lt;/a&gt;, directly on this primitives layer: it’s a tool that lets a small community in the Atmosphere enforce its own norms without needing to build an entire platform to do it.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://npmx.dev/&#34;&gt;NPMx&lt;/a&gt; was demoing something even more ambitious: a browsing layer that lets you navigate ATProto&amp;rsquo;s data space with custom views and filters, putting curation control in the hands of the person, not the app. And Bluesky was beta-testing an AI agent, Attie, letting users personalize moderation by describing exactly what they want to see or avoid, eliminating the need for users to write complex code or logic.&lt;/p&gt;
&lt;p&gt;What strikes me about all of these projects is that none of them is trying to be the final answer to moderation. They&amp;rsquo;re experiments in what becomes possible when moderation is infrastructure rather than policy. &lt;br&gt;
&lt;br&gt;
The design questions they&amp;rsquo;re opening up, like “what does a trust subscription feel like?”, “how do you make a labeling service legible to a non-technical user?”, or “how do you balance community norms with individual autonomy?”, are genuinely novel. Designers haven&amp;rsquo;t had to design for these things before, simply because the architecture didn&amp;rsquo;t permit it.&lt;/p&gt;
&lt;h2 id=&#34;closing-thoughts&#34;&gt;Closing thoughts&lt;/h2&gt;
&lt;p&gt;And so, I came back from the ATmosphere Conference with something I didn&amp;rsquo;t expect: a renewed sense that the problems with the ecosystem of social media platforms worth working on are actually tractable. They’re not easy, not solved, but approachable–designable—in a way that they weren&amp;rsquo;t before.&lt;/p&gt;
&lt;p&gt;The open science and moderation problems I&amp;rsquo;ve described converge on many of the same problems from different angles. Each is fundamentally about the relationship between people, content, and trust, and who gets to define the terms of that relationship. &lt;br&gt;
&lt;br&gt;
What ATProto does is take that question out of the hands of any single platform and put it into the protocol layer, where it becomes a design problem anyone in an ecosystem of apps can work on and fix.&lt;/p&gt;
&lt;p&gt;The community at ATmosphere — researchers, journalists, builders, designers — felt genuinely energized in a way that stood apart from the usual conference dynamic. There was a warmth and sincerity from the outset, shaped in part by how the space was facilitated.&lt;/p&gt;
&lt;p&gt;People kept referring to “the atmosphere” as something more than the event or the protocol itself — a shared orientation toward building systems that don’t repeat the mistakes of Web 2.0.&lt;/p&gt;
&lt;p&gt;Whether that idealism holds up at scale is still an open question. But the design space it is opening up feels real. I&amp;rsquo;ll be watching it closely.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>When do security tools help and when do they fail people?</title>
      <link>https://superbloom.design/learning/blog/when-do-security-tools-help-and-when-do-they-fail-people/</link>
      <pubDate>Thu, 07 May 2026 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/when-do-security-tools-help-and-when-do-they-fail-people/</guid>
      <description>&lt;p&gt;We’ve been sold a simple story about staying safe online. Use a password manager. Turn on two-factor authentication. Download a VPN. Switch to encrypted messaging. If you’re not doing those things, the implication is clear: you’re the problem.&lt;/p&gt;
&lt;p&gt;That story starts to fall apart the minute you step outside ideal conditions. The issue isn’t whether people know about these tools. It’s whether they can actually use them in the context of their daily lives.&lt;/p&gt;
&lt;p&gt;Talk to anyone who manages more than one device, or shares one with family. Talk to people dealing with unreliable internet or moving between apps that don’t quite work together. The tools don’t sit side by side neatly. They stack. A password manager here,  two-factor authentication somewhere else, a messaging app that won’t sync, a VPN that slows everything down or blocks access when you need it most. None of it breaks dramatically, but it just weighs on you with each click.&lt;/p&gt;
&lt;p&gt;What gets dubbed“non-adoption” is usually something more mundane. People forget logins. They get locked out. The onboarding doesn’t quite work. Something breaks and there’s no obvious way back in. Or they simply decide it’s not worth the hassle.&lt;/p&gt;
&lt;p&gt;So they make it work as best they can. They reuse passwords, drop tools halfway through, or they find their own shortcuts. This is not done out of apathy, but because the system isn’t really set up for them.&lt;/p&gt;
&lt;p&gt;And still, much of the response treats this as a behavioral problem. It’s something to fix with better training, clearer nudges, or more awareness. Unequivocally, that misses the point, given the friction is built in.&lt;/p&gt;
&lt;p&gt;We think that’s the wrong starting point. &lt;/p&gt;
&lt;h2 id=&#34;what-were-trying-to-understand&#34;&gt;What we’re trying to understand&lt;/h2&gt;
&lt;p&gt;At Superbloom, we want to understand what actually happens when people use security and privacy tools in the real world. We’re interested in everyday tools: password managers, encrypted messaging, VPNs, and two-factor authentication, along with the moments where they break down.&lt;/p&gt;
&lt;p&gt;That might be during onboarding, over time as habits slip, or when tools collide with real-life conditions like shared devices, unstable connectivity, or organizational constraints. &lt;/p&gt;
&lt;p&gt;Just as importantly, we want to discover what people do next. From the workarounds they develop, to the trade-offs they make, and what’s missing from the current ecosystem. If we want better tools, we need a clearer account of where things fall apart. This research is our attempt to do that. &lt;/p&gt;
&lt;h2 id=&#34;how-were-approaching-it&#34;&gt;How we’re approaching it &lt;/h2&gt;
&lt;p&gt;We’re starting this work with a Pol.is conversation. To be clear, Pol.is is not a survey, and it’s not designed to produce representative findings. Instead, we’re using Pol.is as an exploratory form of sentiment mapping to understand how people are thinking and talking about these tools. We are looking to surface themes, identify points of agreement and disagreement, and pay attention to the language people use to describe their experiences. Pol.is will also allow us to help pinpoint where engagement occurs, which is an important signal in itself at this early stage of our research process. &lt;/p&gt;
&lt;p&gt;It’s worth being clear about what this approach can and can’t do: Pol.is can surface patterns and tensions, but it doesn’t tell us how widespread a view is or represent entire populations. It’s not a substitute for more structured research, but a way to listen first before narrowing the scope too quickly.&lt;/p&gt;
&lt;p&gt;We’ll keep this conversation open over the next two weeks as we test different ways to reach people and invite participation. We’ll then step back to look at what emerges, what themes stand out, what surprises us, where engagement came from, and what remains unclear. Those insights will inform the next phase of the work: designing a more in-depth, repeatable research survey to better understand the patterns we’re seeing and the people behind them.&lt;/p&gt;
&lt;h2 id=&#34;who-do-we-want-to-hear-from&#34;&gt;Who do we want to hear from?&lt;/h2&gt;
&lt;p&gt;We want to hear from people who’ve actually tried to make these tools work. Maybe you use them every day. Maybe you gave up halfway through. Maybe you never really got started. Either way, we want to learn from you. &lt;/p&gt;
&lt;p&gt;Research shows that when security tools don’t work, people take matters into their own hands by working around them, replacing them or dropping them entirely! That has consequences for individuals, organizations, and entire ecosystems, as well as for anyone trying to build or support better alternatives to the systems we already have.&lt;/p&gt;
&lt;h2 id=&#34;share-your-perspective&#34;&gt;S﻿hare your perspective&lt;/h2&gt;
&lt;p&gt;Explore and respond to the Pol.is conversations below.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://pol.is/2wapn8fzmj&#34;&gt;Trust &amp;amp; social proof&lt;/a&gt;&lt;a href=&#34;https://pol.is/8buydnccfj&#34;&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://pol.is/6dmdzed9mu&#34;&gt;Ecosystem friction&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://pol.is/5vfdrszvsa&#34;&gt;Context &amp;amp; resource constraints&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://pol.is/2bbebkdtyd&#34;&gt;Default adoption &amp;amp; shared use&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://pol.is/8buydnccfj&#34;&gt;Onboarding &amp;amp; first use&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://pol.is/3pr7b4kmcx&#34;&gt;Fatigue &amp;amp; institutional pressure&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://pol.is/8udrjxfbnh&#34;&gt;Lockouts &amp;amp; workarounds&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://pol.is/2dtekhpvdk&#34;&gt;Choice overload &amp;amp; defaults&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://pol.is/5ct554bjmu&#34;&gt;Visual trust &amp;amp; transparency&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>MakeShift 2026: Registration Now Open</title>
      <link>https://superbloom.design/learning/blog/makeshift-2026-registration-now-open-1/</link>
      <pubDate>Wed, 06 May 2026 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/makeshift-2026-registration-now-open-1/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/screenshot-2026-05-06-at-11.45.49_hu_b122714b277ae0ff.png&#34; alt=&#34;A banner for promoting MakeShift 2026 happening in NYC on 20-21 May with the event logo and organizers listed as Superbloom, Helpful Places and SVA MFA Interaction Design&#34; width=&#34;740&#34; height=&#34;744&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://luma.com/602z282n&#34;&gt;MakeShift 2026&lt;/a&gt; is just around the corner. Across two days, we’ll bring together designers, technologists, policymakers, academics, and researchers to explore how digital systems shaping public life can become more legible, accountable, and open to intervention.&lt;/p&gt;
&lt;p&gt;Hosted by &lt;a href=&#34;https://helpfulplaces.com/&#34;&gt;Helpful Places&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/&#34;&gt;Superbloom Design&lt;/a&gt;, and the &lt;a href=&#34;https://interactiondesign.sva.edu/&#34;&gt;MFA Interaction Design program&lt;/a&gt; at the &lt;strong&gt;School of Visual Arts&lt;/strong&gt;, MakeShift 2026 will take place &lt;strong&gt;May 20–21, 2026,&lt;/strong&gt; in &lt;strong&gt;New York City&lt;/strong&gt; during &lt;strong&gt;NYC Design Week&lt;/strong&gt;, with support from the &lt;a href=&#34;https://www.nsf.gov/funding/initiatives/pathways-enable-open-source-ecosystems&#34;&gt;U.S. National Science Foundation POSE program&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We’re now sharing a first look at the agenda.&lt;/p&gt;
&lt;h2 id=&#34;designing-accountability-into-public-systems&#34;&gt;Designing accountability into public systems&lt;/h2&gt;
&lt;p&gt;As AI and digital infrastructure become more embedded in everyday environments, the question is no longer just what these systems do but how they are understood, governed, and challenged.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://makeshift2026.dtpr.io/&#34;&gt;MakeShift 2026&lt;/a&gt; is focused on that shift. The program brings together conversations on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;AI and accountability in public contexts&lt;/li&gt;
&lt;li&gt;Designing infrastructure, not just interfaces&lt;/li&gt;
&lt;li&gt;Frameworks for making systems visible and understandable&lt;/li&gt;
&lt;li&gt;How these ideas translate into practice&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;what-to-expect&#34;&gt;What to expect&lt;/h2&gt;
&lt;p&gt;MakeShift 2026 combines plenary sessions, community-led workshops, and a project showcase, creating space to move between discussion and application. The program is still taking shape, with more sessions and contributors to be announced soon. Below is an early snapshot of the agenda.&lt;/p&gt;
&lt;h3 id=&#34;plenary-sessions&#34;&gt;Plenary sessions&lt;/h3&gt;
&lt;p&gt;The agenda includes sessions exploring what it means to design accountability into emerging systems:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Building the Accountability Layer for Public AI&lt;/strong&gt; - A discussion on methods, standards, and the communities these systems serve.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;DTPR for AI&lt;/strong&gt; - How the Digital Trust for Places and Routines framework can be applied to AI systems in public environments.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;workshops&#34;&gt;Workshops &lt;/h3&gt;
&lt;p&gt;Throughout the event, community-led workshops will explore these questions by sharing approaches, tools, and challenges across civic tech, governance, and design. Among them are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Co-designing the Algorithm: Participatory Approaches to AI&lt;/strong&gt; - Reshaping AI systems to foster inclusion, accountability, and meaningful human connection.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SMOL GARDENS: Accountable AI for Civic Tech&lt;/strong&gt; - Exploring how to build accountable, community-centered AI using small language models and practical impact frameworks.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;project-showcase&#34;&gt;Project showcase&lt;/h3&gt;
&lt;p&gt;The program also includes a project showcase and public reception, featuring prototypes, installations, and early-stage ideas. This is a chance to see these concepts being tested in practice and to connect directly with the people building them. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;NYC Transit Pulse&lt;/strong&gt; is a voice-first AI agent that gives New Yorkers real-time subway intelligence — delays, service alerts, elevator outages, and more — through natural conversation.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;311 Live&lt;/strong&gt; is a live, multimodal civic reporting product that reimagines how residents communicate city issues. Instead of filling out static forms, residents can speak naturally while showing a problem through their phone camera. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Unseen Stories&lt;/strong&gt; is a series of physical and digital interactive installations in Strawberry Fields, Central Park. Visitors lift a vintage telephone to hear archival voices, look through a viewfinder to glimpse the site&amp;rsquo;s layered past, and take home a wooden coaster that brings the stories back to life when scanned.&lt;/p&gt;
&lt;h2 id=&#34;who-should-attend&#34;&gt;Who should attend&lt;/h2&gt;
&lt;p&gt;MakeShift is for people working across:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Design &amp;amp; UX&lt;/li&gt;
&lt;li&gt;Research &amp;amp; academia&lt;/li&gt;
&lt;li&gt;Civic tech &amp;amp; public infrastructure&lt;/li&gt;
&lt;li&gt;Policy &amp;amp; governance&lt;/li&gt;
&lt;li&gt;Digital rights &amp;amp; public-interest technology&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you’re working on how digital systems shape public life or trying to intervene in that process, this is a space to connect and share. Curious to learn more? Register to attend now! &lt;a href=&#34;https://luma.com/602z282n&#34;&gt;https://luma.com/602z282n&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;register-for-makeshift-2026&#34;&gt;Register for MakeShift 2026&lt;/h2&gt;
&lt;p&gt;May 20–21, 2026&lt;br&gt;
&lt;a href=&#34;https://maps.app.goo.gl/py2nKRLoKGyKctnr8&#34;&gt;136 W 21st Street, New York City&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.nycxdesign.org/festival&#34;&gt;Part of NYC Design Week&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Register to attend:&lt;/strong&gt; &lt;a href=&#34;https://luma.com/602z282n&#34;&gt;https://luma.com/602z282n&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MakeShift 2026 website:&lt;/strong&gt; &lt;a href=&#34;https://makeshift2026.dtpr.io/&#34;&gt;https://makeshift2026.dtpr.io/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Interested in sponsoring the event? Get in touch at &lt;a href=&#34;mailto:hello@dtpr.io&#34;&gt;hello@dtpr.io&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Call for Proposals: MakeShift 2026 Submissions Now Open</title>
      <link>https://superbloom.design/learning/blog/call-for-proposals-accepting-submissions-for-makeshift-2026/</link>
      <pubDate>Mon, 09 Mar 2026 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/call-for-proposals-accepting-submissions-for-makeshift-2026/</guid>
      <description>&lt;p&gt;Digital systems increasingly shape public life, from sensors embedded in city infrastructure to AI-enabled systems that influence how services, mobility, and public spaces operate. Yet the technologies shaping our shared environments often remain invisible to the people affected by them.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MakeShift 2026: Accountable Tech by Design&lt;/strong&gt; invites designers, technologists, researchers, artists, and advocates to reimagine how we design and govern digital systems to make them more legible, accountable, and trustworthy in public spaces.&lt;/p&gt;
&lt;p&gt;Hosted by &lt;a href=&#34;https://www.helpfulplaces.com/&#34;&gt;Helpful Places&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/&#34;&gt;Superbloom Design&lt;/a&gt;, and the &lt;a href=&#34;https://interactiondesign.sva.edu/&#34;&gt;MFA Interaction Design program at the School of Visual Arts&lt;/a&gt;, MakeShift 2026 will take place &lt;strong&gt;May 20–21, 2026,&lt;/strong&gt; in &lt;strong&gt;New York City&lt;/strong&gt; during &lt;strong&gt;NYC Design Week&lt;/strong&gt;, with support from the &lt;strong&gt;U.S. National Science Foundation POSE program&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;We are now accepting submissions for call for proposals across two tracks.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Track 1 - Propose a Session&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We welcome proposals for talks, workshops, roundtables, design sprints, or community gatherings that explore questions around AI accountability, civic technology, digital governance, public infrastructure, and participatory design. Sessions may run up to 90 minutes and should contribute new ideas, practices, or frameworks for designing accountable technology.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Track 2 - Respond to the Design Challenge&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Participants may also submit creative projects responding to the &lt;a href=&#34;https://dtpr.io/&#34;&gt;Digital Trust for Places &amp;amp; Routines&lt;/a&gt; (DTPR) standard—an open-source framework designed to make technologies operating in shared spaces more transparent and understandable.&lt;/p&gt;
&lt;p&gt;Projects might include prototypes, research, signage systems, speculative design, installations, or other creative work exploring how design can make digital infrastructure more visible and accountable. Selected projects will be exhibited during NYC Design Week at the School of Visual Arts and featured as part of the conference program.&lt;/p&gt;
&lt;h3 id=&#34;who-should-apply&#34;&gt;&lt;strong&gt;Who Should Apply&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;We welcome submissions from designers, artists, researchers, technologists, civic technologists, digital rights advocates, public-sector innovators, and community organizers working at the intersection of design, technology, governance, and digital justice.&lt;/p&gt;
&lt;h3 id=&#34;how-to-apply&#34;&gt;&lt;strong&gt;How To Apply&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;S﻿ubmission deadline:&lt;/strong&gt; 17 April, 2026&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;S﻿ubmission Guide:&lt;/strong&gt; &lt;a href=&#34;https://tinyurl.com/makeshiftguide&#34;&gt;https://tinyurl.com/makeshiftguide&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Apply Here:&lt;/strong&gt; &lt;a href=&#34;https://forms.gle/gbVY6rc93JSmPAcU8&#34;&gt;https://forms.gle/gbVY6rc93JSmPAcU8&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Have Questions?:&lt;/strong&gt; Contact us at &lt;a href=&#34;mailto:hello@dtpr.io&#34;&gt;hello@dtpr.io&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Making Threat Modeling Human: Key Takeaways from Our Work with Bitpart </title>
      <link>https://superbloom.design/learning/blog/making-threat-modeling-human-key-takeaways-from-our-work-with-bitpart/</link>
      <pubDate>Tue, 03 Mar 2026 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/making-threat-modeling-human-key-takeaways-from-our-work-with-bitpart/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;Imagine you&amp;rsquo;re a librarian of a vast library of precious books. What keeps you up at night? How would you protect the books from threats? You might worry about fires, floods, or people trying to steal or destroy what’s inside. But what if the biggest risks weren’t outside the library at all—what if they lived inside it, in the everyday decisions and limits of the librarians themselves? How would you keep everyone safe, including the people doing the protecting?&lt;/p&gt;
&lt;p&gt;These are the kinds of questions that guided our work with &lt;a href=&#34;https://throneless.tech/&#34;&gt;Throneless Tech&lt;/a&gt; on &lt;a href=&#34;https://bitp.art&#34;&gt;Bitpart&lt;/a&gt;, a secure communications platform for journalists, activists, and human rights defenders. This work was part of the &lt;a href=&#34;https://www.opentech.fund/labs/uxd-lab/&#34;&gt;UXD Lab&lt;/a&gt;, supported by the &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;. Before its launch, we worked together with Throneless Tech to design and stress-test the platform&amp;rsquo;s prototype. By combining &lt;a href=&#34;https://coach.andrewlb.com/workshop/disaster-game&#34;&gt;Disaster Games&lt;/a&gt; with &lt;a href=&#34;https://superbloom.design/learning/resources/persona-non-grata/&#34;&gt;Personas Non Grata&lt;/a&gt;— methods used to surface failure modes, threats, and risks—we learned that you can’t secure a “library” if you don’t account for the stress, burnout, and humanity of the people caring for the books and holding the keys.&lt;/p&gt;
&lt;h4 id=&#34;the-problems-we-aimed-to-solve&#34;&gt;The Problems We Aimed To Solve&lt;/h4&gt;
&lt;p&gt;There’s no shortage of threat modeling frameworks. &lt;a href=&#34;https://en.wikipedia.org/wiki/STRIDE_model&#34;&gt;STRIDE&lt;/a&gt;, attack trees, and data flow diagrams offer structured ways to surface technical vulnerabilities and answer questions like, what can an attacker do to our assets, and where might the system be weak? Those tools are valuable when you have a relatively stable product, team, and architecture, and you mainly need to harden endpoints, restrict access, or perhaps patch dependencies.&lt;/p&gt;
&lt;p&gt;Bitpart was not that kind of project. It was an early-stage prototype for high-risk users, built by a small developer co-op balancing multiple commitments, in environments where “security” has to include legal, social, and organizational realities—not just encrypted databases and hardened APIs. So we needed to understand threats that don’t show up neatly in predefined categories: burnout, coercion, overwork, and single points of human failure.&lt;/p&gt;
&lt;p&gt;That meant offering space for participation, not prescription. A prescriptive use of a traditional framework might have produced a solid list of vulnerabilities to fix, but not a shared understanding of why they mattered in this context or how new ones might emerge over time. Instead, with the team, we were aiming to build threat literacy specific to Bitpart: a shared capacity across users, administrators, and maintainers to think proactively about risk.&lt;/p&gt;
&lt;p&gt;Existing frameworks acknowledge concepts such as insider threats and social engineering, but they usually frame humans as attack vectors or points of failure. We were focused on what could go wrong with the people and how that would cascade through everything else. That required empathizing with the exhausted, stressed, multitasking people operating and sustaining the platform and treating their cognitive limits and working conditions as core security concerns, not necessarily edge cases.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/screenshot-2026-03-03-at-19.40.34_hu_c1c86a7ffbb58c8b.png&#34; width=&#34;740&#34; height=&#34;66&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;our-approach&#34;&gt;Our Approach&lt;/h4&gt;
&lt;p&gt;&lt;strong&gt;Making space&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;To begin, we anonymously collected team members&amp;rsquo; anxieties using a short survey before the Disaster Game workshop.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/screenshot-2026-03-03-at-12.27.26_hu_b718d730ae7c357f.png&#34; width=&#34;740&#34; height=&#34;632&#34;&gt;
&lt;/p&gt;
&lt;p&gt;We wanted to give all team members the space to communicate the disasters they see as possible and the anxieties they hold about Bitpart. We would later prioritize the responses we compiled from the survey during the workshop.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Priming the team&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;To begin our workshop, we decided that before we even mentioned threats or any consequential risks we had gathered from our short survey, we should facilitate a review of the user personas from our earlier research. These were not demographic composites but instead personas of end users and admins with concrete scenarios about how they would actually use Bitpart under pressure. In taking a moment to do this from the outset, we were centering human experience to prime the team’s imagination. I believe this was an important step for a product prototype. Meaning rather than talking about Bitpart users in the abstract and/or hastily crafting scenarios on the spot, we were prepared to ground the exercise in specific people, contexts, and constraints. That way, later, whenever we asked, “What could go wrong?”, the question would be anchored by something shared and concrete.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/bitpart-organizer-persona_hu_d859a0a8522bd6a4.png&#34; width=&#34;740&#34; height=&#34;740&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;meet-akello-online-organizer&#34;&gt;Meet A﻿kello: Online Organizer&lt;/h4&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/screenshot-2026-03-03-at-13.26.32_hu_603d4b0184265939.png&#34; width=&#34;740&#34; height=&#34;667&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Playing With Disasters&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;With those personas in mind, we continued on with the Throneless Tech team. We deliberately steered the focus away from the “easy” disasters—server crashes or widespread data breaches—and instead, focused the team on clear stress cases (i.e. catastrophes like arrests, device seizures, admin abductions, and funding cuts). As the team played the game, it focused on these “likely” catastrophes, threats, and vulnerabilities that surfaced across end users, admins, and maintainers—the platform&amp;rsquo;s whole human stack.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;After the Workshop&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;At the close of the workshop, we shifted to an “actor-based” threat-modeling approach. That is, after composing and sorting the most likely disasters for Bitpart, we helped the team decompose one of those disasters to properly identify potential threat actors within an inflection point or catastrophe. So after the workshop, I continued with this process for the rest, ultimately grouping them into a threat-scenario matrix that detailed all the actors, their goals, potentially affected system areas, and potential consequences.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/bitpart-state-actor-persona_hu_6405771519d59ae0.png&#34; width=&#34;740&#34; height=&#34;740&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/screenshot-2026-03-03-at-12.45.29_hu_77baf89a134ee010.png&#34; width=&#34;740&#34; height=&#34;202&#34;&gt;
&lt;/p&gt;
&lt;p&gt;I used this as input to take a more process-based approach to understand the threats in the specific conversational flows and the larger arcs of user journeys. Using the Personas Non Grata, I stepped through both conversational flows and journeys to see exactly where and how a disaster could emerge from a threat actor at a specific interaction (i.e. site of vulnerability).&lt;/p&gt;
&lt;h4 id=&#34;what-we-discovered&#34;&gt;What We Discovered&lt;/h4&gt;
&lt;p&gt;&lt;strong&gt;Safety and Care Throughout the Whole Human Stack&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The workshop reframed where safety and care “live” in Bitpart. As the group played through these catastrophes, something important emerged. The threats they identified didn’t cluster around a single type of user. Vulnerabilities showed up across three distinct but interdependent layers:&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/screenshot-2026-03-03-at-12.49.33_hu_ff8e3de4a4dabbd8.png&#34; width=&#34;740&#34; height=&#34;272&#34;&gt;
&lt;/p&gt;
&lt;p&gt;End-users whose devices and identities could be exposed, Bitpart Administrators whose judgment and capacity shaped how safely Bitpart was operated, and the Maintainers whose ability to sustain the project determined whether any of that protection would exist over time. A failure in any one of these layers could cascade into the others; e.g., an overworked admin making a rushed decision could expose subscribers, or a burned-out maintainer could leave critical vulnerabilities unpatched.&lt;/p&gt;
&lt;p&gt;What became clearer was that a “harmful librarian” is almost always a system failure, not a personal failure. People might make unsafe choices when systems they use lean too heavily on their memory and attention. Furthermore, without giving them adequate support or guidance, these people are likely to sacrifice their own well-being under pressure.&lt;/p&gt;
&lt;p&gt;Overall, Disaster Games worked not because it produced a better checklist, but because it emotionally simulated what panic, stress, and overwhelm might feel or look like in practice. We weren’t just thinking through risks; we were feeling what it would mean to be the “librarian” while everything went wrong. That simulation surfaced vulnerabilities that no audit alone would have revealed.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Personas Made Threats More Designable&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We surfaced a lot of emotional content during the workshop: fear of legal retaliation, worry about making mistakes under pressure, and anxiety about being the only person who knows how a specific system works. The patterns in those fears told us where the team already had awareness of Bitpart’s fragility—places where responsibilities were vague or where safeguards relied too heavily on individual heroics. We turned those anxieties into Personas Non Grata; we weren’t inventing new threats; we were giving shape to the risks the team already felt but hadn’t yet named.&lt;/p&gt;
&lt;p&gt;Once those anxieties were crystallized into concrete personas—the coerced admin, the overextended moderator, the solo maintainer—they became design inputs. With the team, we could ask targeted questions like, &lt;em&gt;what happens in this flow if the admin is exhausted? What if they are under legal pressure? What guardrails or prompts in the UI would help?&lt;/em&gt; This was an important shift, since it turned abstract anxieties into specific design opportunities. Meaning the team could make design decisions more effectively. Examples could include clearer defaults, better documentation, safer handoff points, and ways to reduce the cognitive load on people operating Bitpart under stress.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sustainability is a Risk&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;One of the most important discoveries was that project sustainability itself emerged after the workshop as a security problem, not just an operational one. Through the game and the subsequent mappings, it became clear how much of Bitpart’s safety depended on some people continuing to have time, energy, and funding to maintain it. The lack of contributors was not just a potential problem of governance; it was an existential threat to any user who might rely on Bitpart, since an unmaintained security tool quickly becomes a dangerous one.&lt;/p&gt;
&lt;p&gt;Here, the divergent exploration of “everything that could go wrong” in the Disaster Game helped prevent tunnel vision and provided a diversity of ideas. By opening up to a wide range of socio-technical catastrophes (and only later converging on the most likely and impactful ones), we weren’t fixating on a single, familiar category of risk (e.g., external attackers) and missing slow-moving threats like maintainer exhaustion or funding gaps. This insight led directly to another workshop focused on mapping the Contributor Persona and Journey with conversations about documentation and governance as forms of safety and care work.&lt;/p&gt;
&lt;h4 id=&#34;the-outcome&#34;&gt;The Outcome&lt;/h4&gt;
&lt;p&gt;Again, the most important outcome wasn’t a checklist of issues; it was shared threat literacy across everyone working on Bitpart. Now, Throneless had a common vocabulary for talking about risk at the end-user, administrator, and maintainer layers, with a clearer sense of how failures in one layer could cascade into the others.&lt;/p&gt;
&lt;p&gt;Combining Disaster Games and Personas Non Grata turned ambient worry and rumination into actionable design questions. Instead of the vague sense “someone is at risk,” the team could now ask, what happens in this flow if the administrator is overwhelmed? What guardrails or defaults could better support them in this moment? This led to concrete changes: clearer defaults in flows, safer handoff points between the platform and users, and a renewed focus on documentation as a way to reduce cognitive load.&lt;/p&gt;
&lt;p&gt;Finally, the team recognized that their nascent platform’s security depended heavily on a few people continuing to maintain and fundraise for the project. That realization led directly to the team treating governance and contributor onboarding as forms of safety and care work for the communities Bitpart aims to serve.&lt;/p&gt;
&lt;h4 id=&#34;credits&#34;&gt;C﻿redits&lt;/h4&gt;
&lt;p&gt;W﻿ith thanks to &lt;a href=&#34;https://www.opentech.fund&#34;&gt;Open Technology Fund&lt;/a&gt; for supporting this work.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>From Content to Interface: Rethinking Platform Transparency Through Design</title>
      <link>https://superbloom.design/learning/blog/2026-the-year-we-choose-to-protect-childrenor-fail-them/</link>
      <pubDate>Tue, 16 Dec 2025 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/2026-the-year-we-choose-to-protect-childrenor-fail-them/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/chirayu-trivedi-lh-6oe-dllu-unsplash_hu_2e9067877d8af67.jpg&#34; alt=&#34;A photo of a lit candle with stars in the dark.&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;p&gt;A few weeks ago, a photo on LinkedIn from the TikTok For You(th) Summit in London caught my eye. Baby pink background, cheerful branding, adults discussing safety and well-being for youth. It was optimistic. &lt;/p&gt;
&lt;p&gt;This was a stark contrast to &lt;a href=&#34;https://www.amnesty.org/en/documents/POL40/0360/2025/en/&#34;&gt;Amnesty Tech’s report on TikTok&lt;/a&gt;’s treatment of teens, which I stumbled upon only hours before. The findings specifically focused on how accounts coded as children were pulled into self-harm content spirals within hours after signup. Those two moments, the glossy summit and the grim findings, sat side by side on my screen like two realities that cannot co-exist.&lt;/p&gt;
&lt;p&gt;One is the safety story platforms tell us. The other is what research continues to show.&lt;/p&gt;
&lt;p&gt;And this isn’t unique to TikTok. Instagram recently received its own reckoning in &lt;a href=&#34;https://fairplayforkids.org/wp-content/uploads/2025/09/Teen-Accounts-Broken-Promises-How-Instagram-is-failing-to-protect-minors.pdf&#34;&gt;Teen Accounts: Broken Promises,&lt;/a&gt; a report co-authored by the Meta whistleblower who has been warning the company internally for years. The headline number is devastating:&lt;/p&gt;
&lt;p&gt;64% of Instagram’s safety mechanisms for teens were “red” — meaning they didn’t work or were easily bypassed. Only 17% worked as promised.&lt;/p&gt;
&lt;p&gt;Meta says children are protected. The numbers suggest children are navigating these systems mostly alone.&lt;/p&gt;
&lt;p&gt;As a Hungarian, design-focused digital rights researcher — and a parent — I’ve come to recognise the pattern: big tech platforms, like governments, often prioritize the performance of care instead of delivering it. &lt;/p&gt;
&lt;p&gt;We’ve also witnessed childhood safety being compromised and justified not only on social platforms but by generative AI chatbot firms, too. Look no further than the recent OpenAI suicide case, where a child used ChatGPT to assist them in taking their own life. The company argues that a 16-year-old violated its terms by bypassing safety measures, and that its FAQ warned users not to rely on outputs without independent verification. &lt;/p&gt;
&lt;p&gt;Expecting a teenager to read, understand, and comply with the terms of service is not child protection. It is abdication. Terms of use and FAQs are not safety measures; they are legal shields. They exist to manage corporate liability, not to protect a child in crisis.&lt;/p&gt;
&lt;p&gt;Offloading responsibility onto minors by asking them to decipher legal language, interpret abstract warnings, and regulate their behavior while interacting with a persuasive, human-like system is the opposite of safety by design. It is a calculated transfer of risk from companies to children.&lt;/p&gt;
&lt;p&gt;And let’s be clear: if a “safeguard” can be breached by a child through ordinary, foreseeable use, then it was never a safeguard at all. A protection a child cannot understand, access, or use in the moment it matters is not protection. It is a fiction and a dangerous one.&lt;/p&gt;
&lt;h3 id=&#34;might-2026-signal-a-long-awaited-shift&#34;&gt;Might 2026 signal a long-awaited shift?&lt;/h3&gt;
&lt;p&gt;The EU’s Digital Services Act (DSA), passed in 2022, was designed to finally give regulators the power to intervene when digital platforms harm users. DSA’s Article 28 requires platforms to make environments safe and age-appropriate for minors by design. One part of the &lt;a href=&#34;https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:C_202505519&#34;&gt;Article 28’s guidelines&lt;/a&gt; deals specifically with children’s user experience: the buttons they see, the defaults they’re nudged into, the friction they meet when trying to protect themselves.&lt;/p&gt;
&lt;p&gt;Confronting this is vital because children are not harmed only by content, they’re harmed by the design choices that surround them. Children encounter everything from autoplay to infinite scrolling, night-time notifications, default-open DMs and perhaps even a &amp;ldquo;safety&amp;rdquo; toggle buried under six cheerful menus. These harms are not distributed evenly: marginalized children – racialized, disabled, queer, migrant, or low-income youth – often face compounded risks and fewer accessible protections. &lt;/p&gt;
&lt;p&gt;None of this is random. All of it is measurable if we measure the right things. These design choices don’t appear in a vacuum. They are embedded in &lt;a href=&#34;https://rankingdigitalrights.org/its-the-business-model/&#34;&gt;business models&lt;/a&gt; that depend on maximizing attention, data extraction, and engagement. Any meaningful safety effort should confront not only interface issues but also the incentives beneath them.&lt;/p&gt;
&lt;p&gt;And now the &lt;a href=&#34;https://www.europarl.europa.eu/news/en/press-room/20251120IPR31496/children-should-be-at-least-16-to-access-social-media-say-meps&#34;&gt;European Parliament is pushing even harder&lt;/a&gt;: proposing a 16+ minimum age for social media, banning engagement-based recommender systems for minors, and switching off addictive features like infinite scroll and autoplay by default. While the EU currently leads on regulatory frameworks, children’s digital experiences and the harms they face vary widely globally. Any approach to platform safety must avoid exporting a single regional standard as universal, and must include voices and realities from the Global Majority.&lt;/p&gt;
&lt;p&gt;So, we face a crucial question: How do we study manipulative platform design without exposing children to harm, and in a way that regulators can enforce? Most research still focuses on what children see, and that is important. We are interested in understanding how they get there. In our work, we don’t chase virality metrics or moderation logs. We look at flows. Because harm is rarely a single feature. It’s the journey: the clicks it takes to report abuse, the invisibility of the “off” switch, how fast a child can exit once something feels wrong.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;How might we avoid exposing children to harmful feeds, while still learning what matters—namely, whether safety features are truly usable?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Can they turn off tracking? Can they delete an account? Can they limit recommendations, set time boundaries, and exit when things don’t feel right?&lt;/p&gt;
&lt;p&gt;If reporting a harmful interaction takes seven taps and a trip outside the app, only &lt;a href=&#34;https://fairplayforkids.org/wp-content/uploads/2025/09/Teen-Accounts-Broken-Promises-How-Instagram-is-failing-to-protect-minors.pdf&#34;&gt;0.02% of teens will get help—as Meta’s own data shows&lt;/a&gt;. UX is not superficial: it is the mechanism through which harm travels. &lt;strong&gt;If a safety control is unusable or inaccessible to a child, it is effectively not there.&lt;/strong&gt; And that’s problematic for children, parents and society as a whole. &lt;/p&gt;
&lt;p&gt;Traditional oversight models rely on content analysis, algorithmic audits, or risk assessment documentation provided by platforms themselves. All are valuable but not sufficient for effectively measuring compliance of platform design-related issues.&lt;/p&gt;
&lt;p&gt;Civil society faces two barriers:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;We cannot ethically expose minors to harmful environments to study them. And when we involve young people in research, that participation must be ethical, compensated, consent-driven, and grounded in long-term relationships not extractive.&lt;/li&gt;
&lt;li&gt;This research must be replicable and affordable, not just something a well resourced organisation can do once.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The good news is that in user research, when a feature is broken, it breaks fast. We don’t need thousands of minors, just small, diverse cohorts of users. Patterns reveal themselves quickly.  Children and teens are not only vulnerable. They are experts in their own experiences. Effective safety systems must be shaped with them, not merely for them, especially across lines of race, disability, gender, and socioeconomic background.&lt;/p&gt;
&lt;p&gt;The part that needs to scale isn’t the children. It’s the structure around them.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;interface maps of entire safety journeys&lt;/li&gt;
&lt;li&gt;shared taxonomies of manipulative patterns&lt;/li&gt;
&lt;li&gt;standardized walkthrough scripts for regulators&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/superblooms-user-experience-toolbox-for-risk-mitigation-and-accessibility/&#34;&gt;usability &amp;amp; accessibility heuristics&lt;/a&gt; tied to Article 28&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Heuristics, in plain language, are rule-of-thumb tests for whether a design works. Did the child understand the setting? Could they find it? Did it behave as expected? If not, it fails, even if it “exists” on paper.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;This matters because compliance has often meant: the safety feature exists somewhere. What we need is a safety feature that works for the users it is intended to serve, and it protects them.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;And if &lt;a href=&#34;https://www.reuters.com/sustainability/boards-policy-regulation/meta-buried-causal-evidence-social-media-harm-us-court-filings-allege-2025-11-23/&#34;&gt;recent revelations about Meta&lt;/a&gt; have shown us anything - from lawsuits alleging intentionally ineffective youth safety tools to internal reports where researchers were allegedly told not to collect data on under-13s “due to regulatory concerns” - it’s that platforms cannot be relied on to evaluate their own design risks. Someone else has to test the interface.&lt;/p&gt;
&lt;h2 id=&#34;so-what-should-change-look-like-in-2026&#34;&gt;So, what should change look like in 2026?&lt;/h2&gt;
&lt;p&gt;Here’s the hopeful version, and I think it’s still possible:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Default-safe design, not default-addiction.&lt;/li&gt;
&lt;li&gt;Safety features that work, not safety features that just exist.&lt;/li&gt;
&lt;li&gt;Safety feature design needs to be co-designed with children. &lt;/li&gt;
&lt;li&gt;Shared interface design audit tooling so every investigation doesn&amp;rsquo;t restart from zero.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Regulators don’t just need data. They need methods. And they are starting to say so out loud. Parents across the political spectrum want change, and patience is gone. 2026 won’t be the year we fix everything. But it could be the year we stop pretending and start acting. &lt;/p&gt;
&lt;p&gt;No single team, researcher, regulator, or NGO can solve this. Durable change requires shared accountability across youth, parents, educators, civil society, platform workers, and regulators. Our work is one piece of a much larger ecosystem.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>DTPR</title>
      <link>https://superbloom.design/learning/collections/dtpr/</link>
      <pubDate>Mon, 10 Nov 2025 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/collections/dtpr/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Growing the DTPR Ecosystem: A New Chapter for Digital Trust and Transparency</title>
      <link>https://superbloom.design/learning/blog/growing-the-dtpr-ecosystem-a-new-chapter-for-digital-trust-and-transparency/</link>
      <pubDate>Mon, 10 Nov 2025 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/growing-the-dtpr-ecosystem-a-new-chapter-for-digital-trust-and-transparency/</guid>
      <description>&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dtpr-header-2.svg&#34; alt=&#34;A graphic of a park and members of the community in a publlic space in pale blue. &#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.helpfulplaces.com/&#34;&gt;Helpful Places&lt;/a&gt; and Superbloom are excited to team up in order to grow the open-source ecosystem around &lt;a href=&#34;https://dtpr.io/&#34;&gt;Digital Trust for Places &amp;amp; Routines (DTPR)&lt;/a&gt;. This next chapter isn’t just about launching new work. It’s about expanding a shared story: seeing the invisible digital systems around us, building practical tools that make transparency meaningful for everyone, shifting norms, and setting new expectations for how technology is introduced into communities. &lt;/p&gt;
&lt;h5 id=&#34;seeing--making-the-invisible-visible&#34;&gt;Seeing → Making the invisible visible&lt;/h5&gt;
&lt;p&gt;Every day, digital technologies operate quietly in the background of our physical world: sensor networks in transit hubs, analytics in cultural spaces, smart infrastructure in public parks, traffic management systems and automatic license plate readers on our roads. For most people, these systems are invisible.  DTPR helps people see them. It’s a human-centered, open framework inspired by visual languages and the “nutrition label” to make AI and data practices that are part of the built environment and our everyday routines more visible. Consisting of a structured taxonomy, associated icons and design patterns on how to use and present these components, DTPR explains what data is being collected, by whom, and for what purpose. It turns hidden digital infrastructure and processes into something legible and accountable.&lt;/p&gt;
&lt;h5 id=&#34;building--turning-principles-into-practice&#34;&gt;Building → Turning principles into practice&lt;/h5&gt;
&lt;p&gt;With support from the U.S. National Science Foundation, Helpful Places and Superbloom are exploring ways to lay the groundwork for DTPR to scale as an open-source ecosystem. Over the coming months, the partnership will focus on three pillars:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ecosystem research: Mapping how DTPR is currently being used, identifying which communities, geographies, and sectors might be interested in using it next, and what barriers might be limiting adoption and contribution. &lt;/li&gt;
&lt;li&gt;Community development:  Creating spaces such as workshops, collaboration channels, and convenings where designers, cities, researchers, and civic technologists can learn from each other, engage around governance, co-create, and develop DTPR.&lt;/li&gt;
&lt;li&gt;Shared governance: Designing a sustainable structure so that DTPR remains community-led, open, and adaptable long into the future.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This phase is about learning, listening and figuring out how to make it easy for practitioners and community members to implement DTPR, contribute back, and shape it as a living public resource that serves everyone.&lt;/p&gt;
&lt;h5 id=&#34;shifting--from-pilots-to-norms&#34;&gt;Shifting → From pilots to norms&lt;/h5&gt;
&lt;p&gt;Transparency shouldn’t be a special project or a nice-to-have. It should be standard practice.&lt;/p&gt;
&lt;p&gt;As digital technologies become embedded in everyday places and daily routines -  From libraries to transit systems, people need ways to understand and trust the digital systems that affect their lives and communities. DTPR helps create that cultural shift: openness not as a promise, but as an expectation.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“DTPR began as a way to make invisible technologies visible,” said Jacqueline Lu, Founder and CEO of Helpful Places. “Now we’re building the networks and governance that can sustain it, ensuring it remains open, adaptable, and rooted in public benefit.”&lt;/p&gt;
&lt;p&gt;“This next phase is about growing DTPR as a living ecosystem,” said Georgia Bullen of Superbloom. “We’re creating the conditions for open collaboration, so communities can build on DTPR and make transparency a shared standard.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Together, Helpful Places and Superbloom are working toward a world where public technologies are designed with care, accountability, and community at the center.&lt;/p&gt;
&lt;p&gt;Want to learn more or be part of the growing ecosystem? &lt;a href=&#34;https://docs.google.com/forms/d/e/1FAIpQLSdCOrFKYzPwjqhGlvbaKNOXjXXvpY7kGGRUbf79moVayX8azQ/viewform&#34;&gt;Register to attend&lt;/a&gt; our workshop at Smart Cities Connect on Friday, November 21, at 9:00 a.m. &lt;/p&gt;
&lt;p&gt;Follow along as we share updates, invitations to participate, and stories from the growing DTPR community. Visit: &lt;a href=&#34;https://dtpr.io&#34;&gt;https://dtpr.io&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;This project, Legible Urban Tech - Digital Trust for Places and Routines, is made possible by support from the U.S. National Science Foundation through the Pathways to Open Source Ecosystems (POSE) program.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>NSF POSE</title>
      <link>https://superbloom.design/work/projects/nsfpose/</link>
      <pubDate>Mon, 10 Nov 2025 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/work/projects/nsfpose/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Open Source Summit Europe</title>
      <link>https://superbloom.design/community/events/open-source-summit-europe/</link>
      <pubDate>Tue, 28 Oct 2025 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/events/open-source-summit-europe/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Seeing Open Source Through a Designer’s Eyes at Open Source Summit Europe 2025</title>
      <link>https://superbloom.design/learning/blog/seeing-open-source-through-a-designers-eyes-at-oss-summit-eu-2025/</link>
      <pubDate>Tue, 28 Oct 2025 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/seeing-open-source-through-a-designers-eyes-at-oss-summit-eu-2025/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_oss_summit_2025_hu_51761ecd596e1cd2.png&#34; alt=&#34;Event slide image. Teal/yellow/lilac Van Gogh style image with the slide title: The Secret Lives of OSS Designers: Understanding Designers Contributing to OSS&#34; width=&#34;740&#34; height=&#34;414&#34;&gt;
&lt;/p&gt;
&lt;p&gt;In August 2025, I had the chance to attend Open Source Summit Europe 2025, a flagship event by the Linux Foundation, held in Amsterdam from 25 to 27 August. As a first-time speaker and designer stepping into a developer-dominated space, I joined thousands of contributors, maintainers, and innovators for four days of talks, workshops, and community days focused on advancing open source software. What started with a bit of hesitation quickly turned into an inspiring experience, proving that design has a vital seat at the open source table.&lt;br&gt;
&lt;br&gt;
&lt;a href=&#34;https://www.youtube.com/watch?v=ZdFID6ViKHo&amp;amp;list=PLwz4EueITgvmJzrNWbGkAMeDVLlOWQuch&#34;&gt;&lt;/a&gt;This year, I walked into &lt;a href=&#34;https://events.linuxfoundation.org/archive/2025/open-source-summit-europe/&#34;&gt;Open Source Summit Europe 2025&lt;/a&gt; for the very first time, not just as an attendee, but as a speaker. And I’ll admit, I carried a quiet hesitation with me.&lt;/p&gt;
&lt;p&gt;As a designer in the world of open source, I’ve learned to expect raised eyebrows. At best, polite confusion: “What’s a designer doing here?” At worst, a cold shoulder. This is especially given that OSS spaces have historically catered to developers. Too often, design is treated as decoration, something that comes after the “real” work is done.&lt;/p&gt;
&lt;p&gt;But something shifted at OSSummit. Instead of skepticism, I found curiosity. Instead of dismissal, I found conversations. Contributors and maintainers asked questions, sought out resources, and welcomed design as part of the fabric of open source. For me, it was a reminder that OSS doesn’t just belong to developers. It belongs to anyone willing to help make it stronger, safer, and more usable.&lt;/p&gt;
&lt;h4 id=&#34;security-as-a-shared-responsibility&#34;&gt;Security as a shared responsibility&lt;/h4&gt;
&lt;p&gt;One theme echoed through almost every session: security and integrity in OSS.&lt;/p&gt;
&lt;p&gt;I sat in on Daniel Rabinovitz’s talk, “Keeping Your Software Supply Chain Healthy.” His message was simple but powerful: every contributor—regardless of role—has a part to play in securing OSS.&lt;/p&gt;
&lt;p&gt;At first, it felt far from my lane as a designer. But the more I listened, the clearer it became:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;As a researcher and designer, understanding developers’ priorities around security helps me grasp their workflows, their mental models, and the pressures shaping their decisions.&lt;/li&gt;
&lt;li&gt;As a contributor, even if I’m not writing code, knowing the risks of supply chains and dependencies makes me a more responsible member of the OSS ecosystem.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It was a reminder that open source isn’t a collection of silos. Documentation, design, code, and community are all interconnected.&lt;/p&gt;
&lt;h4 id=&#34;oss-as-critical-infrastructure&#34;&gt;OSS as critical infrastructure&lt;/h4&gt;
&lt;p&gt;Walking between sessions, another theme emerged: open source as critical infrastructure.&lt;/p&gt;
&lt;p&gt;Talks on digital public goods and civic technology painted OSS as globally essential, powering research labs, public services, and everyday tools. It was inspiring to see OSS spoken about in the same breath as utilities we rely on. But it was also sobering. With recognition comes responsibility: How do we maintain stability? How do we sustain it?&lt;/p&gt;
&lt;p&gt;The answers weren’t simple. Funding models. Licensing debates. Contribution infrastructure. Borrowing practices from the proprietary tech world. No silver bullet, just a collective willingness to wrestle with the complexity.&lt;/p&gt;
&lt;h4 id=&#34;inclusion-and-non-code-contributions&#34;&gt;Inclusion and non-code contributions&lt;/h4&gt;
&lt;p&gt;Some of the most powerful conversations weren’t about code at all.&lt;/p&gt;
&lt;p&gt;For instance, Imma Valls from Grafana Labs gave a talk, “Understanding the Need for Systemic Change in Open Source Through Intersectionality.” What started as a presentation on gender disparities became an open-floor discussion. People spoke candidly about their experiences, their frustrations, and their hopes for change.&lt;/p&gt;
&lt;p&gt;It flowed naturally into my own talk: “The Secret Lives of OSS Design Contributors.” I spoke about how design can bring accessibility and usability into OSS, and how projects can make space for that. The response was energizing. Attendees connected it to their own realities: maintainers juggling multiple hats, contributors trying to make tools usable beyond tight developer circles. That mix of perspectives felt like the best of OSS: conversations that challenge, expand, and connect.&lt;/p&gt;
&lt;h4 id=&#34;the-value-of-variety&#34;&gt;The value of variety &lt;/h4&gt;
&lt;p&gt;Over coffee breaks and hallway chats, I kept hearing the same thing: projects want varied contributions, as long as they’re useful and relevant.&lt;/p&gt;
&lt;p&gt;Companies building OSS tools told me they’re actively looking to involve designers. For them, it’s not about ticking boxes. It’s about setting up users for success, from hiring designers or supporting community contributors. Either way, design isn’t optional; it’s key to usability and growth.&lt;/p&gt;
&lt;h4 id=&#34;community-days-learning-in-action&#34;&gt;Community days: learning in action&lt;/h4&gt;
&lt;p&gt;After the main summit wrapped, I joined the Open SSF Community Day. I half-expected to feel out of place in a security-heavy crowd. Instead, I was met with an unexpected energy. People introduced me to those shaping attestations and other security practices. I even got to share some of my own UI/UX work and gather direct feedback.&lt;/p&gt;
&lt;p&gt;That day underscored the value of these community spaces. They’re not just deep dives into niche topics. They’re spaces for cross-pollination. Security meets design. Research meets development. Ideas flow in ways they can’t during formal sessions.&lt;/p&gt;
&lt;h4 id=&#34;final-reflections&#34;&gt;Final reflections&lt;/h4&gt;
&lt;p&gt;By the end of the week, one truth became clear for me: design belongs in open source. Not as an afterthought, not as polish layered on top, but as a core contribution shaping usability, accessibility, and sustainability.&lt;/p&gt;
&lt;p&gt;What struck me most was how open people were to that message. Whether in supply chain sessions, inclusion talks, or community days, the response was the same: OSS thrives when skills mix.&lt;/p&gt;
&lt;p&gt;I left the summit feeling more connected, more informed, and more hopeful. Designers may still be a minority in OSS spaces, but moments like these prove our perspectives matter, and that the OSS community is ready to listen.&lt;/p&gt;
&lt;div style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
      &lt;iframe allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen&#34; loading=&#34;eager&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; src=&#34;https://www.youtube.com/embed/ZdFID6ViKHo?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0&#34; style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; title=&#34;YouTube video&#34;&gt;&lt;/iframe&gt;
    &lt;/div&gt;

</description>
    </item>
    
    <item>
      <title> Sustain Africa</title>
      <link>https://superbloom.design/community/events/sustain-africa/</link>
      <pubDate>Wed, 22 Oct 2025 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/events/sustain-africa/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Sustaining Open Source Design: Reflections from Sustain Africa</title>
      <link>https://superbloom.design/learning/blog/sustaining-open-source-design-reflections-from-sustain-africa/</link>
      <pubDate>Tue, 21 Oct 2025 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/sustaining-open-source-design-reflections-from-sustain-africa/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_sustain_blog_white_hu_658a799b4c9b1099.png&#34; alt=&#34;White image of the letters OS where the centre of the &amp;lsquo;o&amp;rsquo; is an outline of the map of Africa&#34; width=&#34;740&#34; height=&#34;350&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;background&#34;&gt;Background&lt;/h4&gt;
&lt;p&gt;The Sustain Africa event is a one-day unconference held at the OSCA Festival, a huge open source conference hosted by the Open Source Community Africa (OSCA). It brings together builders and users of open source projects to discuss key aspects of OSS, including design, governance, web development, and maintainer burnout. As a designer, I found the conversations on sustaining OSS design really valuable.&lt;/p&gt;
&lt;p&gt;Some open source organizations like CHOASS, Gnome, and Nextcloud have tried to prioritize design and have made efforts to push design contributions and make designers visible, yet compared to other aspects of open source contributions, design remains hidden in the ecosystem. We discussed how this is evident in the allocation of grants, where a smaller number is given for the maintenance of design or dedicated-design programs. This year’s discussions explored in greater depth how we can sustain OSS design as contributors, how African designers can leverage contributions as a pathway for growth, and how projects can articulate their design needs and document processes in a way that promotes the development of the community and projects. Listening to participants, I reflected on the challenges of trust, sustainability, and visibility for design contributors, issues that resonate globally.&lt;/p&gt;
&lt;h4 id=&#34;what-do-people-think-oss-design-is&#34;&gt;What do people think OSS design is?&lt;/h4&gt;
&lt;p&gt;One key question was: What do we think OSS design is?&lt;/p&gt;
&lt;p&gt;The answers varied: some saw it as designing assets, such as icons, buttons, and layouts, while others defined it as applying open and collaborative OSS principles to design. More experienced contributors expanded it to include shaping user experiences beyond interfaces, that is, onboarding, documentation structures, and even how a community is governed.&lt;/p&gt;
&lt;p&gt;If design is viewed solely as UI, contributors with research or strategy skills may be overlooked. A broader framing positions design as a bridge between users, maintainers, and developers. It also highlights unique challenges in a design context—the complexity of tools, differences in technical skill, and language barriers. We define OSS design in this way to ensure we are part of the global conversation and can shape how design is practiced worldwide.&lt;/p&gt;
&lt;h4 id=&#34;sustaining-oss-design&#34;&gt;Sustaining OSS design&lt;/h4&gt;
&lt;p&gt;Sustainability requires more than one-off design contributions. Design work must be thoroughly documented and treated as integral to projects.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Education is foundational. Many Africans are introduced to OSS through talks and articles, but a deeper understanding of the space requires in-depth education. Although GitHub and Linux provide resources, design education often falls short because programs tend to prioritize technical skills over design principles.&lt;/li&gt;
&lt;li&gt;Sustaining OSS design also means recognizing that research, prototyping, and usability testing need resources. Without funding, contributors burn out. Financial support not only helps designers but also strengthens overall project development.&lt;/li&gt;
&lt;li&gt;Documentation is another challenge. README files rarely include design information, as many technical writers, though talented, may not be able to fully document a design process, except they are designers themselves or have a design background. Assigning designers to collaborate, set up, and maintain these assets ensures clarity and consistency. Find a designer who can document design or train a designer to document design. &lt;/li&gt;
&lt;li&gt;Integration matters too. Too often, design conversations are scattered across external tools or private chats. When design discussions are integrated into platforms like GitHub Discussions, GitLab issues, and mailing lists, contributors can trace the history and access conversations. While some projects hesitate to add this layer, fearing disruption, it is key for continuity.&lt;/li&gt;
&lt;li&gt;Finally, mentorship is lacking. Developers often have maintainers or senior guides, while designers lack role models in OSS. Without senior contributors to mentor, knowledge sharing and sustainability suffer. Building mentorship is essential for long-term design growth.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;the-oss-playbook-community-vs-core-trust&#34;&gt;The OSS playbook: community vs. core trust&lt;/h4&gt;
&lt;p&gt;Another theme discussed was the need for a playbook or widely accepted documentation from the OSS design community. Such a resource could help projects define design direction and avoid treating design as an outsourced, one-off effort.&lt;/p&gt;
&lt;p&gt;This raised questions of trust. Are design contributors seen as collaborators or just surface fixers? If communities limit design to polishing interfaces, we are reproducing closed practices within spaces that claim openness. Including design voices early reshapes trust dynamics and ensures access and influence.&lt;/p&gt;
&lt;h4 id=&#34;pathways-for-contributors-to-grow-in-design&#34;&gt;Pathways for contributors to grow in design&lt;/h4&gt;
&lt;p&gt;A major frustration is the lack of visible pathways for designers in OSS. Developers often move from beginner issues to maintainer roles, but designers rarely see progression or leadership opportunities.&lt;/p&gt;
&lt;p&gt;Participants explored what growth pathways could look like. Visibility was a recurring theme: contributors need platforms to showcase their work through blogs, portfolios, or community highlights. Recognition motivates designers and helps them translate contributions into career opportunities. Without visibility and pathways, talented designers remain on the sidelines, unable to shape the ecosystems they support.&lt;/p&gt;
&lt;h4 id=&#34;improving-design-contributions-in-open-source&#34;&gt;Improving design contributions in open source&lt;/h4&gt;
&lt;p&gt;We discussed practical ways to improve design contributions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Automation reduces repetitive tasks and lowers the risk for newcomers.&lt;/li&gt;
&lt;li&gt;Templates provide structure for design changes and ensure uniformity in contributions.&lt;/li&gt;
&lt;li&gt;Clear documentation helps new contributors understand standards and processes, making design more transparent.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These processes make design contributions less intimidating and more impactful.&lt;/p&gt;
&lt;h4 id=&#34;keeping-the-conversation-alive&#34;&gt;Keeping the conversation alive&lt;/h4&gt;
&lt;p&gt;At the end of the session, I felt a renewed commitment to the OSS design community in Africa. We have a unique opportunity to shape the future of OSS design by investing in education, funding, mentorship, and documentation. Sustaining design isn’t only about technical fixes—it’s a cultural shift toward openness, recognition, and collaboration.&lt;/p&gt;
&lt;p&gt;The OSCA Festival may have ended, but the conversations must continue. As OSS advocates, we have both the responsibility and the opportunity to influence the next chapter of open source design globally.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Do’s and Don’ts for Visual Storytelling in Sensitive Scenarios</title>
      <link>https://superbloom.design/learning/resources/dos-and-donts-for-visual-storytelling-in-sensitive-scenarios/</link>
      <pubDate>Mon, 15 Sep 2025 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/dos-and-donts-for-visual-storytelling-in-sensitive-scenarios/</guid>
      <description>&lt;p&gt;The images you use matters to your audience. To help brands choose visuals with sensitivity and respect, we’ve created a &lt;a href=&#34;https://miro.com/app/board/uXjVLBlTwlA=/&#34;&gt;Miro board&lt;/a&gt; showing the do’s and don’ts for various scenarios that impact marginalized genders and identities.&lt;/p&gt;
&lt;p&gt;It covers a range of scenarios from war to revenge porn, gun violence, stalking and more. This is a resource for anyone seeking to create visual design that truly resonates with marginalized genders and the potentially tough topics that interest them.&lt;/p&gt;
&lt;p&gt;This practical resource was shaped with real community input.&lt;/p&gt;
&lt;p&gt;Inside, you’ll discover:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Key topics and tough scenarios requiring thoughtful image selection.&lt;/li&gt;
&lt;li&gt;Guidance on tone and pacing to prevent harm and foster empathy.&lt;/li&gt;
&lt;li&gt;Tips for communicating authentically and inclusively.&lt;/li&gt;
&lt;li&gt;Avoid common pitfalls—explore the board.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Y﻿ou can find &lt;a href=&#34;https://drive.google.com/file/d/1goyrZkSzVaKmTIfjjCpVwBE746cQeYwJ/view?usp=drive_link&#34;&gt;a PDF of the Miro board here&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;disclaimer&#34;&gt;Disclaimer&lt;/h4&gt;
&lt;p&gt;The images collected in the ‘ok’ and ‘bad’ examples don’t mean these are ‘ok’ and ‘bad’ designs or images, it means they are more likely to be upsetting when seen in context of ‘marginalised genders and identities using secure and private communication technology, based off our user research with marginalised genders and identities. In certain cases, creating ‘upsetting’ imagery may be the point/focus of a design/image.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Why Defining Gender Diversity Matters to Your Brand — and the Challenges You May Face</title>
      <link>https://superbloom.design/learning/blog/why-defining-gender-diversity-matters-to-your-brand--and-the-challenges-you-may-face/</link>
      <pubDate>Mon, 18 Aug 2025 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/why-defining-gender-diversity-matters-to-your-brand--and-the-challenges-you-may-face/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_butterfly_messages_hu_6d7fe46458e367e8.png&#34; alt=&#34;Image of two mobile phones with hands coming out of them pointing at one another with a butterfly on the index finger. Left hand phone with purple phone and butterfly. Right hand in green.&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;p&gt;At Superbloom, clients often are curious about audience and how to reach people beyond the usual suspect for an app or tool. Most recently, we were approached by a client who asked a vital question with real implications: How can our tool and brand better appeal to marginalized genders and identities? It&amp;rsquo;s a question more organizations should be asking — especially those building tools meant to empower or protect users, such as privacy-focused software. But as simple as the question sounds, answering it—and acting on it—requires a deliberate, often uncomfortable reckoning.&lt;/p&gt;
&lt;p&gt;Before we could begin designing for inclusion we needed to address a foundational issue we encounter often in the tech world: many tools are originally built for majority audiences—most commonly, men with a high degree of technical fluency. Unsurprisingly, this history shapes everything: product features, tone, visual language, even how user trust is earned. When these systems attempt to pivot toward inclusion without reevaluating their assumptions or defining their strategy clearly, they often fall short. That’s because diversity can’t be retrofitted around a default — and certainly not when that default is exclusionary from the start.&lt;/p&gt;
&lt;h4 id=&#34;the-fallacy-of-broad-appeal&#34;&gt;The fallacy of “broad appeal” &lt;/h4&gt;
&lt;p&gt;Time and time again, we hear clients say: “We just want to appeal more broadly.” While well-intentioned, this type of wishful thinking is ultimately ineffective and even risky. Without specificity, efforts to engage with marginalized genders and identities tend to default into the vague—and the vague is almost always a re-centering of the dominant group.&lt;/p&gt;
&lt;p&gt;Take, for example, the vague catch-all term “marginalized genders.” Too often, this label is treated as an umbrella that includes “everyone who isn’t a tech-bro,” a definition that over-simplifies, erases nuance, and reinforces the norms marginalized individuals are already pushing against. Worse still, it sustains harmful hierarchies by positioning those users as deviations from the imagined “typical” user — male, cisgender, and highly technical.&lt;/p&gt;
&lt;p&gt;Effective, respectful design begins with clarity. Who are we really talking about? Which identities, lived experiences, and cultural contexts are we centering? What does trust look like for them? What past harms must we be mindful not to repeat?&lt;/p&gt;
&lt;h4 id=&#34;why-this-process-is-hard--and-necessary&#34;&gt;Why this process is hard — and necessary &lt;/h4&gt;
&lt;p&gt;Clarifying these definitions isn’t just a semantic exercise; it can be organizationally and emotionally uncomfortable. It requires brands to step out of autopilot mode — to challenge internal assumptions and recognize gaps in team knowledge, systems, and design approaches. It can bring teams face-to-face with blind spots they didn’t know they had.&lt;/p&gt;
&lt;p&gt;For our client, this process can mean shifting from a broad, undefined concern about diversity to a deeper interrogation: Who exactly are we doing this for?&lt;/p&gt;
&lt;p&gt;To guide our user research and shape our design direction, we collaboratively defined what we meant when we spoke of gender diversity. Not a monolith — but a spectrum of experiences, sensibilities, and social contexts that deserved acknowledgment in specifics.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_pixel-butterfly-3_hu_984571e10c3d1e09.png&#34; alt=&#34;Image of three dark purple butterflies side by side morphing from left to right - image to pixelated image&#34; width=&#34;740&#34; height=&#34;252&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;our-working-definition-of-gender-diverse-users&#34;&gt;Our working definition of gender-diverse users &lt;/h4&gt;
&lt;p&gt;To design with intention and empathy, we developed the following working definition for our team:&lt;/p&gt;
&lt;h4 id=&#34;who-we-mean-by-gender-diverse&#34;&gt;Who we mean by gender diverse&lt;/h4&gt;
&lt;p&gt;Individuals who identify as: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Femme-presenting&lt;/li&gt;
&lt;li&gt;Man (not cisgender)&lt;/li&gt;
&lt;li&gt;Woman (cis and trans)&lt;/li&gt;
&lt;li&gt;Transgender&lt;/li&gt;
&lt;li&gt;Non-binary&lt;/li&gt;
&lt;li&gt;Gender-fluid&lt;/li&gt;
&lt;li&gt;Gender-queer&lt;/li&gt;
&lt;li&gt;Androgyne&lt;/li&gt;
&lt;/ul&gt;
&lt;h5 id=&#34;they-have-often-experienced&#34;&gt;They have often experienced: &lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;Discrimination, exclusion, and “othering”&lt;/li&gt;
&lt;li&gt;A lack of visible role models&lt;/li&gt;
&lt;li&gt;Misrepresentation in technology and media &lt;/li&gt;
&lt;li&gt;Hate or backlash from groups like incels&lt;/li&gt;
&lt;li&gt;The need to mask or hide their identities&lt;/li&gt;
&lt;/ul&gt;
&lt;h5 id=&#34;theyve-also-found-strength-in&#34;&gt;They’ve also found strength in:&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;Community (online and offline)&lt;/li&gt;
&lt;li&gt;Inclusive spaces&lt;/li&gt;
&lt;li&gt;Activism, collaboration, and mutual support&lt;/li&gt;
&lt;li&gt;Strong social networks and alternative structures of connection&lt;/li&gt;
&lt;/ul&gt;
&lt;h5 id=&#34;their-behavior-around-privacy-tools-varies&#34;&gt;Their behavior around privacy tools varies:&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;Some use them actively&lt;/li&gt;
&lt;li&gt;Some wish to but haven’t started&lt;/li&gt;
&lt;li&gt;Some avoid them intentionally&lt;/li&gt;
&lt;li&gt;Some choose not to for personal or systemic reasons&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Understanding this range allowed us to pinpoint whom we should prioritize in research, how to create inclusive design strategies, and how to avoid tokenism or generalizations . Without such grounding, there’s too great a risk of flattening experiences and missing the point entirely.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_pixel-butterfly-4-2-_hu_c4f3c873445e2e33.png&#34; alt=&#34;Image of three light purple butterflies side by side morphing from left to right - image to pixelated image&#34; width=&#34;740&#34; height=&#34;265&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;why-definitions-make-brands-stronger--not-weaker&#34;&gt;Why definitions make brands stronger — not weaker &lt;/h4&gt;
&lt;p&gt;It’s natural to fear that narrowing your scope will limit your reach. But from Superbloom’s experience, the opposite is true: By meeting a specific community with specificity, you demonstrate integrity, depth, and real commitment.&lt;/p&gt;
&lt;p&gt;Brands that say “we welcome everyone” but sidestep the hard work of clearly defining who everyone means often foster exclusion by default. A vague welcome is no welcome at all. And in industries where gender-diverse individuals have historically been pushed out or ignored, this approach feels like more of the same.&lt;/p&gt;
&lt;p&gt;When brands get intentional about speaking directly to historically marginalized users, they don’t exclude the majority users—they just stop over-prioritizing them. They stop designing only for one type of user and instead allow room for multiple histories, values, and ways of connecting.&lt;/p&gt;
&lt;h4 id=&#34;the-takeaway&#34;&gt;The takeaway&lt;/h4&gt;
&lt;p&gt;Designing for marginalized genders and identities is not about checking a box. It’s about stretching your organization’s values to meet the real diversity of lived experience with clarity and respect. The first step? Say what you mean. Define who you’re designing for, and involve them meaningfully. Yes, it might force some uncomfortable conversations. But it will spark the kind of growth that makes your product—and your brand—more relevant, more just, and more human.&lt;/p&gt;
&lt;p&gt;Want to learn more about how to create truly inclusive, user-centered design strategies? We’d love to talk! Get in touch: &lt;a href=&#34;mailto:contact@superbloom.design&#34;&gt;contact@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;credits&#34;&gt;C﻿redits&lt;/h4&gt;
&lt;p&gt;W﻿ith thanks to &lt;a href=&#34;https://www.opentech.fund/labs/impact-engagement-lab/&#34;&gt;Open Technology Fund Impact &amp;amp; Engagement Lab&lt;/a&gt; (formerly Learning lab) for supporting this work.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Feature Guide for High-Risk Contexts (2025)</title>
      <link>https://superbloom.design/learning/blog/feature-guide-for-high-risk-contexts-2025/</link>
      <pubDate>Fri, 21 Feb 2025 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/feature-guide-for-high-risk-contexts-2025/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_feature_guide_for_high-risk_contexts_-2025_edition-_hu_ec2d4947bc4564b9.png&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;If you’re creating technology in 2025, take a hint from the feature wish lists of activists, journalists, and human rights defenders. Here’s our 2025 guide to what you should consider including in every tech tool and why.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This guide helps designers and developers adapt tech tools for high-risk contexts. &lt;/p&gt;
&lt;p&gt;Whether you design specialized tools for high-risk contexts, or you want to create adaptable, resilient technology that can flex with different levels of risk, this list is for you. At Superbloom, our goal is to use design to help improve both types of technology. Specialized apps need to be usable in order to fulfil their promise of security; everyday apps should take higher-risk environments into account. &lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/Superboom_Design_Feature_Guide_for_High_Risk_Contexts.pdf&#34;&gt;Our Feature Guide for High-Risk Contexts&lt;/a&gt; is a selection of security and privacy features that people in high-risk contexts have brought up in our research projects from 2018 to 2024. Additionally, we hosted a workshop with other designers and tool builders in the space (and hope to host more soon). We identified a menu of features that we divided into five categories:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Features that disguise help people hide their use of a tool.&lt;/li&gt;
&lt;li&gt;Features that delete help people minimize data or easily make their data go away. &lt;/li&gt;
&lt;li&gt;Features that educate give people hints and reminders relevant to privacy and security.&lt;/li&gt;
&lt;li&gt;Features that welcome make a tool pleasant and straightforward to use.&lt;/li&gt;
&lt;li&gt;Features that support social dynamics let people use the group structures and roles that work best for them.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;our-high-risk-design-approach&#34;&gt;Our high-risk design approach&lt;/h4&gt;
&lt;p&gt;We are all at risk when participating in the modern technology ecosystem: it is powered by monetizing user data, with an experience splintered by microtargeting and governed by opaque corporate policies. &lt;/p&gt;
&lt;p&gt;However, some environments and interactions are especially risky. People in these contexts are particularly helpful to learn from, since they often have already spent time thinking about the features, protections, and mitigations they need from their technology. &lt;/p&gt;
&lt;p&gt;We are grateful to many activists, journalists, and human rights defenders from all over the world for sharing their do’s and don’ts with us, their wish lists and wisdom. The strategies they use and the reality of their day-to-day tech use inform our approach to design: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Strengthen both specialized and everyday tools.&lt;/li&gt;
&lt;li&gt;Avoid interfering with users’ own risk-mitigation strategies.&lt;/li&gt;
&lt;li&gt;Offer protective features that empower users without restricting them.&lt;/li&gt;
&lt;li&gt;Adapt to real-world usage patterns and evolving threats.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;high-risk-features-are-for-everybody&#34;&gt;High-risk features are for everybody&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/Superboom_Design_Feature_Guide_for_High_Risk_Contexts.pdf&#34;&gt;Our feature guide&lt;/a&gt; comes from interviews we conducted between 2018 and 2024 with people who are using technology in high-risk contexts. But given economic and geopolitical trends in 2025, these features will be helpful to everyone at some point. Risk is layered and shifts over time; factors as diverse as identity, government and corporate policies, and personal circumstances all determine how vulnerable a particular person is, at what time, and to what threats. If you have ever switched from Facebook Messenger to Signal, if you have ever closed Chrome and opened Tor, or if you have ever lowered your voice in a café, you have experienced how risk can shift based on context. At Superbloom, we want technology to support shifts in the risk landscape.&lt;/p&gt;
&lt;p&gt;So, no matter what kind of technology you are working on, no matter who you expect will be using it, &lt;a href=&#34;https://superbloom.design/learning/resources/Superboom_Design_Feature_Guide_for_High_Risk_Contexts.pdf&#34;&gt;check out the 2025 edition of this feature guide&lt;/a&gt;. There’s a good chance some of these features make sense for you to include. &lt;/p&gt;
&lt;p&gt;If you see something missing, please let us know. Even better, if you would like to take part in a mini-workshop to update and expand the list, reach out to us! We find that group settings work particularly well for exchanging this type of information. Write to us at &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;further-resources&#34;&gt;Further resources&lt;/h4&gt;
&lt;p&gt;For a more holistic approach that integrates accessibility and usability, see Superbloom’s &lt;a href=&#34;https://superbloom.design/learning/resources/user-experience-toolbox-for-risk-mitigation-and-accessibility/&#34;&gt;User Experience Toolbox for Risk Mitigation and Accessibility&lt;/a&gt;. It contains a wealth of higher-level resources to inform your overall process and philosophy.&lt;/p&gt;
&lt;p&gt;Profiles:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/persona-non-grata/&#34;&gt;Personas Non Grata&lt;/a&gt;, a collection of adversary types by Superbloom.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://usable.tools/personas/&#34;&gt;Profiles of high-risk users&lt;/a&gt;, part of the USABLE project by Internews. &lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://usable.tools/adversaries/&#34;&gt;Profiles of adversaries&lt;/a&gt;, part of the USABLE project by Internews. &lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://usable.tools/organizations/&#34;&gt;Profiles of high-risk organizations&lt;/a&gt;, part of the USABLE project by Internews.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Libraries of interface-level suggestions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;Decentralization Off the Shelf (DOTS): a design pattern library for usable decentralization&lt;/a&gt;, by Superbloom and others. For apps with decentralized structures.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://catalogue.projectsbyif.com/&#34;&gt;Trustworthy Design patterns for digital services&lt;/a&gt;, by Projects by If.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href=&#34;https://developer.android.com/privacy-and-security/security-best-practices&#34;&gt;Android Security Best Practices&lt;/a&gt;, by Google. Aimed at developers, but also relevant at the UI level.&lt;/strong&gt;&lt;/p&gt;
&lt;h4 id=&#34;credits&#34;&gt;Credits&lt;/h4&gt;
&lt;p&gt;T﻿his blog was written by Molly Wilson. Report by Molly Wilson and Katie Wilson.&lt;/p&gt;
&lt;p&gt;With thanks to &lt;a href=&#34;https://www.opentech.fund/labs/uxd-lab/&#34;&gt;Open Technology Fund User Experience &amp;amp; Discovery Lab&lt;/a&gt;f﻿or supporting this work.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>High Risk Contexts</title>
      <link>https://superbloom.design/learning/collections/high-risk-contexts/</link>
      <pubDate>Fri, 21 Feb 2025 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/collections/high-risk-contexts/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Report Launch:Design for Internet Shutdowns in Taiwan. Taxi Drivers, Satellites, and Tech: The Surprising Heroes in Taiwan&#39;s Fight Against Internet Shutdowns</title>
      <link>https://superbloom.design/learning/blog/report-launch-design-for-internet-shutdowns-in-taiwan-taxi-drivers-satellites-and-tech-the-surprising-heroes-in-taiwans-fight-against-internet-shutdowns/</link>
      <pubDate>Fri, 21 Feb 2025 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/report-launch-design-for-internet-shutdowns-in-taiwan-taxi-drivers-satellites-and-tech-the-surprising-heroes-in-taiwans-fight-against-internet-shutdowns/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom_design_design_for_internet_shutdowns_in_taiwan_report_image_1_hu_e15b7ad37e4f96c9.png&#34; alt=&#34;Image alt text: A stylised illustration of 4 people holding devices, speaking with each other with other technology and internet/web imagery surrounding them like routers, microphones and browser frames. There are sticky notes and paper clips in the background and silhouette hands holding smart phones, tape recorders and floppy disks. The people have various Taiwanese cultural symbols on them such as flag hats, vegetable bags and charm necklaces. Find out more about this image by reading the documentation by the artist, Vico Yang on Github here. This image is under the license Creative Commons Zero v1.0 Universal.&#34; width=&#34;740&#34; height=&#34;524&#34;&gt;
&lt;/p&gt;
&lt;h1 id=&#34;開源設計工作坊-捍衛台灣網路中斷無名英雄-計程車司機衛星和科技&#34;&gt;開源設計工作坊-捍衛台灣網路中斷無名英雄-計程車司機、衛星和科技&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Superbloom is delighted to launch its report, resources, documentation and open source artworks focussing on the Design for Internet Shutdowns OSS Technology workshops at COSCUP 2023. This report has insights into how designers practice in OSS, how Taiwanese and South East Asian citizens view critical internet shutdowns and censorship circumvention topics and a framework for running similar workshops for OSS anywhere in the world.&lt;/strong&gt;&lt;/p&gt;
&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;Superbloom is invested in how design, and design processes are improved, sustained and made more accessible worldwide in internet freedom open source software. This is not only achieved through direct interventions and a design procurement process for OSS projects that are fortunate enough to fund the hiring of designers or design agencies, but achieved through investment in design communities, OSS communities and internet freedom communities. We practise design as a method of bringing together these three stakeholder groups. In order to improve internet freedom OSS as a whole.&lt;/p&gt;
&lt;p&gt;This report stresses the importance of bringing together:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Designers that know how the internet freedom OSS space works.&lt;/li&gt;
&lt;li&gt;Designers with citizen and cultural context who want to contribute to improve internet freedom.&lt;/li&gt;
&lt;li&gt;Internet freedom OSS tool maintainers and developers being included in user centred design processes.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;By bringing these stakeholders together and iterating on usable and useful resources is critical in better understanding how internet freedom OSS gains improved and sustainable access to designers and user centred design methods. &lt;/p&gt;
&lt;p&gt;You can read more about what we did at the &lt;a href=&#34;https://superbloom.design/learning/blog/open-design-workshop-at-coscup-2023-understanding-internet-shutdowns-and-how-design-can-improve-tools/&#34;&gt;COSCUP 2023 workshop in our blog&lt;/a&gt;, and at the &lt;a href=&#34;https://superbloom.design/learning/blog/design-contributions-to-oss-at-coscup-2024/&#34;&gt;COSCUP 2024 workshop in this blog&lt;/a&gt;. Most but not all sections have both English and Mandarin language available.&lt;/p&gt;
&lt;h4 id=&#34;the-importance-of-design-for-internet-freedom-oss-and-the-taiwanese-perspective&#34;&gt;The importance of design for internet freedom OSS and the Taiwanese perspective&lt;/h4&gt;
&lt;p&gt;In the first section of the report (viewable as &lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open/tree/main/Documenting%20Internet%20Shutdowns%20Workshop/1-introduction&#34;&gt;individual text files on GitHub&lt;/a&gt; here or at the beginning of both the &lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open/blob/main/Documenting%20Internet%20Shutdowns%20Workshop/No%20executive%20summary%20-%20of%20Design%20for%20Internet%20Shutdowns%20in%20Taiwan%20-%20Report%20(en%20%26%20cn).pdf&#34;&gt;pdf files&lt;/a&gt; and the &lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open/blob/main/Documenting%20Internet%20Shutdowns%20Workshop/design-for-internet-shutdowns-in-taiwan-report-en-cn.md&#34;&gt;text files&lt;/a&gt; on the &lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open/tree/main/Documenting%20Internet%20Shutdowns%20Workshop&#34;&gt;GitHub repository&lt;/a&gt;) we explore three framing topics:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Why design and designers are important for internet freedom OSS &lt;/li&gt;
&lt;li&gt;Why COSCUP is an important event for internet freedom OSS&lt;/li&gt;
&lt;li&gt;Taiwan&amp;rsquo;s relationship to internet freedom and OSS&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In these introductory chapters we explore the statements of activists, journalists and internet freedom tool users when they speak to the user experiences of these tools, with comments such as:&lt;/p&gt;
&lt;p&gt;“Well I use these tools for my journalism reporting but, honestly I still use big tech’s communication tools too, even though I know it’s risky, they are easier to use and my family won’t switch to secure tools.”&lt;/p&gt;
&lt;p&gt;As designers, when we hear these statements from users, alarm bells ring about how the usability of these tools fails to meet the needs of those using them. Though these are the comments and statements that we are able to culturally and contextually understand. There are many more circumstances and situations that only designers with specific localised citizen based knowledge can address. The importance of COSCUP as a catalyst event for OSS in Taiwan, and better understanding the relationship that Taiwanese citizens have towards internet freedom topics such as internet shutdowns, censorship, misinformation, disinformation and internet scams are paramount.&lt;/p&gt;
&lt;h4 id=&#34;the-workshop-framework&#34;&gt;The workshop framework&lt;/h4&gt;
&lt;p&gt;Superbloom has tested many workshop frameworks, activities and resources over the years for different and diverse audiences. This 2023 iteration of the workshop is intended to focus on design methods and skills and applying them to the internet freedom OSS tool space. As such, the workshop is structured into five sections: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Introduction, safety, goals and team formation&lt;/li&gt;
&lt;li&gt;Tool landscape and understanding goals of internet freedom OSS&lt;/li&gt;
&lt;li&gt;User research Insights and practice scenarios&lt;/li&gt;
&lt;li&gt;Design activities: Personas, User Journeys, User Scenarios and Ideation&lt;/li&gt;
&lt;li&gt;Documentation and feedback opportunities&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This framework empowers designers to take the lead and centers users through those activities and opportunities for investigation. This process can allow for non-designers, developers and tool maintainers to learn and practice design in a supportive and encouraging environment and gives them the opportunity to focus on users and explore scenarios and journeys without being held back by technical requirements and possibilities.&lt;/p&gt;
&lt;p&gt;This workshop specifically allowed for designers to explore the motivations and journeys of activists and users of internet freedom OSS and add their Taiwanese and South East Asian citizen perspectives. By stepping back from what any existing internet freedom OSS currently ‘want’ to develop, the user journeys and technology ideas were able to ground themselves in the Taiwanese lived experience.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open/blob/main/Documenting%20Internet%20Shutdowns%20Workshop/design-for-internet-shutdowns-in-taiwan-report-en-cn.md#workshop-methods-and-processes--%E5%B7%A5%E4%BD%9C%E5%9D%8A%E7%9A%84%E6%96%B9%E6%B3%95%E5%92%8C%E9%81%8E%E7%A8%8B&#34;&gt;Read the workshop framework here&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom_design_design_for_internet_shutdowns_in_taiwan_report_image_2_hu_71e41b87acd4bc6a.png&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;insights-into-taiwanese-designers-solutions-for-internet-freedom-challenges&#34;&gt;Insights into Taiwanese designers&amp;rsquo; solutions for internet freedom challenges&lt;/h4&gt;
&lt;p&gt;After the workshop was completed, Superbloom staff and our partners undertook user interviews with the workshop participants to better understand each team’s user journey and which led them to create their chosen solutions. &lt;/p&gt;
&lt;p&gt;The teams all picked their own persona and their own user journeys/scenarios and found a moment in those journeys where a technological intervention could be made in order to create a better outcome for the user in an internet shutdown or other human rights circumstance. All teams came up with a Taiwanese scenario and solution grounded in the existing infrastructures and realities of Taiwan and its citizens.&lt;/p&gt;
&lt;p&gt;By interviewing the workshop participants we were able to ask questions about these solutions that we were not able to achieve in the one day workshop. We were able to dig deeper into the choices made by teams and how that was connected to specific internet freedom issues in Taiwan. We were also able to better understand how designers, most of whom had never interacted with OSS technology or internet freedom technology as configurers, and only as potential users, felt about engaging with design improvements to these OSS technologies and how they need to feel more empowered to be able to contribute outside of supported workshop spaces.&lt;/p&gt;
&lt;p&gt;The solutions the teams - all named after group members&amp;rsquo; favourite foods - came up with ranged from the analogue to the interconnected:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ideas around how taxi drivers in Taiwan can help to move critical verified information around a city in times of misinformation as well as people who are seeking safety in crisis. &lt;/li&gt;
&lt;li&gt;Utilising 7-11 convenience stores as hubs for connectivity and verified information via QR codes. &lt;/li&gt;
&lt;li&gt;Understanding how information puts journalists and publishing researchers at risk when they want to ensure citizens have the most accurate information in times of national crisis and how they might utilize systems of limited connection and satellites to communicate as they attempt to leave the country.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open/blob/main/Documenting%20Internet%20Shutdowns%20Workshop/design-for-internet-shutdowns-in-taiwan-report-en-cn.md#workshop-team-solutions-and-designer-analysis--%E8%BB%8A%E9%96%93%E5%9C%98%E9%9A%8A%E8%A7%A3%E6%B1%BA%E6%96%B9%E6%A1%88%E5%8F%8A%E8%A8%AD%E8%A8%88%E5%B8%AB%E5%88%86%E6%9E%90&#34;&gt;Read the solutions here&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;h4 id=&#34;recommendations-design-workshops-for-internet-freedom-oss&#34;&gt;Recommendations: design workshops for internet freedom OSS&lt;/h4&gt;
&lt;p&gt;In this section Superbloom summarises a series of improvements to workshops of this nature. These recommendations were all informed by the participant interviews post workshop about what they aspired to see happen in subsequent workshops. Recommendations are written to be actionable steps for those looking to run their own workshops along similar themes or structures. &lt;/p&gt;
&lt;p&gt;The example below outlines the structure of recommendations:&lt;/p&gt;
&lt;p&gt;Recommendation #3 - including activists in workshops&lt;/p&gt;
&lt;p&gt;The presence of people with experience of human rights abuses and internet censorship/shutdowns is important to designers, technologists and OSS developers alike. When workshop participants get stuck on a particular point, question or circumstance they can look to the person with experiences to offer perspective and their own account. As an informational resource people with lived experience can quickly feel exploited and vulnerable when offering information and therefore we recommend the safest ways to involve these people possible be it remotely, funded in-person attendance and anonymous representation or representative information. We encourage offering access and further value to the activists or communities in the form of involvement in the OSS.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open/blob/main/Documenting%20Internet%20Shutdowns%20Workshop/design-for-internet-shutdowns-in-taiwan-report-en-cn.md#looking-ahead-post-workshop-feedback-and-improving-workshops&#34;&gt;Read the recommendations here&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;h4 id=&#34;positionalities-documentation-and-artwork&#34;&gt;Positionalities, documentation and artwork&lt;/h4&gt;
&lt;p&gt;Finally, those involved in the workshops offered positionality statements using a pseudonym. These give an insight into the hopes, aspirations, experiences and also some of the bias introduced when running a workshop. It’s important to remember that as people invested in the improvement of internet freedom, technology, design and OSS, as well as our own identity backgrounds (race, country of residence, gender etc) we bring our own selves into this work. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open/blob/main/Documenting%20Internet%20Shutdowns%20Workshop/design-for-internet-shutdowns-in-taiwan-report-en-cn.md#positionality-statements&#34;&gt;Read the positionality statements here.&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The documentation process is &lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open/blob/main/Documenting%20Internet%20Shutdowns%20Workshop/design-for-internet-shutdowns-in-taiwan-report-en-cn.md#oss-and-documentations-process&#34;&gt;described and referenced here&lt;/a&gt; in brief.&lt;/p&gt;
&lt;p&gt;As part of this work we worked with a Taiwanese graphic artist and illustrator who was part of the workshop herself. She was able to bring to life the workshop team solutions, visually representing these ideas and grounding them in Taiwanese culture. You can &lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open/blob/main/Documenting%20Internet%20Shutdowns%20Workshop/graphics%20and%20illustrations/visuals-and-graphics.md&#34;&gt;read more about the motivations behind each piece of artwork here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom_design_design_for_internet_shutdowns_in_taiwan_report_image_4_hu_542a4b4e6373414a.png&#34; width=&#34;740&#34; height=&#34;1048&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;what-next&#34;&gt;What next?&lt;/h4&gt;
&lt;p&gt;Superbloom continues to invest time and resources into bettering design for internet freedom OSS and cultivating and shepherding the design communities interested in OSS contributions. We’ll continue to run workshops that aim to iterate based on our informed recommendations where funding and support is available but we hope that these public resources empower designers to run workshops on contributing to OSS globally and we encourage you to add your insights, frameworks and resources.&lt;/p&gt;
&lt;p&gt;If you would like to discuss a design for internet freedom OSS workshop at your conferences or ask questions on the framework, we’d love to talk to you. Likewise, if you’d like to make a contribution, &lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open/tree/main&#34;&gt;fork the repository&lt;/a&gt; or translate this framework into another language we welcome your contributions. Get in touch!: &lt;a href=&#34;mailto:coaching@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;credits&#34;&gt;Credits&lt;/h4&gt;
&lt;p&gt;&lt;strong&gt;Blog post contributors:&lt;/strong&gt; Eriol Fox, Abhishek Sharma.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;With thanks to:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.opentech.fund/labs/learning-lab/&#34;&gt;Open Technology Fund Learning Lab&lt;/a&gt; for funding critical documentation and design related to internet freedom globally. &lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://coscup.org/2023/en/&#34;&gt;COSCUP&lt;/a&gt; for hosting and supporting design in OSS and the attendees and volunteers for the workshop that dedicated their time to making these workshops successful over 2023 and 2024.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.ixda.org.tw/&#34;&gt;IxDA Taiwan&lt;/a&gt; for supporting the local design community in the COSCUP 2023 workshop.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.linkedin.com/in/terry-wang&#34;&gt;Tofu Wang&lt;/a&gt; for translations of the documentation for 2024 COSCUP workshop.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.linkedin.com/in/liujulia/&#34;&gt;Julia Liu&lt;/a&gt; for project management across OSS workshops and this work and Mandarin translations.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://www.linkedin.com/in/vicoyang&#34;&gt;Vico Yang&lt;/a&gt; for the graphics and illustrations of this work.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Measuring the Privacy Experience</title>
      <link>https://superbloom.design/learning/blog/measuring-the-privacy-experience/</link>
      <pubDate>Thu, 20 Feb 2025 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/measuring-the-privacy-experience/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_measuring_the_privacy_experience_image_hu_c88e304a311a5426.png&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;How do you know that a product respects your privacy – other than by wading through the fine print? We’ve created a framework to measure the way people actually experience privacy in tech products.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;However, even where people’s privacy is protected by policy, they may not actually experience privacy. That’s where our Privacy Experience Heuristics come in. They list aspects of the end-user experience that bring people into contact with privacy policies. &lt;/p&gt;
&lt;p&gt;A product that performs better on the Privacy Experience Heuristics isn’t just doing a better job with privacy: it’s doing a better job in a way people will notice. Privacy Experience Heuristics takes privacy from being a technical compliance issue to becoming something people like and value about a product. &lt;/p&gt;
&lt;h4 id=&#34;guides-and-rankings-in-the-era-of-privacy-awareness&#34;&gt;Guides and rankings in the era of privacy awareness&lt;/h4&gt;
&lt;p&gt;GDPR reflects a global shift in people’s attitudes towards their personal data online. According to a &lt;a href=&#34;https://www.pewresearch.org/internet/2023/10/18/views-of-data-privacy-risks-personal-data-and-digital-privacy-laws/#personal-data-and-information&#34;&gt;2023 Pew Research report&lt;/a&gt;, 81% of Americans are concerned about how companies use their personal data. 73% of Americans say they have little to no control over the data that companies collect, and 67% say they have little to no knowledge of companies’ practices. According to a 2021 &lt;a href=&#34;https://blog.google/products/admanager/new-european-research-privacy-focused-future/&#34;&gt;Ipsos/Google report&lt;/a&gt;, 80% of people in Europe are concerned about the potential misuse of personal information online. The phenomenon isn’t confined to the US and EU. A &lt;a href=&#34;https://iapp.org/resources/article/privacy-and-consumer-trust-summary/&#34;&gt;2023 IAPP report&lt;/a&gt; stated that 68% of consumers globally are concerned about their online privacy.&lt;/p&gt;
&lt;p&gt;The average consumer will likely find it difficult to figure out which products respect data privacy. Stepping into the gap are civil society organizations that rank and score products based on their privacy practices. Resources such as &lt;a href=&#34;https://foundation.mozilla.org/en/privacynotincluded/&#34;&gt;Privacy Not Included&lt;/a&gt; (Mozilla), the scorecards from &lt;a href=&#34;https://rankingdigitalrights.org/&#34;&gt;Ranking Digital Rights&lt;/a&gt;, US organization &lt;a href=&#34;https://www.consumerreports.org/digital-security-privacy/&#34;&gt;Consumer Reports&amp;rsquo; privacy-focused guides&lt;/a&gt;, and in Germany, &lt;a href=&#34;https://www.test.de/thema/datenschutz-it-sicherheit/&#34;&gt;Stiftung Warentest&lt;/a&gt;, aim to assist consumers in making informed decisions based on the privacy practices of products and services. These guides not only help users identify products that prioritize privacy but also put market pressure on less privacy-conscious companies to improve their practices. &lt;/p&gt;
&lt;h4 id=&#34;privacy-experience-heuristics&#34;&gt;Privacy experience heuristics&lt;/h4&gt;
&lt;p&gt;A list of heuristics allows us to identify strengths and areas to improve. In this case, we’re evaluating the privacy features offered to people who use a tech product. This is not an evaluation of privacy practices, nor is it a legal compliance checklist: it’s a way to measure whether people can find, understand, and use privacy features.&lt;/p&gt;
&lt;p&gt;Third-party assessments spotlight current products that are doing privacy particularly well (and particularly badly), a major boon to readers doing comparison research before a purchase. But these rankings and assessments are not designed to be performed by the readers themselves. Another limitation of buyers’ guides: they report results, but rarely show how the product could have improved. We saw a need for a complementary tool, an open methodology that offers concrete examples of dos and don’ts: Privacy Experience Heuristics.&lt;/p&gt;
&lt;p&gt;Heuristic evaluation and benchmarking practices are a core part of the privacy professionals’ toolbox, both on the legal and technical sides of privacy. Privacy practices are defined in requirements, internal documentation and training, and internal policies. &lt;/p&gt;
&lt;p&gt;But most people outside the company don’t see any of this material. They only see the legal fine print – the privacy policy, the terms and conditions – and the options and text included into the product interface.&lt;/p&gt;
&lt;p&gt;The Privacy Experience Heuristics are for you if you are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Working on a technical product. Use these heuristics to evaluate how people experience your privacy features. Compare yourself against competitors to see how you measure up.&lt;/li&gt;
&lt;li&gt;Not working on a product yourself, but interested in evaluating and comparing the privacy experience&lt;/li&gt;
&lt;/ul&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href=&#34;https://superbloom.design/resources/privacy-experience-heuristics.pdf&#34;&gt;Read or download the Privacy Experience Heuristics.&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;h4 id=&#34;privacy-feels-smooth-supportive-and-empowering&#34;&gt;Privacy feels smooth, supportive, and empowering&lt;/h4&gt;
&lt;p&gt;For our Privacy Experience Heuristics, we wanted to quantify the experience of using a product that respects privacy. We broke down the experience of privacy into three aspects: a privacy-respecting product should feel smooth, supportive, and empowering. &lt;/p&gt;
&lt;p&gt;The Privacy Experience Heuristics build on &lt;a href=&#34;https://en.wikipedia.org/wiki/Privacy_by_design&#34;&gt;Privacy by Design&lt;/a&gt; (PbD), a framework that defines seven broad principles to guide a privacy-friendly approach to user data. These heuristics apply Privacy by Design principles directly to the user experience. They illustrate that Privacy by Design, usually read as applying to legal and technical privacy professionals, can also be implemented in product design.&lt;/p&gt;
&lt;h4 id=&#34;smooth&#34;&gt;Smooth&lt;/h4&gt;
&lt;p&gt;What makes a privacy experience feel smooth? &lt;/p&gt;
&lt;p&gt;People can just start using the product without being hassled or burdened with too many choices. They can trust that the default settings will meet a majority of their needs. &lt;/p&gt;
&lt;p&gt;Selected heuristics:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Users are not nudged to enter information that is not required for platform use.&lt;/li&gt;
&lt;li&gt;Rejecting non-essential cookies is possible with 1 click.&lt;/li&gt;
&lt;li&gt;Advertising is based on activity, not demographic data.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Corresponds with Privacy by Design, Principle 2: Privacy by Default.&lt;/strong&gt;&lt;/p&gt;
&lt;h4 id=&#34;supportive&#34;&gt;Supportive&lt;/h4&gt;
&lt;p&gt;What makes a privacy experience feel supportive? &lt;/p&gt;
&lt;p&gt;People are nudged towards actions that are in their interest. Personal data collection is minimized. The product warns or even forbids people from doing things that would compromise their privacy. People know there are guardrails in place to protect them, both from the company and from other people.&lt;/p&gt;
&lt;p&gt;Selected heuristics:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Camera and microphone access is only requested and used when relevant to what the user is doing.&lt;/li&gt;
&lt;li&gt;Metadata is removed from uploaded images.&lt;/li&gt;
&lt;li&gt;Permission to use precise location is not requested, unless users are aware of a feature that needs precise location to function.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Corresponds with Privacy by Design, Principle 3: Privacy Embedded Into Design; Principle 5, End-To-End Security; Principle 1, Proactive not reactive.&lt;/strong&gt;&lt;/p&gt;
&lt;h4 id=&#34;empowering&#34;&gt;Empowering&lt;/h4&gt;
&lt;p&gt;What makes a privacy experience feel empowering? &lt;/p&gt;
&lt;p&gt;People can control their experience, change their settings, and understand what’s going on. They can exercise their legal rights, whether that’s accessing their data or lodging a complaint. &lt;/p&gt;
&lt;p&gt;Selected heuristics:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Users can view how their profile looks to others.&lt;/li&gt;
&lt;li&gt;Users are periodically prompted to review their privacy choices.&lt;/li&gt;
&lt;li&gt;Users can request a copy of their data in the interface. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Corresponds with Privacy by Design, Principle 6: Visibility and Transparency; Principle 4, Full-Sum, Not Zero-Sum.&lt;/strong&gt;&lt;/p&gt;
&lt;h4 id=&#34;but-wait&#34;&gt;But wait… &lt;/h4&gt;
&lt;h5 id=&#34;do-people-actually-want-more-transparency-and-choice-or-do-they-want-smart-defaults-so-they-dont-have-to-think&#34;&gt;Do people actually want more transparency and choice, or do they want smart defaults so they don’t have to think?&lt;/h5&gt;
&lt;p&gt;People need both! That’s why our list of heuristics has categories called both “smooth” and “empowering.”&lt;/p&gt;
&lt;p&gt;Defaults should be privacy-preserving. People should opt in, not out, of sharing their data. A person who doesn’t want to dig around in their profile settings should have the most privacy-preserving experience that is practical.&lt;/p&gt;
&lt;p&gt;It should also be easy to alter the defaults: easy to find the settings, easy to figure out what the settings mean, easy to change settings and change them back.&lt;/p&gt;
&lt;h4 id=&#34;are-these-heuristics-a-guide-for-companies-to-fake-privacy&#34;&gt;Are these heuristics a guide for companies to fake privacy?&lt;/h4&gt;
&lt;p&gt;No, they aren’t. The features described require appropriate policies to back them up, otherwise they (mostly) won’t work. &lt;/p&gt;
&lt;p&gt;Here’s what the heuristics do for companies:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Even if a company’s policies are compliant with regulations, that might not be clear to the average user. Most people don’t read the fine print of terms and conditions to learn about the privacy they are entitled to. Their rights should be expressed in the product itself, as well as in the legal and technical documentation. &lt;/li&gt;
&lt;li&gt;These heuristics help companies to identify and enhance privacy features that are not just compliant with regulations, but also increase competitiveness and brand value.&lt;/li&gt;
&lt;li&gt;By highlighting how improved privacy can serve as a competitive advantage, the heuristics engage teams not traditionally involved in privacy, like product and marketing, encouraging them to champion privacy features. Their advocacy can drive support for enhancing privacy policies across the organization.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;credits&#34;&gt;Credits&lt;/h4&gt;
&lt;p&gt;Project Contributors: Veszna Wessenauer, Molly Wilson, Abhishek Sharma.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;This blog post is based on a session at MozFest 2024, “&lt;a href=&#34;https://pretalx.com/mozfest-house-amsterdam-2024/talk/DXZF9W/&#34;&gt;Elevating Privacy: Centering User Experience&lt;/a&gt;,” presented by &lt;a href=&#34;https://superbloom.design/about/people/veszna/&#34;&gt;Veszna Wessenauer&lt;/a&gt;, &lt;a href=&#34;https://www.linkedin.com/in/mascha-a-188a1a145/&#34;&gt;Mascha Arnst&lt;/a&gt;, and &lt;a href=&#34;https://www.linkedin.com/in/jasper-enderman/&#34;&gt;Jasper Enderman&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Communications Toolkit for Civic &amp; Nonprofit Tech</title>
      <link>https://superbloom.design/work/projects/comms__design_templates/</link>
      <pubDate>Mon, 28 Oct 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/work/projects/comms__design_templates/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Communications Tools For Teams Like Yours (And Ours)</title>
      <link>https://superbloom.design/learning/blog/communications-tools-for-teams-like-yours-and-ours/</link>
      <pubDate>Mon, 28 Oct 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/communications-tools-for-teams-like-yours-and-ours/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_comms_toolkit-cover_hu_b3b73ca7324c0a62.png&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Superbloom is proud to be part of a community that actively contributes to the responsible development of technology. There are lots of people like us out there: small teams and organizations, lots of us nonprofits or open-source projects, all of us working different angles to improve and diversify the tech landscape.&lt;/p&gt;
&lt;p&gt;While we don’t have a large marketing budget, we do want to deliver quality communications and be noticed and understood and get the work into the hands of the people who need it.&lt;/p&gt;
&lt;p&gt;At Superbloom, we work with nonprofits working to strengthen their tech and strategy offerings. In collaboration with the Open Technology Fund’s Learning Lab, we’ve made a collection of resources for small tech and activist organizations who are undertaking communications projects. We like to share the tools we use ourselves. These are also the tools we use when we work together with other organizations. And we hope they’re useful to you as well.&lt;/p&gt;
&lt;p&gt;We’d like to spotlight two parts of this communications toolkit that we think are particularly applicable to civic and nonprofit tech projects.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_comms_toolkit_row_1_hu_2d4b79bc00587a8f.png&#34; width=&#34;740&#34; height=&#34;164&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;can-you-do-this-in-a-month-check-our-scoping-guide&#34;&gt;Can you do this in a month? Check our scoping guide&lt;/h4&gt;
&lt;p&gt;First, we’d like to show you our &lt;a href=&#34;https://superbloom.design/learning/resources/scoping-communications-projects/&#34;&gt;Communications Project Scoping Guide&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;There is plenty of great communications advice on the internet. But how do you turn advice into deliverables? And how do you turn deliverables into a plan (and a budget)? That’s why we wrote some sample project plans for you to pick from and use.&lt;/p&gt;
&lt;p&gt;As a small organization, we know that before you start a project, you need to resource it. What’s the budget, where’s the expertise, and what timeline are you working with? If you don’t have much familiarity with communications projects, this lack of planning information could stop you in your tracks. Our scoping guide removes that blocker. We aren’t afraid to get specific: we tell you what you likely need (and what you don’t), and approximately how long we think it should take to complete. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_comms_toolkit_row_2_hu_dcb164a9e5a14928.png&#34; width=&#34;740&#34; height=&#34;164&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;design-with-your-community-not-just-for-them---heres-how&#34;&gt;Design with your community, not just for them - here’s how &lt;/h4&gt;
&lt;p&gt;Next, we’d like to point you to our &lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design/&#34;&gt;Guide to Participatory Approaches in Communications&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;A lot of communications advice is about “getting your message out there.” What if you don’t know what your message is? And what if you’re not sure about the best way to say it? We can’t answer those questions for you. But there are people who can guide you: &lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design/&#34;&gt;your community&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;As human-centered designers, we start a project by involving people affected by it. Our guide to participatory communications processes gives you some starting points for bringing stakeholders together in co-design workshops. This doesn’t apply to every type of communications project – your community doesn’t need to help you with your invoice letterhead – but especially for projects around how to project your image externally, some well-structured workshops with your community can be an enormous source of insight and inspiration.&lt;/p&gt;
&lt;p&gt;Now, your community isn’t a source of free labor; don’t expect them to design you a logo or write you a pitch deck. You still need to take responsibility for driving and completing the project. Think of your community rather as a group of wise, trusted mentors. They likely see you more clearly than you see yourself. They can help you emphasize the right points, get the most out of your communications efforts, and avoid messaging missteps. Just remember to respect their time, open your mind to their feedback, and give them credit when you launch. &lt;/p&gt;
&lt;p&gt;When you coordinate your communications, branding, and identity, it doesn’t just help your organization – it helps us all. People can find us all more easily, understand what we’re trying to do, and engage with our work. &lt;/p&gt;
&lt;p&gt;Is this toolkit helpful to you? We’d love to hear how.&lt;/p&gt;
&lt;p&gt;Is there a resource you’d really like us to create or add? Tell us that, too.&lt;/p&gt;
&lt;p&gt;Would you like to work together on a communications project? Our mailbox is open. Say &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;credits&#34;&gt;Credits&lt;/h4&gt;
&lt;p&gt;Project Contributors: Ame Elliott, Veszna Wessenauer, Abhishek Sharma, Georgia Bullen, Laura Gaetano, Molly Wilson.&lt;/p&gt;
&lt;p&gt;With support from &lt;a href=&#34;https://www.opentech.fund/labs/learning-lab/&#34;&gt;Open Technology Fund Learning Lab&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>182 Days To Create A Prototype</title>
      <link>https://superbloom.design/learning/blog/182-days-to-create-a-prototype/</link>
      <pubDate>Wed, 25 Sep 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/182-days-to-create-a-prototype/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_182_days_prototype_fund_schwag_hu_6470df7b977948fe.jpg&#34; alt=&#34;Photograph of a table with a piece of checked paper and a beaded wristband with the initials P T F. Above the wristband is the word ANALOG in blue overlaid by the word DIGITAL in blue.&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;p&gt;They have an idea. They have programming skills. And now they have 182 days to create a prototype. This is the Prototype Fund, a German government program to support open-source projects. Superbloom has been providing support for the teams on “everything but code” since 2018 – from UX design to fundraising and everything in between. This blog post is for Prototype Fund teams, and really, it’s for anyone hoping to do a lot on a development project in a short time. Here’s how you make the most of 182 days!&lt;/p&gt;
&lt;p&gt;We’ve written this blog post for Prototype Fund teams, or really for anyone who’s working on an early-stage tech project. We’ve assumed you have expertise in the technical nuts and bolts. What we can help you with is… well, everything else. We’re experts in many different areas adjacent to civic, open-source, and nonprofit tech, and we specialize in providing you with just enough expertise to get you going in the right direction.&lt;/p&gt;
&lt;p&gt;Here’s our perspective on how each project needs to focus its efforts and create a good flow. It’s a non-exhaustive list, and our intention is to create talking points for teams, and ideas for coaching sessions with us where we can dig into some of these topics more. Here we go!&lt;/p&gt;
&lt;h3 id=&#34;usability-testing&#34;&gt;Usability testing&lt;/h3&gt;
&lt;p&gt;Identify and resolve usability issues early! You’re the wrong person to find the usability hiccups with your project – everything makes sense to you, after all – but minor issues can cause major problems, making it harder for others to find, download, or use your project. Getting feedback is easy and often even fun, and becomes easier the more you do it. &lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Test opportunistically and often: Testing is part of a process, not a last step. In fact, if you wait to test until the end, we guarantee you will wish you’d done it earlier. We like to store results on a digital whiteboard, such as Miro or Excalidraw so you can cluster similar feedback from different tests, even if they’re weeks or months apart. &lt;/li&gt;
&lt;li&gt;Start with your friends: Some people worry about finding testers who are an exact demographic match for the target user group, or about reaching the correct sample group size. These are valid concerns, but they should not stop you from testing! A small “hey, could you try to make a meeting on this app” with a friend beats testing too late in your process. &lt;/li&gt;
&lt;li&gt;Testing without code: You can test even if you do not have any running code. You can use paper prototypes, boxes-and-lines mockups, or code that just shows UI with no real data behind it. &lt;/li&gt;
&lt;li&gt;Testing with code: Once you do have code, aim to reach a point where you run all relevant parts of the software together instead of just single bits. It helps with both testing code and usability since you always have a running version of your software. &lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Suggested reading and resources:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://sprblm.github.io/devs-guide-to/&#34;&gt;A Dev&amp;rsquo;s Guide to User Testing, Superbloom&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/how-to-test-software-for-usability-and-usefulness-when-you-havent-finished-writing-the-code/&#34;&gt;How To Test Software For Usability And Usefulness When You Haven’t Finished Writing The Code, Jan Dittrich/Superbloom&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/user-testing-cheatsheet/&#34;&gt;User Testing Cheat Sheet, Molly Wilson/Superbloom&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://sensible.com/rocket-surgery-made-easy/&#34;&gt;Rocket Surgery Made Easy, Steve Krug&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.sciencedirect.com/book/9780123848697/observing-the-user-experience&#34;&gt;Observing The User Experience, Goodman et al&lt;/a&gt; (chapters 2, 11 in particular)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;branding-and-identity&#34;&gt;Branding and identity&lt;/h3&gt;
&lt;p&gt;At first glance, “brand” might sound like something a nonprofit or civic tech project needs to prioritize. The word “branding” carries the connotation of advertising, selling, and competing in the marketplace, which may not match your project or goals. But at its core, branding is about making clear who you are (and who you aren’t), something every project can use. Even a no-frills, minimalist approach to a consistent look and feel goes a long way to help others recognize, understand, and be able to talk about your work. &lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Focus on consistency, not uniqueness. It’s hard, and becoming harder, to come up with groundbreaking brand elements that nobody has used before. Of course, you don’t want people to confuse you with other projects, and straight up copying others leaves you open to legal threats. But if a tea house in Yorkshire has the same name as your ad-blocking browser extension, nobody is realistically going to be confused. The same goes for colors, illustrations, and typography. &lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Test brand elements in context: It’s far easier to judge whether a name, logo, or other building block is working well when you mock it up in the exact place you’re going to use it. Practice saying “you should check out [name] on GitHub.” Write a “lorem ipsum” website and tweak the colors and images before you try writing a real blog post. Photoshop your logo onto a picture of a laptop to see how it works as a sticker.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Rely on libraries and helper tools: Especially if you’re not confident with visual communication, take advantage of the many libraries and tools out there that can help you create a professional, consistent look and feel quickly. &lt;a href=&#34;https://leonardocolor.io/#&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;For open-source fonts, check out &lt;a href=&#34;https://open-foundry.com/fonts&#34;&gt;Open Foundry&lt;/a&gt;. &lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://leonardocolor.io/#&#34;&gt;Leonardo&lt;/a&gt; is an open-source color theme generator.&lt;/li&gt;
&lt;li&gt;And, the &lt;a href=&#34;https://search.creativecommons.org/&#34;&gt;Creative Commons search portal&lt;/a&gt; points you to images and other media that are free to use under CC licenses.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;It’s not just how you look, it’s how you speak: Branding and identity aren’t only about the parts you see (such as the visuals, name, and tagline). Branding and identity are also about how you speak to your users and community (also called “voice”), what you stand for, and your values. For example, if you’re trying to make a complex and intimidating process accessible to beginners, your voice should be friendly, approachable, and encouraging. If you’re writing a more advanced library or API, your voice should probably be knowledgeable, clear, and collegial&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The smallest bits are the most challenging: Creating a logo and deciding on a name are actually some of the hardest parts of creating a branding and identity. These building blocks need to do a lot of work in a small space, so a lot of work is needed from concept to finished design. Don’t be afraid to ask for help (for example, from us).&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Suggested resources:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/comms-toolkit/&#34;&gt;Communications Toolkit for Civic &amp;amp; Nonprofit Tech, Superbloom&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.fordes.de/posts/logodesign_softwareproject.html&#34;&gt;Designing A Logo For Your Software Project - Fordes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;technical-infrastructure-and-code&#34;&gt;Technical infrastructure and code&lt;/h3&gt;
&lt;p&gt;We’ve put together a short list of some of our top tips for early ideas and tech prototypes for technical builds.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Work on creating a running version early on: An early version is also great for obtaining early feedback from users via user testing! Most importantly, make sure different parts of your system will work together, even if they just pass hard-coded mock data. A simple method to plan and collaborate on running software is the tracer bullet method described in &lt;a href=&#34;https://pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition/&#34;&gt;The Pragmatic Programmer&lt;/a&gt; and &lt;a href=&#34;https://pragprog.com/titles/prj/ship-it/&#34;&gt;Ship It!&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Avoid building from scratch: Make use of existing open source software and tools instead of building everything from scratch.&lt;/li&gt;
&lt;li&gt;Avoid elaborate development methods or complex tools if possible: These were often designed and developed for work for big companies, and we find it’s best to keep it simple.&lt;/li&gt;
&lt;li&gt;Use tools that you and your team are already familiar with, even those others may see as boring: For example, e-mail, chat groups and office programs are not cool, but often do the job well. Java, Python, JSON, and Object Oriented Programming are not particularly exciting, but have plenty of documentation and best practices. It is important to be able to collaborate and work efficiently and this works best if you build on knowledge and skills you already have.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Suggested reading: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition/&#34;&gt;The Pragmatic Programmer, David Thomas and Andrew Hunt&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://pragprog.com/titles/prj/ship-it/&#34;&gt;Ship It! A Practical Guide to Successful Software Projects, Jared Richardson, Will Gwaltney, Jr&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;organization-and-management&#34;&gt;Organization and management&lt;/h3&gt;
&lt;p&gt;Being organized is a sure way to set yourself up for success in short turnaround projects. We’ve made a list of recommendations:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Communication: Rules, tickets/issues and meetings may seem useless - and this is certainly sometimes the case - but very often they help a team to work better. A lot of organizing is about communicating in a way that people have a shared understanding of what they need to do now and what they want to achieve next. What may seem like mere bureaucracy can help with that. &lt;/li&gt;
&lt;li&gt;Todo list: There are many organization and project management methods. The basic version is a shared, prioritized list. Important things are listed at the top, and project teams pick things from the top. There are many free todo list apps and project management tools such as Notion, Monday etc.&lt;/li&gt;
&lt;li&gt;Make tasks clear and actionable: Vague tasks such as “Make software more usable” or “Clean up code” are never completed on a todo list. Move tasks like this to another place eg “Values” or “General ideas to consider”. Tasks should be self contained and it should be easy to decide if and when they are to be actioned.&lt;/li&gt;
&lt;li&gt;Winning: To feel like you’re winning, at the end of each working day, make a list of the three things you want to achieve/complete the following day (big or small), and do those three things before you do anything else the following work day. &lt;/li&gt;
&lt;li&gt;Be specific: If you find yourself making lists of lots of issues, try to find a format that you can repeat. We like: “User story/what should happen/what happens now/notes”. This helps to remember information that is important later. “Fix FooBarManager: Crash condition” might make sense now, but in a few days’ time, you may not remember what those notes were for.&lt;/li&gt;
&lt;li&gt;Standups: Have a regular (ideally daily) project team standup meeting where you briefly say what you did, what you want to do and what you need help with. No discussions or explanations; just a quick update for all. After the standup you can collaboratively decide what you want to hear more about, or what you want to discuss together.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;fundraising-and-sustainability&#34;&gt;Fundraising and sustainability&lt;/h3&gt;
&lt;p&gt;Thinking and planning for a fundraising and sustainability strategy in OSS often begins with a series of decisions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How much do you and your users/maintainers want to diversify funding streams? &lt;/li&gt;
&lt;li&gt;What does sustainability really mean to your OSS project and your users? &lt;/li&gt;
&lt;li&gt;What values does our OSS uphold when it comes to financial sustainability and fundraising matters, and how might we govern difficult decisions?&lt;/li&gt;
&lt;li&gt;Should we search out grants, corporate sponsorships, membership fees, tenders, individual donations, or similar?&lt;/li&gt;
&lt;li&gt;Are we putting all our eggs in one basket, or should we explore a few different options to stay secure?&lt;/li&gt;
&lt;li&gt;Should we be a non-profit, foundation, or something else that fits our funding goals?&lt;/li&gt;
&lt;li&gt;Besides money, what else do we need, for example: maintainers, infrastructure, hardware or volunteers to keep things running smoothly?&lt;/li&gt;
&lt;li&gt;Are we ready to pivot or tweak our strategy if our/the situation changes?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Considering these questions as discussion points is a good place to start, followed by finding out what other stakeholders think, and what they need will help you better define a strategy. &lt;/p&gt;
&lt;p&gt;Now you have your list, we’ve put together our top seven fundraising and sustainability tips:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Legal and compliance considerations: Make sure your OSS project is set-up to legally accept funds, whether as a non-profit, foundation, or another type of entity. Be aware of any tax issues, licensing concerns, or legal rules that could affect your fundraising and sustainability plans. Don’t forget that the legal structure you choose for your company will affect the kinds of funding you can go after in the future. Not every company type can accept all kinds of funding, so think carefully about how your setup matches with potential grants, donations, or investments.&lt;/li&gt;
&lt;li&gt;Networking and follow-up: Maintain relationships with the people and funders you meet. Stay in touch via emails, professional networks, or however works best. Don’t just take their business card and leave it at that. Keep them in the loop about your project’s progress and any cool new updates. By regularly reaching out and making them feel like part of your community, you’re more likely to keep them engaged and supportive.&lt;/li&gt;
&lt;li&gt;Value proposition for funders: Your value proposition/vision may take time to become clear to you, but once it does, it will be a powerful tool in securing funding. A solid value proposition connects your project’s goals with what funders care about, helping them see why they should support you. It also keeps your fundraising efforts aligned with your company’s values and long-term vision.&lt;/li&gt;
&lt;li&gt;Diverse funding sources and risk mitigation: Look into different funding sources to avoid relying too much on just one eg individual donations, corporate sponsorships, grants, tenders, or selling services. It’s also a good idea to have a backup plan in case funding streams dry up or the economy takes a downward turn.&lt;/li&gt;
&lt;li&gt;In-kind contributions and non-financial support: Remember to encourage and recognize non-financial support such as hardware e.g. donated server space or volunteer developer hours. These kinds of contributions are super important for keeping your OSS project going and should be part of your strategy. A rainy day fund is also important for good financial health.&lt;/li&gt;
&lt;li&gt;Diversification of funding streams: Consider all the different ways of diversifying your funding streams such as one-time vs. recurring donations, or revenue from related services or products and membership fees. Each type of funding plays a key role in keeping your project sustainable.&lt;/li&gt;
&lt;li&gt;Create a sustainability plan/roadmap: Having a roadmap of what you would like to be funded, and the approximate labor or infrastructure costs to support that is key. Make these fundraising goals public in your OSS codebase as this can make it easier for funders to assess and find projects to fund. Also, consider what beyond financial funding would be needed in order to keep the project operational in various scenarios. For example, if your project would need 2-3 maintainers with specific programming skills in order to assess and merge pull requests, your sustainability plan would outline who is needed and how.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;community-building&#34;&gt;Community building&lt;/h3&gt;
&lt;p&gt;Community building is a broad and far-reaching topic, and summarizing how to build a community is often over-generalized. Here are are how-to’s:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Understand what your community expects of you and what you expect in return: As the OSS project and the maintainers of the OSS project, being clear, honest, and communicative about these expectations is always beneficial. Understanding your community&amp;rsquo;s expectations can be done by utilizing GitHub’s discussions/issues, forums, chat services and email feedback.&lt;/li&gt;
&lt;li&gt;Ask yourself why you need a community?: Yes, community is important for sustainability, but community building and engagement is a lot of work for a small project team. And sometimes the time isn’t right. Evaluate whether building and engaging with a community is right for you.&lt;/li&gt;
&lt;li&gt;Build documentation and processes: Once expectations have been communicated and set, you can begin to build documentation and processes that meet and expand on these expectations. For example, ensure your readme document is clear, informative and descriptive beyond the installation or functions of your OSS project work. Making sure you have a readme in &lt;a href=&#34;https://book.the-turing-way.org/project-design/code-styling/code-styling-readability.html&#34;&gt;Human Readable Code&lt;/a&gt; ensures that people of all skill levels, entry points and interests can participate. Human Readable Code, as referenced in the linked article is a great practice across issues, pull requests and the code base itself.&lt;/li&gt;
&lt;li&gt;Create contributing documents: Moving on to create dedicated contributing documents per function contribution (e.g. design-contributing.md, documentation-contributing.md etc.) sends a clear signal to your community that you value contributions beyond code. These are actions that subtly promote inclusion and diversity in your OSS Project.&lt;/li&gt;
&lt;li&gt;Create a roadmap: Write a short guide for you and your team to set up your community. Include your aims: who is your community, where will you find them, how will you engage with them, what are you offering them, how often will you engage with them, what you are hoping to gain from them etc.&lt;/li&gt;
&lt;li&gt;Making your community self-supporting: Once you’ve begun to grow community participation, you can consider what it means to have the community support, promote and grow itself, so that it becomes a self-supporting function of the OSS project. This is a long-term goal – it’s unlikely you will accomplish this in your first 182 days.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;networking&#34;&gt;Networking?&lt;/h3&gt;
&lt;p&gt;Networking may not seem like a priority, or very important, and tends to be downplayed as something rather unserious or not valued. It’s also about making new connections, such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Superbloom coaches who themselves might be well-connected to the open source or civic tech world.&lt;/li&gt;
&lt;li&gt;The Prototype Fund team, who through their work in the last few years have met a lot of different people and are well-connected (and might have pointers about other ways to support a project financially).&lt;/li&gt;
&lt;li&gt;People with similar interests who may be interested in supporting your work financially or contributing.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There are a lot of myths surrounding networking. You don’t have to be an “extrovert” to network and it doesn’t just happen at events. It also doesn’t have to be exhausting! Connecting with fellow projects informally for inspiration and camaraderie often happens online as well as offline. If you do want to attend events:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Be present: Be present in the spaces (physical or otherwise) you enjoy and want to be involved in will allow people to remember you and remember your work. &lt;/li&gt;
&lt;li&gt;Present your ideas: Present your ideas and work at relevant conferences as this allows you to learn about people working on similar topics/projects. &lt;/li&gt;
&lt;li&gt;Be visible: Be part of relevant physical and digital space, which will help people think of you as part of a particular community. These can also act as “multipliers” by sharing your work, or connecting you to similar people (“hey, you’re working on X, you should meet Y who is working on Z, as there is some overlap”).&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;There’s lots of overlap between networking and usability testing (see above); networking is full of opportunities to seek and receive feedback throughout the whole development process. If nothing else, connecting with others can be a powerful motivator to be told that what you&amp;rsquo;re working on is exactly what someone else needs, wants to see, or always hoped would be developed. You’re on the right track!&lt;/p&gt;
&lt;h3 id=&#34;what-next&#34;&gt;What next?&lt;/h3&gt;
&lt;p&gt;We hope you enjoyed reading our perspective about how to make the most of 182 days to work on your prototype! There’s a lot to keep track of, but there are many people out there - including us - in the open source and nonprofit tech community excited, and able to help and support you.&lt;/p&gt;
&lt;p&gt;If you’d like more customized advice, we’d love to talk to you. If you’re a Prototype Fund team, good news – this is already covered for you. Get in touch!: &lt;a href=&#34;mailto:coaching@superbloom.design&#34;&gt;coaching@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;Blog post contributors: Rocío Armillas Tiseyra, Tori Boeck, Victory Brown, Jan Dittrich, Eriol Fox, Laura Gaetano, Nicola Pratt, Saptak Sengupta, Molly Wilson.&lt;/p&gt;
&lt;p&gt;With thanks to the &lt;a href=&#34;https://prototypefund.de/en/&#34;&gt;Prototype Fund&lt;/a&gt;, a Berlin based program of the &lt;a href=&#34;https://okfn.de/&#34;&gt;Open Knowledge Foundation Deutschland&lt;/a&gt; dedicated to supporting public interest tech.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Communications Toolkit for Civic &amp; Nonprofit Tech: Participatory Approaches</title>
      <link>https://superbloom.design/learning/resources/participatory-comms-design/</link>
      <pubDate>Mon, 16 Sep 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/participatory-comms-design/</guid>
      <description>&lt;p&gt;&lt;em&gt;This resource is part of our &lt;a href=&#34;https://superbloom.design/learning/resources/comms-toolkit&#34;&gt;Communications Toolkit for Civic &amp;amp; Nonprofit Tech&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Traditionally, communications is about crafting a message and delivering it to an audience. You decide what you want to tell people. You choose words, media, and channels to get this message across to those people. And you put the message out in the world, and measure whether it&amp;rsquo;s having the effect you wanted.&lt;/p&gt;
&lt;p&gt;But this approach contains assumptions that you, and we, may not actually agree with.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You assume that you know what needs to be communicated, and to whom.&lt;/li&gt;
&lt;li&gt;You assume that you are the right person to be communicating it.&lt;/li&gt;
&lt;li&gt;You assume that you know the most effective way to communicating it.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Put another way: &lt;em&gt;you assume that you know what others want and need.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;What if we flip the traditional communications approach on its head? What if we put the needs and priorities of our community first?&lt;/p&gt;
&lt;p&gt;This point of view has been beautifully articulated by the &lt;a href=&#34;https://designjustice.org/&#34;&gt;Design Justice Network&lt;/a&gt;, a group that aims to move beyond &amp;ldquo;design for social good,&amp;rdquo; which assumes that a benevolent designer knows what&amp;rsquo;s best for the target audience, and towards a &lt;a href=&#34;https://designjustice.org/read-the-principles&#34;&gt;&amp;ldquo;design justice&amp;rdquo;&lt;/a&gt;
that centers the people affected and aims to heal, liberate, and restore.&lt;/p&gt;
&lt;p&gt;If this sounds too lofty for organizational communications, consider that the role of communications is to &lt;em&gt;connect&lt;/em&gt;. In the nonprofit world, connection is not as easy as declaring our desire to help. Depending on your own positionality related to the communities you&amp;rsquo;re working with, you may have centuries of patriarchy, colonialism, ableism, and other supremacist mindsets gumming up the channels of communication – even if you personally see yourself as not perpetuating these forces, you still need to push back against them, and your communications practices are a key piece of your strategy.&lt;/p&gt;
&lt;p&gt;Your name, branding, and overall vibe can either distance you from your community, or bring you closer. Your use of social media will either make you into cringeworthy do-gooders, or show that you&amp;rsquo;re serious about making a difference.&lt;/p&gt;
&lt;p&gt;This change in approach can be described in many ways. You may hear the terms &amp;ldquo;co-design,&amp;rdquo; &amp;ldquo;participatory design,&amp;rdquo; and &amp;ldquo;human-centered design.&amp;rdquo; These terms indicate different degrees to which the community is involved in the process. We aren&amp;rsquo;t going to define the terms here, since the nuances depend somewhat on which field you&amp;rsquo;re coming from; for example, the terms mean different things in citizen science than they do in urban planning.&lt;/p&gt;
&lt;p&gt;Whatever you call the process, &lt;strong&gt;you can involve the people you serve in every phase of your communications work&lt;/strong&gt; – and you&amp;rsquo;ll be glad you did.&lt;/p&gt;
&lt;h2 id=&#34;whats-different-about-a-community-led-process&#34;&gt;What&amp;rsquo;s different about a community-led process?&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;You&amp;rsquo;ll need to give people an overview of the whole process. Let them know where decision-making power lies at each part of the process: with the community, with a small committee, or with your organization? (This may challenge you to give the community more decision-making power than you had originally intended - that&amp;rsquo;s usually a good thing!)&lt;/li&gt;
&lt;li&gt;If people come to a meeting, offer to compensate them for their time. Cash or a gift certificate are common acknowledgements of people&amp;rsquo;s time and effort.&lt;/li&gt;
&lt;li&gt;Expect some drop-off from people who don&amp;rsquo;t have time to participate in a longer process; start with a slightly larger group than you need.&lt;/li&gt;
&lt;li&gt;Replace an extractive mindset – you&amp;rsquo;re gathering material and using it to make decisions – with a collaborative mindset – you&amp;rsquo;re learning and making decisions together.&lt;/li&gt;
&lt;li&gt;Be clear with everyone involved when you are in a &amp;ldquo;flare&amp;rdquo; mode, where more input and ideas are better, and when you are transitioning to a &amp;ldquo;focus&amp;rdquo; mode, when you are editing down and making decisions. In our experience, collisions between one person&amp;rsquo;s flare and another person&amp;rsquo;s focus make up most of the conflict in a participatory session or project.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;folks-we-admire&#34;&gt;Folks we admire&lt;/h2&gt;
&lt;p&gt;We have learned an enormous amount from the collaborative design studio &lt;a href=&#34;https://www.andalsotoo.net/&#34;&gt;And Also Too&lt;/a&gt;. They were instrumental in helping us shape the community-driven approach that we took to our own rebranding.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&#34;https://www.de-center.net/what-is-design-from-the-margins1_&#34;&gt;Design from the Margins (DFM)&lt;/a&gt; methodology developed by re|center is a research-based methodology that emphasizes deeply taking the perspectives of vulnerable people into account. The &lt;a href=&#34;https://www.de-center.net/resources&#34;&gt;case studies&lt;/a&gt; of DFM in practice are powerful and important to read.&lt;/p&gt;
&lt;h2 id=&#34;practical-resources&#34;&gt;Practical resources&lt;/h2&gt;
&lt;p&gt;There isn&amp;rsquo;t exactly an existing toolkit for community-led design in organizational communications. (That&amp;rsquo;s one big reason we&amp;rsquo;re writing this series!)&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re interested in taking this approach, first, understand and scope the communications issue you want to solve.&lt;/p&gt;
&lt;p&gt;Then, peruse some of these participatory design toolkits developed for other applications, and consider which ones might work well for different phases of your communications project.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re stuck, you can &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;contact us&lt;/a&gt;! We did our own rebrand using a community-led process, and we&amp;rsquo;d love to talk through your ideas with you.&lt;/p&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
&lt;p&gt;Throughout this toolkit, we&amp;rsquo;ve called out opportunities for giving your community the opportunity to guide you - look for the purple boxes.&lt;/p&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;a href=&#34;https://www.liberatingstructures.com/ls/&#34;&gt;35 patterns of Liberating Structures&lt;/a&gt; are an excellent jumping-off point if you have a bit of facilitation experience. They describe ways to arrange and structure a group in order to challenge or even invert the existing power dynamics.&lt;/li&gt;
&lt;li&gt;The Crown Wellness Institute at the University of Colorado Boulder has a &lt;a href=&#34;https://www.colorado.edu/crowninstitute/welcome-crown-institute-participatory-toolkit&#34;&gt;Participatory Research Toolkit&lt;/a&gt; that is primarily geared towards health and wellness research, but could also be useful for communication design, especially since the methods are described for both physical and digital groups.&lt;/li&gt;
&lt;li&gt;The majority of participatory design toolkits deal with the topic of space – &lt;a href=&#34;http://urbantoolkit.eu/tools-and-methods/participatory-design/&#34;&gt;urban space&lt;/a&gt;, &lt;a href=&#34;http://deptofplaces.org/partdesigntoolkit&#34;&gt;architectural space&lt;/a&gt;, &lt;a href=&#34;https://www.enterprisecommunity.org/resources/participatory-design-toolkit&#34;&gt;affordable housing&lt;/a&gt;. These methods can be challenging to translate to the digital realm, but they are helpful to understand the mindset of participatory design.&lt;/li&gt;
&lt;li&gt;The &lt;a href=&#34;https://www.liberatorydesign.com/&#34;&gt;Liberatory Design Toolkit&lt;/a&gt; works at a broader level than the other toolkits above, and may help you to rethink your relationship to the communication project you&amp;rsquo;re planning.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;As Shannon Webber of Northeastern University &lt;a href=&#34;https://dsg.northeastern.edu/asking-questions-that-matter-the-power-of-participatory-design/&#34;&gt;writes&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Participatory design is not about not &lt;em&gt;fearing&lt;/em&gt; the public, it’s about &lt;em&gt;engaging&lt;/em&gt; with them in spite of the fear of rejection. As a facilitator it is your job to figure out the problems that they want solved by asking as many questions as possible. More questions mean more answers. More answers mean more information. More information means better opportunity for understanding.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;There aren&amp;rsquo;t so many examples of participatory design in communications, and we&amp;rsquo;d like to create more. If you end up using community-centered methods in your communications project, please let us know! We would love to feature your work and help others get inspired.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/comms-toolkit&#34;&gt;This toolkit&lt;/a&gt; was developed with the support of the &lt;a href=&#34;https://www.opentech.fund/labs/learning-lab/&#34;&gt;Open Technology Fund Learning Lab&lt;/a&gt;. Got feedback? Want to work together? Please write to us at &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Communications Toolkit</title>
      <link>https://superbloom.design/learning/collections/communications-toolkit-for-civic-nonprofit-tech-1/</link>
      <pubDate>Tue, 10 Sep 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/collections/communications-toolkit-for-civic-nonprofit-tech-1/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Communications Toolkit for Civic &amp; Nonprofit Tech: Crafting a Press Release</title>
      <link>https://superbloom.design/learning/resources/crafting-press-release/</link>
      <pubDate>Tue, 10 Sep 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/crafting-press-release/</guid>
      <description>&lt;p&gt;&lt;em&gt;This resource is part of our &lt;a href=&#34;https://superbloom.design/learning/resources/comms-toolkit&#34;&gt;Communications Toolkit for Civic &amp;amp; Nonprofit Tech&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Structured public communications, like press releases, media advisories, and research reports, are important tools for you to communicate your advocacy and impact. This post leads you through the building blocks of a press release. (If you like, you can also fill out our &lt;a href=&#34;https://docs.google.com/document/d/1KNHTTzDREANkMbqb61osQHRQI-etGpRcv26xiKIAocs/edit#heading=h.y86i10uckoir&#34;&gt;press release template (Google Docs)&lt;/a&gt;.)&lt;/p&gt;
&lt;h2 id=&#34;understanding-different-communication-tools&#34;&gt;Understanding different communication tools&lt;/h2&gt;
&lt;p&gt;Before we dive into creating a press release, let&amp;rsquo;s clarify the key communication tools at your disposal.&lt;/p&gt;
&lt;h3 id=&#34;press-release&#34;&gt;Press release&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Definition:&lt;/strong&gt; A press release is a formal written statement aimed at journalists and media outlets. It provides detailed information about a specific event, development, report, or issue.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Purpose:&lt;/strong&gt; To announce news, generate media coverage, and provide journalists with comprehensive information for reporting in your area. Many journalists may not be experts, and you can help them get the information they need and frame the issues in a way that Effective use of press releases can lead to media coverage and build momentum towards change.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;media-advisory&#34;&gt;Media advisory&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Definition:&lt;/strong&gt; A media advisory is a brief alert to journalists, inviting them to an upcoming event, press conference, or interview opportunity.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Purpose:&lt;/strong&gt; To grab journalists&amp;rsquo; attention, encourage attendance, and ensure people are aware of your event.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;research-report&#34;&gt;Research report&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Definition:&lt;/strong&gt; Civil society organizations at the intersection of technology and human rights often conduct research.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Purpose:&lt;/strong&gt; Research reports use the insights you collect to inform policy decisions and advocacy efforts. Research reports often present data, analysis, and recommendations in order to educate the public and raise awareness. Reports are also a &amp;ldquo;show, don&amp;rsquo;t tell&amp;rdquo; way to illustrate your expertise and impact, which can support fundraising and further your mission. (Check out this toolkit&amp;rsquo;s &lt;a href=&#34;https://docs.google.com/document/d/1yftME-d9EZxAxoxQfQ51mbhmtRu-6AXO1f5emnTILkI/edit&#34;&gt;template for a research report (Google Docs)&lt;/a&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;crafting-a-press-release&#34;&gt;Crafting a press release&lt;/h2&gt;
&lt;p&gt;We&amp;rsquo;ll be talking here about &lt;strong&gt;press releases&lt;/strong&gt;. Follow these steps to create a press release, using prompts and examples that you can modify for your needs. (We also have a &lt;a href=&#34;https://docs.google.com/document/d/1KNHTTzDREANkMbqb61osQHRQI-etGpRcv26xiKIAocs/edit#heading=h.y86i10uckoir&#34;&gt;press release template (Google Docs)&lt;/a&gt; you can fill out.)&lt;/p&gt;
&lt;h3 id=&#34;start-with-a-compelling-headline&#34;&gt;Start with a compelling headline&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Do this:&lt;/strong&gt; Write a headline that summarizes the main message of your press release.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Example:&lt;/strong&gt; &amp;ldquo;New Report Reveals Alarming Data Privacy Violations in Tech Industry&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;write-an-engaging-lead-paragraph&#34;&gt;Write an engaging lead paragraph&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Do this:&lt;/strong&gt; Craft a concise lead paragraph (1-2 sentences) that captures the most important information.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Example:&lt;/strong&gt; &amp;ldquo;A groundbreaking report by [Your Organization] exposes widespread data privacy violations within the tech industry, raising urgent concerns about the protection of user data.&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;provide-key-details&#34;&gt;Provide key details&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Do this:&lt;/strong&gt; Share the who, what, when, where, why, and how of your news.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Example:&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Who: [Your Organization]&lt;/li&gt;
&lt;li&gt;What: Release of the Data Privacy Violations Report&lt;/li&gt;
&lt;li&gt;When: [Date], [Time]&lt;/li&gt;
&lt;li&gt;Where: [Event Venue or Online Platform]&lt;/li&gt;
&lt;li&gt;Why: To inform the public about data privacy issues and call for industry reform&lt;/li&gt;
&lt;li&gt;How: Through a press conference and online publication&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;include-quotes&#34;&gt;Include quotes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Do this:&lt;/strong&gt; Add quotes from key stakeholders or experts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Example:&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;[Leader in Your Organization]: &amp;lsquo;This report underscores the urgency of protecting user data in the digital age.&amp;rsquo;&lt;/li&gt;
&lt;li&gt;[Data Privacy Expert]: &amp;lsquo;These findings reveal a systemic problem that demands immediate attention.&amp;rsquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;provide-background-information&#34;&gt;Provide background information&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Do this:&lt;/strong&gt; Offer context or background information about the issue or event.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Example:&lt;/strong&gt; Explain the current state of data privacy in the tech industry and your organization&amp;rsquo;s role in advocating for change.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;add-multimedia-content&#34;&gt;Add multimedia content&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Do this:&lt;/strong&gt; Consider including images, infographics, or videos to enhance your press release. Make sure to properly credit any media you did not create.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Example:&lt;/strong&gt; Attach a graph showing data privacy violations by tech companies.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;end-with-a-boilerplate-and-contact-information&#34;&gt;End with a boilerplate and contact information&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Do this:&lt;/strong&gt; Include a brief description of your organization and contact information for media inquiries.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Example:&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;About [Your Organization]: [Brief description of your organization&amp;rsquo;s mission and work], and link to website&lt;/li&gt;
&lt;li&gt;For media inquiries, contact [Name], [Email], [Phone Number].&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;proofread-and-edit&#34;&gt;Proofread and edit&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Do this:&lt;/strong&gt; Review your press release for grammar, spelling, and accuracy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Example:&lt;/strong&gt; Ensure all names, dates, and facts are correct, and that the writing is clear and concise.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;send-it&#34;&gt;Send it!&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Do this:&lt;/strong&gt; Post the press release on your website. Post a link to your social media. If you have a newsletter, include it in your newsletter. And send it individually to anybody you feel would benefit from it – especially journalists or media professionals you have been in contact with in the past.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/comms-toolkit&#34;&gt;This toolkit&lt;/a&gt; was developed with the support of the &lt;a href=&#34;https://www.opentech.fund/labs/learning-lab/&#34;&gt;Open Technology Fund Learning Lab&lt;/a&gt;. Got feedback? Want to work together? Please write to us at &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Communications Toolkit for Civic &amp; Nonprofit Tech: Resources for Communications Strategy</title>
      <link>https://superbloom.design/learning/resources/organizational-comms-strategy/</link>
      <pubDate>Tue, 10 Sep 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/organizational-comms-strategy/</guid>
      <description>&lt;p&gt;&lt;em&gt;This resource is part of our &lt;a href=&#34;https://superbloom.design/learning/resources/comms-toolkit&#34;&gt;Communications Toolkit for Civic &amp;amp; Nonprofit Tech&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ve collected some resources from around the web to help guide you through your organizational communication strategy.&lt;/p&gt;
&lt;h2 id=&#34;is-it-ethical-to-use-social-media&#34;&gt;Is it ethical to use social media?&lt;/h2&gt;
&lt;p&gt;Corporate social media platforms would like you to think they are neutral channels delivering information to people. In fact, the companies behind the large social media platforms are some of the biggest for-profit companies in the world, and they make that money (for the most part) by &lt;a href=&#34;https://www.wired.com/story/social-media-ceo-hearing-cant-defend-business-model/&#34;&gt;gathering as much user data as possible so that they can targeting ads as precisely as possible&lt;/a&gt;. Social media&amp;rsquo;s UX features, privacy and security, and moderation practices all exist in service of &lt;a href=&#34;https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8179701/&#34;&gt;attracting users, increasing engagement, and targeting advertisements&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re guessing this mission doesn&amp;rsquo;t exactly match your values. You&amp;rsquo;re probably not that enthusiastic about encouraging your community to &amp;ldquo;engage&amp;rdquo; on social media in order to feed the data machine.&lt;/p&gt;
&lt;p&gt;Alternatives like &lt;a href=&#34;https://mastodon.social/explore&#34;&gt;Mastodon&lt;/a&gt; offer an appealing way to use social media in a way that better matches our values. At the same time, many of us can&amp;rsquo;t afford not to be on corporate social media. We may need to get our message out and reach a more mainstream audience. How do we manage these competing priorities?&lt;/p&gt;
&lt;p&gt;Digital strategist &lt;a href=&#34;https://keidradchaney.net/&#34;&gt;Keidra Chaney&lt;/a&gt; has written in Nonprofit Quarterly about &lt;a href=&#34;https://nonprofitquarterly.org/why-nonprofits-need-a-values-based-social-media-strategy/&#34;&gt;the tradeoffs values-driven organizations should consider when developing their social media strategy&lt;/a&gt;. Her article is a must-read and will help you make key decisions that show your audience who you are. After all, the medium is the message.&lt;/p&gt;
&lt;h2 id=&#34;how-to-create-a-campaign&#34;&gt;How to create a campaign&lt;/h2&gt;
&lt;p&gt;Do you have a certain issue or message you need to get the word out about?&lt;/p&gt;
&lt;p&gt;This could be something linked to current events, such as an urgent legal, policy, or human rights issue. Maybe there is a unique and timely opportunity to create momentum and change. Social media is a great fit for this kind of issue, since new posts with a clear call to action will show up on the top of people&amp;rsquo;s feeds.&lt;/p&gt;
&lt;p&gt;However, many important issues are seen as harder to communicate because of a lack of built-in urgency – particularly issues that have been around for a long time and aren&amp;rsquo;t going away anytime soon. A communications campaign can also help here, giving you the opportunity to craft a sharp and timely message.&lt;/p&gt;
&lt;p&gt;This &lt;a href=&#34;https://pjp-eu.coe.int/en/web/human-rights-speech/communicate&#34;&gt;guide from the Council of Europe&lt;/a&gt; is tailored towards human rights organizations will help you plan a campaign around a particular issue.&lt;/p&gt;
&lt;h2 id=&#34;how-to-communicate-with-care-and-safety&#34;&gt;How to communicate with care and safety&lt;/h2&gt;
&lt;p&gt;Many of us need to think about safety when we plan our communications – whether that&amp;rsquo;s the safety of our organization, the safety of the people we serve, or both. Tactical Tech and the Association for Progressive Communication have published &lt;a href=&#34;https://xyz.informationactivism.org/en/zen-art-making-tech-work-for-you/&#34;&gt;these manuals and case studies for how to create safe(r) online spaces&lt;/a&gt;. A must-read, especially if you work near topics such as gender, harassment, sexuality, or sex work.&lt;/p&gt;
&lt;h2 id=&#34;from-social-media-to-movement-building&#34;&gt;From social media to movement-building&lt;/h2&gt;
&lt;p&gt;Let&amp;rsquo;s move beyond clicks, shares, and likes: what is the real-world effect you want to see from your communications?&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.civicus.org/documents/Strengthening_Citizen_Action_Communication_for_Civil_Society_Organisations.pdf&#34;&gt;This guide from Civicus&lt;/a&gt; leads you backwards through designing your communications, starting with the result you want to achieve. We highly recommend this toolkit for anyone who wants to develop their movement and turn ideas into action.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/comms-toolkit&#34;&gt;This toolkit&lt;/a&gt; was developed with the support of the &lt;a href=&#34;https://www.opentech.fund/labs/learning-lab/&#34;&gt;Open Technology Fund Learning Lab&lt;/a&gt;. Got feedback? Want to work together? Please write to us at &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Communications Toolkit for Civic &amp; Nonprofit Tech: Resources for Social Media Posts</title>
      <link>https://superbloom.design/learning/resources/social-media-graphics/</link>
      <pubDate>Tue, 10 Sep 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/social-media-graphics/</guid>
      <description>&lt;p&gt;&lt;em&gt;This resource is part of our &lt;a href=&#34;https://superbloom.design/learning/resources/comms-toolkit&#34;&gt;Communications Toolkit for Civic &amp;amp; Nonprofit Tech&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Finding information online about how to create social media posts can be like drinking from the proverbial firehose. We have selected a few resources we&amp;rsquo;ve found useful when we&amp;rsquo;re making posts for social media. &lt;em&gt;These resources are current as of fall 2024, when this toolkit was published; we&amp;rsquo;ll do our best to keep them up to date.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;assessing-your-social-media-needs&#34;&gt;Assessing your social media needs&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://miro.com/app/board/uXjVMKoSauM=/&#34;&gt;Social media needs assessment template, by Superbloom (Miro)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;audience-definition&#34;&gt;Audience definition&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Our pick for beginners: &lt;a href=&#34;https://okthanks.com/persona-builder&#34;&gt;Persona builder, by Okthanks&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://miro.com/app/board/uXjVMIFHYqo=/&#34;&gt;Audience persona template, by Superbloom (Miro)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://miro.com/app/dashboard/?tpTemplate=behavioral-persona&amp;amp;isCustom=false&amp;amp;share_link_id=212384798363&#34;&gt;Behavioral persona exercise, by Miro team (Miro)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.figma.com/file/wODaaKxGdvL0ggXbKlT2e2/User-Persona-Template?node-id=0-1&amp;amp;t=tWnT70iogZET0T8k-0&#34;&gt;User persona template, by Figma (Figjam)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;competitive-analysis&#34;&gt;Competitive analysis&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://miro.com/app/dashboard/?tpTemplate=competitor-analysis&amp;amp;isCustom=false&amp;amp;share_link_id=955115531366&#34;&gt;Competitive analysis exercise, by Miro team (Miro)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://mailchimp.com/resources/what-is-competitor-analysis/&#34;&gt;How to conduct competitor analysis&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;writing-text&#34;&gt;Writing text&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://buffer.com/library/headline-formulas/&#34;&gt;30 headline formulas for tweets, posts, articles, and emails, by Buffer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://buffer.com/library/ways-to-write-social-media-updates/&#34;&gt;71 techniques for social media updates, by Buffer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://docs.google.com/document/d/15SlUvGNfdL02pQoQxCxVpYaKnDF3WTRf_3ox-9BBz1U/edit?usp=drive_link&#34;&gt;Template: Social media text (Google Docs)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;creating-images&#34;&gt;Creating images&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://miro.com/app/board/uXjVMLagH4k=/&#34;&gt;Template: Social media posts, by Superbloom (Miro)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.brandwatch.com/blog/social-media-image-sizes-guide/#section-7&#34;&gt;Social media image size guide, by Brandwatch&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;If you&amp;rsquo;re tempted to use generative AI for your social media posts, our advice is: nope. &lt;a href=&#34;https://superbloom.design/learning/resources/creating-brand-guidelines#generative-ai&#34;&gt;Here&amp;rsquo;s why&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;planning-and-scheduling&#34;&gt;Planning and scheduling&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://buffer.com/library/schedule-social-media-content-plan/&#34;&gt;Scheduling social media content, by Buffer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://docs.google.com/spreadsheets/d/1BWJY-dsdNrhsh1_frT7L6C-omzle6HvD/edit?usp=drive_link&amp;amp;ouid=106639959202589259575&amp;amp;rtpof=true&amp;amp;sd=true&#34;&gt;Template: Social media calendar, by Superbloom (Google Sheets)&lt;/a&gt; &lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;guidance-for-specific-platforms&#34;&gt;Guidance for specific platforms&lt;/h2&gt;
&lt;h3 id=&#34;linkedin&#34;&gt;LinkedIn&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.linkedin.com/posts/fred-melanson_35-linkedin-secrets-you-need-to-know-activity-7029857413897854976-AEVB?utm_source=share&amp;amp;utm_medium=member_desktop&#34;&gt;35 LinkedIn tips (on LinkedIn, of course)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;instagram&#34;&gt;Instagram&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://blog.hootsuite.com/instagram-best-practices/&#34;&gt;Best practices for growth on Instagram, by HootSuite&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://business.instagram.com/instagram-post-tips&#34;&gt;Creating successful posts on Instagram, by Instagram, naturally&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;general-social-media-guidance&#34;&gt;General social media guidance&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://nonprofitquarterly.org/why-nonprofits-need-a-values-based-social-media-strategy/&#34;&gt;Why nonprofits need a values-based approach to social media, by Keidra Chaney for Nonprofit Quarterly&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.undp.org/eurasia/blog/social-media-tips-for-nonprofit&#34;&gt;10 social media tips for nonprofits, by United Nations Development Programme&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://blog.hootsuite.com/social-media-content-creation/&#34;&gt;Content creation strategy, by HootSuite&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;fundraising-on-social-media&#34;&gt;Fundraising on social media&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.nptechforgood.com/101-best-practices/social-media-statistics-for-nonprofits/&#34;&gt;Social media stats for nonprofits 2024, by Nonprofit Tech for Good&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.societ.com/blog/nonprofit-marketing/how-to-get-started-with-social-media-giving-tools/&#34;&gt;The ultimate social media guide to nonprofit giving tools, by Societ&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
&lt;p&gt;Does social media feel like a lot to take in? Orient yourself by &lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design/&#34;&gt;giving your community and other stakeholders the opportunity to guide you&lt;/a&gt;. Ask them what platforms are most meaningful to them and why. If your loyal boosters like staying caught up on LinkedIn, posting your updates on GitHub may not be reaching as many people as you&amp;rsquo;d like to!&lt;/p&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;p&gt;&lt;em&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/comms-toolkit&#34;&gt;This toolkit&lt;/a&gt; was developed with the support of the &lt;a href=&#34;https://www.opentech.fund/labs/learning-lab/&#34;&gt;Open Technology Fund Learning Lab&lt;/a&gt;. Got feedback? Want to work together? Please write to us at &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Communications Toolkit for Civic &amp; Nonprofit Tech: Scoping Communications Projects</title>
      <link>https://superbloom.design/learning/resources/scoping-communications-projects/</link>
      <pubDate>Tue, 10 Sep 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/scoping-communications-projects/</guid>
      <description>&lt;p&gt;&lt;em&gt;This resource is part of our &lt;a href=&#34;https://superbloom.design/learning/resources/comms-toolkit&#34;&gt;Communications Toolkit for Civic &amp;amp; Nonprofit Tech&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;style&gt;
    .scoping-template tr td.work-area p span, .scoping-template tr td.project-scope p span, .scoping-template tr.project-sml p span {
        font-family: &#34;JetBrains Mono&#34;, &#34;Ubuntu Mono&#34;, &#34;DejaVu Sans Mono&#34;, &#34;Courier New&#34;, Courier, monospace, sans-serif !important; 
        font-weight: 600;
}
    .scoping-template tr td.work-area {
        background-color: #ffffff;
        color: #000000;
        font-family: &#34;JetBrains Mono&#34;, &#34;Ubuntu Mono&#34;, &#34;DejaVu Sans Mono&#34;, &#34;Courier New&#34;, Courier, monospace, sans-serif !important; 
        font-weight: 600;
    }

    .scoping-template tr td.project-scope {
        font-family: &#34;JetBrains Mono&#34;, &#34;Ubuntu Mono&#34;, &#34;DejaVu Sans Mono&#34;, &#34;Courier New&#34;, Courier, monospace, sans-serif !important;
        font-weight: 600;
    }
    .scoping-template tr.project-sml {
        background-color: #424faa;
        color: white;
        font-family: &#34;JetBrains Mono&#34;, &#34;Ubuntu Mono&#34;, &#34;DejaVu Sans Mono&#34;, &#34;Courier New&#34;, Courier, monospace, sans-serif !important;
        font-weight: 600;
        td {
            background-color: #424faa;
            color: white;
        }
        p, span {
        font-family: &#34;JetBrains Mono&#34;, &#34;Ubuntu Mono&#34;, &#34;DejaVu Sans Mono&#34;, &#34;Courier New&#34;, Courier, monospace, sans-serif !important; 
        font-weight: 600;
        }
    }
   .scoping-template tr.project-sml td {
            background-color: #424faa;
            color: white;
    }
&lt;/style&gt;
&lt;p&gt;One of the most daunting parts about undertaking a communications project comes right at the project’s beginning: &lt;strong&gt;planning and scoping the project.&lt;/strong&gt; These projects, by definition, aren’t frequent. You only need to do them once every few years at most. So it makes sense that most organizations don’t have much practice scoping them.&lt;/p&gt;
&lt;p&gt;If you choose to fund and pursue the project internally, you need a sense of not just the expertise required, but also the time investment needed for various results. The &lt;a href=&#34;#identity-project-scoping-template&#34;&gt;scoping templates&lt;/a&gt; we have created can guide you through planning and resourcing your project.&lt;/p&gt;
&lt;p&gt;Engaging external partners is a great option, but that too requires a sense of the project’s scope. Even if you work with external partners, these scoping templates will help you communicate your needs and use the partner’s time efficiently.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Note that we’re using the word “organization” to refer to the group doing the project. Substitute “project,” “group,” “collective,” or any other description that matches you.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;#identity-design-project&#34;&gt;1. Identity project&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;#communications-strategy-project&#34;&gt;2. Communications strategy project&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;#communications-design-project&#34;&gt;3. Communications design project&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;identity-design-project&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h1 id=&#34;identity-design-project&#34;&gt;Identity design project&lt;/h1&gt;
&lt;h2 id=&#34;what-is-an-identity-design-project&#34;&gt;&lt;strong&gt;What is an identity design project?&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;An identity design project has to do with defining the way your organization’s visuals communicate your mission, values, and personality. On a small scale, it involves harmonizing multiple elements that don’t quite hang together. On a larger scale, it involves articulating who you are and creating a visual language that expresses it.&lt;/p&gt;
&lt;p&gt;Depending on the scale and scope of the identity project, you may also need a small, medium, or large &lt;a href=&#34;#communications-strategy-project&#34;&gt;communications strategy project&lt;/a&gt; or &lt;a href=&#34;#communications-design-project&#34;&gt;communications design project&lt;/a&gt;.&lt;/p&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
&lt;p&gt;Doing identity work &lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design/&#34;&gt;together with your community&lt;/a&gt; can be a powerful way to learn and reorient. You may know why &lt;em&gt;you&lt;/em&gt; would like to rebrand and what you would like to communicate, but what do others think? Before you decide on your direction, convene at least a few interviews with people affected by your work. Find out what they like, how they see you, what they think you should be emphasizing in your brand.&lt;/p&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;h2 id=&#34;identity-project-scoping-template&#34;&gt;&lt;strong&gt;Identity project scoping template&lt;/strong&gt;&lt;/h2&gt;
 &lt;table class=&#34;scoping-template toolbox-bottom-table&#34;&gt;
        &lt;thead&gt;
            &lt;tr class=&#34;c19&#34;&gt;
                &lt;td class=&#34;c26 work-area&#34; colspan=&#34;1&#34; rowspan=&#34;2&#34;&gt;
                    &lt;p class=&#34;c21 c18&#34;&gt;&lt;span class=&#34;c4&#34;&gt;&lt;/span&gt;&lt;/p&gt;
                    &lt;p class=&#34;c21&#34;&gt;&lt;span class=&#34;c38&#34;&gt;Work area&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
                &lt;td class=&#34;c16 c49 project-scope&#34; colspan=&#34;3&#34; rowspan=&#34;1&#34;&gt;
                    &lt;p class=&#34;c9&#34;&gt;&lt;span class=&#34;c4&#34;&gt;Project scope&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr class=&#34;c19 project-sml&#34;&gt;
                &lt;td class=&#34;c25 c16&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                    &lt;p class=&#34;c21&#34;&gt;&lt;span class=&#34;c40 c41&#34;&gt;Small &lt;/span&gt;&lt;span class=&#34;c40 c41&#34;&gt;(50-200 hours)&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
                &lt;td class=&#34;c17 c16&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                    &lt;p class=&#34;c21&#34;&gt;&lt;span class=&#34;c40 c41&#34;&gt;Medium &lt;/span&gt;&lt;span class=&#34;c40 c41&#34;&gt;(200-500 hours)&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
                &lt;td class=&#34;c10 c16&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                    &lt;p class=&#34;c21&#34;&gt;&lt;span class=&#34;c4&#34;&gt;Large (500-800 hours)&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
        &lt;tbody&gt;&lt;/tbody&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Goal&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c25&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1 c11&#34;&gt;Fix inconsistencies and technical issues, fill gaps, bring
                        together existing resources&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c17&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1 c11&#34;&gt;Update and modernize identity, expand available assets&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1 c11&#34;&gt;Refresh and redefine identity, reframe position in landscape, a
                        &amp;ldquo;makeover&amp;rdquo;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c39&#34;&gt;Does this work need to be communicated to your community?&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c25&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1 c11&#34;&gt;Probably not. Your identity will look better but not that
                        different.&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c17&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1 c11&#34;&gt;Maybe. Depends on how close you stay to your existing
                        identity.&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1 c11&#34;&gt;Definitely! Make sure you plan time and resources for your rollout. People need to know that you&#39;re still you, just with a new look. If you structure a process that gets input from your community, this can help you communicate the rationale and result behind this work. &lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Brand audit&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c25&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c17&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Name audit&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c25&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c17&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Possibly&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Naming workshop&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c25&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c17&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Possibly&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Logo&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c25&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Technical adjustments, such as different file formats or
                        resolutions&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c17&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Update logo with tweaks and adjustment &amp;mdash;&amp;nbsp;when the logo
                        direction is right but needs visual touch-ups.&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c39&#34;&gt;New or refurbished logo &amp;mdash;&amp;nbsp;&lt;/span&gt;&lt;span
                        class=&#34;c40 c45&#34;&gt;exploring new directions for existing logo&lt;/span&gt;&lt;span class=&#34;c1&#34;&gt;.&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c19&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Color scheme&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c25&#34; colspan=&#34;1&#34; rowspan=&#34;3&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Fixing any styling inconsistencies&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c17&#34; colspan=&#34;1&#34; rowspan=&#34;3&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Adjust and tweak color scheme, fonts, font combinations&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;3&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c40 c45&#34;&gt;New&lt;/span&gt;&lt;span class=&#34;c1&#34;&gt;&amp;nbsp;color scheme, fonts, font
                        combinations &lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c19&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Typography&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c19&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Illustrations, icons, photography&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Visual language&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c25&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Examples of how colors, fonts, illustrations/icons/photos come together
                        in comms materials such as social media posts&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c17&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Examples of how colors, fonts, illustrations/icons/photos come together
                        in comms materials such as social media posts &lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Examples of how colors, fonts, illustrations/icons/photos come together
                        in comms materials such as social media posts&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Market research&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c25&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c17&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
&lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Gathering a few impressions about what similar organizations are doing with their branding.&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Market informed brand design &amp;mdash;&amp;nbsp;studying the landscape&lt;/span&gt;
                &lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Community involvement&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c25&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
&lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Convene a session with some members of your community to get their reaction to your branding – but make it clear that you are only making small tweaks at this point. This session can help you focus on the important aspects for now, and give you ideas for larger projects you might want to undertake later.&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c17&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Convene a session with some members of your community to get their reaction to your branding.&lt;/span&gt;
                &lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Convene several sessions with some members of your community to get their reaction to your branding, structuring your process so that they give feedback and help you make decisions as you go.&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Stakeholder feedback&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c25&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c17&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Maybe&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;1-2 rounds of feedback from internal and/or external stakeholders&lt;/span&gt;
                &lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c26&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c12&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Assets&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c25&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Asset library including:&lt;/span&gt;&lt;/p&gt;
                &lt;ul class=&#34;c37 lst-kix_5tnj66msvj7r-0 start&#34;&gt;
                    &lt;li class=&#34;c6 li-bullet-0&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Brand book&lt;/span&gt;&lt;/li&gt;
                    &lt;li class=&#34;c6 li-bullet-0&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Illustrations (stock selections)&lt;/span&gt;&lt;/li&gt;
                &lt;/ul&gt;
                &lt;p class=&#34;c7 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c17&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Asset library including:&lt;/span&gt;&lt;/p&gt;
                &lt;ul class=&#34;c37 lst-kix_5tnj66msvj7r-0&#34;&gt;
                    &lt;li class=&#34;c6 li-bullet-0&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Brand book&lt;/span&gt;&lt;/li&gt;
                    &lt;li class=&#34;c6 li-bullet-0&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Illustrations (stock selections)&lt;/span&gt;&lt;/li&gt;
                    &lt;li class=&#34;c6 li-bullet-0&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Merch (stickers, tshirts, letterhead&amp;hellip;)&lt;/span&gt;
                    &lt;/li&gt;
                &lt;/ul&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Complete asset library including:&lt;/span&gt;&lt;/p&gt;
                &lt;ul class=&#34;c37 lst-kix_5tnj66msvj7r-0&#34;&gt;
                    &lt;li class=&#34;c6 li-bullet-0&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Brand book&lt;/span&gt;&lt;/li&gt;
                    &lt;li class=&#34;c6 li-bullet-0&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Set of branded illustrations&lt;/span&gt;&lt;/li&gt;
                    &lt;li class=&#34;c6 li-bullet-0&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Merch (stickers, tshirts, letterhead, business
                            card&amp;hellip;)&lt;/span&gt;&lt;/li&gt;
                    &lt;li class=&#34;c6 li-bullet-0&#34;&gt;&lt;span class=&#34;c39&#34;&gt;Set of social media posts&lt;/span&gt;&lt;/li&gt;
                &lt;/ul&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;/thead&gt;
    &lt;/table&gt;
&lt;p&gt;&lt;a name=&#34;communications-strategy-project&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h1 id=&#34;communications-strategy-project&#34;&gt;Communications strategy project&lt;/h1&gt;
&lt;h2 id=&#34;what-is-a-communications-strategy-project&#34;&gt;&lt;strong&gt;What is a communications strategy project?&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;A communications strategy project helps you figure out how to shape your communications process, content, and workflow.&lt;/p&gt;
&lt;p&gt;A small communications strategy project is suitable for an organization that already has defined a clear audience and message, but needs to refine their internal toolkit for delivering the message to the audience. It is also a good fit for organizations that need to communicate a major organizational change (e.g. rebrand, acquisition).&lt;/p&gt;
&lt;p&gt;A larger communications strategy project helps organizations that are not yet clear on their audience and/or message, helping them define their communication goals and create an efficient, effective plan for getting there. A larger communications strategy plan also needs to both contain goals to be achieved, and have a plan for how to evaluate whether those goals are achieved.&lt;/p&gt;
&lt;p&gt;If your organization’s identity is fragmented or you may need to undertake an identity project as well. &lt;a href=&#34;#identity-design-project&#34;&gt;See the “Identity design project” scoping template&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;communications-strategy-project-scoping-template&#34;&gt;&lt;strong&gt;Communications strategy project scoping template&lt;/strong&gt;&lt;/h2&gt;
&lt;table class=&#34;scoping-template toolbox-bottom-table&#34;&gt;
        &lt;thead&gt;
            &lt;tr class=&#34;c19&#34;&gt;
                &lt;td class=&#34;c8 work-area&#34; colspan=&#34;1&#34; rowspan=&#34;2&#34;&gt;
                    &lt;p class=&#34;c21 c18&#34;&gt;&lt;span class=&#34;c4&#34;&gt;&lt;/span&gt;&lt;/p&gt;
                    &lt;p class=&#34;c21&#34;&gt;&lt;span class=&#34;c38&#34;&gt;Work area&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
                &lt;td class=&#34;c16 c29 project-scope&#34; colspan=&#34;3&#34; rowspan=&#34;1&#34;&gt;
                    &lt;p class=&#34;c9&#34;&gt;&lt;span class=&#34;c4&#34;&gt;Project scope&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr class=&#34;c19 project-sml&#34;&gt;
                &lt;td class=&#34;c10 c16&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                    &lt;p class=&#34;c21&#34;&gt;&lt;span class=&#34;c4&#34;&gt;Small project (20-40 hours)&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
                &lt;td class=&#34;c10 c16&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                    &lt;p class=&#34;c21&#34;&gt;&lt;span class=&#34;c4&#34;&gt;Medium project (40-100 hours)&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
                &lt;td class=&#34;c10 c16&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                    &lt;p class=&#34;c21&#34;&gt;&lt;span class=&#34;c4&#34;&gt;Large project (100-300 hours)&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
        &lt;tbody&gt;&lt;/tbody&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c8&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Goal&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Clarify open questions regarding organizational communication;
                        communicate a major change&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Refine messaging, define audiences, streamline internal procedures&lt;/span&gt;
                &lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Create a cohesive set of organizational communication goals; collect
                        resources needed to reach them and evaluate progress&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c8&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Communication strategy audit&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c8&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Audience definition&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c8&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Community interviews&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Maybe&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c8&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Voice and tone guide&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c8&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Social media channel analysis&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Maybe&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c8&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Social media posting calendar&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Maybe&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c8&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Set up, use, and monitor analytics (as well as privacy policy and
                        disclosure!)&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c8&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c39&#34;&gt;Evaluation plan&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c10&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;/thead&gt;
    &lt;/table&gt;
&lt;p&gt;&lt;a name=&#34;communications-design-project&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h1 id=&#34;communications-design-project&#34;&gt;Communications design project&lt;/h1&gt;
&lt;h2 id=&#34;what-is-a-communications-design-project&#34;&gt;&lt;strong&gt;What is a communications design project?&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;A communications design project makes your external communications harmonize with and strengthen your organization’s identity. It concerns templates for reports, presentations, social media posts, and more.&lt;/p&gt;
&lt;p&gt;If your organization doesn’t already have a consistent identity, you may need to undertake an identity project as well. &lt;a href=&#34;#communications-strategy-project&#34;&gt;See the “Identity design project” scoping template&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If your organization hasn’t defined its audience or message, you may need to undertake a communications strategy project as well. &lt;a href=&#34;#communications-strategy-project&#34;&gt;See the “Communications strategy project” scoping template&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;communications-design-project-scoping-template&#34;&gt;&lt;strong&gt;Communications design project scoping template&lt;/strong&gt;&lt;/h2&gt;
&lt;table class=&#34;scoping-template toolbox-bottom-table&#34;&gt;
        &lt;thead&gt;
            &lt;tr class=&#34;c19&#34;&gt;
                &lt;td class=&#34;c36 work-area&#34; colspan=&#34;1&#34; rowspan=&#34;2&#34;&gt;
                    &lt;p class=&#34;c21 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&lt;/span&gt;&lt;/p&gt;
                    &lt;p class=&#34;c21&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Work area&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
                &lt;td class=&#34;c16 c51 project-scope&#34; colspan=&#34;3&#34; rowspan=&#34;1&#34;&gt;
                    &lt;p class=&#34;c47&#34;&gt;&lt;span class=&#34;c4&#34;&gt;Project scope&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr class=&#34;c19 project-sml&#34;&gt;
                &lt;td class=&#34;c42 c16&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                    &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c4&#34;&gt;Small project (10-30 hours)&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
                &lt;td class=&#34;c3 c16&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                    &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c4&#34;&gt;Medium project (30-60 hours)&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
                &lt;td class=&#34;c33 c16&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                    &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c4&#34;&gt;Large project (60-200 hours)&lt;/span&gt;&lt;/p&gt;
                &lt;/td&gt;
        &lt;tbody&gt;&lt;/tbody&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c36&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Goal&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c42&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Apply elements from existing identity to templates for a few specific use
                        cases&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c3&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Create a template library based on an existing identity&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c33&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Create a design system that guides future visual design&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c36&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Presentation templates&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c42&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;If needed&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c3&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c33&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c36&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c39&#34;&gt;Document templates&lt;/span&gt;&lt;span class=&#34;c1&#34;&gt;&amp;nbsp;(letters, proposals,
                        press releases etc&amp;hellip;)&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c42&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;If needed&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c3&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c33&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c36&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Report templates&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c42&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;If needed&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c3&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c33&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c36&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Social media post templates&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c42&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;If needed&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c3&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c33&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c36&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Icons/avatars&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c42&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;If needed&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c3&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c33&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr class=&#34;c5&#34;&gt;
            &lt;td class=&#34;c36&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7&#34;&gt;&lt;span class=&#34;c1&#34;&gt;Design system &lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c42&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c3&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c7 c18&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td class=&#34;c33&#34; colspan=&#34;1&#34; rowspan=&#34;1&#34;&gt;
                &lt;p class=&#34;c2&#34;&gt;&lt;span class=&#34;c1&#34;&gt;&amp;#10004;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;/thead&gt;
    &lt;/table&gt;
&lt;p&gt;&lt;em&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/comms-toolkit&#34;&gt;This toolkit&lt;/a&gt; was developed with the support of the &lt;a href=&#34;https://www.opentech.fund/labs/learning-lab/&#34;&gt;Open Technology Fund Learning Lab&lt;/a&gt;. Got feedback? Want to work together? Please write to us at &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Communications Toolkit for Civic &amp; Nonprofit Tech</title>
      <link>https://superbloom.design/learning/collections/communications-toolkit-for-civic-nonprofit-tech/</link>
      <pubDate>Mon, 09 Sep 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/collections/communications-toolkit-for-civic-nonprofit-tech/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Communications Toolkit for Civic &amp; Nonprofit Tech: Creating Brand Guidelines</title>
      <link>https://superbloom.design/learning/resources/creating-brand-guidelines/</link>
      <pubDate>Mon, 09 Sep 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/creating-brand-guidelines/</guid>
      <description>&lt;p&gt;&lt;em&gt;This resource is part of our &lt;a href=&#34;https://superbloom.design/learning/resources/comms-toolkit&#34;&gt;Communications Toolkit for Civic &amp;amp; Nonprofit Tech&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Before we start: let&amp;rsquo;s talk about storytelling.&lt;/p&gt;
&lt;p&gt;Humans love a good story; for as far back as we know, humans have shared stories with each other in their own communities. At its very core, branding is about storytelling and communication: What story do you want to tell your users, your community, your stakeholders? Ideally, every single element you add to your brand should benefit this unified story you are trying to tell.&lt;/p&gt;
&lt;p&gt;When you are stuck, think of that question: &lt;strong&gt;What is our story?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Now let’s get started!&lt;/p&gt;
&lt;h1 id=&#34;table-of-contents&#34;&gt;Table of contents&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;#brand-guide-elements&#34;&gt;Brand guide elements&lt;/a&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;#brand-background&#34;&gt;Brand background&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#brand-visual-foundation&#34;&gt;Brand visual foundation&lt;/a&gt; // &lt;a href=&#34;#logo&#34;&gt;Logo&lt;/a&gt;, &lt;a href=&#34;#colors&#34;&gt;Colors&lt;/a&gt;, &lt;a href=&#34;#typography&#34;&gt;Typography&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#visual-language&#34;&gt;Visual language elements&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#brand-voice&#34;&gt;Brand voice&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;#formats&#34;&gt;Brand guide formats&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;#accessibility&#34;&gt;Accessibility considerations&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;#color-considerations&#34;&gt;Color considerations&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;#digital-first-logos&#34;&gt;Considerations for digital-first logos&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;#choosing-typeface&#34;&gt;Choosing a typeface&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;#choosing-images&#34;&gt;Choosing images and illustrations&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;#inspiration&#34;&gt;Sources for inspiration&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;brand-guide-elements&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;brand-guide-elements&#34;&gt;Brand guide elements&lt;/h2&gt;
&lt;p&gt;Depending on your organization’s needs, your brand guide might be thorough and extensive or fairly minimal. Here are the elements that you can use in your brand guide to describe and define your brand.&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;brand-background&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;brand-background&#34;&gt;Brand background&lt;/h3&gt;
&lt;p&gt;The brand background is an important part of who you are as a company or an organization, and it’s your chance to get really personal (if you want to). Your brand story could include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The brand name and history:&lt;/strong&gt; How was the brand established? How did you come up with the name?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The brand values:&lt;/strong&gt; What is important to your organization? What are some of the values that members of the organization should ideally strive towards or identify with?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The brand personality:&lt;/strong&gt; What are your brand’s key character traits?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;brand-visual-foundation&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;brand-visual-foundation&#34;&gt;Brand visual foundation&lt;/h3&gt;
&lt;p&gt;The brand visual foundation is an overview of all the core visual elements that make up your brand: logo, colors, and type.&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;logo&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;logo&#34;&gt;Logo&lt;/h4&gt;
&lt;p&gt;Your logo can be a &lt;em&gt;logotype&lt;/em&gt; (which centres around stylised text and is also often referred to as &lt;em&gt;wordmark&lt;/em&gt; or &lt;em&gt;lettermark&lt;/em&gt;), a &lt;em&gt;logomark&lt;/em&gt; (a pictorial mark, i.e. a symbol or image) or a combination of both.&lt;/p&gt;
&lt;p&gt;You may also want to have different versions of your logo to cover all usage: For example, you could use a combination of logotype and logomark as your primary logo, but use only the logomark or symbol in certain situations.&lt;/p&gt;
&lt;p&gt;The more information you include with your logo, the less likely it is that it will be used incorrectly.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Formats&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Provide your logo in a variety of file formats for download (we suggest at least PNG and SVG); this potentially includes different formats for print and digital.&lt;/p&gt;
&lt;p&gt;Have your logo available in several sizes, at least the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;64 x 64 px (for use as an icon or favicon)&lt;/li&gt;
&lt;li&gt;256 x 256 px&lt;/li&gt;
&lt;li&gt;1024 x 1024 px&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Minimum size and spacing&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Your guide should include information about the minimum size of each version of the logo. You might also want to include specifications around spacing — how much space should be left, at minimum, on each side (left, right, top and bottom) of your logo.&lt;/p&gt;
&lt;p&gt;Note: you might want to include here a visual of what this could look like! Here&amp;rsquo;s an example from Firefox.&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/fx_design_logo_masterlogo-space-horizontal-1.svg&#34; alt=&#34;Firefox brand guidelines showing clear space around logo, the height of the F in Firefox&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Correct and incorrect usage&lt;/strong&gt;
It’s always helpful to give pointers on how to correctly use your logo — but also on what incorrect usage looks like.
Some examples:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What colors can or can’t be used for the logo?&lt;/li&gt;
&lt;li&gt;Do you offer black and white variations on the logo? In what situations (e.g. to adapt to a certain site style)?&lt;/li&gt;
&lt;li&gt;Can the logo be placed in a container, a frame, or on a busy background?&lt;/li&gt;
&lt;li&gt;Can the logo be stretched, rotated or resized?&lt;/li&gt;
&lt;li&gt;Are there specific guidelines around using the different versions of the logo (e.g. when do you use the logotype or the logomark?)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Secondary marks and mascots&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;You might also think about creating an additional, recognizable mark such as a secondary logo, a symbol or a mascot. This is either useful in places where your primary logo might not physically fit (for example, in a browser tab), or as an additional way to achieve brand recognition.&lt;/p&gt;
&lt;p&gt;Secondary marks can be an important visual mark of your brand: Just think about the recognisability of mascots like the Duracell Bunny or Ronald MacDonald, Freddie (the Mailchimp chimpanzee) or Duo (the Duolingo owl). As always, consistency is key: those secondary marks are nice-to-haves, but they should also serve a purpose. In the case of mascots, this is often used to add playfulness and personality to your brand!&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;colors&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;colors&#34;&gt;Colors&lt;/h4&gt;
&lt;p&gt;Your color palette should include a variety of colors for different use:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;primary color(s)&lt;/li&gt;
&lt;li&gt;secondary colors&lt;/li&gt;
&lt;li&gt;any additional accent colors&lt;/li&gt;
&lt;li&gt;your background, functional, or neutral colors&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Be clear about which is which, and how to use them, especially when it comes to accessibility, as not every color will fit everywhere or with every other color. Some brands also provide a color ratio for correct usage, i.e. what percentage of each colour type should be used across materials (for example: 50% neutral colors, 30% primary color, 10% secondary, 10% accent). This is useful to make sure your visual content is visually balanced and achieves the mood you want, but it’s in no way necessary.&lt;/p&gt;
&lt;p&gt;It’s good to keep in mind that your colors might be used in different media (digital and print), so provide color codes in different formats — at minimum HEX, RGB and CMYK codes. If you’re using Pantone colors, make sure you have those codes (PMS) in your color library, too.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Colour resources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://colourco.de/&#34;&gt;Colour Code&lt;/a&gt;: A color palette generator&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://mycolor.space&#34;&gt;Color Space&lt;/a&gt;: A generator that creates different types and styles of palettes based on a single colour (HEX code or RGB) input.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;typography&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;typography&#34;&gt;Typography&lt;/h4&gt;
&lt;p&gt;Depending on the media you work in, you might have to work with more or less typefaces, or adapt typefaces to the media you work in. Because of that, it’s good to have basic guidelines and principles in place for how you use typography within your organization and brand. In this section, we’ve collected the most basic information to include when defining guidelines for your brand’s typography.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Give context:&lt;/strong&gt; Which font style is used for what? Or, if you use more than one typeface — when do you use which font?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Think about the medium:&lt;/strong&gt; Do you have different typefaces for different media (digital, print, etc.)? Do you have fallback fonts for when access to your brand typefaces is limited?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Give guidance for presentation:&lt;/strong&gt; Provide specific guidance on how the text should be presented — this includes the text colour, but also what kind of spacing should be used (e.g. vertical spacing between lines or paragraphs), whether you follow a typographic scale, and how copy is aligned within the content (is text centred or left-aligned, or a mix of both?)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Provide setup information:&lt;/strong&gt; How can your typefaces be downloaded, installed, and used?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;visual-language&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;visual-language-elements&#34;&gt;Visual language elements&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;What do we mean by “visual language”?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The visual language is all the visual imagery you use across your brand and materials (apart from your visual foundation). This includes illustrations, photography, and symbols. Often, these are supporting visuals that will expand your brand, bring the point across and, in some cases, make your content more easy to digest and understand. Visual language elements can also be used to bring in an element of fun, where appropriate.&lt;/p&gt;
&lt;p&gt;Like everything in branding: Your visual language might be very simple or quite extensive — there’s no right or wrong way.&lt;/p&gt;
&lt;p&gt;It’s good to draft some guidelines on what type of illustrations or photography you want to use (and avoid), for example:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Usage of imagery:&lt;/strong&gt; What type of imagery (illustration, photography, abstract shapes and symbols, etc.) do you use? If you use different types: Are there rules around when to use which?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Stock imagery:&lt;/strong&gt; Do you use stock images? If so, from which sources, and what are the usage guidelines?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Visual language system:&lt;/strong&gt; Especially if you use abstract shapes — do these shapes follow a pattern or a system? Are they taken from existing elements (like your logo or your organization name)?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Image library:&lt;/strong&gt; Do you provide access to an image library with images that have been “vetted” and can be used / reused?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Making your imagery inclusive:&lt;/strong&gt; Do you consider diversity and inclusion as part of your imagery choice? Do you specifically try to look for a diverse range of images and photographs?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;brand-voice&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;brand-voice&#34;&gt;Brand voice&lt;/h3&gt;
&lt;p&gt;The brand voice is the foundation of how you communicate with your users, stakeholders, and community. It’s important to have a clear idea of the brand voice to make your communication consistent and avoid confusion.&lt;/p&gt;
&lt;p&gt;Some things to consider and questions to ask when defining your brand voice:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Personality:&lt;/strong&gt; What is your brand’s personality?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Humor:&lt;/strong&gt; Is your organization more on the fun or the serious side? Do you bring humor into your communication?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Versatility:&lt;/strong&gt; Do you adapt to the communication platforms you use and to the different types of users you have, or do you keep a similar voice across all communication types?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Specific guidelines:&lt;/strong&gt; Do you use American or British English spelling when communicating? Do you use emojis?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;formats&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;brand-guide-formats&#34;&gt;Brand guide formats&lt;/h2&gt;
&lt;p&gt;There is no right or wrong format for a brand guide; as with everything, it will depend on your audience and your needs and resources.&lt;/p&gt;
&lt;p&gt;Some things you might want to consider before choosing a brand guide format for your organisation:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Who will be using the brand guide?&lt;/li&gt;
&lt;li&gt;Are there any specific needs of the users / designers / developers?&lt;/li&gt;
&lt;li&gt;How often will the brand guide be updated and by whom?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Option 1: PDF&lt;/strong&gt;
Especially for smaller organisations, a static file (usually a PDF) is one of the most common formats for a brand guide. Having a PDF brand guide is easiest when the brand guidelines have already been established and will not be updated regularly (as making changes and exporting the PDF again can quickly become tedious). It might be the best solution for you if you want an easily shareable format that will not need constant updates; you can add it (or a link to it) to your organisation’s centralised knowledge database / system to make sure the latest version is always accessible to everyone.
Note: Make sure your PDFs are versioned, so that when you do make changes to the brand guide, it’s clear from the version name.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Option 2: Brand guide website&lt;/strong&gt;
Having a website for your brand guide is a bit of work, but it might be the most versatile type of format for a brand guide. It can be an internal or password-protected site, but can also be shared externally.
While it might need to be maintained, it will also allow you to be able to add cross-references, links, and embed different types of content. This might be a good solution if you have people who can update / maintain the site, and if you have an extensive brand guide with the needs for cross references.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Option 3: A user-specific platform&lt;/strong&gt;
Many organizations or teams, especially smaller ones, tend to put their brand guide in whatever tool is most accessible to or most used by them. This could be something like Notion or Confluence (a centralized knowledge / documentation tool), Figma (or another design tool), or GitHub/GitLab/Bitbucket (their code repository).
This comes with advantages and disadvantages: A change of tooling might mean having to find a new home for your brand guide; on the other hand, when your brand guide is on a platform your whole team uses regularly, it also means that it’s more likely to be up-to-date than a static document.&lt;/p&gt;
&lt;p&gt;Whatever tool or format you use, make sure you don’t accidentally exclude some of your users — for example, by putting your brand guide in Figma even though it should also be used by developers who might not be using Figma, or even have access to it. This will ensure everyone is on the same page and will avoid information silos.&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;accessibility&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;accessibility-considerations&#34;&gt;Accessibility considerations&lt;/h2&gt;
&lt;p&gt;In order to provide an inclusive and accessible experience for all of your users, it’s essential to think about accessibility at every step of the branding process. Accessibility can help users with permanent or temporary disabilities, but also, for example, users navigating your site on low data plans and bad connections. Often, when thinking about accessibility, we focus on the “obvious”, but text readability and color contrast are only the first step to an accessible brand.&lt;/p&gt;
&lt;p&gt;Here are a few things to consider to make sure you can avoid discriminatory design and biassed branding:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Make your text readable:&lt;/strong&gt; Choose an appropriate text size that also factors in your choice of typeface&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Make your text clear: T&lt;/strong&gt;hink about your users when writing your content, rather than about hypothetical “experts”. Everyone benefits from clear and concise explanations!&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Check your color contrast:&lt;/strong&gt; Use contrast checkers to make sure your brand colors work well together, and that you have alternate colors and a neutral palette to fall back on where needed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Consider screen reader and keyboard users:&lt;/strong&gt; your site should be compatible with screen readers and the content should be easily navigated using a keyboard.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Provide a clear hierarchy for your content:&lt;/strong&gt; Among other things, use semantic HTML — this is particularly helpful for users navigating your site using a screen reader.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Write short and clear alt text for images:&lt;/strong&gt; It’s important to provide alternate text for users with visual impairments or users who might be unable to download or view images on their device, and to learn a bit about how to write alt text that is useful to users and provides the right context&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Provide alternatives for media content:&lt;/strong&gt; Provide an alternative to audio content for people with hearing impairments in the form of  audio descriptions, captions, and transcripts&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Avoid unnecessary animations, autoplay, or flashing content and text:&lt;/strong&gt; video and audio should never start playing on their own, and flashes must be limited to 3 per second for photosensitive viewers.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Consider the importance of inclusive representation:&lt;/strong&gt; Think about the variety and diversity of your users — would they all feel represented by the imagery and photography you have selected?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;color-considerations&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;color-considerations&#34;&gt;Color considerations&lt;/h2&gt;
&lt;p&gt;Colors are a powerful tool in your toolkit. When choosing your brand or organization’s colors, it’s important to think about the context in which color will be used.&lt;/p&gt;
&lt;p&gt;Colors are often associated with certain feelings, moods, or adjectives. The easiest and most obvious example is for the color red, which is often used in Western cultures to signify “Danger” (think of the specific usage of red in road signs and traffic lights).&lt;/p&gt;
&lt;p&gt;Before settling on a specific brand color, it might be beneficial to learn more about color theory (how colors work in the physical world) and color psychology (how colors are perceived by humans).&lt;/p&gt;
&lt;p&gt;Geography, culture and religion will also play a role in your choice of brand colours: depending on where your users, community, stakeholders, etc. are located, are from, or which culture they belong to, they will have formed different associations to certain colors, which is something you will need to be aware of.&lt;/p&gt;
&lt;p&gt;Lastly, what field or area your organization is in, as well as the experience you want to be associated with, might impact your color choices: Think about how many tech and business companies have blue as a primary brand color, or how organizations that focus on the environment often use green in their communication and branding.&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;digital-first-logos&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;considerations-for-digital-first-logos&#34;&gt;Considerations for digital-first logos&lt;/h2&gt;
&lt;p&gt;A digital-first logo should be both simple and versatile. When designing primarily for digital media, you have to deal with different sizes, resolutions and contexts; because of that, your logo should be, first and foremost, recognizable at small sizes (think, a browser tab favicon or app icon), so here are a few tips and questions to think about when creating a digital-first logo.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Use a vector format where you can:&lt;/strong&gt; For example, SVG. This allows you to scale the logo up and down without losing quality.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Use an appropriate format and size:&lt;/strong&gt; This will always work in your favor, as it will positively impact loading speed and image quality, as well as compatibility with devices and platforms. You might not always have the possibility to use a vector format for your logo, but it’s still important to think about falling back on an array of sizes for raster formats (png/jpg).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Avoid too many details:&lt;/strong&gt; When designing an icon at smaller sizes, for example as a favicon, it’s ok to let some details go in favour of readability — adapt your logo as needed so that it’s clean and can be recognized or seen well.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Offer different image ratios:&lt;/strong&gt; it’s important to think about the different contexts of your logo and where it will be seen. It could be that you need different image ratios based on where your logo is used, such as 2:3, 3:4 and 1:1 ratios.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Be prepared:&lt;/strong&gt; Ask yourself an array of questions to be prepared for different situations. Will our logo look good on a small screen and as an app icon? How will it look scaled down to the size of a favicon, on a variety of background colours?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;choosing-typeface&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;choosing-a-typeface&#34;&gt;Choosing a typeface&lt;/h2&gt;
&lt;p&gt;Choosing a typeface might be a daunting task that feels like one of the hardest things in branding; we might not have all the answers, but we have a few thoughts on what can make your typeface decision easier.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Lean into your brand’s style:&lt;/strong&gt; Every typeface has different elements that contribute to  a certain style and visual aesthetic; be aware of this when picking a typeface. You can use your brand’s non-visual foundations to find a typeface that embodies the mood you want to create in your content.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Choose legibility over aesthetics:&lt;/strong&gt; Ideally, the typography should be both readable and visually appealing; unless your style is purposely “messy” or “artsy”, prioritie finding a typeface that is legible.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;When in doubt, use fewer different typefaces or styles:&lt;/strong&gt; An interface, website, or even a print medium can start to look messy fast if there are too many styles and typefaces being used. One of the most difficult things about type is pairing them, so where you can, stay on the minimalist side and think about where the fonts will be used (digital / printed material).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Do a typography audit to help with consistency:&lt;/strong&gt; If your issue is an existing product or interface, try going through all of your content and material, writing down where you’re using which typeface, style, and size. You might uncover some inconsistencies or an overload of variations that can easily be fixed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Free typefaces are totally okay:&lt;/strong&gt; Just because a typeface is free, doesn’t mean it’s bad; and vice-versa, just because you paid a lot of money for a font, doesn’t mean it will serve you well or be perfect for your purpose. There are many free quality typefaces out there!&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Think about your audience:&lt;/strong&gt; Another potential consideration to make is that of accessibility. Will the typeface need accented or non-English characters, diacritic marks, etc? If so you might want to make sure that all of those characters are included in the typeface.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;choosing-images&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;choosing-images-and-illustrations&#34;&gt;Choosing images and illustrations&lt;/h2&gt;
&lt;p&gt;Just like many other aspects of your branding, the imagery you choose will support your message and your story. It’s important to think a bit about the type of images you want to display (or not), the style of photography and illustration you want to use across your brand, and how it reflects and supports your values.&lt;/p&gt;
&lt;p&gt;Sometimes this is really obvious, at times it’s less clear — regardless, it’s always helpful to take a step back and collect your thoughts before jumping into imagery research. This is also the right place for you to have fun, and collect inspiration!
So, while we can’t do the work for you, we can help guide some of your decisions with a few suggestions below.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Make it cohesive:&lt;/strong&gt; Ideally, pick a single illustration style. It doesn’t really matter if it’s found illustration (but don’t forget to credit!) or if you work with an illustrator for custom or bespoke illustrations — the style across all the illustrations you use should be similar enough that it doesn’t confuse your audience.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Have guiding principles around photography:&lt;/strong&gt; It  doesn’t have to be a whole book of guidelines, it’s enough to have one or two guiding principles. For example, “photographs of people will be candid and spontaneous as opposed to posed” or “we will always use a backdrop with one of our primary brand colors for studio photography”.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Explore and experiment:&lt;/strong&gt; Try out different things, brainstorm, and play around. Get a feel for what imagery feels like your brand, and see what’s possible and what isn’t. Especially when it comes to illustrations, there are so many things to consider — shadows, perspective (such as flat vs. 3D), usage of shapes, lines, and colors.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Last but not least, credit where credit’s due:&lt;/strong&gt; Make sure you only ever use photos and graphics that you are allowed to use, and that you credit as originally agreed with the image author. And since working on a team can be chaotic and messy — make sure credit guidelines are saved in the same place where you save your images, as this will definitely avoid some headaches later.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;generative-ai&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;to-ai-or-not-to-ai&#34;&gt;To AI, or not to AI?&lt;/h3&gt;
&lt;p&gt;If you&amp;rsquo;ve gotten this far, chances are you&amp;rsquo;ve tried generating images in your target image style using a generative AI tool (e.g. Midjourney, DALL-E). You may have been shocked by how good the results look, at a cost (to you) of pennies per image. Even so, &lt;strong&gt;we strongly recommend against using generative AI for your brand.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The images won&amp;rsquo;t actually match each other:&lt;/strong&gt; The line weight won&amp;rsquo;t be the same. The color palette will be slightly off. The characters&amp;rsquo; faces won&amp;rsquo;t match from image to image. Even if you use the exact same style keywords and parameters, the generative AI will give results that just don&amp;rsquo;t look quite right with each other.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Yes, people can tell, part 1:&lt;/strong&gt; Generative AI images have a subtle whiff of just not quite making logical sense. Elements are the wrong size, lit wrong, oriented wrong. Brushstrokes don&amp;rsquo;t have a start and an end, phones have three headphone ports, geometric shapes don&amp;rsquo;t have matching angles, every woman looks 23 years old with perfectly clear skin.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Yes, people can tell, part 2:&lt;/strong&gt; Even if the image itself looks fine (no six-finger hands, mismatched glasses lenses, or garbled background text), your use of imagery needs to make sense with your likely budget and staffing. If a 12-person nonprofit posts studio-quality photography on Instagram every day, this smells fishy to your audience.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Are you really ok with this?&lt;/strong&gt; We won&amp;rsquo;t belabor the point here, but the environmental and cultural cost of using generative AI to create &amp;ldquo;art&amp;rdquo; that represents your organization may not be something you want to support. (If you&amp;rsquo;d like to get in touch with great illustrators, we at Superbloom are happy to help!)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;inspiration&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;where-to-find-inspiration&#34;&gt;Where to find inspiration&lt;/h2&gt;
&lt;h3 id=&#34;logo-and-brand-inspiration&#34;&gt;Logo and brand inspiration&lt;/h3&gt;
&lt;p&gt;&lt;a href=&#34;https://bpando.org/&#34;&gt;BP&amp;amp;O&lt;/a&gt; is a regularly updated creative blog with handpicked, high-quality brand designs. It’s not just a collection of cool design, it also offers more context, insights and opinion on each work. You can get site updates sent through a weekly newsletter.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.typewolf.com/&#34;&gt;Typewolf&lt;/a&gt; is a typography resource by designer &amp;amp; art director Jeremiah Shoaf. The site has several interesting sections, including a typography blog, a “site of the day” section (one inspiring site screenshot every day with a description of the typefaces used), and a collection of their favorite portfolio and design studio sites.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://theinspirationgrid.com&#34;&gt;Inspiration Grid&lt;/a&gt; is a huge collection of images from around the web, encompassing design, photography, art and industrial design. If you&amp;rsquo;re looking for &lt;a href=&#34;https://theinspirationgrid.com/category/identity/&#34;&gt;branding&lt;/a&gt; or &lt;a href=&#34;https://theinspirationgrid.com/category/illustration/&#34;&gt;illustration&lt;/a&gt; ideas, this is a great place to start building your moodboard. The sheer size of the site can get overwhelming, and the articles for each piece are usually image-heavy and have minimal amounts of text (i.e. little context about the work) but it’s a great place to see a variety of images.&lt;/p&gt;
&lt;h3 id=&#34;brand-guidelines-and-design-system-inspiration&#34;&gt;Brand guidelines and design system inspiration&lt;/h3&gt;
&lt;p&gt;We’ve collected a few interesting design systems and brand guidelines from around the web.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://brandland.zendesk.com/&#34;&gt;Zendesk brand guidelines&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://mozilla.design/&#34;&gt;Mozilla / Firefox brand guidelines&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.redhat.com/en/about/brand/standards&#34;&gt;Red Hat brand standards&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://wwf-brand.azurewebsites.net/&#34;&gt;WWF brand strategy&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://design.duolingo.com/&#34;&gt;Duolingo brand guidelines&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://ux.mailchimp.com/patterns/color&#34;&gt;Mailchimp pattern library&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://drive.google.com/file/d/1WKkeBOwkE9MdIbqN-Wm4D659bI_y2HWO/view&#34;&gt;Glific style guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.figma.com/file/08usGYMEQR1lyS0s3U6bbI/superbloom_styleguide?t=Hg1G7bn0piEknaEe-0&#34;&gt;Proposed Superbloom style guide (Figma file)&lt;/a&gt; - we used some of this, but not all of it, in our final brand&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/comms-toolkit&#34;&gt;This toolkit&lt;/a&gt; was developed with the support of the &lt;a href=&#34;https://www.opentech.fund/labs/learning-lab/&#34;&gt;Open Technology Fund Learning Lab&lt;/a&gt;. Got feedback? Want to work together? Please write to us at &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Communications Toolkit for Civic &amp; Nonprofit Tech: The Brand Development Process</title>
      <link>https://superbloom.design/learning/resources/brand-development-process/</link>
      <pubDate>Mon, 09 Sep 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/brand-development-process/</guid>
      <description>&lt;p&gt;&lt;em&gt;This resource is part of our &lt;a href=&#34;https://superbloom.design/learning/resources/comms-toolkit&#34;&gt;Communications Toolkit for Civic &amp;amp; Nonprofit Tech&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;When you hear the word “brand,” you might think of commercial products, not civic and nonprofit tech.&lt;/p&gt;
&lt;p&gt;You might be surprised to hear us say that your organization needs a brand, too – otherwise you&amp;rsquo;ll end up with a patchwork &amp;ldquo;brand&amp;rdquo; made up of mismatched elements you didn&amp;rsquo;t plan, and it might not send the right message.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A brand is a structured, consistent way to use words and media.&lt;/strong&gt; When it&amp;rsquo;s working well, it uses these elements to express the values, purpose, and mission of a product or organization. Using an appropriate brand dramatically increases the trust that others will put in you – whether that be your community, your funders, or potential collaborators. (&lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails/&#34;&gt;Here&amp;rsquo;s a case study on our work with the Linux distribution Tails to develop their brand.&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;If you are not starting your brand from scratch, you may not need all the steps outlined below. You may have done some of the work already. However, if you haven’t yet done work to define your organization or tool’s mission and vision, please do not skip it! You may end up with a brand that looks pretty, but doesn’t actually communicate your values and purpose effectively. You can find more about branding in our &lt;a href=&#34;https://superbloom.design/learning/resources/creating-brand-guidelines&#34;&gt;guide to creating brand guidelines&lt;/a&gt;.&lt;/p&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
&lt;p&gt;We strongly recommend &lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design/&#34;&gt;involving your community in the branding process&lt;/a&gt;. They know things about your image, your reputation, and your communication style that you can&amp;rsquo;t possibly see from the inside. There are lightweight ways to involve community, and also more intensive models - what&amp;rsquo;s right for you depends on the scope of the project and also the availability and interest of community members.&lt;/p&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;h3 id=&#34;where-to-start&#34;&gt;Where to start?&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;What do you need? How much money do you have? How much budget do you have?&lt;/em&gt; These three questions will guide the nuts and bolts of your brand design process.&lt;/p&gt;
&lt;p&gt;In general, design professionals use the following steps to develop a brand.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;#scoping&#34;&gt;Scoping&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#positioning&#34;&gt;Positioning&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#brand-audit&#34;&gt;Brand audit&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#market-research&#34;&gt;Market research&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#stakeholder-research&#34;&gt;Stakeholder research&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#moodboard&#34;&gt;Moodboard&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#brand-design&#34;&gt;Brand design&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#review-feedback&#34;&gt;Review and feedback&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#brand-design-system&#34;&gt;Brand design system&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/brand-identity-project-process-1-_hu_8f8cfe9886fecd07.png&#34; alt=&#34;Flowchart. Begins with Discuss project needs and requirements, arrow points to Create a project scope, budget and timeline, next arrow points to Discovery workshop. An arrow to the side points to Share synthesis. Arrow points from Discovery workshop to Collect brand identity collateral, next arrow points to Brand identity audit, an arrow to the right points to Share Findings. The next arrow points from Brand identity audit to Market and Stakeholder Research. The next arrow points from that to Mood board. An arrow to the side points from Mood board to Discuss and collect feedback, and there is also an arrow pointing from this back to Mood board, putting the two labels in a cycle. An arrow points from Mood Board to Brand Identity Design, and an arrow points to the side to Review and Collect Feedback. These two labels are also linked in a cycle. The next arrow leads from Brand Identity Design to Design System, and the last arrow from Design System to Handoff and Coaching. &#34; width=&#34;740&#34; height=&#34;825&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;scoping&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;scoping&#34;&gt;Scoping&lt;/h4&gt;
&lt;p&gt;Before you get started, you&amp;rsquo;ll need to understand the size and scope of the project you&amp;rsquo;re taking on. This questionnaire will help you understand high level requirements of the project so you can set up the right activities, processes, and timelines.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://docs.google.com/document/d/1Fy_aiSmtfdU-43l8zsfA452UOoDGdAmdumMbLm_Tot8/edit?usp=drive_link&#34;&gt;Questionnaire: High level scoping tool for brand development&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;positioning&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;positioning&#34;&gt;Positioning&lt;/h4&gt;
&lt;p&gt;Positioning refers to how people think about you in relation to other, similar organizations. Compared to others in your space, are you the big one, the small and nimble one, the quiet and serious one, the raucous one? To understand and create your position, you need to understand both who you already are, and who you&amp;rsquo;d like to become.&lt;/p&gt;
&lt;p&gt;A positioning workshop should include people who understand the organization really well, such as the founding team and the current leadership.&lt;/p&gt;
&lt;p&gt;Budgets and timelines may also affect the workshop. Hence, add or remove workshop activities as per your needs and the answers you are seeking. For example, if you know your audience well and have already documented it, then feel free to remove that from the workshop. Pick activities from the templates to reflect what you hope to learn about the project during the needs assessment workshop.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;If you’re creating a new activity for your workshop which may benefit others, please share it with us! Write us at &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://miro.com/app/board/uXjVMdUeHFs=/&#34;&gt;Brand positioning workshop template (Miro link)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;brand audit&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;brand-audit&#34;&gt;Brand audit&lt;/h4&gt;
&lt;p&gt;Collect all your brand collateral in one place: logos, letterheads, website screenshots, whatever you have. Look at it all together, and identify opportunities for improvement.&lt;/p&gt;
&lt;p&gt;Use insights from the brand positioning workshop as a part of this exercise to set criteria for analysis. For example, if you figured out that your organization wants a playful visual style, then analyze the brand for playfulness.&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;market research&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;market-research&#34;&gt;Market research&lt;/h4&gt;
&lt;p&gt;Understand the landscape that your brand exists in by studying the organizations that work in the same domain and the organizations that the target audience is influenced by. Do a brief landscape map during needs assessment workshop, then follow it up with a more in-depth examination if you feel that would help.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://miro.com/app/dashboard/?share_link_id=212384798363&#34;&gt;Behavioral persona for describing your audience, by Miro (Miro link)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.figma.com/file/wODaaKxGdvL0ggXbKlT2e2/User-Persona-Template?node-id=0-1&amp;amp;t=tWnT70iogZET0T8k-0&#34;&gt;User persona for describing audience members, by Figma (Figjam link)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://miro.com/app/dashboard/?tpTemplate=41794e58-ab14-4f62-be3e-5c23194e3fb1&amp;amp;isCustom=false&amp;amp;share_link_id=965730463424&#34;&gt;Competitive analysis, by Miro (Miro link)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://mailchimp.com/resources/what-is-competitor-analysis/&#34;&gt;What is competitive analysis? Article by Mailchimp&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;stakeholder research&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;stakeholder-research&#34;&gt;Stakeholder research&lt;/h4&gt;
&lt;p&gt;Learn what others think of your organization – we can tell you that you will be surprised, and it&amp;rsquo;s often a nice surprise, since we are our own worst critics!&lt;/p&gt;
&lt;p&gt;Important stakeholders include the people you hope to impact, people who support you, funders, and employees/team members. Get feedback from them on any previous existing brand assets, and ask questions to understand how they perceive the brand and organization.&lt;/p&gt;
&lt;p&gt;Suggested activities include interviews, either short or longer, and questionnaires. You may also find these Miro boards useful to make sense of the information you gather:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://miro.com/app/board/uXjVMSqd5-c=/&#34;&gt;Audience map (Miro link)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://miro.com/app/board/uXjVPxc6ETo=/&#34;&gt;Synthesis board (Miro link)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;moodboard&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;moodboard&#34;&gt;Moodboard&lt;/h4&gt;
&lt;p&gt;An essential step for most branding projects, a moodboard will help to explore a visual direction for the brand. You will collect images that you like in order to create an inspiration guide for your visual style. Gather examples from food, fashion, art, and your daily life – not just from other tech tools and organizations!&lt;/p&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
&lt;p&gt;Creating a moodboard can be a great exercise to do &lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design/&#34;&gt;together with your community&lt;/a&gt;. Just make sure you also take time to focus, or make decisions, after you&amp;rsquo;ve done your creative brainstorming together.&lt;/p&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.figma.com/board/1dZdm1JlMFrmyiC787G9Sp/Moodboard-template?node-id=0-1&amp;amp;t=VWiMpcqJXy9hmGAb-1&#34;&gt;Moodboard template by Figma (FigJam link)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;brand design&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;brand-design&#34;&gt;Brand design&lt;/h4&gt;
&lt;p&gt;After all this research and planning, it is finally time for creative development! This is where you put pencil to paper: define the brand direction, sketch logo ideas, build a brand narrative, apply the moodboard to sketches, and create a brand design.&lt;/p&gt;
&lt;p&gt;If you have been working with an external designer, they will provide a lot of support and ideas here. It&amp;rsquo;s reasonable to ask for several directions, so that you can discuss them together and decide what works best.&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;review-feedback&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;review-and-feedback&#34;&gt;Review and feedback&lt;/h4&gt;
&lt;p&gt;Arrange review sessions where the people working on the project can present the brand design and synthesis and get reactions. Always present the background work and the rationale, not just the visuals! You want people to react based on whether the brand communicates the desired message, not just on whether they &amp;ldquo;like it&amp;rdquo; or not.&lt;/p&gt;
&lt;p&gt;You don&amp;rsquo;t need to wait until everything is done. Feedback is useful even if the work is only 80% or so complete.&lt;/p&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
&lt;p&gt;We are huge fans of &lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design/&#34;&gt;involving your community in this process&lt;/a&gt;. However, we really do &lt;em&gt;not&lt;/em&gt; recommend getting opinions on a brand in progress on social media or via a public poll, even if you usually work in the open. People will react to your work in isolation without knowing the &amp;ldquo;why&amp;rdquo; behind it, and the result won&amp;rsquo;t tell you anything about which logo or color scheme is actually better for what you need. Much better to convene a session of community members, lead them through the background and goal of your project, and then ask them if your design ideas are actually doing the job.&lt;/p&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;p&gt;&lt;a name=&#34;brand-design-system&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;brand-design-system&#34;&gt;Brand design system&lt;/h4&gt;
&lt;p&gt;This is the final output and deliverable. It describes the story and rationale behind the logo, colors, typeface, illustrations, and visuals, linking them to the organization’s brand values. It also gives instructions on how and why to use all components.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.figma.com/design/lDtyBAC6vAuhtldg3WeHFB/%5BOrgname%5D_styleguide-Template?node-id=0-1&amp;amp;t=4clNj0eTb4NMe8Wc-1&#34;&gt;Style guide template (Figma file)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;For example style guides, see &lt;a href=&#34;https://superbloom.design/learning/resources/creating-brand-guidelines/&#34;&gt;the guide to creating brand guidelines&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;p&gt;Brands need to be designed, and then they need to be put into practice. Now that you&amp;rsquo;ve designed your brand, you can get started on implementing it.&lt;/p&gt;
&lt;p class=&#34;customTable&#34;&gt;One of the quickest ways to see results is by creating some templates. Here are some templates for commonly used communications collateral.&lt;/p&gt;
&lt;table class=&#34;toolbox-bottom-table&#34;&gt;
  &lt;thead&gt;
      &lt;tr&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;Resource&lt;/th&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;To help you with&lt;/th&gt;
      &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/social-media-graphics&#34;&gt;Guide: Social media graphics&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Creating, researching, planning and publishing content on social media.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/document/d/15SlUvGNfdL02pQoQxCxVpYaKnDF3WTRf_3ox-9BBz1U/edit#heading=h.755hrdox3z68&#34;&gt;Template: Social media text (Google Docs)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Planning your text for social media.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://miro.com/app/board/uXjVMLagH4k=/?share_link_id=558690864957&#34;&gt;Template: Social media visuals (Miro)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Preparing images in the recommended sizes before you post.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/document/d/1vUq-4xaPw5ZZHtQcwDyOPXHMNLUyghVYKES0kDIOOVg/edit?usp=drive_link&#34;&gt;Questionnaire: Tone &amp;amp; voice (Google Docs)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Establishing a consistent and impactful tone and voice in your communications efforts.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/presentation/d/1g-uKI2UGdCx9S7sE26r6hyV0P0rHxDwGd87BiMS44zI/edit?usp=drive_link&#34;&gt;Template: Lightning talk (Google Slides)&lt;/a&gt;&lt;/td&gt;
          &lt;td&gt;&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/presentation/d/1LrcWgD4Aagbo-JOBjlSkJlOvrRHn-heYEM8z16BWdYw/edit?usp=drive_link&#34;&gt;Template: Organizational overview (Google Slides)&lt;/a&gt;&lt;/td&gt;
          &lt;td&gt;&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/presentation/d/1Vb76PyIqQ3CzUWU-pbUjRt5efoXG07eJFWu3OAGp_6Y/edit?usp=drive_link&#34;&gt;Template: Research shareout (Google Slides)&lt;/a&gt;&lt;/td&gt;
          &lt;td&gt;&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/document/d/1yftME-d9EZxAxoxQfQ51mbhmtRu-6AXO1f5emnTILkI/edit?usp=drive_link&#34;&gt;Template: Report (Google Docs)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Creating a report with ready-to-use formatting. Insert your own fonts and colors.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/document/d/1KNHTTzDREANkMbqb61osQHRQI-etGpRcv26xiKIAocs/edit?usp=drive_link&#34;&gt;Template: Press release (Google Docs)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Creating a press release with ready-to-use formatting. Insert your own fonts and colors.&lt;/td&gt;
      &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&lt;em&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/comms-toolkit&#34;&gt;This toolkit&lt;/a&gt; was developed with the support of the &lt;a href=&#34;https://www.opentech.fund/labs/learning-lab/&#34;&gt;Open Technology Fund Learning Lab&lt;/a&gt;. Got feedback? Want to work together? Please write to us at &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Design Contributions to OSS at COSCUP 2024</title>
      <link>https://superbloom.design/learning/blog/design-contributions-to-oss-at-coscup-2024/</link>
      <pubDate>Thu, 05 Sep 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/design-contributions-to-oss-at-coscup-2024/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_design_contributions_oss_coscup_2024_1_hu_d1dc6306c478d2f3.png&#34; alt=&#34;A group of 7 Taiwanese designers are gathered around a table with laptops, papers and sticky notes on the table. One person holds a microphone and speaks about the project that the group decided to work on making contributions to. In the background, two other tables of designers are visible&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;At COSCUP 2023, we held a workshop “The Design We Open - Network Disruption Hackathon” (The Design We Open Workshop - 網路中斷黑客松), a workshop focused on how we - as designers and configurers of technology for human rights needs - can better understand Taiwanese citizens. &lt;a href=&#34;https://superbloom.design/learning/blog/open-design-workshop-at-coscup-2023-understanding-internet-shutdowns-and-how-design-can-improve-tools/&#34;&gt;Read the 2023 blog here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://coscup.org/2024/en/&#34;&gt;COSCUP&lt;/a&gt; is a large, international conference for open source coders, users and promoters. COSCUP has a large Taiwanese, East-Asian and South-East Asian attendance base and is growing, which demonstrates how critical the event is to the wider OSS ecosystem and the OSS decentering of conversations from western Europe and the United States.&lt;/p&gt;
&lt;p&gt;In 2024 we returned to COSCUP to hold another workshop focussed on designers making a contribution to an OSS project: “Designers in Tech-Open Source Design Workshop”, and you can find the open whiteboard canvas hosted on the Superbloom Miro account &lt;a href=&#34;https://bit.ly/COSCUP-2024&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;workshop-aims&#34;&gt;Workshop aims&lt;/h2&gt;
&lt;p&gt;The workshop brought together participants from diverse backgrounds to collaboratively address issues in civic tech, privacy, security, and human rights-focused OSS tools. Attendees were primarily designers, but also developers, product managers and document writers. Superbloom selected OSS projects from previous projects, and those with Taiwan-specific civic challenges. The Superbloom team ensured that the OSS projects it reached out to were able to actively participate before, during and after the workshop. The team supported the projects in detecting potential tasks in the projects’ public code repositories (where tasks and progress is tracked by most OSS projects) and initiated discussion using these suggestions. The OSS projects were then able to add additional information, resources and additional or alternative challenges for the designers to work on during the workshop.&lt;/p&gt;
&lt;p&gt;The workshop was structured to ensure that participants - especially those new to OSS contributions - could effectively engage and make design contributions. It featured a series of guided activities and exercises, focusing on understanding the OSS tasks, and digesting user research and usability needs identified in existing OSS projects. The Superbloom staff and volunteers provided experience in design, UI/UX and product management in OSS, and supported participants and guided them when requested.&lt;/p&gt;
&lt;h2 id=&#34;key-objectives-of-the-workshop&#34;&gt;Key objectives of the workshop&lt;/h2&gt;
&lt;p&gt;The workshop’s key objectives included:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Demystifying non-code contributions&lt;/strong&gt;: Educating participants about how to translate developer issues into design briefs and make meaningful design contributions to OSS projects.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Facilitating hands-on contributions&lt;/strong&gt;: Ensuring each participant, as part of a larger group, makes a tangible design contribution to an OSS project by the end of the workshop.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Promoting ongoing engagement&lt;/strong&gt;: Providing resources and documentation to encourage continued contributions from designers to OSS projects post-workshop.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Adding value&lt;/strong&gt;: Ensuring the design has a valued and prominent place in the configuring, discussion and building of open source technology globally and is not overlooked as an essential part of the process of meaningful and citizen relevant technology.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;preparing-for-a-design-contribution-workshop&#34;&gt;Preparing for a design contribution workshop&lt;/h2&gt;
&lt;p&gt;We wanted to offer a different kind of workshop to that we offered back in 2023. The 2023 “Network Disruption Hackathon” for designers was well received and enjoyed by participants and had a focus on vital OSS technologies that help people in internet shutdown and internet censorship situations. However, this workshop had a lower impact on the OSS projects and a higher impact on the designers and citizens in terms of access to new knowledge and OSS tools. In 2024, we wanted to ensure tangible design contributions to selected OSS.&lt;/p&gt;
&lt;p&gt;With this focus, we built the workshop activities around four key pillars:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Understanding the roles and responsibilities in OSS and the skills and expertise designers can offer OSS.&lt;/li&gt;
&lt;li&gt;Deep user research examples to inform and speed up the knowledge gap that the designers may have of users of censorship circumvention, privacy and security OSS tools.&lt;/li&gt;
&lt;li&gt;Understanding and translating issues (tasks or needs) typically written by coders and OSS maintainers in “OSS coder language” and extrapolating the design to understand the need from these.&lt;/li&gt;
&lt;li&gt;Providing optional templates for design contributions to these issues. From high threat anti-persona exploration and empathy maps to heuristic evaluation breakdowns and user testing script templates.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;These four pillars all focussed on the ultimate (and challenging) goal of making a design contribution during the course of a single day hackathon.&lt;/p&gt;
&lt;p&gt;In preparation for the event we explored many of the OSS projects that Superbloom has previously been involved with as well as OSS projects that are Taiwan-native and grown. &lt;/p&gt;
&lt;p&gt;We wanted to ensure these OSS projects had a clear set of criteria including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Open and welcoming of design and design contributions during and after the ‘Designers in Tech-Open Source Design Workshop’. (Two developers from two different OSS projects even attended to give on-site support!)&lt;/li&gt;
&lt;li&gt;Reasonably easy to understand issues/tasks accessible from a public location that designers with limited knowledge of the OSS could make first contributions to.&lt;/li&gt;
&lt;li&gt;Reasonably easy to understand and present a system of documentation and/or clear explanation of the OSS intended purpose and user base.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A bonus criteria was that each of these tools were familiar to Superbloom workshop team members, either via previous work completed by Superbloom on the tools or through previous voluntary contributions.&lt;/p&gt;
&lt;h2 id=&#34;workshop-activities-and-differences-from-2023&#34;&gt;Workshop activities and differences from 2023&lt;/h2&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_design_contributions_oss_coscup_2024_2_hu_159e2098a2b98a60.png&#34; alt=&#34;An image of various papers, sharpie pens, stickers and blank sticky notes piled on a table. These papers have both English and Mandarin translations of the exercises and content of the workshop.&#34; width=&#34;740&#34; height=&#34;554&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;introductions-and-ice-breaker&#34;&gt;Introductions and ice breaker&lt;/h3&gt;
&lt;p&gt;This workshop began with brief introductions and agenda setting and we launched into our first active session which also served as an icebreaker exercise.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_design_contributions_oss_coscup_2024_3_hu_b16659a438b43252.png&#34; width=&#34;740&#34; height=&#34;415&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_design_contributions_oss_coscup_2024_4_hu_5e080feecff05975.png&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;p&gt;The goal of this exercise was to share skills with others in the room with a focus on what skill you want to teach others, what skill you feel confident offering as a contribution to OSS, and what skill you want to learn more about. Attendees could learn about the skills of those in the room, and as we requested people gather in groups of 5-7, they could also self-assign skill sets per group if they wished.&lt;/p&gt;
&lt;h3 id=&#34;forming-groups-and-learning-about-each-others-skills&#34;&gt;Forming groups and learning about each other’s skills&lt;/h3&gt;
&lt;p&gt;After groups were formed, the additional meaning of this exercise was revealed. In OSS nobody in the OSS project would know what it was possible a team member could do, wanted to do and wanted to learn more about unless those skills are clearly communicated. Design is generally an under-served skill in OSS and it’s even more important for designers to be familiar and be comfortable with describing their skills and what they want to contribute and why. This benefits the OSS ecosystem’s knowledge base of design, designers, and the skills that designers bring.&lt;/p&gt;
&lt;p&gt;Once everyone had settled into groups we moved onto core preparation exercises, the first being a deep review of user research prepared by Superbloom, and based on our expertise and previous user research insight into the world of OSS, privacy, security and mis/disinformation. &lt;/p&gt;
&lt;h3 id=&#34;talking-about-the-tools&#34;&gt;Talking about the tools&lt;/h3&gt;
&lt;p&gt;Both Superbloom and the OSS maintainers prepared User Personas, User Journeys and User Scenarios, and offered spoken insight into the use and purpose of the OSS tools. Ceno and Co-facts team members who were present on-site talked about their tech solutions and provided detailed information about their work.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_design_contributions_oss_coscup_2024_5_hu_386d32d5aae46ea0.png&#34; alt=&#34;An example user person showing the ‘OSS Activist’ detailing their needs, actions, wants and what could harm them in both implicit and explicit ways.&#34; width=&#34;740&#34; height=&#34;534&#34;&gt;
&lt;/p&gt;
&lt;p&gt;After spending time digesting this information and discussions in groups, we moved onto the next core preparation exercise, looking at the available issues and using a guiding template to translate the issues from a “developer/coder” focused issue to a “designer/user” focused issue.&lt;/p&gt;
&lt;p&gt;The template takes the groups through a few key questions such as “Please describe the problem from at least one “user’s” point of view” and “What is success for our user/s?”. Issues in OSS that are written from “coder” or “engineering” perspectives are often technical solutions focused on how they are written, and rarely explore or mention what broad and researched user expectations, needs and success mean. This is where designers, using their background, user insight and deduction skills can begin to contribute immense value to OSS.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_design_contributions_oss_coscup_2024_6_hu_5e4b0314045a24c5.png&#34; alt=&#34;An example of the issues selected for the Cofacts project which is a LINE app bot and api service that helps citizens in Taiwan report and crowdsource information on content to find out if it could be misinformation, disinformation or online scams.&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;participants-picked-the-issues-they-wanted-to-work-on&#34;&gt;Participants picked the issues they wanted to work on&lt;/h3&gt;
&lt;p&gt;The groups spent time with six different issues across three different OSS projects and came to a group decision about which one they wanted to tackle in the remaining time. We ended up with at least one team focussing on each OSS project across different “scales” of problem. These ranged from helping make user interface elements clearer and informative to making sure users can make well-informed settings choices for their privacy and security needs.&lt;/p&gt;
&lt;h3 id=&#34;hands-on-time-making-design-contributions&#34;&gt;Hands-on time, making design contributions&lt;/h3&gt;
&lt;p&gt;After making their choices, the groups moved onto the main section of the workshop about their design contributions to these issues. Superbloom prepared a number of different templates for contributions should workshop attendees struggle to find a format they wished to contribute to, or if they wished to divide up a number of connected contributions to the same issue. &lt;/p&gt;
&lt;p&gt;These templates were:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;A persona non-grata (or adversarial personas) template&lt;/strong&gt;. An exercise that helps OSS tools understand how a tool, feature or situation can be used maliciously by a particular kind of user with bad intentions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Two heuristic analysis / UX review of OSS tool statements&lt;/strong&gt;. This is a way for tool teams and designers to locate usability and design issues within an interface. Heuristics act as guidelines or ideals toward which we hope all interfaces can strive that make systems safe and easy to use.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;User Empathy maps&lt;/strong&gt;. These maps help an OSS project better understand the motivations and drives of users generally or in specific scenarios.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;User Testing/User Research script primer&lt;/strong&gt;. This helps the designer and OSS project begin to lay out how they can user test a particular feature or aspect of the functionality of their OSS.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open/tree/main/design-contribution-templates&#34;&gt;You can find the templates in our open repository here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_design_contributions_oss_coscup_2024_7_hu_d9e724d64bb61a83.png&#34; alt=&#34;Mandarin version of the first page of our user testing template for OSS design contributions.&#34; width=&#34;740&#34; height=&#34;1030&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_design_contributions_oss_coscup_2024_8_hu_5fbb685ef5d9b704.png&#34; alt=&#34;English version of the persona non-grata template for OSS design contributions.&#34; width=&#34;740&#34; height=&#34;1030&#34;&gt;
&lt;/p&gt;
&lt;p&gt;The teams then had two and half hours to make their contribution and submit them to the OSS projects to issue before the end of the workshop.&lt;/p&gt;
&lt;p&gt;All teams made their contributions before the end of the workshop, and you can see the results here:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://github.com/cofacts/open165/issues/7&#34;&gt;For Cofacts 165 reporting spam in Taiwan issue&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://gitlab.com/censorship-no/ceno-browser/-/work_items/74&#34;&gt;For Ceno to ensure users understand know about privacy and consent &lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://github.com/oxen-io/session-android/issues/1595&#34;&gt;For Session to ensure users understand when messages and media have been shared from a private message thread&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;translations-to-mandarin-and-open-resources&#34;&gt;Translations to Mandarin and open resources&lt;/h2&gt;
&lt;p&gt;All the resource templates, slides and content was translated into Mandarin by our dedicated and valued volunteer Tofus (&lt;a href=&#34;https://github.com/Tofuswang&#34;&gt;GitHub&lt;/a&gt; and &lt;a href=&#34;https://x.com/tofuswang&#34;&gt;Twitter&lt;/a&gt;). He joined us as a valued and trusted volunteer at the workshop, and helped attendees to make these first contributions to OSS. He has spent a number of years as a member of &lt;a href=&#34;https://g0v.tw/&#34;&gt;g0v Taiwan&lt;/a&gt; making sure that design has a clear and consistent presence in the OSS projects there. Thank you Tofus 💐. &lt;/p&gt;
&lt;p&gt;We’d also like to thank Julia Liu for her incredible contribution of translating English to Mandarin live for the participants during the workshop. &lt;/p&gt;
&lt;p&gt;We’d also like to thank and mention &lt;a href=&#34;https://www.linkedin.com/in/ossianlin19739513/&#34;&gt;Yu-Jung Lin&lt;/a&gt;’s &lt;a href=&#34;https://medium.com/sekkei-tori-seikatsu/collaborative-design-into-open-source-communities-5b389c6f2c70&#34;&gt;Medium article&lt;/a&gt; from the perspective of a workshop attendee.&lt;/p&gt;
&lt;h2 id=&#34;designers-in-oss-challenges-and-next-steps&#34;&gt;Designers in OSS: challenges and next steps&lt;/h2&gt;
&lt;p&gt;Designers face both familiar and unique challenges when contributing to OSS. Ensuring that there is sufficient clarity and time to spend on an issue in order to make a contribution is critical. The intended benefit of these workshops is that it pools peer support of fellow designers and OSS technologists to quickly answer or address the lack of clarity that most OSS projects can have around user needs.&lt;/p&gt;
&lt;p&gt;Another aspect of these workshops that is very difficult or impossible to find in the more common, online, distributed ways of contributing to OSS is that designers lack the opportunity to discuss user insight when online and isolated, and to share broader knowledge/experience and iterate on their ideas with one another. OSS repository hosts sites do not offer a way for design “outputs” (UI, UX, written research, graphics etc.) to be “commented on and &lt;a href=&#34;https://www.perforce.com/blog/vcs/branching-definition-what-branch&#34;&gt;branched&lt;/a&gt;” similar to and common to code in OSS. By gathering designers in person it is possible to facilitate that process without the need for software “hacks” online. &lt;/p&gt;
&lt;p&gt;In person events make design and designers more visible in the OSS space. It makes it possible to build camaraderie, friendships and community within OSS and with other design practitioners. We hope this leads to a healthier flow of people and skills coming into the OSS community.&lt;/p&gt;
&lt;p&gt;These insights and many more like them can also be found in our project blog post: &lt;a href=&#34;https://superbloom.design/learning/blog/the-secret-life-of-open-source-designers/&#34;&gt;&amp;ldquo;The Secret Life of Open Source Designers&amp;rdquo;&lt;/a&gt;. This study looked at designers&amp;rsquo; experiences contributing to OSS over a period of 16 weeks.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;If you’d like to run a similar workshop at an OSS event and would like to use our resources, you can find them in our open and free repository here: &lt;a href=&#34;https://github.com/sprblm/The-Design-We-Open&#34;&gt;https://github.com/sprblm/The-Design-We-Open&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project contributors: &lt;a href=&#34;https://superbloom.design/&#34;&gt;Superbloom&lt;/a&gt;, &lt;a href=&#34;https://coscup.org/&#34;&gt;COSCUP&lt;/a&gt;, &lt;a href=&#34;https://www.ntust.edu.tw/home.php?Lang=en&#34;&gt;National Taiwan University of Science and Technology&lt;/a&gt;, &lt;a href=&#34;https://getsession.org/&#34;&gt;Session&lt;/a&gt; app, &lt;a href=&#34;https://censorship.no/en/index.html&#34;&gt;Ceno Browser&lt;/a&gt; (&lt;a href=&#34;https://equalit.ie/&#34;&gt;eQualitie&lt;/a&gt;) and &lt;a href=&#34;https://cofacts.tw/&#34;&gt;Cofacts&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;With grateful support from &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Communications Toolkit for Civic &amp; Nonprofit Tech</title>
      <link>https://superbloom.design/learning/resources/comms-toolkit/</link>
      <pubDate>Wed, 04 Sep 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/comms-toolkit/</guid>
      <description>&lt;p&gt;This is a toolkit for civic, open-source, and/or nonprofit technology teams undertaking communications projects. &lt;/p&gt;
&lt;p&gt;Messaging who you are and what you do is a crucial opportunity to unlock your impact. However, many teams aren’t experienced with scoping, managing, or implementing projects in this area. Communications work is often left out of funding proposals and seen as something that will naturally happen on its own.&lt;/p&gt;
&lt;p&gt;With the support of the &lt;a href=&#34;https://www.opentech.fund/labs/learning-lab/&#34;&gt;Open Technology Fund&amp;rsquo;s Learning Lab&lt;/a&gt;, we at Superbloom set out to make a set of resources to help organizations scope and undertake identity and communications projects.&lt;/p&gt;
&lt;p&gt;These resources are for you if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Your organization’s public face doesn’t reflect your work as well as it could, and you’d like to fix that&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design&#34;&gt;You believe that the communities you work with should be involved in your communications process&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;You would like to do a project around identity (branding) or another element of communications, but you don’t know how to scope or plan it&lt;/li&gt;
&lt;li&gt;You need some perspective and guidance in the middle of a communications project in progress&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These resources are geared towards smaller organizations who don’t have a dedicated communications staff.&lt;/p&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
&lt;p&gt;Our approach to communications is somewhat different from the &amp;ldquo;standard&amp;rdquo; approach: we believe you can have the most impact when you not only get input from your community, but involve them as deeply as you can in the process. Read more in our &lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design&#34;&gt;Guide to Participatory Approaches in Communications&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;p&gt;&lt;em&gt;(We’ll use the word “organization” from here on out, but please substitute “team,” “project,” “group,” “community,” or whatever description best suits what you are working on.)&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;why-its-all-about-the-roadmap&#34;&gt;Why it&amp;rsquo;s all about the roadmap&lt;/h3&gt;
&lt;p&gt;This toolkit is not just about how to &lt;em&gt;do&lt;/em&gt; communications work, but about how to &lt;em&gt;scope and plan&lt;/em&gt; it. &lt;/p&gt;
&lt;p&gt;Planning and scoping your communications project is a crucial, and challenging, part of the work, whether you are working internally, working with a partner organization, or bringing on individual freelancers. &lt;/p&gt;
&lt;p&gt;We have seen that the planning process – assessing needs, estimating timelines and work hours, and mapping out projected deliverables – can be a barrier to doing (and funding) communications work. Just like any other project, communications projects can be planned and scoped.&lt;/p&gt;
&lt;p&gt;Our aim is to demystify how communications projects work, so that you can confidently get started. If you’re working internally, you’ll be able to resource the project and plan your team’s time. If you’re working with external partners, you’ll be able to clearly articulate what you need from them and why, leading to a more pleasant and productive collaboration. And &lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design&#34;&gt;when you involve your community in the process&lt;/a&gt;, you&amp;rsquo;ll be able to be clear with them about what you need, when you need it, and how you use it, so that you&amp;rsquo;re respecting their time.&lt;/p&gt;
&lt;h1 id=&#34;investing-in-communications-why-its-worth-it&#34;&gt;Investing in communications: why it&amp;rsquo;s worth it&lt;/h1&gt;
&lt;p&gt;Reading the time estimates in our &lt;a href=&#34;http://superbloom.design/learning/resources/scoping-communications-projects&#34;&gt;guide to scoping projects&lt;/a&gt; may discourage you from undertaking communications work. After all, those hours could be spent on pursuing your primary mission, right? &lt;/p&gt;
&lt;p&gt;We’d like to frame the question differently: &lt;em&gt;your primary mission deserves an investment in communications.&lt;/em&gt; &lt;a href=&#34;#identity&#34;&gt;Creating an identity&lt;/a&gt;, &lt;a href=&#34;#communications-strategy&#34;&gt;crafting a communications strategy&lt;/a&gt;, and &lt;a href=&#34;#communications-design&#34;&gt;designing communications collateral&lt;/a&gt; are directly related to both the impact you’ll have, and the support and sustainability you’ll be able to achieve. &lt;/p&gt;
&lt;p&gt;This sounds logical, so why is it relatively rare to see an investment in communications?&lt;/p&gt;
&lt;p&gt;In our experience, it often feels like communication will happen more or less organically: that messaging what we care about will come easily, and that quality work will naturally draw attention and create buzz. It would be nice if this were true! We can tell you from our own experience that &lt;em&gt;you need to plan external communications, or it won’t happen.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img-mic_hu_d3ddc5a73fd2ed3c.png&#34; alt=&#34;Line drawing of hand holding microphone&#34; width=&#34;740&#34; height=&#34;284&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;youll-create-a-memorable-impression-in-a-crowded-space&#34;&gt;You&amp;rsquo;ll create a memorable impression in a crowded space&lt;/h2&gt;
&lt;p&gt;It’s safe to say that anyone working in nonprofit technology is deluged with new information. We work at the crossroads of many different fields, and we are all trying to stay up-to-date on conferences, reports, release announcements, press releases… we’re tired just thinking about it. Additionally, social media is in a complicated transition: neither federation nor intransparent behemoths have fully won out, and people stay up to date using many different channels.&lt;/p&gt;
&lt;p&gt;To stand out in this chaos, a distinctive, and consistent look and feel is an absolute must-have. A memorable identity – name, visuals, tagline, voice, and overall personality – gives you the shot at impact and sustainability that your work deserves. &lt;/p&gt;
&lt;h2 id=&#34;you-can-say-who-you-are-not-just-what-you-do&#34;&gt;You can say who you are, not just what you do&lt;/h2&gt;
&lt;p&gt;Not only do you want to be memorable – you want to be memorable for the right reasons. You want to share what your mission is. You also want to give people the right impression about how you go about this work. Are you serious or casual? Technical or humanistic? Ironic or earnest? Are you reliable and established, or hip and socially engaged? &lt;/p&gt;
&lt;p&gt;Communications work gives you the opportunity to tell people these things in a subtle way, using tools like color, type, images, and associations. It lets you pick how you make people feel. The phrase “a picture speaks a thousand words” has plenty of truth to it. Take the opportunity to craft an accurate visual and emotional impression for your community, and you’ll have spared yourself a great deal of explanation effort.&lt;/p&gt;
&lt;h2 id=&#34;youll-save-time&#34;&gt;You&amp;rsquo;ll save time&lt;/h2&gt;
&lt;p&gt;Building out a communications and identity infrastructure is absolutely a time-saver. You’ll see the benefits the first time you are able to find a logo file instantly, create a presentation from a template, or put together a social media post in 15 minutes.&lt;/p&gt;
&lt;p&gt;Once you have a library of elements to draw from, you’ll be able to focus on your content, without fiddling with templates and searching for graphics every time you need to create a piece of public-facing collateral.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img-picture-frame_hu_7efa3812c5fb15bc.png&#34; alt=&#34;Minimalist line drawing of hands straightening picture frame&#34; width=&#34;740&#34; height=&#34;284&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;three-building-blocks-of-communications&#34;&gt;Three building blocks of communications&lt;/h2&gt;
&lt;p&gt;We&amp;rsquo;ll help you through &lt;strong&gt;three building blocks&lt;/strong&gt; of your organizational communications:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&#34;#identity&#34;&gt;Identity&lt;/a&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&#34;#communications-strategy&#34;&gt;Communications strategy&lt;/a&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&#34;#communications-design&#34;&gt;Communications design&lt;/a&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;table class=&#34;toolbox-bottom-table&#34;&gt;
  &lt;thead&gt;
      &lt;tr&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;Resource&lt;/th&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;To help you with&lt;/th&gt;
      &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/scoping-communications-projects&#34;&gt;Guide: Scoping projects&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Estimating project length. Gives example scopes for small, medium, and large scopes for these three areas.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design/&#34;&gt;Guide: Participatory approaches&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;How and why to involve your community in your communications project.&lt;/td&gt;
      &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;
&lt;!-- However, they all influence each other, and your **[identity](#identity)** is usually the piece that you change the least often. So, we’ve put identity first – not because everyone needs to work on their identity, but because anyone planning identity work should resolve their new name, logo, colors, and other elements before they move on to communications strategy and design. --&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/communications-venn-diagram_hu_62a695ab2f998541.png&#34; alt=&#34;Venn diagram with 3 circles. First circle says: Identity: define and message what you are and what you stand for. Second circle says: Communications strategy: Hone your communications processes. Third circle says: Communications design: make your communications consistent and efficient. The intersection of Identity and Communication Design says, identify your community, your context, and your goals. The intersection of communications strategy and communications design says, create the right assets for your needs. The intersection of identity and communications design says, get a professional, consistent look and feel throughout your organization. The intersection of all three circles says, tell the world who you are!&#34; width=&#34;740&#34; height=&#34;541&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;identity&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;identity&#34;&gt;Identity&lt;/h2&gt;
&lt;p&gt;An identity is a structured system of elements that work together to communicate your project or organization’s mission, values, and character. It’s unique and recognizable, working on a mostly subconscious level to build a sense of belonging and pride.  It helps people remember you, associate your work with you, and notice where you’re present. Your identity is an incredible opportunity to shape and reflect the emotional relationship of communities and funders towards you.&lt;/p&gt;
&lt;p&gt;Your identity consists of many different elements. Some of these elements are easy to isolate and identify: name, tagline, colors, logo, and typefaces. Some of them are more subtle: the way you use images, the way you write, the way you use space and alignment.&lt;/p&gt;
&lt;p&gt;When the building blocks of your identity harmonize well together and send the message you want to send: congratulations! Your identity is working well for you.&lt;/p&gt;
&lt;p&gt;But in many cases, these building blocks aren’t working effectively together. If this is the case, you probably already know it. You will have a gut feeling that something isn’t quite right. But it can be hard to put your finger on what the problem is (it’s almost never just your logo!), and also hard to justify putting in the effort to diagnose and fix the issue.&lt;/p&gt;
&lt;p&gt;We’ve seen a few common patterns in organizations whose identity needs some revision. In our experience, here are some signs that it’s time to allocate resources to identity work:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You feel you are spending too much time explaining your organization&lt;/li&gt;
&lt;li&gt;Your community gives you feedback on your identity (this is a great opportunity for learning – ask them for more details!)&lt;/li&gt;
&lt;li&gt;You avoid using your identity elements because you think they will hold you back in certain contexts, or with certain communities&lt;/li&gt;
&lt;li&gt;Your identity reflects an outdated understanding of a field or of a community&lt;/li&gt;
&lt;li&gt;Your organization or group has changed structure or ownership (e.g. is now under a new umbrella organization, has become a workers’ cooperative, has merged with another group)&lt;/li&gt;
&lt;li&gt;Someone has asked you to change parts of your identity, whether as a favor or via legal avenues&lt;/li&gt;
&lt;li&gt;People seem to confuse you often with another organization, or have a hard time remembering your organization&lt;/li&gt;
&lt;li&gt;Your identity is all over the place (e.g. the font looks playful, but the illustrations look serious)&lt;/li&gt;
&lt;/ul&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
&lt;p&gt;Consider convening a session where you &lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design/&#34;&gt;ask the communities you serve&lt;/a&gt; to react to your name, branding, and communications. This may be hard to hear! It may help to ask someone to facilitate the session who didn&amp;rsquo;t create the work themselves. You&amp;rsquo;ll get incredibly useful insights about how you are coming across to the world.&lt;/p&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;p&gt;Identity work is much, much more than logo design. It is challenging and time-consuming. It requires a high degree of internal participation, commitment, and humility. It also needs input and buy-in from your community. It should not be undertaken lightly.&lt;/p&gt;
&lt;p&gt;But an identity that isn’t working is holding you back and needs your attention. In the end, identity work serves your community and deepens your impact, and the payoff will last a long time.&lt;/p&gt;
&lt;p&gt;It’s not just decoration for your work: it shows who has done the work. It saves you time; it helps people connect with you; and it tells your story for you.&lt;/p&gt;
&lt;p class=&#34;customTable&#34;&gt;&lt;br /&gt;&lt;/p&gt;
&lt;table class=&#34;toolbox-bottom-table&#34;&gt;
  &lt;thead&gt;
      &lt;tr&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;Resource&lt;/th&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;To help you with&lt;/th&gt;
      &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/document/d/1Fy_aiSmtfdU-43l8zsfA452UOoDGdAmdumMbLm_Tot8/edit?usp=drive_link&#34;&gt;Questionnaire: High level scoping questions for brand development (Google Docs)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Identifying specifically what aspects of your brand need to be worked on.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/document/d/1-rYUb7W1ZuRVyywCnllGsuVjcRkxsocsZUd6gcN3Yts/edit?usp=drive_link&#34;&gt;Questionnaire: High level scoping questions for naming (Google Docs)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Identifying specifically what aspects of your name need to be worked on.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/brand-development-process/&#34;&gt;Guide: Brand development process&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;The steps to creating a brand, from research to feedback.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/creating-brand-guidelines&#34;&gt;Guide: Brand guideline toolkit&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Understanding and documenting the various aspects of a brand.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://miro.com/app/board/uXjVMo53Gi8=/&#34;&gt;Template: Naming workshop template (Miro)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Naming or renaming a product, project, or team.&lt;/td&gt;
      &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&lt;a name=&#34;communications-strategy&#34; &gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;communications-strategy&#34;&gt;Communications strategy&lt;/h2&gt;
&lt;p&gt;Your organization has an &lt;strong&gt;&lt;a href=&#34;#identity&#34;&gt;identity&lt;/a&gt;&lt;/strong&gt;. Maybe you’ve worked on the templates and collateral to use that identity in your &lt;strong&gt;&lt;a href=&#34;#communications-design&#34;&gt;communications&lt;/a&gt;&lt;/strong&gt;. Now, how do you actually put these elements into practice?&lt;/p&gt;
&lt;p&gt;A successful communications practice means something different for every organization. You need to understand your goals before you create a communications strategy. Are you aiming to build a closer connection with the community you serve? Do you want to network with partner organizations? Are you hoping to build your profile among funders? Is there a particular way you’d like to position yourself in the landscape?&lt;/p&gt;
&lt;p&gt;Your internal needs, resources, and interests are as important as your external goals. Are you a tiny software team with nobody who particularly enjoys writing? Blog about your conference presentations, but don’t bother with an email newsletter. Is your staff impressively multilingual? Think about how you can use this to your advantage on social media.&lt;/p&gt;
&lt;p&gt;The current social media landscape is full of contradictions, and reading about current trends can feel overwhelming. (Is federated social media on the rise, or do Meta and TikTok rule the market? Does everyone need to make short vertical videos, or are email newsletters where it’s at?) You don’t have to be everything to everyone. Focusing on a particular audience, and the channels and content they’re likely to appreciate, will help you conserve your energy.&lt;/p&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/participatory-comms-design/&#34;&gt;Ask the communities you work with&lt;/a&gt; what platforms they use, and what they use them for. Try mocking up posts that would appear on different platforms, and see what people think: are you giving the right information and striking the right tone for the platform?&lt;/p&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;br /&gt;
&lt;table class=&#34;toolbox-bottom-table&#34;&gt;
  &lt;thead&gt;
      &lt;tr&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;Resource&lt;/th&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;To help you with&lt;/th&gt;
      &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/organizational-comms-strategy&#34;&gt;Resource list: Communications strategy&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;A list of resources to guide you in developing your organization&amp;rsquo;s communication strategy.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/document/d/1H1vgPoC8JQX7zCi18k3RZ-sguaiBASZWQiMX_NkHv_4/edit#heading=h.9937v0e1djhj&#34;&gt;Questionnaire: High level scoping questions for writing projects (Google Docs)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Identifying the scope and specifications of writing projects such as blogs, articles, reports, press releases, etc.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/scoping-communications-projects&#34;&gt;Guide: Scoping communications projects&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Planning and resourcing your communications projects, with examples of small, medium, and large scopes.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://miro.com/app/board/uXjVN4pTNjQ=/?share_link_id=24140407328&#34;&gt;Template: Social media strategy workshop (Miro)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Matching your social media strategy with your organization&amp;rsquo;s needs.&lt;/td&gt;
      &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&lt;a name=&#34;communications-design&#34; &gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;communications-design&#34;&gt;Communications design&lt;/h2&gt;
&lt;p&gt;Do you copy and paste a recent presentation, report, or document every time you need to create a new one? You’re not alone. When an organization is getting started, templates for communications design usually aren’t the first priority. However, once more people are involved and the trail of documents and presentations gets longer, the benefits of a communications design system begins to become clear.&lt;/p&gt;
&lt;p&gt;Without a communications design system:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;You can’t make any synchronized changes to your &lt;strong&gt;&lt;a href=&#34;#identity&#34;&gt;identity&lt;/a&gt;&lt;/strong&gt;. Different people may have different “templates” they are privately using, so there’s no way for everyone to change elements like color scheme or image treatment.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Onboarding new people who don’t have ambient knowledge of past communications is challenging. They are missing the tools to create effective communications without help from somebody who has been around for longer.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Your outward face is inconsistent and confusing. It may not be clear whether certain communications are actually from you or not.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;You are wasting time reinventing the wheel – time you could be spending doing other work! Create a template once, store it in a place that’s easy to find, and you never need to make the same document again.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A communications design system uses elements from your &lt;strong&gt;&lt;a href=&#34;#identity&#34;&gt;identity&lt;/a&gt;&lt;/strong&gt;, taking into account your &lt;strong&gt;&lt;a href=&#34;#communications-strategy&#34;&gt;strategy&lt;/a&gt;&lt;/strong&gt;. Most communications design systems include overall guidance about visuals and tone, as well as a variety of specific templates. Sample presentations, social media posts, reports, documents, letterheads, and press releases are all common templates that can save you and your team time and effort.&lt;/p&gt;
&lt;p class=&#34;customTable&#34;&gt;&lt;br /&gt;&lt;/p&gt;
&lt;table class=&#34;toolbox-bottom-table&#34;&gt;
  &lt;thead&gt;
      &lt;tr&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;Resource&lt;/th&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;To help you with&lt;/th&gt;
      &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/document/d/1e1ynFtmvriVR0S70nVAvysbLEfIS_bNuob4sxwyVAM0/edit#heading=h.9t95l84hcr9w&#34;&gt;Questionnaire: High level scoping questions for social media graphics (Google Docs)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Identifying the specific aspects of the social media communications that need to be worked on.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/social-media-graphics&#34;&gt;Resource list: Social media posts&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;A list of resources to help you plan and execute social media posts.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/document/d/15SlUvGNfdL02pQoQxCxVpYaKnDF3WTRf_3ox-9BBz1U/edit#heading=h.755hrdox3z68&#34;&gt;Template: Social media text (Google Docs)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Planning your text for social media.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://miro.com/app/board/uXjVMLagH4k=/?share_link_id=558690864957&#34;&gt;Template: Social media visuals (Miro)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Preparing images in the recommended sizes before you post.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/document/d/1vUq-4xaPw5ZZHtQcwDyOPXHMNLUyghVYKES0kDIOOVg/edit?usp=drive_link&#34;&gt;Questionnaire: Tone &amp;amp; voice (Google Docs)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Establishing a consistent and impactful tone and voice in your communications efforts.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;http://superbloom.design/learning/resources-crafting-press-release&#34;&gt;Guide: Crafting a press release&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Crafting a press release.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/spreadsheets/d/1BWJY-dsdNrhsh1_frT7L6C-omzle6HvD/edit?usp=drive_link&amp;amp;ouid=106639959202589259575&amp;amp;rtpof=true&amp;amp;sd=true&#34;&gt;Template: Social media content calendar (Google Sheet)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Creating a schedule for posting content.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/presentation/d/1g-uKI2UGdCx9S7sE26r6hyV0P0rHxDwGd87BiMS44zI/edit?usp=drive_link&#34;&gt;Template: Lightning talk (Google Slides)&lt;/a&gt;&lt;/td&gt;
          &lt;td&gt;&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/presentation/d/1LrcWgD4Aagbo-JOBjlSkJlOvrRHn-heYEM8z16BWdYw/edit?usp=drive_link&#34;&gt;Template: Organizational overview (Google Slides)&lt;/a&gt;&lt;/td&gt;
          &lt;td&gt;&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/presentation/d/1Vb76PyIqQ3CzUWU-pbUjRt5efoXG07eJFWu3OAGp_6Y/edit?usp=drive_link&#34;&gt;Template: Research shareout (Google Slides)&lt;/a&gt;&lt;/td&gt;
          &lt;td&gt;&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/document/d/1yftME-d9EZxAxoxQfQ51mbhmtRu-6AXO1f5emnTILkI/edit?usp=drive_link&#34;&gt;Template: Report (Google Docs)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Creating a report with ready-to-use formatting. Insert your own fonts and colors.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://docs.google.com/document/d/1KNHTTzDREANkMbqb61osQHRQI-etGpRcv26xiKIAocs/edit?usp=drive_link&#34;&gt;Template: Press release (Google Docs)&lt;/a&gt;&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Creating a press release with ready-to-use formatting. Insert your own fonts and colors.&lt;/td&gt;
      &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&lt;br&gt;
&lt;em&gt;&lt;a href=&#34;http://superbloom.design/learning/resources/comms-toolkit&#34;&gt;This toolkit&lt;/a&gt; was developed with the support of the &lt;a href=&#34;https://www.opentech.fund/labs/learning-lab/&#34;&gt;Open Technology Fund Learning Lab&lt;/a&gt;. Got feedback? Want to work together? Please write to us at &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Adobe | Video Series II</title>
      <link>https://superbloom.design/work/projects/adobe_video_series_ii/</link>
      <pubDate>Sat, 24 Aug 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/work/projects/adobe_video_series_ii/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Co-designing Platform Policy For &#34;High Risk&#34; Content Creators: The Tech Policy Design Lab Approach</title>
      <link>https://superbloom.design/learning/blog/co-designing-platform-policy-for-high-risk-content-creators-the-tech-policy-design-lab-approach/</link>
      <pubDate>Fri, 05 Jul 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/co-designing-platform-policy-for-high-risk-content-creators-the-tech-policy-design-lab-approach/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_co-designing_platform_policy_image_2_hu_2e03ff1cd27482cc.png&#34; alt=&#34;A photo of half of a peeled grapefruit. A dark skinned hand with pale pink painted nails has put their fingers in between the segment of the grapefruit giving a ‘suggestive’ quality to the image.&#34; width=&#34;740&#34; height=&#34;675&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A &lt;a href=&#34;https://techlab.webfoundation.org/playbook&#34;&gt;Tech Policy Design Playbook&lt;/a&gt; was developed and published as the culmination of our work with the World Wide Web Foundation and 3x3 on &lt;a href=&#34;https://superbloom.design/learning/blog/together-against-deceptive-design/&#34;&gt;Deceptive Design&lt;/a&gt;, and includes guidance on how to run community co-design engagements around tech policy design. Superbloom, in partnership with &lt;a href=&#34;https://www.northumbria.ac.uk/about-us/our-staff/a/carolina-are/&#34;&gt;Dr Carolina Are&lt;/a&gt;, facilitated three community sessions around the risks to “high risk” content creators and being de-platformed from essential social and content platforms.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.northumbria.ac.uk/about-us/our-staff/a/carolina-are/&#34;&gt;Dr Carolina Are&lt;/a&gt;, reached out to Superbloom to leverage and test the &lt;a href=&#34;https://techlab.webfoundation.org/playbook/how-to-run-a-tpdl&#34;&gt;Tech Policy Design Lab Playbook: &amp;ldquo;How To Run A TPDL&amp;rdquo;&lt;/a&gt; in a series of three workshops aimed to improve the design and policies of social media platforms through centering the needs of marginalized communities, journalists/activists, sex educators and adult content creators. These content creators are regularly at risk of de-platforming and shadow banning which is when they lose access to their social media account(s) e.g. TikTok, Instagram, Twitter/X, via malicious &amp;ldquo;crowd-sourcing&amp;rdquo;; an example of which is when those in online communities rally others within the community to have someone’s account deleted by reporting the profile and/or account.&lt;/p&gt;
&lt;h3 id=&#34;making-space-for-high-risk-identities-when-building-policy&#34;&gt;Making space for high-risk identities when building policy &lt;/h3&gt;
&lt;p&gt;Participants in the first of three workshop groups were individuals who identified across the LGBTQIA+ spectrum and had experiences of their content being censored, mass-reported or taken down due to the LGBTQIA+ related-content. The second was a group of varied adult content creators ranging from lingerie makers, painters, photographers, pole dancers and sex-workers. These individuals are very aware of the rules for banned content on social media platforms and often find their content is removed even when it complies with a platform&amp;rsquo;s rules. The most devastating effect on adult content creators is that they often rely on these platforms for promotion as they are a vital source of income generation. &lt;/p&gt;
&lt;p&gt;The third and final group were people involved in activism and journalistic work that use social media platforms to spread and gather information about human rights cases globally. This work is often difficult due to platform censorship of different “violent” and/or “sensitive” information and they are frequently “mobbed” by those who want to suppress certain voices and perspectives. This is usually exercised through the malicious mass reporting of posts.&lt;/p&gt;
&lt;p&gt;The workshop groups were provided with information and scenarios in advance of the workshops, and invited to take part in breakout group activities to propose solutions to some of the main challenges in social media’s governance of their content types. These workshops use a sex positive framework to re-design platform governance. Participants didn’t require previous knowledge of design or specific technologies to participate in the workshops, however; as we often find when facilitating workshops, those who attend these workshops have vast and varied levels of comfort with tech, design and policy topics. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_co-designing_platform_policy_image_1_hu_fe32e8657a56887.png&#34; alt=&#34;Tarot card style illustrations that were used for the workshops to communicate different kinds of people creating high-risk and/or adult content for platforms. There is a gender-non-conforming person with high platform shoes with a miniskirt, jacket and shaved head, a masc person with visible top-surgery scars and two femme presenting people one slim with dark hair and one larger with short locks in lingerie.&#34; width=&#34;740&#34; height=&#34;419&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;the-main-concerns-for-high-risk-content-creators&#34;&gt;The main concerns for high-risk content creators&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;“&amp;hellip;Content moderation often fails to take the human experience into account to prioritize speed and platform interests, lacking in the necessary empathy for users who are experiencing abuse, censorship, loss of livelihood and network as well as emotional distress. Indeed, being de-platformed from social media often leaves users unable to access work opportunities, information, education as well as their communities and networks – and research has found this has adverse mental health and wellbeing impacts”.&lt;/strong&gt;&lt;/em&gt; &lt;/p&gt;
&lt;p&gt;&lt;em&gt;Dr Carolina Are’s report &lt;a href=&#34;https://www.themoderationarcana.com/_files/ugd/dfdcfd_f42d3469947d43b394193d5a1d5e53c7.pdf&#34;&gt;“Co-Designing Platform Governance Policies&lt;/a&gt;” courtesy of the &lt;a href=&#34;https://www.themoderationarcana.com/&#34;&gt;Moderation Arcana&lt;/a&gt; project website.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The overwhelming frustrations expressed by all workshop attendees were that those woh configure, manage and govern current social media platforms are not always representative of identities such as theirs (LGBTQIA+, adult content creators and human rights activists/journalists). This is apparent through the very design of the platforms and policies which govern them (e.g. reporting processes that overwhelmingly punish certain identities). Although the three workshop groups were separated by content specifics and context, all had a shared purpose. Each has a perspective and voice to share, and they are providing essential information e.g. journalists and desired services e.g. adult content, creative expression arts, and are punished by the platform’s design for speaking out or for simply sharing their profession or identity. Often they are punished by the very systems put in place to protect them. Here sits the complex contradiction of platforms made to facilitate the ability of ordinary citizens to share and voice opinions (social media), where the politicization of certain “risky” content can arise from those who seek to censor, whether it be a platform or the citizens themselves who decide that certain content should not be allowed to be shared on platforms because of their own moral standpoint.&lt;/p&gt;
&lt;p&gt;These marginalized identities and content creators went on to further state that they yearn for platforms created by and for people like them, LGBTQIA+ folks, Sex Workers and Activists but lamented the fact that creating these platforms has been attempted in the past to only marginal success. This marginal success then pushes people back to the mainstream platforms in order to reach others; like-minded communities, newly exploring LGBTQIA+ folks, people who pay for adult services and those who can benefit from hearing activist/citizen journalist news over the mainstream media. These mainstream platforms have a hold over these marginalized communities due to their popularity and prevalence. The existence of marginalized identities on these platforms is a constant high-risk dance between the lines of censorship and being banned from the platform.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;“It’s a constant anxious battle. Instagram is always terrifying, and anxious and nerve-wracking and there&amp;rsquo;s never any positive feelings around Instagram. It is always inadequacy, “Oh my goodness, I&amp;rsquo;m not posting enough”, or “Oh my God, if I don&amp;rsquo;t post everyday then my followers are going to drop”, and of course, “If I post every day, I&amp;rsquo;m more likely to get shadow banned or blacklisted or deleted, and have posts removed.”&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Workshop participant&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Many participants spoke to the business and revenue increasing-focus of many platforms, stating that they felt that while from a content perspective they were not wanted on these platforms, the platforms couldn’t deny the business revenue that they bring. They expressed the sense of deliberate tenuous co-existence with high-risk content from the platform’s perspective; that they were wanted there for the viewer traffic, but were not invited to make the platforms safer and more stable places for them.&lt;/p&gt;
&lt;p&gt;The greatest sense of stability for these content creators came from three places:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Being in community and connecting with similar types of content creators.&lt;/li&gt;
&lt;li&gt;Discussing and equipping themselves with knowledge of platform policies and national and international content laws.&lt;/li&gt;
&lt;li&gt;Being able to have an “inside person” working at these platforms.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;All participants felt a sense of injustice about working with these methods; that being in community often means being at risk of competition or being more easily identified by citizen “online mobs” or platform moderators. Equipping yourself with knowledge requires the time to find and understand frequently complex policy language, and having an inside person or employee connection is down to luck.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_co-designing_platform_policy_image_3_hu_8a5d0bb2a9bd1c1c.png&#34; alt=&#34;Tarot card style illustrations that were used for the high-risk workshops to communicate different kinds of people creating high-risk and/or adult content for platforms. There is a long haired person in a loose suit jacket and pants. A skeletal hand holding a phone with the Instagram logo and an error message that an account cannot be found and a femme presenting person, in a crouched position in dancing club clothing with a fist raised in power. There are two figures with protest signs below her that have messages that sex worker rights are human rights.&#34; width=&#34;740&#34; height=&#34;419&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;ways-we-want-to-see-platforms-change-policies-to-ensure-content-creator-safety&#34;&gt;Ways we want to see platforms change policies to ensure content creator safety&lt;/h3&gt;
&lt;p&gt;It was unanimously agreed that content creators at risk of shadowbanning and de-platforming want explicit and clear inclusion in the decision making processes that platforms use when making content reporting and account take-down policies. This includes better internal knowledge and training for social media platform staff, but also platform endorsed training for these kinds of content creators. This comes with the need for specific and dedicated communication lines with platform staff and content creators. Without content, these platforms do not have an audience. The symbiotic nature of all kinds of content, and that the platforms rely on humans creating and posting content was made clear in our discussions, and that platforms currently lean towards an authoritative approach to their platform.&lt;/p&gt;
&lt;p&gt;The Superbloom workshop facilitation team also saw the benefit of equipping individuals with background knowledge ahead of policy workshops such as these. All come into these spaces with different levels of understanding and access. Efforts to equalize these levels are tricky and usually done by sending reading materials and resources ahead of time. In itself this is a polarizing action, given that many may not have the time or background to parse that information ahead of a workshop. This is why human-understandable policy information must be created to empower individuals to speak about their needs with regard to the platforms they frequent.&lt;/p&gt;
&lt;p&gt;In discussing the users who seek to harm others using the systems that platforms have put in place for safety e.g. mass-reporting, we advocate for a method that Superbloom utilizes when working with the risk of “bad actors” or people and/or structures that seek to censor. We call these &lt;a href=&#34;https://superbloom.design/learning/resources/persona-non-grata/&#34;&gt;Personas Non Grata&lt;/a&gt;. These archetypes are ways of modeling behavior that harms others, whether deliberately or not.&lt;/p&gt;
&lt;p&gt;In summary, in facilitating the three workshops, we learned there must be more consultation with those who create “high-risk” content in order for all public platforms and tools to better include all users of the internet in a way that’s safe for everyone.&lt;/p&gt;
&lt;p&gt;You can read more academic papers from Carolina Are in her &lt;a href=&#34;https://orcid.org/0000-0003-1110-3155&#34;&gt;research portfolio&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;C﻿redits&lt;/h3&gt;
&lt;p&gt;&lt;a href=&#34;https://www.northumbria.ac.uk/about-us/our-staff/a/carolina-are&#34;&gt;D﻿r Carolina Are&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/about/people/eriol/&#34;&gt;Eriol Fox&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/about/people/ann-marie/&#34;&gt;Ann Marie Carrothers&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Tech Policy Design Lab: Deceptive Design</title>
      <link>https://superbloom.design/work/projects/tpdl/</link>
      <pubDate>Fri, 05 Jul 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/work/projects/tpdl/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Join the Superbloom Board</title>
      <link>https://superbloom.design/community/opportunities/2024-call-for-directors/</link>
      <pubDate>Fri, 28 Jun 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/opportunities/2024-call-for-directors/</guid>
      <description>&lt;h4 id=&#34;the-role&#34;&gt;&lt;strong&gt;The role&lt;/strong&gt;&lt;/h4&gt;
&lt;p&gt;We are recruiting 1-2 new members to our Board of Directors in 2024. These individuals will serve as stewards of our mission, and support our organization’s senior leadership as we continue our growth and evolution. Note: This is an unpaid position, members of our Board of Directors serve in a volunteer capacity.&lt;/p&gt;
&lt;p&gt;The Superbloom Board of Directors is made up of experts in the public interest technology space who apply a critical lens to technology, and believe that design is a lever for changing who technology serves. We are recruiting new members as part of a Board expansion effort, and in anticipation of Sara “Scout” Sinclair Brody’s departure at the end of her third and final term. New members will serve a two-year term, with the opportunity to be re-elected for two more terms to a maximum of six consecutive years&amp;rsquo; service.&lt;/p&gt;
&lt;p&gt;The Superbloom Board works in a voluntary, active advisory capacity. It advises our organization to drive impact against our strategic goals, and have the fiduciary responsibility to ensure our finances can support the work that we do and that we are in compliance with our legal obligations. Read more about the &lt;a href=&#34;https://superbloom.design/about/board/&#34;&gt;Superbloom Board and governance&lt;/a&gt;, as well as our Board Development Criteria for more information on the qualities we’re looking for in potential candidates as well as expectations and responsibilities. We welcome expressions of interest via the form for full consideration. Please submit as soon as possible, as we will be reviewing applications on a rolling basis.&lt;/p&gt;
&lt;h4 id=&#34;about-us&#34;&gt;&lt;strong&gt;About us&lt;/strong&gt;&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design&#34;&gt;Superbloom&lt;/a&gt;, previously known as &lt;a href=&#34;https://simplysecure.org/&#34;&gt;Simply Secure&lt;/a&gt;, leverages design as a transformative practice to shift power in the tech ecosystem. We apply a holistic approach and view design as an intervention opportunity to center people and their needs. Our vision is a world where everyone has the knowledge, network, and digital tools needed to enrich their lives. Launched in 2014, Superbloom is a US 501(c)3 nonprofit design and research organization, leveraging practices from human rights, systems thinking, service design and threat modeling to help teams design technology and services that center and protect communities’ most vulnerable needs. Since 2020, we have been piloting fiscal sponsorship as a leadership development and support program, incubating emerging efforts that align with our mission. Read more about our Board Development Criteria, our programs, and our &lt;a href=&#34;https://superbloom.design/work/&#34;&gt;work&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Superbloom is an equal opportunity employer. We believe that systemic bad behaviors disproportionately hurt the most marginalized people in society — including people of color, people from working class backgrounds, women, and LGBTQ people. We believe that these communities must be centered in the work we do. We strongly encourage applications from people with these identities or who are members of other marginalized communities. &lt;/p&gt;
&lt;p&gt;We thank all applicants for their interest; however, only those selected for an interview will be contacted.&lt;/p&gt;
&lt;h5 id=&#34;this-opportunity-closed-on-august-29th-2024-please-contact&#34;&gt;&lt;strong&gt;This opportunity closed on August 29th, 2024. Please contact &lt;a href=&#34;mailto:opportunities@superbloom.design&#34;&gt;opportunities@superbloom.design&lt;/a&gt; should you wish to be informed of future opportunities.&lt;/strong&gt;&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/board&#34;&gt;Superbloom Board and Governance Overview&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>On Being a Coach: Support for Designers in Privacy and Security Open Source Software</title>
      <link>https://superbloom.design/learning/blog/on-being-a-coach-support-for-designers-in-privacy-and-security-open-source-software/</link>
      <pubDate>Fri, 28 Jun 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/on-being-a-coach-support-for-designers-in-privacy-and-security-open-source-software/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_adoptable_blog_climbers_hu_ca3bd1899b7439c6.png&#34; alt=&#34;A femme person in exercise gear is shown halfway up an indoor climbing wall with a safety rope attached and a masc presenting person is holding the safety rope from the ground. Image chosen for this blog subject due to the metaphor of how coaching is like supporting people climbing a project related ‘wall’.&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;p&gt;In December 2022, Superbloom partnered with &lt;a href=&#34;https://internews.org/&#34;&gt;Internews&lt;/a&gt; and &lt;a href=&#34;http://okthanks.com&#34;&gt;Okthanks&lt;/a&gt; to create resources that help open source software (OSS) teams better understand how design processes and user-centered activities improve usability, and therefore the security of open source tools. After publishing these resources and speaking about them to the wider OSS community, we found that designers and developers working in privacy and security OSS tool teams wanted to explore specific challenges through conversations with us. This led to the final component of the Adoptable project in the form of coaching.&lt;/p&gt;
&lt;p&gt;Coaching draws on the wide, collective knowledge that Superbloom team members have gathered over 10+ years of working in the internet freedom, Human Rights technology and Privacy and Security tool spaces. We called this work Adoptable:Coaching. Below, we outline some insights and needs we discovered while coaching privacy and security OSS tool teams. We utilized our general coaching approach to this project, and you can find out more on the &lt;a href=&#34;https://superbloom.design/community/our-support/#coaching&#34;&gt;Coaching&lt;/a&gt; page of our website..&lt;/p&gt;
&lt;p&gt;This work was highly sensitive, and publishing it could cause risk and harm to participating individuals, which is why we have abstracted and generalized our coaching learnings and have not mentioned any identifiers ie specific tools, teams, individuals or information.&lt;/p&gt;
&lt;p&gt;You can find all of the resources we created as part of the Adoptable project in an &lt;a href=&#34;https://github.com/sprblm/devs-guide-to&#34;&gt;open repository&lt;/a&gt; where you can access files directly and engage with the project. These are also available on the Adoptable project &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/&#34;&gt;website&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;what-common-needs-came-up-in-our-coaching-sessions&#34;&gt;What common needs came up in our coaching sessions?&lt;/h3&gt;
&lt;h4 id=&#34;designers-and-we-suspect-those-in-other-less-prominent-and-valued-roles-in-oss-production-often-operate-in-a-reactive-state&#34;&gt;Designers (and we suspect those in other less prominent and valued roles in OSS production) often operate in a reactive state.&lt;/h4&gt;
&lt;p&gt;Much of our early coaching conversations were around responses, strategies and methods that designers (though these can be broadly applied across job role function) can implement in order to gain an active or proactive role in their OSS projects/tool teams. There was deep discussion about how design can act as the user-voice. And about how design can then advocate for user-voice’s prominence in software development cycles. This then led to a concern around how to avoid design/designers being characterized as “strong personalities” or as a “gatekeeper” who stops technical improvements. This is often a tension with an OSS project’s ideas about how the OSS &amp;ldquo;should&amp;rdquo; be built and from whose perspective.&lt;/p&gt;
&lt;p&gt;Practically, many of the strategies employed include ways of managing a plethora of complex conversations about product direction at the same time as maintaining the time, space and resources to adequately research and express user insight to the wider OSS team. &lt;/p&gt;
&lt;p&gt;For suggested exercises, you can take a look at our &lt;a href=&#34;https://superbloom.design/learning/resources/user-experience-toolbox-for-risk-mitigation-and-accessibility/&#34;&gt;User Experience Toolbox For Risk Mitigation And Accessibility&lt;/a&gt; (see Part 2: Assessing Risks &amp;amp; Threats) about how to think ahead and communicate user needs through your role in a Privacy and Security focussed OSS tool.&lt;/p&gt;
&lt;h4 id=&#34;communicating-when-why-how-and-what-kind-of-projects-and-tasks-to-introduce-and-implement-for-user-centered-design-processes&#34;&gt;Communicating when, why, how and what kind of projects and tasks to introduce and implement for user centered design processes.&lt;/h4&gt;
&lt;p&gt;We coached on how to best communicate user centered processes in small software team development cycles. This included when to introduce these processes, for what scale of project and/or task and pacing of that process. Designers, specifically those unaccustomed to small development teams and OSS processes, tend to lean towards taught design methodologies which stress grave importance on the order in which to perform design processes. While holding oneself and a small and open source development team to a strict order, and a model that nets user centered benefits; more often than not it decouples design from development. In most cases, we advise a collaborative stakeholder approach to user research and user centered design as well as an approach to &amp;ldquo;make your own opportunities&amp;rdquo; as a designer in OSS. OSS can be described as a &amp;ldquo;show us the benefits first&amp;rdquo; operating structure, and it helps to have evidence for processes that benefit the tools and software.&lt;/p&gt;
&lt;p&gt;This is a tricky balance as it toes a line between complete transparency - by stating your intentions with design in the OSS development process - and an &amp;ldquo;ask forgiveness not permission&amp;rdquo; approach. Often the best assessment of which approach to use is already known to the coachee, yet reasonable and rational worries remain about their credibility and the function of their role.&lt;/p&gt;
&lt;p&gt;One method we coached on, to help folks develop a transparent and clear understanding of design needs for users, was a process of translating &amp;ldquo;issues&amp;rdquo; (typically written in a development centered way) to &lt;a href=&#34;https://github.com/Erioldoesdesign/opendesign/blob/master/translating-issues-to-design-challenges.md&#34;&gt;design challenges that focus on users&lt;/a&gt;. Other communication methods include &lt;a href=&#34;https://drive.google.com/file/d/1-e7XUAmFeGNbGBU5vJajqnsMgiPGv3v8/view?usp=sharing&#34;&gt;consent-based decision making&lt;/a&gt; from Sociocracy 101. &lt;/p&gt;
&lt;p&gt;When does user research and design lean into &amp;ldquo;too much&amp;rdquo; discussion and not enough action? Otherwise known as the variableness of user insight that different designers and/or OSS projects need or want to design well for UI/UX.&lt;/p&gt;
&lt;p&gt;It’s a tricky topic, as are most topics that edge into design and user experience in OSS. We discussed deeply some of the inclinations that different roles in OSS have when it comes to doing enough or &amp;ldquo;too much&amp;rdquo; user research and the risks involved when assumptions are the basis of design and software choices. The most difficult part isn’t about knowing or not knowing that line, again it’s to do with the communication of that line and the consistent negotiation of that line with the wider OSS tool team and how it ultimately impacts the users.&lt;/p&gt;
&lt;p&gt;It’s not always bad to design based on assumptions, but testing and confirming where and when assumptions are accurate, or not, are where lengthy and complex conversations can ensue. Deciding as a team where are the critical and impactful parts of a tools process, and where are the most risk and harms can focus resources on the most critical moments of a user&amp;rsquo;s use of a tool. And demonstrating the differences between assumption based design and evidence based design surfaced as a key continual resource for designs and OSS tool teams.&lt;/p&gt;
&lt;p&gt;A great resource for how to measure, understand and carry out &amp;ldquo;just enough&amp;rdquo; research is Erika Hall’s book &lt;a href=&#34;https://abookapart.com/products/just-enough-research&#34;&gt;&amp;ldquo;Just Enough Research, A Book Apart&amp;rdquo;&lt;/a&gt;. Other advice we have given is to find time to do user testing that isn’t time restricted. &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/user-testing/&#34;&gt;User Testing that can be given by users incrementally&lt;/a&gt; and in their own time will give the team insight on what they need without that feeling of losing time to a moderated &amp;ldquo;interviewer-interviewee&amp;rdquo; user testing process.&lt;/p&gt;
&lt;h4 id=&#34;understanding-and-communicating-the-value-of-deep-foundational-user-research-and-the-tension-when-theres-still-a-backlog-of-tech-issues&#34;&gt;Understanding and communicating the value of deep, foundational user research and the tension when there’s still a &amp;ldquo;backlog&amp;rdquo; of tech issues.&lt;/h4&gt;
&lt;p&gt;Similar to the above challenge around &amp;ldquo;just enough&amp;rdquo; user research is the challenge of when and how to do foundational research, especially when there’s likely to be an existing backlog of tech debt tasks as well as UI/UX debt tasks. Foundational research, whether focused on users or focused on a specific sector, domain or technology, allows designers, tool teams and, if published openly, the wider OSS community to learn from that foundational understanding. Technology and how it’s accessed and used changes over time and with social, political and economical change. This makes regular foundational research critical especially post situation changing events.&lt;/p&gt;
&lt;p&gt;As discussed with our coachees, foundational research is often viewed as costly in time and funds. While this can be true it is also possible to do slower, incremental foundational research strategies with a user community. Though this does often require an existing and amenable user base to initiate. As in most user research work, we came to a similar conclusion in that communicating the benefits of that work and the risks of not undertaking that work is an essential &amp;ldquo;tool&amp;rdquo; in the designers toolkit to advocate for what they need. Therefore, it’s key to operationalise these communications and include as many stakeholders in that process of learning as early as possible.&lt;/p&gt;
&lt;p&gt;You can take a look at other foundational research undertaken by similar tools and organizations as your own in order to get a head start on foundational research. We recommend looking at &lt;a href=&#34;https://usable.tools/personas/&#34;&gt;Personas - USABLE Tools&lt;/a&gt; and &lt;a href=&#34;https://okthanks.com/blog/2021/5/14/clean-consent-ux&#34;&gt;Okthanks &amp;ldquo;A Guide to Clean Consent UX&amp;rdquo;&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;design-teams-of-one-or-few-have-a-lot-to-accomplish-we-discussed-how-common-patterns-can-help-us-but-allow-us-to-not-fall-prey-to-privacy-and-security-pitfalls&#34;&gt;Design teams of one or few have a lot to accomplish. We discussed how common patterns can help us but allow us to not fall prey to privacy and security pitfalls.&lt;/h4&gt;
&lt;p&gt;Designers working within teams where OSS tools are built are rarely teams of more than one or two. If there are more than one or two designers in a team, it’s likely we’re looking at an organization that has multiple OSS tools or projects and yet, there’s likely to be only one or two designers per project. This often means that designers in these teams play a &amp;ldquo;full stack&amp;rdquo; role, doing design and user research, interface design, product design, graphics, marketing, community outreach and product management. To-do lists are long, even if the task is contained and simple. Having others with an understanding of user centered software design with whom to discuss aspects of an as yet to be implemented design was a huge part of our coaching. This raised a further question of how designers can use or build their own &amp;ldquo;cheat sheets&amp;rdquo; about how to design within a potentially complex OSS system and ensure that all the elements of the design works appropriately with the OSS. A subsequent need arose about how it could be done quickly, and in a privacy and security focused way. When UI/UX tasks are deemed too small for user research or usability testing, and are designed based on a team&amp;rsquo;s best assumptions, then this is where critical security and privacy aspects of the design and implementation may falter. Ensuring there are acceptance criteria as part of a quality assurance process for the UI and design aspects goes some way to helping mitigate these pitfalls.&lt;/p&gt;
&lt;p&gt;Another tool we have used in the past is the &lt;a href=&#34;https://www.humanrightscentered.design/s/Secure-UX-Checklist.pdf&#34;&gt;Digital Security and Privacy Protection UX Checklist&lt;/a&gt;. We also encourage teams to build and iterate their own security and privacy UX/UI checklists and operationalise this as part of the design to development to implementation pipeline.&lt;/p&gt;
&lt;h4 id=&#34;designers-are-continually-fulfilling-product-management-functions-in-small-teams-when-their-plates-are-already-full-prioritizing-pm-processes-that-help-design-is-critical&#34;&gt;&lt;strong&gt;Designers are continually fulfilling product management functions in small teams when their plates are already full. Prioritizing PM processes that help design is critical.&lt;/strong&gt;&lt;/h4&gt;
&lt;p&gt;Last, but by no means least, the least discussed topic in coaching was the challenge of product management absences in OSS tool teams. Many OSS teams have an absence of product management (PM) within a team member’s core role. If this role is present, those in these roles are often more knowledgeable about software development processes than design processes. This is steadily changing and PM is becoming a valued skill and role in OSS as well as the balance tipping into PM being present in the design phases of software development. The very real challenge for designers in OSS is that when absent, the role of product manager often falls to the designer during the phases of design, and often carries through to development/implementation in order to ensure that users&amp;rsquo; needs are well respected in implementation. Through our coaching we found that this split role comes naturally to designers who tend to have an inclination towards seeing software holistically across all its aspects. However, while knowing everything from how an API functions, to how back-end is organized, through to front-end frameworks, is often critical to designing integrated experiences for users, it means that less time is spent on design and more time is spent on product management. This can raise a role definition tension as well as a processes stewardship tension in the teams as product management and guiding the goals of software can be a contentious issue even if governance processes exist within the OSS and the team.&lt;/p&gt;
&lt;p&gt;We recently formalized many of our own product management processes, and have coached people on using them as templates in Miro. &lt;a href=&#34;https://miro.com/app/board/uXjVNIKYM6U=/?share_link_id=752867797584&#34;&gt;You can view these here.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_adoptable_blog_rower_hu_6e080e3fea1f5c5a.png&#34; alt=&#34;A masc presenting exercise coach and a femme presenting person using a rowing machine in exercise clothing. The coach is watching how they position the rowing bar and supporting them. Image chosen for this blog subject due to the metaphor of how coaching is like supporting people in their own training and own ability to strengthen and overcome their project challenges.&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;looking-ahead&#34;&gt;Looking ahead&lt;/h3&gt;
&lt;p&gt;We have noticed that coaching - whether it’s part of a formal organizational relationship or on a casual peer-to-peer basis - is critical work that is difficult to maintain. The main challenge here is that &amp;ldquo;formal&amp;rdquo; coaching is relatively accessible to fund, either for teams or via a funder that supports coaching organizations in reaching out to projects and individuals who would like coaching. The less formal peer-to-peer coaching that happens largely in community spaces is harder to fund and sustain and therefore, it&amp;rsquo;s hard to document the benefits, growth and positive effects on individuals and OSS tools.&lt;/p&gt;
&lt;p&gt;Coaching often allows for concentrated time to really dig into a handful of topics in detail but sometimes, coaching is also about solidarity and support for a function that is under pressure and resource constrained. In our experience this mostly applies to designers, but we have also paid attention to other under-represented functions in OSS such as product management, community engagement and building, marketing and documentation/content. &lt;/p&gt;
&lt;p&gt;Designers can crave a community of peers to help problem-solve without needing to &amp;ldquo;upskill&amp;rdquo; or have to explain “how design works” to people unfamiliar with design terms and processes eg often the time and resources required to plan and run user testing sessions is deemed as “superfluous” or “trivial”. Designers are often then tasked with explaining, often repeatedly to each OSS project, the benefits of user testing and how it saves time and money in the long run. You can read more about the benefits of user testing &lt;a href=&#34;https://www.uxdesigninstitute.com/blog/guide-to-usability-testing-for-ux/#Why_is_usability_testing_important_in_UX&#34;&gt;here&lt;/a&gt;. This design knowledge gap is another challenge we meet when coaching OSS projects with no previous design experience because we want to make design accessible and doable by all. We aim to help cultivate space in OSS projects where cross-pollination of functions and roles allows for greater respect and active support in each other&amp;rsquo;s function and the pressures that begin to stack upon roles or individuals can be better spread among the teams.&lt;/p&gt;
&lt;p&gt;Coaching is an evolving practice at Superbloom and you can find out more about &lt;a href=&#34;https://superbloom.design/about/people/#coaches&#34;&gt;our coaches here&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;Project contributors: &lt;a href=&#34;https://superbloom.design/&#34;&gt;Superbloom&lt;/a&gt;, &lt;a href=&#34;https://internews.org/&#34;&gt;Internews&lt;/a&gt;, &lt;a href=&#34;https://okthanks.com/&#34;&gt;Okthanks&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Adoptable:Coaching</title>
      <link>https://superbloom.design/work/projects/adoptable/</link>
      <pubDate>Thu, 27 Jun 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/work/projects/adoptable/</guid>
      <description></description>
    </item>
    
    <item>
      <title>How To Test Software For Usability And Usefulness When You Haven’t Finished Writing The Code</title>
      <link>https://superbloom.design/learning/blog/how-to-test-software-for-usability-and-usefulness-when-you-havent-finished-writing-the-code/</link>
      <pubDate>Wed, 19 Jun 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/how-to-test-software-for-usability-and-usefulness-when-you-havent-finished-writing-the-code/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superblooom.design_how_to_test_software_blog_bandwboxes_hu_c87d3d77d853213c.png&#34; width=&#34;740&#34; height=&#34;528&#34;&gt;
&lt;/p&gt;
&lt;p&gt;How do you find out if the software you are building is usable and useful for others? We’ve written this blog post about how to address this challenge! It is often easiest to try out the software when it’s been fully built, but this is also when any mistakes are most difficult to fix because so much has already been coded. This is a concern and a challenge for product managers, developers and UX designers alike. &lt;/p&gt;
&lt;p&gt;Users don’t care about your database access layer or your programming language. But they do care about how the software looks and behaves. In this post I demonstrate four methods to get feedback from users without having to first write all the code. These are: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Sketching&lt;/li&gt;
&lt;li&gt;Paper prototyping&lt;/li&gt;
&lt;li&gt;Creating a part of the frontend only &lt;/li&gt;
&lt;li&gt;“Developing outside-in”, that is, quickly creating a running version of the software&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The above list is in order of complexity and closeness to the finished product: Both sketching and paper prototyping do not require any code, and creating part of the frontend only requires some coding. “Developing outside-in” does not only need code, it actually builds upon code that you can (potentially) use to build the actual product.&lt;/p&gt;
&lt;p&gt;With this said, let&amp;rsquo;s look at the first of the methods, Sketching and talking. &lt;/p&gt;
&lt;h2 id=&#34;sketches-and-talking&#34;&gt;&lt;strong&gt;Sketches and talking&lt;/strong&gt;&lt;/h2&gt;
&lt;h4 id=&#34;problem&#34;&gt;Problem&lt;/h4&gt;
&lt;p&gt;Talking about your idea and concept is simple. You do not need any tools and can do it wherever you may be. However, when talking about how easy the software will be to use, it is very easy to talk about imagined results and intended impressions rather than how something appears to the user. You might say that users can “simply select an item” but this is literally easier said than done. It is also very easy to state things that turn out to be impossible: e.g. “the dialogue provides the information”, but the dialogue only fits one of the five sentences needed. Or “select one of the five buttons” when there would be only space for two. You need something more concrete, with easily usable constraints. &lt;/p&gt;
&lt;h4 id=&#34;solution&#34;&gt;Solution&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;The simplest way to obtain useful feedback is to combine your explanations with simple sketches.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Draw rough sketches of how the interface would look and work. For me, a black marker and A5 paper works well. Sketches do not need to stand on their own, but should work with your explanations. The result will be similar to a storyboard that runs in parallel with your words.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superblooom.design_how_to_test_software_blog_bandwboxes_hu_c87d3d77d853213c.png&#34; alt=&#34;Image of black writing on a white page showing Logo Search and a box and login written next to it. Underneath that, Available Tools is written and there are eight boxes under that three of them contain images, one of a gun, one of a hat, and one of a ladder&#34; width=&#34;740&#34; height=&#34;528&#34;&gt;
&lt;/p&gt;
&lt;p&gt;When creating sketches, you will probably notice problems as well as opportunities that were not as obvious when they were simply an idea. &lt;/p&gt;
&lt;p&gt;It is best to focus on a single feature or idea first; there is no need to sketch and explain everything. It’s better to start in a focussed way and iterate on it rather than do it all at once. &lt;/p&gt;
&lt;p&gt;When you have finished the sketches that illustrate the step-by-step use of a feature, it’s a good idea to show them to team members or potential users and walk them through the processes to show how the interaction with the software would work. Ask for feedback to find out if the feature makes sense and to find out if the interactions are intuitive and familiar. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: If you first want to develop ideas within your team, try the &lt;a href=&#34;https://www.jpattonassociates.com/wp-content/uploads/2015/03/design_studio_quickref.pdf&#34;&gt;Design Studio method&lt;/a&gt;, a way to collaboratively create and give feedback on designs.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; It is tempting to try out totally new ways to build interfaces, but often the most obvious solutions are the most intuitive for the users. This is because new interfaces are understood by using past experiences. Read more in Jef Raskin’s “&lt;a href=&#34;https://www.asktog.com/papers/raskinintuit.html&#34;&gt;Intuitive Equals Familiar&lt;/a&gt;”.&lt;/p&gt;
&lt;h2 id=&#34;simple-prototypes-no-code-involved&#34;&gt;&lt;strong&gt;Simple prototypes, no code involved&lt;/strong&gt;&lt;/h2&gt;
&lt;h4 id=&#34;problem-1&#34;&gt;Problem&lt;/h4&gt;
&lt;p&gt;You have ideas about how users can interact with your product. But, before you start coding, you want to test your designs and find out the strengths and problems of different approaches.&lt;/p&gt;
&lt;h4 id=&#34;solution-1&#34;&gt;Solution&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Build an interactive prototype from sketches, simulate interactions by acting as the computer and swap out parts of the interface.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Using sketches, you can try out interfaces and you can communicate them in a more concrete way. With some additional effort, you can use sketches to test the interface with users by building a paper prototype. A paper prototype shows your interface on paper, but it is interactive in a limited way. You simulate the computer and swap out parts of the interface. &lt;/p&gt;
&lt;p&gt;Providing explanations about how things work defeats the purpose of seeing how people would interact with an interface when on their own. This means that you can still opt for a simple look, but elements should be clearly recognizable i.e. labels should be readable, buttons should look like buttons etc. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superblooom.design_how_to_test_software_blog_hand_hu_8a59e46e34622e31.png&#34; alt=&#34;Image of two boxes drawn, one on top of the other on a piece of paper stuck on a page with a hand holding a pen writing in the top box and another hand is shown underneath holding the piece of paper in place&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;p&gt;The user testing the interface interacts with it by pointing to elements and saying something like “I click here” and may also fill out forms. You can get creative: Build parts that you can unfold, simulate forms using tape you can write on with a non-permanent marker, have separate pop-ups or transparent overlays. Have some blank paper ready as sometimes you’ll need to improvise and add elements. &lt;/p&gt;
&lt;p&gt;Still too abstract? &lt;a href=&#34;https://www.youtube.com/watch?v=yafaGNFu8Eg&#34;&gt;Watch this example&lt;/a&gt; for how this works!&lt;/p&gt;
&lt;p&gt;Paper prototypes are fun to create and clearly communicate that software is not yet finished; this directs feedback towards conceptual questions (do people understand how to check for the availability of an item?) and not questions of visual design (do users like this shade of green?). In our scenario, you could take the prototype to a meeting or event at the neighborhood center and ask people if they want to try it out. &lt;/p&gt;
&lt;p&gt;There are several other ways to create testable prototypes. UI design tools such as Figma or Penpot, allow you to link different views so that users can navigate between them. This is great for link-based navigation, but if there are forms to complete, it is more difficult to prototype well. The biggest caveat is that these tools are usually made to specify UIs (color, fonts, positions…), rather than to quickly try them out. Therefore, it is easy to be distracted by exact colors, the width of borders, font selection and other options. &lt;/p&gt;
&lt;p&gt;Similar link-based interactions can be prototyped with Powerpoint or LibreOffice Impress. If you have skills using spreadsheets and your application relies a lot on form-filling or visualizations, you can also prototype with Excel or LibreOffice Calc!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Read more about paper prototyping: &lt;a href=&#34;https://alistapart.com/article/paperprototyping/&#34;&gt;https://alistapart.com/article/paperprototyping/&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id=&#34;write-a-part-of-the-frontend-only&#34;&gt;&lt;strong&gt;Write a part of the frontend only&lt;/strong&gt;&lt;/h2&gt;
&lt;h4 id=&#34;problem-2&#34;&gt;Problem&lt;/h4&gt;
&lt;p&gt;Not all interactions can be easily prototyped on paper (e.g. filtering a list) and while sketches provide useful constraints about what you can and can’t do, they are still somewhat removed from how the actual UI will behave. But, how can you run your interface when you have barely written any code?&lt;/p&gt;
&lt;h4 id=&#34;solution-2&#34;&gt;Solution&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Write just parts of the interface you want to test in code and mock the rest.&lt;/em&gt; &lt;/p&gt;
&lt;p&gt;To create your first prototype of the frontend, use tools that you are familiar with, so you can get a running version of the prototype quickly, without getting bogged down by discussions about the right technology.&lt;/p&gt;
&lt;p&gt;In the end, your product will likely communicate with a server or read from a local file system. Usually, this is something you should ignore at this time: you only want to test a part of the interface. This means you mock the rest. Usually, this means you hardcode stuff into a variable that stands in for the server.&lt;/p&gt;
&lt;p&gt;It is helpful not to concern yourself with code-reuse; be OK with throwing away the code. It is a prototype, after all, and if you worry about throwing it away you have probably over-engineered it beyond its original exploratory purpose.&lt;/p&gt;
&lt;p&gt;To make sure the feedback you receive is useful, it’s important to make your prototype easy to try out and easy to distribute. Creating your prototype in a website that may be opened on a laptop or phone with a link to click on makes it easy to try out. Requiring knowledge of linux, git and docker will severely limit the range of people who can trial the prototype.&lt;/p&gt;
&lt;h2 id=&#34;developing-your-code-outside-in&#34;&gt;&lt;strong&gt;Developing your code outside-in&lt;/strong&gt;&lt;/h2&gt;
&lt;h4 id=&#34;problem-3&#34;&gt;Problem&lt;/h4&gt;
&lt;p&gt;Now you are ready to start writing code for the real thing, i.e. not a prototype. Usually the code consists of several parts that need to work together (frontend/backend, Model/View/Controller etc.) Now, there is a danger of not planning enough and ending up with parts that don’t work together, or planning too much and getting stuck in analysis. In both cases, you may end up with a system that you can never try because a part does not work or refuses to play with others.&lt;/p&gt;
&lt;h4 id=&#34;solution-3&#34;&gt;Solution&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;With your team members define the required parts of code. First, write the interfaces/contracts: The data they need and the data they provide. For now, enable the parts to simply exchange mock data. Afterwards, develop these components outward-in, always to keep the data exchange working. That way, you will always have a running system that you can demo!&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The solution is to first focus on the communication between the parts and then build the system from the interfaces between the parts, outside-in. This might be counterintuitive, as it seems plausible for many to build inside-out, starting with an abstract core in each part of the system and then, at the very end, connect all of them together. But this means that you need to gamble on being able to connect the parts in the end, and that you always know what you are working towards, which is a great risk. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superblooom.design_how_to_test_software_blog_blue_boxes_hu_3b78e42333883b89.png&#34; alt=&#34;Image of four boxes giving an overview of outside-in development and inside-out development&#34; width=&#34;740&#34; height=&#34;609&#34;&gt;
&lt;/p&gt;
&lt;p&gt;If you first decide upon the way that parts of the software will talk to each other, you will immediately get a running version of the software: The parts won’t yet do anything, but they will exchange mock data. That is enough to test if they work together. Then you can work on the components separately and reduce the mock data step by step. The backend- and frontend programmer might define what the HTTP-API should do to enable the core functionality: What should the frontend request, what should the server return? This is what forms the contract for how the parts communicate with one another. Now, the frontend programmer writes a function requesting data from the API and the backend-programmer writes a request handler that returns mock data. Then try it out. If it works, you can start to both build the interface and the backend. It is relatively easy to recognize the situations where you need the parts to talk to each other:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;When the contract needs to be extended e.g. when more data is needed from the server&lt;/li&gt;
&lt;li&gt;When the contract needs to be changed, e.g. the API is restructured&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superblooom.design_how_to_test_software_blog_people_hu_d56a21743ff7a415.png&#34; alt=&#34;Black and white image of two people with a speech bubble above. One says &amp;ldquo;So, you need&amp;hellip; and I need&amp;hellip;&amp;rdquo; and the other says &amp;ldquo;Yes!&amp;rdquo;&#34; width=&#34;740&#34; height=&#34;767&#34;&gt;
&lt;/p&gt;
&lt;p&gt;In all circumstances you should keep the system running, so if you e.g. extend the API, talk to your collaborators, define the data to be exchanged, mock it and then integrate the change with the self-contained part. &lt;/p&gt;
&lt;p&gt;This method is also called tracer bullet development and is described in more detail in the books &lt;a href=&#34;https://pragprog.com/titles/prj/ship-it/&#34;&gt;Ship It!&lt;/a&gt; and &lt;a href=&#34;https://pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition/&#34;&gt;The Pragmatic Programmer&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;conclusion&#34;&gt;C﻿onclusion&lt;/h2&gt;
&lt;p&gt;When working on a project, you can use the methods in the order they appear in this blogpost: Early on you can start with sketching and talking, and then try crucial parts of the interface using paper prototyping. Then, when you have a good idea of what to build, see how it works on a screen by creating a part of the frontend only. When it comes to writing larger parts of the code, developing your code outside-in can ensure that you always have a running version that integrates all of the crucial parts, and allows you, your team and potential users to actually run your software while you write it. &lt;/p&gt;
&lt;p&gt;I wrote this guide in the hope that it assists anyone writing user-facing software in general, and in particular for &lt;a href=&#34;https://prototypefund.de/&#34;&gt;Prototype Fund&lt;/a&gt; coaching projects. If you’ve tried the methods outlined, I would be happy to hear about your experiences – drop me a mail at &lt;a href=&#34;mailto:d_jan@ymail.com&#34;&gt;d_jan@ymail.com&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;C﻿redits&lt;/h2&gt;
&lt;p&gt;Thanks to Saptak S for reviewing.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Prototype Fund</title>
      <link>https://superbloom.design/work/projects/prototype-fund/</link>
      <pubDate>Wed, 19 Jun 2024 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/work/projects/prototype-fund/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Centering People Who Change Who Technology Serves: Fiscal Sponsorship at Superbloom</title>
      <link>https://superbloom.design/learning/blog/fiscal-sponsorship-update-mar2024/</link>
      <pubDate>Fri, 01 Mar 2024 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/fiscal-sponsorship-update-mar2024/</guid>
      <description>&lt;p&gt;Superbloom&amp;rsquo;s mission is to change who technology serves. We leverage fiscal sponsorship as a tool to support the growth and maturity of the digital rights and Internet Freedom communities, with a focus on human-centered research and design. &lt;br&gt;
&lt;br&gt;
Looking for potential fiscal sponsorship options? Please fill out the inquiry form and we&amp;rsquo;ll follow up with you.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/fiscal-sponsorship-interest/&#34; class=&#34;button button--primary read-more&#34;&gt;Fiscal Sponsorship Inquiry&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Superbloom piloted its &lt;a href=&#34;https://superbloom.design/community/our-support/#fiscal-sponsorship&#34;&gt;fiscal sponsorship program&lt;/a&gt; in early 2020, and now hosts five fiscally sponsored projects. We&amp;rsquo;ve also been early adopters of efforts like &lt;a href=&#34;https://opencollective.com&#34;&gt;Open Collective&lt;/a&gt;, focusing on the power of transparency and usable donation tools as critical digital infrastructure in the ecosystem.&lt;/p&gt;
&lt;p&gt;We were saddened to learn about the &lt;a href=&#34;https://blog.opencollective.com/open-collective-official-statement-ocf-dissolution/&#34;&gt;changes at Open Collective Foundation&lt;/a&gt;, but want to help out. If you are helping hosts find fiscal sponsors or if you are a fiscally sponsored project whose mission aligns with our mission — please reach out.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;L﻿earn more about &lt;a href=&#34;https://superbloom.design/community/our-support/#fiscal-sponsorship&#34;&gt;fiscal sponsorship&lt;/a&gt; at Superbloom.&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Untangling Digital Spaghetti: Gina Giampaolo on CS&amp;S Website Refresh</title>
      <link>https://superbloom.design/learning/blog/untangling-digital-spaghetti-gina-giampaolo-on-cs-s-website-refresh/</link>
      <pubDate>Thu, 21 Dec 2023 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/untangling-digital-spaghetti-gina-giampaolo-on-cs-s-website-refresh/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_untangling_digital_spaghetti_image_1_hu_ddf1542d3cc3fd98.png&#34; alt=&#34;An illustration of a fork hovering over a plate of spaghetti and web page boxes with the words information architecture! multiple sites! and branding! Oh my!&#34; width=&#34;740&#34; height=&#34;491&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;We worked with developer and designer &lt;a href=&#34;mailto:hello@whoisgina.com&#34;&gt;Gina Giampaolo&lt;/a&gt; to refresh the Code for Science &amp;amp; Society website in 2022. We caught up with Gina to reflect on the project and talk about design in civic tech.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In 2022, we were lucky enough to work with Code for Science &amp;amp; Society to revamp its &lt;a href=&#34;http://codeforsociety.org&#34;&gt;website&lt;/a&gt;. We partnered with designer and developer &lt;a href=&#34;mailto:hello@whoisgina.com&#34;&gt;Gina Giampaolo&lt;/a&gt; to: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Refresh the look, feel, information architecture, and navigation of the website so that it clearly communicates the organization&amp;rsquo;s mission, vision, and programs.&lt;/li&gt;
&lt;li&gt;Improve and simplify the experience of editing the website by implementing a well-documented, easy to use CMS.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For non-profit organizations, websites play many roles. A website not only showcases the organization’s mission and vision through its declaration of values and brand identity, it often acts as a repository of the org’s work. Sites act as a catalog of past and current projects and their impact, a resource library of useful and replicable content for the community, a source of event and gathering information, and a key place to talk about what they do on a day-to-day basis. We recognized through this and other similar projects that an organization’s website is actually critical digital infrastructure for serving its mission. So taking it seriously and deeply understanding the needs for CS&amp;amp;S’s unique case was critical. &lt;/p&gt;
&lt;h4 id=&#34;from-concept-to-reality&#34;&gt;From concept to reality &lt;/h4&gt;
&lt;p&gt;Understanding the website as a critical hub and resource for CS&amp;amp;S, we dug into the goals, needs, and desires that CS&amp;amp;S staff had for their site through user research. After 12 interviews with staff and stakeholders and one focus group, we landed on some key findings about its old website: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The site’s content was buried, out of date, and not easily navigable.&lt;/li&gt;
&lt;li&gt;CS&amp;amp;Ss program strategy and the impact of their programs and fiscally sponsored projects were not effectively showcased.&lt;/li&gt;
&lt;li&gt;The team wanted to have more agency in editing and maintaining the website, but the infrastructure wasn’t usable or well documented enough to support them. As the org had grown, multiple websites were created to fulfill different needs, and each used different website hosting technologies and had different editing processes, which made it very difficult for the org to maintain. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We also landed on common values for the future of the site: &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_untangling_digital_spaghetti_image_2_hu_56d3c75a19b71659.png&#34; width=&#34;740&#34; height=&#34;436&#34;&gt;
&lt;/p&gt;
&lt;p&gt;From there, we worked on the Information Architecture needed to unify the disparate sites into one main hub, expanded the existing CS&amp;amp;S brand to work for the web, and designed the UX and UI of the website,  and set up a holistic CMS with the fearless direction of &lt;a href=&#34;mailto:hello@whoisgina.com&#34;&gt;Gina Giampaolo&lt;/a&gt;.  We decided to interview Gina about her experience working on the project since she played such a critical role. We’re happy to say the &lt;a href=&#34;http://codeforsociety.org&#34;&gt;CS&amp;amp;S website&lt;/a&gt; has been up-and-running successfully for about a year now! &lt;/p&gt;
&lt;h3 id=&#34;interview-with-gina-giampaolo&#34;&gt;Interview with &lt;a href=&#34;mailto:hello@whoisgina.com&#34;&gt;Gina Giampaolo&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Introduce yourself!&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;I’m Gina Giampaolo. I’m a developer and designer living and working in Portland, Oregon. I went independent back in 2021 and since then have been building websites that help organizations and individuals wrangle lots of data in useful ways. I’m a competitive powerlifter and love big trees, video games, sewing garments, and all things fiddly and complicated.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;How did you become familiar with CS&amp;amp;S and its work?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I used to work at Rumors (RIP) with Andy Pressman, who is Danielle Robinson, the Executive Director of CS&amp;amp;S’s partner. So I’ve basically just been in the neighborhood for a long time, ha! CS&amp;amp;S supported a short-lived meetup called Dat Night (also RIP) that was all about introducing Dat (and another RIP) to non-developers, specifically artists and makers. I worked with them a bit back in 2019, and again in 2021 providing website support and some design work, before we started on the CS&amp;amp;S site rebuild in earnest in 2022.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Tell us a bit about your approach to design and development&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;My favorite things to build are applications that unite a lot of disparate data and processes in one place in a way that both supports the people using the tool and presents information clearly. I want the editor experience to be just as good as the front end user experience. This is an interesting challenge that has come along with the explosion of website building tools and frameworks — you have to actually design and build, not just the end user experience of the website, but the editor experience. A good, usable editor experience is critical for small organizations as they don’t often have a dedicated web team or communications team, and the website is the platform for their organization.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What, to you, is the importance of design in the world of public interest tech and science? What motivates you as a designer and developer in the space?&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;I think that design can facilitate the communication of the really complex and exciting ideas that are often kicking around in public interest tech, and demystify that complexity – understanding a process is the first step to supporting it. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What about this process was most exciting to you when we got started?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Okay so CS&amp;amp;S had a lot of websites, which I think is normal for an org like this that’s running events, starting initiatives, taking on new projects, etc. There was a lot of digital spaghetti to untangle, and the idea of getting it sorted into a new supportive system was very satisfying.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What part of the website or system you created are you most proud of?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Resources! Originally, we hadn’t planned to focus on the resources at all, but once we got talking about it it was impossible to not build it because everyone was so excited about it. Resources and knowledge development are core to CS&amp;amp;S’s DNA and mission as an organization, so not developing this key functionality would’ve been leaving them with a website that didn’t meet their needs nor their mission and vision.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What part of this process was the most challenging?&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;It’s always hard to communicate just how “loaded” a design is. The schema is represented in the content shown, but the structure of a page or section mirrors content hierarchies that are set up in the back end in often much more complex ways. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What are some challenges you&amp;rsquo;ve encountered working as a designer and developer in the open-source, public interest, and/or nonprofit space?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In terms of design practices, there are too many cooks in the kitchen sometimes, flatter organizational hierarchies sometimes mean random people show up with a whole lotta feedback and you’ve gotta manage expectations around that, but politely!&lt;/p&gt;
&lt;p&gt;In development, open source at all cost is sometimes restrictive … but I get it. Lots of excitement about new tools that get quickly abandoned and become unusable, so you can end up with a graveyard of statically generated sites pretty quickly.&lt;/p&gt;
&lt;p&gt;Lastly, lots of extremely knowledgeable people and institutional knowledge that never makes it outside because there’s not a concerted effort made to communicate those ideas effectively to outside audiences. Good stuff gets trapped in brilliant brains!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What’s next for you?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I’m building a subscription platform for a friend using Craft CMS, yet another case of pulling a whole lot of disparate stuff into one place in a way that is easy to use and functional for her needs. &lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;Project Contributors: Susan Kennedy (now at Open Technology Fund), Katie Wilson, &lt;a href=&#34;mailto:hello@whoisgina.com&#34;&gt;Gina Giampaolo&lt;/a&gt;, CS&amp;amp;S staff including: &lt;a href=&#34;mailto:danielle@codeforsociety.org&#34;&gt;Danielle Robinson&lt;/a&gt;, Joe Hand, Page Metcalf, Jessica Hardwicke, Moni Awolesi, Rayya El Zein, and Angela Okune.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>CS&amp;S Web and Content Strategy</title>
      <link>https://superbloom.design/work/projects/css/</link>
      <pubDate>Tue, 19 Dec 2023 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/work/projects/css/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Requiem for Cyberspace and the Next Theory of Change for IoT</title>
      <link>https://superbloom.design/learning/blog/requiem-for-cyberspace-and-the-next-theory-of-change-for-iot/</link>
      <pubDate>Fri, 15 Dec 2023 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/requiem-for-cyberspace-and-the-next-theory-of-change-for-iot/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_requiem-for_cyberspace_image_2_hu_a0ff1c294bb37dee.png&#34; width=&#34;740&#34; height=&#34;740&#34;&gt;
&lt;/p&gt;
&lt;p&gt;The dream of the ‘90s is over. We now have an Internet of Things thriving in physical space where our bodies live instead of a Cyberspace envisioned as a realm solely of the mind. That&amp;rsquo;s cause for optimism as we consider how resilient organizations can collaboratively build a different future in this, our physical reality.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Note: This essay was written in December 2022 as a personal reflection on four years of education, design, and tech policy with the &lt;a href=&#34;https://cordis.europa.eu/project/id/813508.&#34;&gt;Open Design of Trusted Things&lt;/a&gt;, an EU Horizon 2020 program, as contrasted with experiences in the 1990’s tech community in the San Francisco Bay Area. It originally appeared in &lt;a href=&#34;https://ec.europa.eu/research/participants/documents/downloadPublic?documentIds=080166e5f91e892a&amp;amp;appId=PPGMS&#34;&gt;Reboot IoT: Regain Trust/Refresh Hope&lt;/a&gt;, edited by Jon Rogers and Michelle Thorne.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;John Perry Barlow’s 1996 manifesto against government regulation, &lt;a href=&#34;https://www.eff.org/de/cyberspace-independence&#34;&gt;Declaration of Independence of Cyberspace&lt;/a&gt;, laid out a naive vision of the internet as a self-organizing place guided only by the Golden Rule. At a time when computer equipment, internet connections, and email addresses were primarily housed at universities with private access restricted to the wealthiest people in the world, Barlow drew artificial battle lines with the government on one side and a disembodied group of denizens of Cyberspace on the other.&lt;/p&gt;
&lt;p&gt;This techno-libertarian tract would go on to shape internet culture and was published from the World Economic Forum in Davos, Switzerland. Barlow wrote, “Our identities have no bodies, so, unlike you, we cannot obtain order by physical coercion. We believe that from ethics, enlightened self-interest, and the commonweal, our governance will emerge.”&lt;/p&gt;
&lt;h2 id=&#34;1990s-cyberspace-is-dead&#34;&gt;1990s cyberspace is dead&lt;/h2&gt;
&lt;p&gt;Twenty-seven years later, this way of thinking is as embarrassingly dated as the thinking of the “weary governments of the Industrial World” was to Barlow. Of course Cyberspace is not separate from the material world. Of course people have bodies. Of course those bodies inform online experiences. And of course the sensors of Internet of Things (IoT) devices installed in physical places have made the idea of Cyberspace as a civilization of the mind obsolete.&lt;/p&gt;
&lt;p&gt;Unsurprising for the World Economic Forum, Barlow&amp;rsquo;s Declaration of Independence of Cyberspace is founded on the idea of marketplaces as the obvious organizing principle for society. This ethos spawned a tech ecosystem where a handful of software companies headquartered in the United States, a physical place with a particular set of cultural values and legal frameworks, shape the internet experience for the global majority.&lt;/p&gt;
&lt;h2 id=&#34;maybe-companies-will-save-us-from-government&#34;&gt;Maybe companies will save us from government&lt;/h2&gt;
&lt;p&gt;Over time the “us” of Barlow’s Cyberspace, the group opposed to government intervention, has been consolidated into publicly-traded companies acting as custodians of the internet. The commercialization of the internet, and the associated infrastructure for innovation and product development produced an explicitly capitalist theory of how technology changes.&lt;/p&gt;
&lt;p&gt;Consumers buy products that change company behavior as they produce more products to meet demand and stop producing products for which there is no demand. &lt;/p&gt;
&lt;h2 id=&#34;no-companies-wont-change-when-it-hurts-profits&#34;&gt;No, companies won’t change when it hurts profits&lt;/h2&gt;
&lt;p&gt;What can people do to change technology? Buy different things. In the advertising-fueled context of surveillance capitalism, that means not only buying alternative products, but directing attention differently: viewing different content, configuring different options, and spending time differently. The ecosystem of innovation and product development running on Human-Centered Design practices relies on a similar model of tracking user behavior to understand how to allocate resources to make product changes. The vocabulary of user engagement, organic traffic, time on task, and conversion rates guides investment.&lt;/p&gt;
&lt;p&gt;Under this paradigm, individual choice and individual responsibility to select and configure products are presented as central to this model, with individuals suffering the consequences of their mistakes. If their privacy is violated, money wasted, reputation damaged, that’s a consequence of not understanding the application, reading the fine print or being an informed customer. The public interest tech community works for change within this system through policy and advocacy campaigns to raise awareness of issues, educate people to use different products, and train them in how to use available products differently. &lt;/p&gt;
&lt;p&gt;The result of the 1990s dream of a Cyberspace free from government control is an internet with power firmly consolidated within a small number of quasi-monopolistic companies, a configuration recognizable from the industrial age. No place is this clearer than in the consumer IoT space, which is dominated by Amazon products (i.e. Alexa voice assistant, Echo smart speakers, and Ring connected doorbells), and Google products, (i.e. Google voice assistant, Nest thermostats, cameras, speakers, and doorbells). The fresh companies of the 1990s became the same type of “weary giants” Barlow abhorred.&lt;/p&gt;
&lt;h2 id=&#34;maybe-governments-will-save-us-from-companies&#34;&gt;Maybe governments will save us from companies&lt;/h2&gt;
&lt;p&gt;How did we get here? Barlow’s trust in markets was misplaced, and today’s companies are “imposing tyrannies” the way he feared governments would. What if governments are needed to protect people from companies? How would treating people as citizens rather than customers change technology development? Within the European Union, where governments enjoy more positive reputations than tech companies, this has become the dominant view, resulting in a different Theory of Change. &lt;/p&gt;
&lt;p&gt;People elect governments to create regulations that change tech company behavior to protect citizens. &lt;/p&gt;
&lt;p&gt;It’s worth pointing out that democracy and elections are not necessary for this Theory of Change. Governments can also make and enforce laws without input from the public. There is nothing inherently democratic about regulation, but in a European context, the actions people take as citizens to change technology rely on democratic processes. The public interest tech community and associated policy and advocacy campaigns still have an awareness-building and educational focus, but the motor of change is not commercial activity. Instead citizens are encouraged to sign petitions, make their views known to politicians, elect different people, and comment on proposed legislation.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.eff.org/de/cyberspace-independence&#34;&gt;The Declaration&lt;/a&gt; addresses this, “Governments derive their just powers from the consent of the governed. You have neither solicited nor received ours. We did not invite you.” Contemporary Europeans are enthusiastically inviting their government to regulate technology. Enforcement of regulations is essential to this model because companies are motivated by profit to avoid expensive fines, costly legal proceedings, and the potential loss of customers in markets where their products become illegal. &lt;/p&gt;
&lt;p&gt;Yet looking at the state of technology regulation and enforcement, there is cause for alarm. Despite the General Data Protection Regulation (GDPR) in the EU providing broad privacy protection for citizens, day-to-day experience of using technology from Big Tech has changed little, and companies are making record profits without making high-profile changes. The implementation of GDPR has offloaded responsibility to individuals, who again bear responsibility for clicking the right boxes and making the right configuration choices, for example by refusing consent to data collection.  &lt;/p&gt;
&lt;h2 id=&#34;no-governments-are-not-helping-quickly-enough&#34;&gt;No, governments are not helping quickly enough&lt;/h2&gt;
&lt;p&gt;Does that mean governments are unsuited to the task of changing technology? No. Governments such as the European Union work in a slow, consensus-building, multilateral way. Compared to product development cycles driven by quarterly earnings, the years-long approach of regulation is glacial by comparison. However, time is of the essence because IoT devices pose an urgent threat by extending a web of surveillance beyond the screens of 1990s Cyberspace and into the homes, schools, stores, streets, hospitals, and transit hubs of today.&lt;/p&gt;
&lt;p&gt;The simplistic binary of governments versus companies also ellides the complicated ways they work together, sometimes in ways that compromise the rights of citizens and consumers. For example, public-private partnerships abound for deploying IoT devices in civic infrastructure. Touted benefits such as saving tax-payer money and benefiting from companies’ previous experience developing technology has led to joint projects in areas including regulation of parking, monitoring usage of public transit, and managing crowds. Controlling the spread of disease during pandemic and conserving energy during a war are adding pressure for more public-private collaborations. Yet unclear models for data ownership, transparency, and accountability in these alliances between governments and companies create opportunities for misuse that threaten the public well-being.&lt;/p&gt;
&lt;h2 id=&#34;is-anybody-coming-to-save-us&#34;&gt;Is anybody coming to save us?&lt;/h2&gt;
&lt;p&gt;Despite growing threats and the absence of any quick-fixes, there are still causes for optimism. First, the user experience design techniques that developed current IoT products can be applied to undo some of the harms those products cause. Studying how ideas move from policies to pixels can create new processes for change. In this approach, policies are embodied in the user interface and change the user experience in visible ways. Awareness and education move from abstract media campaigns directly into the interface. The work of policy, regulation, and enforcement is disproportionately textual, while the experience of using the internet, particularly with connected devices, is not. &lt;/p&gt;
&lt;h2 id=&#34;policies-become-pixels-and-sounds-and-movements&#34;&gt;Policies become pixels (and sounds and movements)&lt;/h2&gt;
&lt;p&gt;Exploring interaction design patterns and systems that demonstrate how policies are expressed in interfaces closes the feedback loop of user behavior and tech change. The regulation discussion shifts from the featureless expanse of generic Cyberspace to an embodied experience: where do the eyes suggest to click to navigate a menu, what to say to activate a voice assistant, which alert sounds convey an appropriate amount of urgency, and how does a device feels in the hand as it moves? Expanding the rich vocabulary of sensorial qualities for interacting with IoT devices beyond the corporate product design world can include more people in creating those experiences, including policy makers and the public. User experience design practices such as flow diagrams and system maps make it easier to identify manipulative elements of deceptive designs and to combat them. The internet may still be 0s and 1s, but discussion of it should not be only alphanumeric.&lt;/p&gt;
&lt;h2 id=&#34;intentionally-resilient-organizations&#34;&gt;Intentionally resilient organizations&lt;/h2&gt;
&lt;p&gt;A second reason for optimism are promising experiments with organizational resilience. The current climate crisis, wars, natural resource shortages, and pandemics all require new approaches that explore systems of power in a time of decaying trust in institutions. Plugging a fraying social safety net with corporate apps will not solve these problems. But encouragingly, these cataclysmic shifts have provided fertile ground for new kinds of organizations that side-step companies, governments, and public-private partnerships.&lt;/p&gt;
&lt;p&gt;Mutual accountability makes organizations resilient in the face of change and uncertainty. Neighborhood groups, trade associations, investment clubs, coalitions, labor unions, data ownership collectives, and membership organizations of many kinds are thriving. One factor driving this renaissance is a new attention to governance and organizational structures. Being intentional about how these structures work and explicitly naming and identifying power is an exciting alternative to waiting for top-down answers. &lt;/p&gt;
&lt;p&gt;New collective governance structures can also subvert the emphasis on individual action and individually born harm. Other ways of being beyond being a more informed consumer or engaged citizen emerge. When help isn’t coming from companies or governments, people known to each other working in a decentralized manner have capabilities those centralized power structures lack. We can help each other. Collectively, we are better equipped to fight back against technology that threatens our freedoms leaving us helpless. &lt;/p&gt;
&lt;p&gt;Re-examining Cyberspace as described by Barlow as “both everywhere and nowhere, but it is not where bodies live,” through an IoT lens exposes this as a dangerously out-moded way of thinking. The IoT happens where our bodies live, and embodied action is the only possibility for addressing its potential harms. Two starting points to address those harms are putting policies into pixels and designing resilient organizations with innovative governance structures. Building on these suggestions, we can collaboratively build a different future.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;We can save each other.&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Contributors: &lt;a href=&#34;https://superbloom.design/about/people/ame/&#34;&gt;Ame Elliott&lt;/a&gt;, industry expert for the Open Design of Trusted Things project. Team of &lt;a href=&#34;https://ec.europa.eu/research/participants/documents/downloadPublic?documentIds=080166e5f91e892a&amp;amp;appId=PPGMS&#34;&gt;Reboot IoT: Regain Trust/Refresh Hope&lt;/a&gt;: Michelle Thorne, Jon Rogers, Georgia Bullen, Babitha George, Davide Gombe, Solana Larsen, Kasia Odrozek, Irini Papadimitriou, Bas Raijmakers, and Geke van Dijk. A special thank you to the Early Stage Researchers, faculty, and staff of the OpenDoTT programme.&lt;/p&gt;
&lt;p&gt;H2020 MSCA-ITN 2018&lt;br&gt;
&lt;a href=&#34;https://cordis.europa.eu/project/id/813508&#34;&gt;This project&lt;/a&gt; received funding from the European Union’s &lt;a href=&#34;https://research-and-innovation.ec.europa.eu/funding/funding-opportunities/funding-programmes-and-open-calls/horizon-2020_en&#34;&gt;Horizon 2020&lt;/a&gt; research and innovation programme under the Marie Skłodowska-Curie grant agreement No. 813508.&lt;/p&gt;
&lt;p&gt;F﻿unded by the &lt;a href=&#34;https://european-union.europa.eu/index_en&#34;&gt;European Union&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Finance &amp; Operations Manager</title>
      <link>https://superbloom.design/community/opportunities/finance-and-operations-manager/</link>
      <pubDate>Wed, 13 Dec 2023 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/community/opportunities/finance-and-operations-manager/</guid>
      <description>&lt;p&gt;&lt;strong&gt;H﻿iring for this role is currently paused.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The Role&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Superbloom is seeking a full-time remote Finance and Operations Manager (in US Central or Eastern Time Zones, or UK/EU in GMT Zones, with immediate availability) to help develop and manage its finances and operations. This role will report to the Executive Director.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;About Us&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design&#34;&gt;Superbloom&lt;/a&gt;, previously known as &lt;a href=&#34;https://simplysecure.org/&#34;&gt;Simply Secure&lt;/a&gt;, leverages design as a transformative practice to shift power in the tech ecosystem. We apply a holistic approach and view design as an intervention opportunity to center people and their needs. Our vision is a world where everyone has the knowledge, network, and digital tools needed to enrich their lives. Launched in 2014, Superbloom is a US 501(c)3 nonprofit design and research organization, leveraging practices from human rights, systems thinking, service design and threat modeling to help teams design technology and services that center and protect communities’ most vulnerable needs. Since 2020, we have been piloting fiscal sponsorship as a leadership development and support program, incubating emerging efforts that align with our mission.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;About You&lt;/strong&gt; &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You have proven experience in financial management in a US nonprofit organization.&lt;/li&gt;
&lt;li&gt;You are adept at using web-based applications to work with a remote team both in the US and in Europe, and can help us manage our finances and processes in a scalable way. &lt;/li&gt;
&lt;li&gt;You have a strong understanding of nonprofit accounting principles and fund accounting.&lt;/li&gt;
&lt;li&gt;You have excellent analytical, communication, and interpersonal skills.&lt;/li&gt;
&lt;li&gt;You have three or more years experience with Quickbooks and financial management.&lt;/li&gt;
&lt;li&gt;You have knowledge of multi-currency accounting and transactions.&lt;/li&gt;
&lt;li&gt;You have advanced knowledge of Google Workspace (Gmail, Google Drive, Docs, Sheets, Calendar and Google Meet).&lt;/li&gt;
&lt;li&gt;You have proficiency in financial software and Microsoft Excel.&lt;/li&gt;
&lt;li&gt;You have the ability to work independently, prioritize tasks, and meet deadlines.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Nice to Have&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Bachelor’s degree in Finance, Accounting, or a related field. &lt;/li&gt;
&lt;li&gt;CPA or other relevant certifications.&lt;/li&gt;
&lt;li&gt;Experience working with fiscally sponsored projects.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Responsibilities&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Financial Planning and Analysis:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Develop and implement financial strategies that align with the organization’s mission and objectives.&lt;/li&gt;
&lt;li&gt;Prepare and analyze financial reports, forecasts, and budgets to support decision-making and provide insights to the leadership team.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Budget Management:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Collaborate with program managers to develop program budgets and ensure adherence to financial goals.&lt;/li&gt;
&lt;li&gt;Monitor and track budget performance, identifying variances and proposing corrective actions as needed.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Financial Reporting:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Prepare accurate and timely financial statements, including income statements, balance sheets, and cash flow statements.&lt;/li&gt;
&lt;li&gt;Ensure compliance with regulatory requirements and reporting standards for nonprofit organizations.&lt;/li&gt;
&lt;li&gt;Manage third-party bookkeeping team to ensure invoices, receipts and expense claims are processed in a timely manner and to support accurate financial reporting.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Grant Management:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Oversee the financial aspects of grant proposals and reports, ensuring compliance with grant requirements.&lt;/li&gt;
&lt;li&gt;Work closely with program managers to track grant spending and provide financial updates and invoices to grantors.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Audit and Compliance:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Coordinate annual financial audits and liaise with external auditors.&lt;/li&gt;
&lt;li&gt;Ensure compliance with relevant accounting standards, tax regulations, and nonprofit financial reporting requirements.&lt;/li&gt;
&lt;li&gt;Assist with quarterly and annual financial review.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Cash Flow Management:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Manage cash flow to ensure the organization’s financial stability and liquidity.&lt;/li&gt;
&lt;li&gt;Implement effective strategies for cash management and forecasting.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Financial Policies and Procedures:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Develop and maintain financial policies and procedures to ensure internal controls and accountability.&lt;/li&gt;
&lt;li&gt;Train and educate staff on financial policies and procedures.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Team Collaboration:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Collaborate with other departments to provide financial guidance and support for various projects and initiatives.&lt;/li&gt;
&lt;li&gt;Act as a key liaison between the operations team and other departments.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Operations:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Administer and manage our contracting process, including developing, processing, tracking and filing service agreements and vendor contracts ensuring appropriate tax documentation is received and completed.&lt;/li&gt;
&lt;li&gt;Support our fiscally sponsored projects in all things operations and financial.&lt;/li&gt;
&lt;li&gt;Lead operational and financial processes for our fiscally sponsored projects. &lt;/li&gt;
&lt;li&gt;Assist management in planning and preparing board meeting packets including filing meeting minutes, drafting resolutions and other board documentation as needed.&lt;/li&gt;
&lt;li&gt;Support the team on grants writing, management and reporting.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Work Hours and Benefits&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This position is for a full-time employee, 40 hours per week with availability during our core work hours (8-5pm ET), at 78,500-98,500 USD per year depending on experience. Benefits include health insurance, unlimited PTO, 401(k), generous parental leave, and a monthly tech stipend.&lt;/p&gt;
&lt;p&gt;Sound like a good fit?&lt;/p&gt;
&lt;p&gt;Please email us at &lt;a href=&#34;mailto:jobs@superbloom.design&#34;&gt;jobs@superbloom.design&lt;/a&gt;, including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Resumé.&lt;/li&gt;
&lt;li&gt;Cover letter&lt;/li&gt;
&lt;li&gt;1-2 references. References will be taken in the last phase of application review.&lt;/li&gt;
&lt;li&gt;The times you are available for approx 45 minutes to 1 hour for interviews within our working hours (9am to 5pm Eastern Standard Time).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;This position is open until filled, and applications will be evaluated on a rolling basis. Reach out to &lt;a href=&#34;mailto:jobs@superbloom.design&#34;&gt;jobs@superbloom.design&lt;/a&gt; with any questions.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Superbloom is an equal opportunity employer. We believe that systemic bad behaviors disproportionately hurt the most marginalized people in society — including people of color, people from working class backgrounds, women, and LGBTQ people. We believe that these communities must be centered in the work we do. We strongly encourage applications from people with these identities or who are members of other marginalized communities. &lt;/p&gt;
&lt;p&gt;We are open to candidates located in US Central and Eastern time zones and UK/GMT zones. Final hiring decisions will be contingent upon our ability to contract and pay in the candidate’s country. Superbloom does not provide relocation or visa support. &lt;/p&gt;
&lt;p&gt;We thank all applicants for their interest; however, only those selected for an interview will be contacted.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Feira 2023: Reflecting, Reconnecting, and Revitalizing</title>
      <link>https://superbloom.design/learning/blog/feira-2023-reflecting-reconnecting-and-revitalizing/</link>
      <pubDate>Wed, 06 Dec 2023 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/feira-2023-reflecting-reconnecting-and-revitalizing/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_feira_2023_reflecting_reconnecting_and_revitalizing_image_1_hu_d6b85501aca92806.png&#34; width=&#34;740&#34; height=&#34;598&#34;&gt;
&lt;/p&gt;
&lt;p&gt;In September 2023, we were able to &lt;a href=&#34;https://superbloom.design/learning/blog/the-feira-the-global-gathering-2023-will-you-join-us-there/&#34;&gt;participate&lt;/a&gt; in Feira, the Global Gathering, a festival for digital rights defenders, convened by Team Community. The Feira was a three day social and networking festival hosted in Estoril, Portugal on September 15 - 17, 2023. The event, designed, modeled and named for the concept of a community market, was created to provide digital rights defenders with a space to connect with others in the digital rights community for informal meetups, discussions, and joy — particularly as this was the first time gathering in-person for most participants since before the start of the COVID19 pandemic. &lt;/p&gt;
&lt;p&gt;A few folks were able to attend from Superbloom and its &lt;a href=&#34;https://superbloom.design/community/our-support/&#34;&gt;fiscally sponsored projects&lt;/a&gt;, and so we asked them to reflect on their experience, their learnings, and overall takeaways from the event.&lt;/p&gt;
&lt;h3 id=&#34;what-did-you-expect-from-the-event-and-how-did-it-meet-your-expectations&#34;&gt;What did you expect from the event and how did it meet your expectations?&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Eriol&lt;/strong&gt;: I’m always pleasantly surprised by the enthusiasm and welcome perspectives of designers who attend human rights technology spaces. I often expect design and user experience experts to receive cautious inclusion into spaces where technologists and coders have majority representation.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Jamie&lt;/strong&gt;: After being away from the civil society space for a few years, attending Feira, reconnecting with past peers, and meeting new people passionate about digital security and human rights technology was wonderful. Feira was a welcoming place to share our different experiences and perspectives in different types of non-traditional conference configurations. Having flexibility with the physical space allowed the sessions to be more interactive, more creative, more collaborative, more intimate, and more productive.&lt;/p&gt;
&lt;h3 id=&#34;what-were-your-key-takeaways-from-feira&#34;&gt;What were your key takeaways from Feira?&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Eriol&lt;/strong&gt;: It is always important to have a voice for users present in spaces which will be perceived as highly technical. Bringing a perspective such as &amp;ldquo;What about if a user has no idea what the details for a network data on internet shutdowns really means, how can they understand what their experiences and information could contribute?”. This was one question I brought to a session focused on internet shutdown data and how (and whether) to define what types of shutdowns occur. The focus leaned into the data and numbers and the things that are typically focused on by technical people. We worked with those with a security and privacy trainer perspective in balancing the focus to include the real life use of and participation in tools, and systems that help protect users during shutdowns.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Matt&lt;/strong&gt;: We were grateful to have space to connect with the digital rights and internet freedom community through our product demo booth. At our booth, we shared our open directory of digital security projects, introduced people to the &lt;a href=&#34;https://civictech.guide&#34;&gt;Civic Tech Field Guide&lt;/a&gt;, and had lots of productive conversations with community members, catching up with current partners and sparking some new collaborations, and of course — swapping swag like stickers, the critical currency of community.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Caroline&lt;/strong&gt;: I had a really wonderful time connecting with folks, especially lots of folks who couldn’t make it to RightsCon. The ability to have longer, more in-depth, and more community focused sessions and conversations over the three days and at the UX Clinic booth was fantastic. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Jamie:&lt;/strong&gt; During the &lt;em&gt;IT Service Providers for Nonprofits &amp;amp; Human Rights Organizations&lt;/em&gt; meetup, we had an unexpected and shared realization that as a group we do not interface with each other as much as we should. There is a huge opportunity for us to share our experiences and refer our clients to each other, so we are best meeting the needs of the nonprofits and human rights organizations we serve. When it comes to human rights, we are not in competition with each other; we operate to serve and support the missions and the ecosystem at-large through technology.&lt;/p&gt;
&lt;h3 id=&#34;what-were-the-topics-on-everyones-mind-what-did-people-want-to-know-about&#34;&gt;What were the topics on everyone’s mind? What did people want to know about?&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Eriol&lt;/strong&gt;: At Feira, many projects approached us as designers with questions about how to improve not only the visual user interface elements of their tools but how to better include broad user types including those that struggle to use tools that are perceived as complex and “too technical”. The privacy and security OSS space gives the impression of over-complicated, very particular set-ups and often prioritizes the complex set-ups for systems and tools when a majority of users, or soon to be users, will likely not describe themselves as such. In addition to these in depth conversations, the designers and user advocates in attendance at Feira spent time speaking with OSS tools and organizations about their design and usability challenges, how to prioritize, how to better understand a problem through user research and how to do that research in a privacy respecting way were some of the key focuses we discussed with people.&lt;/p&gt;
&lt;h3 id=&#34;looking-ahead&#34;&gt;Looking ahead&lt;/h3&gt;
&lt;p&gt;This year has been an amazing opportunity to connect with the community across in-person and remote events. We’re excited to follow up on all of the conversations we had and relationships built at Feira and other events from 2023. As always, if you want to connect about opportunities or collaborations, please reach out!&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;Project Contributors: Jamie Tomasello, Eriol Fox, Matt Stempeck, Caroline Sinders.&lt;/p&gt;
&lt;p&gt;With support from &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Open Technology Fund Secure Usability &amp;amp; Accessibility Lab&lt;/a&gt; and &lt;a href=&#34;https://www.ned.org/&#34;&gt;National Endowment for Democracy&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>From Policy to Pixels:  Strategic UX Design and User Support for GDPR Implementation</title>
      <link>https://superbloom.design/learning/blog/from-policy-to-pixels-strategic-ux-design-and-user-support-for-gdpr-implementation/</link>
      <pubDate>Mon, 20 Nov 2023 00:00:23 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/from-policy-to-pixels-strategic-ux-design-and-user-support-for-gdpr-implementation/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_from_policy_to_pixels_image_1_hu_1aec2e660901b3fe.png&#34; alt=&#34; &#34; width=&#34;740&#34; height=&#34;415&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Introducing our new report “&lt;a href=&#34;https://sprblm.cc/p2p-gdpr-ux&#34;&gt;From Policy to Pixels: Strategic UX Design and User Support for GDPR Implementation&lt;/a&gt;.” Supported by the University of California Berkeley Center for Long-Term Cybersecurity (CLTC), we conducted research to better understand how GDPR policy implementation is situated in current UX practices and how multi-disciplinary product teams reach design decisions.&lt;/p&gt;
&lt;p&gt;We have all seen them: the boxes that pop up when we enter a site, obstructing our view and interrupting our reason for being there in the first place. These boxes are cookie banners, and they exist to inform you of your right to opt-in to data collection (or opt-out, based on the laws where you live). By presenting the user with that choice immediately upon pulling up a website, the user is forced to make a decision to continue their original task. This is a good thing, right? Users should be able to decide whether businesses collect their personal data. However; in practice, it’s not that simple. The design of these banners greatly impact the user’s experience, and their experience impacts their ability to make an informed and active choice.&lt;/p&gt;
&lt;p&gt;Cookie banner design is important, and too often overlooked. We explored this issue and are pleased to present the results in our new report “&lt;a href=&#34;https://sprblm.cc/p2p-gdpr-ux&#34;&gt;From Policy to Pixels: Strategic UX Design and User Support for GDPR Implementation&lt;/a&gt;.” Supported by the Center for Long-Term Cybersecurity (CLTC) at the University of California Berkeley, we conducted qualitative interviews with five designers and front-end developers with experience in creating cookie banners. Our goal was to situate GDPR policy implementation in current UX practices, and understand how multi-disciplinary product teams reach design decisions as a compliance effort. As part of our work, in July 2022, the CLTC invited us to participate in its symposium “Comparing Effects and Responses to GDPR and CCPA/CPRA,” which brought together multi-disciplinary researchers to discuss current and developing data privacy policies. &lt;a href=&#34;https://cltc.berkeley.edu/publication/comparing-effects-of-and-responses-to-the-gdpr-and-ccpa-cpra/&#34;&gt;(Read the symposium summary here!)&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;what-does-design-have-to-do-with-policy&#34;&gt;What does design have to do with policy?&lt;/h4&gt;
&lt;p&gt;GDPR is the EUs General Data Protection Regulation, which among other things requires that businesses give online users a choice regarding data collection. This is why cookie banners are ubiquitous in the EU. However; it’s been well proven that cookie banners do not work, at least not in common design implementations. With data privacy laws being introduced and updated all around the world, there is an urgent opportunity to examine how the user-facing implementation of these policies work and what can be done to improve them. In our study, we found that business discussions about cookie banner implementation promote a focus on compliance legalese rather than interactive, usable visual elements that enable active choice. &lt;/p&gt;
&lt;p&gt;In our paper, we outline these core findings, and propose a preliminary framework of personas (archetypal profiles) for capturing a range of attitudes towards GDPR cookie consent compliance and graphical implementation. Using those personas to evaluate existing tools for cookie management, we identified a gap in the tooling and support ecosystem that can meet the needs of people without large budgets or specialized legal or technical knowledge who are eager to cater a cookie banner experience around meaningful, user-centered consent. Equipping people without specialized domain knowledge or personal passion for privacy to participate in discussion about GDPR cookie consent implementation is essential for shifting the status quo and making informed consent a reality.&lt;/p&gt;
&lt;p&gt;Want to learn more? &lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://sprblm.cc/p2p-gdpr-ux&#34;&gt;Read our full report&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://sprblm.cc/p2p-gdpr-ux&#34;&gt;&lt;/a&gt;And see our &lt;a href=&#34;https://superbloom.design/learning/resources/p2p-zine/&#34;&gt;printable Zine&lt;/a&gt; that introduces our persona framework, outlining divergent approaches to cookie banner implementation.&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Contributors: Ame Elliott, Susan Kennedy, Georgia Bullen.&lt;/p&gt;
&lt;p&gt;*﻿ Susan Kennedy undertook this work with Ame Elliott while she was Program Manager at Superbloom. She is now at Open Technology Fund and may be found on &lt;a href=&#34;https://www.linkedin.com/in/susan-mary-kennedy/&#34;&gt;LinkedIn&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;With support from &lt;a href=&#34;https://cltc.berkeley.edu/&#34;&gt;Center for Long-Term Cybersecurity (CLTC) University of California Berkeley&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Policy to Pixels Zine: Who Implements Cookie Banners?</title>
      <link>https://superbloom.design/learning/resources/p2p-zine/</link>
      <pubDate>Fri, 17 Nov 2023 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/p2p-zine/</guid>
      <description>&lt;p&gt;Zine related to our Policy to Pixels research project covering learnings from people who had to implement GDPR regulation. These zines complement the full report “&lt;a href=&#34;https://sprblm.cc/p2p-gdpr-ux&#34;&gt;From Policy to Pixels: Strategic UX Design and User Support for GDPR Implementation&lt;/a&gt;.” See more in the &lt;a href=&#34;https://superbloom.design/learning/blog/from-policy-to-pixels-strategic-ux-design-and-user-support-for-gdpr-implementation/&#34;&gt;announcement blog&lt;/a&gt; post.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/Superbloom-P2P-PersonasZine-Screen-v3.pdf&#34;&gt;Z﻿ine: Screen Readable&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/Superbloom-P2P-GDPR-UX-Zine-Print-Cut.pdf&#34;&gt;Z﻿ine: Print to Fold&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Usable Security Audit Methodology</title>
      <link>https://superbloom.design/work/projects/usam/</link>
      <pubDate>Sun, 05 Nov 2023 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/work/projects/usam/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Superbloom&#39;s User Experience Toolbox for Risk Mitigation and Accessibility</title>
      <link>https://superbloom.design/learning/blog/superblooms-user-experience-toolbox-for-risk-mitigation-and-accessibility/</link>
      <pubDate>Fri, 03 Nov 2023 21:39:05 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/superblooms-user-experience-toolbox-for-risk-mitigation-and-accessibility/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_user_experience_toolbox_risk-mitigation_accessibility_hu_9b74dfc11ea760ef.png&#34; width=&#34;740&#34; height=&#34;495&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Over the last six months, we’ve been updating our Usable Security Audit Methodology to better reflect our current practices, the advances in our fields of interest, and accessibility as a core principle. Through an inventory of our tools and practices, surveying the field to find similar work we admire, and workshops with close collaborators and community members, we revamped our approach, which we’re now calling our User Experience Toolbox for Risk Mitigation and Accessibility.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;By sharing our auditing approach and inviting collaboration, feedback, and community input, we also aim to provide software teams in the digital rights, human rights, and internet freedom spaces – including researchers, coaches, creators, designers, product managers, and engineers – with a set of resources that can be useful and adaptable to their unique context. &lt;/p&gt;
&lt;h4 id=&#34;evolving-our-approach&#34;&gt;Evolving our approach&lt;/h4&gt;
&lt;p&gt;Beginning in 2014, Superbloom (then Simply Secure) worked with the Open Technology Fund &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Secure Usability and Accessibility (SUA) Lab&lt;/a&gt; to address what we perceived as the shortcomings of so-called “traditional&amp;rsquo;&amp;rsquo; security audits and usability assessments, especially as they relate to open-source software projects. Traditional technical security audits serve a valuable purpose, namely identifying potential vulnerabilities in software code design and implementation. However, these audits do not traditionally focus on the socio-technical aspects of a tool that make systems insecure, e.g. the usability of a tool. We worked to close this gap by &lt;a href=&#34;https://simplysecure.org/resources/techreports/InitialUsableSecurityAuditMethodology.pdf&#34;&gt;creating an audit methodology&lt;/a&gt; that evaluated security and privacy through the lens of user experience and usability. Since its creation, we have used this methodology as a framework for working with tools to improve security through usability and design. &lt;/p&gt;
&lt;p&gt;But, a lot has changed – both for us at Superbloom and within our practitioner ecosystems – since 2014. With support from &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;OTF SUA Lab&lt;/a&gt; and advice from &lt;a href=&#34;https://www.a11ylab.com/?lang=EN&#34;&gt;Accessibility Lab&lt;/a&gt;, we set out to update the framework to better reflect the needs and values of our team and community. &lt;/p&gt;
&lt;h4 id=&#34;putting-trust-first&#34;&gt;Putting trust first &lt;/h4&gt;
&lt;p&gt;In today’s landscape of increasingly riskier digital experiences, successful software development requires more than just functionality and aesthetics. The multifaceted challenges faced by software teams require prioritizing user experiences while carefully addressing potential harms and respecting human rights. We designed this Toolbox to move beyond a set of heuristics that attempt to bridge usability, security, and accessibility towards a more holistic and modular approach to understanding and mitigating risk within human-centered tool design and development.&lt;/p&gt;
&lt;p&gt;Our goal with this Toolbox is to foster trust among all stakeholders involved in the user experience being designed within a given tool or project. By empowering the users of these resources to evaluate the accessibility, risk, and security of the software tools and projects they work on through the lens of user experience and usability, we hope that practitioners learn to better prioritize the needs of the software&amp;rsquo;s intended users while addressing the vulnerabilities associated with its development.&lt;/p&gt;
&lt;h4 id=&#34;accessibility-as-a-core-principle&#34;&gt;Accessibility as a core principle&lt;/h4&gt;
&lt;p&gt;Special thanks to &lt;a href=&#34;https://www.a11ylab.com/?lang=EN&#34;&gt;Accessibility Lab&lt;/a&gt; for advising on and providing resources for this Toolbox!&lt;/p&gt;
&lt;p&gt;Accessibility practices and audits often happen in addition to, not in concert with, usable security reviews, and sometimes they don’t happen at all or are treated as afterthoughts or “nice to haves,” excluding huge swathes of people from their right to digital tools and information, not to mention basic dignity and equity. As UX practitioners, we’ve learned that there is interplay, overlap, and synergistic benefits between each of these aspects, and therefore, we sought to center accessibility as a core principle in this framework:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The security and accessibility of your product are critical aspects of usability: If your software is not accessible, it is not truly usable; if your software is not secure, it is not truly usable; if your software is not usable, it is not truly effective.&lt;/li&gt;
&lt;li&gt;Usability 🤝 Security 🤝 Accessibility: We hope to warn against and work to break down the sometimes false dichotomies that arise when attempting to make software that is usable, secure, and accessible. For example, teams are often warned or worried that accessibility comes at the cost of security or usability. These concepts are mutually beneficial and dependent on one another, and importantly, non-competing.&lt;/li&gt;
&lt;li&gt;The benefits greatly outweigh the perceived and real costs: Making software that is usable, accessible and secure increases users, trust, and the legitimacy of the product. Considering these aspects as early as possible in a development cycle saves teams countless hours of work refactoring when problems arise later. Accessibility compliance can save a company or organization from discriminating against users and potential noncompliance litigation. All of these three aspects are green flags to funders looking to support sustainable software.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;our-toolbox-will-evolve-with-our-community&#34;&gt;Our toolbox will evolve with our community &lt;/h4&gt;
&lt;p&gt;Our approach will shift over time in response to emergent technological considerations and best practices in human-centered design, as well as in response to feedback and contributions from the wider community. We intend for this resource to be updated annually at a minimum, and will continue to add resources via the Superbloom &lt;a href=&#34;https://superbloom.design/learning/&#34;&gt;learning hub&lt;/a&gt; and our &lt;a href=&#34;https://superbloom.design/learning/blog/&#34;&gt;blog&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;We enthusiastically encourage our community to contribute ideas, resources, and feedback to this framework. To do so, you may join us on &lt;a href=&#34;https://superbloom.design/community/join/#online&#34;&gt;Slack&lt;/a&gt;, contribute to the project on &lt;a href=&#34;https://github.com/sprblm&#34;&gt;GitHub&lt;/a&gt;, or send us an email at &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Be sure to check out the full methodology here:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/user-experience-toolbox-for-risk-mitigation-and-accessibility/&#34;&gt;User Experience Toolbox for Risk Mitigation and Accessibility&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/resources/superbloom-accessibility-and-usability-heuristic-review.pdf&#34;&gt;Accessibility and Usability Heuristic Review&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;credits&#34;&gt;Credits&lt;/h4&gt;
&lt;p&gt;Project Contributors: Ngoc Trieu, Philliph Drummond, Veszna Wessenauer, Katie Wilson, Molly Wilson, Nancy Reyes, Saptak Sengupta, Georgia Bullen. &lt;/p&gt;
&lt;p&gt;With support from the Open Technology Fund &lt;strong&gt;&lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Secure Usability and Accessibility Lab&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>User Experience Toolbox for Risk Mitigation and Accessibility</title>
      <link>https://superbloom.design/learning/resources/user-experience-toolbox-for-risk-mitigation-and-accessibility/</link>
      <pubDate>Thu, 02 Nov 2023 12:04:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/user-experience-toolbox-for-risk-mitigation-and-accessibility/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;(Download the PDF version of this resource &lt;a href=&#34;https://superbloom.design/resources/superbloom-accessibility-and-usability-heuristic-review.pdf&#34;&gt;here&lt;/a&gt;&lt;/em&gt;).&lt;/p&gt;
&lt;p&gt;This document represents Superbloom’s approach to scoping risks and improving usability for software projects. It is a collection of tools, resources, practices, and lines of inquiry to help us navigate risks and mitigate potential harms present and emergent in software design and development. By evaluating the accessibility, risk, and security of software tools and projects through the lens of user experience and usability, we aim to help foster a deeper level of trust among all stakeholders involved in the user experience being designed within and around a given tool or project.&lt;/p&gt;
&lt;p&gt;This toolbox is intended to be an adaptable mechanism that encourages research and design activities to prioritize the needs of the software&amp;rsquo;s intended users while addressing the vulnerabilities associated with its development. By sharing our approach and inviting collaboration, feedback, and community input, we also aim to provide software teams in the Digital Rights, Human Rights, and Internet Freedom spaces – including researchers, coaches, creators, designers, product managers, and engineers – with a set of resources that can be useful and adaptable to their unique contexts.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Using this toolbox will help our team members and other software teams to:&lt;/u&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Evaluate the potential risks and harms associated with the use and maintenance of software.&lt;/li&gt;
&lt;li&gt;Work towards a balance between user convenience and robust security without compromising trust or engagement.&lt;/li&gt;
&lt;li&gt;Address accessibility as a core principle in itself, and in identifying and mitigating potential security vulnerabilities to reinforce the software’s reliability and protection of human rights.&lt;/li&gt;
&lt;li&gt;Implement accessibility best practices to create user-friendly experiences for everyone, thus broadening the software’s reach and impact.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;who-we-are&#34;&gt;Who we are&lt;/h2&gt;
&lt;p&gt;Founded in 2014 as Simply Secure, Superbloom leverages design as a transformative practice to shift power in the tech ecosystem. We apply a holistic approach and view design as an intervention opportunity to center people and their needs. Our vision is a world where everyone has the knowledge, network, and digital tools needed to enrich their lives. Together, we&amp;rsquo;re committed to bring about a more just world by exposing the dangers and inequalities of emerging technologies, co-building alternative models, and contributing to the global cultivation of a transformative movement in tech.&lt;/p&gt;
&lt;p&gt;We work to overcome the alarming lack of available resources in the public interest technology space by openly sharing our knowledge and partnering with organizations to identify unmet needs, design for access, and extend the impact of newly built tools and interventions. Changing who technology serves requires challenging not just the technology, but the processes that formed it. Our approach is to intervene in the tech strategy, design and development process across multiple contexts and scales. Our focus has been on bridging areas of expertise – such as usability, accessibility, and security – to develop new methods that shed light on the interplay between people and technology, especially among at-risk populations dealing with threats to their privacy, safety, or security.&lt;/p&gt;
&lt;h2 id=&#34;what-is-this-toolbox&#34;&gt;What is this toolbox?&lt;/h2&gt;
&lt;p&gt;In today’s landscape of increasingly riskier digital experiences, successful software development requires more than just functionality and aesthetics. The multifaceted challenges faced by software teams require prioritizing user experiences while carefully addressing potential harms and respecting human rights.
We designed this document to move beyond a set of heuristics that attempt to bridge usability, security, and accessibility toward a more holistic and modular approach to understanding and mitigating risk within human-centered tool design and development.&lt;/p&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
&lt;p&gt;&lt;strong&gt;While the toolbox provides a holistic, structured approach, it has limitations, requires thoughtful application, and is not a cure-all solution.&lt;/strong&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;p&gt;This framework does not detail a full or typical design-thinking process, &lt;u&gt;nor does it offer a full set of research and design activities that ought to take place throughout a product design and development cycle.&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;The methods detailed here cannot replace &lt;u&gt;a technical security audit, security design review, or an expert accessibility audit.&lt;/u&gt; It cannot eliminate all risks associated with software development. Instead, it provides a set of human-centered tools and strategies that can be used to mitigate these risks to a manageable level. It is up to the software team and the organization to use these tools effectively, and to continually monitor and adjust their approach as needed.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Expert reviews to consider in parallel to the methods listed here:&lt;/u&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Security audit&lt;/strong&gt;: our approach here should not replace a systemic evaluation that happens during a security audit of your software’s code and infrastructure. Our approach does not assess the effectiveness of any security policies or controls, nor does it provide recommendations for improvement on that front. &lt;a href=&#34;https://www.opentech.fund/labs/red-team-lab/&#34;&gt;The Open Tech Fund’s Red Team Lab&lt;/a&gt; offers security audits for Open Source projects.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Security design review&lt;/strong&gt;: our approach here is not a security design review – this approach is not focused on security architecture to harden a tool against technical vulnerabilities and risks in a software stack. Our approach does not emphasize infosec principles like CIA (confidentiality, integrity, availability). Instead, we’ve focused this document on a holistic review of human factors, mitigating biases that emerge in the process, examining security from a user-centered perspective, providing a balanced set of recommendations to enhance the user experience while meeting your software’s security/compliance requirements. The Open Source Security Foundation offers courses and &lt;a href=&#34;https://github.com/ossf/security-reviews&#34;&gt;maintains a repository&lt;/a&gt; of security design reviews of open source software.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Expert accessibility audit&lt;/strong&gt;: While self-audits can help teams get ahead of common accessibility “fails”, expert accessibility audits provide a complete, rigorous breakdown of all WCAG 2.1&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; requirements for your tool, including testing your tools on assistive technology and with disabled users. Expert audits obviously help teams comply with accessibility standards and regulations, but further, they can enhance user engagement and improve SEO. We recommend contacting our friends at &lt;a href=&#34;https://www.a11ylab.com/&#34;&gt;A11y Lab&lt;/a&gt; if you’re looking for an expert accessibility audit.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;heuristics-tools-and-guidelines-can-never-replace-user-input&#34;&gt;Heuristics, tools, and guidelines can never replace user input&lt;/h2&gt;
&lt;p&gt;While we believe that the principles, guidelines, and tools here can help you to design more usable, accessible, and security- and privacy-minded software products and tools, they are not guarantees. A tool or website can be 100% WCAG 2.1 compliant and still have accessibility challenges that went unforeseen. &lt;u&gt;The only way to get ahead of these surprise issues is to test your tools with real and diverse sets of users early and often.&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;Testing with diverse sets of users from multiple perspectives is important to cover the bases of usability, accessibility, and security:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Users representing your different personas will improve usability issues&lt;/li&gt;
&lt;li&gt;Users that employ different assistive technologies will improve accessibility issues&lt;/li&gt;
&lt;li&gt;Users that have a range of threat models will improve security and privacy issues.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;a-living-resource&#34;&gt;A living resource&lt;/h2&gt;
&lt;p&gt;Our approach will shift over time, in response to emergent technological considerations and best practices in human-centered design, amongst other factors. We intend for this resource to be updated annually at the minimum, and will continue to add resources via the Superbloom &lt;a href=&#34;https://superbloom.design/learning/&#34;&gt;learning hub&lt;/a&gt; and our &lt;a href=&#34;https://superbloom.design/learning/blog/&#34;&gt;blog&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We also enthusiastically encourage our community to contribute ideas, resources, and feedback to this framework. To do so, you may join our community on &lt;a href=&#34;https://superbloom.design/community/join/#online&#34;&gt;Slack&lt;/a&gt; or send us an email at &lt;a href=&#34;mailto:hi@superbloom.design&#34;&gt;hi@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;h1 id=&#34;our-responsibilities-as-human-centered-user-experience-practitioners&#34;&gt;Our responsibilities as human-centered User Experience practitioners&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;What is the degree of responsibility for designers/developers to reduce harm in technology and software?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We at Superbloom believe that one of our responsibilities is to acknowledge and mitigate bias in our work, which means acknowledging and mitigating the harm that comes from a variety of &lt;a href=&#34;#types-of-bias&#34;&gt;potential biases&lt;/a&gt;.  Amidst a general lack of and struggle for human rights in software development, the effects of personal bias are often amplified at scale, causing harm and perpetuating the marginalization of at-risk communities. For a further explanation of what bias looks like in this work and for methods and resources to address it, see &lt;a href=&#34;#part-1-knowing-your-users-and-yourself&#34;&gt;Part 1&lt;/a&gt; of this document.&lt;/p&gt;
&lt;p&gt;We also hold ourselves responsible for approaching technology not as a static product, but as a &lt;em&gt;process&lt;/em&gt; that includes, affects, and is affected by many people. This responsibility to us also intersects with and supports the effectiveness of technology: to have a truly effective software product, as well as a responsible one, it must consider and prioritize Accessibility, Usability, &lt;em&gt;and&lt;/em&gt; Security. Failing in any of these aspects will not only significantly impact the software’s overall success and user satisfaction, but can introduce avoidable risk and harm to its users. Importantly, as software itself is an evolving process, so must our attention be towards these three key aspects; one-off audits and reviews will not be sufficient for attending to the ongoing usability, accessibility, and security of a software product.&lt;/p&gt;
&lt;h2 id=&#34;key-definitions&#34;&gt;Key Definitions&lt;/h2&gt;
&lt;p&gt;Working towards rights-respecting software development requires a shared understanding of the key values and ideas we are upholding. Here we define the most central concepts to this framework; for more definitions, please see the &lt;a href=&#34;#glossary&#34;&gt;Glossary&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Accessibility&lt;/u&gt;: The degree to which a product, service, or digital interface can be used effectively and comfortably by everyone, regardless of their abilities or the assistive technologies they use. It ensures that all users can access and interact with the system without discrimination or barriers.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Digital Security&lt;/u&gt;: the practice of protecting digital information from unauthorized access, use, disclosure, disruption, modification, or destruction. We often define security in function of a particular threat model: i.e. “is a program secure against threats A, B, and C?”&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Risk Mitigation&lt;/u&gt;: The process of identifying and reducing potential risks or uncertainties associated with a project or product development. In the context of software development, it involves planning and implementing strategies to avoid or minimize potential negative impacts on the project&amp;rsquo;s success.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Threat Modeling&lt;/u&gt;: A way of thinking about the sorts of protection you want for your data so you can decide which potential threats you are going to take seriously. Coming up with a set of possible threats you plan to protect against is called threat modeling, or risk assessment. While it’s impossible to protect against every kind of trick or adversary, threat modeling enables users to envision possible scenarios on a scale of likely to less likely, and plan accordingly&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Usability&lt;/u&gt;: The measure of how easy and efficient it is for users to achieve their goals when interacting with a product, system, or interface. Usability focuses on aspects such as learnability, efficiency, memorability, errors, and user satisfaction.&lt;/p&gt;
&lt;h2 id=&#34;whats-at-stake&#34;&gt;What’s at stake?&lt;/h2&gt;
&lt;p&gt;While the potential threats, risks, and harms related to a particular software product will depend on its own context, &lt;a href=&#34;https://superbloom.design/learning/resources/user-experience-toolbox-for-risk-mitigation-and-accessibility/#part-1-knowing-your-users-and-yourself&#34; title=&#34;Part 1: Knowing your users and yourself&#34;&gt;users&lt;/a&gt;, and &lt;a href=&#34;#part-2-assessing-risks--threats&#34;&gt;threat model&lt;/a&gt;, we advocate for this general approach to work against the larger scale ways that technology fails to be human- and user-centered. Lacking usable security means that in the worst case scenarios, users find ways around usability barriers, which can increase their risk (e.g. by choosing the wrong settings and sharing data unsafely, or revealing more of their identity than intended due to not being able to safely navigate the options). Accessibility practices and audits often happen in addition to, not in concert with, usable security reviews, and sometimes they don’t happen at all or are treated as afterthoughts or “nice to haves,” excluding huge swaths of people from their right to digital tools and information, not to mention basic dignity and equity.&lt;/p&gt;
&lt;p&gt;As UX practitioners, we’ve learned that there is interplay, overlap, and synergistic benefits between each of these aspects:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;The security and accessibility of your product are critical aspects of usability&lt;/u&gt;: if your software is not accessible, it is not truly usable; if your software is not secure, it is not truly usable; if your software is not usable, it is not truly effective.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Usability 🤝 Security 🤝 Accessibility&lt;/u&gt;: We want to warn against and work to break down the sometimes false dichotomies that arise when attempting to make software that is usable, secure, and accessible. For example, teams are often warned or worried that accessibility comes at the cost of security or usability. These concepts are mutually beneficial, dependent on one another, and importantly, noncompeting.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Benefits greatly outweigh the perceived and real costs&lt;/u&gt;: Making software that is usable, accessible, and secure increases usership, user trust, and legitimacy for your product. Considering these aspects from as early as possible in a development cycle saves teams countless hours of work refactoring when problems arise later. Accessibility compliance can save a company or organization from both discriminating against users and potential noncompliance litigation. All three aspects are green flags to funders looking to support sustainable software.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id=&#34;using-this-toolbox&#34;&gt;Using this toolbox&lt;/h1&gt;
&lt;p&gt;When and how to use the methods and practices outlined in this document will depend on many factors in a given tool team or project. Sometimes Superbloom staff are brought into a project at its inception, and other times we enter years into its existence. For external dev teams and partners, the question often arises: how do I balance the need for timely releases with thorough reviews (of any type)? Instead of prescribing a set of steps or an order of operations, we instead encourage teams and practitioners to consider the following principles when using this set of resources:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Early and meaningful community input&lt;/u&gt;: practicing human-centered work means putting the people using and being affected by your software at the center of your design and development process. Engaging community members not only builds trust, but it can provide invaluable insight for any question you may have.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Open communication&lt;/u&gt;: transparency benefits users and products; making the design process and discussions visible increases trust amongst team members and between teams and their users.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Experimentation&lt;/u&gt;: as mentioned, this framework is not a one-size-fits all prescription of activities. Experiment with what methods and inquiries suit the project at hand.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Openness to pivoting and adjustment&lt;/u&gt;: user-centric work means challenging our own assumptions and beliefs, and taking seriously when those assumptions are proven wrong.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Sensitivity to local contexts&lt;/u&gt;: not all users and users groups operate within the same contexts personally – which &lt;a href=&#34;#part-1-knowing-your-users-and-yourself&#34;&gt;personas, bias mitigation, etc&lt;/a&gt;, can help us think through – but users also reside within and among vastly different geopolitical contexts that affect: 1) their access to information and their susceptibility to censorship and information oppression and 2) their risk tolerance and threat models. Depending on the local context, concepts like security, risk, usability, and accessibility may shift and take on different stakes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Holistic mindset required&lt;/u&gt;: rather than thinking of accessibility, usability, and security attributes separately, they must be considered holistically in order to identify synergies and reconcile conflicts. The optimum balance is not static, and as contexts evolve, designs should be re-evaluated to ensure the right “tradeoffs” are being made. Improving one attribute may inadvertently worsen another. For example, adding more security controls can harm usability. Enhancing accessibility can introduce vulnerabilities if the adjustments aren’t accounted for in the security design. Overlaps, when accounted for together, are typically synergistic – i.e. improving one attribute enhances the others – but the overlap is not symmetrical at all times between any aspect, so remain diligent.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id=&#34;understanding-risks-in-software-development&#34;&gt;Understanding risks in software development&lt;/h1&gt;
&lt;p&gt;We see UX design playing a critical role within risk mitigation. UX methods not only help to clarify, understand, and empathize with the potential pains, challenges, and frustrations in a user’s experience, but can play a key role in anticipating, planning for, and alleviating potential risk.&lt;/p&gt;
&lt;p&gt;We understand risk as a broad concept that encompasses the potential vulnerabilities inherent to a software product’s users and stakeholders, especially those that impact the key aspects of security, accessibility, and usability.&lt;/p&gt;
&lt;p&gt;To capture the breadth of what risk can entail, we also acknowledge and ground this framework in key &lt;u&gt;Contributing Factors&lt;/u&gt;, which all increase risk in a project for several reasons that can be mitigated:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Sensitive User Data&lt;/u&gt;: Handling sensitive user data requires careful design to ensure privacy and security. Typically, the most sensitive user data is called &lt;a href=&#34;#pii&#34;&gt;Personal Identifiable Information (PII)&lt;/a&gt;. Mismanagement and poor security design can lead to data breaches or unintentional user error, which can leave users vulnerable to malicious activity with their PII. This can lead to not only identity theft and financial fraud, but also to significant physiological and emotional distress which erodes users’ trust in a company or a software team, resulting in reputational damage or financial loss.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Security Risks&lt;/u&gt;: Security risks can compromise the integrity of a product and the privacy of its users. UX design can help mitigate these risks by designing for security from the ground up.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Vulnerable Populations&lt;/u&gt;: Products designed without considering the needs of vulnerable populations can lead to exclusion and discrimination. UX design can help ensure inclusivity and accessibility.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Legal Considerations&lt;/u&gt;: Non-compliance with laws and regulations can result in legal penalties. UX design can help ensure compliance by incorporating legal requirements, including accessibility requirements, into the design process.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Potentially Harmful Stimuli&lt;/u&gt;: UX design can help prevent harmful stimuli by considering the potential impact of design decisions on users&amp;rsquo; mental and physical health. &lt;a href=&#34;https://hrcd.pubpub.org/pub/traumaanddesign-082020communitycall/release/1&#34;&gt;Trauma-informed UX design&lt;/a&gt; can help mitigate this kind of harm.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Experimental Interventions&lt;/u&gt;: Experimental interventions can introduce unexpected risks. UX design can help manage these risks by testing interventions in a controlled environment before implementation.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Intrusive Research Methods&lt;/u&gt;: Intrusive research methods can replicate aspects of surveillance capitalism, invade users&amp;rsquo; privacy, and cause harm. UX design can help mitigate this risk by using non-intrusive research methods.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Human Rights Considerations&lt;/u&gt;: Rights-respecting considerations are essential in UX design to avoid harm. Human rights provide specific principles enshrined in international declarations that should frame any design practice. Observing these principles ensures regulatory compliance and prevents alienating users, which can lead to negative repercussions.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Local contexts and the limits of Open Source tooling&lt;/u&gt;: As mentioned above, what is considered high-risk is dependent on local context — geopolitical, cultural, linguistic, infrastructural, etc differences affect what high risk means for different users around the world. Predominant Open Source tools and security infrastructure are often premised on the local contexts that those teams know well, meaning they are biased toward more Western and/or better understood risk contexts, and thus can be inadequate for high-risk scenarios in other global contexts that are less well understood (particularly those that are highly censored and thus harder to get visibility into).&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href=&#34;#part-2-assessing-risks--threats&#34;&gt;Part 2&lt;/a&gt; goes into the practices and methods you can employ when scoping threats.&lt;/p&gt;
&lt;h1 id=&#34;foregrounding-accessibility&#34;&gt;Foregrounding accessibility&lt;/h1&gt;
&lt;!-- borderedbox --&gt;
&lt;div id=&#34;bordered-box&#34;&gt;
&lt;p&gt;&lt;strong&gt;Special thanks to &lt;a href=&#34;https://www.a11ylab.com/?lang=EN&#34;&gt;Accessibility Lab&lt;/a&gt; for advising on and providing resources for this document.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;A11y Lab is a company that seeks to ensure the inclusion of people with disabilities through accessibility in the digital world. They work with public, private, and civil society organizations to promote and defend digital rights.&lt;/p&gt;
&lt;p&gt;A11y Lab provides many indispensable services to teams, companies, and organizations looking to take accessibility seriously. See their offerings &lt;a href=&#34;https://www.a11ylab.com/services&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;!-- /borderedbox --&gt;
&lt;p&gt;&lt;em&gt;This section acts as a quick primer on accessibility in software design. We go more into detail about accessibility audits in &lt;a href=&#34;#part-3-usability--accessibility-audit&#34;&gt;Part 3&lt;/a&gt; of this document and the accompanying &lt;a href=&#34;https://superbloom.design/resources/superbloom-accessibility-and-usability-heuristic-review.pdf&#34;&gt;heuristic review&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;While it’s easy to understand why creating accessible software is important from an equity perspective, the most common factor limiting the accessibility of software is its treatment as an afterthought. The benefits of creating accessible user experiences are far reaching:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;u&gt;Social responsibility&lt;/u&gt;: we are responsible as creators of tools and products not to discriminate against potential users due to their physical or mental abilities.&lt;/li&gt;
&lt;li&gt;&lt;u&gt;Competitive advantage&lt;/u&gt;: the more people who can use your software, the more users you can have, and the more likely people are to choose your software over a competitor with fewer accessibility features.&lt;/li&gt;
&lt;li&gt;&lt;u&gt;Improves SEO positioning and compatibility&lt;/u&gt;: the way that accessibility requirements are often coded into software inadvertently (but helpfully) improves the discoverability of your software on search engines.&lt;/li&gt;
&lt;li&gt;&lt;u&gt;Complies with legislation&lt;/u&gt;: most countries in which we work have legislation requiring compliance with accessibility standards.&lt;/li&gt;
&lt;li&gt;&lt;u&gt;Security&lt;/u&gt;: accessible online services offer efficient and secure options for everyday tasks.&lt;/li&gt;
&lt;li&gt;&lt;u&gt;Autonomy&lt;/u&gt;: web accessibility improves everyone&amp;rsquo;s quality of life.&lt;/li&gt;
&lt;li&gt;&lt;u&gt;Efficiency&lt;/u&gt;: good, accessible design factored into a development process early saves developers time and businesses money.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Contrary to some belief, accessibility does not negatively affect design or security. Most requirements are not displayed to users who are not utilizing assistive technology, i.e. alternative text, tags on data entries, header tags, or language options.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.w3.org/TR/WCAG21/#abstract&#34;&gt;The Web Content Accessibility Guidelines (WCAG 2.1)&lt;/a&gt; are the standard of compliance for accessibility online. They cover a wide range of recommendations for making Web content more accessible, and when implemented to their full extent, software creators can benefit from having the following acknowledgments:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;u&gt;&lt;a href=&#34;https://www.w3.org/WAI/planning/statements/&#34;&gt;Accessibility Statement&lt;/a&gt;&lt;/u&gt;: A powerful declaration of commitment which is normally available in the footer via a link and includes information about the platform’s accessibility.&lt;/li&gt;
&lt;li&gt;&lt;u&gt;The W3C Conformance logo&lt;/u&gt;: The platform indicates a claim of conformance to a specified conformance level of the Web Content Accessibility Guidelines 2.1 W3C, could be level A, AA or AAA.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;consciousness-raising&#34;&gt;Consciousness raising&lt;/h2&gt;
&lt;p&gt;Foregrounding accessibility in software practices may necessitate some consciousness raising amongst teams, which can help people to empathize with and understand better the severity of need for accessibility practice. &lt;u&gt;Understanding accessibility is often understanding new user personas.&lt;/u&gt; Of course, collaborating and testing with users with disabilities is the most ideal way to work on the accessibility of your project.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Key concepts and tools:&lt;/u&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;u&gt;Learn from leaders in the field:&lt;/u&gt; Some large and popular companies are great examples of foregrounding accessibility (i.e. Apple). Learn from their approach.&lt;/li&gt;
&lt;li&gt;&lt;u&gt;Use disability simulators, to help understand and empathize with different users’ needs.&lt;/u&gt; Some useful tools include:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.whocanuse.com/&#34;&gt;Whocanuse.com&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;u&gt;Learning and using person-first language:&lt;/u&gt; i.e. “person with disabilities” rather than “disabled person.”&lt;/li&gt;
&lt;li&gt;&lt;u&gt;Practice using digital tools that simulate accessibility needs:&lt;/u&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://accessibility.digital.gov/front-end/screen-reader/&#34;&gt;Learn how to navigate a webpage using only your keyboard&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Learn how to use a screen reader, such as &lt;a href=&#34;https://www.youtube.com/watch?v=5R-6WvAihms&#34;&gt;VoiceOver on a Mac&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Try using a tool you’ve worked on while closing your eyes or covering the keyboard to test usability. You can use resources like &lt;a href=&#34;https://universaldesignguide.com/ability-prompt-cards/&#34;&gt;Ability Prompt Cards&lt;/a&gt; to help structure the activity.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Another way to raise your literacy around accessibility and disability justice is to familiarize yourself with the various &lt;a href=&#34;https://mn.gov/admin/at/getting-started/understanding-at/types/&#34;&gt;types of Assistive Technology&lt;/a&gt; in use by millions of people around the world. Some common examples include:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.inclusive.com/uk/hardware/alternative-keyboards/high-visibility-keyboards.html&#34;&gt;High contrast keyboards&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.perkins.org/resource/introduction-7-common-adaptive-switches/&#34;&gt;Adaptive switches&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://abilitynet.org.uk/factsheets/keyboard-and-mouse-alternatives-and-adaptations&#34;&gt;Adaptations to mouse track pads&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.boia.org/blog/how-braille-displays-help-users-with-visual-impairments-access-the-web&#34;&gt;Braille displays&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.w3schools.com/accessibility/accessibility_screen_readers.php&#34;&gt;Screen readers&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.accessibility.com/blog/a-guide-to-motion-and-eye-tracking-technology&#34;&gt;Eye trackers&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Zoom options&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://accessibleweb.com/assistive-technologies/assistive-technology-focus-sip-and-puff-devices/&#34;&gt;Sip and puff&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.cnet.com/tech/computing/apple-voice-control-adds-voice-accessibility-to-iphones-apple-computers-ios-macos/&#34;&gt;Voice control&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;And more!&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id=&#34;part-1-knowing-your-users-and-yourself&#34;&gt;Part 1: Knowing your users and yourself&lt;/h1&gt;
&lt;h2 id=&#34;positionality-bias-and-cultural-context&#34;&gt;Positionality, bias, and cultural context&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Driving question: “How can we proactively identify our own biases and gaps in understanding stemming from team culture and positionality?”&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We acknowledge that our team and other teams employing the concepts in this framework may need additional support to highlight their gaps stemming from their own cultural viewpoint. Understanding that viewpoint means practicing self-awareness and reflecting on and understanding one’s own positionality related to the contexts, tools, and topics involved in the software at hand, and to the user groups it represents. Taking a meaningful step towards interrogating our own positionality, potential biases, and potential gaps helps to prevent harms that may arise from ignorance and/or unconscious discrimination.&lt;/p&gt;
&lt;p&gt;Below are some concrete exercises to start identifying bias and articulating positionality. These are focused on the questions “who am I?” and “who are we?” and how those answers reflect or don’t reflect the communities and users we’re intending to serve. Once articulated, how can we open ourselves to the perspectives and people we may be missing?&lt;/p&gt;
&lt;p&gt;It’s important to note that bias itself isn’t the enemy. We will never be free from bias. But, we believe the purpose of identifying bias is to move towards underlying “design justice [that] seeks more than ‘freedom from bias.’” Because bias leads to real-world harm, interrupting bias helps us to “unpack the ways that intersecting forms of oppression, including patriarchy, white supremacy, ableism, and capitalism, are constantly hard-coded into designed objects, platforms, and systems&lt;sup id=&#34;fnref:3&#34;&gt;&lt;a href=&#34;#fn:3&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;3&lt;/a&gt;&lt;/sup&gt;.&amp;quot;&lt;/p&gt;
&lt;p&gt;Once identified, one way to navigate identified gaps within ourselves is through cultural brokers. Cultural brokers can provide insider perspectives to enhance cultural relevance and prevent ethical pitfalls. Their mediation and interpretation is invaluable for creating an user experience that is responsible, inclusive, and respectful of the user&amp;rsquo;s rights and dignity. They can also help to employ a design process that seeks to care for a software team themselves. So, as this framework notes risk factors and mitigations associated in the use of a particular method, it identifies how a cultural broker might intervene/aid in a particular mitigation.&lt;/p&gt;
&lt;h3 id=&#34;resources&#34;&gt;Resources:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/resources/superbloom-positionality-worksheet.pdf&#34;&gt;Positionality worksheet&lt;/a&gt;: This worksheet helps to explain what positionality is, why it’s important for participatory research and design projects, and how it informs potential bias. It guides the reader to write their own positionality statement.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://medium.com/@ProjectInkblot/how-to-begin-designing-for-diversity-41b6f9a7f8e4&#34;&gt;How to begin designing for diversity&lt;/a&gt;: A guide from Jahan + Boyuan of Project Inkblot with helpful resources for positionality and diversity in design ideation.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://sdfsguide.medium.com/using-assumption-dumps-to-explore-design-diversity-564315dbc73e&#34;&gt;Assumption Dump&lt;/a&gt;: As a team, an assumption dump can help surface biases that may be unspoken within yourself or your project peers.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://universaldesignguide.com/ability-prompt-cards/&#34;&gt;Ability Prompt Cards&lt;/a&gt;: These can be used for more than just accessibility awareness, but also to understand where our assumptions and ideas may be leaving people behind.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/resources/superbloom-cultural-brokering-guidelines.pdf&#34;&gt;Guidelines for Being a Cultural Broker&lt;/a&gt;: Cultural brokering is the act of bridging, linking, or mediating between groups or persons of different cultural backgrounds for the purpose of reducing conflict or producing change. This document outlines Superbloom’s approach to the practice.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://freedomhouse.org/report/freedom-net&#34;&gt;Freedom of the Net reports by Freedom House&lt;/a&gt;: Freedom of the Net reports are annual assessments of internet freedom around the world. They examine the state of digital rights, censorship, surveillance, and restrictions on online activities. These reports provide insights into the extent to which governments and other entities are limiting internet access and expression in various countries.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://www.giswatch.org/&#34;&gt;Global Information Society Watch (GISWatch)&lt;/a&gt;: it is a collaborative platform that provides critical analysis and monitoring of information and communication technologies (ICTs) and their impact on society. It focuses on issues related to internet governance, digital rights, and access to information, offering insights and reports from various contributors around the world. GISWatch aims to foster an inclusive, equitable, and open global information society by addressing key challenges in the digital age.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://www.accessnow.org/keepiton/&#34;&gt;#KeepItOn reports by Access Now&lt;/a&gt;: these reports are about documenting and raising awareness of internet shutdowns and disruptions around the world. These reports provide information on the extent and impact of government-imposed internet restrictions, with a focus on human rights violations, censorship, and the suppression of free expression.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;identifying-and-familiarizing-yourself-with-users&#34;&gt;Identifying and familiarizing yourself with users&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Driving question: How can we rigorously understand the perspective of all potential segments of our users, not just the “intended” users?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;It is essential that software and evaluation teams develop a clear picture of who the target users are for the tool. Otherwise, there’s no standpoint from which to evaluate risk. Users include both those the team would like to encourage to use their tool, but also users who are likely to use the tool (or who are currently using it), even if they are outside of the group that the team would like to focus on.&lt;/p&gt;
&lt;p&gt;While the desired user population should be the highest priority in evaluating usability, entirely ignoring probable or actual user populations will result in frustration for the development team when they receive a high volume of complaints from this “extra” population. Ignoring likely but unexpected users of tools with a security or privacy focus can also cause these users to be endangered when the threats they face are not the threats the tool protects against, if the tool does not help them understand this.&lt;/p&gt;
&lt;h3 id=&#34;resources-to-identify-users&#34;&gt;Resources to identify users&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Persona exercises&lt;/u&gt; enable tool teams to think through their potential user groups and create sample identities (called a “persona”) that can stand-in for the needs of larger groups of users. Some useful templates include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.servicedesigntoolkit.org/downloads.html&#34;&gt;Service Design Toolkit Templates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://okthanks.com/persona-builder&#34;&gt;Ok Thanks Persona Builder&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/resources/persona-template-tech.pdf&#34;&gt;Superbloom Persona Template&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/resources/ecosystem-mapping-exercise.pdf&#34;&gt;Ecosystem or stakeholder map&lt;/a&gt;: helps you to understand the broader context within which your tool is being created, which includes users but also other stakeholders and people/ecosystems affected by your work.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Engaging with community boards and channels:&lt;/u&gt; Users tend to congregate online, especially when they face usability challenges (Twitter, StackOverflow, Reddit, Slack and Discord groups, etc can all be places where users communicate). Open Source projects often have the great advantage of engaged contributors and users who congregate on Github and other OSS channels. Use these channels to your advantage by treating them as ad-hoc user research repositories and direct lines of communication to user groups.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Simulation Exercises:&lt;/u&gt; In the absence of direct access to users&amp;rsquo; lives, simulation exercises can offer insight into the realities of certain situations that we play out in theory in our minds. Physically playing out a scenario helps us understand users in relation to time, space and environment.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;u&gt;Shadowing, Touchstone tours:&lt;/u&gt; If a user invites you into their experiences and environment you can shadow their behavior or take the opportunity to take a touch stone tour - where you ask the users to talk and walk you through their interactions with both software tools and their lived environment.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id=&#34;part-2-assessing-risks--threats&#34;&gt;Part 2: Assessing risks &amp;amp; threats&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;Driving question: What vulnerabilities are there that may increase risks for either users or stakeholders?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Once grounded in our own and our users’ perspectives and positionality, we can take our comprehension of risks and threats conceptually and move toward assessment and action. This section focuses on lines of inquiry and resources for doing threat modeling and risk assessment in projects and with project teams.&lt;/p&gt;
&lt;h3 id=&#34;resources-to-utilize-in-this-phase-include&#34;&gt;Resources to utilize in this phase include:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/resources/superbloom-user-journey-mapping-template.pdf&#34;&gt;User Journey mapping&lt;/a&gt;: A structured activity for charting users’ possible journeys to and through a tool, as a way to identify potential pain points and vulnerabilities.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://tarotcardsoftech.artefactgroup.com/&#34;&gt;Tarot Cards of Tech&lt;/a&gt;: A set of provocations to help think through different scenarios and your tool’s effect on society and users.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/designunderpressure/#resources&#34;&gt;Design Under Pressure&lt;/a&gt;: a practical resource to help you and your team proactively create products and services that hold up under stress cases.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/resources/superbloom-threat-modeling-template.pdf&#34;&gt;Threat modeling&lt;/a&gt;: a &lt;a href=&#34;https://cheatsheetseries.owasp.org/cheatsheets/Threat_Modeling_Cheat_Sheet.html&#34;&gt;structured approach&lt;/a&gt; of identifying and prioritizing potential threats to a system, and determining the value that potential mitigations would have in reducing or neutralizing those threats.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/persona-non-grata/&#34;&gt;Personas non grata&lt;/a&gt;: ten people you probably don&amp;rsquo;t want in your product or service, but who are likely to find their way in anyway. A way to plan for potential malicious actors.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/resources/anxiety-games-template.pdf&#34;&gt;Anxiety games&lt;/a&gt;: a workshop created by Andrew Lovett-Barron for playing out different threat scenarios to help build resilience and proactive risk mitigation into your tool.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://andrewlb.com/writing/2021-05-16-covid-anxiety/&#34;&gt;Blog post&lt;/a&gt; about the method.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://arcticwolf.com/resources/glossary/red-team-blue-team/#:~:text=Blue%20Team%20Exercise%3F-,A%20red%20team%20vs.,variety%20of%20pre%2Ddetermined%20scenarios.&#34;&gt;Red Team, Blue Team&lt;/a&gt;: exercise that helps scope security vulnerabilities and possible actions and interventions to prevent them.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Document reviews: can help teams know if their licenses, contracts, agreements, policies, and procedures are compliant, effective, and up-to-date.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Once again, what we offer here is not a comprehensive introduction to security, privacy, and data handling best practices that ought to be in use in software projects. As a jumping off point, digital security training guidelines about day to day digital hygiene can be applied to developing and designing software. We like the guides from &lt;a href=&#34;https://freedom.press/training/&#34;&gt;Freedom of the Press Foundation&lt;/a&gt; and the &lt;a href=&#34;https://ssd.eff.org/&#34;&gt;Electronic Frontier Foundation&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Use the table below to walk through possible lines of inquiry and methods that may be useful to your exploration in this phase.&lt;/u&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;/p&gt;
&lt;!-- Table: Assessing Risks and Threats --&gt;
&lt;table class=&#34;customTable&#34;&gt;
  &lt;thead&gt;
      &lt;tr&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;Assessing Risks and Threats&lt;/th&gt;
      &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;strong&gt;Context&lt;/strong&gt;: Your team is cautious. Your team needs to identify risks and vulnerabilities. You want to prevent harm to users and stakeholders early in development when mitigations are cheaper and easier to implement.&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;&lt;strong&gt;Driving question&lt;/strong&gt;: What vulnerabilities are there that may increase risks for either users or stakeholders?&lt;/td&gt;
      &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;
&lt;table class=&#34;toolbox-bottom-table&#34;&gt;
  &lt;thead&gt;
      &lt;tr&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;Lines of inquiry&lt;/th&gt;
          &lt;th style=&#34;text-align: left&#34;&gt;Methods&lt;/th&gt;
      &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;What motivated attackers or abuses should we plan for? Where are we vulnerable? What assets do we need to protect?&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Threat modeling&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;What potential risks or threats could impact the target user? Where are we most susceptible to ethical pitfalls or unintended societal consequences?&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Anxiety games&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;What risks could lead to failure down the line? How might our solution be misused?&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Threat modeling, anxiety games, Design Under Pressure&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;What are the key touchpoints and interactions that users have with the product? How can we visualize and analyze moments to intervene with mitigations in the user&amp;rsquo;s overall experience?&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Journey mapping&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;How does data move through the software itself? Where might user data be exposed or vulnerable to malicious actors? How can we use mitigations to better enable data and enhance our users&amp;rsquo; goals?&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Data flow mapping&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;How can we create realistic representations that represent different potential threat actors or adversaries to understand their motivations, capabilities, and potential actions?&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Persona non-grata&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;What are the needs, concerns, interests and expectations of stakeholders related to the software&amp;rsquo;s development? How do stakeholders want to be involved in the software&amp;rsquo;s development?&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Stakeholder interviews&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Are all of our licenses, contracts, agreements, policies, and procedures compliant? How effective are our internal controls?&lt;/td&gt;
          &lt;td style=&#34;text-align: left&#34;&gt;Document review&lt;/td&gt;
      &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;
&lt;!-- Table: Assessing Risks and Threats --&gt;
&lt;h1 id=&#34;part-3-usability--accessibility-audit&#34;&gt;Part 3: Usability &amp;amp; accessibility audit&lt;/h1&gt;
&lt;p&gt;An accessibility audit on its own is beneficial because it can help organizations comply with accessibility standards and regulations, enhance user engagement, and improve SEO. We’ve found that an accessibility audit is a complementary process to an UX audit; they share a goal to improve user experience and each focuses on overlapping aspects of the software.&lt;/p&gt;
&lt;p&gt;Here we have combined the best practices of a usability heuristic evaluation with an accessibility self-audit, while keeping privacy and security top-of-mind.  We believe that using this method, software teams can develop complementary findings, identifying a wider range of issues and opportunities for improvement which can help ensure their product or service is both usable and accessible to a broader range of users.&lt;/p&gt;
&lt;p&gt;Please see this document: &lt;a href=&#34;https://superbloom.design/resources/superbloom-accessibility-and-usability-heuristic-review.pdf&#34;&gt;Accessibility and Usability Heuristic Review&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;outputs&#34;&gt;Outputs&lt;/h2&gt;
&lt;p&gt;The output of a heuristic evaluation is a list of pain points. Each pain point should include information on the relative priority of the problem (e.g., “must fix before launch”, “fix soon”, “fix someday”), details on why it is painful (“users will expect X and be frustrated when they get Y”), and suggestions for improvement. In some cases it will not be possible for evaluators to directly suggest solutions, in which case they should aim to characterize what an improvement would look like (e.g., “this dialogue box should help the user understand A in addition to B”).&lt;/p&gt;
&lt;h1 id=&#34;glossary&#34;&gt;Glossary&lt;/h1&gt;
&lt;p&gt;&lt;u&gt;Accessibility&lt;/u&gt;: The degree to which a product, service, or digital interface can be used effectively and comfortably by everyone, regardless of their abilities or the assistive technologies used. It ensures that all users can access and interact with the system without discrimination or barriers.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Digital Security&lt;/u&gt;: the practice of protecting digital information from unauthorized access, use, disclosure, disruption, modification, or destruction. We often define security in function of a particular threat model: i.e. “is a program secure against threats A, B, and C?”&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Human Rights Centered Design&lt;/u&gt;: insists on the same sovereignty and protection for the user of a product. In essence, this means respecting a user’s privacy and data, thinking about the digital rights of people across the world (instead of just in our own backyards), and designing for all&lt;sup id=&#34;fnref:4&#34;&gt;&lt;a href=&#34;#fn:4&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;4&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
&lt;p&gt;&lt;u id=pii&gt;Personal Identifiable Information (PII)&lt;/u&gt;: any data that could potentially identify a specific individual, either directly or indirectly. Examples include legal name, address, phone number, credit card and bank account numbers, passport and driver’s license numbers, social security numbers, etc.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Risk Mitigation&lt;/u&gt;: The process of identifying and reducing potential risks or uncertainties associated with a project or product development. In the context of software development, it involves planning and implementing strategies to avoid or minimize potential negative impacts on the project&amp;rsquo;s success.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Threat Modeling&lt;/u&gt;: A way of thinking about the sorts of protection you want for your data so you can decide which potential threats you are going to take seriously. Coming up with a set of possible threats you plan to protect against is called threat modeling, or assessing your risks. While it’s impossible to protect against every kind of trick or adversary, threat modeling enables users to envision possible scenarios on a scale of likely to less likely, and plan accordingly&lt;sup id=&#34;fnref:5&#34;&gt;&lt;a href=&#34;#fn:5&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;5&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Trauma&lt;/u&gt;: A complex, disruptive, and painful phenomena that people experience individually and collectively from abuse, deprivation, neglect, violence, or other violation of their basic needs and human rights.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Trigger experience&lt;/u&gt;: Not all people who experience trauma experience triggers. It results in greatly reduced capacity for the duration of the person’s response. This experience is frequently, but not always, terrifying for the person involved. It can be extremely difficult for people around the person who is triggered, too.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Triggered/trigger response&lt;/u&gt;: A person’s extreme, involuntary, rapid, physiological and mental response to an experience that the amygdala, or ‘reptilian’ part of their brain, has associated with an earlier trauma. Being triggered renders important parts of a person’s physiological and mental capacity temporarily non-functional.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Usability&lt;/u&gt;: The measure of how easy and efficient it is for users to achieve their goals when interacting with a product, system, or interface. Usability focuses on aspects such as learnability, efficiency, memorability, errors, and user satisfaction.&lt;/p&gt;
&lt;h2 id=&#34;types-of-bias&#34;&gt;Types of Bias&lt;sup id=&#34;fnref:6&#34;&gt;&lt;a href=&#34;#fn:6&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;6&lt;/a&gt;&lt;/sup&gt;&lt;/h2&gt;
&lt;p&gt;&lt;u&gt;Confirmation Bias&lt;/u&gt;: The tendency to favor information that confirms one&amp;rsquo;s preexisting beliefs or hypotheses while ignoring or downplaying contradictory evidence. It can lead to skewed research results and erroneous conclusions.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Cultural Bias&lt;/u&gt;: The tendency to interpret information and experiences based on one&amp;rsquo;s own cultural background, leading to potential misinterpretations or misunderstandings when designing products for users from different cultural backgrounds.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Negativity Bias&lt;/u&gt;: The psychological tendency for people to pay more attention to and be influenced by negative information or experiences than positive ones. In UX research, this bias can impact how users perceive and evaluate a product.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Observational Bias&lt;/u&gt;: A bias that occurs when a researcher&amp;rsquo;s preconceived notions or expectations influence their observations and interpretations during a study. It can unintentionally affect the objectivity and validity of the research findings.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Recency Bias&lt;/u&gt;: The cognitive bias that gives more weight to recent events or experiences when making decisions or judgments, often overshadowing older or more distant information. In UX research, it can affect how users recall and evaluate their experiences with a product.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Segmentation Bias&lt;/u&gt;: A bias that arises when researchers make generalizations about a diverse group of users based on the behaviors or preferences of a specific subgroup within that larger group.&lt;/p&gt;
&lt;br /&gt;
&lt;h1 id=&#34;appendix-a---how-to-prioritize-expert-audit-outputs&#34;&gt;Appendix A - How to Prioritize Expert Audit Outputs&lt;/h1&gt;
&lt;h2 id=&#34;upon-receiving-the-report&#34;&gt;Upon receiving the report&lt;/h2&gt;
&lt;p&gt;Review the audit report then try to identify the specific accessibility violations that need to be addressed.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Prioritize the violations based on their severity and impact on users. For example, violations that affect the most critical functions of the product or service should be addressed first.&lt;/li&gt;
&lt;li&gt;For each violation, create or edit the user story that describes the problem and its impact on users.
&lt;ol&gt;
&lt;li&gt;Identify or create a (proto)persona to be the subject of the user story&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&#34;implementation-of-solutions&#34;&gt;Implementation of solutions&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Work with the development team to ensure that the design solutions are implemented and tested to ensure they meet accessibility standards.
&lt;ol&gt;
&lt;li&gt;Develop design solutions that address the violations and improve the accessibility of the product or service. This may involve working with developers to implement changes to the user interface, such as adding alt text to images or providing alternative text for non-text content.&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&#34;testing-of-solutions&#34;&gt;Testing of solutions&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Conduct user testing with people with disabilities to ensure that the design solutions are effective and meet their needs&lt;/li&gt;
&lt;li&gt;Continuously monitor and evaluate the accessibility of the product or service and make adjustments as needed.&lt;/li&gt;
&lt;/ol&gt;
&lt;br /&gt;
&lt;hr&gt;
&lt;h1 id=&#34;footnotes&#34;&gt;Footnotes&lt;/h1&gt;
&lt;div class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;
&lt;hr&gt;
&lt;ol&gt;
&lt;li id=&#34;fn:1&#34;&gt;
&lt;p&gt;&lt;a href=&#34;https://www.w3.org/TR/WCAG21/#abstract&#34;&gt;The Web Content Accessibility Guidelines (WCAG 2.1)&lt;/a&gt; are the standard of compliance for accessibility online. They cover a wide range of recommendations for making Web content more accessible. For more information about incorporating accessibility standards, see &lt;a href=&#34;https://www.w3.org/TR/WCAG21/#abstract&#34;&gt;here&lt;/a&gt;.&amp;#160;&lt;a href=&#34;#fnref:1&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id=&#34;fn:2&#34;&gt;
&lt;p&gt;Adapted from EFF definition of &lt;a href=&#34;https://ssd.eff.org/glossary/threat-model&#34;&gt;threat model&lt;/a&gt;.&amp;#160;&lt;a href=&#34;#fnref:2&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id=&#34;fn:3&#34;&gt;
&lt;p&gt;&lt;a href=&#34;https://designjustice.mitpress.mit.edu/pub/3h2zq86d/release/1?from=40310&amp;amp;to=40670&#34;&gt;https://designjustice.mitpress.mit.edu/pub/3h2zq86d/release/1?from=40310&amp;amp;to=40670&lt;/a&gt;&amp;#160;&lt;a href=&#34;#fnref:3&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id=&#34;fn:4&#34;&gt;
&lt;p&gt;Definition from &lt;a href=&#34;https://www.humanrightscentered.design/glossary&#34;&gt;https://www.humanrightscentered.design/glossary&lt;/a&gt;&amp;#160;&lt;a href=&#34;#fnref:4&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id=&#34;fn:5&#34;&gt;
&lt;p&gt;Adapted from EFF: &lt;a href=&#34;https://ssd.eff.org/glossary/threat-model&#34;&gt;https://ssd.eff.org/glossary/threat-model&lt;/a&gt;.&amp;#160;&lt;a href=&#34;#fnref:5&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id=&#34;fn:6&#34;&gt;
&lt;p&gt;For more on cognitive bias in design, we recommend David Dylan Thomas’s &lt;a href=&#34;https://abookapart.com/products/design-for-cognitive-bias&#34;&gt;Design for Cognitive Bias&lt;/a&gt;.&amp;#160;&lt;a href=&#34;#fnref:6&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>Open Design Workshop at COSCUP 2023: Understanding Internet Shutdowns and How Design Can Improve Tools</title>
      <link>https://superbloom.design/learning/blog/open-design-workshop-at-coscup-2023-understanding-internet-shutdowns-and-how-design-can-improve-tools/</link>
      <pubDate>Fri, 27 Oct 2023 00:00:59 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/open-design-workshop-at-coscup-2023-understanding-internet-shutdowns-and-how-design-can-improve-tools/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_understanding_internet_shutdowns_image_9_hu_7f0350912817f28.png&#34; alt=&#34;A photo of &amp;ldquo;The Design We Open&amp;rdquo; workshop in Taiwan at COSCUP 2023. There are 20 plus people gathered around a table with laptops, sticky notes and writing on the tables from the workshop. Everyone is looking towards the camera and some people are smiling.&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;p&gt;At COSCUP 2023, we held a workshop &lt;a href=&#34;https://coscup.org/2023/en/session/FYPKL9&#34;&gt;&amp;ldquo;The Design We Open - Network Disruption Hackathon&amp;rdquo;&lt;/a&gt; (The Design We Open Workshop - 網路中斷黑客松), a workshop focused on how we, as designers and configurers of technology for human rights needs can better understand Taiwanese citizens&amp;rsquo; understanding and experiences of internet shutdowns, and what is important in a partial or full internet shutdown.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;All of the openly available resources created at our workshop in Miro (an online white-board tool) are &lt;a href=&#34;https://miro.com/app/board/uXjVM3Baplg=/?share_link_id=900816932790&#34;&gt;available to view&lt;/a&gt;; a backup version was downloaded in September 2023. You can explore the &lt;a href=&#34;https://hackmd.io/5W_UE4J3Q_O7IRNx9xfPEQ&#34;&gt;HackMD notes from the workshop&lt;/a&gt; and read the details of the session on the &lt;a href=&#34;https://coscup.org/2023/en/session/FYPKL9&#34;&gt;2023 COSCUP schedule&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;planning-and-preparing-a-oss-and-design-workshop-for-internet-shutdowns&#34;&gt;Planning and preparing a OSS and design workshop for internet shutdowns&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;http://coscup.org/&#34;&gt;COSCUP&lt;/a&gt; is a large, international, open source conference that has been running for as long as, or almost as long as &lt;a href=&#34;https://fosdem.org/&#34;&gt;FOSDEM&lt;/a&gt;. It predominantly serves and is rooted in the Taiwanese and broader east Asian open source community.&lt;/p&gt;
&lt;p&gt;This year Superbloom put forward a proposal that combines design, OSS and human rights in a workshop at COSCUP which was hosted at the &lt;a href=&#34;https://www.ntust.edu.tw/&#34;&gt;National Taiwan University of Science and Technology (NTUST) in Taipei&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The COSCUP event is divided into a number of different areas or tracks, run by a community that chooses different track focuses. We hosted our workshop in the Open Design track and it was the second year an Open Design track was held at COSCUP. &lt;/p&gt;
&lt;p&gt;We called the workshop &lt;a href=&#34;https://coscup.org/2023/en/session/FYPKL9&#34;&gt;&amp;ldquo;The Design We Open - Network Disruption Hackathon&amp;rdquo;&lt;/a&gt; (The Design We Open Workshop - 網路中斷黑客松). Our workshop focused on how we, as designers and configurers of technology for human rights needs can better understand Taiwanese citizens&amp;rsquo; understanding and experiences of internet shutdowns, and what is important in a partial or full internet shutdown. The extended aim of the workshop was to bring together designers, OSS contributors, human rights advocates and concerned citizens to explore and communicate the opportunities and innovations that could be built to support continued, uncensored access to the open internet.&lt;/p&gt;
&lt;p&gt;At Superbloom, we know that internet shutdowns have been increasing around the world, affecting more and more people. Building on our &lt;a href=&#34;https://superbloom.design/learning/blog/learnings-from-the-otf-shutdowns-getdown-gathering-2022/&#34;&gt;takeaways from a convening on internet shutdowns in 2022&lt;/a&gt; we have been exploring ways to better understand the global impact of internet shutdowns, how they affect people, and the open source tools that people and human rights activists need to access in order to develop resilience around and combat in response to a shutdown. For the COSCUP workshop, our goal was to attract not just technologists who build open source software for internet shutdown scenarios, but also other stakeholders who can contribute, e.g. designers, community organizers, and other kinds of practitioners who haven’t been as involved previously. We created a space where this diverse group of practitioners could share their experiences, co-create, and contribute input for how these tools and scenarios can be better designed.&lt;/p&gt;
&lt;p&gt;There is a wealth of knowledge within the open source and human rights technology design community which can be leveraged to make human rights tools more user centered, usable and accessible by everyone. At Superbloom, we believe that creating bridges between stakeholder groups within shared cultural contexts provides insights that can lead to critical improvements as well as contribute to improvements that are globally relevant.&lt;/p&gt;
&lt;p&gt;We are dedicated to ensuring that the work needed to connect these different communities is well-facilitated and supported. One of our main aims in the workshop was to make sure that designers from a community that may not have as much experience with open source software or with human rights technology were able to offer their design expertise alongside their experience of residing in Taiwan/east Asia. This facilitation and community gathering work often goes unnoticed and unsupported. Critical human rights topics can be better tackled as a coordinated effort by bringing together different communities.&lt;/p&gt;
&lt;p&gt;When designing workshops for open source conferences we don’t know who will attend which sometimes makes it difficult to plan. Furthermore, we wanted the COSCUP workshop to be friendly and accessible to beginners. As such, we had many conversations with the organizers of the Open Design track and the volunteers helping us, to better understand their aims and how the workshop sits within the event.&lt;/p&gt;
&lt;p&gt;Despite having a sign-up process, we didn’t plan to “gate keep” participants. If attendees didn&amp;rsquo;t have a certain level of skill, we would not exclude them. We wanted to make sure this was open and available for all kinds of people; people with a lot of design expertise, people with not a lot of design knowledge, people versed in open source, and people with not a lot of open source knowledge. &lt;/p&gt;
&lt;p&gt;One of the ways we were successful in bringing many more designers into the space was in partnering with IxDA Taiwan. IxDA Taiwan brought an understanding of the design processes that made sense within Taiwan and supported attendees&amp;rsquo; understanding of designing for tools which they may not have a lot of experience with. While incredibly knowledgeable in design practices, designers and IxDA team members are not as knowledgeable in the design practices that work for human rights tools and internet shutdown scenarios.&lt;/p&gt;
&lt;p&gt;This is where Superbloom brought its unique expertise to the workshop. We design and build technology for human rights uses, for human rights activists and for internet shutdown scenarios on a daily basis. We are immersed in this knowledge and practice. &lt;/p&gt;
&lt;p&gt;While a lot of designers&amp;rsquo; knowledge and expertise is transferable into the human rights technology space, there needs to be more effort and support given to people who can be the facilitators and custodians of the bridges between skills and domains, and who can advise where those skills can be applied. &lt;/p&gt;
&lt;p&gt;Many of the design workshop activities were not necessarily new or ground breaking in technique, but as mentioned above, bringing together designers within the internet shutdown scenario space in an open source environment was the most groundbreaking part of the workshop.&lt;/p&gt;
&lt;h3 id=&#34;introductions-and-icebreaker&#34;&gt;Introductions and icebreaker&lt;/h3&gt;
&lt;p&gt;We began by introducing Superbloom and ourselves as facilitators, and the IxDA Taiwan team did the same. We started with an icebreaker activity to make sure that people didn’t necessarily gravitate towards the group in which they felt most comfortable.&lt;/p&gt;
&lt;h3 id=&#34;human-rights-tools-demo&#34;&gt;Human rights tools demo&lt;/h3&gt;
&lt;p&gt;After groups were formed, we demoed key human rights technologies and open source software tools, explaining how and why they are used. We focussed on tools that can be used offline, and also tools that have limited capabilities when there is a patchy internet connection. &lt;/p&gt;
&lt;p&gt;To gain insight, we brainstormed tools the participants knew about that could be used in internet shutdown scenarios. Participants suggested technology tools and also &amp;ldquo;low tech tools&amp;rdquo; such as ham radio or pen and paper to deliver messages to different people. Other suggested tools were: BB calls, drones, block chain, physical letters, radio messages, Starlink, satellite phones, Bridgefy, Lalamove and Telegram.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_understanding_internet_shutdowns_image_2_hu_a65aeff40533c30b.png&#34; alt=&#34;An image that shows many virtual sticky notes on a canvas. The writing is in Mandarin and English and lists various technologies and processes that people thought could be useful during internet shutdowns.&#34; width=&#34;740&#34; height=&#34;595&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;personas-discussion&#34;&gt;Personas discussion&lt;/h3&gt;
&lt;p&gt;We then moved into a segment around a series of personas we had prepared. These personas were intended to &amp;ldquo;spark ideas&amp;rdquo; and were there to be remixed and edited by workshop participants. This was the first activity the attendees worked on together in their groups. We asked them to read the personas as well as the various internet shutdown scenarios we had prepared and to choose which ones they wanted to focus on.&lt;/p&gt;
&lt;p&gt;With the tool knowledge from the demos, sample personas and scenarios workshop segments, we asked participants to adapt and amend the personas and scenarios we presented, or to come up with completely new scenarios. &lt;/p&gt;
&lt;p&gt;Some of the scenarios given were:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A user persona is covering a student-led protest about surveillance technology for her journalism job.&lt;/li&gt;
&lt;li&gt;A user persona is trying to access information about relocation in case content might be blocked via an internet shutdown. &lt;/li&gt;
&lt;li&gt;A user persona is being harassed and bullied online and needs to document what has happened and what is happening in order to send out the information to contacts before social media is blocked and her VPN stops working.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_understanding_internet_shutdowns_image_3_hu_f8dc5e9bdcbb4376.png&#34; alt=&#34;An image of virtual sticky notes detailing persona scenarios.&#34; width=&#34;740&#34; height=&#34;455&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Our personas followed a few different conventions, and participants were able to bring unique Taiwanese and East Asian perspectives.&lt;/p&gt;
&lt;p&gt;These are the personas we put forward:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A journalist and activist who identifies as a woman. She is a well-informed activist who stays up-to-date on current events and the latest news, and she has been targeted by the government and other entities. She uses a lot of chat applications to talk with contacts, and she writes a lot of articles that are not only critical of the government, but also talk about sensitive topics that governments and other entities would prefer citizens don’t talk about openly.&lt;/li&gt;
&lt;li&gt;An older computer science literate blogger and activist who has previously been surveilled and visited by Government authorities, detained and received many phishing articles after posting articles critical of government authorities around technology.&lt;/li&gt;
&lt;li&gt;A women&amp;rsquo;s and LGBTQ+ rights activist who works with students and other local women, advising them and funding them, as well as finding funding opportunities for them. In this role she supports a lot of different community members, and her needs were mostly around moving from a more typical role within society to a sensitive, high risk role via the nature of the work she&amp;rsquo;s doing in the personas. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_understanding_internet_shutdowns_image_4_hu_e00ad7b8150156b8.png&#34; alt=&#34;An image of two different personas. One a computer scientist in academia that has been critical of the government, and the other a journalist who covers protests and social movements.&#34; width=&#34;740&#34; height=&#34;636&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Sections detailed who they were and what they needed, what could hurt them, and their goals and struggles. The difference between what they need, what could hurt them and their struggles are often fuzzy. Trying to better understand what the person is going through is critical in order to better design tools for them.&lt;/p&gt;
&lt;p&gt;We also provided past user feedback from different human rights and internet shutdown related tools. We talked about the existing UI standards for human rights technology and current different circumvention tools. These are often not user-informed and have complex UIs and complex functions.&lt;/p&gt;
&lt;p&gt;The first half of the workshop mostly included understanding information, information gathering, and coming together as teams to better understand the problems. Before we simulated an internet shutdown, we asked workshop attendees to report to the group on their personas and their scenario. During the simulation, we asked participants to switch off the internet on their phone and various devices. This was to help those who have never experienced a situation without internet connectivity to better understand what it&amp;rsquo;s like, and how they might perform typical communications and technology tasks when they cannot rely on the internet.&lt;/p&gt;
&lt;h3 id=&#34;user-journey-mapping-exercises&#34;&gt;User journey mapping exercises&lt;/h3&gt;
&lt;p&gt;For the remainder of the workshop we took the persona, scenarios and understanding of OSS technologies, and used these to do user journey mapping exercises. We did this because we find these exercises to be profound within the internet shutdowns and circumvention tool scenarios, because it is where we find critical intervention points in tool usage. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_understanding_internet_shutdowns_image_5_hu_8586c481061121a9.png&#34; alt=&#34;This image shows a persona written and edited by a team at the workshop and their user journey map taking shape on large sheets of paper stuck on the wall with sticky notes in different sections of a user journey map.&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;p&gt;The user journey mapping exercise mostly included conversations about the different kinds of actions and choices that can be made during a large protest, or when being tracked and monitored by malicious entities, as a lot of people don’t have experience in what it&amp;rsquo;s like to experience these scenarios.&lt;/p&gt;
&lt;p&gt;During the workshop, we encouraged participants to think about the different possibilities, and to pick the route their chosen persona would most likely and logically take when faced with a user choice. There are not necessarily any incorrect routes. All routes of a user journey map are worth mapping, so that we can discover as many uses of tools as possible.&lt;/p&gt;
&lt;p&gt;Participants at workshops such as these will always greatly benefit from people with first hand experience of the high-risk human rights cases the personas were mapping. Lack of first-hand experience is a consistent challenge in delivering design and technology workshops of this kind. This is typically because we must ensure the safety of people who have experienced human rights abuses and internet shutdowns while still inviting them to workshops in order for them to offer their experiences and expertise. This can be a big ask of their time and resources.&lt;/p&gt;
&lt;p&gt;Sensitive to these dynamics, we step in and offer our own knowledge as a substitute for some of these first-hand experiences. This way, participants can ask us questions about the work we&amp;rsquo;ve done around these high-risk user situations and the choices they may make. We also encouraged the workshop participants to do research in whichever way they are able in order to map and model the different routes that could be open to the users for the user journey.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_understanding_internet_shutdowns_image_6_hu_223712ab3921cf10.png&#34; alt=&#34;An image of one team&amp;rsquo;s journey map which maps a protest scenario when the internet is shutdown.&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;p&gt;When teams were satisfied with their user journey maps, we invited them to find a critical point of intervention in order to explore what they could do to improve a tool or the experience of a user within the scenario.&lt;/p&gt;
&lt;h3 id=&#34;finding-critical-moments-in-user-journey&#34;&gt;Finding critical moments in user journey&lt;/h3&gt;
&lt;p&gt;In the workshop we used an example of a critical point of intervention we found within a protest internet shutdown scenario. We discovered a go-to behavior when the internet is shut off and the user still has access to a messaging application. This is where, despite the internet being &amp;ldquo;off&amp;rdquo;, users will still scroll their applications and message history while waiting to see if the messages go through. Here we found an important point of intervention. As users are unable to send critical files of information, they can scroll their chat history and &amp;ldquo;rediscover&amp;rdquo; files and information which may be useful.&lt;/p&gt;
&lt;p&gt;Here, the intervention was the act of sending essential information when the internet is &amp;ldquo;on&amp;rdquo; in case they need this information when the internet is &amp;ldquo;off&amp;rdquo;. This is what we learned through user journey mapping.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_understanding_internet_shutdowns_image_7_hu_a4147f8f188d4410.png&#34; alt=&#34;An image of the room during the workshop. People are sitting in seats as they listen while others present their journey maps.&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;ideation-and-design&#34;&gt;Ideation and design&lt;/h3&gt;
&lt;p&gt;Workshop participants found a number of critical points of intervention throughout the workshop and mapped a series of different interventions, from localized mesh networks to using taxi drivers to understand the layout of a city and deliver messages. Participants designed a variety of solutions that included software, hardware tools, utilizing existing tools and creating new technology.&lt;/p&gt;
&lt;p&gt;User experience interventions were developed such as pinning information at the top of messaging tools, and messaging applications automatically pinning when &amp;ldquo;offline&amp;rdquo; on that device.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_understanding_internet_shutdowns_image_8_hu_c7e6c7498fe0a4e.png&#34; alt=&#34;An image of one team&amp;rsquo;s prototype intervention with sketches. This idea utilized taxi drivers to find and distribute safe locations to civilians.&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;looking-ahead&#34;&gt;Looking ahead&lt;/h2&gt;
&lt;p&gt;In future internet shutdowns focused workshops, we would like to directly apply our learnings to the technology at hand. However, it would be much more useful if people who have experienced these scenarios and/or the tools creation teams are present. In order to close this gap, we will invite technology tool teams to workshops where direct tool interventions can be made live in an open source way. This is how we can develop and build on the success of this workshop.&lt;/p&gt;
&lt;p&gt;To sum up, we really enjoyed attending COSCUP 2023 and meeting all of the participants. We appreciate their dedication and full participation in the workshop.&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project contributors: &lt;a href=&#34;https://superbloom.design/&#34;&gt;Superbloom&lt;/a&gt;, &lt;a href=&#34;https://www.ixda.org.tw/&#34;&gt;IxDA Taiwan&lt;/a&gt;, &lt;a href=&#34;http://coscup.org/&#34;&gt;COSCUP&lt;/a&gt;, &lt;a href=&#34;https://www.ntust.edu.tw/home.php?Lang=en&#34;&gt;National Taiwan University of Science and Technology&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;With support from the &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Policy to Pixels</title>
      <link>https://superbloom.design/work/projects/policy-to-pixels/</link>
      <pubDate>Thu, 19 Oct 2023 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/work/projects/policy-to-pixels/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Six Key Tenets for Open Source Designers</title>
      <link>https://superbloom.design/learning/blog/six-key-tenets-for-open-source-designers/</link>
      <pubDate>Fri, 06 Oct 2023 19:49:06 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/six-key-tenets-for-open-source-designers/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_six_key_tenets_for_open_source_designers_hu_3c6562463a2b468c.png&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Being a designer in Open Source (OS) isn’t always easy or straightforward, neither is it the same for all designers. Different open source projects are set up differently, hence demand different outputs and engagements from designers. In this blog, we list the six main tenets for a successful design contribution to OS projects.&lt;/p&gt;
&lt;p&gt;Designers in Open Source may have their own reasons to be a part of OS, but if you’re new or still figuring out why you want to be in OS and how to make your way in, there are many helpful resources such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://designerup.co/blog/contributing-to-open-source-for-designers/&#34;&gt;This blog post&lt;/a&gt; written by DesignerUP which introduces the reader to Open Source, areas of contribution for designers in Open Source, how to find a project, mistakes to avoid and lots more.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://opensource.guide/how-to-contribute/&#34;&gt;This guide&lt;/a&gt; which details the context required to contribute, and walks you through how to contribute to Open Source.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.rocket.chat/blog/open-source-projects&#34;&gt;This article&lt;/a&gt;, which lists a number of Open Source projects, each with a brief description, and goes on to talk about why you should contribute to Open Source.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://learnwithnie.hashnode.dev/beginners-guide-to-open-source-design&#34;&gt;This article&lt;/a&gt; written by Victory Brown details some of the cultural and community aspects of joining an Open Source project for the first time as a designer.&lt;/li&gt;
&lt;li&gt;And &lt;a href=&#34;https://www.youtube.com/watch?v=t5QTs8oRFZE&#34;&gt;this talk&lt;/a&gt; by Abigail Makolo speaks about her experiences of contributing to Open Source as a designer and the “hacks” she learned.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There’s a reason why we’re still talking about why and how to contribute to Open Source which is about a lot more than becoming a better contributor or designer within the Open Source ecosystem. This is because the Open Source design community isn’t at a scale that can sustainably respond to Open Source design needs. There are still very few designers who have reached a stage where they feel comfortable cold-approaching an Open Source project to offer their contribution. These designers continue to self-learn and borrow design practices from the for-profit world and adapt it for Open Source and human rights centered design. Design in Open Source and Human Rights is an evolving practice that is slowed by the limited resources offered.&lt;/p&gt;
&lt;p&gt;Though this is a difficult space in which to practice design, we have compiled six tenets for designers to keep in mind when contributing to or working in Open Source. Although these can benefit any designer, they have been structured and written from an Open Source design perspective:&lt;/p&gt;
&lt;h4 id=&#34;1-center-the-users-in-your-thinking&#34;&gt;1. Center the users in your thinking&lt;/h4&gt;
&lt;p&gt;Users are the reason we produce design. Everything we produce is centered around solving the user’s problems. There may be users we don’t have an opportunity to interact with, especially for those of us who aren’t full-time designers on an Open Source project. To overcome this, we can try to learn user perspectives from “support issues”, user forums, project communication channels, such as Slack, Discord, Discourse etc, and even from developers and other team members who may previously have interacted with the users. Learning about users means making design decisions about our Open Source Software that makes sense to the users. The continued return on design effort investment is expressed in the form of features and commands being more regularly used and contributed to. The more detail we have about our users, the better decisions we can make about our designs. User needs aren’t only about designing a working solution within the technical or usability bounds of the software but also about considering their security, privacy, inclusion, accessibility, and diversity needs. Those users who belong to the &lt;a href=&#34;https://www.youtube.com/watch?v=QH1Na9OW-Bg&amp;amp;t=7s&#34;&gt;edge cases (or stress cases) for a product&lt;/a&gt;, or even those not to design it for. The only way for a designer to make these considerations a regular part of their work is to learn and practice them continuously. When we don’t, it is not easy to make it a part of the design process as it’s not included in our project planning, estimates or conversations with stakeholders. Ergo, it will be difficult to uphold why these considerations need attention and how they support product/business goals. All users are important users of Open Source Software, whether it is the people that use the tools, coders, designers or contributors, therefore we must keep in mind everyone that is affected by our work.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Example:&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;A GitHub issue for an Open Source project did not list any details or provide clarity about user behavior required for the design. As designers, we elaborated on the issue and added more context by bringing in users’ points of view via user stories and their journey using the product. Detailing a GitHub issue in such a manner is a valid contribution to the project and it shows that we’re thinking about the users. In another case, we ran a user journey mapping exercise to discover specific pain points and moments when the product could intervene in a users’ life to solve their problem. Designing around such moments is a great way to make our design contributions to Open Source Software user centric. &lt;/p&gt;
&lt;p&gt;In another example, &lt;a href=&#34;https://sosdesign.sustainoss.org/12&#34;&gt;here’s a talk&lt;/a&gt; by Abhishek Sharma about working with users while designing an Open Source product.&lt;/p&gt;
&lt;h4 id=&#34;2-learn-the-ways-of-a-developer&#34;&gt;2. Learn the ways of a developer&lt;/h4&gt;
&lt;p&gt;Wait, why are developers in second position? The collaboration and respect between designers and developers is critical to building widely useful Open Source Software. Developers perform an essential role because they implement design solutions, add technical constraints or opportunities and bring design concepts to life for the users. Learning about how they work and what is important to them makes us better design contributors, and we can learn a lot from them, especially if they’ve worked with other designers.&lt;/p&gt;
&lt;p&gt;There are some things we can only learn by working with developers, such as understanding the feasibility of our designs with the tech stack the product is built on. There’s little point getting into a debate or argument with a developer about why our ideas are the best solution for the users when the complexity and effort needed to build within the current tech stack hasn’t been considered. Developers will always have multiple priorities, therefore we must create design alternatives that work well for users and that are feasible to develop. We need perseverance for some ideas more than others to help the developers understand and agree to build them. And sometimes we have to totally revise an idea. All of this is a part of product development (regardless of whether it is Open Source!). The best solution always wins and it’s not about us versus the developer.&lt;/p&gt;
&lt;p&gt;In our product experience we try to keep a healthy mix of finding alternatives and pressing for an idea. Shipping a feature or solution is the most essential part of the job so that the product is useful. We frequently need to work with developers to iterate on an idea — this means that the most usable or ideal version of an idea won’t be shipped in one go; rather it is shipped in multiple release cycles. It’s normal to wait up to two years for a feature to go live in Open Source Software! &lt;/p&gt;
&lt;p&gt;Working with developers isn’t just about handing off our designs, it’s about building a partnership with them. In many cases we may not be able to interact directly with developers, and we need to make sure our ideas are explained clearly in writing (or via a recorded video of our screen while explaining the design) to facilitate hand-off of our designs. This should include a detailed description of the solution with comments, annotations and prototype, along with our assumptions and user considerations. This should be done in such a way that developers can understand the journey we’ve taken to arrive at a solution, and shouldn’t require a live presentation of our work. Developers who have worked with other designers are able to understand where we’re coming from even before we have explained ourselves. They will appreciate our work, be able to provide constructive criticism and understand our point of view. If they haven’t worked a lot with other designers, they may only be able to share their own perspectives which can still be useful if we learn or ask questions about why a design feature is not possible. Most of the time we will find a solution that the developer and we are both happy with. At the same time, it is sometimes frustrating when we’re unable to implement ideas in the way we want. In these moments work collaboratively to find a solution both parties agree with.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Examples of Superbloom’s work with developers in previous projects:&lt;/em&gt; &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Using the “Five Whys” method, we used this Superbloom resource “&lt;a href=&#34;https://sprblm.github.io/devs-guide-to/synthesis-for-open-source/&#34;&gt;Synthesis for Open-Source&lt;/a&gt;” to help developers undertake various user centric tasks such as user testing, recruiting users, planning, and operations, to synthesize findings from users. This resource is not about getting developers to do design work, rather, it’s part of a collaborative effort to sensitize each to one another’s processes. &lt;/li&gt;
&lt;li&gt;During the research phase of our &lt;a href=&#34;https://user-project.superbloom.design/&#34;&gt;USER project&lt;/a&gt;, we discovered various points of view and patterns around how scientific Open Source projects and the developers working on them view usability and design. The project investigates the conditions that enable scientific open source teams to prioritize and focus successfully on usability.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;3-think-about-assets-and-design-documentation&#34;&gt;3. Think about assets and design documentation&lt;/h4&gt;
&lt;p&gt;This is how we can get our ideas and solutions across to developers, users, product managers or any other stakeholders we’re working with. It includes our:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Penpot or Figma file&lt;/li&gt;
&lt;li&gt;Documentation of user stories&lt;/li&gt;
&lt;li&gt;Communicating on GitHub or other channels&lt;/li&gt;
&lt;li&gt;Measurement metrics&lt;/li&gt;
&lt;li&gt;Assumptions and considerations&lt;/li&gt;
&lt;li&gt;Documentation for another designer to collaborate&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All of these help to explain our design specifications, why the design works and how someone can contribute. Assets also include our design systems, grids, components, and everything else we create for a handoff to developers or other designers. In our experience it has been a valuable investment to set up component libraries and design systems at the start of a project even if it’s just one component. It doesn’t have to be a complete, extensive, all encompassing design system at the outset. It’s about laying down the foundation with our atoms and molecules (&lt;a href=&#34;https://atomicdesign.bradfrost.com/&#34;&gt;Brad Frost’s atomic design&lt;/a&gt;) in place. We can always go back and edit as and when the designs change, however, it is useful to set them in place so that we don’t have to spend a lot of time managing changes across our design file even for minor changes. If we aren’t building a custom design system for a project, we can also benefit from Open Source design systems such as Material UI Design or paid libraries. Today, really advanced tools such as &lt;a href=&#34;https://penpot.app/&#34;&gt;Penpot&lt;/a&gt; (an Open Source prototyping tool we can use in a browser), or &lt;a href=&#34;https://www.figma.com/&#34;&gt;Figma&lt;/a&gt;, enable this type of work and these tools are always being improved. Therefore, make all design assets easy to read, understand and access by anyone — there’s usability to our assets too! We may even user test it if we’re really driven to produce high quality work.&lt;/p&gt;
&lt;p&gt;Here’s &lt;a href=&#34;https://www.figma.com/file/GLg0zPNnwMEGIb9TytCrxQ/Resilience-App?type=design&amp;amp;node-id=1257-553&amp;amp;mode=design&amp;amp;t=ffcf1oKyqCaZZUIf-0&#34;&gt;an example&lt;/a&gt; of documentation that enables designers and other stakeholders to navigate and use a design file. This documents the team structure, areas for contribution, and even some instructions for collaborating in Figma!&lt;/p&gt;
&lt;p&gt;In another instance, we helped discover insights about the requirements from a user perspective by talking to users and updating GitHub issues. This asset helped everyone involved in the project to make the right product decisions.&lt;/p&gt;
&lt;h4 id=&#34;4-think-about-other-designers&#34;&gt;4. Think about other designers&lt;/h4&gt;
&lt;p&gt;Early in my career, I designed with the sole intention of communicating an idea to a team and developers by putting together screen grabs and annotations, or only designing a part of the screen, as if there was no need for the UI once it was built and added to the product. I soon realized this was a very short-sighted view of my design contributions. This method made it hard for other designers to use my designs, and made it challenging to reuse them or build on top of them. I took this approach because:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;I didn’t have the required time or budget to do the design properly&lt;/li&gt;
&lt;li&gt;I wanted to optimize the design process and work for myself&lt;/li&gt;
&lt;li&gt;I didn’t know the bigger picture of the product and the extent of contributions required from me&lt;/li&gt;
&lt;li&gt;I didn’t have opportunities to collaborate with other designers&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It’s good to design on the basis that we may not contribute to a project forever and therefore set up the designs in a way that we can easily pass the baton onto other designers. This connects to the previous point about how we set up our assets and documents. When we step outside the established “norm” of designers being solo creative geniuses, and look at a bigger, collaborative, co-designed picture, our actions and approach towards the project changes. We start paying more attention to documentation, asset creation and keeping our work clean and proper at all times. Thinking about our designer community also makes the project more sustainable from a design perspective. This means that we may have to size up the project and estimate the number of tasks, and how long they will take. With a little practice, this becomes second nature.&lt;/p&gt;
&lt;p&gt;Thinking about other designers enables us to be welcoming to them and may also help onboard and mentor them or learn from them ourselves.&lt;br&gt;
&lt;br&gt;
Example: &lt;a href=&#34;https://www.youtube.com/watch?v=LW62cVDckO4&amp;amp;list=PLwz4EueITgvmJzrNWbGkAMeDVLlOWQuch&#34;&gt;Here’s a talk by Eriol Fox&lt;/a&gt; about how they enabled onboarding of designers into OSS.&lt;/p&gt;
&lt;h4 id=&#34;5-think-about-the-product-business-and-domain&#34;&gt;5. Think about the product, business and domain&lt;/h4&gt;
&lt;p&gt;In a Superbloom research project, we found that one of the foremost roadblocks or challenges to valuable design contributions is a lack of understanding of the domain, business and users. For example, a designer contributing to a scientific research OSS in biochemistry must also understand a few things about biochemistry and how its users, the scientists, work. Each domain has its nuances and may require different design principles and approaches. It’s not something that can’t be learnt but it can be demanding. A designer’s work is not just about the screens and User Interface, we help people achieve their goals. Therefore, from a goals perspective, it’s crucial that OSS designers understand what is feasible to build and how to build it. It may not be easy to find designers who are familiar with the subject matter and so it becomes a product team’s responsibility to nurture a designer in their domain. A designer must also decide which domain, product or business they wish to contribute to. It’s worth considering which domain we want to work in long term, for example, messaging, productivity, social tech, healthcare, scientific research etc… so that we remain interested even when we change projects. But for those getting started, start anywhere! There are many opportunities and we can always change our trajectory later!&lt;/p&gt;
&lt;h4 id=&#34;6-think-about-the-community&#34;&gt;6. Think about the community&lt;/h4&gt;
&lt;p&gt;A community approach and building together is at the heart of Open Source Software (not just for coders!). This may seem like an extension of thinking about the users or other designers, but there’s more to it. It manifests by creating resources for the community, sometimes beyond our OSS design team and domain. We can create learning materials, design systems, a components library, illustrations etc. For designers who may be starting out — it’s never too early to think about the extended Open Source community. To those more focused on their career and growth, — it’s never too late! &lt;/p&gt;
&lt;p&gt;There are many other ways to contribute to the community e.g. participating in community events, networking with others, sharing job/work opportunities, adopting, translating and localizing resources for your region, exchanging ideas and learning with community members.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Example:&lt;/em&gt; &lt;/p&gt;
&lt;p&gt;Both &lt;a href=&#34;https://opensourcedesign.net/&#34;&gt;Open Source Design&lt;/a&gt; and &lt;a href=&#34;https://simplysecure.org/what-we-do/#community-building&#34;&gt;Superbloom&lt;/a&gt; have channels where many folks from the Open Source community hang out, interact and participate, and the &lt;a href=&#34;https://sosdesign.sustainoss.org/&#34;&gt;Sustain Open Source Design&lt;/a&gt; podcast is a space to talk about OSS experiences.&lt;/p&gt;
&lt;p&gt;*﻿**&lt;/p&gt;
&lt;p&gt;To sum up, it may not always be possible to balance these six tenets at all times during our work, but to make our contributions long lasting and sustainable, we have to keep trying!&lt;/p&gt;
&lt;p&gt;C﻿redits: &lt;a href=&#34;https://superbloom.design/about/people/abhishek/&#34;&gt;Abhishek Sharma&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/about/people/eriol/&#34;&gt;Eriol Fox&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>The Secret Life of Open Source Designers</title>
      <link>https://superbloom.design/learning/blog/the-secret-life-of-open-source-designers/</link>
      <pubDate>Wed, 04 Oct 2023 21:18:52 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/the-secret-life-of-open-source-designers/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_designers_in_oss_image_1_hu_b99cf18cc4d095e0.png&#34; alt=&#34;n illustration of a person with shoulder length hair facing away from the camera sitting on a chair at a laptop with an open book next to them. The text reads “A summary of diary studies from designers who contribute to Open Source Software”&#34; width=&#34;740&#34; height=&#34;488&#34;&gt;
&lt;/p&gt;
&lt;h1 id=&#34;a-summary-of-diary-studies-from-designers-who-contribute-to-open-source-software&#34;&gt;A summary of diary studies from designers who contribute to Open Source Software&lt;/h1&gt;
&lt;p&gt;The aim of this short research project was to investigate some of the key questions relating to design in OSS and fill some of the larger systemic &amp;ldquo;gaps&amp;rdquo; of information from non-code contributors&amp;rsquo; experiences in OSS. There is existing research about designers in open source, but it has focused on analysis of data on issue trackers or interviews with designers. Thus, longitudinal, qualitative analysis of everyday activities are missing. We planned this research as a &lt;a href=&#34;https://www.nngroup.com/articles/diary-studies/&#34;&gt;diary study&lt;/a&gt;. This also enabled participants to describe their experiences in a safe environment and through anonymous, privacy respecting means. We were able to award a stipend to a sample of designers who recorded in their diaries. &lt;/p&gt;
&lt;p&gt;Our research was enabled by an OCEAN grant (&lt;a href=&#34;https://vermontcomplexsystems.org/partner/OCEAN/awards/&#34;&gt;Open-Source Ecosystems and Networks Research Awards program&lt;/a&gt;) awarded to superbloom in 2022 by the Vermont Complex Systems Center at The University of Vermont.&lt;/p&gt;
&lt;p&gt;This blog post is an overview of our OSS designer diary study findings  and you can find the full &lt;a href=&#34;https://github.com/simplysecure/Diary-Studies-Designers-in-OSS/blob/main/findings-report.md&#34;&gt;findings report in our repository on GitHub&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;study-structure&#34;&gt;Study structure&lt;/h2&gt;
&lt;p&gt;In order to obtain an understanding of our participants, we started the study with a series of semi-structured interviews lasting approximately forty five minutes. Moving into the study we asked the designers a series of weekly questions and they used Google Forms to record their weekly OSS diary submissions. They could also use free form documents, audio recordings or video recordings to do this. &lt;/p&gt;
&lt;h2 id=&#34;an-idea-of-who-we-studied-and-the-oss-that-was-contributed-to&#34;&gt;An idea of who we studied and the OSS that was contributed to&lt;/h2&gt;
&lt;p&gt;We published an open call for designers to participate in a diary study and selected as many globally distributed people as possible. Our participants were from and reside in: Canada, USA, Nigeria, Brazil and the Netherlands. Our participants were sixty percent women identifying and forty percent men identifying. Sixty per cent of participants were early in their design (and OSS) careers and forty percent were postgraduate students. All of our study participants had been contributing to OSS for at least one year. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_designers_in_oss_image_2_hu_e39d1b3c50ecef97.png&#34; width=&#34;740&#34; height=&#34;353&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Approximately 10 OSS projects were contributed to in some way across the study. These projects ranged from educational tools, spoken language apps, websites, events, browser extensions, open data, scientific tools, academic tools and visualization tools.&lt;/p&gt;
&lt;h2 id=&#34;how-do-designers-decide-whether-theyd-like-to-contribute-to-or-work-on-an-oss-project&#34;&gt;How do designers decide whether they’d like to contribute to or work on an OSS project?&lt;/h2&gt;
&lt;p&gt;Most designers were aligned in how they first came to the decision to contribute to an OSS. The following being the most common ways of deciding an OSS project is ready for design contributions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Is it reasonably clear what the OSS project wants from the design/designer? Is the project clear what problems they want solved by the designer?&lt;/li&gt;
&lt;li&gt;Am I able to do that skill/task or am I able to learn how to do it for this contribution?&lt;/li&gt;
&lt;li&gt;How &amp;ldquo;in need&amp;rdquo; is the project? Are there others that can do this or does the project have good enough support to get this done elsewhere?&lt;/li&gt;
&lt;li&gt;Is this OSS a one-person project and is it still active?&lt;/li&gt;
&lt;li&gt;How close is this OSS to my culture/geo-location? Will I be able to contribute in my native language comfortably and be welcomed with my context?&lt;/li&gt;
&lt;li&gt;Does the documentation make sense to me and can I learn enough about the OSS in order to participate?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Along with these bullet points you can find a more detailed account of &lt;a href=&#34;https://github.com/simplysecure/Diary-Studies-Designers-in-OSS/blob/main/findings-report.md#how-do-designers-decide-whether-theyd-like-to-contribute-to-or-work-on-an-oss-project&#34;&gt;how designers decide whether they’d like to contribute to or work on an OSS project in our findings document&lt;/a&gt;. Knowing how, when and why a designer chooses to engage with an OSS project is critical information for OSS projects aiming to become more inclusive to non-coding relating contributions and OSS that intends to center users that are not part of the “contribution” communication cycles e.g. users that do not participate in issues, pull requests and discussions.&lt;/p&gt;
&lt;h2 id=&#34;what-work-did-designers-share&#34;&gt;What work did designers share?&lt;/h2&gt;
&lt;p&gt;Most participants shared either UX research written documents, repositories (GitHub/GitLab) or websites of information as “artifacts&amp;quot;. They rarely shared User Interface (UI) progress design with us, but they did describe the processes involved in designing the UI elements such as technical requirements, conversations with users and developers/owners of the OSS projects. &lt;/p&gt;
&lt;p&gt;Four collections of contributions focused around OSS events for particular technologies and the design work required to operate those events (e.g. illustration/graphics, merchandise design, event website design, form design etc). The remaining design contributions were a combination of User Research documents (user testing plans/scripts and Heuristic Analysis) and results, UI/UX design visuals in shareable design file formats, design/visual systems for projects to follow, accessibility research/design and design insight/guidance in issues/PRs.&lt;/p&gt;
&lt;p&gt;Understanding what is produced  within a timescale by designers across their level of contribution commitment helps us to better understand design as part of a process that can be better included in the OSS space. The first step to inclusion of more user centered design in OSS projects is to first understand the  processes designers are using in OSS right now.&lt;/p&gt;
&lt;h1 id=&#34;an-overview-of-our-findings&#34;&gt;An overview of our findings&lt;/h1&gt;
&lt;p&gt;A number of different challenges and focuses surfaced during the 16 week study. There are &lt;a href=&#34;https://github.com/simplysecure/Diary-Studies-Designers-in-OSS/blob/main/findings-report.md&#34;&gt;sections in the findings&lt;/a&gt; about how designers and developers collaborate and the meaning that collaboration holds for designers in OSS, how designers are currently practicing openness in their design for OSS and the attempts they make to be more “open” when design is a type of contribution where openness is difficult and time consuming. As one designer in the diary study states “I’m on the way (to more openness)! Using Penpot and not Figma…”.&lt;/p&gt;
&lt;p&gt;We then moved into sections where we collected accounts on what success means for designers and how that is defined in their relationships with other OSS contributors and the OSS project itself. &lt;/p&gt;
&lt;p&gt;These success sections are:&lt;/p&gt;
&lt;p&gt;Success via feedback — when and what feedback designers contributing design to OSS find valuable and in what time frames. &lt;/p&gt;
&lt;p&gt;This section is full of rich information and includes comments about when feedback is “not usable” by designers, which is when feedback is missing constructive and relevant critique and only non-specific affirmations of “good” or opinions of “bad”. Some of this section speaks to who and how many people involved in the OSS give feedback and when that becomes unwieldy.&lt;/p&gt;
&lt;p&gt;Success via completion of design and/or &amp;ldquo;live release&amp;rdquo; — The importance that designers place on design contributions produced for OSS “going live” and an overall lack of clarity about when they might “go live” is &lt;a href=&#34;https://github.com/simplysecure/Diary-Studies-Designers-in-OSS/blob/main/findings-report.md#success-via-completion-of-design-andor-live-release&#34;&gt;detailed in this section on success&lt;/a&gt;. In our own personal experience contributing design to OSS, design can often be “completed” many months or years before the contributors or teams responsible for implementation make moves to implement it. This isn’t necessarily a bad experience for designers, but an unusual one given that most commercial design for software has shorter implementation cycles and more consistent communication. Helping designers learn and understand the timelines for OSS is critical to their understanding and inclusion.&lt;/p&gt;
&lt;p&gt;Success via knowing what is a priority for the OSS — In the section about prioritizing, we hear how some designers are unsure who/what group of people have authority in the OSS to make decisions and how they struggle to assert design processes that bring in the voice of users to help OSS better prioritize based on user insight. &lt;/p&gt;
&lt;p&gt;Success via attracting more designers to the OSS — Attracting and supporting more designers into OSS is a success metric for some designers. These designers are typically those who contribute to multiple OSS projects, and a strong sense of how mentoring and supporting designers is healthy for both design and OSS cultures and industries.&lt;/p&gt;
&lt;p&gt;Success via acknowledgement, inclusion and collaboration — Designers, like many OSS contributors, thrive on positive acknowledgment, gratitude and being purposefully included in the OSS, both in terms of their contribution, but also the wider OSS contribution culture and onboarding.&lt;/p&gt;
&lt;p&gt;Success via accessibility and usability — Our last section focuses on how some designers find success in ensuring users with disabilities and impairments are included, and users who are not at the same knowledge or skill level as developers and maintainers are included. This is a difficult success measurement to achieve for most designers given what tasks take priority in OSS (code contributions typically).&lt;/p&gt;
&lt;p&gt;The final section of the findings focuses on length of communication cycles, decision making processes, being paid for contributions, dealing with overwhelming amounts of work and how designers might want to exit an OSS project. &lt;/p&gt;
&lt;p&gt;As described by the designers in the study, these sections start off by detailing the long cycles of communication involved in creating and approving design work and the ensuing confusion around decision making authority, and the lack of agency designers feel they can create for themselves without being &amp;ldquo;granted&amp;rdquo; decision making &amp;ldquo;power&amp;rdquo; about what design of the OSS could look like. &lt;/p&gt;
&lt;p&gt;The next sections talk about designers&amp;rsquo; feelings around being paid for contributions. These were generally positive, yet some expressed payment being against OSS contribution purposes. Designers then detailed the amount of work they feel needs to be done on their OSS projects as overwhelming, and explained how they give comments and advice to OSS projects about what OSS could look like as designers transition out of active contribution to more advisory, mentoring roles, and eventually leave OSS projects and communities.&lt;/p&gt;
&lt;p&gt;Our findings are full of rich information supported by quotes from our designer participants along with some of our own researchers&amp;rsquo; interpretations and hypotheses on the meaning behind certain findings.&lt;/p&gt;
&lt;h2 id=&#34;implications-of-this-study-and-emergent-recommendations&#34;&gt;Implications of this study and emergent recommendations&lt;/h2&gt;
&lt;p&gt;We produced a series of recommendations from the findings and these were supported by sections of the research. These recommendations include advice such as:&lt;/p&gt;
&lt;p&gt;As an OSS project interested in receiving design contributions, review and take note of the ways in which designers decide whether to offer design services to an OSS project. Some of these indicators include “Is the project clear what problems they want solved by the designer?” and “Is this OSS a one-person project and is it still active?” See &lt;a href=&#34;https://github.com/simplysecure/Diary-Studies-Designers-in-OSS/discussions/19&#34;&gt;&amp;ldquo;How do designers decide whether they’d like to contribute to or work on an OSS project?”&lt;/a&gt; section.&lt;/p&gt;
&lt;p&gt;A way to improve user centered design in OSS by helping designers to define rough definitions of user types of the OSS collaboratively with OSS project team members. See &lt;a href=&#34;https://github.com/simplysecure/Diary-Studies-Designers-in-OSS/discussions/34&#34;&gt;&amp;ldquo;Who are the &amp;ldquo;users”?”&lt;/a&gt; section.&lt;/p&gt;
&lt;p&gt;You can find these emergent recommendations here in our &lt;a href=&#34;https://github.com/simplysecure/Diary-Studies-Designers-in-OSS/discussions/categories/potential-future-research-recommendations&#34;&gt;GitHub projects discussion&lt;/a&gt; section. We invite community members to comment and discuss these recommendations.&lt;/p&gt;
&lt;p&gt;The wider implications of the diary studies are as wide reaching as the data collected in the study. Our first critical implication is that it is possible to collect information about how design is being done in real time by designers in the OSS space. What we learned about behaviors, processes, communication and success is vital for building understanding of design in OSS as an ongoing commitment into the future, yet the simple knowledge that these studies can and should be funded and produced is encouraging for the future of better designed OSS to come.&lt;/p&gt;
&lt;h1 id=&#34;continuing-to-learn-about-design-and-designers-in-oss&#34;&gt;Continuing to learn about design and designers in OSS&lt;/h1&gt;
&lt;p&gt;This study was one of the first to capture OSS designers&amp;rsquo; experiences across multiple weeks and see what recurring trends and insights we can learn about designers&amp;rsquo; participation in OSS. There are, however, many missing components to this study which  would benefit the OSS community widely. This includes inviting more OSS projects and community members into interviews and better understanding the ways in which different roles view design and designers alongside the purpose of the OSS. &lt;/p&gt;
&lt;p&gt;Take a look at &lt;a href=&#34;https://github.com/simplysecure/Diary-Studies-Designers-in-OSS/&#34;&gt;our GitHub repository&lt;/a&gt; where we captured the ongoing data from designers across the diary study weeks. There, you can add new issues for data you’d like to see in the next set of diary studies and discuss these findings in the &lt;a href=&#34;https://github.com/simplysecure/Diary-Studies-Designers-in-OSS/discussions&#34;&gt;discussion section of GitHub&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If you’d like to participate in the next round of OSS designer diary studies, email &lt;a href=&#34;http://OSSdesignerdiaries@superbloom.design&#34;&gt;OSSdesignerdiaries@superbloom.design&lt;/a&gt; or if you’d like to contribute to funding these diary studies, email &lt;a href=&#34;http://OSSdesignerdiaries@superbloom.design&#34;&gt;OSSdesignerdiaries@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;h1 id=&#34;credits&#34;&gt;Credits&lt;/h1&gt;
&lt;p&gt;Project contributors: &lt;a href=&#34;https://superbloom.design/&#34;&gt;Superbloom&lt;/a&gt;, &lt;a href=&#34;https://vermontcomplexsystems.org/partner/OCEAN/awards/&#34;&gt;Open-Source Complex Ecosystems &amp;amp; Networks (OCEAN)&lt;/a&gt;, &lt;a href=&#34;https://vermontcomplexsystems.org/&#34;&gt;Vermont Complex Systems Center at the University of Vermont&lt;/a&gt; along with the anonymous designers who participated in our research.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;br&gt;
With support from &lt;a href=&#34;https://opensourcedesign.net/&#34;&gt;Open Source Design&lt;/a&gt; volunteers &lt;a href=&#34;https://github.com/nimishavijay&#34;&gt;Nimisha Vijay&lt;/a&gt; and &lt;a href=&#34;https://www.fordes.de/&#34;&gt;Jan Dittrich&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>OCEAN</title>
      <link>https://superbloom.design/work/projects/ocean/</link>
      <pubDate>Wed, 04 Oct 2023 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/work/projects/ocean/</guid>
      <description>&lt;p&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Bringing Human Centered Design to the Decentralized Web</title>
      <link>https://superbloom.design/learning/blog/bringing-human-centered-design-to-the-decentralized-web/</link>
      <pubDate>Tue, 26 Sep 2023 10:40:05 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/bringing-human-centered-design-to-the-decentralized-web/</guid>
      <description>&lt;p&gt;Superbloom recently attended DWeb Camp 2023, an “unconference” focused on building a more resilient, private, and accessible decentralized web. We stewarded the event’s first ever Design Track; Ngọc Triệu led organization of the Design Track with support from Philliph Drummond. It was a real treat to camp among California redwoods and explore the intersections of human-centered design and decentralized technologies. Indeed, our curiosity and passion for both motivated us in what proved to be an immense organizational effort both before and during the event.&lt;/p&gt;
&lt;p&gt;Over the course of the four days, the Design Track served as a hub for all things related to human-centered design. The track itself became a space where designers, developers, researchers, end-users and policymakers came together to understand how we as a community could create a more humane decentralized web—i.e. one that concerns itself with being as decentralized, distributed, and resilient as it is usable, inclusive, and sustainable.&lt;/p&gt;
&lt;h3 id=&#34;before-camp-planning-and-organizing&#34;&gt;Before camp: planning and organizing&lt;/h3&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://images.squarespace-cdn.com/content/v1/54064905e4b072d122d5b8d2/1423349847615-W16P7TAED78GEMMAMEKY/DSC_0137.jpg?format=750w&#34; alt=&#34;View of Hacker&amp;rsquo;s Hall at Camp Navarro&#34;&gt;
&lt;/p&gt;
&lt;p&gt;To create the clearing that then became the Design Track at Camp Navarro, we co-organized an inclusive space that was open to a variety of thematic topics within the domain of user experience design. We wanted to broaden our focus, moving away from curated design and usability-related sessions. When we first met our collaborators, it was clear we all had a desire to deepen the camp experience for &lt;a href=&#34;https://dwebcamp.org/fellowships/&#34;&gt;DWeb Fellows&lt;/a&gt; via the track’s content. We held planning meetings with other DWeb community co-organizers, which resulted in launching &lt;a href=&#34;https://dwebcamp.org/designers/&#34;&gt;a dedicated webpage&lt;/a&gt; on the DWeb site, and a Designer Facilitator Discord to help inform and organize the design track facilitators and design practitioners attending camp. We settled on a total of 14 sessions: co-design workshops, clinics, meetups along with open discussions on topics like privacy and security, aesthetics, user onboarding and advocacy, and envisioning alternative futures.d&lt;/p&gt;
&lt;h3 id=&#34;during-camp-stewardship-and-networking&#34;&gt;During camp: stewardship and networking&lt;/h3&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://ia802709.us.archive.org/BookReader/BookReaderImages.php?zip=/15/items/2023-06-21-dweb-ver-2-images/2023-06-21-Dweb-ver2_jp2.zip&amp;amp;file=2023-06-21-Dweb-ver2_jp2/2023-06-21-Dweb-ver2_0473.jp2&amp;amp;id=2023-06-21-dweb-ver-2-images&amp;amp;scale=2&amp;amp;rotate=0&#34; alt=&#34;DWeb Camp Circle&#34;&gt;
&lt;/p&gt;
&lt;p&gt;At camp we oversaw the Design Track from Cozy Hollow, a delightful nook tucked away just below Hacker’s Hall. From here, we focused on supporting facilitators with their sessions and helped attendees to make meaningful connections with one another. A big part of that work was helping with user testing and feedback for DWeb Camp’s Emergence App, creating a &lt;a href=&#34;https://drive.google.com/file/d/17XwMjoiSNpHmqMep4PMDOPnhOxDp29cl/view?usp=sharing&#34;&gt;zine&lt;/a&gt; for the Local Network team, and leading two sessions: &amp;ldquo;Human-Centered Design for Responsible AI &amp;amp; Tech&amp;rdquo; and &amp;ldquo;Design &amp;amp; Usability Clinic.” These two hands-on sessions served as a &amp;ldquo;mushroom patch&amp;rdquo; from where we spread design knowledge, resources, and tools across the many conversations at camp. We did this by promoting meaningful conversations about the risk, usability, and design with community leaders, founders, creators, funders, and end-users during each of the sessions.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/LAN-zine-cover_hu_d0baed96d9901332.png&#34; alt=&#34;Cover for Local Area Network Zine&#34; width=&#34;740&#34; height=&#34;1131&#34;&gt;
&lt;/p&gt;
&lt;p&gt;In bringing together the design community at DWeb Camp, as co-organizers we wanted to learn more about the real human challenges facing DWeb projects. We spoke with teams behind apps such as Manyverse, Mapeo, and CENO Browser to understand each of teams’ goals and pain points. These conversations revealed that while encryption and resilience (security) are priorities, usability and accessibility continues to remain an afterthought. We learned that the dev teams lacked the resources, or struggled to develop deep insight into how people actually use, or intend to use, their products. We found that many decentralized web applications tend to be challenging and cumbersome to use, creating obstacles to broader adoption. We heard that the marginalized groups that could most benefit from these tools are often not included in the design process. A common feeling is that the needs of end-users are not prioritized on a systemic level.&lt;/p&gt;
&lt;h3 id=&#34;after-the-camp-reflections-and-learning&#34;&gt;After the camp: reflections and learning&lt;/h3&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://dwebcamp.org/media/DWebTomorrow-cover01.banner.jpg&#34; alt=&#34;Dweb Tomorrow Banner&#34;&gt;
&lt;/p&gt;
&lt;p&gt;After the event, we spent some time reflecting on our experiences to understand what we had learned. We reviewed some of the consistent questions and topics collected from Design Track sessions including: how to onboard designers, the challenge to secure funding and resources for user research or design work, and the nuances of onboarding new users to different styles or modes of social networking. The internet shutdown experiment called &lt;a href=&#34;https://dwebcamp.org/tomorrow/&#34;&gt;“Tomorrow”&lt;/a&gt; is a great example of both the latter and the other issues related to the Design Track. &lt;/p&gt;
&lt;p&gt;On the Saturday and Sunday of DWeb Camp, the camp’s entire local area network – and, unexpectedly, the camp’s electrical power - was shutdown meaning attendees were unable to connect to the internet. This experience was simultaneously enlightening and fruitful. It rooted in us the importance of focusing on not only the technology needed during an internet shutdown, but also on the broader societal conditions that enable or create friction in the use of peer-to-peer (P2P) technologies. I.e. it revealed that some could not “see the forest for the trees”. This provided a concrete, tangible understanding of the importance of advocating for those who experience heavy censorship or internet shutdowns, as well as those who have no access, or degrees of limited access, to the web or electrical infrastructure.&lt;/p&gt;
&lt;p&gt;Reflecting on the “Tomorrow” experiment made us respect it for the experiment that it was and led us to ponder what might need to change to make the DWeb Camp more human-centered. Here are a few ideas:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Rally around real people&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We must advocate for end users: the humans experiencing the decentralized platforms and tools being created, especially those facing censorship and shutdowns. Understanding how they live and their needs is critical to building technology interventions that resonate with and fit into people’s lives. To do this well, software teams require a collaborative relationship with consistent input from end users to improve tools and better serve users’ needs.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Design and designers are critical infrastructure&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Funders and builders in the DWeb ecosystem must prioritize people&amp;rsquo;s needs from the start, not as an afterthought. And adding experienced designers to their teams who grasp the human side of decentralized tech can accelerate efforts. Our experiences and observations at DWeb Camp further validated the importance of integrating usability and accessibility into the infrastructure of the decentralized web.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Design intuitive onboarding&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;There’s a huge knowledge gap between centralized tech and new, decentralized protocols for most end users. Again, intuitive onboarding is a critical touchpoint to help bridge this divide, especially for the average, non-technical user. And generally, this knowledge gap can be addressed by informing users about key differences which might affect their experience of a decentralized application. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Look beyond the technology&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;During the experiment, the focus of some focused was very narrow i.e. on testing apps whereas we felt they should have focused on the human experience enabled by those tools, and the broader context of the overall experience instead, e.g. preparation, communication, and community infrastructure. However, this narrow focus did highlight that compounding technical issues can create some wicked challenges. Challenges that should be considered as part of developing design intervention e.g. developing low-power mode for applications for use in shutdown scenarios, or having multiple methods applications may use to communicate so that they are not dependent on mechanisms that might have additional dependencies, e.g. power and cell phone towers, or WiFi and power to routers.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open up the design process&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;DWeb values collaboration, so we should extend that to valuing open design as well through practices such as participatory workshops, and sharing research learnings. An open collaborative process is desirable for many reasons. It creates a sense of shared ownership, fosters empathy and understanding among team members, encourages transparency and accountability, and can lead to better design outcomes that reflect diverse perspectives and needs. By opening up the design process, one can create a more collaborative and inclusive environment that empowers designers, developers, and end-users alike to together build a more humane decentralized web.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Build more humane tech together&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Established designers should mentor new voices to grow the ranks of human-centered DWeb designers. DWeb Camp provides a perfect knowledge sharing forum for this.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Looking ahead: follow-ups and future engagements&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We had many aspirations for DWeb Camp 2023 which certainly brought its own challenges. From logistical hiccups to managing different tasks simultaneously, the journey found us in some arduous and rocky outcrops, but it was ultimately very rewarding. The distributed physical and social structures of the Camp made group convening difficult, and last-minute changes posed additional problems we had to adapt to. However, the positive feedback we received underlined the significance and impact of having a designated Design Track, and why such a space was necessary.&lt;/p&gt;
&lt;p&gt;The end of DWeb Camp 2023 marked the beginning of numerous follow-ups and potential collaborations. Through these collaborations, we aim to further the conversation around design and usability, fostering a more inclusive and user-friendly decentralized web space.&lt;/p&gt;
&lt;p&gt;DWeb Camp 2023 offered a unique platform for designers, technologists, and other stakeholders to engage, collaborate, and discuss how to make the decentralized web more user-friendly, inclusive, and environmentally conscious. As we move forward, the lessons learned and the connections made at the camp will play a significant role in driving the design and usability agenda in the DWeb space. Our next steps are to continue spreading the word and taking an intersectional approach that distributes power equitably. After diving deep into the decentralized future, we’re hopeful we can build a more humane web, for everyone.&lt;/p&gt;
&lt;h4 id=&#34;credits&#34;&gt;&lt;strong&gt;Credits&lt;/strong&gt;&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;With support from the &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Design Track: &lt;a href=&#34;https://dwebcamp.org/designers/&#34;&gt;https://dwebcamp.org/designers/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;About DWeb Camp: &lt;a href=&#34;https://www.youtube.com/watch?v=zx7Dduv0Hd4&#34;&gt;https://www.youtube.com/watch?v=zx7Dduv0Hd4&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>The Feira @ The Global Gathering 2023: Will You Join Us There?</title>
      <link>https://superbloom.design/learning/blog/the-feira-the-global-gathering-2023-will-you-join-us-there/</link>
      <pubDate>Wed, 13 Sep 2023 22:33:13 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/the-feira-the-global-gathering-2023-will-you-join-us-there/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_feira_2023_estoril_hu_290ce66af95f1237.jpg&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;h1 id=&#34;the-feira--the-global-gathering&#34;&gt;The Feira @ the Global Gathering&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;feira. [ˈfejra ] feminine noun. 1. fair. 2. (mercado) market. fazer a feira to go to market. feira livre market.&lt;/em&gt; &lt;/p&gt;
&lt;p&gt;The Feira @ the Global Gathering is a three day social and networking festival for digital rights defenders, hosted in an outdoor space in Estoril, Portugal on September 15th, 16th and 17th, 2023. &lt;/p&gt;
&lt;p&gt;The Feira is designed to provide digital rights defenders with a space to connect with others in the digital rights community for informal meetups and discussions with food, music, local vendors, project booths, glitter and more.  The event is 100% outdoor; plenty of sun for all!&lt;/p&gt;
&lt;p&gt;Superbloom team members: &lt;strong&gt;Jamie Tomasello&lt;/strong&gt; (Managing Director), and &lt;strong&gt;Eriol Fox&lt;/strong&gt;, (Senior Designer &amp;amp; Researcher), and Superbloom FSPs &lt;strong&gt;Matt Stempeck&lt;/strong&gt; (Civic Tech Field Guide), and &lt;strong&gt;Caroline Sinders&lt;/strong&gt; (Convocation) will be attending the event and look forward to seeing you there.&lt;/p&gt;
&lt;h4 id=&#34;who-is-participating&#34;&gt;Who is participating?&lt;/h4&gt;
&lt;p&gt;&lt;strong&gt;Jamie Tomasello&lt;/strong&gt; will be attending as a digital security practitioner and organizational resilience and health advocate. Jamie has built global multidisciplinary operations, security, compliance, customer success, and trust and safety teams at internet service providers, security companies, law firms, and nonprofits for over 20 years. She/he finds joy in empowering teams and contributing to a culture where psychological safety is prioritized.&lt;/p&gt;
&lt;p&gt;She/he will be co-hosting the Cyber FUD meetup on September 16th from 1400 - 1500, and she/he will be at the UX Clinic on the 16th and 17th of September. She/he will be attending sessions such as &amp;lsquo;From Rapid Response to Sustainable Protection: Responding to Digital Threats Through Funding&amp;rsquo; and &amp;lsquo;Advancing SAFETAG as a framework for the next generation of organizational security practitioners&amp;rsquo;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Eriol Fox&lt;/strong&gt; will be attending as a Human Rights Centered Design (HRCD) practitioner and advocate. Eriol has been a long standing member of the &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;HRCD community&lt;/a&gt; and helped organize remote and in person events centered around how designers and user experience specialists are involved in the design and build of technology used for human rights.&lt;/p&gt;
&lt;p&gt;They will be at the UX Clinic on the 16th and 17th of September and Eriol will be available to support projects and people on human rights centered design topics.&lt;/p&gt;
&lt;p&gt;They will be attending sessions such as ‘Experience of censored users’ ‘Mapping out collaboration and info sharing for anti-censorship work’ and ‘Sharing lesson on usability research / user needs’.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Matt Stempeck&lt;/strong&gt; will be demoing &lt;a href=&#34;https://civictech.guide/&#34;&gt;Civic Tech Field Guide&lt;/a&gt; at The Feira @ The Global Gathering product showcase on Friday 15th and Saturday 16th. Members of the digital rights community are invited to browse its extensive collection of &lt;a href=&#34;https://directory.civictech.guide/listing-category/digital-rights&#34;&gt;digital rights&lt;/a&gt;, &lt;a href=&#34;https://directory.civictech.guide/adjacent#:~:text=security%20and%20privacy-,Cybersecurity,-Digital%20rights&#34;&gt;cybersecurity&lt;/a&gt;, and &lt;a href=&#34;https://directory.civictech.guide/listing-category/ethical-tech-and-responsible-tech&#34;&gt;responsible tech&lt;/a&gt; resources, and add their own projects so that others can find them.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Caroline Sinders&lt;/strong&gt; is the co-founder of Convocation Research + Design and they will be attending as a human rights centered design, security, privacy, policy and OGBV expert. Caroline is an artist and researcher who has spent over a decade researching how technology harms marginalized groups. They are excited to see friends and attend IFF (now The Global Gathering) for the very first time! They aren&amp;rsquo;t sure what they will be seeing but are excited to float along and experience The Feira @ TGG. Catch Caroline at the UX Clinic on the 16th and 17th of September. Don&amp;rsquo;t be surprised if you see Caroline making zines, designing posters, or drinking copious amounts of coffee!&lt;/p&gt;
&lt;h4 id=&#34;where-can-you-find-us&#34;&gt;Where can you find us?&lt;/h4&gt;
&lt;h5 id=&#34;friday-15th&#34;&gt;Friday 15th&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;Digital Security Meetup 1400-1500 (Jamie)&lt;/li&gt;
&lt;li&gt;Researchers Meetup 1400-1500 (Jamie)&lt;/li&gt;
&lt;li&gt;Technologist Meetup 1400-1500 (Jamie)&lt;/li&gt;
&lt;li&gt;Project Showcase rounds 1500-1800 (Jamie)&lt;/li&gt;
&lt;li&gt;North America Digital Rights Meetup 1530-1630 (Jamie)&lt;/li&gt;
&lt;li&gt;Project Showcase: Civic Tech Field Guide - Booth 3 1600-1800 (Matt)&lt;/li&gt;
&lt;/ul&gt;
&lt;h5 id=&#34;saturday-16th&#34;&gt;Saturday 16th&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;Cyber FUD 1400-1500 (Jamie)&lt;/li&gt;
&lt;li&gt;Mapping Out Collaboration and Info Sharing for Anti-censorship Work 1400-1500 (Jamie)&lt;/li&gt;
&lt;li&gt;IT Service Providers for Nonprofits &amp;amp; Human Rights Organizations 1530-1630 (Jamie)&lt;/li&gt;
&lt;li&gt;Designers United + Accessibility Lab - UX and Comms Clinic + Digital Accessibility Awareness 1500-1600 (Eriol), 1600-1700 (Eriol, Caroline)&lt;/li&gt;
&lt;li&gt;Quiet — Table 1600-1800 (Jamie)&lt;/li&gt;
&lt;li&gt;Project Showcase: Civic Tech Field Guide - Booth 3 1600-1800 (Matt)&lt;/li&gt;
&lt;li&gt;Experience of Censored Users 1700-1800 (Jamie)&lt;/li&gt;
&lt;li&gt;Web Accessibility 1700-1800 (Jamie)&lt;/li&gt;
&lt;li&gt;Harassment Reporting 1700-1800 (Jamie)&lt;/li&gt;
&lt;/ul&gt;
&lt;h5 id=&#34;sunday-17th&#34;&gt;Sunday 17th&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;Designers United + Accessibility Lab - UX and Comms Clinic + Digital Accessibility Awareness 1400-1500 (Caroline), 1400-1530 (Jamie), 1500-1800 (Eriol)&lt;/li&gt;
&lt;li&gt;Sharing Lesson on Usability Research / User Needs 1400-1500 (Jamie)&lt;/li&gt;
&lt;li&gt;From Rapid Response to Sustainable Protection: Responding to Digital Threats Through Funding 1530-1630 (Jamie)&lt;/li&gt;
&lt;li&gt;Advancing SAFETAG as a Framework for the Next Generation of Organizational Security Practitioners 1700-1800 (Jamie)&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;credits&#34;&gt;Credits&lt;/h4&gt;
&lt;p&gt;Contributors: Jamie Tomasello, Eriol Fox, Matt Stempeck, Caroline Sinders.&lt;/p&gt;
&lt;p&gt;With support from &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/TeamCommunity&#34;&gt;@teamcommunity&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Personas Non Grata</title>
      <link>https://superbloom.design/learning/resources/persona-non-grata/</link>
      <pubDate>Wed, 19 Jul 2023 12:02:56 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/persona-non-grata/</guid>
      <description>&lt;p&gt;These ten &amp;ldquo;personas non grata&amp;rdquo; are people you probably don&amp;rsquo;t want in your product or service, but who are likely to find their way in anyway.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re on mobile, &lt;a href=&#34;http://designunderpressure.glideapp.io/&#34;&gt;the Personas Non Grata mobile app&lt;/a&gt; includes news stories that show what these characters have been up to lately.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why no &amp;ldquo;hacker&amp;rdquo;?&lt;/strong&gt; Because any of these personas non grata can use a digital attack.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why no &amp;ldquo;troll&amp;rdquo;?&lt;/strong&gt; Because we don&amp;rsquo;t care whether they are being &amp;ldquo;funny&amp;rdquo; or not, and that&amp;rsquo;s not the conversation we want to have.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why no &amp;ldquo;racist&amp;rdquo; or &amp;ldquo;homophobe&amp;rdquo; or &amp;ldquo;misogynist&amp;rdquo;?&lt;/strong&gt; The personas below cover actions, not motivations. Any of these may be motivated by racism, misogyny, homophobia, etc. That&amp;rsquo;s an important discussion, but a different one.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/personas-non-grata-4-_hu_8903f7e9c1ebbef3.png&#34; alt=&#34;Personas non grata images: cartoons of each of the 10 personas: Stalker, Abuser, Prankser, Naif, Truther, Surveillance, Opportunist, Fraudster, Swarm, and Terrorist&#34; width=&#34;740&#34; height=&#34;523&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/designunderpressure/&#34;&gt;Stalker&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Gathers information about another person&amp;rsquo;s activities and identity in order to blackmail or intimidate&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/designunderpressure/&#34;&gt;Abuser&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Uses psychological, physical, or financial power to prevent another person from exercising basic freedoms&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/designunderpressure/&#34;&gt;Prankster&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Disrupts or causes chaos for the sake of pleasure, power, or notoriety&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/designunderpressure/&#34;&gt;Naïf&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Doesn&amp;rsquo;t know how to properly behave in a certain context, and as a result ends up annoying or harming themselves or others&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/designunderpressure/&#34;&gt;Truther&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Denies scientific, legal, or social consensus, and plays on emotions and on the multiplying power of technology to tell the &amp;ldquo;real story&amp;rdquo;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/designunderpressure/&#34;&gt;Surveillance&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Tracks and traces people in a way that is against their interests, with the weight of government and law behind them&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/designunderpressure/&#34;&gt;Opportunist&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Finds loopholes and workarounds that allow them to use your product or service to make money&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/designunderpressure/&#34;&gt;Fraudster&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Uses misrepresentation – of themselves or of a product or service – to fool others&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/designunderpressure/&#34;&gt;Swarm&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Gathers a mass of individuals in order to coordinate an attack, multiply its effects, and decentralize its sources&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/designunderpressure/&#34;&gt;Terrorist&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Encourages, recruits for, and/or plans to carry out a violent, ideologically motivated attack&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Human Rights Centered Design: Respecting the Privacy and Security of Users While Still Sharing User Insights Among Practitioners</title>
      <link>https://superbloom.design/learning/blog/human-rights-centered-design-respecting-the-privacy-and-security-of-users-while-still-sharing-user-insights-among-practitioners/</link>
      <pubDate>Mon, 10 Jul 2023 20:40:43 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/human-rights-centered-design-respecting-the-privacy-and-security-of-users-while-still-sharing-user-insights-among-practitioners/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_hrcd_rightscon_2023_telephones_purple_hu_63f4ac9b63170157.png&#34; width=&#34;740&#34; height=&#34;554&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The organizations doing vital design and user research work in the Human Rights Technology space are good at sharing when they convene but not so much in asynchronous ways due to security and privacy concerns. &lt;/li&gt;
&lt;li&gt;With support from the Open Technology Fund Secure Usability and Accessibility Lab, we were able to gather UX Designers, User Researchers, Digital Security Trainers and OSS tool builders at the Human Rights Centered Design gathering at RightsCon 2023 to have critical discussions about the challenges and opportunities that sharing user insights could bring to how OSS tools for human rights needs are built in a ways that are more context sensitive and specific.&lt;/li&gt;
&lt;li&gt;Starting this discussion was a critical step in acknowledging that our informal, in-person ways of sharing are valuable, yet fall short when we are unable to meet. As we discussed we discovered the limitations and considerations needed when sharing information as well as prototyping ideas, such as sharing through trusted funder networks, to facilitate an information sharing process digitally.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Many designers, researchers and trainers have returned to attending events and conferences post pandemic. Events provide a critical space for connecting with the community, sharing insights, and having organic conversations that are often challenging to do online. Though in-person events also introduce many challenges, such as visa access, funding and the general safety and accessibility of attendees, it is often easier to navigate security challenges - such as recognising who is from which organization and in what capacity, which is more secure at events like RightsCon which has processes to verify and validate attendees - in order to support and enable the sharing of critical user insights, stories, and needs with one other. At the RightsCon 2023 &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;Human Rights Centered Design community&lt;/a&gt; event on Day 0, we discussed what we could do to better augment in-person information sharing that is safe, private, and which empowers human rights activist users and tool teams without compromising risky personal information.&lt;/p&gt;
&lt;p&gt;At Superbloom, some of our team have been focusing on this from the vantage point of improving practices for participant and researcher safety, with a particular focus on high-risk contexts. This conversation became front of mind for Eriol Fox, Senior Designer, after attending the &lt;a href=&#34;https://aspirationtech.org/events/devsummit&#34;&gt;Nonprofit Software Development Summit in November 2022&lt;/a&gt; where folks that work directly as front line support for human rights activists expressed a need to have their experiences and frustrations with human rights tools heard by the technical teams. They told stories not only of the ways in which tools did not meet user needs but the work-arounds they had developed in certain contexts as well as their frustrations with the methods that many tools have to provide feedback about their tools. One attendee expressed exhaustion at raising an issue in GitHub or filling out a Google form, given they have “no idea how long or where that goes”, not to mention needing to provide the same or similar information in multiple tools, and they wondered what could be done to limit the time spent communicating the same cases in many tools.&lt;/p&gt;
&lt;p&gt;Coincidentally, José Gutiérrez - as a newcomer to the Internet Freedom space and having done consultancy work for &lt;a href=&#34;https://okthanks.com/&#34;&gt;Okthanks&lt;/a&gt; and &lt;a href=&#34;https://internews.org/&#34;&gt;Internews&lt;/a&gt; - has seen the kinds of problems that researchers/designers, end-users, and tool makers have in the space. One of those being the apparent togetherness that communities have, but the lack of actual information sharing. Of the great opportunity our community has of materializing values such as openness, transparency, and collaboration on a new level.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;Human Rights Centered Design&lt;/a&gt; community, co-facilitated by &lt;a href=&#34;https://superbloom.design&#34;&gt;Superbloom&lt;/a&gt;, held space on Day 0 at &lt;a href=&#34;https://www.rightscon.org/&#34;&gt;RightsCon 2023&lt;/a&gt; for those practicing design functions in the Human Rights Technology space, as well as those interested in design practices in Human Rights work. The day was informal and centered around collaboration, conversation and problem solving discovery sessions.&lt;/p&gt;
&lt;p&gt;Eriol facilitated a session that explored questions around how and why we might share information about user needs, behaviors and contexts. Discussion groups were formed around the stakeholders involved: the tool teams, the designers/researchers and the end user human rights activists/defenders. The attendant collaborators of the session broke into discussion groups choosing the group they felt most affiliated with: Tools Teams, Designers or End Users.&lt;/p&gt;
&lt;p&gt;The groups were encouraged to discuss the topic of sharing user insights/research safely and securely but also offered a series of questions including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How might tool teams &amp;lsquo;receive’ user insights/research directly from users, digital security trainers, designers and intermediaries that are not based in technologies and processes which are comfortable for the information-givers rather than the tools?&lt;/li&gt;
&lt;li&gt;How can designers/researchers share user insights/research safely, securely and ethically with other designers/researchers and relevant tool teams these designers/researchers aren’t directly connected with? What might that sharing enable for the tool teams or designers/researchers?&lt;/li&gt;
&lt;li&gt;How might end users directly participate in the sharing of their own experiences and contexts with a clear understanding of what that information might be useful or used for? What guidance would end users need? What safety measures do they need across various contexts?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The session collaborators were encouraged to discuss ideas around the above prompts but also generate their own questions, boundaries, needs and challenges. The hypothesis being that if we are able to find ways users can remain safe while sharing their insights and context, this information might directly improve tools for human rights needs; by building new features that prioritize human rights’ user needs and broaden the potential tools able to be used in human rights circumstances.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_hrcd_rightscon_2023_telephones_hu_2a542f31f3e15eab.png&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;what-we-learned-from-the-discussions&#34;&gt;What we learned from the discussions&lt;/h3&gt;
&lt;p&gt;As stated above, the purpose of the discussions was not to come up with definitive answers, but spend the remainder of the time discussing the challenges, opportunities, concerns and details of how user insights/research can be shared amongst OSS tool teams. Here’s what each team (Tools, Design, End Users) discovered.&lt;/p&gt;
&lt;h4 id=&#34;design&#34;&gt;Design&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;The default would need heavy anonymising of information in case specific information is identifiable. We decided that the existence of a completely anonymised, redacted document was better than the information not appearing to exist at all. In this way. trusted networks of researchers and tools teams could still seek out more detailed information or less anonymised documents. &lt;/li&gt;
&lt;li&gt;Threat modeling for user insight could help designers/researchers better understand what needs heavy anonymisation and what doesn&amp;rsquo;t, and could be shared more openly.&lt;/li&gt;
&lt;li&gt;Designers/researchers and their organizations could still write reflections from more of a researcher point of view to protect the users’ contexts.&lt;/li&gt;
&lt;li&gt;Designers ultimately want to gain a better understanding of needs and context by sharing information across organizations and teams. We surmised that rarely would this information be used to make ‘final product decisions’ but this information could help the designers/researchers better form their own research into specific subjects and contexts.&lt;/li&gt;
&lt;li&gt;We briefly discussed what role funders play in the encouragement of cross-organisation information sharing, and whether those funders could act as the host of a trusted network of tool teams and researchers that could securely share via an online platform which is maintained and secured by that funder.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;tools&#34;&gt;Tools&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;If the user’s insight is specific to a tool or function, the tools and platforms need a secure way to capture this information in a way which doesn’t create a risk to that tool or platform&amp;rsquo;s own security.&lt;/li&gt;
&lt;li&gt;Ways of collecting feedback by using specific surveys or collection tools that are ‘destroyed’ could be an option for destructible feedback over a specific period of time or for a specific need.&lt;/li&gt;
&lt;li&gt;Some concerns were expressed about bad actors sending in information that actively stops or derails a tool&amp;rsquo;s progress, or compromises the integrity of the tool.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;end-users&#34;&gt;End users&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Users should remain the ultimate owners of their own data and understand how that has been used, by whom, and for what. This introduces a level of complexity on any ‘platforms’ that might facilitate the sharing of user insight, but allows for critical safety measures to be integrated and also awareness of what happens to user insight.&lt;/li&gt;
&lt;li&gt;The ability to join together with other similar end users would allow for a generalization of user insight that could better protect specific individuals.&lt;/li&gt;
&lt;li&gt;Relationships between end users, the designer/researcher and a particular tool were expressed as important contexts for user insight. How could this be shared (if at all?).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;moving-forward-with-secure-safe-user-insights-sharing&#34;&gt;Moving forward with secure, safe user insights sharing &lt;/h3&gt;
&lt;p&gt;At Superbloom we’re investigating how we can better facilitate feedback and research, with a focus on participant and research safety including what a platform that facilitates the sharing of user research and insights could look like. This platform might not only contain the research reports and insights, but also the secure methodologies and processes we use internally to keep at-risk individuals and communities from harm. To maintain safety, these processes and methods are often shared in private confidence with fellow designers and user researchers, but what would a privacy, security and human rights OSS tool space look like if we could all benefit from the insights and knowledge we learn across tools? As open source and openness advocates, we believe that sharing as much as we can, when we can, helps to maintain a healthy OSS ecosystem with safer tools to use for all.&lt;/p&gt;
&lt;h3 id=&#34;how-to-get-involved&#34;&gt;How to get involved? &lt;/h3&gt;
&lt;p&gt;We would recommend getting involved in the &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;HRCD community&lt;/a&gt;. Reach out to let us know how you would like to collaborate and progress this conversation.&lt;/p&gt;
&lt;p&gt;You can also check out the resources we co-created with &lt;a href=&#34;https://okthanks.com/&#34;&gt;Okthanks&lt;/a&gt; and &lt;a href=&#34;https://internews.org/&#34;&gt;Internews&lt;/a&gt; as part of the &lt;a href=&#34;https://usable.tools/&#34;&gt;USABLE&lt;/a&gt; and the &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/&#34;&gt;A Dev’s Guide to&amp;hellip; Adoptable Projects&lt;/a&gt; which focuses on design resources for security and privacy OSS tools teams.&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;Project Contributors: &lt;a href=&#34;https://twitter.com/EriolDoesDesign&#34;&gt;Eriol Fox&lt;/a&gt;, &lt;a href=&#34;https://josernitos.com/&#34;&gt;José Gutiérrez&lt;/a&gt;, The &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;Human Rights Centered Design&lt;/a&gt; community group.&lt;/p&gt;
&lt;p&gt;With support from &lt;a href=&#34;https://www.rightscon.org/&#34;&gt;RightsCon&lt;/a&gt; 2023, &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;, &lt;a href=&#34;https://okthanks.com/&#34;&gt;Okthanks&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Designing for Security</title>
      <link>https://superbloom.design/learning/resources/design-for-security/</link>
      <pubDate>Mon, 10 Jul 2023 14:52:14 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/design-for-security/</guid>
      <description>
      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/321474122?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;h3 id=&#34;resources&#34;&gt;Resources&lt;/h3&gt;
&lt;h4 id=&#34;principles-and-background&#34;&gt;Principles and Background&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/talking-across-divide&#34;&gt;Designing For More Than “It’s Secure”&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;learn-about-contexts&#34;&gt;Learn about contexts&lt;/h4&gt;
&lt;p&gt;Simply Secure’s &lt;a href=&#34;https://superbloom.design/learning/blog/personas&#34;&gt;persona template&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://medium.com/@gusandrews/user-personas-for-privacy-and-security-a8b35ae5a63b&#34;&gt;User Personas for Privacy and Security&lt;/a&gt; (Gus Andrews)&lt;/p&gt;
&lt;h4 id=&#34;mental-models&#34;&gt;Mental models&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://www.amazon.com/Mental-Models-Aligning-Strategy-Behavior-ebook/dp/B004VFUOQ0/&#34;&gt;Mental Models: Aligning Design Strategy with Human Behavior&lt;/a&gt; (Indi Young, 2008)&lt;br&gt;
&lt;a href=&#34;https://superbloom.design/learning/blog/whatsapp-update&#34;&gt;Tradeoffs In Seamlessness&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;with&lt;/strong&gt; Eileen Wagner, Casey Callendrello&lt;br&gt;
&lt;strong&gt;Produced by&lt;/strong&gt; Eileen Wagner, Ben Mergelsberg, Molly Wilson&lt;br&gt;
&lt;strong&gt;Directed by&lt;/strong&gt; Ben Mergelsberg&lt;br&gt;
&lt;strong&gt;Camera assistent:&lt;/strong&gt; Luciana Damiao&lt;br&gt;
&lt;strong&gt;Art:&lt;/strong&gt; Molly Wilson&lt;br&gt;
&lt;strong&gt;Music:&lt;/strong&gt; “Downtown” by bensound.com&lt;br&gt;
&lt;strong&gt;Filmed at&lt;/strong&gt; &lt;a href=&#34;https://www.stattlab.net/&#34;&gt;Stattlab&lt;/a&gt; and &lt;a href=&#34;http://wrangelfilm.com/&#34;&gt;Wrangelfilm&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Supported by&lt;/strong&gt; &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Special thanks to&lt;/strong&gt; Scout Brody, Maya Wagoner, Brett Gaylor&lt;br&gt;
&lt;strong&gt;Simply Secure CC-BY&lt;/strong&gt; (Georgia Bullen, Ame Elliott, Eileen Wagner, Molly Wilson)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Launching USER: Findings and Recommendations for Scientific and Research Open Source</title>
      <link>https://superbloom.design/learning/blog/launching-user-findings-and-recommendations-for-scientific-and-research-open-source/</link>
      <pubDate>Mon, 10 Jul 2023 08:43:45 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/launching-user-findings-and-recommendations-for-scientific-and-research-open-source/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_sloan_user3_hu_e30f5903aa027b2d.png&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Usable Software Ecosystem Research (USER) is a Sloan Foundation-supported research initiative that explores how open source scientific and research software (SROSS) teams understand, consider, and undertake usability and design opportunities in their projects. To read more about this project please check out &lt;a href=&#34;https://superbloom.design/learning/blog/introducing-user-usable-software-ecosystem-research/&#34;&gt;Blog #1&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/learning/blog/user-a-work-in-progress/&#34;&gt;Blog #2&lt;/a&gt;, our &lt;a href=&#34;https://user-project.superbloom.design/&#34;&gt;project website&lt;/a&gt;, and &lt;a href=&#34;https://github.com/simplysecure/USER_project&#34;&gt;open repo&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;wrapping-up-a-world-of-insights&#34;&gt;Wrapping up a world of insights&lt;/h3&gt;
&lt;p&gt;In the last 6+ months, our team completed 27 interviews, two community surveys and attended nearly 10 conferences and convenings related to the USER project and its line of inquiry. Since February, our six-person research team has collaborated virtually and in-person to analyze the huge amount of qualitative and quantitative data we’ve collected over the course of this project. USER illuminated countless insights, from a close look into how a diverse set of Science and Research Open Source Software (SROSS) projects and their contributors consider their users to how they approach the usability and broader design aspects of their projects, to the complex and often contradictory ways in which they understand and build SROSS tools.&lt;/p&gt;
&lt;p&gt;Our complete findings can be found on our newly published &lt;a href=&#34;https://user-project.superbloom.design/&#34;&gt;project website&lt;/a&gt; and in our &lt;a href=&#34;https://github.com/simplysecure/USER_project&#34;&gt;public repository&lt;/a&gt; on GitHub. We’ve selected excerpts from a few key findings and recommendations to give a taste of what this research surfaced:&lt;/p&gt;
&lt;h3 id=&#34;finding-sross-projects-and-the-designers-working-on-them-are-engaging-in-deeply-cross-disciplinary-work-that-requires-the-cultivation-of-language-and-mutual-respect-amongst-collaborators&#34;&gt;Finding: SROSS projects and the designers working on them are engaging in deeply cross-disciplinary work that requires the cultivation of language and mutual respect amongst collaborators&lt;/h3&gt;
&lt;p&gt;If you’re curious to learn more, read our Executive Summary and complete in-depth findings on our &lt;a href=&#34;https://user-project.superbloom.design/&#34;&gt;project website&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;SROSS development often needs cross-disciplinary work. This can be challenging as norms and common language need to be negotiated between different work cultures. In SROSS projects, there is often a disciplinary exchange between programmers and scientists. Add designers, and there is a third ‘language’ and working style. Effective cross-disciplinary collaboration ranges in strategy and process. Some projects prioritize mutual understanding and a state of continuous knowledge transfer between disciplines, while others take a more synergistic approach where each expert is able to excel in their domain without the burden of needing to know the ‘other’ discipline well. Regardless of the approach, mutual respect, communication and knowing the value of each role&amp;rsquo;s contribution is vital to the success of design and usability in SROSS.&lt;/p&gt;
&lt;h3 id=&#34;finding-implementation-of-design-practices-is-aspirational-but-inconsistent-across-projects&#34;&gt;Finding: Implementation of design practices is aspirational but inconsistent across projects&lt;/h3&gt;
&lt;p&gt;Whether projects establish design and usability practices depends on the perceived utility of design work; what non-designers define as design, usability, and accessibility; and the ease of implementing design changes. If design work is seen as time intensive, disruptive, requiring code overhaul, and/or frivolous, the implementation of design practices is unlikely. Even when design and usability are valued, many see it as optional, incidental, or aspirational. In this case, design implementation is only ‘worth it’ when it is clearly linked to the expansion of a user base. We observed this most potently in projects with diverse users. SROSS projects express that they want to improve tools and services. Dedicated design and usability work could help doing this, but SROSS projects do not often realize this. Good design and usability practices empower users, make tools easier to use, and require less immediate support from maintainers, which ultimately helps fulfil the purpose of research and scientific discovery.&lt;/p&gt;
&lt;h3 id=&#34;based-on-our-findings-we-developed-recommendations-for-sross-projects&#34;&gt;Based on our findings, we developed recommendations for SROSS projects&lt;/h3&gt;
&lt;p&gt;Here are three of our recommendations. To read all of our recommendations, see our &lt;a href=&#34;https://user-project.superbloom.design/&#34;&gt;project website&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Promote design and usability as a practice that cuts labor and time for maintainers.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Usability improvements can reduce the time that maintainers, developers and community contributors spend writing step-by-step user guides and answering customer support requests when users are having difficulties with the tool.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Make the entry points to contribution beyond code clear and inclusive.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Clear contribution paths and entry points allow potential contributors to understand where they are needed and how they can be most useful.&lt;/p&gt;
&lt;p&gt;Inclusivity increases contributions, because designers and other non-code contributors will see their work as valued and prioritized.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Develop resources, community spaces, shared channels, and information repositories for SROSS design.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If OSS/SROSS designers share experiences and learn from each other, they can help shape best practices and reduce barriers for designers new to the ecosystem. Also, including designers in OSS/SROSS maintainer channels, and vice-versa, will help increase designer/developer collaboration and provide guidance to projects without a designer on the team. Institutions can support this by promoting reuse of science and research and usability.&lt;/p&gt;
&lt;p&gt;*﻿&lt;/p&gt;
&lt;p&gt;In closing, we invite you to read our Executive Summary and complete in-depth findings on our &lt;a href=&#34;https://user-project.superbloom.design/&#34;&gt;project website&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;Project Contributors: &lt;a href=&#34;https://twitter.com/EriolDoesDesign&#34;&gt;Eriol Fox&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/simulo&#34;&gt;Jan Dittrich&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/kirakirawes&#34;&gt;Ngọc Triệu&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/abhi1203&#34;&gt;Abhishek Sharma&lt;/a&gt;, &lt;a href=&#34;https://t.co/OUjwQhySyQ&#34;&gt;Katie Wilson&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/smklibrarian&#34;&gt;Susan Kennedy&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/georgiamoon&#34;&gt;Georgia Bullen&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;With support from the &lt;a href=&#34;https://sloan.org/&#34;&gt;Alfred P. Sloan Foundation&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>DWeb Camp</title>
      <link>https://superbloom.design/community/events/dweb-camp/</link>
      <pubDate>Wed, 21 Jun 2023 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/events/dweb-camp/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Meet Jasmine McNealy, Superbloom Board Member</title>
      <link>https://superbloom.design/learning/blog/meet-jasmine-mcnealy-superbloom-board-member/</link>
      <pubDate>Wed, 14 Jun 2023 21:53:59 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/meet-jasmine-mcnealy-superbloom-board-member/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_jasmine_mcnealy_hu_3a6692b244952949.png&#34; width=&#34;740&#34; height=&#34;414&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;tell-us-a-little-bit-about-yourself-and-what-you-do-professionally&#34;&gt;Tell us a little bit about yourself and what you do professionally.&lt;/h4&gt;
&lt;blockquote&gt;
&lt;p&gt;Hello! I am an associate professor at a university in the southeastern US and the founder and principal of a research and strategy consultancy called The Alveary LLC. I am also an attorney and, I suppose, an overall nerd.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id=&#34;how-did-you-end-up-on-this-path&#34;&gt;How did you end up on this path?&lt;/h4&gt;
&lt;blockquote&gt;
&lt;p&gt;To tell the truth, I wandered into this path. It is not anything I could have imagined.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id=&#34;what-keeps-you-motivated-to-do-this-important-work&#34;&gt;What keeps you motivated to do this important work?&lt;/h4&gt;
&lt;blockquote&gt;
&lt;p&gt;I think there are opportunities to change how people are forced to live, how organizations do business, and to reduce harm. These are the things that are purposeful and important to me.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id=&#34;when-did-you-first-hear-of-superbloom&#34;&gt;When did you first hear of Superbloom? &lt;/h4&gt;
&lt;blockquote&gt;
&lt;p&gt;In 2018/2019 I was doing a fellowship based in NYC and in Boston. I was introduced to Superbloom folks and affiliates through connections with Data &amp;amp; Society, Civic Hall, and the Kennedy School. &lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id=&#34;why-did-you-decide-to-join-our-board&#34;&gt;Why did you decide to join our Board?&lt;/h4&gt;
&lt;blockquote&gt;
&lt;p&gt;I think Superbloom has an important mission and set of values. I think the work that the organization does is important and being a Board member allows me to take part in this very important work.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id=&#34;how-do-you-see-your-experience-and-expertise-supporting-superbloom-as-a-member-of-the-board&#34;&gt;How do you see your experience and expertise supporting Superbloom as a member of the Board? &lt;/h4&gt;
&lt;blockquote&gt;
&lt;p&gt;I think that my experience and expertise will support the Board in a broad range of issues and considerations. I’m happy to serve in any of the areas necessary.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id=&#34;why-is-it-important-to-change-who-technology-serves-how-do-you-think-superbloom-is-positioned-to-support-that-vision&#34;&gt;Why is it important to change who technology serves? How do you think Superbloom is positioned to support that vision?&lt;/h4&gt;
&lt;blockquote&gt;
&lt;p&gt;It is important to change who technology serves because the use and implementation of technology can cause both short- and long-term impacts. It has implications for how people live their lives. Superbloom is positioned to assist organizations in critically considering how they are deploying and creating technology that impacts people, and hopefully, persuading organizations to make the important changes to their values and systems to mitigate harm.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id=&#34;what-is-something-thats-exciting-you-at-the-moment&#34;&gt;What is something that’s exciting you at the moment?&lt;/h4&gt;
&lt;blockquote&gt;
&lt;p&gt;I’m getting into some research that I think is important and can snowball into other things.&lt;/p&gt;
&lt;/blockquote&gt;
</description>
    </item>
    
    <item>
      <title>Together Against Deceptive Design</title>
      <link>https://superbloom.design/learning/blog/together-against-deceptive-design/</link>
      <pubDate>Tue, 06 Jun 2023 16:26:45 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/together-against-deceptive-design/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_deceptive_design_header_hu_a230aadc5c111fca.png&#34; width=&#34;740&#34; height=&#34;415&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Deceptive design, sometimes referred to as &lt;a href=&#34;https://www.deceptive.design/about-us&#34;&gt;Dark Patterns&lt;/a&gt;, is not just an inconvenience, and is far more than a consumer protection problem. Deceptive design is a human rights issue that disproportionately harms marginalized people with fewer resources.  Beyond financial loss, deceptive design limits consent and autonomy online, invades privacy, and causes negative impacts on mental health. &lt;/p&gt;
&lt;p&gt;In partnership with the &lt;a href=&#34;https://webfoundation.org/&#34;&gt;World Wide Web Foundation&lt;/a&gt; and &lt;a href=&#34;https://3x3.co/&#34;&gt;3x3&lt;/a&gt;, we facilitated a series of workshops with global participants to explore ways of combating deceptive design and promoting trustworthy products and services instead.&lt;/p&gt;
&lt;p&gt;We are pleased to announce the result of this work: &lt;a href=&#34;https://techlab.webfoundation.org/deceptive-design/overview&#34;&gt;Deceptive Design: Moving Towards Trusted Design Patterns&lt;/a&gt; which outlines the challenges - including the global harms - and opportunities to combat deceptive design for technical and design teams, policy makers, regulators, academics, activists, and journalists.  The recommendations are organized into &lt;a href=&#34;https://techlab.webfoundation.org/deceptive-design/strategies-for-change&#34;&gt;five key opportunity&lt;/a&gt; areas to leverage as we move from the unacceptable status quo of exploitation and manipulation towards a better future of trusted design patterns.&lt;/p&gt;
&lt;h3 id=&#34;a-global-problem-with-patchwork-solutions&#34;&gt;A Global Problem With Patchwork Solutions&lt;/h3&gt;
&lt;p&gt;In this work, listening to both harms from, and successes in, combatting deceptive design from experts around the world, we heard how different cultural expectations and regulatory contexts make a one-size-fits all approach unrealistic. Adedolapo Evelyn Adegoroye and Victoria Adaramola from &lt;a href=&#34;https://techhiveadvisory.africa/&#34;&gt;TechHive Advisory&lt;/a&gt; highlighted regulatory fragmentations:&lt;/p&gt;
&lt;p&gt;“Many digital platforms either operate or aspire to operate across countries and continents. Thus, fragmented [regulatory] frameworks make it more difficult and less enticing for tech companies who operate cross-country to comply. The regulator should develop operational guidelines, codes of ethics, and best practices for UI/UX designers, tech associations, software engineers, digital marketers, and tech companies.” – in &lt;a href=&#34;https://webfoundation.org/2022/10/tackling-deceptive-design-on-the-african-continent/&#34;&gt;Tackling Deceptive Design Across the African Continent&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;We did learn about opportunities to translate positive changes in one region and apply them to other regions. For example, the European Union is hard at work on policies to combat deceptive design: the &lt;a href=&#34;https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32022R2065&amp;amp;from=EN&#34;&gt;Digital Services Act (DSA)&lt;/a&gt; and the Digital Markets Act, both approved by the European Parliament in July 2022, have the aim of ensuring consumer rights online. As Dr. Jen King &lt;a href=&#34;https://techpolicy.press/do-the-dsa-and-dma-have-what-it-takes-to-take-on-dark-patterns/&#34;&gt;writes in Tech Policy Press&lt;/a&gt;: “In terms of fighting manipulative algorithms, the DSA goes where so far, U.S. regulators have yet to tread.” &lt;/p&gt;
&lt;p&gt;Superbloom acted as a conduit and amplifier of these emerging opportunities to adapt practices that work well in one region to apply to other regions in order to protect more people from the harms of deceptive design.&lt;/p&gt;
&lt;h3 id=&#34;how-do-we-combat-deceptive-design&#34;&gt;How Do We Combat Deceptive Design?&lt;/h3&gt;
&lt;p&gt;In collaboration with our workshop participants, our partners at 3x3 and at the World Wide Web Foundation, we developed &lt;a href=&#34;https://techlab.webfoundation.org/deceptive-design/strategies-for-change&#34;&gt;strategies for change&lt;/a&gt; to shift the tech ecosystem away from deceptive design and towards trusted design. These opportunities were developed collaboratively, as a result of hours of discussion with 117 stakeholders from 31 countries. Workshop participants included regulators, researchers, governmental officials, activists and advocates, professional association leaders, employees at tech companies, and academics. We are pleased to share this synthesis with participants and the greater community.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_deceptive_design_outputs_hu_96621641bb408c6f.png&#34; width=&#34;740&#34; height=&#34;266&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;1-build-a-coalition-to-mobilize-change&#34;&gt;1. Build A Coalition To Mobilize Change&lt;/h4&gt;
&lt;p&gt;Our first opportunity area for combatting deceptive design is &lt;a href=&#34;https://techlab.webfoundation.org/strategies-for-change/coalition&#34;&gt;coalition building&lt;/a&gt;. During the course of our workshops, it became clear that the space we were holding and facilitating was in itself a valuable asset in the fight against manipulative design patterns. During our workshops, we heard from participants that sharing challenges and best practices across regions is beneficial, and there is an appetite for doing even more. We propose formalizing this format into a coalition of stakeholders with diverse backgrounds to: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Develop best practices and policy guidance to pave the way for implementation at the national level&lt;/li&gt;
&lt;li&gt;Advocate for the application of &lt;a href=&#34;https://techlab.webfoundation.org/strategies-for-change/trusted-design-norms&#34;&gt;Trusted Design Norms&lt;/a&gt; into a range of regulatory and design frameworks&lt;/li&gt;
&lt;li&gt;Develop an open process for validating and evolving the Trusted Design Norms&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For additional details, including a coalition-building road map, please refer to the &lt;a href=&#34;https://techlab.webfoundation.org/strategies-for-change/coalition&#34;&gt;TPDL website&lt;/a&gt;. We welcome your participation, as an individual or as an organization; message us to &lt;a href=&#34;mailto:trusted-design@superbloom.design&#34;&gt;join the coalition&lt;/a&gt; and receive updates on our process and convenings.&lt;/p&gt;
&lt;h4 id=&#34;2-create-a-crowdsourced-reporting-tool&#34;&gt;2. Create A Crowdsourced Reporting Tool&lt;/h4&gt;
&lt;p&gt;Building on &lt;a href=&#34;https://darkpatternstipline.org/&#34;&gt;The Dark Patterns Tipline&lt;/a&gt;, we see an opportunity to gather information about deceptive design for several purposes. Documenting deceptive design patterns is a necessary step towards building awareness, giving activists, journalists, and researchers the real-world examples they need to illuminate the issue and its scope. A reporting tool can communicate a common, understandable understanding of the impact of deceptive design. The collected reports can help regulators understand the problem and potentially become evidence for strategic litigation. Toward that end, the TPDL Deceptive Design website explains opportunities for &lt;a href=&#34;https://techlab.webfoundation.org/strategies-for-change/crowdsourced-reporting-tool&#34;&gt;regulator and researcher workflows&lt;/a&gt; to complement the experience of reporting harms by web users.&lt;/p&gt;
&lt;h4 id=&#34;3-launch-a-storytelling-campaign&#34;&gt;3. Launch A Storytelling Campaign&lt;/h4&gt;
&lt;p&gt;The harms of deceptive design are global, and impact young people in resource-constrained contexts far from offices where policies are crafted. An advocacy campaign fueled by youth activism tools, such as video shorts can inspire culture change. The Pravana Institute’s &lt;a href=&#34;https://www.design.pranavainstitute.com/&#34;&gt;Design Beyond Deception&lt;/a&gt; work is one exciting example. Our workshop participants were particularly interested in centering neurodiversity and building a culture of care. We heard opportunities for global voices with regional representation to curate and surface content. Ideas for &lt;a href=&#34;https://techlab.webfoundation.org/strategies-for-change/storytelling-campaign&#34;&gt;structuring a collection of global stories&lt;/a&gt; is available on the website.&lt;/p&gt;
&lt;h4 id=&#34;4-develop--adopt-trusted-design-norms&#34;&gt;4. Develop &amp;amp; Adopt Trusted Design Norms&lt;/h4&gt;
&lt;p&gt;Synthesizing the discussions in the workshops, we produced a prototype set of resources documenting trusted design norms and best practices. A crowd-sourced reporting tool building on the Dark Patterns Tip Line describes what not to do, but what does trusted design look like? These resources bridge that gap by giving concrete information about what to do instead.&lt;/p&gt;
&lt;p&gt;In the &lt;a href=&#34;https://techlab.webfoundation.org/strategies-for-change/trusted-design-norms&#34;&gt;Trusted Design Norms&lt;/a&gt; section of the website there is an embedded slide presentation covering&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Principles for Trusted Design&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Build for at-risk communities first, such as youth, seniors, economically disadvantaged people, those outside the Global North&lt;/li&gt;
&lt;li&gt;Deliver user agency and control&lt;/li&gt;
&lt;li&gt;Free people from cognitive burdens&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Examples found in practice to emulate&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Discussion guides and organizational assessment questions&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_deceptive_design_ma_quilts_hu_25630aef8a62ca18.png&#34; width=&#34;740&#34; height=&#34;421&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Image: the principle of equitability found in practice on the website for &lt;a href=&#34;https://www.maquilts.com/&#34;&gt;MA Quilts&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In addition to these guidelines, we synthesized recommendations from workshop contributors and a task force led by Sage Cheng of Access Now into a database of recommendations sortable by teams/discipline (e.g. user research, visual design), product areas (e.g. onboarding, errors), and guidelines (e.g. equitable, transparent).&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_deceptive_design_airtable_57_recommendations_hu_f800d8096ed40406.png&#34; width=&#34;740&#34; height=&#34;512&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Image: Please explore the collection of &lt;a href=&#34;https://airtable.com/app185ywjVuL0fFpr/pagja2Q0EUvWxAciU&#34;&gt;57 recommendations&lt;/a&gt; for trusted design in Airtable.&lt;/em&gt;&lt;/p&gt;
&lt;h4 id=&#34;5-develop-tools-for-evaluation--accreditation&#34;&gt;5. Develop Tools For Evaluation &amp;amp; Accreditation&lt;/h4&gt;
&lt;p&gt;Bringing together a global group of stakeholders in our workshops underscored the need for an independent body to coordinate standards for trusted design. We also see opportunities to build accreditation programs to support the move towards trustworthy design patterns.. It is imperative that this framework and accreditation program be created with meaningful inclusion of global majority stakeholders. For more details about how this might work, including self-assessment questions for developers, regulators, and researchers, please refer to the &lt;a href=&#34;https://techlab.webfoundation.org/strategies-for-change/evaluation-accreditation&#34;&gt;TPDL Deceptive Design website&lt;/a&gt;. &lt;/p&gt;
&lt;h3 id=&#34;get-involved&#34;&gt;Get Involved&lt;/h3&gt;
&lt;p&gt;We need your help to build a trusted, rights-respecting online world as we pilot a multi-stakeholder working group to combat deceptive design and invite individuals and organizations to join the growing network of activists, policymakers, and technologists advancing trustworthy design.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;mailto:trusted-design@superbloom.design&#34;&gt;Contact the team to get involved.&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;Our thanks to the World Wide Web Foundation, particularly to Kaushalya Gupta and Katherine Townsend for their leadership; to Sage Cheng from Access Now; to Megan Marini and Janice Dean from 3x3; and to all our &lt;a href=&#34;https://techlab.webfoundation.org/deceptive-design/acknowledgements&#34;&gt;participants and collaborators&lt;/a&gt;. Without them, this work would not be possible.&lt;/p&gt;
&lt;p&gt;Header image screenshots created with Midjourney.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Where Can You Find Us At RightsCon 2023?</title>
      <link>https://superbloom.design/learning/blog/where-can-you-find-us-at-rightscon-2023/</link>
      <pubDate>Mon, 05 Jun 2023 13:45:10 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/where-can-you-find-us-at-rightscon-2023/</guid>
      <description>&lt;p&gt;​​The world’s leading summit on human rights in the digital age is back. After three years online, the 12th edition of RightsCon is both live in San José, Costa Rica, and online via the RightsCon platform from Monday, June 5 to Thursday, June 8 2023.&lt;/p&gt;
&lt;p&gt;RightsCon offers a platform for thousands of participants around the world to convene, connect, and contribute to a shared agenda for the future of human rights and technology. Join leaders, activists, technologists, policymakers, journalists, philanthropists, researchers, and artists to explore opportunities to advance human rights in the digital age.&lt;/p&gt;
&lt;p&gt;Those excited to be traveling to San José include: Georgia Bullen (Executive Director), Eriol Fox (Senior Product Manager and Designer), and Caroline Sinders (Convocation) and we hope to see and/or meet you at one of our events or please say hello.  If you’d like to meet us there please reach out via email to &lt;a href=&#34;mailto:rightscon2023@superbloom.design&#34;&gt;rightscon2023@superbloom.design&lt;/a&gt;, and we’ve provided our session booking links below.&lt;/p&gt;
&lt;h3 id=&#34;human-rights-centered-design-gathering-satellite-event&#34;&gt;Human Rights Centered Design Gathering Satellite Event&lt;/h3&gt;
&lt;h4 id=&#34;june-5-2023--9-3pm-cst-gmt-6&#34;&gt;June 5, 2023 | 9-3pm CST (GMT-6)&lt;/h4&gt;
&lt;h4 id=&#34;hybrid&#34;&gt;Hybrid&lt;/h4&gt;
&lt;p&gt;Following the last in-person convening of the Human Rights-Centered Design Community at RightsCon 2019, this event aims at bringing together designers, user researchers, technologist, digital security trainers and policy experts to reflect on the progress in the areas at the intersection between human rights and tech product design. We are inviting community members and first-timers to join in-depth working groups to discuss new trends and developments in accessibility, privacy, security and other critical factors that can decide whether a digital product can protect, rather than undermine human rights. This event requires additional registration: &lt;a href=&#34;https://pretix.eu/hrcd/rightscon2023/&#34;&gt;https://pretix.eu/hrcd/rightscon2023/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_rightscon_2023_succulent_hu_c4e3c1d8a30ad77f.jpg&#34; width=&#34;740&#34; height=&#34;492&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;dismantling-deceptive-design-practices-a-human-rights-centered-approach&#34;&gt;Dismantling deceptive design practices: a human rights-centered approach&lt;/h3&gt;
&lt;h4 id=&#34;june-6-2023--430-530pm-cst-gmt-6&#34;&gt;June 6, 2023 | 4.30-5.30pm CST (GMT-6)&lt;/h4&gt;
&lt;h4 id=&#34;hybrid-1&#34;&gt;Hybrid&lt;/h4&gt;
&lt;h4 id=&#34;georgia-bullen-superbloom-dr-jen-king-stanford-university-becca-ricks-mozilla-willmary-escoto-access-now-hayley-tsukayama-electronic-frontier-foundation-sage-cheng-access-now&#34;&gt;Georgia Bullen (Superbloom), Dr Jen King (Stanford University), Becca Ricks (Mozilla), Willmary Escoto (Access Now), Hayley Tsukayama (Electronic Frontier Foundation), Sage Cheng (Access Now)&lt;/h4&gt;
&lt;p&gt;Deceptive designs, also known as dark patterns, manipulate people on the web into making choices against their own self-interest. Deceptive design is a human rights issue because these designs limit consent and autonomy online, particularly for vulnerable populations. Harms include financial loss, invasions of privacy, and negative impacts on mental health. Our human rights-centered design approach centers on lived experiences, and our presenters will share case studies and narratives for dismantling deceptive design. This multi-stakeholder conversation explores successes to replicate and pitfalls to avoid, looking not only at tech platforms and products but also at organizational design challenges and how companies can transform themselves to dismantle deceptive design and build trust. Using our best practices and facilitation tooling for equitable participation, our reliance on multiple input methods includes real-time notes to support neurodivergent people.  &lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/rightscon-costa-rica-2023/events/dismantling-deceptive-design-practices-a-human-rights-centered-approach-cdtYB1aVoUXSojLLimPbgj&#34;&gt;Add to your sessions&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;transparency-beyond-social-media-a-practical-exploration-of-recommendation-algorithms&#34;&gt;Transparency beyond social media: a practical exploration of recommendation algorithms&lt;/h3&gt;
&lt;h4 id=&#34;june-7-2023--1015-1115am-cst-gmt-6&#34;&gt;June 7, 2023 | 10.15-11.15am CST (GMT-6)&lt;/h4&gt;
&lt;h4 id=&#34;online&#34;&gt;Online&lt;/h4&gt;
&lt;h4 id=&#34;caroline-sinders-convocation-michal-luria-center-for-democracy--technology-becca-ricks-mozilla&#34;&gt;Caroline Sinders (Convocation), Michal Luria (Center for Democracy &amp;amp; Technology), Becca Ricks (Mozilla)&lt;/h4&gt;
&lt;p&gt;Social media platforms have been under the spotlight with demands for more transparency about how their recommendation algorithms work. Yet many other, non-social media platforms also use recommendation algorithms, and have just as significant of an impact on people’s lives in domains such as shopping, media, travel, transportation and more. In this workshop, we propose to include participants in considering what companies should share with users about how their recommendation algorithms work. In a hands-on exploration, participants will delve into what key non-social media platforms are currently sharing, while highlighting significant gaps in knowledge that companies need to address.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/rightscon-costa-rica-2023/events/transparency-beyond-social-media-a-practical-exploration-of-recommendation-algorithms-8KSQ5RVfL58PEdTHP9FcPX&#34;&gt;Add to your sessions&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_rightscon_2023_toucan-costa-rica_hu_5bb32c4eb886df28.jpg&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;tools-for-enhancing-personal-protection-on-encrypted-messaging-platforms-with-secure-and-trusted-design&#34;&gt;Tools for enhancing personal protection on encrypted messaging platforms with secure and trusted design&lt;/h3&gt;
&lt;h4 id=&#34;june-7-2023--2-3pm-cst-gmt-6&#34;&gt;June 7, 2023 | 2-3pm CST (GMT-6)&lt;/h4&gt;
&lt;h4 id=&#34;in-person&#34;&gt;In person&lt;/h4&gt;
&lt;h4 id=&#34;caroline-sinders-convocation-justin-hendrix-tech-policy-press-nathalie-maréchal-center-for-democracy--technology&#34;&gt;Caroline Sinders (Convocation), Justin Hendrix (Tech Policy Press), Nathalie Maréchal (Center for Democracy &amp;amp; Technology)&lt;/h4&gt;
&lt;p&gt;The tension between protecting communities, at risk groups and general personal communication through encrypted services, and concerns about harmful content that can only be moderated to a limited degree is an ongoing debate. Several recent research efforts have recommended addressing this tension by providing communities with more agency, including providing tools to improve user control, filtering abilities, and reporting experiences. In this hands-on design workshop we will map solutions and tools that either currently exist, or that platforms can create for users in the near future, while highlighting some of their possible advantages and disadvantages of each tool.&lt;/p&gt;
&lt;p&gt;In forming this mapping of possibilities, we will draw on recent findings from two research projects: a Tech Policy Press and Convocation Research + Design report on barriers to secure and trusted messaging, and a CDT research study conducted with teenagers and young adults in the US to capture their perspectives on digital message interactions they find concerning. We will discuss ways of addressing a range of “unwanted” content categories we have identified in our research, brainstorm practical tools/tooling that messaging platforms could provide to young audiences, and community/individual best practices around ‘safer’ messaging. We will also consider how these might or might not break encryption.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/rightscon-costa-rica-2023/events/tools-for-enhancing-personal-protection-on-encrypted-messaging-platforms-with-secure-and-trusted-design-uM6RPmAM7kGsQ2agX3KmVN&#34;&gt;Add to your sessions&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;a-clear-and-present-use-case-for-peer-2-peer&#34;&gt;A clear and present use case for peer-2-peer&lt;/h3&gt;
&lt;h4 id=&#34;june-7-2023--2-3pm-cst-gmt-6-1&#34;&gt;June 7, 2023 | 2-3pm CST (GMT-6)&lt;/h4&gt;
&lt;h4 id=&#34;in-person-1&#34;&gt;In person&lt;/h4&gt;
&lt;h4 id=&#34;eriol-fox-superbloom-marcel-oomens-zamaneh-media-alex-meduza-sudeshna-chanda-nemo-network-of-exiled-media-outlets-nemo-jenny-ryan-equalitie&#34;&gt;Eriol Fox (Superbloom), Marcel Oomens (Zamaneh Media), Alex (Meduza), Sudeshna Chanda (NEMO Network of Exiled Media Outlets (NEMO), Jenny Ryan (eQualitie)&lt;/h4&gt;
&lt;p&gt;The #KeepItOn Coalition reported 931 internet shutdowns across 74 countries between 2016 and 2021. Authorities have learnt that shutdowns are an effective tool at shutting down dissent. The activist community looks at peer-2-peer technology to keep dissenting voices heard during a shutdown. But peer-2-peer communication, not reliant on internet connectivity, is a technology without a clear and present use case. Existing peer-2-peer tools are often interesting technology showcases with very small user bases. Adding peer-2-peer features to commercial apps and platforms adds little business value, so we need to look to the donor and (online and digital rights) activist communities to take a user-centered approach to designing and developing peer-2-peer tools. For example, Zamaneh Media, and online, Persian news medium, is investigating how peer-2-peer can help its newsroom maintain access to sources and reach audiences during a shutdown.&lt;/p&gt;
&lt;p&gt;We need a clear and present use case for peer-2-peer. In this workshop, we wish to crowdsource the &amp;ldquo;Peer-2-Peer Design Manifesto&amp;rdquo;: 1. Which (internet) functions benefit the most from peer-2-peer connectivity during a shutdown? 2. Which websites and applications are easily extensible with peer-2-peer connectivity? 3. How do peer-2-peer features best support the users&amp;rsquo; needs from these applications? 4. How to design features that provide a seamless, user-friendly peer-2-peer experience? Join this workshop. Bring your needs, your ideas and your experiences with peer-2-peer and distributed applications. What has worked for you previously and what do you need from your tools going forward? Come and leave your mark on your future peer-2-peer tools!  &lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/rightscon-costa-rica-2023/events/a-clear-and-present-use-case-for-peer-2-peer-tyRzevmyPmMbg7NsC68Esd&#34;&gt;Add to your sessions&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_rightscon_2023_iguana_hu_cd178c41e1d691e.jpg&#34; width=&#34;740&#34; height=&#34;494&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;the-devils-in-the-details-adversarial-design-in-action&#34;&gt;The devil&amp;rsquo;s in the details: adversarial design in action&lt;/h3&gt;
&lt;h4 id=&#34;june-7-2023--430-530pm-cst-gmt-6&#34;&gt;June 7, 2023 | 4.30-5.30pm CST (GMT-6)&lt;/h4&gt;
&lt;h4 id=&#34;in-person-2&#34;&gt;In person&lt;/h4&gt;
&lt;h4 id=&#34;eriol-fox-superbloom-ashley-fowler-internews-nick-merrill-uc-berkeley-center-for-long-term-cybersecurity-cltc-helen-nyinakiiza-digital-security-trainer-jon-camfield-meta&#34;&gt;Eriol Fox (Superbloom), Ashley Fowler (Internews), Nick Merrill (UC Berkeley Center for Long-Term Cybersecurity (CLTC), Helen Nyinakiiza (Digital Security Trainer), Jon Camfield (Meta)&lt;/h4&gt;
&lt;p&gt;Nuanced discussions on these threat actors, their goals and tactics are critical, but with the potential to re-traumatize victims or send defense, product, and policy teams into rabbit holes, the specific details can be counterproductive and derail holistic, risk-leveled approaches. This workshop explores the use of adversarial personas as a way that different stakeholders (the civil society, human rights defenders, the research community, and social media platforms) can work together to prevent, detect, and respond to advanced threat actors. Workshop leaders from academia, trust and safety efforts, design firms, and community digital safety trainers will present, share, and discuss their use of adversarial personas to address product design challenges as well as engage on traumatic experiences caused by powerful and persistent threat actors.&lt;/p&gt;
&lt;p&gt;This workshop will also open up a discussion on complex, non-adversarial personas. This is to ensure we consider journalists, human rights defenders, and other important users who use overlapping or similar tactics as some adversaries, but for vastly different reasons. These users are working to maximize their own security and the security of their communities, but may be using anonymizing tools, accounts which appear fake, constantly logging in from “new” devices, using burner mobile numbers, and so on. While often signals of adversaries, these are legitimate tools which we need to take into account these positive, rights-protecting use cases in the use of adversarial personas&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/rightscon-costa-rica-2023/events/the-devils-in-the-details-adversarial-design-in-action-vfqp8MGheDqvFcB8r3ed9v&#34;&gt;Add to your sessions&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;fck-it-well-do-it-ourselves-building-products-to-prevent-and-counter-gender-based-violence-online&#34;&gt;F*ck it, we&amp;rsquo;ll do it ourselves: building products to prevent and counter gender-based violence online&lt;/h3&gt;
&lt;h4 id=&#34;june-8-2023--315-415pm-cst-gmt-6&#34;&gt;June 8, 2023 | 3.15-4.15pm CST (GMT-6)&lt;/h4&gt;
&lt;h4 id=&#34;in-person-3&#34;&gt;In person&lt;/h4&gt;
&lt;h4 id=&#34;georgia-bullen-superbloom-eduardo-carillo-tedic-luisa-braig-social-finance-uk-fernanda-martins-internetlab&#34;&gt;Georgia Bullen (Superbloom), Eduardo Carillo (TEDIC), Luisa Braig (Social Finance UK), Fernanda Martins (InternetLab)&lt;/h4&gt;
&lt;p&gt;Whether the cause of gender violence online is the misuse by bad actors of a platform as intended, or a platform prioritizing engagement over safety, harassment is rife online and among the needed changes are the very products that we use every day. Many in the human rights and gender justice community have proposed direct changes to products, often without knowledge and collaboration of how product changes are made within companies. This session will provide an overview of the extent of the problem of gender harassment online, common pitfalls in working with platforms to change their services, and a workshop on the best ways to approach product development to prevent and respond to online gender-based violence.  &lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/rightscon-costa-rica-2023/events/fck-it-well-do-it-ourselves-building-products-to-prevent-and-counter-gender-based-violence-online-vnbQzLcXuXvcpAxC5MjGPz&#34;&gt;Add to your sessions&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_rightscon_2023_colibri_humming-bird_hu_7af9303f6481848a.jpg&#34; width=&#34;740&#34; height=&#34;481&#34;&gt;
&lt;/p&gt;
&lt;p&gt;We hope to see you in San José and online!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>A Dev’s Guide To Design In Open Source Software</title>
      <link>https://superbloom.design/learning/blog/a-devs-guide-to-design-in-open-source-software/</link>
      <pubDate>Wed, 24 May 2023 13:25:36 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/a-devs-guide-to-design-in-open-source-software/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_user_testing_can_be_fun_hu_645a8f9cdb75aee1.png&#34; width=&#34;740&#34; height=&#34;507&#34;&gt;
&lt;/p&gt;
&lt;h1 id=&#34;a-devs-guide-to-design-in-open-source-software&#34;&gt;A Dev’s Guide To Design In Open Source Software&lt;/h1&gt;
&lt;p&gt;You can find all of the Adoptable resources we created on the &lt;a href=&#34;https://github.com/simplysecure/devs-guide-to&#34;&gt;open repository&lt;/a&gt; or on the &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/&#34;&gt;microsite&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In 2022, Superbloom partnered with &lt;a href=&#34;https://internews.org/&#34;&gt;Internews&lt;/a&gt; and &lt;a href=&#34;http://okthanks.com&#34;&gt;Okthanks&lt;/a&gt; to create resources that help open OSS teams understand how design processes and activities improve the usability of open source tools. We called this work ‘Adoptable’, and throughout the process, we shared and tracked our work progress on an &lt;a href=&#34;https://github.com/sprblm/devs-guide-to&#34;&gt;open and contributable repository&lt;/a&gt;, and published the resources to an &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/&#34;&gt;OS microsite&lt;/a&gt;. Below, we outline some core thematic insights and needs that came out of the research and briefly introduce the five resources.&lt;/p&gt;
&lt;h2 id=&#34;understanding-the-challenge&#34;&gt;Understanding The Challenge&lt;/h2&gt;
&lt;p&gt;Across various types of open source software, design is regularly misunderstood and under utilized. The challenges in doing design in open source software (OSS) typically center around OSS’s systemic production and cultural issues which all impact how design is perceived and respected. OSS teams are often stuck in the ‘design is visuals’ paradigm where those in software development view design as the pixels, the graphics, and user interfaces and less the ways in which tools function according to or failing a user&amp;rsquo;s expectations and needs.&lt;/p&gt;
&lt;p&gt;There is a misunderstanding of what design is and what it can do, of how and when design is done as part of a life cycle of a product, and of what tools designers may use. These complex problems cannot simply be solved by forcing design to be part of open source software tool development.&lt;/p&gt;
&lt;p&gt;In response to this challenge, we decided to make the process of design more accessible and visible by documenting tangible, actionable ways of interacting with users with the goal of unlocking the value of design. But first, in order to make open source software better across broad types of users, the Adoptable team sought to understand how design can be made accessible to open source software developers.&lt;/p&gt;
&lt;h2 id=&#34;unpacking-devs-design-perceptions-and-practices&#34;&gt;Unpacking Devs’ Design Perceptions And Practices&lt;/h2&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_unpacking_devs_design_perceptions_and_practices_hu_5641c21c74f67550.png&#34; width=&#34;740&#34; height=&#34;237&#34;&gt;
&lt;/p&gt;
&lt;p&gt;To create relevant resources, we needed to understand the most salient issues within OSS developer communities regarding design perceptions and practice. We interviewed seven people who were part of security and privacy-focused OSS tool teams to understand:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What are the biggest gaps of design knowledge?&lt;/li&gt;
&lt;li&gt;What are the biggest opportunities for introducing design methods?&lt;/li&gt;
&lt;li&gt;What would be most useful to projects right now? &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This research generated many key insights to inform resource development. These insights were grounded in some core themes we identified:&lt;/p&gt;
&lt;h3 id=&#34;perceived-practical-barriers&#34;&gt;Perceived Practical Barriers&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Design is perceived as ’expensive’ – design and designers cost a lot. When unpacking this idea, we found that design is a less ‘understandable and visible’ aspect of software creation and development. Especially the ‘invisible’ design work, such as user research, UX insights, facilitation, and capacity building, is not often viewed as an ‘output’ and therefore a ‘waste of money’. Visual design is much easier to see and therefore more valued. Without user research, it is harder to create the visual design and the result is less user/human-centered.&lt;/li&gt;
&lt;li&gt;Design tooling is perceived as not easily fitting in the OSS developer’s toolbox. OSS developers shared that they couldn’t imagine easily integrating design processes and tools into their projects’ workflow.  Most often this came down to a mention of designers ’not being on GitHub/GitLab’ (or similar code based repository locations). The key insight here was the need to invest time in building designers&amp;rsquo; understanding of common OSS practices as well as building OSS tool teams’ understanding of design practices. Plan for onboarding and welcoming beyond expecting designers to &amp;lsquo;read the OSS manual’.&lt;/li&gt;
&lt;li&gt;OSS tool teams don’t know how to find designers aligned with their project needs.  Though designers interested in OSS exist and there are communities for them to communicate, collaborate, and meet OSS teams, usually OSS tool teams feel they have to ‘go outside of their sphere of comfort&amp;rsquo; to find and connect with designers. This is true for a wide variety of diversity and inclusion needs within OSS and best described with the phrase: ‘You won&amp;rsquo;t meet new kinds of people in your own house!&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;working-across-disciplines&#34;&gt;Working Across Disciplines &lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Working collaboratively with developers as early as possible is a way to encourage successful design in OSS. For this collaboration to work, both designers and developers must invest time and effort in each others’ day-to-day processes to build trust. It’s important to remove as much constraint and tension within the collaborative relationship as possible. That means going beyond designing for ‘short time frames of development’ to ‘building trust and understanding widely within the OSS in order to design effectively for real users’.&lt;/li&gt;
&lt;li&gt;There are common differences in developers’ understanding of design. Therefore, not all designers will know what and how to deliver design to accommodate developers’ understanding. For example, some developers want high-fidelity prototypes based on a grid, while others are used to implementing with wireframes and a style guide. Best approaches are to grow common understandings of design terminology/practices, learn what to ask for, and ensure designers are set up for success.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;value-and-urgency&#34;&gt;Value And Urgency&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Volunteer designers in OSS are perceived as ’too slow’. Generally designers do their work outside of GitHub/GitLab and this can contribute to OSS tool teams not fully understanding how long ‘good’ design takes. Ensuring there is a plan for onboarding, mentoring and integration into the OSS tool helps with this.&lt;/li&gt;
&lt;li&gt;OSS tool teams have trouble seeing the value of design research compared to issues that feel ‘more pressing.’ In the early design research phases such as user testing, usability research and synthesis, there is an upfront investment in helping designers ‘upskill’ and make the most of the community of users. This is important because user/human insights allow an OSS tool to achieve a new level of maturity beyond the ‘itch to scratch’ implementation process. Yet, this upfront work can be frustrating when there is already a backlog of identified issues in need of developer attention. Placing focus on user research helps the team identify the high-impact problems and this goes a long way to helping design and development in OSS tools work together.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Special considerations:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;High risk users and human rights centered design for sensitive/safety OSS tools is a complex topic with detailed and careful considerations and needs. Open practices and design methods don’t always work well with high risk users OSS tools. This needs to be addressed by designers and the wider team to establish guidelines before jumping into the work.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;designing-friendly-yet-boundary-pushing-resources&#34;&gt;Designing Friendly Yet Boundary-pushing Resources&lt;/h2&gt;
&lt;p&gt;After metabolizing what we heard from OSS developers, the urgency for action came together around four key needs:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Addressing design misconceptions by considering frequently asked questions and tensions in user testing.&lt;/li&gt;
&lt;li&gt;Promoting collaboration by guiding OSS tool teams to better understand user testing and practice these skills alongside designers.&lt;/li&gt;
&lt;li&gt;Focusing on the user via working together in a synthesis process with real user testing insights to converge on core user problems/needs.&lt;/li&gt;
&lt;li&gt;Hearing a variety of voices by asking the OSS community how they collaborate on complex OSS tools.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;From these needs, we explored many directions for resources that addressed these thematic gaps. We thought about ways to integrate this work within the OSS community more broadly, to contextualize and occupy the space that design needs in order to become more culturally accepted. In that spirit, we created actionable resources for use, and we embedded ourselves into community spaces to socialize them.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_designing_friendly_yet_boundary_pushing_resources_hu_6dd25ad7d03e56c1.png&#34; width=&#34;740&#34; height=&#34;509&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;resource-1-user-testing-can-be-fun-an-faq---interactive-guide&#34;&gt;Resource #1: User Testing Can Be Fun: An FAQ - Interactive Guide &lt;/h3&gt;
&lt;p&gt;&lt;a href=&#34;https://usable.itch.io/user-testing-can-be-fun-a-guide-for-oss-developers-and-tool-teams-on-how-to-user&#34;&gt;Play the guide here&lt;/a&gt; - &lt;a href=&#34;https://github.com/simplysecure/usable-user-testing-can-be-fun&#34;&gt;See the repository here&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;This resource, built in Twine using Sugarcube (OSS tools) is a click/tappable guide with conversational, interactive elements. To avoid another ‘pdf document’ or ‘step based list guide’ that are text based and labor  intensive to read/consume we wanted to make our introduction guide to user testing for devs more fun and engaging. &lt;a href=&#34;https://usable.itch.io/user-testing-can-be-fun-a-guide-for-oss-developers-and-tool-teams-on-how-to-user&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_resource_1_hu_91f2e3d9a4dab154.png&#34; width=&#34;740&#34; height=&#34;370&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;resource-2-user-testing-can-be-fun-an-faq---poster&#34;&gt;Resource #2: User Testing Can Be Fun: An FAQ - Poster&lt;/h3&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/simplysecure/usable-user-testing-can-be-fun-poster&#34;&gt;Printable Poster&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A poster that can be printed and stuck on the walls of an office or home. The poster has condensed information and advice for those new to user testing in software. The poster has three different visual versions from ink intensive to ink light for those printing at home and wanting to save printer ink.&lt;/p&gt;
&lt;h3 id=&#34;resource-3-a-devs-guide-to-user-testing&#34;&gt;Resource #3: A Dev’s Guide To User Testing&lt;/h3&gt;
&lt;p&gt;When speaking with developers we heard that user testing and usability testing is largely a mystery to the average developer. Many will have heard of the terms and often are enthusiastic about the opportunities and improvements that user testing and usability testing can give their OSS tools, but when it comes to trying to kick off the process by themselves they’re unsure where to start and what’s sustainable for a team without a designer on staff or a volunteer contributor. We created a series of written documents with copy-paste example templates for recruiting users, scripting testing sessions and gathering data, all kept on our micro site here: &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/a-dev-guide-to-usertesting/&#34;&gt;https://sprblm.github.io/devs-guide-to/a-dev-guide-to-usertesting/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_resource_3_hu_cfb4f1a8337c9866.png&#34; width=&#34;740&#34; height=&#34;370&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;resource-4-synthesis-for-open-source&#34;&gt;Resource #4: Synthesis For Open-source&lt;/h3&gt;
&lt;p&gt;When we spoke with the OSS tool teams about how to perform user tests and usability tests, they asked us ‘what’s next?’ with the wealth of data it had collected. We began to realise that the process of understanding and synthesizing user information was a skill and process OSS devs had not previously experienced. There are many techniques and methods that can be utilized for synthesis of data but we focussed on a method that is collaborative and builds consensus between team members. &lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://sprblm.github.io/devs-guide-to/synthesis-for-open-source/&#34;&gt;https://sprblm.github.io/devs-guide-to/synthesis-for-open-source/&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_resource_4_hu_c8576d573281cd91.png&#34; width=&#34;740&#34; height=&#34;366&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;resource-5-developer-and-designer-collaboration-in-open-source&#34;&gt;Resource #5: Developer And Designer Collaboration In Open Source&lt;/h3&gt;
&lt;p&gt;Continuing the logical progression of skills and processes from user/usability testing to synthesis we continued by fielding questions from the OSS tools teams about how to consistently collaborate between developers and designers in the OSS space. We have processes and preferences at Superbloom but all OSS tools are different and therefore collaboration can look different and need to be different for teams dependant on their circumstances. So instead of providing a single explanation of collaboration we invited other designers, developers and product managers working on security and privacy OSS to discuss collaboration with us.&lt;/p&gt;
&lt;p&gt;You can find the episode recording here: &lt;a href=&#34;https://sosdesign.sustainoss.org/18&#34;&gt;https://sosdesign.sustainoss.org/18&lt;/a&gt; and the transcript of the episode here: &lt;a href=&#34;https://github.com/simplysecure/designer-developer-collaboration-in-OSS/blob/main/In-conversation-with-designers-and-developers-in-OSS-for-SOS-podcast.md&#34;&gt;https://github.com/simplysecure/designer-developer-collaboration-in-OSS/blob/main/In-conversation-with-designers-and-developers-in-OSS-for-SOS-podcast.md&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;community-activities-and-events&#34;&gt;Community Activities And Events&lt;/h3&gt;
&lt;p&gt;As well as crafting and providing resources, the Adoptable team wanted to make sure that we didn’t assume that such resources would be discoverable by default by OSS tool teams. With the overwhelming amount of advice and support across the internet on how to ‘do design’ without the context being OSS, security or privacy focussed, we made sure that our approach to communicating and socializing or resources was rooted in an understanding, appreciation and respect for the OSS and security tool space. We went to the spaces that our community were already in, intentionally invited people into practical sessions as well as instructive sessions and made sure our resources exist in developer and OSS tool team friendly formats, and used OSS technology wherever possible.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_communities_activities_and_events_hu_36edf2d4457a6629.png&#34; width=&#34;740&#34; height=&#34;383&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;IMakeFOSS Twitter takeover&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For our first community activity we spoke with the folks that run the &lt;a href=&#34;https://imakefoss.org/&#34;&gt;IMakeFOSS&lt;/a&gt; &lt;a href=&#34;https://twitter.com/imakefoss&#34;&gt;Twitter account&lt;/a&gt;. We spent five days tweeting from the account as the Adoptable project focused on the content created for ‘user testing can be fun’.&lt;/p&gt;
&lt;p&gt;You can see the tweets archived here: &lt;a href=&#34;https://imakefoss.org/tweets/eriolandkelsey/&#34;&gt;https://imakefoss.org/tweets/eriolandkelsey/&lt;/a&gt; and an interview with the Adoptable team here: &lt;a href=&#34;https://imakefoss.org/curators/eriolfoxandkelseysmith/&#34;&gt;https://imakefoss.org/curators/eriolfoxandkelseysmith/&lt;/a&gt; &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Developer and designer collaboration in open source podcast episode&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We did a podcast to discuss collaboration between developers and designers, which was created with OSS security and privacy tools community members with the aim to provoke discussion and dialogue about methods of collaboration across the OSS tool space.&lt;/p&gt;
&lt;p&gt;You can find the episode recording here: &lt;a href=&#34;https://sosdesign.sustainoss.org/18&#34;&gt;https://sosdesign.sustainoss.org/18&lt;/a&gt; and the transcript of the episode here: &lt;a href=&#34;https://github.com/simplysecure/designer-developer-collaboration-in-OSS/blob/main/In-conversation-with-designers-and-developers-in-OSS-for-SOS-podcast.md&#34;&gt;https://github.com/simplysecure/designer-developer-collaboration-in-OSS/blob/main/In-conversation-with-designers-and-developers-in-OSS-for-SOS-podcast.md&lt;/a&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A dev’s guide to synthesis; a Simply Secure hosted workshop&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We invited specific developers from two OSS tool teams who we interviewed initially to participate in a mock synthesis session with sample data that we’d gathered from a previous project. We often find that if we use live data from OSS tool teams projects then often the data can become the focus, as opposed to the synthesis methods. We spent three hours with these two tool teams taking them through a synthesis process and practicing how to manage data across user testing and user research.&lt;/p&gt;
&lt;p&gt;Check out the explainer for the private workshop: &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/posts/synthesis-for-open-source-workshop/&#34;&gt;https://sprblm.github.io/devs-guide-to/posts/synthesis-for-open-source-workshop/&lt;/a&gt; &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A dev’s guide to synthesis at FOSDEM 2022 for the Open Source Design devroom.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;After the private workshop we wanted to speak more widely about what we’d done, learned and shared with the OSS tool team members but retain their anonymity. We had a 20 minute talk to cover the key elements of our synthesis resource and the private workshop at FOSDEM.&lt;/p&gt;
&lt;p&gt;Check out the talk at FOSDEM that we did about this resource and process: &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/posts/synthesis-for-open-source-at-fosdem22/&#34;&gt;https://sprblm.github.io/devs-guide-to/posts/synthesis-for-open-source-at-fosdem22/&lt;/a&gt; &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A dev’s guide… at MozFest 2022&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Our two penultimate community activities were talk slots at two different conferences that serve the OSS, internet freedom and privacy and security OSS community. At both these events we spoke generally about the resources we created for the Adoptable project and spoke with developers and other OSS community members about doing design in OSS privacy and security tools. We found plenty of excitement and enthusiasm for these resources and requests for active workshops in following years&amp;rsquo; conferences.&lt;/p&gt;
&lt;p&gt;Check out the talk at MozFest here: &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/posts/usable-resources-at-mozfest22/&#34;&gt;https://sprblm.github.io/devs-guide-to/posts/usable-resources-at-mozfest22/&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;Check out the FOSSASIA talk here: &lt;a href=&#34;https://youtu.be/75dAcDSRrC8?list=PLzZVLecTsGpIV6Rb7C9Y3ALatqxIg2wAM&amp;amp;t=28666&#34;&gt;https://youtu.be/75dAcDSRrC8?list=PLzZVLecTsGpIV6Rb7C9Y3ALatqxIg2wAM&amp;amp;t=28666&lt;/a&gt; &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Getting comfortable with user testing through role play at the UXForum 2022&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The last community activity we did was an active session where we invited people to role play a user testing session. One person performed the role of interviewer/researcher and one played the role of the user with a briefing sheet for their character background and details.&lt;/p&gt;
&lt;p&gt;Check out the information here: &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/posts/getting-used-to-user-testing-at-the-uxforum/&#34;&gt;https://sprblm.github.io/devs-guide-to/posts/getting-used-to-user-testing-at-the-uxforum/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;And the role play worksheets here: &lt;a href=&#34;https://drive.google.com/drive/u/1/folders/1wbSHjEhZVqzWMVkxZT_qTSP3RSuJkgxD&#34;&gt;https://drive.google.com/drive/u/1/folders/1wbSHjEhZVqzWMVkxZT_qTSP3RSuJkgxD&lt;/a&gt; &lt;/p&gt;
&lt;h2 id=&#34;looking-ahead&#34;&gt;Looking Ahead&lt;/h2&gt;
&lt;p&gt;As we closed out the first phase of Adoptable, we continued as active participants in the OSS design community by making many of our resources, workshops and talks open repositories available on GitHub. We hope that people will contribute, fork and request additions or changes by opening an issue or commenting on our work. &lt;/p&gt;
&lt;p&gt;By building these resources and continuing our engagements with OSS tool teams, we are ultimately helping to grow the ecosystem’s understanding of how design can help serve users. We plan to continue this work, encouraging the OSS community to shift towards a culture that is more welcoming to contributors – including designers – who bring different perspectives, backgrounds and methods to the table. You can see further exploration in our &lt;a href=&#34;https://superbloom.design/learning/blog/introducing-user-usable-software-ecosystem-research/&#34;&gt;Usable Software Ecosystem Research (USER)&lt;/a&gt; project, investigating how design and usability are perceived and practiced within scientific and research OSS projects &lt;a href=&#34;https://github.com/simplysecure/USER_project&#34;&gt;(see repo here)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Stay tuned, and be sure to check out &lt;a href=&#34;https://sosdesign.sustainoss.org/&#34;&gt;Sustain OSS Design&lt;/a&gt; and &lt;a href=&#34;https://opensourcedesign.net/&#34;&gt;Open Source Design&lt;/a&gt; for information, resources, gatherings, and more.&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project contributors: &lt;a href=&#34;https://superbloom.design/&#34;&gt;Superbloom&lt;/a&gt;, &lt;a href=&#34;https://internews.org/&#34;&gt;Internews&lt;/a&gt;, &lt;a href=&#34;https://okthanks.com/&#34;&gt;Okthanks&lt;/a&gt;, along with the projects we did research with: &lt;a href=&#34;https://docs.digiresilience.org/link/about/&#34;&gt;CDR Link&lt;/a&gt;, &lt;a href=&#34;https://encirculo.org/en/&#34;&gt;Circulo&lt;/a&gt;, &lt;a href=&#34;https://securedrop.org/&#34;&gt;SecureDrop&lt;/a&gt;, &lt;a href=&#34;https://tails.boum.org/&#34;&gt;Tails&lt;/a&gt;, &lt;a href=&#34;https://keepassxc.org/&#34;&gt;KeePassXC&lt;/a&gt;, &lt;a href=&#34;https://www.tella.tv/&#34;&gt;Tella&lt;/a&gt;, &lt;a href=&#34;https://mailvelope.com/en/&#34;&gt;Mailvelope&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;With support from &lt;a href=&#34;https://internews.org/&#34;&gt;Internews&lt;/a&gt;, UXForum, &lt;a href=&#34;https://fossasia.org/&#34;&gt;FOSSASIA&lt;/a&gt;, &lt;a href=&#34;https://fosdem.org/2023/&#34;&gt;FOSDEM’s Open Source Design Devroom&lt;/a&gt;, &lt;a href=&#34;https://www.mozillafestival.org/en/&#34;&gt;MozFest&lt;/a&gt;, &lt;a href=&#34;https://sosdesign.sustainoss.org/&#34;&gt;Sustaining Open Source Design Design podcast (SOSD)&lt;/a&gt; and &lt;a href=&#34;https://www.imakefoss.org/&#34;&gt;IMakeFOSS&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;L﻿ead image: under creative commons license.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>USER: A Work In Process</title>
      <link>https://superbloom.design/learning/blog/user-a-work-in-progress/</link>
      <pubDate>Mon, 15 May 2023 11:04:13 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/user-a-work-in-progress/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_sloan_user_woman_lab_coat_hu_eed29f98d3bee5f.png&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;h1 id=&#34;user-a-work-in-process&#34;&gt;USER: A Work In Process&lt;/h1&gt;
&lt;p&gt;Usable Software Ecosystem Research (USER) is a Sloan Foundation-supported research initiative that explores how open source scientific and research software (S&amp;amp;R OSS) teams understand, consider, and undertake usability and design opportunities in their projects. To read more about this project please check out &lt;a href=&#34;https://superbloom.design/learning/blog/introducing-user-usable-software-ecosystem-research/&#34;&gt;Blog #1&lt;/a&gt; and check out our &lt;a href=&#34;https://github.com/simplysecure/USER_project&#34;&gt;open repo&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;When we last posted an update about our Usable Software Ecosystem Research (USER) project, we were just wrapping up our 27 interviews and closing our two community surveys. Since February, our six-person research team has collaborated virtually and in-person to analyze the huge amount of qualitative and quantitative data we’ve collected over the course of this project. The process has been daunting at times, but has also been energizing and illuminating. Here we outline some key components of our research process and share a draft excerpt from our findings. &lt;/p&gt;
&lt;h2 id=&#34;in-the-thick-of-it&#34;&gt;In The Thick Of It&lt;/h2&gt;
&lt;p&gt;USER has presented our team with a challenge: how do we best do deep, human-centered research with a distributed team while working remotely and collaborating equitably? In previous projects, we’ve tried to stay ahead of the synthesis process by using what we call a “Debrief Synthesis Board&amp;rsquo;&amp;rsquo; in Miro, where we have a grid-like structure that we can use after completing each interview to capture the most important ideas and findings. This method proved to be difficult in the face of such a wide-ranging and complex research topic. In the end, we organized over 1500 sticky notes over many rounds, into more than 25 categories! &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_sloan_user_stickies_1_hu_592727b98efc1a63.png&#34; width=&#34;740&#34; height=&#34;275&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Our Miro board went from the above debrief grid to the below organization of themes and topics, and then through another two iterations of organization - identifying common themes and then consolidating.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_sloan_user_stickies_2_hu_4e9c2e932b6a2464.png&#34; width=&#34;740&#34; height=&#34;275&#34;&gt;
&lt;/p&gt;
&lt;p&gt;To be sure we captured interviewees’ thoughts and words precisely and in context, we also recorded each interview. We created a codebook that allowed us to filter the quotes by theme and subtheme during our outlining and writing process. Together, the Miro board and the codebook left us with a wealth of evidence. We were both overwhelmed by the data and excited that we had learned so much on so many topics from our interviews. &lt;/p&gt;
&lt;h2 id=&#34;returning-to-our-research-questions&#34;&gt;Returning To Our Research Questions&lt;/h2&gt;
&lt;p&gt;Our synthesis process made it clear that both we and the participants in our project had many thoughts about in response to our research questions. We left data collection with a range of findings, beyond what we initially anticipated. So much can influence the level of attention given to design in these projects, from how visual designers collaborate with them, to the values that scientists bring to technology projects, to how academia, hierarchy, and governance affect prioritization and user-awareness. &lt;/p&gt;
&lt;p&gt;The writing phase required us to re-ground ourselves in our research questions. While we also plan to release our more general findings for the ecosystem, we aim to shed the most light on the particular nuances we uncovered around S&amp;amp;R OSS projects, usability, and design. &lt;/p&gt;
&lt;h2 id=&#34;an-excerpt-in-progress&#34;&gt;An Excerpt-in-Progress &lt;/h2&gt;
&lt;p&gt;Our final outputs will be published at the end of May, but we’re eager to share a sample of what we’re working on. The following is a piece of the draft chapter on designers’ experiences in S&amp;amp;R OSS projects.&lt;/p&gt;
&lt;h3 id=&#34;designers-in-projects-often-need-to-justify-design-and-educate-others-about-the-need-for-it-to-get-buy-in&#34;&gt;Designers In Projects Often Need To Justify Design And Educate Others About The Need For It To Get Buy-in&lt;/h3&gt;
&lt;p&gt;If there are designers in teams working on Open Source Research Software, they are often tasked not only with their work, but with educating the team on how design is done and why it&amp;rsquo;s relevant. This is needed, since design is usually a late addition to projects, after other practices, like collaboration on code, have been established. Without educational work, design would remain an activity that is not seen to be relevant in practice. &lt;/p&gt;
&lt;p&gt;For this, they need to balance both making design its own recognized activity while not being perceived as threatening or opposing existing practices. Designers employed different methods to do this: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Presenting design as a “blank slate” without preconceived opinions&lt;/li&gt;
&lt;li&gt;Suggest design activities that do not need a lot of resources, like lightweight usability testing of existing ideas&lt;/li&gt;
&lt;li&gt;Demonstrating the usefulness of design in the context of an ongoing project&lt;/li&gt;
&lt;li&gt;Getting involved in existing discussions rather than opening up new ones&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All these methods involve being not threatening and working in existing structures to, ideally, build small wins that demonstrate that design can be a helpful contribution. &lt;/p&gt;
&lt;p&gt;Designers also tried to manage their identity and distanced themselves from values and activities which are seen as “bad ‘in open source projects: “Polishing” (iterating in small steps with strong care for details), “superficiality” (strong care for immediate visual aesthetics), “maximizing clicks” (tracking user actions and compare them to goals) are seen as bad. &lt;/p&gt;
&lt;p&gt;Still, many struggled with achieving a mutual understanding. Designers wished for a “common language” which they tried to work towards by explaining terminology and educating team members. However, even if the terms were there, it did not necessarily translate into their practice when working on the software. &lt;/p&gt;
&lt;h2 id=&#34;what-comes-next&#34;&gt;What Comes Next&lt;/h2&gt;
&lt;p&gt;We’re currently editing our outputs for publication at the end of May. Please be sure to keep an eye out for the final drafts, and keep an eye on &lt;a href=&#34;https://superbloom.design/learning/blog/&#34;&gt;our blog&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/sprblm_&#34;&gt;Twitter&lt;/a&gt;, and &lt;a href=&#34;https://github.com/simplysecure/USER_project&#34;&gt;GitHub repo&lt;/a&gt; for updates.&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Contributors: &lt;a href=&#34;https://twitter.com/EriolDoesDesign&#34;&gt;Eriol Fox&lt;/a&gt;, &lt;a href=&#34;https://simplysecure.org/who-we-are/katie/&#34;&gt;Katie Wilson&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/abhi1203&#34;&gt;Abhishek Sharma&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/smklibrarian&#34;&gt;Susan Kennedy&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/kirakirawes&#34;&gt;Ngọc Triệu&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/simulo&#34;&gt;Jan Dittrich&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/EmDohh&#34;&gt;Meag Doherty&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;Image credit: Bill Branson (Photographer) - This image was released by the &lt;a href=&#34;https://en.wikipedia.org/wiki/National_Cancer_Institute&#34;&gt;National Cancer Institute&lt;/a&gt;, an agency part of the &lt;a href=&#34;https://en.wikipedia.org/wiki/National_Institutes_of_Health&#34;&gt;National Institutes of Health&lt;/a&gt;, with the ID &lt;a href=&#34;https://visualsonline.cancer.gov/details.cfm?imageid=1844&#34;&gt;1844&lt;/a&gt; (&lt;a href=&#34;https://visualsonline.cancer.gov/retrieve.cfm?imageid=1844&amp;amp;dpi=300&amp;amp;fileformat=jpg&#34;&gt;image&lt;/a&gt;) via &lt;a href=&#34;https://commons.wikimedia.org/wiki/File:Film_Optical_Sensing_Device_for_Input_to_Computers_(FOSDIC).jpg&#34;&gt;Wikimedia Commons&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;With support from the &lt;a href=&#34;https://sloan.org/&#34;&gt;Sloan Foundation&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Making Design More Open: Superbloom At FOSS Backstage 2023</title>
      <link>https://superbloom.design/learning/blog/making-design-more-open-superbloom-at-foss-backstage-2023/</link>
      <pubDate>Thu, 04 May 2023 17:59:03 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/making-design-more-open-superbloom-at-foss-backstage-2023/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_foss_2023_04_image_cakes_hu_653438ebf291f7ca.jpg&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;h6 id=&#34;photo-credit&#34;&gt;&lt;strong&gt;Photo credit: &lt;a href=&#34;https://plainschwarz.com/&#34;&gt;Plain Schwarz&lt;/a&gt;.&lt;/strong&gt;&lt;/h6&gt;
&lt;p&gt;On March 13 and 14, 2023, two of our team members, Eriol Fox and ngọc triệu, and one of our collaborators, Django Skorupa, attended &lt;a href=&#34;https://23.foss-backstage.de/&#34;&gt;FOSS Backstage&lt;/a&gt;, a two-day conference focused on all aspects of free, libre, and open source software (FOSS). The conference covered topics ranging from Sustainability and Funding, Diversity and Inclusion, Legal and Compliance, to Governance and Community. Attendees had the chance to discuss the latest advancements and challenges in the FOSS ecosystem with funders such as the &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;, &lt;a href=&#34;https://sovereigntechfund.de/en/&#34;&gt;Sovereign Tech Fund&lt;/a&gt;, Prototype Fund, developers, and community leaders in the FOSS ecosystem.&lt;/p&gt;
&lt;h2 id=&#34;design-with-a-capital-d-design-in-foss&#34;&gt;Design With A Capital D: Design In FOSS&lt;/h2&gt;
&lt;p&gt;Our workshop at FOSS Backstage focused on &amp;ldquo;Design with a capital D&amp;rdquo; because it&amp;rsquo;s what FOSS has trouble receiving, and for valid reasons. However, it&amp;rsquo;s an essential, critical, yet invisible part of getting to the tangible design.&lt;/p&gt;
&lt;p&gt;Design in FOSS is not a new concept. Designers and those who work on FOSS tool design have been around since the beginning, and may have previously been referred to as usability or human-computer interaction (HCI) experts. Regardless of when designers in FOSS initially started, it is becoming increasingly clear that there has been a growing trend and interest in design within OSS over the past five years or more. Design has become an integral part of technology tools in both proprietary and commercial settings. More and more organizations and companies are adopting design processes and including designers as part of their technology projects.&lt;/p&gt;
&lt;p&gt;The definition and description of UX Design often varies, depending on factors such as the organization, geographical location, and design team. While those collaborating with designers tend to think of design as limited to visuals, graphics, logos, UI, and tangible aspects of design, designers often provide a greater function than their deliverables may suggest. However, for many FOSS projects, those deliverables tend to align with what is valued, such as code that successfully functions.&lt;/p&gt;
&lt;p&gt;But what are those other functions? Often referred to as “Capital D Design” it involves research, thinking, conversations, collaborations, facilitation, interpretation, intuition (from hypotheses), and applying a broad range of design knowledge. This type of work is very difficult to contribute to in a traditional FOSS &amp;ldquo;pushing code&amp;rdquo; sense, so it is largely absent from design in FOSS. Designers have only recently become comfortable with opening up their design processes to the public, and tools like Figma and Penpot&amp;rsquo;s shared teams/files are focused solely on tangible design work. Most of the time, any design work will have a lot of &amp;ldquo;Design with a capital D&amp;rdquo; beforehand, but it&amp;rsquo;s mostly invisible.&lt;/p&gt;
&lt;h2 id=&#34;making-design-more-open-a-design-workshop-for-non-designers-in-foss&#34;&gt;Making Design More Open: A Design Workshop For Non-Designers in FOSS&lt;/h2&gt;
&lt;p&gt;Our workshop was designed to assist non-designers in FOSS in understanding and implementing design principles and tasks that enable them to appreciate the value that design brings. Its aim was to equip them with the necessary knowledge to request appropriate design services for their projects and to feel confident participating in design for FOSS.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_foss_2023_04_image_eriol_hu_f5c7692e90d0fa6f.jpg&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;h6 id=&#34;photo-credit-1&#34;&gt;&lt;strong&gt;Photo credit: &lt;a href=&#34;https://plainschwarz.com/&#34;&gt;Plain Schwarz&lt;/a&gt;.&lt;/strong&gt;&lt;/h6&gt;
&lt;h6 id=&#34;photo-eriol-fox-speaking-at-fossbackstage-2023&#34;&gt;&lt;strong&gt;Photo: E﻿riol Fox speaking at FOSS.Backstage 2023.&lt;/strong&gt;&lt;/h6&gt;
&lt;p&gt;We embraced a human-centered design (HCD) approach for our workshop, aiming to make it relevant and easy to relate to by leading with our personal stories and experiences of doing design in the open source world. As most of the participants were developers, we selected and arranged the design activities with respect to the design process, time allocation (60 minutes), and the audience&amp;rsquo;s level of design proficiency.&lt;/p&gt;
&lt;p&gt;We started by presenting pre-prepared profiles of established FOSS projects that the participants may have already been familiar with. These included &lt;a href=&#34;https://scratch.mit.edu/&#34;&gt;Scratch&lt;/a&gt;, &lt;a href=&#34;https://www.python.org/&#34;&gt;Python&lt;/a&gt;, and &lt;a href=&#34;https://www.signal.org/&#34;&gt;Signal&lt;/a&gt;. Each was accompanied by a brief overview of the software, target audience, and objectives. Participants were divided into groups of 4-5 people before going into our chosen exercises. &lt;/p&gt;
&lt;p&gt;The exercises that we chose to introduced in this workshop include:&lt;/p&gt;
&lt;h3 id=&#34;1-value-proposition&#34;&gt;1. Value Proposition&lt;/h3&gt;
&lt;p&gt;For this activity, each group was tasked with creating a value proposition using the profile of their assigned FOSS Project. A value proposition is a simple and clear statement that communicates the unique benefits of a product or service and sets it apart from other similar products or services.The typical components of a value proposition include: Name, Description Target Users, and Purpose. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_foss_2023_04_image_1._valueprop_example_hu_d1ca9206547e9c74.png&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;h6 id=&#34;an-example-of-a-value-proposition-statement&#34;&gt;An example of a value proposition statement. &lt;/h6&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/design_tools/ValueProp-Generator/ValueProp-template.png&#34;&gt;Download The Value Proposition Generator Template&lt;/a&gt; &lt;/p&gt;
&lt;h4 id=&#34;participant-feedback&#34;&gt;Participant Feedback&lt;/h4&gt;
&lt;p&gt;This exercise helps teams of people who may not have met or worked closely together before, come to a quick understanding and consensus about a project or tool&amp;rsquo;s intentions. However, one point of confusion for our workshop participants was whether to write the value proposition from the perspective of a) a user of the FOSS tool b) a contributor to the FOSS tool c) both combined.&lt;/p&gt;
&lt;h3 id=&#34;2-personas&#34;&gt;2. Personas&lt;/h3&gt;
&lt;p&gt;In this activity, each group of participants received a persona for their FLOSS project profile. A persona is a fictional amalgamation of demographic information created as a design tool to ensure a project stays on track for the needs of the stakeholders. Personas are always rooted in the experiences and wants of real people. For optimal results, the stakeholders should consist of real people randomly selected from a diverse range of demographics that are directly affected by changes to your product.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/superbloom.design_foss_2023_04_image_2_persona_hu_1c9feeccd0f113df.png&#34; width=&#34;740&#34; height=&#34;354&#34;&gt;
&lt;/p&gt;
&lt;h6 id=&#34;an-example-of-three-personas-used-in-the-workshop&#34;&gt;An example of three personas used in the workshop.&lt;/h6&gt;
&lt;p&gt;Participants were asked to consider one of the personas assigned to them, with the specific instruction that despite their own personal interpretation, this person both values and wants to contribute to the project in question. Based on the participants&amp;rsquo; understanding of the project, and the persona on the table, participants were asked to anticipate struggles that those personas would face when attempting to contribute to or use the project. Specifically, they were asked to consider whether or not anything needed to change about the project. Our hope was to prompt them to see their project through the eyes of another person, and understand that sometimes, the most successful research that you can conduct is research that entirely disproves your initial hypothesis. &lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/research_tools/simsec_basic_persona.pdf&#34;&gt;Download The Persona Template&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/personas/&#34;&gt;Learn More About Using Personas In FOSS&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;3-user-research-conducting-an-interview&#34;&gt;3. User Research: Conducting An Interview&lt;/h3&gt;
&lt;p&gt;&lt;a href=&#34;https://miro.com/app/board/uXjVPstnpEM=/&#34;&gt;Roleplay Scripts: Getting Used To User Testing&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In this activity, participants had the opportunity to learn and practice user testing. One person was assigned as the interviewer and another as the user, with the former receiving a guide and a script and the latter being given a persona who they had to pretend to be. We emphasized that there was no wrong way to do the exercise and encouraged participants to have fun, break character, discuss, make changes, and explore what the practice could do for the OSS projects they maintain or contribute to. In addition, we noted that having their hypothesis destroyed during the exercise was extremely beneficial as it saved time that would have been wasted on competitor analysis, design, development, and launching a product that the existing community had no use for.&lt;/p&gt;
&lt;h4 id=&#34;participant-feedback-1&#34;&gt;Participant Feedback&lt;/h4&gt;
&lt;p&gt;As a designer and facilitator, you know an exercise is engaging when your audience doesn&amp;rsquo;t want to stop! Even though role play can be tough for many reasons beyond the initial embarrassment (e.g. language barriers, interview technique and improvement), finding out new information about your FOSS tools and software can quickly help participants overcome these difficult moments. After the workshop, participants left with the scripts in hand as well as a host of other examples from our &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/&#34;&gt;‘A Dev’s Guide to User Testing’.&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;key-learnings-and-takeaways&#34;&gt;Key Learnings And Takeaways&lt;/h2&gt;
&lt;p&gt;As the name of our workshop suggests, we hope we made design more open to non-designers of the FOSS ecosystem by opening our design process and offering an opportunity for hands-on experience with different design tools and methods. &lt;/p&gt;
&lt;p&gt;Our key learnings and takeaways are:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;We should keep working on improving and adapting conventional/industrial/standard design tools, methods, and practices to accommodate the specific needs of the FOSS communities.&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;The FOSS community is wary of industry and the ‘standards’ that are popularized by it. Understanding how and when to introduce an industry-created method is key to its usefulness in a FOSS project. It is also important to know when to adapt and change a method to better suit the principles and goals of FOSS.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Be more strategic about the resources and tools introduced and used in workshops.&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;For example, we could use the introduction of Value Proposition as a case study to think strategically about ways to improve the method itself by asking: “How is Value Proposition as a design method perceived and leveraged differently in OS design compared to industrial design, and how can it better serve the needs of the OS teams?”&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Ensure that design has a presence at FOSS events on a large conference scale, as well as a smaller project-to-project scale. It&amp;rsquo;s challenging but always worthwhile.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;When running workshops around design in FOSS conferences and spaces, we often find ourselves with a full room ready to learn. This has generally improved over the last five years as the FOSS community values non-code contributions to FOSS and understands that building sustainable, usable open source software includes design and designers. &lt;/p&gt;
&lt;h4 id=&#34;further-information&#34;&gt;F﻿urther Information&lt;/h4&gt;
&lt;p&gt;Speak to us about bringing design to your conference or FOSS project by emailing us at &lt;a href=&#34;mailto:contact@superbloom.design&#34;&gt;contact@superbloom.design&lt;/a&gt;.  &lt;/p&gt;
&lt;p&gt;Session slides &lt;a href=&#34;https://miro.com/app/board/uXjVPstnpEM=/&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Watch recordings of all the sessions &lt;a href=&#34;https://www.youtube.com/playlist?list=PLq-odUc2x7i9Zrs4oyM1I3V5xlYICEL2g&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;credits&#34;&gt;Credits&lt;/h4&gt;
&lt;p&gt;Contributors: &lt;a href=&#34;https://twitter.com/EriolDoesDesign&#34;&gt;Eriol Fox&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/DjangoSkorupa&#34;&gt;Django Skorupa&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/kirakirawes&#34;&gt;ngọc triệu&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;With support from &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Human-centered Design</title>
      <link>https://superbloom.design/learning/collections/human-centered-design/</link>
      <pubDate>Thu, 27 Apr 2023 13:39:52 -0400</pubDate>
      <guid>https://superbloom.design/learning/collections/human-centered-design/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Join Us At MozFest 2023!</title>
      <link>https://superbloom.design/learning/blog/join-us-at-mozfest-2023/</link>
      <pubDate>Fri, 17 Mar 2023 18:29:18 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/join-us-at-mozfest-2023/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/44941976284_b61924a0f0_o_hu_650c50bf671327d3.jpg&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;h1 id=&#34;join-us-at-mozfest-2023&#34;&gt;Join us at MozFest 2023!&lt;/h1&gt;
&lt;p&gt;Superbloom will be hosting five sessions at the Mozilla Festival (Monday, March 20 - Friday, March 24 2023). If you’ll be there, we’d love to see you, meet you and get to know you. Come join us! Want to learn how to design a Tech Policy playbook? Are you interested in global tech transparency? Would you like to find out how shadow data affects you? Do you want to understand design’s impact on encrypted messaging? Are you looking for how to center human rights in usability? Join us and 1000s of others at MozFest 2023! This year’s event will be held in person in Amsterdam and online and the Superbloom team will be participating in five of the 360+ sessions. Intrigued? Read more in this post.&lt;/p&gt;
&lt;p&gt;You can register for MozFest &lt;a href=&#34;https://www.mozillafestival.org/&#34;&gt;here&lt;/a&gt;, and links to each of the sessions may found below.&lt;/p&gt;
&lt;h2 id=&#34;the-unfreedom-monitor-a-discussion-on-transparency-in-technology&#34;&gt;The unfreedom monitor: a discussion on transparency in technology&lt;/h2&gt;
&lt;p&gt;March 21, 2023 | 10-11am EDT | 2-3pm GMT&lt;/p&gt;
&lt;p&gt;Veszna Wessenauer and Sindhuri Nandhakumar&lt;/p&gt;
&lt;p&gt;For info and to book: &lt;a href=&#34;https://schedule.mozillafestival.org/session/N8ZFDM-1&#34;&gt;https://schedule.mozillafestival.org/session/N8ZFDM-1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The session’s goal is to provide space to have an interactive discussion on how greater transparency around the use and development of technologies, such as commercial spyware or algorithmic content moderation/ranking/curation, could help communities respond to the threats imposed by digital authoritarianism. The session will illustrate the utility of transparency through real-life events in environments where digital authoritarianism is growing.&lt;/p&gt;
&lt;p&gt;The session will build on the research gathered through The Unfreedom Monitor. It is a project to analyze, document, and report on the growing use of digital communications technology to advance authoritarian governance worldwide.&lt;/p&gt;
&lt;p&gt;We will introduce panelists from our research project, including from Brazil, Zimbabwe and Hong Kong, who will share country-specific insights based on the Unfreedom Monitor research project and their own experiences and showcase how their findings fit into the global context. But before they begin, we will ask participants to think on their own about what ‘transparency in technology’ means to them. The range of interpretations could be broad, which we welcome. Participants will also be encouraged to suggest anecdotal evidence, data and case studies that they think are relevant information for the panelists. They share their questions for the panelists based on this information, and our researchers will share their insights and respond to these questions. This allows for the discussion to be driven as much by participants as panelists.&lt;/p&gt;
&lt;p&gt;At the end of the session, participants will be asked to reflect and share how they might apply what the researchers have said and the panelists will be asked to talk about whether they learned anything new and revealing about what transparency means to both individuals and communities.&lt;/p&gt;
&lt;h2 id=&#34;bringing-light-to-shadow-data&#34;&gt;Bringing light to shadow data&lt;/h2&gt;
&lt;p&gt;March 21, 2023 | 3-4pm EDT | 7-8pm GMT&lt;/p&gt;
&lt;p&gt;Georgia Bullen, Susan Kennedy, Cameron Hickey and Shayne Longpre&lt;/p&gt;
&lt;p&gt;For info and to book: &lt;a href=&#34;https://schedule.mozillafestival.org/session/3WUYRK-1&#34;&gt;https://schedule.mozillafestival.org/session/3WUYRK-1&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;Shadow data is information about individuals that is collected and maintained by social media platforms, but is not necessarily visible or accessible to the individuals themselves. This can include data about online activity, personal preferences, and demographics, as well as data that is inferred or calculated. While some of this data is assembled with the explicit consent of the individual, much of it is obtained through other means, such as third-party data aggregation or machine learning model predictions and scoring. The production, collection, and maintenance of shadow data has significant implications for efforts to establish transparency about social media and for society broadly. Shadow data is a known unknown. We know it exists but we don’t know the scale and shape of it. We don’t know where it is used or why. Bringing greater transparency to the platforms that house our digital public square requires establishing a framework for bringing transparency to shadow data as well. During this conference session, participants will work together to identify and classify the different types of shadow data that can be inferred and maintained by social media platforms, and will discuss the potential implications of this data. They will also propose mechanisms for providing greater transparency about shadow data, including ways in which individuals can access and control their own data, as well as ways in which aggregate data can be made available to researchers and policymakers. Overall, the goal of this session is to bring greater awareness to the issue of shadow data and to encourage the development of approaches that prioritize individual privacy and control. By bringing light to shadow data, we can work towards a more transparent and equitable digital landscape.&lt;/p&gt;
&lt;h2 id=&#34;sender-unknown-designs-impacts-on-deception-and-trust-in-messaging&#34;&gt;Sender unknown: design&amp;rsquo;s impacts on deception and trust in messaging&lt;/h2&gt;
&lt;p&gt;March 21, 2023 | 3-4pm EDT | 7-8pm GMT&lt;/p&gt;
&lt;p&gt;Caroline Sinders and Justin Hendrix&lt;/p&gt;
&lt;p&gt;For info and to book:  &lt;a href=&#34;https://schedule.mozillafestival.org/session/7HAFGJ-1&#34;&gt;https://schedule.mozillafestival.org/session/7HAFGJ-1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Consumers are increasingly using encrypted messaging apps to share information, engage with one another, and conduct commerce. But while the promise of encrypted messaging is private communications and user control over the spread of personal information, the reality is more complicated. An overlapping and interconnected set of engineering, design, and system factors, coupled with varied user behaviors, create the conditions for individuals to subvert their own interests or the interests of their communities on encrypted apps.&lt;/p&gt;
&lt;p&gt;In this workshop, participants will collaboratively identify how design failures, dark patterns and adversarial behaviors by various parties may combine to produce malicious effects in encrypted messaging. Such malicious effects may be patterns that nudge users to share personal information or forward messages to insecure channels, suggestive user interfaces or flawed security mechanisms that can compromise security. What are the design choices app makers have made that lead to or confuse the user into making poor security decisions? Are there insecure apps that use security UI to look more secure than they are? How does this relate to content moderation capabilities on messaging apps? How do people end up compromising their own safety? What is the prevalence of these phenomena, and what are the policy solutions?&lt;/p&gt;
&lt;p&gt;This workshop is split into Two parts: Part 1 is a presentation on our preliminary research.&lt;/p&gt;
&lt;p&gt;In Part 2, the facilitators will break the participants into 2-3 groups. Each group is given a specific prompt or question to work on, and then everyone comes back together to share findings, questions, and suggestions. For example, one group may focus on messaging forwarding within Telegram or Signal, another group may focus on Facebook messaging when messages have tens and 100s of participants.&lt;/p&gt;
&lt;h2 id=&#34;designing-a-tech-policy-playbook-101-tools-and-resources-to-tackle-ogbv&#34;&gt;Designing a tech policy playbook 101: tools and resources to tackle OGBV&lt;/h2&gt;
&lt;p&gt;March 22, 2023 | 7am-8.30am EDT | 11am-12.30pm GMT&lt;/p&gt;
&lt;p&gt;Georgia Bullen, Ngọc Triệu, Ame Elliott, Katherine Townsend, Raashi Saxena, Candy Rodríguez, Bulanda Nkhowani and Victory Brown.&lt;/p&gt;
&lt;p&gt;For info and to book: &lt;a href=&#34;https://schedule.mozillafestival.org/session/K9RTVZ-1&#34;&gt;https://schedule.mozillafestival.org/session/K9RTVZ-1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Bringing design to tech policy can have material benefits for the safety and well-being of people on the web and beyond. Building on work from the last two years with the &lt;a href=&#34;https://webfoundation.org/&#34;&gt;Web Foundation&lt;/a&gt; and many global partners, we will share the &lt;a href=&#34;http://techlab.webfoundation.org/playbook/&#34;&gt;Tech Policy Design Lab (TPDL) Playbook&lt;/a&gt;: a framework that employs a multi-stakeholder collaboration and interactive design approach to gain consensus from a diverse perspective and tackle key tech policy problems with measurable results. &lt;/p&gt;
&lt;p&gt;The Tech Policy Design Lab (TPDL) playbook brings learnings from the first two TPDLs, led by the Web Foundation on &lt;a href=&#34;https://techlab.webfoundation.org/ogbv/overview&#34;&gt;Online Gender Based Violence (OGBV)&lt;/a&gt; and &lt;a href=&#34;https://techlab.webfoundation.org/deceptive-design/overview&#34;&gt;Deceptive Design&lt;/a&gt;, to focus on addressing the urgent challenges of Online Gender-Based Violence (OGBV).&lt;/p&gt;
&lt;p&gt;At Mozilla Festival this year, we are opening our process and invite everyone to join our co-design session who identifies as belonging to the global majority, is interested and/or is working on OGBV and abuses, deceptive design or similar issues, as well as anyone who wants to address tech policy issues in a multi-stakeholder way.&lt;/p&gt;
&lt;p&gt;Keeping the www open, safe and trusted, in a way that empowers everyone requires new ways of working to combat the polarization, normalization of threats, erosion of trust, and manipulative interactions threatening the internet. We believe there is power at the intersection of technology, policy, and design, and that bringing a design approach to policy problems can create positive change to make the web safe for everyone. &lt;/p&gt;
&lt;p&gt;The workshop will be hosted via Zoom and use digital collaboration tools (Google Docs and Miro).&lt;/p&gt;
&lt;h2 id=&#34;centering-human-rights-prioritizing-accessibility--privacy--usability&#34;&gt;Centering human rights: prioritizing accessibility + privacy + usability&lt;/h2&gt;
&lt;p&gt;March 24, 2023 | 3-4pm EDT | 7-8pm GMT&lt;/p&gt;
&lt;p&gt;Caroline Sinders and &lt;a href=&#34;mailto:natalie@open-archive.org&#34;&gt;Natalie Cadranel&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;For info and to book: &lt;a href=&#34;https://schedule.mozillafestival.org/session/MADFVK-1&#34;&gt;https://schedule.mozillafestival.org/session/MADFVK-1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;While best practices and standards for human-rights centered concepts are emerging in the computer science and tool-building spaces, very few have been created for the research and design fields. This session will help fill this gap by presenting a research and design methodology to those developing technologies to help marginalized communities. This work is designed to streamline the process of user research, promote human-rights centered design, and aid technologists who build tools, platforms, and services.&lt;/p&gt;
&lt;p&gt;It is challenging to ensure products or services are adaptive to the needs of a specific community’s privacy and safety, especially in cases where you are building a platform to help vulnerable communities or providing people with direct resources. In light of this, we developed the Human Rights Centered Design (HRCD) curriculum (humanrightscentered.design), which provides best practices, use cases, and knowledge from human rights activists, community organizers, and technologists from across the globe.&lt;/p&gt;
&lt;p&gt;In this session, we aim to share our curriculum, gather feedback from session participants, and learn from others seeking to adopt and standardize usability best practices when working on privacy-enhancing tools. To make the curriculum widely applicable, we will encourage participants to draw upon their previous practices and projects and share their experiences and suggestions. MozFest provides a unique opportunity to connect with like-minded groups, and we will use the session to find areas for collaboration and to discuss related projects.&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Georgia Bullen, Susan Kennedy, Raashi Saxena.&lt;/p&gt;
&lt;p&gt;Photo by Connor Ballard-Pateman | @PinotConoir.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Learnings From OTF Shutdowns Getdown Gathering 2022</title>
      <link>https://superbloom.design/learning/blog/learnings-from-the-otf-shutdowns-getdown-gathering-2022/</link>
      <pubDate>Thu, 02 Mar 2023 18:07:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/learnings-from-the-otf-shutdowns-getdown-gathering-2022/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/8231503306_e34dbafefb_hu_6384d046592a4aaf.jpg&#34; alt=&#34;laptop with the words &amp;ldquo;access denied&amp;rdquo; over a globe displaying on the screen&#34; width=&#34;740&#34; height=&#34;697&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;This blog has been cross posted by &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;, as part of their series on internet shutdowns. You can read our Co-Author&amp;rsquo;s blog about the event &lt;a href=&#34;https://okthanks.com/blog/2023/3/2/how-tech-teams-can-prepare-for-internet-shutdowns&#34;&gt;here&lt;/a&gt;.&lt;/em&gt;&lt;a href=&#34;https://okthanks.com/blog/2023/3/2/how-tech-teams-can-prepare-for-internet-shutdowns&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;key-takeaways&#34;&gt;Key Takeaways&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Technology interventions designed to be useful during shutdowns can learn a lot from crisis planning by focusing on normalizing use day to day of tools, and thinking about how people can get introduced to tools before they need them, rather than as a shutdown is happening&lt;/li&gt;
&lt;li&gt;Better information sharing and feedback among frontline support, technology and design teams, researchers and other key stakeholders can improve shared understanding of how we’re designing intervention and support tools&lt;/li&gt;
&lt;li&gt;Along with better information sharing, the methods to which tools and software offer users and those that support users, needs to be relevant and appropriate to their circumstances and access. Broadening the ways in which feedback is received can help to mitigate user feedback churn&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In October 2022, Open Technology Fund (OTF) brought together a group of around 50 technologists, researchers, usability experts, and digital security practitioners working on internet shutdowns. Together, the group engaged in many topics, ranging from understanding the lived experience of an internet shutdown to the challenges around technology interventions, and measuring and monitoring networks during a shutdown. An &lt;a href=&#34;https://www.accessnow.org/keepiton-faq/&#34;&gt;internet shutdown&lt;/a&gt; is when access to the internet is restricted, such that people are unable to use the internet or internet based services. This is an &lt;a href=&#34;https://citizenlab.ca/2014/08/2014-citizen-lab-summer-institute-monitoring-internet-openness-rights/&#34;&gt;information control&lt;/a&gt; tactic that is increasingly being used around the world to affect the free flow of information.&lt;/p&gt;
&lt;p&gt;The breakout group focused on better understanding the experience from the perspective of people — mapping out what happens as a shutdown occurs, what individuals do to find support, resilience, and seek to understand what’s happening. We talked through what it might look like to prepare and plan for shutdowns and how shutdowns affect people from marginalized groups within communities. We also approached these conversations from the perspective of how better understanding a person’s experience could impact the tools that are in development and in use to help people when a shutdown occurs. During the workshops, our community reiterated the need to learn from crisis response and emergency preparedness work, where a best practice is around scenario planning and practice, as well as ways to facilitate pre-work so that crisis situations are not a question of how to do something, but more about using the muscle memory developed in the planning process.&lt;/p&gt;
&lt;p&gt;As part of the workshop, we leveraged &lt;a href=&#34;https://servicedesigntools.org/tools/journey-map&#34;&gt;journey mapping&lt;/a&gt;, a design tool that allows usto think through the phases of the experience, what happens when, how people respond, what they interact with, and how that overall experience feels for an individual. Using this framework allowed us to identify opportunities and gaps where there could be improvements For example, when people need to be comfortable using potential technological interventions before they need them, so that they aren’t trying to make them work or install them for when a crisis unfolds. This also speaks to opportunities surrounding communications and marketing of tools and the onboarding experience as key for adoption of technology and day-to-day use, rather than purely in the event of a shutdown. For future events, we’re also thinking about using tools like &lt;a href=&#34;http://www.lucykimbell.com/stuff/Fieldstudio_SocialDesignMethodsMenu.pdf&#34;&gt;Storyworld&lt;/a&gt; and expanding on our &lt;a href=&#34;https://simplysecure.org/resources/persona-template-security.pdf&#34;&gt;persona templates&lt;/a&gt; to include important considerations for internet shutdowns, e.g. physical environment or emotional burdens, and generally for more resilient connectivity contexts.&lt;/p&gt;
&lt;p&gt;Another key theme in our learning is around how we can design tools to be more resilient to intermittent connectivity. This mindset shifts how we’re building tools to be more resilient technologically to the lack of internet connectivity, and how we think about design patterns and interfaces that aren’t dependent on connectivity to be understood. We’ve explored issues like this in our work around &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;patterns for decentralized applications&lt;/a&gt;, but there’s lots of work to be done to make it more commonplace that our technology doesn’t depend on a high speed internet connection to be usable. &lt;/p&gt;
&lt;p&gt;Knowing when and how to receive feedback on these tools is critical. Our expectations are that users and digital security trainers will use the methods the tool teams present. However, we anticipate that underserved communities may experience frustration with repetition from users that are shared across multiple services nad tools. These tool teams can better understand safe, secure ways of collecting and sharing user insight to unburden users from repetitive feedback cycles. &lt;/p&gt;
&lt;p&gt;We are excited to work together with the community to continue to improve the interventions available. Some ideas we are considering include: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Developing more offline/local-first design patterns&lt;/li&gt;
&lt;li&gt;Working as a community to create testing and simulation environments, which could also facilitate the development of emergency response toolkits and processes&lt;/li&gt;
&lt;li&gt;Doing more research and research synthesis to help connect learnings from different communities and regions to each other and to the broader community&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you are working on problems like these and want to connect or get involved, we’d love to hear more and get connected to share ideas.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Introducing USER: Usable Software Ecosystem Research</title>
      <link>https://superbloom.design/learning/blog/introducing-user-usable-software-ecosystem-research/</link>
      <pubDate>Tue, 14 Feb 2023 14:02:50 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/introducing-user-usable-software-ecosystem-research/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/fosdic_hu_3e48d7f59a842a01.jpg&#34; alt=&#34;A group of Census Bureau researches talking and making notes behind a full room of 50&amp;rsquo;s era computer machinery.&#34; width=&#34;740&#34; height=&#34;482&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Computer programs have long been used for research purposes. The header image shows U.S. Census Bureau employees using the Film Optical Sensing Device for Input to Computers (FOSDIC) for census data translation and storage. &lt;a href=&#34;https://www.census.gov/history/www/innovations/technology/fosdic.html&#34;&gt;Read more about FOSDIC history here&lt;/a&gt;. Image attribution: U.S. Census Bureau employees, Public domain, via &lt;a href=&#34;https://commons.wikimedia.org/wiki/File:Film_Optical_Sensing_Device_for_Input_to_Computers_(FOSDIC).jpg&#34;&gt;Wikimedia Commons&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;This post is part one in a series of in-progress research updates from the USER team. Stay tuned for more!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In November, we began an exciting new project funded by the &lt;a href=&#34;https://sloan.org/&#34;&gt;Sloan Foundation&lt;/a&gt;. We’ve named it “USER” — short for &lt;strong&gt;Usable Software Ecosystem Research&lt;/strong&gt; – a research initiative that explores how open source scientific and research software (S&amp;amp;R OSS) teams understand, consider, and undertake usability and design opportunities in their projects. We at Superbloom have dedicated ourselves to understanding and sharing how designers work and how design is practiced within open source teams and communities for years (see &lt;a href=&#34;https://opensourcedesign.net/&#34;&gt;Open Source Design&lt;/a&gt; and our podcasts on &lt;a href=&#34;https://sosdesign.sustainoss.org/&#34;&gt;Sustaining Open Source Design&lt;/a&gt;), but the USER project presents a new opportunity for us to dig into these questions within academic and scientific communities in particular. It’s also an invitation to reflect on our own experiences of doing design and usability work across the open source software (OSS) ecosystem.&lt;/p&gt;
&lt;p&gt;Science and research communities have plenty of overlap with other OSS tools and projects we’ve worked with in the past, but they also present unique perspectives and challenges around sustainability and design in open source. To begin, we completed a solid month of desk research and an ecosystem scan. We familiarized ourselves with relevant literature on design, usability, OSS, and scientific software, and started compiling a database of people and projects to map the diversity of the S&amp;amp;R OSS world. We plan to publish an ecosystem map with our other outputs later this year.&lt;/p&gt;
&lt;p&gt;While the USER research team delved into the papers, blogs, repos and written accounts of key terms and subjects, we also made social connections with key S&amp;amp;R OSS funders, projects, institutions and individuals across conferences and community events like CZI Open Science and OpenRIT. We’ve learned from past design research projects in OSS that important context and nuance is revealed through relationship building, so establishing these connections contributed to our exploratory research practice. Developing an understanding of and learning to participate in the culture and community of OSS, not unlike how OSS itself gets built and maintained, comes from connecting with other people who value the work. From these connections, we built relationships that fed the research activities and also allowed our design researchers and the scientists, researchers and designers we met to speak on equitable, social terms and gather initial human-centered insights.&lt;/p&gt;
&lt;p&gt;Our research and outreach at conferences helped to inform preliminary findings and hypotheses, creating the foundation for our published &lt;a href=&#34;https://github.com/simplysecure/USER_project/blob/main/Research%20Phase/user-survey.md&#34;&gt;survey&lt;/a&gt;. We invited the project contributors we’d met in person and those we’d identified in our ecosystem research to participate, and shared in communication channels and email lists frequented by communities of interest. While this online survey collected responses from the science and research open source community at large, we were simultaneously creating our &lt;a href=&#34;https://github.com/simplysecure/USER_project/blob/main/Research%20Phase/interview-guide-and-script.md&#34;&gt;Interview Guide&lt;/a&gt; collaboratively between 4 team members. Our interview script ended up at 32 questions total across 5 key themes, intended to be semi-structured and adaptable to a given conversation with a participant. Needless to say, with each participant we could have done many more interviews, as there was so much to talk about across these key themes - If only time permitted and interview fatigue wasn’t something we and our participants battled with!&lt;/p&gt;
&lt;p&gt;In December, we started conducting interviews and we’re wrapping them up in February 2023, and are expecting to end up with 25-30 interviews. We have been speaking with a broad range of maintainers, developers, designers, scientists, researchers, funders, OSPOs and stakeholders – anyone who is involved with creating and maintaining open source scientific &amp;amp; research software. The &lt;a href=&#34;https://github.com/simplysecure/USER_project/blob/main/Research%20Phase/interview-guide-and-script.md&#34;&gt;Interview Guide&lt;/a&gt; sought to gain further insight into:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How norms in academic, science, and/or open source working environments affect the choices teams make around their users and different kinds of design interventions.&lt;/li&gt;
&lt;li&gt;How team dynamics and trust affects those choices.&lt;/li&gt;
&lt;li&gt;What teams would need to be interested in or able to prioritize usability and design in their work.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These activities so far – ecosystem research, conference attendance, the survey, and interviews – have exposed us to a diverse network of programmers, community managers, stakeholders, and designers who all contribute to the S&amp;amp;R OSS space. These people are volunteers, full time academics, government employees, students, and more. We’ve learned so much from them, not only about how science and technology meet, merge, and occasionally clash in software projects, but about how communities of users and contributors dedicate themselves to writing documentation to improve usability and accessibility, how the sustainability of OS projects shifts across contexts and institutions, and what scientists and designers need to understand better about each other. We’re so excited to be moving into our synthesis phase this week, and we will share more preliminary themes and findings as we work.&lt;/p&gt;
&lt;p&gt;Keep an eye on our blog and on our &lt;a href=&#34;https://github.com/simplysecure/USER_project&#34;&gt;open repo&lt;/a&gt; for further updates! Also, feel free to reach out to us at &lt;a href=&#34;mailto:user-project@superbloom.design&#34;&gt;user-project@superbloom.design&lt;/a&gt; if you would like to learn more about this work.&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Contributors: Eriol Fox, Katie Wilson, Susan Kennedy, Ngọc Triệu, Jan Dittrich&lt;/p&gt;
&lt;p&gt;With support from the &lt;a href=&#34;https://sloan.org/&#34;&gt;Sloan Foundation&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;tags&#34;&gt;Tags&lt;/h2&gt;
&lt;p&gt;Open source, usability, research&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Tea Time: Trust and Responsibility</title>
      <link>https://superbloom.design/learning/collections/tea-time/</link>
      <pubDate>Fri, 10 Feb 2023 15:08:59 -0500</pubDate>
      <guid>https://superbloom.design/learning/collections/tea-time/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Security, Privacy and Transparency</title>
      <link>https://superbloom.design/learning/collections/security-privacy-transparency/</link>
      <pubDate>Fri, 10 Feb 2023 15:04:26 -0500</pubDate>
      <guid>https://superbloom.design/learning/collections/security-privacy-transparency/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Respectful Research</title>
      <link>https://superbloom.design/learning/collections/respectful-research/</link>
      <pubDate>Fri, 10 Feb 2023 14:59:13 -0500</pubDate>
      <guid>https://superbloom.design/learning/collections/respectful-research/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Design Spots</title>
      <link>https://superbloom.design/learning/collections/design-spots/</link>
      <pubDate>Fri, 10 Feb 2023 14:46:06 -0500</pubDate>
      <guid>https://superbloom.design/learning/collections/design-spots/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Design Under Pressure</title>
      <link>https://superbloom.design/learning/collections/design-under-pressure/</link>
      <pubDate>Fri, 10 Feb 2023 14:46:06 -0500</pubDate>
      <guid>https://superbloom.design/learning/collections/design-under-pressure/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Internet of Things</title>
      <link>https://superbloom.design/learning/collections/internet-of-things/</link>
      <pubDate>Fri, 10 Feb 2023 14:46:06 -0500</pubDate>
      <guid>https://superbloom.design/learning/collections/internet-of-things/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Branding</title>
      <link>https://superbloom.design/learning/collections/branding/</link>
      <pubDate>Fri, 10 Feb 2023 14:34:26 -0500</pubDate>
      <guid>https://superbloom.design/learning/collections/branding/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Artifical Intelligence</title>
      <link>https://superbloom.design/learning/collections/artificial-intelligence/</link>
      <pubDate>Fri, 10 Feb 2023 14:29:30 -0500</pubDate>
      <guid>https://superbloom.design/learning/collections/artificial-intelligence/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Least Authority DRL Project</title>
      <link>https://superbloom.design/work/projects/least-authority-drl-project/</link>
      <pubDate>Tue, 31 Jan 2023 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/work/projects/least-authority-drl-project/</guid>
      <description></description>
    </item>
    
    <item>
      <title>2022 Superbloom Highlight Reel</title>
      <link>https://superbloom.design/learning/blog/2022-superbloom-highlight-reel/</link>
      <pubDate>Fri, 16 Dec 2022 19:22:10 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/2022-superbloom-highlight-reel/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/2022-eoy-header_hu_866943144af2d102.png&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;p&gt;2022 was a year full of shifts, adaptations and evolutions for so many in our community. For us, we launched a new identity, welcomed four new team members and three new fiscally sponsored projects, and partnered with many new organizations and funders. And, for many on our team, this year presented several opportunities to meet for the first time in person. These markers of growth and evolution could not have happened without the continued support from our community. &lt;/p&gt;
&lt;p&gt;That’s why we’re so excited to share with all of you Superbloom’s 2022 highlight reel - just some of the many projects we worked on, resources we developed, and events we participated in.&lt;/p&gt;
&lt;h2 id=&#34;but-first-icymi-simply-secure---superbloom&#34;&gt;But first, ICYMI: Simply Secure -&amp;gt; Superbloom&lt;/h2&gt;
&lt;p&gt;One of our proudest moments from 2022 was the transition from ‘Simply Secure’ to ‘Superbloom.’ Our new brand was the culmination of a two-year, in-depth collaboration with our community. Read more about the &lt;a href=&#34;https://superbloom.design/learning/blog/introducing-superbloom/&#34;&gt;launch&lt;/a&gt; and &lt;a href=&#34;https://superbloom.design/learning/blog/whats-next-for-simply-secure-part-3-how-we-built-superbloom/&#34;&gt;branding&lt;/a&gt; on our blog, and get some &lt;a href=&#34;https://www.redbubble.com/people/Superbloom-Dsgn/shop&#34;&gt;Superbloom swag&lt;/a&gt; at our newly minted swag store. All proceeds directly support our nonprofit mission to change who technology serves. &lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://lh4.googleusercontent.com/jC3AxrlFZr4Qj5kga9s3JuACxhXkVC6hRxRd8bvR-6GJGzqsxocbiQLEBe0GWpoBvVNe6wdVwldQ-HUHMyWz_nhZ21OCyCAtK2mh2tKsPsGKR1TqIpNGkXRR3BEusvR3zZGR0JVxyHVuJHjALaFmy4vIdv9mRrtUdsaRVO8fUEy_CL_hbVuEiXmnTIbCkQ&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;themes-tools-partners-impacts&#34;&gt;Themes, Tools, Partners, Impacts&lt;/h2&gt;
&lt;p&gt;This year, we’ve tackled some particularly sticky design problems across security, policy, and community. Here’s a handful of themes from our work this past year. &lt;/p&gt;
&lt;h3 id=&#34;usability-as-critical-infrastructure&#34;&gt;Usability as Critical Infrastructure&lt;/h3&gt;
&lt;p&gt;No matter how secure the code may be, a tool is not truly safe unless it is easy to use - and security is most important for those highest at risk. This is why we believe usability should be seen as critical infrastructure. Through partnerships such as the Open Technology Fund &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Secure Usability Lab&lt;/a&gt;, the &lt;a href=&#34;https://usable.tools/blog/2020-10-01-uxfund2020/&#34;&gt;UXFund&lt;/a&gt;, and &lt;a href=&#34;https://prototypefund.de/en/&#34;&gt;Prototype Fund&lt;/a&gt;, we help open source software teams better understand their users and improve usability. With &lt;a href=&#34;https://www.digital-democracy.org/&#34;&gt;Digital Democracy&lt;/a&gt;, we helped instill user-centered research practices to make essential improvements to their mapping app for indigenous communities, &lt;a href=&#34;https://www.digital-democracy.org/mapeo/&#34;&gt;Mapeo&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;related-blog-posts&#34;&gt;&lt;em&gt;Related Blog Posts:&lt;/em&gt;&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/improving-onboarding-usability-for-different-user-groups/&#34;&gt;All Aboard: Getting Mainstream Users Up and Running on Decentralized Systems&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/hey-whose-keys-are-these/&#34;&gt;Hey, whose keys are these? Guiding Mailvelope users through the headaches of key management&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/keeping-everyone-safe-quick-user-oriented-problem-solving-with-mapeo/&#34;&gt;Keeping Everyone Safe: Quick, User-oriented Problem-solving with Mapeo&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/finding-the-balance-adding-support-for-organization-wide-pgp-keys-to-mailvelope/&#34;&gt;Finding the Balance: Adding support for organization-wide PGP keys to Mailvelope&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;community-energy&#34;&gt;Community Energy&lt;/h3&gt;
&lt;p&gt;This year, you may have seen us around (earlier as Simply Secure, more recently as Superbloom). We’ve attended, presented, and workshopped at many community events, such as &lt;a href=&#34;https://www.mozillafestival.org/en/&#34;&gt;MozFest&lt;/a&gt;, &lt;a href=&#34;https://www.rightscon.org/&#34;&gt;RightsCon&lt;/a&gt;, &lt;a href=&#34;https://dwebcamp.org/&#34;&gt;DWeb Camp&lt;/a&gt;, &lt;a href=&#34;https://www.atlanticcouncil.org/programs/digital-forensic-research-lab/360os/360os-2022/&#34;&gt;360 Open/Summit&lt;/a&gt;, and &lt;a href=&#34;https://2022.allthingsopen.org/&#34;&gt;All Things Open&lt;/a&gt;. We don’t just share our work - we’ve been harnessing community energy in-person and online to collaborate, fill gaps, identify needs and synthesize together. &lt;/p&gt;
&lt;p&gt;At MozFest 2022, we convened the community to ‘Reimagine Consent’ by curating examples of dark patterns in the wild with examples of empowered consent experiences, proactively imagining how we can shift power back to end-users. And together with &lt;a href=&#34;https://www.reset.tech/&#34;&gt;Reset.tech&lt;/a&gt;, we designed gatherings bringing together different stakeholders on topics such as evidence gathering for strategic litigation, and how to best develop an index for platform transparency.&lt;/p&gt;
&lt;h4 id=&#34;related-blog-posts-and-resources&#34;&gt;&lt;em&gt;Related Blog Posts and Resources:&lt;/em&gt;&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/join-us-at-rightscon-2022/&#34;&gt;Join us at RightsCon 2022&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/open-call-submissions-for-reimagining-digital-consent-a-discussion-gallery-exhibition-at-mozfest-2022/&#34;&gt;Submissions for “Reimagining Digital Consent: A Discussion &amp;amp; Gallery Exhibition” at MozFest 2022&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/join-us-at-mozfest-2022/&#34;&gt;Join Us at MozFest 2022&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://airtable.com/shrZSumhBM6DSyILb/tblkHBbRqiAaV22gs&#34;&gt;Reimaging Consent Gallery, MozFest 2022&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;sharing-tools--processes&#34;&gt;Sharing Tools &amp;amp; Processes&lt;/h3&gt;
&lt;p&gt;Creating open resources is at the heart of what we do. Human-centered design approaches allow us to co-design tools and processes alongside the communities that will use and benefit from them. &lt;/p&gt;
&lt;p&gt;Partnering with &lt;a href=&#34;https://internews.org/&#34;&gt;Internews&lt;/a&gt; and &lt;a href=&#34;https://www.okthanks.studio/&#34;&gt;Okthanks&lt;/a&gt;, we created a set of visual and interactive resources on &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/&#34;&gt;user testing for open source developers&lt;/a&gt;. Continuing to promote developer/designer collaboration, we began a project to study how scientific open source software projects think about their users, work with designers, and prioritize usability thanks to a grant by &lt;a href=&#34;https://sloan.org/&#34;&gt;Sloan Foundation&lt;/a&gt;. And earlier this year, we launched &lt;a href=&#34;https://buildingblocks.simplysecure.org/&#34;&gt;Building Blocks&lt;/a&gt;, a toolkit for funders to better understand and support critical digital infrastructure projects to promote sustainability.&lt;/p&gt;
&lt;h4 id=&#34;related-blog-posts-and-resources-1&#34;&gt;&lt;em&gt;Related Blog Posts and Resources:&lt;/em&gt;&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/building-blocks-funding-digital-infrastructure-from-the-ground-up/&#34;&gt;Funding Digital Infrastructure From the Ground Up&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://buildingblocks.simplysecure.org/&#34;&gt;Building Blocks for Funding Digital Infrastructure&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://sprblm.github.io/devs-guide-to/about/&#34;&gt;A Dev’s Guide to User Testing&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;looking-ahead&#34;&gt;Looking Ahead&lt;/h2&gt;
&lt;p&gt;We have a lot to look forward to in 2023! Here’s just a handful of things we have coming up:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;We will be publishing research on challenges for designers in creating GDPR-compliant websites.&lt;/li&gt;
&lt;li&gt;Co-authoring a report synthesizing the outcomes and insights developed at a workshop on defining platform transparency, in partnership with &lt;a href=&#34;https://www.junkipedia.org/&#34;&gt;Junkipedia&lt;/a&gt; and &lt;a href=&#34;https://sites.brown.edu/informationfutures/&#34;&gt;Information Futures Lab&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Sharing out from our work on addressing deceptive design in partnership with the &lt;a href=&#34;https://webfoundation.org/&#34;&gt;World Wide Web Foundation&lt;/a&gt; &lt;a href=&#34;https://webfoundation.org/2021/04/tech-policy-design-lab-pilot-building-solutions-to-tackle-online-abuse-of-women/&#34;&gt;Tech Policy Design Lab&lt;/a&gt; and &lt;a href=&#34;https://3x3.co/&#34;&gt;3X3.co&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;And building on that work, we’re excited to be co-designing an open source tool kit based on the &lt;a href=&#34;https://webfoundation.org/&#34;&gt;Web Foundation&lt;/a&gt; &lt;a href=&#34;https://webfoundation.org/2021/04/tech-policy-design-lab-pilot-building-solutions-to-tackle-online-abuse-of-women/&#34;&gt;Tech Policy Design Lab&lt;/a&gt; and making it accessible and beneficial to global communities.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And as always, we’re looking to partner with internet freedom and open source projects on secure usability, design, and recently - content strategy. If you’re interested, you can get design and usability support from us via the Open Technology Fund Secure Usability and Learning Labs. Or just reach out!&lt;/p&gt;
&lt;p&gt;Last-but-not-least, stay tuned for our new website. It will include our extensive new brand identity, as well as a shiny new resource library. Check out the transitional site at our future domain, &lt;a href=&#34;https://superbloom.design/&#34;&gt;superbloom.design&lt;/a&gt;. &lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Susan Kennedy (copy), ngọc triệu (image).&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>What&#39;s Next For &#39;Simply Secure&#39;? Part 3: How We Built Superbloom</title>
      <link>https://superbloom.design/learning/blog/whats-next-for-simply-secure-part-3-how-we-built-superbloom/</link>
      <pubDate>Wed, 19 Oct 2022 18:12:27 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/whats-next-for-simply-secure-part-3-how-we-built-superbloom/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/refresh-blog-3-final_hu_adefb402ff15e58f.jpg&#34; width=&#34;740&#34; height=&#34;503&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Read our previous posts in the &amp;ldquo;What&amp;rsquo;s next for &amp;lsquo;Simply Secure&amp;rsquo;?&amp;rdquo; identity series: &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey/&#34;&gt;Part 1&lt;/a&gt; of our identity story will give you some background about why we chose to rebrand ourselves; &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-refreshing-our-name-and-identity-part-2/&#34;&gt;Part 2&lt;/a&gt; introduces our community-based approach.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;As you may have heard, we have big news: &lt;a href=&#34;https://superbloom.design/learning/blog/introducing-superbloom&#34;&gt;Simply Secure is now Superbloom&lt;/a&gt;. When we last reported on our progress, we had figured out &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-refreshing-our-name-and-identity-part-2/&#34;&gt;what values we were trying to get across and who we were&lt;/a&gt;. In this post, we tell the story of how we decided to express our organization visually. We worked to connect the feeling to imagery with &lt;a href=&#34;http://hanna-kim.com/&#34;&gt;visual designer Hanna Kim&lt;/a&gt;, and we&amp;rsquo;re excited to share with you the shape that she gave to our identity. Building off of Hanna’s work, we have developed a full design system that we’re using to reintroduce ourselves to the world and bring Superbloom’s work to life in the years to come.&lt;/p&gt;
&lt;h2 id=&#34;building-our-visual-identity-mixing-matching-and-staying-grounded&#34;&gt;Building our visual identity: mixing, matching, and staying grounded&lt;/h2&gt;
&lt;h3 id=&#34;first-explorations-with-our-community&#34;&gt;First explorations with our community&lt;/h3&gt;
&lt;p&gt;We first began the process of exploring visuals during &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-refreshing-our-name-and-identity-part-2/&#34;&gt;our community workshops&lt;/a&gt;. We scoured the web for images that matched the qualities we’d identified in the workshop, then we grouped the visuals into three categories: journey, with images of travel and maps; building, with images of layers, patterns, and blocks; and ecology, with nature images such as mycelium and science illustration.&lt;/p&gt;
&lt;h3 id=&#34;finding-a-theme&#34;&gt;Finding a theme&lt;/h3&gt;
&lt;p&gt;Even though our work isn’t about nature or the outdoors, we noticed that we were consistently drawn to organic images that invoked &amp;ldquo;down-to-earth&amp;rdquo; – a phrase that came up several times in our foundational collaborative design process. But we also wanted to incorporate technology: images showing architecture, systems, and patterns kept showing up in our mood boards.&lt;/p&gt;
&lt;p&gt;Hanna dove into those boards and designed three different themes for a visual identity unique to our organization, which ended up being the basis for our visual look and feel: “Down to earth,” “Collage &amp;amp; assemblage,” and “The human experience.” These themes helped us understand that our identity should be organic, energetic, and approachable, with people at the center. We needed this exploratory process to start making decisions – not just about our colors and logo, but about our name, tagline, and our entire identity.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/down-to-earth_hu_4a5f18562b630c18.png&#34; width=&#34;740&#34; height=&#34;740&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Visual inspiration for the theme “Down to earth,” drawing  from the artwork of &lt;a href=&#34;https://en.wikipedia.org/wiki/Ernst_Haeckel&#34;&gt;Ernst Haeckel&lt;/a&gt; and &lt;a href=&#34;https://fromkeetra.com/&#34;&gt;Keetra Dean Dixon&lt;/a&gt;, as well as sediment layers and grain texture.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/collage_hu_929483571b03de3c.png&#34; width=&#34;740&#34; height=&#34;740&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Visual inspiration for the theme “Collage &amp;amp; assemblage,” drawing from the artwork of Richard Hamilton, &lt;a href=&#34;https://www.pacegallery.com/artists/louise-nevelson/&#34;&gt;Louise Nevelson&lt;/a&gt;, &lt;a href=&#34;https://www.sarahsze.com/&#34;&gt;Sarah Sze&lt;/a&gt;, &lt;a href=&#34;https://www.anthonygerace.co.uk/&#34;&gt;Anthony Gerace&lt;/a&gt;, &lt;a href=&#34;https://kanghee.kim/&#34;&gt;Kanghee Kim&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/human-experience_hu_abe879b58ad66112.png&#34; width=&#34;740&#34; height=&#34;740&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Visual inspiration for the theme “The human experience,” drawing from works by &lt;a href=&#34;https://coopercolegallery.com/artist/geoff-mcfetridge/&#34;&gt;Geoff McFetridge&lt;/a&gt;, &lt;a href=&#34;http://taeyoonchoi.com/&#34;&gt;Taeyoon Choi&lt;/a&gt;, and the &lt;a href=&#34;https://artbma.org/about/our-brand-story/&#34;&gt;Baltimore Museum of Art&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;building-our-name-staying-friendly-and-trustworthy-precise-and-expansive&#34;&gt;Building our name: staying friendly and trustworthy, precise and expansive&lt;/h2&gt;
&lt;p&gt;Alongside our explorations into a visual identity that suited us, we undertook a related journey to rework our name. Simply Secure &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey/&#34;&gt;didn’t fit us any more&lt;/a&gt; for many reasons. It described our work in a very limited way, which made it hard for us to communicate the breadth of our offerings and expertise to our partners and our community. &lt;/p&gt;
&lt;p&gt;To say naming is difficult is an understatement!  But things changed when Hanna found one image in the mood boarding process: a patchwork of riotous color on a mountainside. It was a superbloom - a mass blossoming event in the desert of the west coast of North America. Some of our Californian team members instantly recognized it and added the name “Superbloom” on our list of name ideas, and we just kept coming back to it. “We’re Superbloom,” we tried saying. “We work at Superbloom.” “This report was authored by Superbloom.” It felt optimistic, energetic, and easy to say – and it passed legal review. We had it!&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/wildsuperbloom_hu_ce2e51d530c4da8c.jpg&#34; width=&#34;740&#34; height=&#34;506&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;A superbloom at Carrizo Plain National Monument. Source: &lt;a href=&#34;https://www.flickr.com/photos/blmcalifornia/33688792841&#34;&gt;https://www.flickr.com/photos/blmcalifornia/33688792841&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;A superbloom is a rare desert botanical phenomenon in which an unusually high proportion of wildflowers whose seeds have lain dormant in desert soil germinate and blossom at roughly the same time.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;we-are-superbloom-changing-who-technology-serves&#34;&gt;We are Superbloom. Changing who technology serves.&lt;/h2&gt;
&lt;p&gt;While our new name gets the spotlight, our tagline gave us the confidence to choose it. The name doesn’t actually describe what we do; it evokes a feeling. The tagline, on the other hand, complements our name by giving a literal description of who we are. &lt;/p&gt;
&lt;p&gt;Taglines have a lot of demands on them! We needed something clear, people-centered, authentic, and friendly, all while conveying our mission and giving us room to grow. We mixed and matched words, like a digital version of magnetic poetry, until we had a combination that scored high on all these criteria: Superbloom – changing who technology serves.&lt;/p&gt;
&lt;h2 id=&#34;developing-the-superbloom-design-system&#34;&gt;Developing the Superbloom design system&lt;/h2&gt;
&lt;h3 id=&#34;the-logo&#34;&gt;The Logo&lt;/h3&gt;
&lt;p&gt;Condensing complexity into a single recognizable graphic was a challenging and sophisticated graphic design task. We needed Hanna Kim’s expertise and inspiration - when she came up with the asterisk, we were excited from the start. &lt;/p&gt;
&lt;p&gt;The asterisk is rich in symbolism:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Privacy and hidden information: when typing a password, characters may be obscured with an asterisk.&lt;/li&gt;
&lt;li&gt;Depth and detail: when an asterisk appears at the end of a sentence, it leads to a footnote explaining more. In several programming languages, asterisks denote comments.&lt;/li&gt;
&lt;li&gt;Flourishing and blossoming: the asterisk resembles a flower, pointing to our name, Superbloom.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/logo_hu_2b702e5cf362cbdd.png&#34; width=&#34;740&#34; height=&#34;914&#34;&gt;
&lt;/p&gt;
&lt;p&gt;As multilayered as the asterisk is, though, it was missing one important aspect: our &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-refreshing-our-name-and-identity-part-2/&#34;&gt;community-oriented, human-centered focus&lt;/a&gt;. Hanna built that into her rendering of the asterisk by making the logo creation into a participatory exercise.&lt;/p&gt;
&lt;p&gt;We asked team members, committee members, and board members to contribute and co-design with us by submitting their hand drawn asterisks. The submissions were combined to form the organization&amp;rsquo;s logo, symbolizing the group effort and contribution. In this way, we have a logo born from the community.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/communityasterisks_hu_a42ae98d0c9b80de.png&#34; width=&#34;740&#34; height=&#34;357&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Our collection of hand drawn asterisks submitted by our community.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/asterisk-_hu_26b856245a03264a.png&#34; width=&#34;740&#34; height=&#34;723&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;A collective 10-point asterisk was created by fusing together each member’s strokes like puzzle pieces, creating a composite 10-point asterisk made up of all of our handwriting.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;colors-found-in-nature&#34;&gt;Colors: Found in nature&lt;/h3&gt;
&lt;p&gt;Following the findings from our moodboarding exercises, our colors are found in nature. Though saturated, they are more muted than neon or web-based colors, friendlier for human eyes. They have grainy textures that look like pixels — though they’ll usually appear on a screen, they welcome human touch.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/colorpalette_hu_3d3a9a9d8ae7394a.png&#34; width=&#34;740&#34; height=&#34;615&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The Superbloom color palette&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;typeface-jetbrains-mono&#34;&gt;Typeface: JetBrains Mono&lt;/h3&gt;
&lt;p&gt;We chose &lt;a href=&#34;https://www.jetbrains.com/lp/mono/&#34;&gt;JetBrains Mono&lt;/a&gt; in our logotype to add a techy-touch, balancing out the hand-drawn asterisk. JetBrains, a monospace font, is made for reading code. We liked that it is taller than some monospace fonts, improving accessibility and readability. To cap it off, JetBrains Mono is free &amp;amp; open source.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/typeface_hu_afbf40d2d8777da4.png&#34; width=&#34;740&#34; height=&#34;886&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The Superbloom typeface is JetBrains Mono.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;graphics-human-hands-doing-things&#34;&gt;Graphics: Human hands doing things&lt;/h3&gt;
&lt;p&gt;We’ve punctuated our name, tagline, logo, and typeface with a human touch: line drawings of hands doing things, penned by our very own team member Molly Wilson. To us, this style combined the best of who we are and what our visual exploration brought forward: we’re doers, focused on the human experience, with a “down to earth” energy. These hands represent the human experiences, ideas, and lives that sustain a safer and healthier digital world – they are personal and full of energy. They keep us grounded in the people that power and inspire Superbloom. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/hands_hu_e17913c372fafcb4.png&#34; width=&#34;740&#34; height=&#34;536&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;lessons-we-learned&#34;&gt;Lessons we learned &lt;/h2&gt;
&lt;h3 id=&#34;make-feedback-central-to-the-process&#34;&gt;Make feedback central to the process&lt;/h3&gt;
&lt;p&gt;Most design project planning starts with deliverables: when will the logo be done? What about the color scheme? We took a different project management approach in order to incorporate insights from our team and community at every stage. By starting with the feedback loops we needed, other project pieces fell right into place. &lt;/p&gt;
&lt;h3 id=&#34;go-slowly-until-it-feels-right&#34;&gt;Go slowly until it feels right&lt;/h3&gt;
&lt;p&gt;Even with a great list of heuristics and an afternoon set aside to discuss name or tagline ideas, we weren’t always able to land on “the one”, and even though this sometimes felt dispiriting, we were careful not to rush the process. If we felt stuck, moving to another area – the name, the tagline, or the visuals – often gave us a much-needed creative jolt. &lt;/p&gt;
&lt;h3 id=&#34;explain-your-instincts&#34;&gt;Explain your instincts&lt;/h3&gt;
&lt;p&gt;Creating lists of criteria helped us take personal taste out of the equation. We all have a certain aesthetic and our own likes and dislikes, but we needed to set them aside; this identity is meant to be bigger than us and serve the organization well into the future.To facilitate this, we requested that feedback follow the framework: “I think X fits because Y”. &lt;/p&gt;
&lt;h3 id=&#34;always-remember-the-foundation&#34;&gt;Always remember the foundation&lt;/h3&gt;
&lt;p&gt;Whenever we felt like we’d lost our way, we went back to the attributes we’d established in our community workshop.After all, our new brand is a communication tool, and those attributes are the story it needs to tell – using pictures and words, with letters, colors, and symbols. We think Superbloom’s new identity tells the story of us, and we hope you do, too. &lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Team: Georgia Bullen, Melissa Huerta, Molly Wilson, Kelsey Smith, Hanna Kim, Susan Kennedy, Katie Wilson, Philliph Drummond, ngọc triệu &lt;/p&gt;
&lt;p&gt;Our new visual identity was developed in collaboration with a host of partners, using a community-based design approach. Thank you for contributing!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Simply Secure team &amp;amp; alumni: Georgia Bullen, Cade Diehm, Ame Elliott, Eriol Fox, Melissa Huerta, Susan Kennedy, Rae McKelvey, Nicola Pratt, Piper Ru, Kelsey Smith, ngọc triệu, Eileen Wagner, Katie Wilson, Molly Wilson, Carissa Yao, Philliph Drummond, Aaron Brunmeier, Kami Joseph&lt;/li&gt;
&lt;li&gt;Our rebrand committee: Jochai Ben-Avie, Peter Bihr, Sage Cheng, Antonela Debiasi, Eriol Fox, Allen Gunn, Julia Kloiber, Niels ten Oever, Ttcat, Kirstie Whitaker&lt;/li&gt;
&lt;li&gt;Board of Directors, current and recent alumni: Ben Scott, Sara “Scout” Sinclair Brody, Dorothy Chou, Jackie Lu, Jasmine McNealy&lt;/li&gt;
&lt;li&gt;Visual designer: Hanna Kim&lt;/li&gt;
&lt;li&gt;Co-Design Advisor: Una Lee&lt;/li&gt;
&lt;li&gt;Writing consultant: John Stith&lt;/li&gt;
&lt;li&gt;Transformation Coach: Vanessa Rhinesmith&lt;/li&gt;
&lt;li&gt;Legal team&lt;/li&gt;
&lt;li&gt;Survey respondents&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Introducing Superbloom</title>
      <link>https://superbloom.design/learning/blog/introducing-superbloom/</link>
      <pubDate>Wed, 19 Oct 2022 17:58:11 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/introducing-superbloom/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/ss-to-sb_hu_e218748f5e6fd1ba.gif&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Two years ago, Simply Secure &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey/&#34;&gt;asked our community&lt;/a&gt; for feedback about how our brand and name communicate our identity. The results of the survey were conclusive: We had outgrown our name, and our branding was too playful for our mission. We needed a new approach to reflect the serious work that we do.&lt;/p&gt;
&lt;p&gt;So we launched a &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-refreshing-our-name-and-identity-part-2/&#34;&gt;co-design process&lt;/a&gt;—what we called a brand refresh.&lt;/p&gt;
&lt;p&gt;We organized a community identity committee to explore, grow, and design our new name and branding. Through interviews, workshops, and creative iterations, we &lt;a href=&#34;https://superbloom.design/learning/blog/whats-next-for-simply-secure-part-3-how-we-built-superbloom/&#34;&gt;landed on a direction&lt;/a&gt; that conveys the breadth of our current work, as well as our values, practice, and growth.&lt;/p&gt;
&lt;p&gt;Allow us to introduce:&lt;br&gt;
&lt;br&gt;
Superbloom: Changing Who Technology Serves. &lt;/p&gt;
&lt;p&gt;Superbloom leverages design as a transformative practice to shift power in the tech ecosystem. We view design as an intervention opportunity to center people and their needs. We closely collaborate with others in the space to grow a community focused on shaping our collective online future. &lt;/p&gt;
&lt;p&gt;Our vision is a world where everyone has the knowledge, network, and digital tools needed to enrich their lives.&lt;/p&gt;
&lt;p&gt;In the spirit of championing human-centered design, we’re aiming to make the transition from Simply Secure to Superbloom as seamless as possible. Our new website - to be launched soon - will feature all of our projects, along with an easy-to-use Resource Library. &lt;a href=&#34;http://superbloom.design&#34;&gt;Check out our transition site&lt;/a&gt; in the meantime.&lt;/p&gt;
&lt;p&gt;The world is changing. As we increasingly shift our lives online, there are more threats than ever to digital security. But those threats create opportunities for us to collaborate around thoughtful, purposeful, responsible design. &lt;/p&gt;
&lt;p&gt;A superbloom is a rare event, when long-dormant wildflower seeds bloom together to transform a harsh landscape with renewed energy and resilience. We believe technology design is at a Superbloom inflection point, and we’re excited to be shaping it into a beautiful future.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Mid/Senior Designer</title>
      <link>https://superbloom.design/community/opportunities/mid-senior-designer/</link>
      <pubDate>Thu, 13 Oct 2022 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/opportunities/mid-senior-designer/</guid>
      <description>&lt;h3 id=&#34;we-are-looking-for-a-midsenior-designer-with-expertise-in-either-ux-design-research-or-ux-and-ui-craft-and-design&#34;&gt;&lt;strong&gt;We are looking for a mid/senior designer with expertise in either UX design research or UX and UI craft and design.&lt;/strong&gt;&lt;/h3&gt;
&lt;h3 id=&#34;the-role&#34;&gt;&lt;strong&gt;The role&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Simply Secure is looking to hire a mid/senior designer with expertise in either UX design research or UX and UI craft and design. We are looking for someone who has strength in either or both of these design ‘quadrants’ to work on a variety of projects at Simply Secure. Depending on your strengths, and interest in where you wish to grow as a professional, you would work on one primary project that speaks to your strength, and be able to support on projects in your growth area. e.g. If you are a strong design researcher, a majority of your time would be on design research projects with the option to support and take on the occasional UX/UI project.&lt;/li&gt;
&lt;li&gt;Definitions of “levels” vary across organizations, so here’s what “mid/senior” means to us. You should be able to help scope projects as well as execute on them. You should be capable of taking the lead in communication with partners, and lead meetings. You should feel ready to manage other designers, either providing project guidance and/or serving as a “people manager.” We are open to many different kinds of design experience, but this should not be your first job in this area.&lt;/li&gt;
&lt;li&gt;You’ll be a critical part of our team, responsible for collaboratively outlining our research and design projects, conducting community-based research to support real needs, or ensuring our partners and projects get the best UX/UI possible for their technology interventions.&lt;/li&gt;
&lt;li&gt;The design research and UX/UI process will be iterative, requiring close collaboration with the project team, including: weekly meetings, asynchronous updates, and willingness to be responsive to team direction and ideas.&lt;/li&gt;
&lt;li&gt;You’ll work with internal and external project teams, leading and managing a number of projects with different partners and engagement models, making sure that we are on top of timelines, communicating effectively, and delivering on the work.&lt;/li&gt;
&lt;li&gt;This role will start in October/November 2022, and offer a salary in the $60,000-$85,000 range including benefits. For employees, we have a benefit structure that emphasizes equity between countries, but in all countries where we can hire, we offer health insurance, contributions towards retirement, paid vacation and federal holidays, a device stipend, and a monthly office stipend. We can provide specific information about benefits based on location.&lt;/li&gt;
&lt;li&gt;We care about flexibility and balance to support people to work in a way that they need, and so are open to contract, full-time and part-time models for the role. We are a US 501(c)3 organization that has the ability to hire in the US, Germany, and anywhere supported by &lt;a href=&#34;http://remote.com&#34;&gt;remote.com&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;about-us&#34;&gt;&lt;strong&gt;About us&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Changing who technology serves.&lt;/em&gt; Simply Secure is a small US 501(c)3 nonprofit organization, founded in 2014 at the intersection of digital design and human rights.&lt;/p&gt;
&lt;p&gt;Simply Secure leverages design as a transformative practice to shift power in the tech ecosystem. We apply a critical lens to technology development, and view design as an intervention opportunity to center people and their needs. We collaborate closely with others in the space to grow the community focused on shaping our collective online future. Our vision is a world where everyone has the knowledge, network, and digital tools needed to enrich their lives.&lt;/p&gt;
&lt;p&gt;We’ve contributed design to a variety of tools that enhance security, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We’ve held &lt;a href=&#34;https://simplysecure.org/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we’ve done a lot more than usable security. Just in the last year, we’ve launched a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;h3 id=&#34;about-you&#34;&gt;&lt;strong&gt;About you&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;A critical thinker with strengths as a strategist, convener and builder.&lt;/li&gt;
&lt;li&gt;You have experience with leading projects and project delivery.&lt;/li&gt;
&lt;li&gt;Experience with leading research and design work for technology, e.g. human-centered design, design thinking, service design, UX design, or participatory research (specifically field research) or experience leading on multiple UX/UI projects in a technology/digital space while working closely with a design research resource.&lt;/li&gt;
&lt;li&gt;Awareness of and/or interest in one or more of the following areas: tech criticism and activism, open source software, scientific software and/or science generally, human rights advocacy and/or human rights technology, internet freedom.&lt;/li&gt;
&lt;li&gt;You like working independently, and in collaboration with a fully remote team.&lt;/li&gt;
&lt;li&gt;You are comfortable with cross-cultural communication, collaboration and resolving conflicts, through work with international teams.&lt;/li&gt;
&lt;li&gt;You are comfortable advocating for yourself and your work to make sure that you’re getting what you need from the wider team.&lt;/li&gt;
&lt;li&gt;You are available to work with overlap during prime work hours where we have team members (11-6pm Central Europe / 10-5pm UK / 8-6pm US Eastern / 8-3pm US Pacific).&lt;/li&gt;
&lt;li&gt;You use tools that facilitate remote collaboration, primarily: Figma/PenPot, Notion, Miro, Slack and Google docs/suite.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;nice-to-have&#34;&gt;&lt;strong&gt;Nice to have&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You are familiar with design or development in open source, and are comfortable working in the open.&lt;/li&gt;
&lt;li&gt;You are interested in areas of research, e.g. scientific or research technology, communication and collaboration technology, or particular issue areas, e.g. science/research fields or tech policy and internet freedom issues.&lt;/li&gt;
&lt;li&gt;Have experience managing and enjoy working with a fully remote, distributed team, across many time zones and cultures.&lt;/li&gt;
&lt;li&gt;Proficiency in a language other than English. Although we operate in English, we work internationally. Currently, we provide &lt;a href=&#34;https://simplysecure.org/what-we-do/ux-guidance/&#34;&gt;coaching&lt;/a&gt; in English and German and are interested to be able to connect with more communities in local languages. Currently, members of our team speak one or more of: English, German, Spanish, Vietnamese.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;sound-like-a-good-fit&#34;&gt;&lt;strong&gt;Sound like a good fit?&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Please send us:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Resumé.&lt;/li&gt;
&lt;li&gt;2-3 examples of your work and tell us, briefly, about the &lt;strong&gt;timeline and process&lt;/strong&gt;: How did these projects get created? Who was involved? What did the process look like? How long did it take?&lt;/li&gt;
&lt;li&gt;1-2 references. References will be taken in the last phase of application review.&lt;/li&gt;
&lt;li&gt;The times you are available for approx 45 minutes to 1 hour for interviews within our working hours (9am to 5pm Eastern Standard Time).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;This position is open until filled and applications will be evaluated on a rolling basis. We will stop accepting applications on October 31, 2022.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We believe that systemic bad behaviors disproportionately hurt the most marginalized people in society — including people of color, people from working class backgrounds, women and LGBTQ people. We believe that these communities must be centered in the work we do. We strongly encourage applications from people with these identities or who are members of other marginalized communities. We are open to candidates from around the world. Final hiring decisions will be contingent upon our ability to contract and pay in the candidate’s country. Simply Secure does not provide relocation or visa support.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;No longer accepting applications.&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Project Manager Fall 2022</title>
      <link>https://superbloom.design/community/opportunities/project-manager-fall2022/</link>
      <pubDate>Thu, 13 Oct 2022 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/opportunities/project-manager-fall2022/</guid>
      <description>&lt;h3 id=&#34;we-are-looking-for-a-project-manager-to-help-us-wrangle-our-diverse-portfolio-of-work&#34;&gt;&lt;strong&gt;We are looking for a project manager to help us wrangle our diverse portfolio of work.&lt;/strong&gt;&lt;/h3&gt;
&lt;h3 id=&#34;the-role&#34;&gt;&lt;strong&gt;The role&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You’ll help us manage a number of different projects with different partners and engagement models, making sure we keep on top of timelines, communicate effectively and deliver on the work.&lt;/li&gt;
&lt;li&gt;You’ll be a critical part of our team, responsible for crafting and refining our project management approach, tools, and processes.&lt;/li&gt;
&lt;li&gt;We are a small, multifaceted team, and we all wear many hats. If you also have interests in other areas relevant to our work, such as fundraising, UX design, facilitation, graphic design, writing or communications, you will definitely have the opportunity to build and exercise these skills.&lt;/li&gt;
&lt;li&gt;We care about flexibility and balance to support people to work in a way that they need, and so are open to contract, full-time and part-time models for the role. We are a US 501(c)3 organization that has the ability to hire in the US, Germany and anywhere supported by &lt;a href=&#34;http://remote.com&#34;&gt;remote.com&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;This role will start in October/November, 2022, and offers a salary in the $60,000-$80,000 range including benefits. For employees, we have a benefit structure that emphasizes equity between countries, but in all countries where we can hire, we offer health insurance, contributions towards retirement, paid vacation and federal holidays, a device stipend and a monthly office stipend. We can provide specific information about benefits based on location.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;about-us&#34;&gt;&lt;strong&gt;About us&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Founded in 2014, we are a small US 501(c)3 nonprofit organization with the goal of making security tools easier to use. We believed – and still do – that security doesn’t have to be confusing to end users. Since then, we’ve expanded our scope of work: we design for trustworthy technology and work to change who technology serves. We’ve contributed design to a variety of tools that enhance security such as &lt;a href=&#34;http://www.surveillancemonitor.org&#34;&gt;Mobile Surveillance Monitor&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt;, and &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We’ve also launched a &lt;a href=&#34;https://buildingblocks.simplysecure.org/&#34;&gt;toolkit for funders of digital infrastructure&lt;/a&gt;, a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;p&gt;We’re also rebranding, moving away from the name “Simply Secure.”  &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;More info in this blog!&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;about-you&#34;&gt;&lt;strong&gt;About you&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You have experience with project management, including project delivery and as a project lead.&lt;/li&gt;
&lt;li&gt;You are knowledgeable about one or more of the following areas: open source software, internet freedom, tech criticism and activism, human rights, research &amp;amp; scientific software.&lt;/li&gt;
&lt;li&gt;You have excellent project team communication and meeting facilitation skills.&lt;/li&gt;
&lt;li&gt;You enjoy simplifying complex projects, tracking details, and making sure the project teams are working well together.&lt;/li&gt;
&lt;li&gt;You are experienced in client or partner-centered communication and project management.&lt;/li&gt;
&lt;li&gt;You are able to manage a balance of strategic planning and tactical execution.&lt;/li&gt;
&lt;li&gt;You are comfortable advocating for yourself and your work to make sure that you are getting what you need to be successful.&lt;/li&gt;
&lt;li&gt;You are familiar with working in the nonprofit space.&lt;/li&gt;
&lt;li&gt;You like working independently and in collaboration with a fully remote, distributed team.&lt;/li&gt;
&lt;li&gt;You are available to work with overlap during prime work hours where we have team members (11-6pm Central Europe / 10-5pm UK / 8-6pm US Eastern / 8-3pm US Pacific).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;nice-to-have&#34;&gt;&lt;strong&gt;Nice to have&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Experience in research and design work, eg human-centered design, design thinking, service design, UX design or participatory research (specifically field research).&lt;/li&gt;
&lt;li&gt;Comfortable with collaborative work tools (we currently use Notion, Slack, Miro and Google Suite).&lt;/li&gt;
&lt;li&gt;Comfortable with exploring and evaluating new tools.&lt;/li&gt;
&lt;li&gt;Comfortable in cross-cultural communication, e.g. experience with international work.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;sound-like-a-good-fit&#34;&gt;&lt;strong&gt;Sound like a good fit?&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Please send us:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Resumé.&lt;/li&gt;
&lt;li&gt;Examples of your work. With each link or document you send, please tell us about the &lt;strong&gt;timeline and process:&lt;/strong&gt; How did these outputs get created? Who was involved? What did the process look like? How long did it take?&lt;/li&gt;
&lt;li&gt;1-2 references. References will be taken in the last phase of application review.&lt;/li&gt;
&lt;li&gt;The times you are available for approx 45 minutes to 1 hour for interviews within our working hours (9am to 5pm Eastern Standard Time).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;This&lt;/strong&gt; p&lt;strong&gt;osition is open until filled, and applications will be evaluated on a rolling basis. We will stop accepting applications on October 31, 2022. Reach out to &lt;a href=&#34;mailto:jobs@simplysecure.org&#34;&gt;jobs@simplysecure.org&lt;/a&gt; with any questions.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We believe that systemic bad behaviors disproportionately hurt the most marginalized people in society — including people of color, people from working class backgrounds, women and LGBTQ people. We believe that these communities must be centered in the work we do. We strongly encourage applications from people with these identities or who are members of other marginalized communities. We are open to candidates from around the world. Final hiring decisions will be contingent upon our ability to contract and pay in the candidate’s country. Simply Secure does not provide relocation or visa support.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;No longer accepting applications.&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Threats, Tests, and Trust: Designing for Mobile Surveillance Monitor </title>
      <link>https://superbloom.design/learning/blog/threats-tests-and-trust-designing-for-mobile-surveillance-monitor/</link>
      <pubDate>Fri, 16 Sep 2022 16:36:14 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/threats-tests-and-trust-designing-for-mobile-surveillance-monitor/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/msm-hero_hu_61d15542f15fa5c7.png&#34; width=&#34;740&#34; height=&#34;442&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;With support from the Open Technology Fund, we supported &lt;a href=&#34;http://www.surveillancemonitor.org&#34;&gt;Mobile Surveillance Monitor&lt;/a&gt; with human-centered research and design.&lt;/li&gt;
&lt;li&gt;This new tool fills a critical gap in providing researchers and everyday users access to real data in a digestible form on surveillance threats.&lt;/li&gt;
&lt;li&gt;The user research phase was critical in challenging assumptions, building a tool that can be trusted, and understanding which users the tool can best serve. We pursued a phased design process to address questions raised in the research.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Surveillance on mobile devices is rampant globally, yet security researchers and everyday users alike struggle to access real data on surveillance threats and where they’re coming from. With support from the Open Technology Fund (OTF), we helped the brand new platform &lt;a href=&#34;http://www.surveillancemonitor.org&#34;&gt;Mobile Surveillance Monitor&lt;/a&gt; (MSM) fill this gap by providing research and design support. This new tool is both a public resource that tracks mobile threats on a map-based dashboard, and a workbook which provides researchers with detailed charts and investigation tools to uncover new details about multiple types of threats. &lt;/p&gt;
&lt;p&gt;Through our collaboration with MSM, we were able to dig deep into the UX of surveillance resources, an arena that often does not incorporate human-centered design practices. We learned that the design of these tools is a big responsibility, relying upon deep trust and user empowerment through education.&lt;/p&gt;
&lt;p&gt;We began our work with MSM with desk research to develop a foundational understanding of current needs and trends in surveillance threat software. We then completed five anonymous, in-depth user interviews with cybersecurity experts, advocates, researchers, human rights workers, and government contractors, who were asked about their experiences being under the threat of surveillance, surveillance mitigation, and their impressions of MSM as a resource. &lt;/p&gt;
&lt;p&gt;In the intervening time, we contracted a brand designer who developed an identity for MSM that moved away from the dark, ominous, hacker-style common to cybersecurity tools to a more practical and approachable look and feel. After synthesizing the user research findings, we began applying the brand work and the research findings to a first version of the MSM dashboard in partnership with &lt;a href=&#34;https://www.esri.com/en-us/home&#34;&gt;ESRi,&lt;/a&gt; a mapping software provider. Finally, after development was complete, we did four user tests to understand some potential users’ perceptions of the site and its usability. &lt;/p&gt;
&lt;h3 id=&#34;we-learned-many-things-throughout-this-process-but-a-few-key-learnings-arose&#34;&gt;We learned many things throughout this process, but a few key learnings arose:&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;OSINT tools that are off-the-shelf, free, available for individual use, and not connected to an institution or organization are relatively rare and/or unreliable.&lt;/strong&gt; They are even less often informed by a broad and inclusive user-centered design process that does not ‘center’ a ‘security expert’ type of user.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Designing for surveillance intelligence is delicate, complex, and a lot of responsibility.&lt;/strong&gt; Developing personas and scenarios of use is critical, and only one part of a larger conversation around safety and threat modeling.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The users of surveillance security tools are broad and unexpected in some cases.&lt;/strong&gt; They are not always the ‘tech savvy’ ‘security geeks’ and often are people doing high-risk human rights work with very little time, focus and energy to spend on ensuring safety from surveillance threats. If they are interested, the tools and practices often exclude them through jargon and assumed background knowledge which can feel alienating.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;working-on-msm-challenged-our-assumptions-and-pushed-us-to-get-creative-to-responsibly-serve-more-users-over-time&#34;&gt;Working on MSM challenged our assumptions and pushed us to get creative to responsibly serve more users over time.&lt;/h3&gt;
&lt;p&gt;Focusing on the learnings of our research and early design process, we hope that our insights can help others in our ecosystems think through complex challenges around surveillance intelligence and design. Including a thorough research and design process in the development of MSM proved to be critical in a number of ways, most notably because &lt;strong&gt;it tested and challenged many of our own assumptions about user needs.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Far before we started designing for MSM, our interviewees urged caution. &lt;strong&gt;They emphasized that security tools must be aware of their potential impacts on users, including&lt;/strong&gt;: giving users a false sense of security, the possibility of users applying intelligence data to their own circumstances misguidedly, eliciting fear without opportunity for action, and eliciting unnecessary fear and/or confusion. Insights from people who have been deeply engaged with surveillance threats from many angles helped us to understand the gravity of designing a security tool and being precise about the intended audience.&lt;/p&gt;
&lt;p&gt;That insight was also developed by the most consistent finding from our research: &lt;strong&gt;surveillance data is only as good as the threat model it is paired with&lt;/strong&gt;. Our interviewees shared that a lot of privacy and security guidance assumes too much:  they give a lot of advice that doesn&amp;rsquo;t apply to people&amp;rsquo;s lives or address the concerns they have. One participant shared: &lt;strong&gt;“When people ask what the secure/safe way is to do things - the answer is always: it depends.”&lt;/strong&gt; These insights ultimately helped us to frame suggestions around MSM’s educational offerings to users, and how critical it is for surveillance data to have appropriate context.&lt;/p&gt;
&lt;p&gt;Through our user interviews and other research, we moved toward design and recommendations for MSM with a sense of responsibility and excitement.  A critical part of that process was fleshing out user personas to better understand who MSM will serve now, and who else it might be able to serve in the future. We found that the first version of MSM principally serves what we named &lt;strong&gt;researcher/academic persona.&lt;/strong&gt; The researcher/academic uses MSM to study mobile surveillance and form questions about trends to more deeply investigate the factors surrounding them. Our research suggested that MSM  also serves what we called the Independent persona – those of mid-tech proficiency, like a journalist or advocate without significant institutional backing – as long as MSM added content and resources to help contextualize the threat intelligence (Which it did!).&lt;/p&gt;
&lt;p&gt;As significantly, we found that in order to properly serve the &lt;strong&gt;low tech/high risk persona&lt;/strong&gt;, the platform would need more intensive investment in the content and educational aspects of MSM, with more research and threat modeling on specific targeted groups that would use it. We have plans to continue our work with &lt;a href=&#34;https://mobileintelligence.org/about-gary-miller&#34;&gt;Gary Miller&lt;/a&gt; of &lt;a href=&#34;https://mobileintelligence.org/&#34;&gt;Mobile Intelligence Alliance&lt;/a&gt; this Fall to explore options for more resourcing and education on MSM for precisely this purpose.&lt;/p&gt;
&lt;h3 id=&#34;a-phased-design-process-proved-critical-to-addressing-user-needs&#34;&gt;A phased design process proved critical to addressing user needs&lt;/h3&gt;
&lt;p&gt;We are very proud of MSM’s launch and believe it is a powerful resource for users to explore mobile security threats. We are also committed to those who shared their expertise with us for this project and to sharing our learnings with our community, because, as we learned, it is difficult to design for security tools considering all of the factors that affect user experience! &lt;/p&gt;
&lt;p&gt;&lt;br&gt;
In the interest of exploring the UX of security tools as a community, we’re sharing an abridged version of our initial phased design proposal that accompanied our user research findings. This is one way that researchers and designers can both advocate for user needs within the parameters of a program or website and offer ideas and solutions to serve more users in the future. MIA and MSM have been wonderful partners, and we’re lucky to already be working toward implementing updated versions of some of these ideas to MSM.&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
Below is a brief description of those the design phases we hypothesized in our user research synthesis:&lt;/p&gt;
&lt;h4 id=&#34;phase-1-a-tool-for-researchers&#34;&gt;&lt;strong&gt;Phase 1: A tool for researchers&lt;/strong&gt;&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Purpose:&lt;/strong&gt; MSM enables researchers to confirm hypotheses and perform geographic and temporal analyses. &lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Design priorities:&lt;/strong&gt; A streamlined, clean, and easily usable dashboard interface (Figure 1). Begin to build infrastructure into the dashboard that can support additional content and educational tools over time (Figure 2). These modules can be flexible, and could be fed by datasets, or could be set up as iFrames with HTML/CSS.&lt;/li&gt;
&lt;li&gt;This design was largely implemented in the &lt;a href=&#34;https://surveillancemonitor.org/surveillance-dashboard&#34;&gt;live version of the MSM dashboard.&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/msm-blog-figure-1_hu_9f148649a7127c68.png&#34; width=&#34;740&#34; height=&#34;365&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Phase 1 Design&lt;/em&gt;&lt;/p&gt;
&lt;h4 id=&#34;phase-2-a-tool-for-those-concerned-about-their-surveillance-risk&#34;&gt;Phase 2: A tool for those concerned about their surveillance risk &lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Purpose:&lt;/strong&gt; Researchers can make increasingly specific searches and associations on the dashboard. Concerned users can filter the dashboard for their location/device type, building a case file for their own protection, and learn about 1) their risk and 2) what they can do about it. &lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Design priorities:&lt;/strong&gt; curate resources for different types of threats, including how people can begin to a develop a threat modeling system for themself or their community. Include definitions / glossary of terms.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/msm-blog_figure-2_hu_acb72c52794410eb.png&#34; width=&#34;740&#34; height=&#34;552&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Phase 2 Design&lt;/em&gt;&lt;/p&gt;
&lt;h4 id=&#34;phase-3-enable-trusted-users-to-contribute-resources-and-data&#34;&gt;Phase 3: Enable trusted users to contribute resources and data. &lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Purpose:&lt;/strong&gt; Our research showed that surveillance intel is most useful if it is vouched for by a trusted source. This version of the MSM dashboard allows users to save and share their dashboards, and comment on different pieces of data to share their insights. MSM allows “power users” to contribute to the platform to improve its trustworthiness. &lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Design priorities:&lt;/strong&gt; “Power users” can log-in and contribute safety resources, region-specific suggestions, and comment on / report back on experiences they’ve had to help bolster the threat modeling work that the data doesn’t provide on its own.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/msm_blog_figure_3_hu_9f2961d8874ede5a.png&#34; width=&#34;740&#34; height=&#34;552&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Phase 3 Design&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We learned so much working with Gary on the Mobile Surveillance Monitor site; from responsible data practices doing high-risk user research to better informational design on a mapping application, this project was challenging and fulfilling for our team. We’re excited to see where MSM goes in the future. &lt;br&gt;
&lt;br&gt;
Be sure to follow along by &lt;a href=&#34;https://surveillancemonitor.org/threat-alerts-1&#34;&gt;signing up for MSM data alerts and news! &lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;OTF SUA Lab, Mobile Intelligence Alliance, Aldo Puicon&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title> All Aboard: Getting Mainstream Users Up and Running on Decentralized Systems</title>
      <link>https://superbloom.design/learning/blog/improving-onboarding-usability-for-different-user-groups/</link>
      <pubDate>Mon, 15 Aug 2022 10:02:40 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/improving-onboarding-usability-for-different-user-groups/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog-cover_hu_ca6e69458c0fce3b.jpg&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Creating a smooth onboarding experience is a common design challenge in free and open-source software (FOSS) projects. Onboarding is a particular challenge for decentralized systems because the mental model is different from mainstream software.&lt;/li&gt;
&lt;li&gt;With support from the Open Technology Fund (OTF) Usability Lab, we partnered with Snikket, a decentralized messaging platform to find the sweet spot between a technically correct mental model and usability. &lt;/li&gt;
&lt;li&gt;Our research exposed a key opportunity: Technical and non-technical users have very different needs from onboarding. We recommended changes to the website content and information architecture to improve the usability of the onboarding experience for both groups.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Be sure to check out our &lt;a href=&#34;https://superbloom.design/learning/blog/on-getting-things-done-a-conversation-with-matthew-wild-from-snikket/&#34;&gt;interview with Snikket’s creator, Matthew Wild&lt;/a&gt;, as well.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://snikket.org/&#34;&gt;Snikket&lt;/a&gt; is an XMPP-based messaging platform that aims to provide an open and secure alternative to proprietary messaging apps such as WhatsApp, Facebook Messenger, and Telegram. What makes Snikket different from other messaging apps is that it allows people to create and host their own servers (including Raspberry Pis) for more control and security.  Personally controlled, decentralized servers are at the heart of Snikket, but this much end-user control means a more complicated onboarding process. Users can’t start using the app by simply downloading it from an app store and creating an account. Snikket’s goal is to distinguish itself in the fragmented and highly technical XMPP ecosystem by providing consistency and usability to a broad group of users.&lt;/p&gt;
&lt;p&gt;Through the &lt;a href=&#34;&#34;&gt;OTF Security and Usability Lab&lt;/a&gt;, our work with Snikket focused on improving the user experience of both iOS and Android devices, and balancing ease of learning and efficiency of use. We conducted a heuristic review of Snikket apps and web interfaces, facilitated a user study, considered several UX design explorations, and delivered design recommendations for an improved onboarding experience that address the barriers for adoption.&lt;/p&gt;
&lt;h3 id=&#34;onboarding-doesnt-have-to-stop-after-the-welcome-screen&#34;&gt;Onboarding doesn’t have to stop after the welcome screen &lt;/h3&gt;
&lt;p&gt;The onboarding process is essentially a user journey to learn about a new application or software. If designed correctly, it creates a positive first impression and increases the likelihood of adoption. According to the &lt;a href=&#34;https://www.nngroup.com/articles/mobile-app-onboarding/&#34;&gt;Nielsen Norman Group&lt;/a&gt;, the key purposes of onboarding include:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;feature promotion — to &amp;ldquo;educate users about the function and benefit of the app;&amp;rdquo;&lt;/li&gt;
&lt;li&gt;customization — to &amp;ldquo;request user data to customize the user&amp;rsquo;s experience;&amp;rdquo;&lt;/li&gt;
&lt;li&gt;instructions — to &amp;ldquo;teach users how to use the interface.&amp;rdquo;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;A tool team might think of an onboarding process as limited to a few first screens when users open an application or software for the first time. For more complicated designs, onboarding can also take place over time, like when new features are introduced once users have achieved a certain level of fluency. This is often the case of free and open source software (FOSS) designs as they are built upon a variety of different decentralized protocols that are usually less familiar to the average, less-technical users. &lt;/p&gt;
&lt;p&gt;For users who aren’t familiar with XMPP, they can request to join a Snikket-hosted server and start using the app from there. Their friends can then join them by getting an invitation to the same server. If a user feels comfortable, they can find instructions on the Snikket’s website to host a XMPP server and then invite their friends. On the surface, this onboarding process may seem straightforward, but the user experience, on the contrary, is not. &lt;/p&gt;
&lt;p&gt;The diagram below illustrates what a non-technical user and a technical user need to do in order to start using Snikket to chat:&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/what-users-need_hu_84777fbb7d1e0817.jpg&#34; width=&#34;740&#34; height=&#34;217&#34;&gt;
&lt;/p&gt;
&lt;p&gt;In contrast, the actual onboarding workflow that both user groups need to go through is much longer and more complicated: &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/user-flow_hu_5350c918a0fbd56.jpg&#34; width=&#34;740&#34; height=&#34;259&#34;&gt;
&lt;/p&gt;
&lt;p&gt;As technical users can create their own instance on Snikket, they are introduced to an entirely different workspace on Snikket (the web portal). After successfully creating a server, they can start sending invitations for others to join. Meanwhile, the non-technical users’ onboarding flow  only starts after they have received an invitation and downloaded the application. A simple task such as signing in can get confusing here when a new user can’t create an account on the app and isn&amp;rsquo;t introduced to the web portal priorly:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“Is this the same address and password [with the one used for the server]?”&lt;/p&gt;
&lt;p&gt;“I don’t know how to sign in, because obviously I don’t know how to sign in.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&#34;mind-the-mental-model-gap&#34;&gt;Mind the mental model gap&lt;/h3&gt;
&lt;p&gt;Our user study revealed that most technical users can use Snikket efficiently,  even when the overall onboarding experience is not always straightforward. They know how to set up a server, create admin accounts, send invitations to their circle, and more. &lt;/p&gt;
&lt;p&gt;However, this ease of use does not apply to non-technical users as most of them struggled to navigate through the app. There was a significant gap between their mental model of Snikket and the centralized messaging apps they are used to. For example, many users thought that inviting someone to a server was the same as adding contact on the app. In reality that is not the case. For example, with Whatsapp, one can simply invite someone by sending them an invitation to their phone number via the app, or they can look up their username/or phone number. With Snikket, one needs to be invited to the server and create an account on that server first. The two options to invite to server and  add contacts are not clearly presented —  inviting someone to server is done on the web hosting site whereas adding contact is done within the app. &lt;/p&gt;
&lt;p&gt;Most of the non-technical testers could not figure out how to install the app. Even if they did manage to download the app, they didn’t know how to start using it. The lack of clearly visible next steps makes it difficult for users to establish a workflow. Most users, including tech-savvy users, expected to be able to use the app right after installation. To address these challenges, we relied on our two personas — the non-technical user and the technical user. We mapped out both persona’s needs and pain points and then identified the similarities in their onboarding process.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/technical-persona_hu_20c802f9d915db82.jpg&#34; width=&#34;740&#34; height=&#34;368&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;em&gt;Technical user persona&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/non-technical-persona_hu_30de72ccacfa130d.jpg&#34; width=&#34;740&#34; height=&#34;370&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Non technical user persona&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;ease-of-learning-versus-efficiency-of-use&#34;&gt;Ease of Learning versus Efficiency of Use &lt;/h3&gt;
&lt;p&gt;The Snikket onboarding process starts at different places depending on the users’ level of technical knowledge and their familiarity with XMPP. A non-technical user usually has their first interaction on the app, while a technical user might go to the website first and start with the Snikket Hosting platform. Because of this, it is important to deliver the right message, in the right place, at the right time. We had to keep in mind that this doesn’t mean packing in and presenting all the information to users at once - users don’t need to know all the technical information in order to perform a task. In some cases, it might be too technical for non-technical users and XMPP beginners to fully comprehend the differences between the variety of Snikket components such as instance, app, network, and server.&lt;/p&gt;
&lt;p&gt;Language and tone are other powerful tools to support the comprehension process and improve usability. As such, we wanted to make the language consistent and reduce technical jargon. It’s advisable to generally avoid technical jargon to deliver concise and timely messages rather than informative yet obtrusive and exhausting ones. Whether it is to employ an interactive walkthrough, help text, or a deck-of-cards tutorials, the instructional onboarding process should be built on existing mental models to reduce memory strain. A good practice when introducing new features is to keep customization to a minimum and provide a clear structure that enables users of different technical levels to follow. &lt;/p&gt;
&lt;p&gt;An effective onboarding process should prioritize what users need to do and know by highlighting the most important information in a timely manner. For example, the images below display a comparison of Snikket two different versions for the UI/UX design of account deletion. In version 1.1, there was no system confirmation of the deletion but two different options of account removal, none of which presented in a non-technical friendly manner. A small UX change in version 1.2 makes it a lot easier for users to perform their task. By eliminating the technical removal options and providing a confirmation message, users can avoid making an error (log-out versus delete) and focus on the task at hand. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/snikket-workspace-2-_hu_78e33f03131e93ea.jpg&#34; width=&#34;740&#34; height=&#34;686&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;usability-starts-with-a-good-onboarding-experience&#34;&gt;Usability starts with a good onboarding experience&lt;/h3&gt;
&lt;p&gt;The benefits of FOSS is that it’s easy and flexible for community members of different disciplines to contribute and there is no paywall for the end-users. Many FOSS and decentralized tools have played a critical role in helping vulnerable communities maintain their security, autonomy and independence. If these technologies are hard to use, they are less likely to get adopted and hence become less critical. When it comes to unfamiliar and highly-technical decentralized tools and protocols such as Snikket’s XMPP,  it is even more important to have a good onboarding design in place. &lt;/p&gt;
&lt;p&gt;Our design recommendations for Snikket’s onboarding process are based on the &lt;a href=&#34;https://github.com/simplysecure/resources/blob/277a57734c1732f9ac0e77fbeb5f7d96d379d99b/Simply%20Secure%2010%20Heuristics%20for%20Responsible%20Interface%20Design.pdf&#34;&gt;Simply Secure 10 Heuristics for Responsible Interface Design&lt;/a&gt;. We believe that a learning-by-doing approach would ensure a balance between the ease of learning and efficiency of use in a complicated and unfamiliar system design like Snikket, not only during the onboarding process but also throughout the entire user experience. We hope that our learning has shed some lights on the importance of onboarding design in enabling usability in FOSS. &lt;/p&gt;
&lt;p&gt;&lt;em&gt;Read our interview with Snikket’s creator, Matthew Wild, &lt;a href=&#34;https://superbloom.design/learning/blog/on-getting-things-done-a-conversation-with-matthew-wild-from-snikket/&#34;&gt;here.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Learn more about our previous work on FOSS design: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Our recommendation on &lt;a href=&#34;https://superbloom.design/learning/blog/globaleaks-case-study/&#34;&gt;default and customization design&lt;/a&gt; in FOSS&lt;/li&gt;
&lt;li&gt;Visit &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;Decentralisation, Off the Shelf&lt;/a&gt;’s library of design/UX patterns for better user-facing applications design in decentralization&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Project Credit&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Project Contributors: Ngọc Triệu, Ame Elliott, Rae McKelvey, Snikket (Matthew Wild)&lt;/p&gt;
&lt;p&gt;Illustration: Ngọc Triệu &lt;/p&gt;
&lt;p&gt;Project funded by Open Technology Fund&amp;rsquo;s &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Secure Usability and Accessibility Lab&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Building Blocks: Funding Digital Infrastructure From the Ground Up </title>
      <link>https://superbloom.design/learning/blog/building-blocks-funding-digital-infrastructure-from-the-ground-up/</link>
      <pubDate>Fri, 15 Jul 2022 15:19:19 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/building-blocks-funding-digital-infrastructure-from-the-ground-up/</guid>
      <description>&lt;ul&gt;
&lt;li&gt;With the support of the Digital Infrastructure Fund, we partnered with 9 regional partners and Superrr Lab to design a set of tools and resources that enable digital infrastructure funders to explore opportunities and address challenges in funding.&lt;/li&gt;
&lt;li&gt;Using human centered design research, we generated tools that are grounded in the principle that funders should listen to the communities they serve.&lt;/li&gt;
&lt;li&gt;Building Blocks includes Opportunities, a &lt;a href=&#34;https://buildingblocks.simplysecure.org/tag/defining-digital-infra/&#34;&gt;definition&lt;/a&gt;, &lt;a href=&#34;https://buildingblocks.simplysecure.org/tag/regional-contexts/&#34;&gt;regional contexts&lt;/a&gt;, c&lt;a href=&#34;https://buildingblocks.simplysecure.org/tag/funding-mechanisms/&#34;&gt;ase studies on funding mechanisms&lt;/a&gt;, &lt;a href=&#34;https://buildingblocks.simplysecure.org/tag/narratives/&#34;&gt;six narrative future scenarios&lt;/a&gt;, and &lt;a href=&#34;https://buildingblocks.simplysecure.org/tag/exploring-our-building-blocks/&#34;&gt;tools and resources&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;the-building-blocks-of-open-source-digital-infrastructure-funding&#34;&gt;The Building Blocks of Open-Source Digital Infrastructure Funding&lt;/h2&gt;
&lt;p&gt;Many of us take infrastructure for granted almost by definition. If we thought about plumbing and sewers every time we turned on the tap, if we pondered the power grid every time we charged a phone, we’d hardly be able to focus. The tech tools we use are no exception; they are infrastructure, and most of the time, their job is to “just work” and hide from notice. &lt;/p&gt;
&lt;p&gt;At the same time, though, someone does have to think about infrastructure; someone has to maintain it, and someone has to fund it. The security and maintenance of this code is precarious, and depends on committed time and effort from human volunteers. As the 2016 report “&lt;a href=&#34;https://www.fordfoundation.org/work/learning/research-reports/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure/&#34;&gt;Roads and Bridges: the Unseen Labor Behind our Digital Infrastructure&lt;/a&gt;” says, “The current state of our digital infrastructure is one of the most poorly understood issues of our time.” (Relatedly, as the venerable webcomic xkcd puts it, all modern digital infrastructure depends on “&lt;a href=&#34;https://xkcd.com/2347/&#34;&gt;a project some random person in Nebraska has been thanklessly maintaining since 2003&lt;/a&gt;.”)&lt;/p&gt;
&lt;p&gt;Our goal: to equip the ethical tech community of developers, maintainers, activists, designers, and funders with tools to support this critical enterprise. The &lt;a href=&#34;https://techcrunch.com/2021/03/03/1-3m-in-grants-go-towards-making-the-webs-open-source-infrastructure-more-equitable/?guccounter=1&amp;amp;guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&amp;amp;guce_referrer_sig=AQAAAL_ADa0sd-pBleFIWF-e34wGWBTdnWu1RfgM-HBkgTHbcGwAlgTCAmUuZoxRlos7Um-EvTdZdbppMOFIs4rnSsw7wIDffQ8frzCVCQoIE_nnKK_YXHb_0lDfkm9WEdBhTqWidSWoXTapRx0ZdLYcHtATo9_Hsl4paYRoFMi9kNgr&#34;&gt;Digital Infrastructure Grants&lt;/a&gt; have been key investments in the future sustainability of open source code. Thanks to this grant, we and our partners created &lt;a href=&#34;https://buildingblocks.simplysecure.org/&#34;&gt;Building Blocks&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;Building Blocks is a multifaceted collection: it’s a set of actionable tools, contextual resources, practical guides, case studies, regional narratives, and speculative futures. Building Blocks is for funders, either those new to supporting digital infrastructure or those hoping to improve and refine their approach. Building Blocks can also be useful for others - such as researchers, activists, and designers - looking to connect and understand how to support the open source community.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;Check out our &lt;a href=&#34;https://superbloom.design/learning/blog/building-a-toolkit-for-funders-to-grow-their-digital-infrastructure-portfolio/&#34;&gt;first blog post&lt;/a&gt; on the toolkit, where we explore funder personas and talk about our geographic approach.&lt;/strong&gt;&lt;/em&gt; &lt;/p&gt;
&lt;h3 id=&#34;why-a-toolkit&#34;&gt;Why a toolkit?&lt;/h3&gt;
&lt;p&gt;Simply Secure, as a design non-profit working closely with infrastructure funders, has advised a number of funders and projects on improving their funding and program design practices. Our projects in this area include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/on-trust-and-transparency&#34;&gt;On Trust and Transparency&lt;/a&gt; (a collaboration with Luminate), a 2018 report uncovering grantees’ experience of the funding process.&lt;/li&gt;
&lt;li&gt;A redesign of the Open Technology Fund’s primary funding program.&lt;/li&gt;
&lt;li&gt;A funding identity and strategy workshop with the Prototype Fund.&lt;/li&gt;
&lt;li&gt;Impact evaluations for Mozilla Open Source Support and &lt;a href=&#34;https://superbloom.design/learning/blog/reflections-on-the-mozilla-fellowships-and-awards-impact-evaluation-lessons-for-the-ecosystem/&#34;&gt;Fellowships and Awards&lt;/a&gt; programs.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Throughout these projects, one consistent theme keeps coming up: &lt;em&gt;&lt;strong&gt;Funders need to listen to the communities they fund.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;As a part of the public interest technology, digital rights, open source, and internet freedom communities, we aim to make this practice of listening into the new industry standard. We have listened to funders, listened to grantees, and helped both funders and grantees learn to listen to each other. &lt;/p&gt;
&lt;p&gt;We’ve noticed three layers of needs to be addressed: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;that of the funders;&lt;/li&gt;
&lt;li&gt;of the project teams they fund;&lt;/li&gt;
&lt;li&gt;and of the end users of these funded projects. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Though we designed Building Blocks primarily for funders, we always kept in mind how improving the funding practices would also benefit grantees and their users in the long run. Our ultimate goal is to improve the relationships between all these stakeholders in order to nourish the digital infrastructure ecosystem as a whole.&lt;/p&gt;
&lt;h3 id=&#34;human-centered-program-design&#34;&gt;Human-Centered Program Design&lt;/h3&gt;
&lt;p&gt;The words “design for funders” might first evoke improving the interface of a funder’s web application platform. A usable, accessible, and friendly application platform is certainly a foundational element. But for us, design is about working at the relationship level, and letting the artifacts and touchpoints – rubrics, metrics, forms, processes – flow from the qualities of that relationship. Funding free and open source software (FOSS) often requires a certain amount of flexibility that is not typically seen in the ways traditional funding programs are designed. Our approach, then, was not to create a playbook for better FOSS funding, but to create a set of modular tools – or “building blocks” – to help funders develop a sustainable, relationship-based approach that emphasizes listening to communities.&lt;/p&gt;
&lt;h3 id=&#34;the-building-blocks&#34;&gt;The Building Blocks&lt;/h3&gt;
&lt;p&gt;Our design approach to the creation of the Building Blocks is grounded in human-centered design (HCD) and service design. In following these two principles, we committed to engaging funders, applicants, and advisors by conducting expert interviews, facilitating design workshops, and working closely with regional partners. We wanted to create a set of tools and resources that are specific to the varied needs of funders, allowing them to address and explore complex challenges such as power dynamics, identity and strategy, and impact measurement. Building Blocks provide more than just design exercises that focus on conducting needs assessments or crafting a new program in a more flexible way. They serve as a reflection mechanism for reviewing, evaluating, improvising, and strengthening program designs in times of uncertainty. &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Opportunities:&lt;/strong&gt; Curated starting points of resources and tools, around a unifying subject: &lt;a href=&#34;https://buildingblocks.simplysecure.org/funding-approach-process/&#34;&gt;Funding Approach and Process&lt;/a&gt;, &lt;a href=&#34;https://buildingblocks.simplysecure.org/identity-strategy/&#34;&gt;Identity &amp;amp; Strategy&lt;/a&gt;, &lt;a href=&#34;https://buildingblocks.simplysecure.org/funding-process-approach/&#34;&gt;Community Engagement&lt;/a&gt;, and &lt;a href=&#34;https://buildingblocks.simplysecure.org/technology/&#34;&gt;Technology&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&#34;https://buildingblocks.simplysecure.org/tag/defining-digital-infra/&#34;&gt;Defining Digital Infrastructure&lt;/a&gt;:&lt;/strong&gt; Get started by exploring a definition and overview, as well as four example profiles of different funders.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&#34;https://buildingblocks.simplysecure.org/tag/regional-contexts/&#34;&gt;Regional Contexts&lt;/a&gt;:&lt;/strong&gt; Our 9 regional partners’ present research syntheses on digital infrastructure funding in the context of their regions of the world.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&#34;https://buildingblocks.simplysecure.org/tag/funding-mechanisms/&#34;&gt;Funding Mechanisms&lt;/a&gt;:&lt;/strong&gt; Four case studies that spotlight different digital infrastructure funding mechanisms and funders.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&#34;https://buildingblocks.simplysecure.org/tag/narratives/&#34;&gt;Narrative Futures&lt;/a&gt;:&lt;/strong&gt; Six future scenarios, created by Superrr Lab, that spark inspiration on how we can shape the digital future in a collaborative, sustainable and equal way.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&#34;https://buildingblocks.simplysecure.org/tag/exploring-our-building-blocks/&#34;&gt;Explore our Building Blocks&lt;/a&gt;:&lt;/strong&gt; A full list of tools + guides for current and future digital infrastructure funders to reflect, engage with grantees, hold workshops, and build strategy.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This work could not have been completed without the help of many partners, including &lt;a href=&#34;https://superrr.net/&#34;&gt;Superrr Lab&lt;/a&gt; in Berlin, who synthesized research from our joint collaboration Roadwork Ahead, which outlines the needs of open source communities. Superrr also created six &lt;a href=&#34;https://buildingblocks.simplysecure.org/tag/narratives/&#34;&gt;Narrative Futures&lt;/a&gt; which tie digital infrastructure to other funding priorities and global issues by sparking inspiration on how we can shape the digital future in a collaborative, sustainable and equal way.&lt;/p&gt;
&lt;p&gt;We also collaborated with 9 regional partners, representing 9 regions - East Africa, Central Africa, West Africa, Oceania, India/SE Asia, Europe, South + Latin America (one partner exploring lower-income countries, the other higher-income countries), and Brazil. The partners presented &lt;a href=&#34;https://buildingblocks.simplysecure.org/tag/regional-contexts/&#34;&gt;research syntheses&lt;/a&gt; on digital infrastructure funding in their respective regions around the world.&lt;/p&gt;
&lt;h2 id=&#34;going-forward&#34;&gt;Going Forward&lt;/h2&gt;
&lt;p&gt;There is lots to build on in the toolkit to better support funders. Here’s a few things that are top of mind:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;First, we are developing plans to increase the reach and impact of the toolkit - likely through engagement opportunities such as events and workshops. &lt;/li&gt;
&lt;li&gt;We also hope to incorporate open feedback mechanisms to hear about how these tools are implemented in practice.&lt;/li&gt;
&lt;li&gt;We will add tools and resources as needs arise. &lt;/li&gt;
&lt;li&gt;The regional contexts are a great window into global nuances of digital infrastructure, but we hope to build on the localization by translating parts of the toolkit, and curating sets of resources specific to different regional contexts.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;As for funders themselves, the support we received in creating Building Blocks is in itself an encouraging sign for the future of sustainable digital infrastructure. The Digital Infrastructure Grants came to be because a consortium of funders — Ford Foundation, Sloan Foundation, Omidyar Network, Mozilla Foundation, and Open Society Foundations — had a shared goal of understanding how digital infrastructure is maintained. Looking ahead in this ecosystem, a promising new initiative by Schmidt Futures Plaintext Group - the &lt;a href=&#34;https://github.com/PlaintextGroup/oss-virtual-incubator&#34;&gt;Open Source Software Virtual Incubator&lt;/a&gt; - is an innovative approach with the goal of “funding systemic improvements in the open source software ecosystem.” In the spirit of open source, the entire submission process is open and hosted on Github. &lt;/p&gt;
&lt;p&gt;While FOSS is upheld by both unpaid volunteer efforts and paid company-backed financial and time investment, the volunteer-led FOSS infrastructure are the projects that are the &amp;lsquo;unseen&amp;rsquo; efforts to under-pin the critical digital infrastructure of the web. It can be challenging to coordinate, share resources, and define funding strategies for these volunteer community initiatives until they are listened to and brought into the conversation about how to best support them alongside FOSS with better &amp;lsquo;visibility&amp;rsquo;. A sensitive, localized approach is essential, and funders around the world could benefit from meeting maintainers where they are and working with them to define their needs. Our hope is  that the tools and resources in Building Blocks help launch those conversations, and get funders thinking about how to build a digital infrastructure sustainability portfolio collaboratively with the community of contributors and maintainers making it all possible.&lt;/p&gt;
&lt;h2 id=&#34;project-credit&#34;&gt;Project Credit&lt;/h2&gt;
&lt;h3 id=&#34;simply-secure&#34;&gt;Simply Secure&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://simplysecure.org/who-we-are/ngoc/&#34;&gt;Ngọc Triệu&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/melechuga&#34;&gt;Melissa Huerta&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://simplysecure.org/who-we-are/susan/&#34;&gt;Susan Kennedy&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://simplysecure.org/who-we-are/georgia/&#34;&gt;Georgia Bullen&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://simplysecure.org/who-we-are/eriol-fox/&#34;&gt;Eriol Fox&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://simplysecure.org/who-we-are/molly/&#34;&gt;Molly Clare Wilson&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;superrr-lab&#34;&gt;&lt;a href=&#34;https://superrr.net/&#34;&gt;SUPERRR Lab&lt;/a&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superrr.net/about/&#34;&gt;Elisa Lindinger&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superrr.net/about/&#34;&gt;Julia Kloiber&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;regional-partners&#34;&gt;Regional Partners&lt;/h3&gt;
&lt;p&gt;&lt;a href=&#34;&#34;&gt;2iC Lab&lt;/a&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;http://linkedin.com/in/celsobessa/&#34;&gt;Celso Bessa&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.linkedin.com/in/bibiana-alarcon-58840232/&#34;&gt;Bibiana Alarcón&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.linkedin.com/in/daniela-prada-ardila-researcher/&#34;&gt;Daniela Prada&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.linkedin.com/in/juan-carlos-roa-bogota-34aa6319/&#34;&gt;Juan Roa&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href=&#34;https://www.mozillapulse.org/profile/4179&#34;&gt;Amarela&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.tedic.org/en/&#34;&gt;TEDIC&lt;/a&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.linkedin.com/in/fernanda-carles-galeano-a4031989/&#34;&gt;Fernanda Carlés&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href=&#34;https://www.linkedin.com/in/michelledbarker/&#34;&gt;Michelle Barker&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://twitter.com/mbunzama&#34;&gt;Narcisse Mbunzama Lokwa&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://theiofoundation.org/&#34;&gt;The IO Foundation&lt;/a&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.linkedin.com/in/jfqueralt/&#34;&gt;Jean F. Queralt&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.linkedin.com/in/raashi-saxena-18a90684&#34;&gt;Raashi Saxena&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://linkedin.com/in/maryamlee&#34;&gt;Maryam Lee&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href=&#34;http://ke.linkedin.com/in/wainainamungai&#34;&gt;Wainaina Mungai&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.linkedin.com/in/chukwuyere-ebere-izuogu-b5505b4/?originalSubdomain=ng&#34;&gt;Chukwuyere Izuogu&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;Project funded by:&lt;/strong&gt;&lt;/em&gt; &lt;a href=&#34;https://www.fordfoundation.org/campaigns/critical-digital-infrastructure-research/&#34;&gt;Digital Infrastructure Grants&lt;/a&gt; (Ford Foundation, Sloan Foundation, Mozilla, Omidyar Network and Open Society Foundations)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Join Us At RightsCon 2022</title>
      <link>https://superbloom.design/learning/blog/join-us-at-rightscon-2022/</link>
      <pubDate>Thu, 26 May 2022 06:46:15 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/join-us-at-rightscon-2022/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/rightscon-banner_hu_91fecbfabd335145.png&#34; width=&#34;740&#34; height=&#34;166&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Would you like to hear how the move from deceptive design to trusted patterns is critical to our shared future?  &lt;/p&gt;
&lt;p&gt;Would you like to learn more about how to make encrypted apps more inclusive and accessible?  &lt;/p&gt;
&lt;p&gt;Do you need on the spot design and UX aid and advice to improve your tools?&lt;/p&gt;
&lt;p&gt;Simply Secure team members will be joining six sessions during RightsCon 2022: June 6-10. We’d love to see you, learn about your work, and collaborate. Come join us!&lt;/p&gt;
&lt;p&gt;You can register for RightsCon &lt;a href=&#34;https://rightscon.summit.tc/&#34;&gt;here&lt;/a&gt; and each session we are participating in is linked below.&lt;/p&gt;
&lt;h3 id=&#34;how-doing-design-is-colonial-within-humanitarian-and-human-rights-work&#34;&gt;How &amp;ldquo;doing design&amp;rsquo; is colonial within humanitarian and human rights work&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/2022/events/how-doing-design-is-colonial-within-humanitarian-and-human-rights-work-26AAcZYykzdoj1FAhTfWPX&#34;&gt;Add to my sessions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;When: June 7 @ 8.15 AM EDT | 2.15 PM CEST&lt;/li&gt;
&lt;li&gt;Who: Eriol Fox, Ngọc Triệu&lt;/li&gt;
&lt;li&gt;What: Community Lab&lt;/li&gt;
&lt;li&gt;The ways in which design is practiced in both professional and academic spheres has a history of colonial power and the ways in which designers &amp;lsquo;conduct&amp;rsquo; research, often from western countries visiting other underrepresented majority communities to &amp;lsquo;do co-design&amp;rsquo; &amp;lsquo;participatory design&amp;rsquo; and other methods with people further embeds these colonial power dynamics in the ways in which one assumes the position of &amp;lsquo;researcher&amp;rsquo; or &amp;lsquo;designer&amp;rsquo; and the others assume position of &amp;lsquo;subject of research&amp;rsquo;. Though there are &lt;a href=&#34;https://www.liberatorydesign.com/&#34;&gt;growing methodologies&lt;/a&gt;, &lt;a href=&#34;https://chicagobeyond.org/researchequity/&#34;&gt;resources&lt;/a&gt; and &lt;a href=&#34;https://www.creativereactionlab.com/&#34;&gt;organizations&lt;/a&gt; aimed at balancing the power in human-centered design and research the scales still feel tipped in favor of colonial powers. How can we come together as a humanitarian, Human Rights, technologists and Design community at RightsCon to better understand how we and our organizations participate in this balance and work together to better understand how future approaches to human-centered design and research can be practiced with equity as the priority? &lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;our-social-network-intersectional-feminist-tech-advocacy-for-journalist-safety&#34;&gt;Our social network: intersectional feminist tech advocacy for journalist safety&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/2022/events/our-social-network-intersectional-feminist-tech-advocacy-for-journalist-safety-3Po9ptiWgGB7zvf4bZK88M&#34;&gt;Add to my sessions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/2022/events/our-social-network-intersectional-feminist-tech-advocacy-for-journalist-safety-3Po9ptiWgGB7zvf4bZK88M&#34;&gt;&lt;/a&gt;When: June 7 @ 9.30 AM EDT | 3.30 PM CEST&lt;/li&gt;
&lt;li&gt;Who: Ame Elliott&lt;/li&gt;
&lt;li&gt;What: Community Lab&lt;/li&gt;
&lt;li&gt;Violence experienced by journalists online disproportionately impacts women, POC and LGBTQIA+ journalists. Existing efforts by tech platforms to keep journalists safe do not address this reality. In this community lab, led by &lt;a href=&#34;https://onlineviolenceresponsehub.org/&#34;&gt;The Coalition Against Online Violence&lt;/a&gt;, we want to hear from journalists, digital safety experts, human rights activists, and even the platforms themselves, about how we can co-design an intersectional approach to research and combat online violence against journalists by leveraging our collective experiences. We hope to collect regional case studies and examples on online abuse, finding solidarity in shared challenges and identifying successes in one region that could be ported to other regions. Ultimately our aim is to connect people from different regions around these shared issues to find solutions to combat online violence. We will facilitate breakout rooms in English, Spanish and French, and welcome everyone to participate in whichever language they are most comfortable. &lt;br&gt;
&lt;br&gt;
This community lab will be facilitated by The International Women’s Media Foundation, ARTICLE 19, Simply Secure, and Vita Activa, who are members of the Coalition Against Online Violence. The COAV is a working group of 60+ global organizations working to find better solutions for women journalists facing online abuse, harassment and other forms of digital attack. The Coalition is funded by Craig Newmark Philanthropies and founded by the International Women’s Media Foundation.  &lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;a-ux-clinic-how-to-improve-digital-tools-with-human-rights-centered-design-principles&#34;&gt;A UX clinic: how to improve digital tools with human rights-centered design principles&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/2022/events/a-ux-clinic-how-to-improve-digital-tools-with-human-rights-centered-design-principles-dxVvBSeGD8VRL7eXwjJo5N&#34;&gt;Add to my sessions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/2022/events/a-ux-clinic-how-to-improve-digital-tools-with-human-rights-centered-design-principles-dxVvBSeGD8VRL7eXwjJo5N&#34;&gt;&lt;/a&gt;When: June 7 @ 1.15 PM EDT | 7.15 PM CEST&lt;/li&gt;
&lt;li&gt;Who: &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;Human Rights Centered Design Community&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;What: Social Hour&lt;/li&gt;
&lt;li&gt;Seeking and internalizing community feedback to improve digital tools can be expensive and challenging. This clinic style workshop invites tool teams to join a dialogue with design and user experience (UX) experts with rich experience working in civil society to explore a community-centered, rights-protected approach to gather feedback.&lt;br&gt;
&lt;br&gt;
The workshop takes the format of a speed-dating style focused-group discussion. Participants are encouraged to bring the projects or tools they are working on with questions or challenges they are facing. Experts and Human Rights-Centered Design professionals will provide immediate design and UX aid and advice for the improvement of the tools to further protect the communities they are serving. Further, the workshop welcomes designers and UX professionals to discuss and develop a holistic human rights-driven design approach. We hope the clinic will bring sparks of ideas and ignite opportunities to open up collaborations and long term support.&lt;br&gt;
&lt;br&gt;
Human Rights-Centered Design is an emerging design approach and way of thinking. It could change the way of UX research and development in digital tools. Yet, it is still in an embryo stage where it needs a lot of nutritions (exchanges of ideas, especially from communities who are impacted by digital tools) to grow. We hope the participants can come to this workshop with an interest in Human Rights-Centered Design (HRCD). And through small-group discussions, participants can leave this session connecting HRCD approach and principles with their own experience in using and developing digital products, platforms, and services.  &lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;the-web-we-want-taking-action-to-stop-deceptive-designs-and-promote-trusted-design-patterns&#34;&gt;The web we want: taking action to stop deceptive designs and promote trusted design patterns&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/2022/events/the-web-we-want-taking-action-to-stop-deceptive-designs-and-promote-trusted-design-patterns-eH3HnBR82vDfkfWXnk1AcC&#34;&gt;Add to my sessions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/2022/events/the-web-we-want-taking-action-to-stop-deceptive-designs-and-promote-trusted-design-patterns-eH3HnBR82vDfkfWXnk1AcC&#34;&gt;&lt;/a&gt;When: June 8 @ 12.30 PM EDT | 6.30 PM CEST&lt;/li&gt;
&lt;li&gt;Who: &lt;a href=&#34;https://webfoundation.org/&#34;&gt;Web Foundation&lt;/a&gt;, &lt;a href=&#34;https://3x3.co/&#34;&gt;3x3&lt;/a&gt; and Simply Secure plus panellists: &lt;br&gt;
Dries Cuijpers (Senior Enforcement Officer, &lt;a href=&#34;https://www.acm.nl/nl&#34;&gt;The Netherlands Authority for Consumers and Markets&lt;/a&gt;)&lt;br&gt;
&lt;a href=&#34;http://cargocollective.com/estellehary&#34;&gt;Estelle Hary&lt;/a&gt; (Designer, CNIL - Commission Nationale de l’Informatique et des Libertés)&lt;br&gt;
&lt;a href=&#34;http://cyberlaw.stanford.edu/about/people/jen-king&#34;&gt;Dr Jennifer King&lt;/a&gt; (Privacy and Data Policy Fellow, Stanford)&lt;br&gt;
&lt;a href=&#34;https://www.linkedin.com/in/nnenna/&#34;&gt;Nnenna Nwakanma&lt;/a&gt; (Chief Web Advocate, Web Foundation)&lt;br&gt;
&lt;a href=&#34;https://www.subtraction.com/&#34;&gt;Khoi Vinh&lt;/a&gt; (Senior Director of Product Design, Adobe)&lt;/li&gt;
&lt;li&gt;What: Panel&lt;/li&gt;
&lt;li&gt;Since the formal launch of the Web Foundation’s Tech Policy Design Lab in November 2022, we have gathered evidence of the potential harms of deceptive designs (often referred to as ‘dark patterns&amp;rsquo;) including who these practices impact the most, and how they affect the most marginalized communities in particular. Over the past months, we have brought together experts from companies, governments and civil society to collaborate constructively to develop policy and product solutions and co-create alternatives for more ethical, empathetic, trusted design that puts people and their needs first.&lt;br&gt;
&lt;br&gt;
Join us as we speak with experts from across the world who will discuss how the move from deceptive design to trusted patterns is critical to our shared future. Learn how to participate in the network of civil society, industry, and government practitioners who will carry the work forward from the Tech Policy Design Lab. &lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;dismantling-deceptive-design-global-policy-design-workshop-for-developing-trusted-design-patterns&#34;&gt;Dismantling deceptive design: global policy design workshop for developing trusted design patterns&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/2022/events/dismantling-deceptive-design-global-policy-design-workshop-for-developing-trusted-design-patterns-wjE8A29WkFog5xSiAaPqVn&#34;&gt;Add to my sessions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/2022/events/dismantling-deceptive-design-global-policy-design-workshop-for-developing-trusted-design-patterns-wjE8A29WkFog5xSiAaPqVn&#34;&gt;&lt;/a&gt;When: June 9 @ 9.30 PM EDT | 3.30 PM CEST&lt;/li&gt;
&lt;li&gt;Who: &lt;a href=&#34;https://webfoundation.org/&#34;&gt;Web Foundation&lt;/a&gt;, &lt;a href=&#34;https://3x3.co/&#34;&gt;3x3&lt;/a&gt; and Simply Secure (Georgia Bullen, Ame Elliott)&lt;/li&gt;
&lt;li&gt;What: Community Lab&lt;/li&gt;
&lt;li&gt;Everything we do online is influenced by how the tools we use are built. Deceptive designs (known as ‘dark patterns’) built into user interfaces alter decision-making or trick users into taking actions they might not otherwise take. While some countries have been focusing on this issue, more needs to be done to ensure that everyone is protected. That is why our work explored a more global scope. Through a series of policy design workshops, we are bringing together stakeholders across sectors and learned directly from those affected by technology to collaboratively redesign our digital spaces. Our facilitators for the session are from India, Nigeria and the United States. We will be sharing evidence of the potential harms of deceptive designs including who these practices impact the most, and how they affect the most marginalized communities.&lt;br&gt;
&lt;br&gt;
We believe that people’s experiences must drive policy and product design, and solutions must take into account the full diversity of those who use digital tools. Let’s come together to share diverse experiences from around the world about the dangers of deceptive design - and how communities counter them - and what we can do as individuals and policymakers to combat these practices globally.&lt;br&gt;
&lt;br&gt;
Let’s build a safe, empowering, and secure web. A web we all can trust.  &lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;encrypted-apps-that-leave-no-one-behind&#34;&gt;Encrypted apps that leave no one behind&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/2022/events/encrypted-apps-that-leave-no-one-behind-Lke798enDiPYHDgS7Ztji&#34;&gt;Add to my sessions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://rightscon.summit.tc/t/2022/events/encrypted-apps-that-leave-no-one-behind-Lke798enDiPYHDgS7Ztji&#34;&gt;&lt;/a&gt;When: June 9 @ 1.30 PM EDT | 7.30 PM CEST&lt;/li&gt;
&lt;li&gt;Who: Georgia Bullen&lt;/li&gt;
&lt;li&gt;What: Panel&lt;/li&gt;
&lt;li&gt;Encrypted apps are a powerful tool to enable secure communication amongst human rights defenders globally. Yet, most of the existing technologies have challenges when it comes to inclusivity and accessibility; be that failure to meet the needs of peoples with disabilities, support different languages, or ability to function within contexts of unstable internet access.&lt;br&gt;
&lt;br&gt;
This RightsCon panel session builds on the Encrypted Apps Action Coalition under Tech for Democracy, which aims at bringing together relevant stakeholders to ensure that accessible encrypted communications technologies exist for all people who might wish to communicate privately. The panel will both discuss the existing needs, the works of the Action Coalition thus far, and allow for questions and inputs from participants.&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Hey, Whose Keys Are These? </title>
      <link>https://superbloom.design/learning/blog/hey-whose-keys-are-these/</link>
      <pubDate>Tue, 03 May 2022 15:18:27 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/hey-whose-keys-are-these/</guid>
      <description>&lt;h2 id=&#34;guiding-mailvelope-users-through-the-headaches-of-key-management&#34;&gt;Guiding Mailvelope users through the headaches of key management&lt;/h2&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/1-mailvelope2-cover_hu_2d92c862ca601fef.jpg&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;a href=&#34;http://mailvelope.com&#34;&gt;Mailvelope&lt;/a&gt; browser extension helps people add an extra layer of security to their email communications by making PGP encryption accessible and usable.&lt;/li&gt;
&lt;li&gt;With support from the &lt;a href=&#34;https://usable.tools/blog/2020-10-01-uxfund2020/&#34;&gt;UXFund&lt;/a&gt;, Simply Secure designed and tested new ways that Mailvelope could help users if they received an email from a contact who used a new keypair.&lt;/li&gt;
&lt;li&gt;With these UX changes, Mailvelope continues to offer usable security measures to more people who need it.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;This is the second blog post in a series about working with the Mailvelope team. Check out &lt;a href=&#34;https://superbloom.design/learning/blog/finding-the-balance-adding-support-for-organization-wide-pgp-keys-to-mailvelope/&#34;&gt;part 1&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;If you’ve ever needed to send an email that nobody except the recipient can read, you’ve probably heard of PGP. And no matter how expert you are, you’ve probably gotten stuck once or twice managing keys.&lt;/p&gt;
&lt;p&gt;For over 30 years, the &lt;a href=&#34;https://en.wikipedia.org/wiki/Pretty_Good_Privacy&#34;&gt;PGP&lt;/a&gt; (Pretty Good Privacy) encryption method has allowed people to encrypt their emails so that intercepted messages can’t be read by adversaries, email providers, ISPs, or indeed any third party. To accomplish this, messages are encrypted into a code that only the recipient can unscramble, using a keypair mechanism that both encrypts and unlocks messages. All PGP users have their own keypair: 1) a public key to share with their contacts, and 2) a private key to keep secret. (To learn more about how public-key cryptography works, &lt;a href=&#34;https://ssd.eff.org/en/module/deep-dive-end-end-encryption-how-do-public-key-encryption-systems-work#:~:text=Public%20key%20cryptography%20allows%20someone,decrypt%20messages%20encrypted%20to%20you.&#34;&gt;check out this explainer from the Electronic Frontier Foundation&lt;/a&gt;.)&lt;/p&gt;
&lt;p&gt;Managing a contact list of public keys is like managing the contact list in your phone: people occasionally get new public keys, just like they may get new email or postal addresses. Their public key is probably uploaded to a server called a keyserver, but can expire or be manually revoked. And in order to send a secure email to a person, you need to know a public key that you are certain belongs to them. That’s where &lt;a href=&#34;http://mailvelope.com&#34;&gt;Mailvelope&lt;/a&gt; comes in. &lt;/p&gt;
&lt;p&gt;Mailvelope is a browser extension that integrates key management with your webmail interface. This means you can select keys from an address book, or “keyring,” and send an encrypted email in just a few clicks. But what about these tricky cases when people change their keys, or even have multiple keys? How can you be sure you’re messaging the right person? With the support of &lt;a href=&#34;https://usable.tools/blog/2020-10-01-uxfund2020/&#34;&gt;UXFund&lt;/a&gt;, Mailvelope came to Simply Secure to collaborate on a solution.&lt;/p&gt;
&lt;h2 id=&#34;key-managements-two-big-headaches&#34;&gt;Key management’s two big headaches&lt;/h2&gt;
&lt;p&gt;How could we make key management less confusing using clearer UX design? We approached the two most confusing key management scenarios by setting up some lightweight user feedback sessions. &lt;/p&gt;
&lt;h3 id=&#34;scenario-a-what-if-you-get-an-email-from-maria-but-its-encrypted-with-a-different-key-than-before-is-this-really-maria-or-is-it-an-imposter&#34;&gt;Scenario A: What if you get an email from Maria, but it’s encrypted with a different key than before? Is this really Maria? Or is it an imposter?&lt;/h3&gt;
&lt;p&gt;This is like getting a letter from Maria with a New York postmark when you thought she lived in Los Angeles. It might be legitimate, but you might want to check with her and see if she moved. &lt;/p&gt;
&lt;p&gt;Sometimes people revoke or abandon an old keypair (public + private keys) and generate a new one. Although generating a new keypair may be necessary if the old one was compromised, a new keypair may also mean that somebody is impersonating your contact and intercepting messages (called a “&lt;a href=&#34;https://en.wikipedia.org/wiki/Man-in-the-middle_attack&#34;&gt;Monster-In-The-Middle&lt;/a&gt;” attack). We wanted to find a way to help Mailvelope’s users if they received an email from a contact who used a new keypair.&lt;/p&gt;
&lt;p&gt;We focused on a notification that would alert the Mailvelope user about a sender’s keypair change. Our goal was to support the user as much as possible and not ask them to make any decisions they didn’t understand. To offer guidance in this unfamiliar, and potentially risky, situation, we knew that careful, concise interface guidance was crucial. For comparison, we found examples from other messaging software, like WhatsApp. Its notification message reads, &amp;ldquo;Your security code with [person] changed. Tap to learn more&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/2-mailvelope2-whatsapp_hu_e980acb48d9f5352.png&#34; width=&#34;740&#34; height=&#34;675&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;When a person gets a new phone, their contacts will see the message: “Your security code with X has changed.” Tap to learn more displays the message: “Your security code with X  changed because there was a registration on a new device of theirs.”&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We decided on a modal design that displayed what happened, the new key details, potential constraints, and advice for what to do next&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/3-mailvelope2-modal_hu_b01f207f0e664a44.png&#34; alt=&#34;We decided on a modal design that displayed what happened, the new key details, potential constraints, and advice for what to do next. &#34; width=&#34;740&#34; height=&#34;440&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;We decided on a modal design that displayed what happened, the new key details, potential constraints, and advice for what to do next.&lt;/em&gt;&lt;/p&gt;
&lt;h4 id=&#34;how-testing-helped-us-solidify-our-design&#34;&gt;How testing helped us solidify our design&lt;/h4&gt;
&lt;p&gt;When we asked people what they would do when faced with this design, we learned that our pop-up message helped users immediately understand the situation: “Maria probably changed her key.” Yet, participants were cautious (PGP users tend to be security-minded!): “Before accepting the key, I would get an OK from Maria on Signal.” The message we added is clearly necessary: as one user said, “The warning makes me feel more comfortable that I&amp;rsquo;m doing the right thing.” In our testing, some people chose &lt;em&gt;Add to Keyring&lt;/em&gt; for the new keypair, while others preferred to stay on the safe side with &lt;em&gt;Cancel&lt;/em&gt;. Offering both options allowed them to select the choice that best matched their level of risk. &lt;/p&gt;
&lt;p&gt;While user testing confirmed some design choices, it also prompted some changes. We realized that the process needed a confirmation message for adding a key. One participant said, “I think I need to go to another page where I save the key.” A participant said, &amp;ldquo;I feel pressured to add it to my keyring, because the alternative is that it disappears forever.&amp;rdquo; So we proposed to change the copy from &lt;em&gt;Cancel&lt;/em&gt; to &lt;em&gt;Not now.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/4-mailvelope2-confirmation_hu_1225471e697969db.png&#34; width=&#34;740&#34; height=&#34;186&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/4-mailvelope2-not-now_hu_50df46ca05b9f59c.png&#34; width=&#34;740&#34; height=&#34;197&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;We proposed some changes to the design such as a confirmation message and changing the secondary button to “not now”.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Testing our prototype proved incredibly useful because we learned which designs achieved our goal.&lt;/p&gt;
&lt;h3 id=&#34;scenario-b-what-if-you-want-to-send-an-email-to-maria-but-you-have-many-different-keys-for-maria&#34;&gt;Scenario B: What if you want to send an email to Maria, but you have many different keys for Maria?&lt;/h3&gt;
&lt;p&gt;While changing out keypairs is a useful security tactic, a side effect is that other people still have all those old keys. It’s as though Maria has moved a lot recently and you might not be sure where you can send her a letter. &lt;/p&gt;
&lt;p&gt;To help Mailvelope users choose their recipients’ current key quickly and easily, we focused on the compose email window, specifically the autocomplete dropdown for the recipient’s email. We considered various well-known symbols (like a checkmark and flag) or adding a tag (like “default key” “primary key” or “Mailvelope’s pick”) that could identify the key, but a lot of these ideas already had another meaning in the PGP world. Any new icons that we made up created more questions than answers. In short, this was a complicated message to boil down to one symbol. And unfortunately, highlighting and bolding interfered with the search list functionality.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/5-mailvelope2-send-original_hu_b4e9b22996bbfb5b.png&#34; width=&#34;740&#34; height=&#34;307&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;In the Mailvelope email compose window, a user starts typing in the email recipient and sees four possible key options for Maria.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We landed on putting the current key first in the list and indenting the old keys. We thought this design would guide users to the right choice but still give them options. The next step was testing it with users - would they understand what the indented list meant?&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/6-mailvelope2-send-test_hu_1033a8d72f3c583c.png&#34; width=&#34;740&#34; height=&#34;304&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;We converged on a dropdown list design that places the current key first and indents the other keys.&lt;/em&gt; &lt;/p&gt;
&lt;h4 id=&#34;good-design-can-be-invisible&#34;&gt;Good design can be invisible&lt;/h4&gt;
&lt;p&gt;When people typed in Maria’s email and saw four keys for Maria, they were puzzled. One participant said, “This seems wrong. Maria has many keys, somehow I imported all of them, and none are revoked.” This indented list was causing confusion, provoking questions but not giving enough answers. Either we needed to add more information or take away irrelevant information. &lt;/p&gt;
&lt;p&gt;Our “a-ha” moment came when we realized that users don’t actually need to access old keys when they send messages (although old keys are still useful for decrypting old messages). So we scrapped all our “alternate key” designs and made the simplest version - just one public key is shown for Maria, because that’s all the sender needs to see. Our final design intervention is not even visible in the UI.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/7-mailvelope2-send-final_hu_c79944836dfc2f.png&#34; width=&#34;740&#34; height=&#34;676&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Our final design intervention is not even visible in the UI. Instead of displaying all the keys, we just show the right one for Maria. We show the user only what they need to see.&lt;/em&gt; &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;👉 Do you want to try this kind of user testing? We believe in the power of user testing so much that we put together a &lt;a href=&#34;https://sprblm.github.io/devs-guide-to/&#34;&gt;microsite&lt;/a&gt; with concise guides and examples to get you started.&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id=&#34;onward&#34;&gt;Onward&lt;/h2&gt;
&lt;p&gt;For over 10 years, Mailvelope has helped people add a protective layer to their email communications. Mailvelope users are people who need a high level of security and can’t always use other secure communication tools, like Signal. They may not have a comprehensive understanding of how keypairs work – but they shouldn’t have to. With these small UX changes, Mailvelope continues its slow and steady journey towards offering usable security measures to more people who need it. &lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;Project Contributors: &lt;/p&gt;
&lt;p&gt;Kelsey Smith, UX Designer at Simply Secure&lt;/p&gt;
&lt;p&gt;Thomas Oberndörfer, developer and founder of Mailvelope&lt;/p&gt;
&lt;p&gt;Hero image of keys: by &lt;a href=&#34;https://unsplash.com/photos/vLuj--T3Fp8&#34;&gt;Alp Duran, Unsplash&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;With support from &lt;a href=&#34;https://usable.tools/blog/2020-10-01-uxfund2020/&#34;&gt;UXFund&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Accounting Administrator, Part-Time</title>
      <link>https://superbloom.design/community/opportunities/accounting-administrator-10hrs-week/</link>
      <pubDate>Tue, 19 Apr 2022 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/opportunities/accounting-administrator-10hrs-week/</guid>
      <description>&lt;p&gt;We are a small US 501(c)3 nonprofit organization, founded in 2014 with the goal of making security tools easier to use. We believed – and still do – that security doesn’t have to be confusing to end users. We’ve contributed design to a variety of tools that enhance security, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We’ve held &lt;a href=&#34;https://simplysecure.org/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we’ve done a lot more than usable security. Just in the last year, we’ve launched a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;p&gt;Simply Secure is seeking a part-time virtual Accounting Administrator (US only) to help process financial needs and reporting. Reporting to the Finance &amp;amp; Operations Manager, the ideal candidate has financial expertise working in an office environment (in person or virtual), preferably in the non-profit sector. They are very adept at using web-based applications to work with a remote team both in the US and in Europe, and can help us manage our finances.&lt;/p&gt;
&lt;h3 id=&#34;duties-and-responsibilities&#34;&gt;Duties and Responsibilities&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Process monthly hours, receipts, and expense claims.&lt;/li&gt;
&lt;li&gt;Prepare invoices, manage AR flow, and update records in a timely manner.&lt;/li&gt;
&lt;li&gt;Collaborate with third-party bookkeeping provider to ensure efficient and accurate financial reporting.&lt;/li&gt;
&lt;li&gt;Support financial reporting for grants and other necessary contracts. &lt;/li&gt;
&lt;li&gt;Support management of company assets and financial expenditures.&lt;/li&gt;
&lt;li&gt;Adhere to best practices in accounting, as outlined by industry experts and espoused by the company.&lt;/li&gt;
&lt;li&gt;Filing and documentation of bills, invoices and expense reports.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;required-skills&#34;&gt;Required Skills&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Experience with Quickbooks and accounts administration.&lt;/li&gt;
&lt;li&gt;Experience with multi-currency transactions and processes.&lt;/li&gt;
&lt;li&gt;Knowledge of payment platforms (e.g. Bill.com, Divvy, Wise).&lt;/li&gt;
&lt;li&gt;Advanced knowledge of Google Workspace (Gmail, Google Drive, Docs, Sheets, Calendar and Google Meet).&lt;/li&gt;
&lt;li&gt;Familiarity with time tracking platforms (e.g. Harvest).&lt;/li&gt;
&lt;li&gt;Experience working with non-profit entities is a plus, but not required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;work-hours&#34;&gt;Work Hours &lt;/h3&gt;
&lt;p&gt;This is a part time position. Salary commensurate with experience. While the contractor may set their own hours, we do expect some overlap with members of the Operations team for meetings, etc. Core work hours are between 8-5pm ET.&lt;/p&gt;
&lt;p&gt;To be considered for this position, we ask that you submit a resumé, along with a cover letter explaining why you are interested in this position, to: &lt;a href=&#34;mailto:hr@simplysecure.org&#34;&gt;hr@simplysecure.org&lt;/a&gt;. We will be reviewing applications on a rolling basis until this position is filled.&lt;/p&gt;
&lt;p&gt;We believe that systemic bad behaviors disproportionately hurt the most marginalized people in society — including people of color, people from working class backgrounds, women and LGBTQ people. We believe that these communities must be centered in the work we do. We strongly encourage applications from people with these identities or who are members of other marginalized communities. We are open to candidates from around the world. Final hiring decisions will be contingent upon our ability to contract and pay in the candidate’s country. Simply Secure does not provide relocation or visa support.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Finance &amp; Operations Manager</title>
      <link>https://superbloom.design/community/opportunities/finance-operations-manager/</link>
      <pubDate>Tue, 19 Apr 2022 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/opportunities/finance-operations-manager/</guid>
      <description>&lt;p&gt;We are a small US 501(c)3 nonprofit organization, founded in 2014 with the goal of making security tools easier to use. We believed – and still do – that security doesn’t have to be confusing to end users. We’ve contributed design to a variety of tools that enhance security, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We’ve held &lt;a href=&#34;https://simplysecure.org/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we’ve done a lot more than usable security. Just in the last year, we’ve launched a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;p&gt;Simply Secure is seeking a full-time remote Finance and Operations Manager (US only, with immediate availability) to help develop and manage its finances and operations. We’re looking for someone who can own and manage the relationships with a variety of third-party finance and operations vendors. As an active member of the team, this person will stay on top of project timelines in relation to financial milestones, and support the team in grant reporting. On a monthly basis, our organization processes 20+ contracts with funding partners and external contractors— this role will lead this effort and manage our financial flow.  &lt;/p&gt;
&lt;p&gt;Reporting to the Managing Director, the ideal candidate has more than five years’ experience working in an office environment (in person or virtual), preferably in the non-profit sector. They are very adept at using web-based applications to work with a remote team both in the US and in Europe, and can help us manage our finances and processes in a scalable way.&lt;/p&gt;
&lt;h3 id=&#34;duties-and-responsibilities&#34;&gt;Duties and Responsibilities&lt;/h3&gt;
&lt;h4 id=&#34;finance&#34;&gt;Finance:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Manage Business/Accounts Administrator and third-party Finance team to ensure invoices, receipts and expense claims are processed in a timely manner and to support accurate financial reporting.&lt;/li&gt;
&lt;li&gt;Assist with quarterly and annual financial review.&lt;/li&gt;
&lt;li&gt;Lead tax compliance process and liaise with third-party tax accountant.&lt;/li&gt;
&lt;li&gt;Track and manage financial reporting requirements for grants.&lt;/li&gt;
&lt;li&gt;Manage ongoing financial reporting to assist management with budgeting and financial tracking.&lt;/li&gt;
&lt;li&gt;Update management on any financial discrepancies found during tax filing or invoicing duties.&lt;/li&gt;
&lt;li&gt;Assist staff with use of accounts systems and field related questions.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;operations&#34;&gt;Operations:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Own and manage relationships with third-party service providers for US and international payroll and benefits. &lt;/li&gt;
&lt;li&gt;Administer and manage our contracting process, including developing, processing, tracking and filing service agreements and vendor contracts ensuring appropriate tax documentation is received and completed.&lt;/li&gt;
&lt;li&gt;Support our fiscally sponsored projects in all things operations and financial.&lt;/li&gt;
&lt;li&gt;Communicate and support organization staff in operational and administrative processes.&lt;/li&gt;
&lt;li&gt;Lead operational and financial processes for our Fiscally Sponsored Projects. &lt;/li&gt;
&lt;li&gt;Assist management in planning and preparing board meeting packets including filing meeting minutes, drafting resolutions and other board documentation as needed.&lt;/li&gt;
&lt;li&gt;Support the team on grants writing, management and reporting.&lt;/li&gt;
&lt;li&gt;Process improvement: Identify and implement user-centered process improvements that support our team in focusing their time and effort on our mission.&lt;/li&gt;
&lt;li&gt;Lead new staff onboarding and offboarding from an operational perspective.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;required-skills&#34;&gt;Required Skills&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Experience managing third-party financial and operational vendors and platforms for successful non-profit organizational management.&lt;/li&gt;
&lt;li&gt;Three or more years experience with Quickbooks and financial management.&lt;/li&gt;
&lt;li&gt;Knowledge of multi-currency accounting and transactions.&lt;/li&gt;
&lt;li&gt;Advanced knowledge of Google Workspace (Gmail, Google Drive, Docs, Sheets, Calendar and Google Meet).&lt;/li&gt;
&lt;li&gt;Curious about new platforms and integrations for supporting organizational efficiency.&lt;/li&gt;
&lt;li&gt;Experience in using web-based business software, especially project management, billing and invoicing, and time tracking platforms (e.g. bill.com, Harvest, Notion). &lt;/li&gt;
&lt;li&gt;Ensures all work is completed on time, professionally, and to a high standard.&lt;/li&gt;
&lt;li&gt;Experience working at a nonprofit preferred.&lt;/li&gt;
&lt;li&gt;Previous use of Slack is beneficial.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;work-hours-and-benefits&#34;&gt;Work Hours and Benefits&lt;/h3&gt;
&lt;p&gt;This position is for a full-time employee, 40 hours per week with availability during our core work hours (8-5pm ET), at $65,000-80,000 per year depending on experience. Benefits include health insurance, sick leave, generous parental leave, and monthly tech stipend.&lt;/p&gt;
&lt;p&gt;To be considered for this position, we ask that you submit a resumé, along with a cover letter explaining why you are interested in this position to: &lt;a href=&#34;mailto:hr@simplysecure.org&#34;&gt;hr@simplysecure.org&lt;/a&gt;. We will be reviewing applications on a rolling basis until this position is filled.&lt;/p&gt;
&lt;p&gt;We believe that systemic bad behaviors disproportionately hurt the most marginalized people in society — including people of color, people from working class backgrounds, women and LGBTQ people. We believe that these communities must be centered in the work we do. We strongly encourage applications from people with these identities or who are members of other marginalized communities. We are open to candidates from around the world. Final hiring decisions will be contingent upon our ability to contract and pay in the candidate’s country. Simply Secure does not provide relocation or visa support.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>On Starting Out In UX: An Interview With Stefanie Mühlbacher, UX Designer</title>
      <link>https://superbloom.design/learning/blog/on-starting-out-in-ux-an-interview-with-stefanie-muhlbacher-ux-designer/</link>
      <pubDate>Fri, 25 Mar 2022 16:29:23 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/on-starting-out-in-ux-an-interview-with-stefanie-muhlbacher-ux-designer/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img_0445_hu_7639fe594b7a5cce.jpeg&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Stefanie points out that a lot of UX-focused resources out there focus on the HOW instead of the WHY of UX methods. There’s an opportunity for growth here. &lt;/li&gt;
&lt;li&gt;For new UX designers, Stefanie encourages them to start working on real-world projects as soon as possible – learning on the job is key to expanding your portfolio.&lt;/li&gt;
&lt;li&gt;For technical teams, she advises involving UX designers from the start to make the software more usable.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Last year, we partnered with Stefanie Mühlbacher to support the &lt;a href=&#34;https://arso.xyz/&#34;&gt;arso&lt;/a&gt; development collective  on user experience and testing for &lt;a href=&#34;https://sonar.arso.xyz/&#34;&gt;Sonar&lt;/a&gt;. Having recently graduated from a UX bootcamp program, we asked Stefanie to share her thoughts on the experience of working on this highly-technical project.&lt;/p&gt;
&lt;h2 id=&#34;about-sonar&#34;&gt;About Sonar&lt;/h2&gt;
&lt;p&gt;Sonar is an open source framework to manage, annotate, and full-text search through data, including media files. It uses peer-to-peer technology to replicate and share collections, and can be used to develop decentralized applications. Some use cases the arso team has explored include searchable and replicable media archives, research databases, blogs, archiving and searching chat logs. &lt;/p&gt;
&lt;p&gt;The arso team consists of a handful of developers working together as a loose collective. Their work centers around preserving and exploring information and media.&lt;/p&gt;
&lt;p&gt;The arso team reached out to Simply Secure for guidance on developing and testing relevant UX patterns. We expected that this might include patterns for key exchange, schema handling, multiwriter conflict resolution, or access management. Our shared goals were to work with actual and potential users on the refinement of UX patterns for P2P search and discovery.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;This interview was edited for length and clarity.&lt;/em&gt; &lt;/p&gt;
&lt;h2 id=&#34;meet-stefanie&#34;&gt;Meet Stefanie&lt;/h2&gt;
&lt;p&gt;Stefanie is a UX designer working - at the moment - for a startup in Munich. She lives on a farm and mostly works from home. Her passions include open-source software, ethical design and cows. Find her portfolio at &lt;a href=&#34;&#34;&gt;stefaniemue.com&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Tell us a little bit about yourself &amp;ndash; what led you to become a UX designer?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I have a background in product design, and kind of dabbled in UX during my studies. After graduation I struggled to find a job for almost a year, and joined a UX bootcamp to get some marketable skills. I liked it way more than I expected and really got into UX, how user-focused it is, and the creative methods its practitioners employ to tackle very complex problems.&lt;/p&gt;
&lt;p&gt;When I was about two-thirds through bootcamp, I heard that friends of friends were working on an open source project, so I scraped together all my courage and asked if they needed a UX designer on their team. A couple of weeks later, I started working on the Sonar project. It was not my first collaboration after bootcamp (I had joined a social project as a UXer while still in bootcamp), but it was my first collaboration with developers and on a very tech-heavy project.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;As one of your first projects after bootcamp, what do you feel you were well prepared for? And what resources do you wish you had?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;During bootcamp, I practiced doing user research and felt quite confident preparing and conducting user interviews and usability tests. Analyzing research data and creating personas and user stories was also something I had learned recently, so I had some tools in my toolbox.&lt;/p&gt;
&lt;p&gt;I looked up UX tools and methods from my bootcamp and applied them directly to the project. I also had help from Simply Secure: I got feedback from [former Simply Secure employee] Eileen and &lt;a href=&#34;https://twitter.com/klsyjnn&#34;&gt;Kelsey&lt;/a&gt; on my research, analysis and prototyping, which was great. It was fantastic to have more experienced UX designers to talk to! The workshops we did with Simply Secure also helped to create mutual understanding and alignment in the team. &lt;/p&gt;
&lt;p&gt;The collaboration with arso was also invaluable. They spent a lot of time explaining to me how Sonar works and what their plans and ideas were. Some also attended user interviews, or helped to write a survey.&lt;/p&gt;
&lt;p&gt;What I really could have used were more resources on how developers and designers can work together successfully, especially in very small teams and without a dedicated project manager. Most of the resources I found were by and for people working in larger companies or in startups, and didn’t really fit our team constellation. Something that was also missing was more information on when to employ which UX methods and how to form a strategy. A lot of resources focus on the HOW instead of the WHY of UX methods.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What can you share about the experience of working on a project about decentralization? What sort of technical complexities did you face?&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;It was quite difficult for me to understand how Sonar works, and especially how things might work differently than I expected based on experiences with other software. Working with privacy-first software that was developed with little resources means that some features I imagined were just not possible, so I had to learn to work with those technical limitations. &lt;/p&gt;
&lt;p&gt;Another challenge we faced was that it was quite hard to find people for the user interviews — we didn&amp;rsquo;t get a lot of responses to emails we sent out. But the people we did reach, once we built a rapport with them (or if they knew someone on the team), we had 2+ hour conversations with them! They were really enthusiastic about the project and super into helping with user testing. They all asked us to give them updates, joined our mailing list etc. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What would your recommendation be for UX designers working on highly technical projects?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Talk to the developers A LOT and don’t be afraid to ask “stupid” questions. Keep asking “why” and “how” until you are sure you understood everything. Take notes while talking to your devs. Some especially complex things you might only understand when you read through them later. &lt;/p&gt;
&lt;p&gt;Last but not least, remember that saying about images being worth a thousand words? When in doubt, draw a diagram of your mental model of the software, how you think it works, and get the devs on your team to look at it with you and adjust it until it’s correct. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Is there anything else you&amp;rsquo;d like to share with new UX designers, technical teams, and/or the space at large?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;Advice for new UX Designers&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;When you get out of university or bootcamp, start working on real-world projects as quickly as you can. You will learn so much more than you could on your own. There are many projects, also in the open source community that need your skills.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;Advice for technical teams&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Dare to involve UX designers into your work from the start!&lt;/p&gt;
&lt;p&gt;The biggest challenge I faced working on Sonar was that I joined the project at the end, when most of the development work was already done. The team knew that UX could bring value to their project, but had zero experience working with UX designers. My biggest frustration was that I could not really work together with the team, because they were already moving on to another project. &lt;/p&gt;
&lt;p&gt;When I was wrapping up my work on the project, I asked the arso team for feedback on the UX process and outcomes. I got the same response from everyone: “we should have done this sooner!” They all agreed that involving a UX designer from the start in a project would have made the whole development process easier, helping to create tasks for developers and making the software more usable and easier to understand. I was incredibly happy to hear this. &lt;/p&gt;
&lt;p&gt;There are already many gifted developers in the open-source space, but we need more UX designers! And developers recognizing the value of UX design is already one step in that direction.&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;Project Contributors: Kelsey Smith, Eileen Wagner, and Stefanie Mühlbacher, in partnership with the arso development collective. &lt;/p&gt;
&lt;p&gt;With support from the &lt;a href=&#34;https://nlnet.nl/&#34;&gt;NLNet Foundation&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Designing Better Data Futures</title>
      <link>https://superbloom.design/learning/blog/designing-better-data-futures/</link>
      <pubDate>Wed, 16 Mar 2022 19:24:43 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/designing-better-data-futures/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/iris_lei_for_popular_science_hu_6ee5c84ac5a01c34.webp&#34; width=&#34;740&#34; height=&#34;494&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Image: Iris Lei for Popular Science&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;It’s March 2022. We’re 2 decades into the new millennium, 54 years after Stanley Kubrick and Arthur C. Clarke imagined humanity traveling to Jupiter with HAL as the guide, and 43 years since Octavia Butler imagined time travel as an exploration of history and heritage in her novel Kindred. Science fiction and design have long been key tools in imagining the future — particularly to explore humanity’s relationship with information technology. &lt;/p&gt;
&lt;p&gt;What if we could imagine and build a future where we control our data, what is shared, who it’s shared with, and how it’s used? What if we could use our data to drive responsible innovation — like if our home energy usage data were shared with green energy companies? Or could be used to lower the cost of something like a home mortgage?  We know the technology exists, so what policies and incentives do we need to give control to consumers? How can we catalyze social and political conversations that critically question our current data dynamic?&lt;/p&gt;
&lt;p&gt;To explore these questions, we teamed up with the &lt;a href=&#34;https://digital-lab.consumerreports.org/&#34;&gt;Digital Lab at Consumer Reports&lt;/a&gt;, 3 science fiction writers, and a cohort of 17 experts to build short science fiction stories. Each story is set in the US in 2030, exploring alternative realities around our relationship with data. &lt;/p&gt;
&lt;p&gt;Published in partnership with &lt;a href=&#34;https://www.popsci.com/&#34;&gt;Popular Science&lt;/a&gt;, these &lt;em&gt;Alternate Data Realities&lt;/em&gt; are a three-story series, exploring near future scenarios in which “we the people” benefit from our own data. &lt;/p&gt;
&lt;p&gt;These stories aren’t utopic &amp;ndash; after all, the protagonists still live in an America grappling with worsening climate change, climbing housing prices, and supporting our elderly parents. But these stories explore a different relationship between humanity and data.  Following each story, a response essay from a policy expert offers actionable recommendations on what’s needed for this alternate reality to come to life. &lt;/p&gt;
&lt;p&gt;We hope that these stories reach far and wide to spur imagination and help us break out from our norms to co-design alternative data realities.&lt;/p&gt;
&lt;h3 id=&#34;explore-the-stories&#34;&gt;Explore the Stories&lt;/h3&gt;
&lt;h4 id=&#34;shared-data&#34;&gt;&lt;a href=&#34;https://www.popsci.com/technology/shared-data-a-short-story-from-an-alternate-future/?taid=6230ac10e9b021000122d0c2&amp;amp;utm_campaign=trueanthem_AI&amp;amp;utm_medium=social&amp;amp;utm_source=twitter&#34;&gt;Shared Data&lt;/a&gt;&lt;/h4&gt;
&lt;p&gt;by &lt;a href=&#34;https://twitter.com/m_older&#34;&gt;Malka Older&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;At the heart of Shared Data is a hypothesis of a future project and cooperative that could have numerous benefits for consumers- a shared data hub and cooperative that provides real time data, insights, and social interaction spaces for communities to provide mutual aid in real time.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Policy Response by:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/dmarti&#34;&gt;Don Marti&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/carolinesinders&#34;&gt;Caroline Sinders&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Rebecca Weiss&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Expert Advisors:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/dcalacci&#34;&gt;Dan Calacci&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/carolinesinders&#34;&gt;Caroline Sinders&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Rebecca Wei&lt;a href=&#34;https://twitter.com/helveticade&#34;&gt;&lt;/a&gt;ss&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/helveticade&#34;&gt;Cade Diehm&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;the-memory-of-tomatoes&#34;&gt;&lt;a href=&#34;https://www.popsci.com/technology/the-memory-of-tomatoes-short-story/&#34;&gt;The Memory of Tomatoes&lt;/a&gt;&lt;/h4&gt;
&lt;p&gt;by &lt;a href=&#34;https://twitter.com/BonnieJoStuffle&#34;&gt;Bonnie Jo Stufflebeam&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A world of the near future where an interesting blend of guarded private spaces, and more intrusive connected technologies co-exist. Where a woman persevering through Alzheimer’s has uploaded her previous thoughts and memories to her own AI via a “neuralink,” and has delegated to her daughter her data access rights &amp;ndash; in this instance, to her “smart” pill case.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Policy Response by:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://twitter.com/richardswhitt&#34;&gt;Richard Whitt&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Expert Advisors:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/EmDohh&#34;&gt;Meag Doherty&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/nickmvincent&#34;&gt;Nick Vincent&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/richardswhitt&#34;&gt;Richard Whitt &lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/nandoodles&#34;&gt;Nandini Jammi&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/caseorganic&#34;&gt;Amber Case&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/JusTechne&#34;&gt;Nicolo Zingales&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;homeheart&#34;&gt;&lt;a href=&#34;https://t.co/cPuOsDXatj&#34;&gt;Home@Heart&lt;/a&gt;&lt;/h4&gt;
&lt;p&gt;by &lt;a href=&#34;https://twitter.com/s_meems&#34;&gt;Sameem Siddiqui&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A sagacious illustration of how we could be convinced to monetize our data in the absence of strong privacy legislation. It tells the story of a young couple of academics who decide to finance their first house through an interest-free loan from a housing union (“Ubiquity”) open to university staff, faculty and students. In exchange, the union requires collection of data of the entire household for 30 years, or until whenever the loan is paid back.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Policy Response by:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://twitter.com/JusTechne&#34;&gt;Nicolo Zingales &lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Expert Advisors:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/dmarti&#34;&gt;Don Marti&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/richmondywong&#34;&gt;Richmond Y. Wong&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;Robert Mahari&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/ddpforall&#34;&gt;Enoch H. Liang&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/afua_bruce&#34;&gt;Afua Bruce &lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/sarahdrinkwater&#34;&gt;Sarah Drinkwater&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;A big thank you to Consumer Reports, Popular Science, and Mozilla Foundation for their support and partnership in this project. Thank you to Torie Bosch for advice, and sharing learnings from the Slate’s Future Tense. And congratulations to our 3 people Malka Older, Sameem Siddiqui, and Bonnie Jo Stufflebeam, and 17 expert advisors who imagined new realities, and then built the map to make them possible!&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>[Open Call] Submissions for “Reimagining Digital Consent: A Discussion &amp; Gallery Exhibition” at MozFest 2022</title>
      <link>https://superbloom.design/learning/blog/open-call-submissions-for-reimagining-digital-consent-a-discussion-gallery-exhibition-at-mozfest-2022/</link>
      <pubDate>Fri, 25 Feb 2022 12:34:41 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/open-call-submissions-for-reimagining-digital-consent-a-discussion-gallery-exhibition-at-mozfest-2022/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/reimagining_digital_consent_blog_image_1_hu_8c08f303b0aefcfb.png&#34; width=&#34;740&#34; height=&#34;820&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Image: &lt;a href=&#34;https://unsplash.com/photos/heEPoapeiVk&#34;&gt;Jason Briscoe&lt;/a&gt; adapted by &lt;a href=&#34;http://okthanks.com&#34;&gt;Carrie Winfrey&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Every day tech platforms confront us with information about how our data is used, and pop-ups with language like this website uses cookies, accept and continue are an accepted part of the online experience. Consenting to sharing data is so strongly encouraged by the platforms that “opting in” or “opting out” is not the right framework because coerced consent cannot be meaningful. However, new privacy regulations such as the forthcoming &lt;a href=&#34;https://www.europarl.europa.eu/news/en/press-room/20211210IPR19209/digital-services-act-safer-online-space-for-users-stricter-rules-for-platforms&#34;&gt;Digital Service Act&lt;/a&gt; from the European Union and &lt;a href=&#34;https://oag.ca.gov/privacy/ccpa&#34;&gt;California’s Consumer Privacy Act&lt;/a&gt; are initial attempts to empower individuals to give meaningful consent to data collection. &lt;/p&gt;
&lt;p&gt;These policies are important steps to protecting people from the harms of data collection. As we describe in our ongoing work on the &lt;a href=&#34;https://superbloom.design/learning/blog/the-limits-to-digital-consent-understanding-the-risks-of-ethical-consent-and-data-collection-for-underrepresented-communities/&#34;&gt;risks of data collection&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;h4 id=&#34;data-accumulation-has-great-power-over-a-persons-agency-their-relationships-and-the-communities-within-which-they-operate--and-the-associated-harms-reach-almost-every-human-being-practitioners-must-therefore-examine-the-systemic-shortcomings-of-digital-consent-and-commit-to-an-ongoing-iteration-of-consent-and-data-governance-within-platforms&#34;&gt;“Data accumulation has great power over a person’s agency, their relationships, and the communities within which they operate – and the associated harms reach almost every human being. Practitioners must therefore examine the systemic shortcomings of digital consent and commit to an ongoing iteration of consent and data governance within platforms.”&lt;/h4&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/resources/The_Limits_to_Digital_Consent_FINAL_Oct2021.pdf&#34;&gt;The Limits of Digital Consent Report&lt;/a&gt; by Simply Secure and the New Design Congress.&lt;/p&gt;
&lt;p&gt;This &lt;a href=&#34;https://schedule.mozillafestival.org/session/9RQHNE-1&#34;&gt;MozFest workshop&lt;/a&gt; provides essential contextual information to improve how policies for providing meaningful consent are implemented. We invite contribution from the community documenting the status quo of how online consent works now and imagining a better future.&lt;/p&gt;
&lt;h3 id=&#34;open-call-for-participation&#34;&gt;Open Call for Participation&lt;/h3&gt;
&lt;p&gt;There are three ways to participate in the Mozfest Reimagining Consent workshop and gallery:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;We invite submissions via &lt;a href=&#34;https://airtable.com/shr3xzoqGYuVgg42n&#34;&gt;this Airtable link&lt;/a&gt; to an online gallery exploring the subject of online consent. We want to hear from you! From the perspectives of design practitioners, researchers, and end-users, help us:&lt;/p&gt;
&lt;p&gt;a. &lt;strong&gt;Document the status quo&lt;/strong&gt;&lt;br&gt;
Collect screenshots of deceptive design examples, such as:&lt;br&gt;
What interface mechanisms are used to collect consent data? What&amp;rsquo;s confusing or manipulative? Helpful and empowering? &lt;/p&gt;
&lt;p&gt;b. &lt;strong&gt;Imagine a bolder future&lt;/strong&gt;&lt;br&gt;
Collect screenshots of empowering consent experiences or share your own work. Let’s explore what meaningful consent looks like. How will we know if new design patterns lead to different results? How can we shift power back to end-users?&lt;a href=&#34;https://airtable.com/shrZSumhBM6DSyILb/tblkHBbRqiAaV22gs&#34;&gt;&lt;/a&gt;&lt;a href=&#34;https://airtable.com/shrZSumhBM6DSyILb/tblkHBbRqiAaV22gs&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://airtable.com/shrZSumhBM6DSyILb/tblkHBbRqiAaV22gs&#34;&gt;View the gallery&lt;/a&gt; any time during MozFest.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/9RQHNE-1&#34;&gt;Join us for a discussion&lt;/a&gt; on reimagining consent on March 8 @ 1:00 - 2:00 PM EST / 6:00 - 7:00 PM GMT.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;guide-to-submissions&#34;&gt;Guide to Submissions&lt;/h3&gt;
&lt;p&gt;Although we welcome original design proposals, we encourage everyone to submit screenshots of consent to data collection examples they encounter online. From American comedian Jimmy Fallon’s &lt;a href=&#34;https://www.youtube.com/watch?v=tLzfN7NdWpA&#34;&gt;Screen Grab&lt;/a&gt; video segments using humor to explore online life to Louise Benson’s example-filled essay on &lt;a href=&#34;https://elephant.art/a-picture-of-a-thousand-words-how-screenshots-changed-visual-culture-02082021/&#34;&gt;how screenshots changed visual culture&lt;/a&gt;, taking screenshots helps us see everyday digital interactions from a new perspective.&lt;/p&gt;
&lt;p&gt;Because we are interested in current online experience, as lived all around the world, we encourage as many people as possible to take advantage of the tools we have to document examples of consent. Any platform, any language, any application - &lt;a href=&#34;https://airtable.com/shr3xzoqGYuVgg42n&#34;&gt;submit your examples&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;Tips for Submissions to the Reimagining Consent Gallery:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Background - review &lt;a href=&#34;https://computing.which.co.uk/hc/en-gb/articles/208520065-Take-a-screenshot-or-screengrab-in-Windows-Mac-tablets-and-phones&#34;&gt;how to take a screenshot&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Consider the role of different UI elements and patterns in consent. Here are some examples of things to consider capturing in a screenshot:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Popup dialog box&lt;/li&gt;
&lt;li&gt;Notification&lt;/li&gt;
&lt;li&gt;Interstitial&lt;/li&gt;
&lt;li&gt;OS features&lt;/li&gt;
&lt;li&gt;Settings&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;We don&amp;rsquo;t need a lengthy explanation. Don’t be shy if you feel like you have nothing to say. Taking the time to submit a screenshot – even without using your name – helps designers, researchers, and policy makers learn about consent.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Examples of &lt;a href=&#34;https://blog.mozilla.org/en/internet-culture/mozilla-explains/deceptive-design-patterns/&#34;&gt;deceptive design patterns&lt;/a&gt; intentionally tricking people into sharing their data are welcome. But also consider sharing examples of things you would like to see more of, that you think work well.  &lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Digital consent covers a broad range of themes – not only privacy, but also e-commerce, and competitiveness (antitrust), so consider all kinds of everyday examples: mobile games, shopping carts, region-blocked content, advertising, etc. No need to limit examples to terms and conditions for data handling.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Here are two examples to encourage more contributions:&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/reimagining_digital_consent_blog_image_2_hu_39417b2b2def1260.png&#34; width=&#34;740&#34; height=&#34;1606&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/reimagining_digital_consent_blog_image_3_hu_99e47c17be877ee0.png&#34; width=&#34;740&#34; height=&#34;1514&#34;&gt;
&lt;/p&gt;
&lt;p&gt;In the above example iPhone screenshots:&lt;/p&gt;
&lt;p&gt;First - a good example of consenting to having location tracked.&lt;/p&gt;
&lt;p&gt;Second - a bad example of an app sharing extremely personal information and making it difficult to learn that it’s happening.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;See what else has been submitted to the &lt;a href=&#34;https://airtable.com/shrZSumhBM6DSyILb/tblkHBbRqiAaV22gs&#34;&gt;Consent Gallery&lt;/a&gt; and &lt;a href=&#34;https://airtable.com/shr3xzoqGYuVgg42n&#34;&gt;submit something today&lt;/a&gt; so that we can include it in our discussion on March 8 @ 1:00 - 2:00 PM EST / 6:00 - 7:00 PM GMT.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Book to attend the MozFest session &lt;a href=&#34;https://schedule.mozillafestival.org/session/9RQHNE-1&#34;&gt;here&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Credits: &lt;a href=&#34;https://twitter.com/georgiamoon&#34;&gt;Georgia Bullen&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/ameellio&#34;&gt;Ame Elliott&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/crwinfrey&#34;&gt;Carrie Winfrey&lt;/a&gt; // &lt;a href=&#34;https://twitter.com/WeAreOkthanks&#34;&gt;Okthanks&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Keeping Everyone Safe: Quick, User-oriented Problem-solving with Mapeo </title>
      <link>https://superbloom.design/learning/blog/keeping-everyone-safe-quick-user-oriented-problem-solving-with-mapeo/</link>
      <pubDate>Tue, 22 Feb 2022 18:21:54 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/keeping-everyone-safe-quick-user-oriented-problem-solving-with-mapeo/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/mapeo_blog_2_header_image_hu_2da3226e69045f28.png&#34; width=&#34;740&#34; height=&#34;490&#34;&gt;
&lt;/p&gt;
&lt;p&gt;This fall, we had the pleasure of working with &lt;a href=&#34;https://www.digital-democracy.org/&#34;&gt;Digital Democracy&lt;/a&gt; on their application, &lt;a href=&#34;https://www.digital-democracy.org/mapeo/&#34;&gt;Mapeo&lt;/a&gt;. Mapeo is a mobile and desktop app that enables indigenous communities to map their lands, sites, and resources, as well as record and monitor environmental and legal abuses by corporations and the state. The app is used by communities around the world, and due to the sensitive nature of the data being recorded, contributing to Mapeo can be high-risk for users. Our design challenge focused on user safety: how to protect end users in the likely event that a community mapper’s phone is lost, seized, damaged, or stolen.&lt;/p&gt;
&lt;p&gt;Simply Secure uses many different Human-Centered Design methods to gather feedback from end-users, but our approach centers participants’ safety. User research with high-risk groups requires special consideration, and sometimes it isn’t always possible or appropriate to work directly with users. Here are some of the considerations we’ve encountered:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;As the pandemic continues, we face travel restrictions and closed borders that hinder global work, in addition to the risks to users and designers of meeting in-person to collaborate.&lt;/li&gt;
&lt;li&gt;We now lack the events, such as RightsCon or the Internet Freedom Festival, that provided opportunities for user research with people from around the world. &lt;/li&gt;
&lt;li&gt;American and European technologists/researchers cannot enter and do work with global communities – indigenous or otherwise – without proper attention to the colonialist dynamics that have the potential to affect the intended collaboration.&lt;/li&gt;
&lt;li&gt;Participating in research can be risky for the end-users because it exposes them to extra attention. &lt;/li&gt;
&lt;li&gt;Remote user research can be difficult in areas with network connectivity challenges and without access to certain technology.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The Mapeo project was uniquely well-positioned to overcome these challenges because Dd has a long history of local partners leading the design and development, an approach recently recognized by an &lt;a href=&#34;https://solve.mit.edu/articles/mit-solve-announces-new-class-of-42-social-entrepreneurs-solving-global-challenges-with-over-2-3-million-in-funding&#34;&gt;M.I.T. Solver Award for Social Entrepreneurship&lt;/a&gt;. As Oswando Nenquimo, the Co-Founder and Director of Monitoring and Territory Defense at Alianza Ceibo explains, the Indigenous experience is central to the history of Mapeo. He says, “Together we built the open source application Mapeo for everyone to use. We were using it then, and we are still using it to defend our lands.”&lt;/p&gt;
&lt;p&gt;In the context of our OTF Usability Lab-supported collaboration on Mapeo, time-sensitivity was front-and-center; implementing features that improve the safety of users was of utmost importance. This encouraged our process to prioritize getting a solution implemented that could be adjusted later on. We wanted to get potentially life-saving solutions integrated into the app as quickly as possible.&lt;/p&gt;
&lt;p&gt;This led us to wonder: How do we design for quick, user-oriented solutions without conducting new user research? How do we help a team like Dd, that already practices human-centered design, lean on their own knowledge to produce user-centered solutions? Building on the collaboration with the Mapeo team, this post shares lessons to help others in similarly challenging situations arrive at human-centered solutions (especially as the pandemic continues on), but that might not have years of local information at hand. Working with Dd solidified for us that doing human-centered design is an ongoing commitment and practice, and that deep engagement and communication with your community of users, as Dd models, is the most valuable asset to doing good design work – especially in the face of challenging circumstances. &lt;/p&gt;
&lt;p&gt;We learned four valuable lessons doing this work:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;✅  Doing human-centred work is a gift that keeps on giving; start where you are, use what you have&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;✅  Don’t go it alone: ask your peers and community before reinventing the wheel&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;✅  Scenario plan: put informed empathy into action&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;✅  Prepare for feedback as soon as you can get it&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;_______________________________________________________________________________________&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;⚠️ &lt;strong&gt;Beware of a sense of techno-solutionism that can come easily when thinking through technical challenges. Threats posed to “high-risk” users or to users engaged in “high risk” activity are often socially and politically rooted, rather than strictly technical.&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;⚠️ &lt;strong&gt;Talking to users is always preferable to making assumptions. If it is safe and physically possible, do it.&lt;/strong&gt; &lt;/p&gt;
&lt;h4 id=&#34;1-doing-human-centered-work-is-a-gift-that-keeps-on-giving-you-already-have-more-knowledge-than-you-realize&#34;&gt;1. Doing human-centered work is a gift that keeps on giving; you already have more knowledge than you realize&lt;/h4&gt;
&lt;p&gt;Even though our design team did not work directly with end-users, we had access to the Dd team, who have a wealth of user-centered information that could be relied upon to begin to answer pressing design challenges. The Dd programs team spends months on the ground with their users, and we designed activities that would help to surface their knowledge and expertise about what their users might need and what threats they face.&lt;/p&gt;
&lt;p&gt;One of the tools we used to make the Dd team’s tacit knowledge explicit was a Threat Modeling / “&lt;a href=&#34;&#34;&gt;Anxiety Games&lt;/a&gt;” Workshop. (Shout-out to our team member Cade and &lt;a href=&#34;https://newdesigncongress.org/en/&#34;&gt;New Design Congress&lt;/a&gt; for introducing us to Anxiety Games). The Threat Modeling workshop helped to get the Dd Programs and Tech teams to talk through common threats to users, based on their knowledge of and interaction with local partners. This format was particularly relevant because, as a global organization, Dd teams operate in different contexts. People with expertise in one country were prompted to articulate some of their implicit knowledge, which created opportunities to discuss similarities and differences with other geographies.&lt;br&gt;
&lt;br&gt;
While exploring the unique needs and challenges faced by the tech team’s defined user groups, we spent time writing down possible threat scenarios as a group. Those threats fell into four categories: Social/Political, Physical, Digital, and Environmental. We then used a game of chance to pull a selection of scenarios and talk through potential interventions.&lt;/p&gt;
&lt;p&gt;While we led the Threat Modeling workshop before focusing our work on device seizure specifically, it a) identified device seizure as a high-priority threat to users, and b) taught us that we could rely on the knowledge of the Dd team to do user-centered work in the absence of new user research. It was a great lesson in the fact that when a team is committed to co-designing with communities and having an on-going, human-centered practice, the benefits snowball over time. Knowing your users deeply enables your team to anticipate needs and more responsibly and effectively design for them.&lt;/p&gt;
&lt;h4 id=&#34;2-dont-go-it-alone-ask-your-peers-and-community-before-reinventing-the-wheel&#34;&gt;2. Don’t go it alone; ask your peers and community before reinventing the wheel&lt;/h4&gt;
&lt;p&gt;Mapeo and its needs presented unique challenges to a typical research and design process. For instance, front-line human rights defenders have other things to do than explain their lives to us. It was more beneficial for us to respect their time and instead work with proximate people with regional knowledge and expertise. We turned to our &lt;a href=&#34;mailto:slack@superbloom.design&#34;&gt;Slack community&lt;/a&gt; and other peers in the design for usable security and human rights space to learn about what design interventions have been tested and successful in similar contexts.&lt;/p&gt;
&lt;p&gt;Through our own desk research and informed by Slack threads and rich conversations with some of our friends (shout-out to Carrie Winfrey from &lt;a href=&#34;https://okthanks.com/&#34;&gt;Okthanks&lt;/a&gt;!), We gathered a short-list of viable design options for protecting against device loss and seizure. By relying on the trusted, user-centered work of our peers, we were able to learn about how other human rights defenders have dealt with similar threats.&lt;/p&gt;
&lt;h4 id=&#34;3-scenario-plan-put-informed-empathy-into-action&#34;&gt;3. Scenario plan: put informed empathy into action&lt;/h4&gt;
&lt;p&gt;Armed with a shortlist of tested design interventions and the confidence that the Dd Programs and Tech teams had a special depth of knowledge about their users, we designed a workspace that was intended to give the team the tools to make an informed decision quickly in the absence of new data from users on the ground. As Dd is well aware, user research is  critical in making key design decisions, but this strategy was our most viable alternative to arriving at an initial user-centered design decision on a tight timeline. &lt;/p&gt;
&lt;p&gt;We created a large workspace in Miro that enabled the Dd team to think through the potential device seizure and loss scenarios their users face or may face and determine which of the identified design interventions made the most sense for Mapeo. The board included a synthesis of the Threat Modeling workshop findings, a section explaining each of the identified design interventions around device loss and seizure (with examples), and a section for in-depth scenario planning and pattern identification. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/mapeo_blog_2_tech_design_strategies_hu_e41ba8e0c67706b6.jpg&#34; width=&#34;740&#34; height=&#34;249&#34;&gt;
&lt;/p&gt;
&lt;p&gt;The scenario planning worksheet provided templates to play out possible loss and seizure scenarios. The board enabled the team to pull from examples from the Threat Modeling workshop or to think of their own scenarios based on their experience with users. We encouraged them to play out a scenario in multiple ways to see it from different angles. For example, in one scenario, we suggested to presume the police are interested in protecting the corporation whose harms a mapper is documenting. In another, presume the police are interested in sussing out a different issue, and therefore aren&amp;rsquo;t concerned with a mapper&amp;rsquo;s environmental activities. At the end of each scenario, the team was prompted to pick which of the identified design strategies would help the user and Mapeo in that situation. After playing through as many scenarios as possible, the team was encouraged to see which strategies come up the most, and use that as a way to pick their design direction for implementation.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/mapeo_blog_2_scenario_planning_worksheet_hu_c3b9594d84e625a.jpg&#34; width=&#34;740&#34; height=&#34;282&#34;&gt;
&lt;/p&gt;
&lt;p&gt;If others are to learn from this work, we want to emphasize that it’s important to be wary of promoting any sense of techno-solutionism to these often very social and political threats. While the Dd team is conscientious of the complexity of the threats their users face, we encourage others engaged in this work to think about scenarios in levels: what does an intervention protect against, what does it not? For example, an intervention might withstand a checkpoint, but not the police running forensics on a user’s phone. In that vein, using Mapeo as an example, it is often more crucial to train users on device and data safety, including what to think about before going into a potentially risky situation, than simply updating the software’s design. How can we empower users to consider: What are the potential harms to me, to the project, to this land, if my device is seized? What can I do to mitigate those harms? Where am I headed? What are the potential threats there? As Dd well understands, Mapeo users should simultaneously be educated on how the software can and cannot protect them, as well as how it could potentially cause them harm.&lt;/p&gt;
&lt;h4 id=&#34;4-prepare-for-feedback-as-soon-as-you-can-get-it&#34;&gt;4. Prepare for feedback as soon as you can get it&lt;/h4&gt;
&lt;p&gt;While this strategy works in challenging circumstances, we (and Dd) always prefer to do user research over not doing it. Therefore, we recommend proactively preparing for the availability of user input by providing a user interview guide to use once user feedback becomes possible. Ours was intended to help gather user feedback after the design strategies had been chosen and implemented and to help the team understand how the strategies were and were not serving the users&amp;rsquo; needs.&lt;/p&gt;
&lt;p&gt;Device loss and seizure, after all, are complicated issues with significant variations in local threats. Our hypothesis was that different geographies would have different needs. Rather than one set of recommendations for how to handle loss &amp;amp; seizure, the interview guide was designed for use in multiple geographies/languages/contexts to get the information needed to make more informed decisions of which tech features to implement in the future for loss and seizure, and to get a sense of whether implemented features were meeting user needs.&lt;/p&gt;
&lt;p&gt;Working with the Dd team on Mapeo was a powerful example for us of how rigorous of a commitment true human-centered design is – and what wonderful work comes out of that commitment. We were honored to take a small part in their collaborative work that centers the indigenous communities using and designing Mapeo. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Also check out &lt;a href=&#34;https://superbloom.design/learning/blog/making-the-mindset-shift-an-interview-with-digital-democracy-lead-ux-designer-sabella-flagg/&#34;&gt;our first post on Mapeo&lt;/a&gt;, an interview with Digital Democracy’s Lead UX Designer, Sabella Flagg.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Credits:&lt;/strong&gt; &lt;a href=&#34;https://simplysecure.org/who-we-are/katie/&#34;&gt;Katie Wilson&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/ameellio&#34;&gt;Ame Elliott&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Illustration by:&lt;/strong&gt; &lt;a href=&#34;https://twitter.com/kirakirawes&#34;&gt;Ngọc Triệu&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Join Us at MozFest 2022</title>
      <link>https://superbloom.design/learning/blog/join-us-at-mozfest-2022/</link>
      <pubDate>Tue, 22 Feb 2022 07:15:47 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/join-us-at-mozfest-2022/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/mozfest_2022_overview_image_1_hu_ef0ffa20358e98bf.jpg&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Are you stuck on how to build or communicate a feature?  Not sure how to get user feedback?  Want to learn more about how the consent user experience has changed?  Are you eager to find out how to navigate design choices while prioritizing human rights?  Is digital infrastructure funding a topic you are keen to hear more about?  Want to dive deep into data colonialism? We have some answers. &lt;/p&gt;
&lt;p&gt;Simply Secure will be hosting five sessions at the second virtual &lt;strong&gt;Mozilla Festival (Monday, March 7 - Thursday, March 10 2022)&lt;/strong&gt;. If you’ll be there, we’d love to see you, learn about your work, and collaborate. Come join us!&lt;/p&gt;
&lt;p&gt;You can register for MozFest &lt;a href=&#34;https://www.mozillafestival.org/&#34;&gt;here&lt;/a&gt;, and below are links to each of the sessions.&lt;/p&gt;
&lt;h2 id=&#34;learning-decolonial-practices-from-the-community&#34;&gt;Learning Decolonial Practices from the Community&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/UB79HT-1&#34;&gt;https://schedule.mozillafestival.org/session/UB79HT-1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;When: March 7 @ 7:00 - 8:30 AM EST / 12:00 - 1:30 PM GMT&lt;/p&gt;
&lt;p&gt;Datafication is one major tactic of data colonialism. Is it truly inevitable or is it a myth waiting to be unraveled and reclaimed? This session aims to bring together designers, researchers, technologists, and community members from across the globe to discuss the manifestations and impacts of data colonialism on the way technology is designed, learn from current decolonial practices, and explore different approaches to resistance in everyday life.&lt;/p&gt;
&lt;p&gt;Below is the agenda of the session:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Introduction &amp;amp; Housekeeping&lt;/li&gt;
&lt;li&gt;Group activity: Defining data colonialism&lt;/li&gt;
&lt;li&gt;Group activity: Identifying data colonialism&amp;rsquo;s every day’s manifestations and impacts&lt;/li&gt;
&lt;li&gt;Individual/Group activity: Exploring community&amp;rsquo;s decolonial practices&lt;/li&gt;
&lt;li&gt;Discussion and Closing&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The session will be facilitated using Miro + a video call platform.&lt;/p&gt;
&lt;p&gt;Before the session: &lt;/p&gt;
&lt;p&gt; We prepare a simple activity for you to explore your relationship with data. The worksheet can be downloaded &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/My%20Data%20Worksheet%20(Hand-drawn).png&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt; We suggest that you should use a personal computer or a laptop to ensure better accessibility and connection. &lt;/p&gt;
&lt;h2 id=&#34;ux--design-speed-dating&#34;&gt;UX &amp;amp; Design Speed Dating&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/CYFY7Y-1&#34;&gt;https://schedule.mozillafestival.org/session/CYFY7Y-1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;When: March 8 @ 10:00 - 11:00 AM EST / 3:00 - 4:00 PM GMT&lt;/p&gt;
&lt;p&gt;Stuck on how to build or communicate a feature? Not sure how to get user feedback? Want to brainstorm some design alternatives for your tool or process? Thinking about how to engage users in your design process? Then this workshop is for you!&lt;/p&gt;
&lt;p&gt;In the session, participants will have the opportunity to meet with design and usability practitioners in the community, with a special focus on designing for privacy. We will set up 10-15 minute &amp;ldquo;speed dating&amp;rdquo; time slots and allow participants to rotate through the presenters so that they can get feedback from multiple perspectives on whatever design and UX challenges they bring to share.&lt;/p&gt;
&lt;p&gt;Participants should bring something to share their work with the UX practitioners (an idea, a problem to work on, design sketches, a prototype) and will leave with feedback, designs, tools, strategies, and follow up opportunities to get support in their work.&lt;/p&gt;
&lt;h2 id=&#34;reimagining-consent-a-discussion--gallery-exhibition&#34;&gt;Reimagining Consent: A Discussion &amp;amp; Gallery Exhibition&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/9RQHNE-1&#34;&gt;https://schedule.mozillafestival.org/session/9RQHNE-1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;When: March 8 @ 1:00 - 2:00 PM EST / 6:00 - 7:00 PM GMT&lt;/p&gt;
&lt;p&gt;Every day tech platforms confront us with options about how our data is used, and pop-ups with language like &amp;ldquo;this website uses cookies&amp;rdquo;, &amp;ldquo;accept&amp;rdquo; and &amp;ldquo;continue&amp;rdquo; are an accepted part of the online experience. Consenting to sharing data is so strongly encouraged by the platforms that end-user choice is not the right framework. Privacy regulations such as the forthcoming &lt;a href=&#34;https://www.europarl.europa.eu/news/en/press-room/20211210IPR19209/digital-services-act-safer-online-space-for-users-stricter-rules-for-platforms&#34;&gt;Digital Service Act&lt;/a&gt; from the European Union and &lt;a href=&#34;https://oag.ca.gov/privacy/ccpa&#34;&gt;California’s Consumer Privacy Act&lt;/a&gt; are initial attempts to empower individuals to give meaningful consent to data collection, but there is much more to be done. &lt;/p&gt;
&lt;p&gt;There are three ways to participate in this session. &lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;We invite submissions via &lt;a href=&#34;https://airtable.com/shr3xzoqGYuVgg42n&#34;&gt;this Airtable link&lt;/a&gt; to an online gallery exploring subject of online consent from the perspectives of design practitioners, researchers, and end-users that&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;i. Document the status quo: What interface mechanisms are used to collect consent data? What&amp;rsquo;s confusing or manipulative? Helpful and empowering? &lt;/p&gt;
&lt;p&gt;ii. Imagine a bolder future: What does meaningful consent look like? How will we know if new design patterns lead to different results? How can we shift power back to end-users?&lt;/p&gt;
&lt;p&gt;View the gallery any time during MozFest. Stay tuned for how to access the collection.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Join us for a discussion on reimagining consent on March 8 @ 1:00 - 2:00 PM EST / 6:00 - 7:00 PM GMT&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&#34;busting-the-dark-patterns-a-human-rights-centered-design-approach&#34;&gt;Busting the Dark Patterns: A Human-Rights-Centered Design Approach&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/38ELGY-1&#34;&gt;https://schedule.mozillafestival.org/session/38ELGY-1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;When: March 9 @ 7:00 - 8:00 AM EST / 12:00 - 1:00 PM GMT&lt;/p&gt;
&lt;p&gt;Dark Patterns, also referred to as deceptive design, are interface design tactics in digital products to persuade you into doing things you would otherwise not do. It has been so commonly used in today&amp;rsquo;s online tools, platforms, and services without questioning that such practices have become defaults-by-design. Despite the rising public outcry against the manipulative nature of Dark Patterns and its contribution to undermining people’s agency and human rights online, efforts to restrain Dark Patterns remain monolateral, often through the policy channel. However, shifting the culture of Dark Patterns takes a much more comprehensive approach that involves a key stakeholder: the user research and design community. For decades, the design community has been through many iterations to define “ethical design” and set a standard on what is good design. In this workshop, we offer a redefinition of “ethical design” by providing a human-rights-centered design approach. Built upon a cross-disciplinary working session between designers, policy experts, and researchers to list simple actions to prevent Dark Patterns, in this workshop, we will be introducing a guide for designers to navigate through design choices while prioritizing human rights. We welcome participants who are interested in product design processes to come to the workshop and collectively brew practices and concerns that are key to building a culture against Dark Patterns and protect people’s privacy and other digital rights as technology evolves.&lt;/p&gt;
&lt;h2 id=&#34;defeating-deceptive-design-getting-control-of-our-online-lives&#34;&gt;Defeating Deceptive Design: Getting Control of Our Online Lives&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/J7WKEE-1&#34;&gt;https://schedule.mozillafestival.org/session/J7WKEE-1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/J7WKEE-1&#34;&gt;&lt;/a&gt;When: March 9 @ 10:00 - 11:00 AM EST / 3:00 - 4:00 PM GMT&lt;/p&gt;
&lt;p&gt;Deceptive designs, also known as &amp;ldquo;dark patterns&amp;rdquo;, are design practices built into user interfaces, either intentionally or unintentionally, that obscure or impair consumer autonomy or choice and can alter decision-making or trick users into taking actions they might not otherwise take. Deceptive Designs go to the heart of people&amp;rsquo;s ability to live their lives online with dignity, autonomy, and a sense of trust in the products and services offered to them by businesses and governments alike. We will share findings from our initial research on deceptive design as a baseline. This session invites everyone — policymakers, civic tech practitioners, private sector, civil servants, and the people of the internet — to share your lived experience, discuss opportunities and barriers to change, and brainstorm interventions for addressing deceptive design globally using our human-centered approach. We are using this tested approach to better understand the many challenges around deceptive design and co-create policy solutions that promote trusted design patterns. Join us to help set the priorities of the Web Foundation’s Tech Policy Design Lab on Tackling Deceptive Design.&lt;/p&gt;
&lt;h2 id=&#34;digital-infrastructure-funders-toolkit&#34;&gt;Digital Infrastructure Funder&amp;rsquo;s Toolkit&lt;/h2&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/mozfest_2022_overview_image_2_hu_4307f3cc6bddf991.png&#34; width=&#34;740&#34; height=&#34;460&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/JEU8YX-1&#34;&gt;https://schedule.mozillafestival.org/session/JEU8YX-1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;When: March 10 @ 10:00 - 11:00 AM EST / 3:00 - 4:00 PM GMT&lt;/p&gt;
&lt;p&gt;In this cafe-style session, we will share the Digital Infrastructure Funder&amp;rsquo;s Toolkit - a project supported by the Open Collective Foundation&amp;rsquo;s Digital Infrastructure Grant - with the community at MozFest. The toolkit is an implementation framework for funders of digital infrastructure with guides, programming, and models, along with narratives of funding in open source and digital infrastructure, and regional contexts about funding digital infrastructure in different parts of the world.&lt;/p&gt;
&lt;p&gt;First, we will give an overview of the toolkit. Next, we will break out into groups with our participating global regional partners who will share out and lead discussions on digital infrastructure funding from their regional contexts.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Credits:&lt;/strong&gt; &lt;a href=&#34;https://twitter.com/georgiamoon&#34;&gt;Georgia Bullen&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/ameellio&#34;&gt;Ame Elliott&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/smklibrarian/&#34;&gt;Susan Kennedy&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/kirakirawes/&#34;&gt;Ngọc Triệu&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Images:&lt;/strong&gt; Header Image Credit: MF Local Production Office // Nathan Reinds // &lt;a href=&#34;http://www.nathanreinds.nl/&#34;&gt;www.nathanreinds.nl&lt;/a&gt; // Attribution 2.0 Generic (CC BY 2.0) // &lt;a href=&#34;https://creativecommons.org/licenses/by/2.0/legalcode&#34;&gt;License&lt;/a&gt; // &lt;a href=&#34;https://creativecommons.org/licenses/by/2.0/#&#34;&gt;Disclaimer&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Digital Infrastructure Funder&amp;rsquo;s Toolkit Credit: &lt;a href=&#34;https://twitter.com/kirakirawes/&#34;&gt;Ngọc Triệu&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Finding the Balance</title>
      <link>https://superbloom.design/learning/blog/finding-the-balance-adding-support-for-organization-wide-pgp-keys-to-mailvelope/</link>
      <pubDate>Thu, 10 Feb 2022 12:28:18 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/finding-the-balance-adding-support-for-organization-wide-pgp-keys-to-mailvelope/</guid>
      <description>&lt;h2 id=&#34;adding-support-for-organization-wide-pgp-keys-to-mailvelope&#34;&gt;Adding Support For Organization-wide PGP Keys To Mailvelope&lt;/h2&gt;

&lt;figure class=&#34;image center&#34;&gt;
&lt;img src=&#34;https://superbloom.design/images/image-1-hero.png&#34; width=&#34;750&#34; height=&#34;500&#34;&gt;
&lt;/figure&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://mailvelope.com/en&#34;&gt;Mailvelope&lt;/a&gt; is a browser extension that makes it easy to use &lt;a href=&#34;https://en.wikipedia.org/wiki/Pretty_Good_Privacy&#34;&gt;PGP encryption&lt;/a&gt;, whether you use Gmail, Outlook, or many other email providers.&lt;/li&gt;
&lt;li&gt;With the support of &lt;a href=&#34;https://usable.tools/tags/uxfund/&#34;&gt;UXFund&lt;/a&gt;, &lt;a href=&#34;https://simplysecure.org/&#34;&gt;Simply Secure&lt;/a&gt; worked with Mailvelope to support users who want to use an organization-wide PGP key to send an encrypted email. &lt;/li&gt;
&lt;li&gt;Kelsey Smith and Thomas Oberndörfer had a conversation in 2022, reflecting on the technical problem and the design process. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In 2021, UXFund supported Mailvelope to partner with Simply Secure on a series of design challenges to improve the browser extension’s usability. Mailvelope’s mission is to make PGP encryption easy to use. This challenge revolved around a new feature for sending an email that is encrypted with a key that the recipient shares with other people in their organization. On technically-challenging problems like this one, how do developers and designers collaborate? The designer on the project, Kelsey Smith, spoke with Thomas Oberndörfer, founder and lead developer of Mailvelope, to reflect on their collaborative experience. &lt;/p&gt;
&lt;p&gt;&lt;em&gt;This conversation was recorded on January 27, 2022. It has been edited for clarity.&lt;/em&gt; &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Kelsey Smith (Simply Secure):&lt;/strong&gt; Hey there, I&amp;rsquo;m Kelsey Smith, I&amp;rsquo;m a UX designer at Simply Secure.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Thomas Oberndörfer (Mailvelope):&lt;/strong&gt; I&amp;rsquo;m Thomas. I&amp;rsquo;m the founder and lead developer of Mailvelope.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Kelsey:&lt;/strong&gt; How would you describe our project, Thomas? &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Thomas:&lt;/strong&gt; In this project we developed a new feature that allows Mailvelope users to send emails encrypted with organization-wide keys. &lt;/p&gt;
&lt;p&gt;Normally, each individual would have their own PGP key. But sometimes organizations don&amp;rsquo;t follow this traditional way of using PGP encryption, and instead, many employees share one organization-wide key. &lt;/p&gt;
&lt;p&gt;How could Mailvelope users encrypt an email with a key that doesn’t belong to the recipient? Before, they couldn’t - it wasn’t possible. So, this project was about rethinking part of how Mailvelope works so it could support more people and use cases.&lt;/p&gt;

&lt;figure class=&#34;image center&#34;&gt;
&lt;img src=&#34;https://superbloom.design/images/image-2-shared-key.png&#34;&gt;
&lt;figcaption&gt;
The challenge was letting Mailvelope users encrypt an email with a shared key - one that the recipient shares with other people.&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;&lt;strong&gt;Kelsey:&lt;/strong&gt; At the core of this project was giving users more freedom and flexibility to use Mailvelope in more situations. A feature like this is one way to make it easier for people to choose encrypted over unencrypted, so their emails can remain private. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Thomas:&lt;/strong&gt; Mailvelope’s main goal is to make PGP encryption usable by avoiding complexity and providing safe defaults. Instead of dozens of options, the user should be able to send an encrypted email with one click. Yet, this feature is a deviation from that concept because it requires user input.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Mailvelope’s main goal is to make PGP encryption usable by avoiding complexity and providing safe defaults.&amp;rdquo; - Thomas&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;Kelsey:&lt;/strong&gt; We kept coming back to the theme of user freedom versus user guidance and how we can find that balance. For anyone, having too many options can be overwhelming, leading to confusion and decision-paralysis. So we had to help users by guiding them, and that means making some decisions for them.&lt;/p&gt;

&lt;figure class=&#34;image center&#34;&gt;
&lt;img src=&#34;https://superbloom.design/images/image-3-freedom-vs-guidance-1.png&#34;&gt;
&lt;figcaption&gt;
The challenge was letting Mailvelope users encrypt an email with a shared key - one that the recipient shares with other people.&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;&lt;strong&gt;Thomas:&lt;/strong&gt; ‘Balance’ was a word we used a lot. Finding balance relates not only to the usability of the tool, but also to the software architecture. With every addition, we increase our complexity, the possibility for errors, and the effort of maintenance. So we sought a minimalistic approach whenever possible. &lt;/p&gt;
&lt;p&gt;We had to balance making this feature visible while not confusing the 99% use case, let’s say. Because most of our users will not send emails encrypted with organization-wide keys, our interface should not be overloaded with this kind of special functionality.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt; &amp;ldquo;‘Balance’ was a word we used a lot. Finding balance relates not only to the usability of the tool, but also to the software architecture. With every addition, we increase our complexity, the possibility for errors, and the effort of maintenance.&amp;rdquo; - Thomas&lt;/p&gt;
&lt;/blockquote&gt;

&lt;figure class=&#34;image center&#34;&gt;
&lt;img src=&#34;https://superbloom.design/images/image-4-balance.png&#34;&gt;
&lt;figcaption&gt;
Finding a balance was a big part of our design work&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;&lt;strong&gt;Kelsey:&lt;/strong&gt; The feature isn&amp;rsquo;t for the broader Mailvelope user base, but it&amp;rsquo;s still important that Mailvelope delivers even in those situations that aren&amp;rsquo;t usual or every day. Treating edge cases like outliers is not a way to make inclusive design.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Treating edge cases like outliers is not a way to make inclusive design.&amp;rdquo; - Kelsey &lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&#34;our-process&#34;&gt;Our Process&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Kelsey:&lt;/strong&gt; Okay, let’s talk about our process. When we started, we thought it would be straightforward. I even created a project timeline of how I thought it would go: a linear design process. I should have known better! We started by mapping the users’ journeys together and had this big picture of the scenario, including user actions, what the user sees, the pain points, and the opportunities. And we realized some of our assumptions weren’t the safest.&lt;/p&gt;

&lt;figure class=&#34;image center&#34;&gt;
&lt;img src=&#34;https://superbloom.design/images/image-5-expectations-vs-reality.png&#34;&gt;
&lt;figcaption&gt;
We thought the design process would be straightforward; instead we took a winding path.&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;&lt;strong&gt;Thomas:&lt;/strong&gt; I would call it ‘creative destruction’ of ideas – the ideas that you thought were good, but do not work. It can be tough to let go of a concept that you already invested so much time into. There’s pressure to deliver, but we gave ourselves the space to explore. &lt;/p&gt;
&lt;p&gt;Our first approach was to add an additional setting to the key to allow the key to be used for multiple recipients. With this setting, we thought we could reduce user frustration because they could set it once and forget it. And then?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Kelsey:&lt;/strong&gt; And then we mapped out some scenarios with pain points and realized, “Do we want our users to forget this key mismatch?” No, we didn’t! &lt;/p&gt;
&lt;p&gt;So we scrapped that and revisited an old idea that the user can add an alternate key when they compose an email. It wouldn’t be a saved setting; it was something they needed to do each time they write an email. This added some ‘friction’ to the user’s process. In creating an extra step, we were trying to make sure the decision was intentional, not a setting a user just forgot about. Sometimes ‘friction’ is necessary. &lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;In creating an extra step, we were trying to make sure the decision was intentional, not a setting a user just forgot about. Sometimes ‘friction’ is necessary.&amp;rdquo; - Kelsey&lt;/p&gt;
&lt;/blockquote&gt;

&lt;figure class=&#34;image center&#34;&gt;
&lt;img src=&#34;https://superbloom.design/images/image-6-mapping.png&#34; width=&#34;750&#34; height=&#34;331&#34;&gt;
&lt;figcaption&gt;
One of our iterations of mapping Mailvelope organization-wide keys feature. Thinking through the whole process helped us consider the context, harms, and design requirements.&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;&lt;strong&gt;Thomas:&lt;/strong&gt; Yes, ‘friction’ was something we went back and forth on. Letting the user make a decision each and every time they want to carry out the task. It was a challenge to figure out if this friction was justified; if we made the right kind of trade-off. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Kelsey:&lt;/strong&gt; And our conversations allowed us to do that. Asking each other questions was a really good way to get to the heart of the problem and find a solution that works. Although it might have looked like we were going backwards sometimes, I felt like we were making progress because we always reached alignment and had realizations together. That was really rewarding.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Thomas:&lt;/strong&gt; Yeah. In my previous projects the concepts were more defined at the start - I already had an abstract idea of a possible solution. In those cases, I looked for a designer to evaluate the usability and translate the vision into the interface. For our project, we worked together at a much earlier stage and created the approach and solution together. Of course, it was successful in the end, because we achieved something. But not only just that - it was a good experience for me. As a technical person (developer) partnering with someone from a different background (UX), we looked at the problem from two different perspectives. This combination leads to progress. &lt;/p&gt;

&lt;figure class=&#34;image center&#34;&gt;
&lt;img src=&#34;https://superbloom.design/images/image-7-designer-developer-collaboration.png&#34;&gt;
&lt;/figure&gt;

&lt;p&gt;&lt;strong&gt;Kelsey:&lt;/strong&gt; Exactly! I feel like what we did was not just a ‘designer-to-developer handoff’, it was a ‘designer-developer collaboration’. I think this sort of collaboration allowed us to work quickly and come to realizations faster because we were building off of each others’ momentum. Sometimes when I work alone, I think about a problem for hours and hours. When I get the chance to bounce ideas off of someone else, we find a solution in just a 30-minute conversation. &lt;/p&gt;
&lt;p&gt;I think we had a lot of those conversations back and forth where we didn&amp;rsquo;t let concepts build up to be huge in our heads, we could quickly get that feedback. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Kelsey:&lt;/strong&gt; Okay, last question: what lesson do you take away from this project?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Thomas:&lt;/strong&gt; Never work without a UX designer!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Kelsey:&lt;/strong&gt; [laughs] That&amp;rsquo;s too good! They’ll think I told you to say that.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Thomas:&lt;/strong&gt; Honestly, this is really how I would like to work in the future. It’s beneficial to have someone with a UX background participating early in the process, not just a handover when things are already defined.&lt;/p&gt;
&lt;h3 id=&#34;the-result&#34;&gt;The Result&lt;/h3&gt;

&lt;figure class=&#34;image center&#34;&gt;
&lt;img src=&#34;https://superbloom.design/images/image-8-email-modal-highlighted.png&#34; width=&#34;750&#34; height=&#34;596&#34;&gt;
&lt;figcaption&gt;
We integrated the option for using a shared, organization wide key into the compose email modal.&lt;/figcaption&gt;
&lt;/figure&gt;


&lt;figure class=&#34;image center&#34;&gt;
&lt;img src=&#34;https://superbloom.design/images/image-9-email-modal-design-decisions.png&#34; width=&#34;750&#34; height=&#34;480&#34;&gt;
&lt;figcaption&gt;
Our collaborative work allowed us to make design decisions around guidance, friction, simplicity, and more.&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;Project Contributors: Kelsey Smith, Thomas Oberndörfer&lt;/p&gt;
&lt;p&gt;With support from &lt;a href=&#34;https://usable.tools/tags/uxfund/&#34;&gt;UXFund&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;You can learn more about Mailvelope and download the browser extension &lt;a href=&#34;https://mailvelope.com/en&#34;&gt;on their website. &lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Decentralization, Off the Shelf</title>
      <link>https://superbloom.design/work/projects/dots/</link>
      <pubDate>Tue, 11 Jan 2022 20:49:41 +0100</pubDate>
      <guid>https://superbloom.design/work/projects/dots/</guid>
      <description>&lt;h3 id=&#34;key-outputs&#34;&gt;key outputs&lt;/h3&gt;
&lt;p&gt;title: DOTS Website
description: Check out the library for yourself here.
link: &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;https://decentpatterns.xyz/&lt;/a&gt;
img:&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Meet Superbloom!</title>
      <link>https://superbloom.design/community/events/meet-superbloom/</link>
      <pubDate>Tue, 11 Jan 2022 20:49:41 +0100</pubDate>
      <guid>https://superbloom.design/community/events/meet-superbloom/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Mozilla Fellowships &amp; Awards Evaluation</title>
      <link>https://superbloom.design/work/projects/mozilla_fellowship_awards/</link>
      <pubDate>Tue, 11 Jan 2022 20:49:41 +0100</pubDate>
      <guid>https://superbloom.design/work/projects/mozilla_fellowship_awards/</guid>
      <description>&lt;p&gt;Key outputs is added here in free form. We can add some shortcodes to insert more structured content.&lt;/p&gt;
&lt;p&gt;Below is the &amp;ldquo;All related content&amp;rdquo;. I need to know how you plan to &amp;ldquo;relate&amp;rdquo; that? Manually via frontmatter? Automatically via e.g. the tags?&lt;/p&gt;
&lt;p&gt;Same questions for the &amp;ldquo;Relevant projects&amp;rdquo; in the sidebar.&lt;/p&gt;
&lt;p&gt;I always recommend doing stuff automatically since it makes the life of the editors easier.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Mozilla Festival</title>
      <link>https://superbloom.design/community/events/mozilla_festival_2022/</link>
      <pubDate>Tue, 11 Jan 2022 20:49:41 +0100</pubDate>
      <guid>https://superbloom.design/community/events/mozilla_festival_2022/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Refresh: Community-Led Identity Change</title>
      <link>https://superbloom.design/work/projects/refresh/</link>
      <pubDate>Tue, 11 Jan 2022 20:49:41 +0100</pubDate>
      <guid>https://superbloom.design/work/projects/refresh/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Snikket</title>
      <link>https://superbloom.design/work/projects/snikket/</link>
      <pubDate>Tue, 11 Jan 2022 20:49:41 +0100</pubDate>
      <guid>https://superbloom.design/work/projects/snikket/</guid>
      <description></description>
    </item>
    
    <item>
      <title>2021 Reflections</title>
      <link>https://superbloom.design/learning/blog/2021-reflections/</link>
      <pubDate>Mon, 03 Jan 2022 16:54:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/2021-reflections/</guid>
      <description>&lt;p&gt;As we enter our third year of a global pandemic, many of us are still in survival mode - reflection doesn’t always seem like a priority. However, as our team looks back upon 2021, we feel gratitude for our health and the impact we are able to have despite all the challenges we’ve faced collectively. We are where we are because of the community of support surrounding us; our partners, our funders, our board, the Human Centered Design Community, our growing community Slack, and more. 2022 is already bringing exciting opportunities and new partnerships, which is possible through the shared resilience of our community. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/2021-in-numbers_hu_4419fd0862a9aaa1.png&#34; alt=&#34;Colored text reads: &amp;lsquo;2021 in numbers: 40 workshops, 30 projects wrapped, 200 research &amp;amp; user chats, 135 new slack community members, 65 total projects, 31 community calls&amp;quot;&#34; width=&#34;740&#34; height=&#34;878&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;2021-in-summary&#34;&gt;&lt;strong&gt;2021 in Summary&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;2021 was quite a year. In the news, we saw new attacks on cybersecurity; the FacebookPapers revelations, and new developments in privacy. In our orbit, The Open Technology Fund reopened, and we were selected again for their newly named Secure Usability and Accessibility Lab - a partnership we value deeply, which connects us with open source project teams working on internet freedom around the world. Internally, our organization engaged in a deep, reflective refresh of our identity - soon, we will roll out a new name, logo, website and brand identity. &lt;/p&gt;
&lt;p&gt;In reflecting on the many projects we completed this year, and the partnerships we fostered - some key themes emerged: &lt;/p&gt;
&lt;h3 id=&#34;challenging-the-status-quo&#34;&gt;Challenging the Status Quo&lt;/h3&gt;
&lt;p&gt;Over the last year, we had the opportunity to work on projects that allowed us to challenge the status quo at the intersection of policy and design - specifically around issues of consent, harassment, and deceptive design. The work we engage in builds interventions that support the most in need, like the &lt;a href=&#34;https://superbloom.design/learning/blog/standing-together-to-stop-online-bullying-harassment-of-women-journalists-is-a-community-problem/&#34;&gt;Online Violence Response Hub&lt;/a&gt; - and also allows us to reflect on why problems exist at all, and the role of design in combating them. We also critically analyzed industry norms, such as deceptive design patterns, and how they affect user experience in tools like &lt;a href=&#34;https://superbloom.design/learning/blog/dark-patterns-in-user-controls-exploring-youtubes-recommendation-settings/&#34;&gt;YouTube&lt;/a&gt;. With the launch of &lt;a href=&#34;https://superbloom.design/learning/blog/the-limits-to-digital-consent-understanding-the-risks-of-ethical-consent-and-data-collection-for-underrepresented-communities/&#34;&gt;Limits to Digital Consent&lt;/a&gt; - co-produced by &lt;a href=&#34;https://newdesigncongress.org/&#34;&gt;New Design Congress&lt;/a&gt; - we exposed how ongoing attempts to incorporate informed consent into data-driven systems fall short of their stated goals.&lt;/p&gt;
&lt;p&gt;Our ongoing work with &lt;a href=&#34;https://www.reset.tech/&#34;&gt;Reset&lt;/a&gt; has included efforts to counter Big Tech’s influence –– from supporting coalition building and activism with &lt;a href=&#34;https://peoplevsbig.tech/&#34;&gt;People vs. Big Tech&lt;/a&gt; and their &lt;a href=&#34;https://www.peoplesdeclaration.net/&#34;&gt;People’s Declaration&lt;/a&gt;, to education and capacity building for law makers through the &lt;a href=&#34;https://recoding.tech/&#34;&gt;Recoding.Tech&lt;/a&gt; resource repository.&lt;/p&gt;
&lt;h3 id=&#34;diversity-equity--inclusion&#34;&gt;Diversity, Equity, &amp;amp; Inclusion&lt;/h3&gt;
&lt;p&gt;In much of our work, there’s always a question of who is being served, who’s involved in shaping the direction of a project, and the inherent power structures that are upheld or dismantled as part of a project. This year we had the opportunity to bring a DEI lens to our design work with &lt;a href=&#34;https://superbloom.design/learning/blog/using-design-to-overcome-structural-inequities-in-peer-review/&#34;&gt;PREreview&lt;/a&gt; by specifically thinking about how the design of the interface could enable the DEI mission of the project — How do we represent individuals &amp;amp; expertise, how do we codify moderation and user/participant protections in ways that align with the code of conduct and the platform goals? Through a partnership with &lt;a href=&#34;https://chaoss.community/&#34;&gt;CHAOSS&lt;/a&gt;, we’ve been exploring how the health of open source projects relates to DEI by joining the DEI Audit committee. In addition to the traditional DEI frame and meaning, we’re also thinking about how design and supporting design contributions can be a DEI effort - both by bringing more diverse voices into a project through engaging with end users for feedback and onboarding designers contributors.&lt;/p&gt;
&lt;h3 id=&#34;strategy--infrastructure&#34;&gt;Strategy &amp;amp; Infrastructure&lt;/h3&gt;
&lt;p&gt;2021 brought opportunities for strategic programmatic, evaluative, and design interventions in infrastructure. How we build interventions — data infrastructure, apps, and programs — easily gets as complex as the problems we are trying to solve. Core to what we do is ensuring practitioners, designers, researchers, activists, and funders are informed, resourced, and empowered. As an ecosystem and community, we all benefit by reflecting and sharing what we’ve learned in working to align a project’s strategy, mission and vision with infrastructural interventions.&lt;/p&gt;
&lt;p&gt;Building on our portfolio of ecosystem analysis leveraging human-centered research, we supported two evaluations with Mozilla to assess, understand, and reflect on how the &lt;a href=&#34;https://superbloom.design/learning/blog/reflections-on-the-mozilla-fellowships-and-awards-impact-evaluation-lessons-for-the-ecosystem/&#34;&gt;Mozilla Fellowships &amp;amp; Awards Program&lt;/a&gt; and &lt;a href=&#34;https://hrcd.pubpub.org/pub/uyydag1t/&#34;&gt;Mozilla Open Source Support Program&lt;/a&gt; serve their grantees, fellows, and the larger ecosystem. Building on our past work with &lt;a href=&#34;https://superrr.net/&#34;&gt;Superrr&lt;/a&gt; on the &lt;a href=&#34;https://recommendations.implicit-development.org/&#34;&gt;Roadwork Ahead&lt;/a&gt; project and our evaluation work with funders, we launched a project to build a &lt;a href=&#34;https://superbloom.design/learning/blog/building-a-toolkit-for-funders-to-grow-their-digital-infrastructure-portfolio/&#34;&gt;Digital Infrastructure Funder’s Toolkit&lt;/a&gt;, supported by a grant from the &lt;a href=&#34;https://opencollective.com/di-grants&#34;&gt;Digital Infrastructure Fund&lt;/a&gt;, which will be a critical resource to help the funding community with tools to effectively develop sustainable funding models for digital infrastructure projects. We worked to put &lt;a href=&#34;https://connecthumanity.fund/&#34;&gt;Connect Humanity&lt;/a&gt;’s vision of digital equity for all into action by designing a usable, strategy-aligned website that will serve as a platform for grantees and funders working on digital equity infrastructure around the world.&lt;/p&gt;
&lt;p&gt;Interventional infrastructure introduces technical, communication and design challenges. While working with the &lt;a href=&#34;https://equalit.ie/&#34;&gt;eQualit.ie&lt;/a&gt; team on &lt;a href=&#34;https://superbloom.design/learning/blog/sustaining-values-driven-software-by-attracting-new-users/&#34;&gt;Deflect&lt;/a&gt;, we explored sustainable infrastructure from a lens of pricing models, transparency and onboarding, modeling ways internet freedom work can be resilient in our economy. Supported by &lt;a href=&#34;https://www.reset.tech/&#34;&gt;Reset.Tech&lt;/a&gt;, we continued our work with &lt;a href=&#34;https://rally.mozilla.org/&#34;&gt;Mozilla’s Rally&lt;/a&gt; project, working to develop privacy preserving data infrastructure to enable internet scale social science. Our &lt;a href=&#34;https://newdesigncongress.org/&#34;&gt;New Design Congress&lt;/a&gt; team members supported the &lt;a href=&#34;https://ati.io/&#34;&gt;Algorithmic Transparency Institute&lt;/a&gt; to develop a cohesive design system for their flagship disinformation research tool, &lt;a href=&#34;https://www.junkipedia.org/&#34;&gt;Junkipedia&lt;/a&gt;, addressing the complexities of data infrastructure interventions in the mis-/disinformation ecosystem.&lt;/p&gt;
&lt;h3 id=&#34;design--usability&#34;&gt;Design &amp;amp; Usability&lt;/h3&gt;
&lt;p&gt;Design &amp;amp; usability remain a cornerstone of our work at Simply Secure. We continued this portfolio of projects through essential partnerships - with the relaunch of the Open Technology Fund and the Secure Usability and Accessibility Lab; our coaching relationship with the &lt;a href=&#34;https://prototypefund.de/&#34;&gt;Prototype Fund&lt;/a&gt;; Internews &lt;a href=&#34;https://usable.tools/blog/2020-10-01-uxfund2020/&#34;&gt;UX Fund&lt;/a&gt;; and &lt;a href=&#34;https://www.amnesty.org/en/&#34;&gt;Amnesty International&lt;/a&gt;. We provided usability and design support for security-focused projects - such as &lt;a href=&#34;https://github.com/phishdetect&#34;&gt;PhishDetect&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/learning/blog/designing-for-a-global-audience-in-the-age-of-remote-usability-testing/&#34;&gt;RiseUp&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/learning/blog/on-getting-things-done-a-conversation-with-matthew-wild-from-snikket/&#34;&gt;Snikket&lt;/a&gt;, &lt;a href=&#34;https://mailvelope.com/en&#34;&gt;Mailvelope&lt;/a&gt;, and &lt;a href=&#34;https://superbloom.design/learning/blog/ssl-tls-and-ftp-oh-my-guiding-users-to-set-up-tls-certificates-in-filezilla/&#34;&gt;Filezilla&lt;/a&gt;; for global projects aimed at protecting and empowering the disconnected and under siege - such as &lt;a href=&#34;https://superbloom.design/learning/blog/bringing-the-offline-online-reviewing-the-developer-experience-of-awala/&#34;&gt;Awala&lt;/a&gt; and &lt;a href=&#34;https://superbloom.design/learning/blog/making-the-mindset-shift-an-interview-with-digital-democracy-lead-ux-designer-sabella-flagg/&#34;&gt;Mapeo&lt;/a&gt;; and coached over 20 projects working on civic tech, data literacy, data security and software infrastructure through our partnership with the Prototype Fund in Germany.&lt;/p&gt;
&lt;h3 id=&#34;building-resources&#34;&gt;Building Resources&lt;/h3&gt;
&lt;p&gt;In line with our educational mission, we devoted much of 2021 to resourcing our community of designers, researchers, activists, and technologists with the design and strategy tools they need to help change who technology serves. &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;Decentralization Off the Shelf (DOTS)&lt;/a&gt; - a collective project hosted at Simply Secure - launched their &lt;a href=&#34;https://decentpatterns.xyz/library/&#34;&gt;Pattern Library&lt;/a&gt; which aims to better equip the community with knowledge to build usable decentralized applications. The DOTS team hosted workshops to co-create and train on usable decentralized design, and published a &lt;a href=&#34;https://decentpatterns.xyz/files/Barriers%20to%20Adoption%20for%20Web%20Monetization%20(April%202021).pdf&#34;&gt;report on the barriers to adoption for web monetization&lt;/a&gt;. We wrapped up our support of the &lt;a href=&#34;https://is.efeefe.me/opendott&#34;&gt;OpenDOTT&lt;/a&gt; program with a series of workshops in partnership with Max von Graffenstein on UX and Privacy Policy. In partnership with &lt;a href=&#34;https://usable.tools/&#34;&gt;USABLE&lt;/a&gt;, our team started a set of resources which are aimed to help ensure at-risk users have a voice in the design and development of open source privacy and security tools.&lt;/p&gt;
&lt;h3 id=&#34;participating-in-the-community&#34;&gt;Participating in the Community&lt;/h3&gt;
&lt;p&gt;2021 was another year without travel, replaced by all virtual conferences and community engagement. Although we missed having face to face time to collaborate among our team and across our community, the pivot to virtual enabled us to be in more places, connect with more of the community, and build new partnerships. At &lt;a href=&#34;https://www.mozillafestival.org/en/&#34;&gt;MozFest 2021&lt;/a&gt;, we held a &lt;a href=&#34;https://superbloom.design/learning/blog/from-paper-to-infinity-whiteboard-inspiring-creativity-and-digital-collaboration-in-online-design-workshops/&#34;&gt;Zine Making&lt;/a&gt; workshop, hosted an Human Rights Centered Design (HRCD) UX Design Clinic, and engaged with the community on the Mozilla F&amp;amp;A Evaluation. We presented to and workshopped with global audiences at 2021 State of the Onion, the Internet vs. Democracy Forum, FOSDEM, FOSS Backstage + UX Clinic, Remote Design Week, UX Y’all, and the TU Delft Panel. &lt;/p&gt;
&lt;p&gt;With support from the Sloan Foundation, we co-published a &lt;a href=&#34;https://superbloom.design/learning/blog/communities-and-remote-collaboration/&#34;&gt;report on remote collaboration&lt;/a&gt; with Caroline Sinders that analyzed the needs of different academic communities in digital spaces during the COVID-19 pandemic. &lt;/p&gt;
&lt;p&gt;As part of the Human Rights Centered Design (HRCD) community, we participated in Monthly Calls and engaged with the community as part of the RightsCon 2021 HRCD track. Important topics we explored as part of HRCD include &lt;a href=&#34;https://hrcd.pubpub.org/pub/rtlusability/&#34;&gt;accessibility for right-to-left languages&lt;/a&gt; and &lt;a href=&#34;https://hrcd.pubpub.org/pub/uyydag1t/&#34;&gt;design &amp;amp; imposter syndrome&lt;/a&gt;. As members of the &lt;a href=&#34;https://sustainoss.org/&#34;&gt;SustainOSS&lt;/a&gt; working group, 2021 found our team hosting and participating in the &lt;a href=&#34;https://podcasts.apple.com/us/podcast/sustain-open-source-design/id1551862881&#34;&gt;Sustaining Open Source Design Podcast&lt;/a&gt;, and contributing to the &lt;a href=&#34;https://sustainoss.org/assets/pdf/Sustain-In-2021-Event-Report.pdf&#34;&gt;2021 Sustain Report&lt;/a&gt;. In 2022, expect to see us engaging in the community even more under our refreshed name + identity.&lt;/p&gt;
&lt;h2 id=&#34;new-design-congress&#34;&gt;New Design Congress&lt;/h2&gt;
&lt;p&gt;The &lt;a href=&#34;https://newdesigncongress.org/&#34;&gt;New Design Congress&lt;/a&gt; is Simply Secure’s inaugural fiscally sponsored project, and 2021 was an ambitious and busy year. Starting from a research focus of infrastructure as power, New Design Congress’ work expanded to new areas of research, including digital identity, ownership, comprehension and connectivity. &lt;/p&gt;
&lt;p&gt;Drawn from New Design Congress provocations, &lt;a href=&#34;https://www.inkandswitch.com/backchannel/&#34;&gt;Backchannel&lt;/a&gt; is a collaboration with &lt;a href=&#34;https://www.inkandswitch.com/&#34;&gt;Ink &amp;amp; Switch&lt;/a&gt; to co-design and prototype an alternative and resilient digital identity paradigm based on relationships rather than usernames and accounts, building in resistance to social engineering attacks and phishing campaigns. Published in Components, &lt;a href=&#34;https://components.one/posts/the-new-pornographers-tech-reviews&#34;&gt;The New Pornographers&lt;/a&gt; is a New Design Congress supported data-driven research report that looks into the prioritisation of exploitation of lust and aesthetics over functionality and user agency by consumer tech reviewers and Big Tech. &lt;a href=&#34;https://interactions.acm.org/archive/view/july-august-2021/aesthetic-flattening&#34;&gt;Aesthetic Flattening&lt;/a&gt;, co-authored by RMIT’s Jaz Choi, introduced a term for describing the limits to consumer computing hardware and the insufficient interaction models of modern platforms and tools, leading to a form of context-collapse experienced by users as a result. &lt;/p&gt;
&lt;p&gt;NDC launched &lt;a href=&#34;https://undersco.re/&#34;&gt;Underscore&lt;/a&gt;, an inclusive collection of open platforms, co-operative tools and public spaces, designed for community collaboration, moderation and data ownership. Underscore is responsible for hosting all of New Design Congress’ publications, livestream and internal collaboration processes, and has begun inviting aligned organisations to participate and publish together. &lt;a href=&#34;https://stream.undersco.re/series/the-para-real&#34;&gt;The Para-Real: Finding the future in unexpected places&lt;/a&gt;, an ongoing livestream series, was introduced to widespread attention as part of broader research into economics and ownership, delving into economic solidarity, platforming communities and subcultures.&lt;/p&gt;
&lt;p&gt;And finally, New Design Congress has been working on a (yet) to be announced prototyped software tool for navigating and understanding spoken testimony, created in response to broad colonialist criticism of tools and civil society. &lt;/p&gt;
&lt;h2 id=&#34;looking-ahead&#34;&gt;Looking Ahead&lt;/h2&gt;
&lt;p&gt;Keep your eyes peeled for Simply Secure rebrand - soon, we will have a new name, logo, website, and brand identity that better communicates our theory of change, growth and practice. [See our &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey/&#34;&gt;posts&lt;/a&gt; about the &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-refreshing-our-name-and-identity-part-2/&#34;&gt;process&lt;/a&gt;!] This has been quite a journey, and we’re thrilled to share our energized look and feel with the community in 2022.&lt;br&gt;
&lt;br&gt;
Want to know what else 2022 will bring? &lt;a href=&#34;https://simplysecure.org/what-we-do/slack/&#34;&gt;Join our community slack&lt;/a&gt;, &lt;a href=&#34;https://simplysecure.org/contact/&#34;&gt;reach out&lt;/a&gt;, and follow us on &lt;a href=&#34;https://twitter.com/simplysecureorg&#34;&gt;Twitter&lt;/a&gt; to find out!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>MDF Tech Exchange Fellow, Tech Design Researcher</title>
      <link>https://superbloom.design/community/opportunities/mdf-tech-exchange-fellow-tech-design-researcher/</link>
      <pubDate>Fri, 17 Dec 2021 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/community/opportunities/mdf-tech-exchange-fellow-tech-design-researcher/</guid>
      <description>&lt;h3 id=&#34;were-looking-for-an-experienced-tech-design-researcher-to-catalyze-building-our-new-trust-initiative-a-community-based-data-driven-research-initiative-that-results-in-resources-for-technologists-designers-and-policymakers&#34;&gt;We’re looking for an experienced Tech Design Researcher to catalyze building our new TRUST initiative, a community-based data-driven research initiative that results in resources for technologists, designers, and policymakers.&lt;/h3&gt;
&lt;h3 id=&#34;the-role&#34;&gt;The role&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You’ll be a critical part of our team, responsible for collaboratively outlining our research agenda, conducting community-based research to support real needs, and building the TRUST initiative in an open, secure, and publicly accessible way.&lt;/li&gt;
&lt;li&gt;You’ll work with internal and external project teams, bringing your data-based expertise to collaborate with our human-centered design expertise to explore some of today’s thorniest issues at the intersection of technology and society. &lt;/li&gt;
&lt;li&gt;You’ll help the team build resources for the community, share them openly, and “translate” key concepts across sectors. &lt;/li&gt;
&lt;li&gt;You’ll report directly to the Executive Director, and work in close partnership with our Managing Director, Program Director, and other staff. This role will start in early February, 2022, and will be in the $60,000-$85,000 range, including benefits.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;about-us&#34;&gt;About us&lt;/h3&gt;
&lt;p&gt;Changing who technology serves. Simply Secure is a small US 501(c)3 nonprofit organization, founded in 2014 at the intersection of digital design and human rights. &lt;/p&gt;
&lt;p&gt;Simply Secure leverages design as a transformative practice to shift power in the tech ecosystem. We apply a critical lens to technology development, and view design as an intervention opportunity to center people and their needs. We collaborate closely with others in the space to grow the community focused on shaping our collective online future. Our vision is a world where everyone has the knowledge, network, and digital tools needed to enrich their lives. &lt;/p&gt;
&lt;p&gt;Our approach to changing who technology serves includes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Resourcing &amp;amp; Practice: building human-centered design capacity through coaching and leadership programs, developing content and information architecture strategy, and facilitating workshops and organizational sprints.&lt;/li&gt;
&lt;li&gt;Research &amp;amp; Innovation: conducting organizational and community-based research, producing best practices and design resources for practitioners and policymakers, and collaborating with funders to leverage research practices and ecosystem experience.&lt;/li&gt;
&lt;li&gt;Community Convening: cultivating a global community through in-person and online opportunities, increasing communal connectivity and knowledge-sharing, and incubating a values-driven practitioner movement through fiscal sponsorship.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Over the past seven years, we’ve supported hundreds of projects and practitioners, including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Partnering with &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;OTF&lt;/a&gt; to develop the infrastructure-expanding &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Usability Lab&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Cultivating design leadership through our &lt;a href=&#34;https://simplysecure.org/underexposed/&#34;&gt;Underexposed Residency program&lt;/a&gt;. &lt;/li&gt;
&lt;li&gt;Supporting funders like &lt;a href=&#34;https://luminategroup.com/&#34;&gt;Luminate&lt;/a&gt; to better understand their grantees’ experiences through program evaluation, shared via our &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;On Trust and Transparency report&lt;/a&gt;. &lt;/li&gt;
&lt;li&gt;Improving user accessibility and trust for &lt;a href=&#34;https://github.com/phishdetect&#34;&gt;PhishDetect&lt;/a&gt;, with Amnesty International.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We’re currently working through an open rebranding process, moving away from the name “Simply Secure” and toward an identity that more accurately reflects the diversity of the work we do. &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;Learn more on our blog&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In 2022, the organization aims to launch the TRUST initiative &amp;ndash; a “big tent” collaborative focused on exploring and answering critical design research questions to further democracy, human rights, and internet freedom, through safe, equitable participant management. In the inaugural year, TRUST will focus on the interplay between tech policy, UX design, and technology, supporting community-based data-driven research that result in resources for technologists, designers, and policymakers. The goal is to increase understanding in the broader internet freedom space about the role of UX/UI design, and how design is a transformative intervention point for a more democratic online experience for all. The MDF Tech Exchange Fellow would help launch this initiative. &lt;/p&gt;
&lt;h3 id=&#34;about-you&#34;&gt;About you&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;A critical thinker with strengths as a strategist, convener, and builder.&lt;/li&gt;
&lt;li&gt;Knowledgeable or interested in usable security, privacy, big data, algorithms, tech policy and internet freedom issues.&lt;/li&gt;
&lt;li&gt;Experienced with privacy conscious web development, leveraging static site generators (e.g. Hugo), CSS, Javascript (client &amp;amp; server side), etc.&lt;/li&gt;
&lt;li&gt;Experienced with technical problem solving focused around research, data analysis and visualization, using the appropriate technical tools, e.g. Python, R, ETL pipelines, SQL-based databases, NoSQL document stores, D3js, etc. &lt;/li&gt;
&lt;li&gt;Knowledgeable about one or more of the following areas: open source software, internet freedom, tech criticism and activism, human rights technology.&lt;/li&gt;
&lt;li&gt;Are comfortable with cross-cultural communication, collaboration and conflict resolution, through work with international teams.&lt;/li&gt;
&lt;li&gt;Availability during our prime work hours (11-6pm Central Europe / 10-5pm UK / 8-6pm US Eastern / 8-3pm US Pacific).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;nice-to-have&#34;&gt;Nice to have&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You have experience and deep understanding of the civil society space as it intersects with technology.&lt;/li&gt;
&lt;li&gt;Experience with research and design work, e.g. human-centered design, design thinking, service design, ux design, or participatory research (specifically field research).&lt;/li&gt;
&lt;li&gt;Have experience managing and enjoy working with a fully remote, distributed team, across many time zones and cultures.&lt;/li&gt;
&lt;li&gt;Comfortable with collaborative work tools (we currently use Notion, Miro, Slack and Google Suite).&lt;/li&gt;
&lt;li&gt;Proficiency in a language other than English &amp;ndash; especially German, French or Spanish.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;sound-like-a-good-fit&#34;&gt;Sound like a good fit?&lt;/h3&gt;
&lt;p&gt;Please send us your resume and 2-5 community-based research topics you’re interested in pursuing as part of this Fellowship to&lt;a href=&#34;mailto:hr@superbloom.design&#34;&gt;&lt;/a&gt;&lt;strong&gt;&lt;a href=&#34;mailto:jobs@superbloom.design&#34;&gt;jobs@superbloom.design&lt;/a&gt;&lt;/strong&gt; with the subject line “MDF Tech Exchange Fellow”.  &lt;strong&gt;The deadline for applications is 00:00 on Saturday, January 15.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We believe that systemic bad behaviors disproportionately hurt the most marginalized people in society — including people of color, people from working class backgrounds, women and LGBTQ people. We believe that these communities must be centered in the work we do. We strongly encourage applications from people with these identities or who are members of other marginalized communities.  We are open to candidates from around the world. Final hiring decisions will be contingent upon our ability to contract and pay in the candidate’s country. Simply Secure does not provide relocation or visa support.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Communities and Remote Collaboration</title>
      <link>https://superbloom.design/learning/blog/communities-and-remote-collaboration/</link>
      <pubDate>Mon, 13 Dec 2021 15:22:29 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/communities-and-remote-collaboration/</guid>
      <description>&lt;h3 id=&#34;how-are-hallway-conversations-and-academic-conferences-recreated-in-the-digital-sphere&#34;&gt;How are hallway conversations and academic conferences recreated in the digital sphere?&lt;/h3&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/what-does-a-community-need1_hu_11e9df4cc1042e1e.png&#34; width=&#34;740&#34; height=&#34;590&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;With support from the &lt;a href=&#34;https://sloan.org/&#34;&gt;Alfred P. Sloan Foundation&lt;/a&gt;, Convocation Research + Design and Simply Secure conducted ethnographic and human centered design research to surface and analyze the needs of different academic communities in digital spaces during the COVID-19 pandemic.&lt;/li&gt;
&lt;li&gt;The report dives into three main categories: the Digital Nature of Events and Communities, the Positives of Digital Events, and the Frictions of Digital Events.&lt;/li&gt;
&lt;li&gt;The 10 recommendations are grounded in community research, and aim to alleviate the burden and cognitive overload that attendees might be facing right now due to the pandemic.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/resources/What_Does_a_Community_Need_Report_2021.pdf&#34; class=&#34;button button--secondary read-more&#34; style=&#34;text-decoration: none;&#34;&gt;Read the full report&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In February 2021, Convocation Research + Design and Simply Secure were supported by the Alfred P. Sloan Foundation to conduct ethnographic and human centered design research to surface and analyze the needs of different academic communities in the context of digital events and spaces during the COVID-19 pandemic.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The goal:&lt;/strong&gt; &lt;em&gt;To understand how hallway conversations and academic conferences are recreated in the digital sphere.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The study presented in this report explores the barriers, frictions, opportunities, and advantages of remote events. Seven virtual academic conferences were observed to assess new emerging norms, event organizers’ needs, attendees’ preferences, and the state of remote events and digital convenings during the COVID-19 pandemic.&lt;/p&gt;
&lt;h3 id=&#34;acknowledging-harm&#34;&gt;Acknowledging Harm&lt;/h3&gt;
&lt;p&gt;Community-based research is designed to be responsive, but the spread and management of COVID-19 itself is not a constant or linear event; new variants emerge, cities shut down and reopen, and vaccination rollout is slower in some countries and areas than others. &lt;a href=&#34;https://journals.sagepub.com/doi/10.1177/08912432211001302&#34;&gt;The COVID-19 pandemic mirrors the structural inequalities that existed before it, both online and offline&lt;/a&gt;. On top of these existing inequities, COVID-19 is generating new ones, with sexual harassment in the workplace, blurred work and home space boundaries, and emotional and physical labor falling more on people who self-identify as women and people of color.&lt;/p&gt;
&lt;p&gt;Although burnout, COVID-19, and “Zoom fatigue” are real factors that impact communities and individuals, their effects and impact are difficult to measure. Our research goal was to see what barriers and opportunities are possible with remote convenings, but as researchers, we cannot separate COVID-19’s emotional and physical impacts on communities. More specifically, it’s difficult to understand general remote best practices in a COVID-19 mitigated future, because these best-practices cannot be decoupled or divorced from the reality of the COVID-19 pandemic. If someone is experiencing burnout, no design or UX or UI improvement will fix the emotional labor that is living with COVID19.&lt;/p&gt;
&lt;h3 id=&#34;contextualizing-the-impact-of-the-covid-19-pandemic&#34;&gt;Contextualizing the Impact of the Covid-19 Pandemic&lt;/h3&gt;
&lt;p&gt;The study presents findings related to digital event design and the current state of community engagement within this space. Throughout the research, two conflicting themes emerged in regard to participation in remote events: remote events are much more accessible to attend, and at the same time, they often compete with external life circumstances.&lt;/p&gt;
&lt;h3 id=&#34;report-insights--observations&#34;&gt;Report Insights &amp;amp; Observations&lt;/h3&gt;
&lt;p&gt;The report outlines 16 major insights across 3 focus areas, and 10 recommendations. Insights include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;It’s Not Just Zoom Fatigue, It’s General Fatigue&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Tacit Community Knowledge Is Not Easily Shared to Newcomers&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Almost All the Events Had This Similar Problem: Time Zones are Difficult to Manage&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Cameras On or Off Don’t Determine Engagement or Interest&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Design Matters&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;recommendations&#34;&gt;Recommendations&lt;/h3&gt;
&lt;p&gt;Digital events require as much organization and curation as an offline event, but they bring new and specific challenges directly related to software and digital environments. The recommendations might seem a bit obvious at first, but they are all focused on streamlined communication, event support, understanding how tools and facilitation can help engagement and why structure for organizers and for attendees. These kinds of recommendations can help lower the burden and cognitive overload that attendees might be facing right now, especially this deep into the pandemic.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;Create Clear and Concise Information Update for Users Over Email&lt;/em&gt; &lt;/li&gt;
&lt;li&gt;&lt;em&gt;Event Planning, Programming and Moderation Matters&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;A Schedule and a Plan Matter for Engagement&lt;/em&gt; &lt;/li&gt;
&lt;li&gt;&lt;em&gt;Scheduling Unstructured Time For Participants to Mingle&lt;/em&gt; &lt;/li&gt;
&lt;li&gt;&lt;em&gt;Breaks Matter (and Are Needed!)&lt;/em&gt; &lt;/li&gt;
&lt;li&gt;&lt;em&gt;The Tools Chosen for Events Matter&amp;hellip;and So Does the Training You Offer&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Not All Engagement Can Be Equally Measured&lt;/em&gt; &lt;/li&gt;
&lt;li&gt;&lt;em&gt;There is No Hallway&amp;ndash; But People Need the Ability to Create Their Own Spaces In Events&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Switch Up Your Schedule to Accommodate for Time Zones&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Nothing Can Replicate in Person&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;looking-forward&#34;&gt;Looking Forward &lt;/h3&gt;
&lt;p&gt;This report was written in November 2021, as the United States and other countries in North America and Europe are rolling out booster shots while facing new lockdown policies, a new variant has emerged on the global stage, and other countries across Africa and South America are still working toward administering their first vaccine shots, due to lack of access. It’s difficult at this moment to determine or predict what the future could hold. To support the academic community in the face of future unknowns, this research proposes a number of key points for digital and remote events in the coming months and years. &lt;/p&gt;
&lt;p&gt;The main highlight includes the fact that equity, accessibility, and responsibility need to be centered. What was gained during remote events should not be lost if events decide to go back to in-person or try a hybrid model. &lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/resources/What_Does_a_Community_Need_Report_2021.pdf&#34; class=&#34;button button--secondary read-more&#34; style=&#34;text-decoration: none;&#34;&gt;Read the full report&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits:&lt;/h3&gt;
&lt;p&gt;Researchers: Caroline Sinders, Kacie Harold, and Melina Garcia with support from Georgia Bullen, Melissa Huerta and Molly Wilson &lt;/p&gt;
&lt;p&gt;With support from the &lt;a href=&#34;https://sloan.org/&#34;&gt;Alfred P. Sloan Foundation &lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>SSL, TLS, and FTP... Oh My!</title>
      <link>https://superbloom.design/learning/blog/ssl-tls-and-ftp-oh-my-guiding-users-to-set-up-tls-certificates-in-filezilla/</link>
      <pubDate>Mon, 13 Dec 2021 11:41:23 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/ssl-tls-and-ftp-oh-my-guiding-users-to-set-up-tls-certificates-in-filezilla/</guid>
      <description>&lt;h2 id=&#34;guiding-users-to-set-up-tls-certificates-in-filezilla&#34;&gt;Guiding users to set up TLS Certificates in FileZilla&lt;/h2&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/ssl-tls-and-ftp-oh-my1_hu_a0852cd314cdd383.png&#34; width=&#34;740&#34; height=&#34;379&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;FileZilla Server has over 20 years experience providing free, open-source file transfer protocol software for client and server. &lt;/li&gt;
&lt;li&gt;As part of the &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;OTF Usability Lab&lt;/a&gt;, Simply Secure worked with FileZilla Server to improve usability of the tool, specifically with high-risk users in mind. We conducted user research and gave design recommendations, which resulted in personas, an expert review, and new UI recommendations for creating a TLS certificate.&lt;/li&gt;
&lt;li&gt;The objective was a safer, easier way to set up TLS certificates using the Let’s Encrypt service through a wizard that guides users while providing explanation and reassurance.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;User researchers and designers often work on projects in which the domain is new to them. Do designers need to be domain experts? Is it necessary to do months of domain research before starting a complex and technical project? &lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://filezilla-project.org/&#34;&gt;Filezilla&lt;/a&gt; is a well-known free and open source tool for FTP (File Transfer Protocol) users, which has been around for just over 20 years. As their website explains:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“A File Transfer Protocol (FTP) is a standardized network protocol used to transfer files between a client and a server over the internet or any other TCP/IP network. FTP has been designed to promote sharing of files, across all types of computers. A strength of FTP is the reliable and efficient bulk transfer of files. FTP is popular with website owners and web designers to upload files to the servers of their web hosting company. Another common use case is the exchange of files between companies; FTP is in many organizations the de facto method for transferring large volumes of data.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;File sharing is an essential component of a networked society, but few designers know the ins-and-outs of FTP tools. So when we enthusiastically agreed to support FileZilla with user research and design recommendations as part of the OTF Usability Lab, there was some learning that we had to do to get up to speed and tackle the unique design challenge of adding a certificate to the FileZilla server.  &lt;/p&gt;
&lt;p&gt;Specifically, our role was to work with the FileZilla team to improve usability of the tool, specifically with high-risk users in mind. We conducted user research and gave design recommendations, which resulted in personas, an expert review, and new UI recommendations for creating a TLS certificate. The objective was a safer, easier way to set up TLS certificates using the Let’s Encrypt service through a wizard that guides users while providing explanation and reassurance.&lt;/p&gt;
&lt;h2 id=&#34;the-project&#34;&gt;The Project &lt;/h2&gt;
&lt;p&gt;We approached this project through the lens of the high-risk use case such as a human rights organization employees that routinely share files with human rights defenders in the field. At Simply Secure, many of our projects focus on this type of use case so we were able to draw from our previous experience. &lt;/p&gt;
&lt;p&gt;This project was scoped in two phases. Phase 1 included foundational research (needs-finding interviews with users of secure file storage, a survey of FileZilla Server users, and comparison analysis of secure file storage tools), user personas, and an expert design review of the installation FileZilla Server and setting up a server. The high-risk persona’s needs and expert review led us to overarching design recommendations that we remembered through the project and guide future FileZilla Server improvements. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/ssl-tls-and-ftp-oh-my2_hu_604ce7dbb0fbc504.png&#34; width=&#34;740&#34; height=&#34;537&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;We translated our research into persona needs, then established design recommendations based on those needs.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;With the foundational work completed, in Phase 2 we prioritized the user experience of the security features and settings of FileZilla, specifically setting up a TLS certificate using the &lt;a href=&#34;https://letsencrypt.org/how-it-works/&#34;&gt;Let&amp;rsquo;s Encrypt&lt;/a&gt; service. We wanted this process to be accessible to a high-risk user type who might be new to FTP or not have access to dedicated IT advice. For this technical challenge, we used several tactics to fill in the gaps of our knowledge.&lt;/p&gt;
&lt;h2 id=&#34;strategies-for-complex-problems-and-technical-challenges&#34;&gt;Strategies for complex problems and technical challenges &lt;/h2&gt;
&lt;h3 id=&#34;competitor-research&#34;&gt;Competitor research&lt;/h3&gt;
&lt;p&gt;In a kickoff call, our favorite question to ask was, “Who are your competitors?” To add to this list, we also asked colleagues and listened for alternatives mentioned in the needs-finding interviews. We compared a wide-array of tools, from CrushFTP to Signal to Airdrop, to identify patterns, good explanations, and solutions. In addition to studying the user interfaces, we also watched competitors’ how-to guides, read FAQs, and listened to conference talks. &lt;/p&gt;
&lt;h3 id=&#34;map-the-current-flow&#34;&gt;Map the current flow&lt;/h3&gt;
&lt;p&gt;For a complex problem like this, we had to understand how setting up a new certificate works currently. Instead of going through the flow ourselves, we wanted to see how it was supposed to work and ask questions at every step of the process. We watched the developer go step by step through the process while we visually mapped each step. Later, we added screenshots, ideas for design, and text for explanations and definitions. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/ssl-tls-and-ftp-oh-my3_hu_83cae4dcc543113d.png&#34; width=&#34;740&#34; height=&#34;343&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;How we mapped the current process of adding a certificate using Let’s Encrypt and also UX issues we identified with these steps.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;stretch-the-boundaries-of-inspiration&#34;&gt;Stretch the boundaries of inspiration&lt;/h3&gt;
&lt;p&gt;For many of the tools that Simply Secure partners with, there aren’t many examples of design patterns already established so finding inspiration can be a challenge. In contrast to complex problems, there are common problems that have plenty of solutions already in existence (for example: editing an online shopping cart). While we may not be able to find a perfect example that would help us solve the complex problems, it’s possible to piece together other patterns and make some leaps. Indirect competitors, such as &lt;a href=&#34;https://www.box.com/home&#34;&gt;Box.com&lt;/a&gt;, provided us with some inspiration for design recommendations.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/ssl-tls-and-ftp-oh-my4_hu_8b5dd1b2abb26318.png&#34; width=&#34;740&#34; height=&#34;273&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Box.com showed our design recommendations in context so that we could show the team what implementation could look like.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;learning-from-domain-experts-and-user-interviews&#34;&gt;Learning from Domain Experts and User Interviews&lt;/h3&gt;
&lt;p&gt;As designers that work with and support many tools, we tend to have broad expertise in many topics and areas, rather than deep expertise in a specific area. Given that, the best thing is to connect with domain experts who can point us in the right direction. For this project, collaborating closely with the FileZilla team was essential, as they are leading experts in FTP. &lt;/p&gt;
&lt;p&gt;In our user research and usability testing, we interviewed people with great knowledge of FTP. At the beginning of the interview, we told the participants that we were not an expert in FTP so we might have questions for them if we don&amp;rsquo;t understand anything. They were all very understanding and as a result we were able to learn from their experiences for our usability research, while also getting some of their knowledge about the technical aspect. &lt;/p&gt;
&lt;h3 id=&#34;experiment-with-feedback&#34;&gt;Experiment! (*with feedback)&lt;/h3&gt;
&lt;p&gt;After mapping out the current flow of setting up an SSL certificate, we started experimenting with new flows. We knew we weren’t going to get it right the first time and that we would certainly have misconceptions about the technology, so it was crucial that we got feedback from the FileZilla team (our domain experts). We held collaborative design sessions with the FileZilla team to get us in the right direction, and even did some live design ideation to get instant feedback. &lt;/p&gt;
&lt;h3 id=&#34;ask-questions--consider-different-methods-of-recording-information&#34;&gt;Ask questions + consider different methods of recording information&lt;/h3&gt;
&lt;p&gt;On any project, we are always fearful of not knowing enough. Asking questions that may at first seem obvious, can help your collaborators in ways you never expected and lead to teams reconsidering why things are the way they are. When trust is formed it becomes easier to be vulnerable, and vulnerability supports collaboration and the design research process. A key challenge in these moments can be taking good enough notes to remember the discussion that was had. Although we normally shy away from recording conversations, we found it especially useful in this project so that we were able to refer back to the sessions, and review the full context of technical constraints and design choices.&lt;/p&gt;
&lt;h2 id=&#34;conclusion&#34;&gt;Conclusion&lt;/h2&gt;
&lt;p&gt;Through a series of tactics to acquire domain expertise quickly by learning from great mentors and domain experts, we were able to learn just enough about FileZilla Server and FTP to conduct thorough user research and provide recommendations that will help improve safe and secure use of FileZilla Server by improving the usability of navigating the security options. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/ssl-tls-and-ftp-oh-my5_hu_30e3b1b014fe22c4.png&#34; width=&#34;740&#34; height=&#34;311&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Our design recommendations took the form of wireframes in a flow.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Contributors: Kelsey Smith, Bernard Tyers, and Rae McKelvey&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
With support from &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Open Technology Fund Usability Lab&lt;/a&gt;, in collaboration with the &lt;a href=&#34;https://filezilla-project.org&#34;&gt;FileZilla&lt;/a&gt; team.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>On Getting Things Done: A Conversation with Matthew Wild from Snikket</title>
      <link>https://superbloom.design/learning/blog/on-getting-things-done-a-conversation-with-matthew-wild-from-snikket/</link>
      <pubDate>Wed, 08 Dec 2021 15:22:13 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/on-getting-things-done-a-conversation-with-matthew-wild-from-snikket/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/on-getting-things-done_hu_2177ba16c1e9d2f9.png&#34; width=&#34;740&#34; height=&#34;490&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://snikket.org/&#34;&gt;Snikket&lt;/a&gt; is a safe and secure, free and open source XMPP-based messaging platform that is hosted on an individual server for more control and security for the users.&lt;/li&gt;
&lt;li&gt;As part of the &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;OTF Usability Lab&lt;/a&gt;, we supported Matthew and Snikket by helping to improve the user experience across platforms through a heuristic review, a user study, and several UX design explorations.&lt;/li&gt;
&lt;li&gt;We interviewed Matthew Wild, the creator of Snikket. He shares his work process and experience working with Simply Secure to improve Snikket’s usability.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href=&#34;https://snikket.org/&#34;&gt;Snikket&lt;/a&gt; is an XMPP-based messaging platform that aims to provide an open and secure alternative to proprietary messaging apps such as WhatsApp, Facebook Messenger, and Telegram. Unlike most other messaging apps, Snikket can be hosted on an individual server (including Raspberry Pis) for more control and security. While the XMPP ecosystem remains fragmented and highly technical, Snikket’s goal is to fill the gap with consistency and usability. &lt;/p&gt;
&lt;p&gt;Through the &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;OTF Usability Lab&lt;/a&gt;, our work with Snikket focused on improving the user experience across platforms and balancing out the ease of learning versus the efficiency of use. In particular, we did a heuristic review of Snikket apps and web interfaces, conducted a user study, carried out several UX design explorations and provided design recommendations to address areas where there are barriers for adaptation and improving the onboarding experience. An upcoming blog post will explore in more detail some of the implementations of this work.&lt;/p&gt;
&lt;p&gt;In this conversation with Matthew Wild, the creator of &lt;a href=&#34;https://snikket.org/&#34;&gt;Snikket&lt;/a&gt; he shares about his work process and experience in working with Simply Secure to improve Snikket’s usability.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The transcript of this conversation was edited for length and clarity.&lt;/em&gt; &lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;strong&gt;Simply Secure (SimSec): Could you tell us more about your motivation for creating Snikket? How long have you been working on it?&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Matthew Wild (MW&lt;/strong&gt;): It&amp;rsquo;s been probably nearly two years now. I&amp;rsquo;ve been working on decentralized and open messaging for over 10 years, mostly on the server side and the technical parts. I&amp;rsquo;ve always been telling people, you should use open communication platforms, and not use these centralized proprietary systems. Over the years I definitely have helped move a lot of people over thanks to stuff that I&amp;rsquo;ve written.&lt;/p&gt;
&lt;p&gt;But I really struggled even just to get my own family over, they were still messaging each other using WhatsApp. After some time, I thought, well, why can&amp;rsquo;t I move my family over to this thing that I work on all the time? They never really understood what it was that I worked on anyway because it was all server stuff, and they don&amp;rsquo;t really know what a server is. So, I started really thinking about how to improve things from the user&amp;rsquo;s perspective, how to make things more simple, more accessible. And so I realized that the parts that I&amp;rsquo;d been working on the server side were just a part of what needed to happen. I had been making a lot of improvements there, along with other contributors to &lt;a href=&#34;https://prosody.im/&#34;&gt;Prosody&lt;/a&gt;, but really just the server-side, for people to adopt it and XMPP and decentralized messaging in general, you need a whole package of something that&amp;rsquo;s easy to use and works well together. &lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“Why can&amp;rsquo;t I move my family over to this thing that I work on all the time?”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I realized that what we needed was a friendly name, a friendly logo, a friendly website, an easy-to-use installation server, and easy apps for people to sign up for. From experience, one of the hardest things about getting people to use XMPP was just to get them started, get them to choose a server, an account, set a password, and find an app. And so that was the first thing that I focused on with Snikket was on-boarding and making it easier for people to get on board. &lt;/p&gt;
&lt;p&gt;The first prototype was an invitation link, and that&amp;rsquo;s still a big part of Snikket. Now, you just send someone a link, and it helps them install the app and get started on your server. So yeah, I sent the link to my family. Now I have 10 people on my family&amp;rsquo;s Snikket server and they no longer use WhatsApp for talking to each other. Obviously, they still use it for talking to their other contacts, but within the family, we&amp;rsquo;re all using Snikket, which I think is a big success (laugh). &lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“I started really thinking about how to improve things from the users&amp;rsquo; perspective, how to make things more simple, more accessible.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;SimSec: We know that you&amp;rsquo;re the creator of Snikket, but what exactly is your role in the team?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MW:&lt;/strong&gt; Like a particular role that I do? Absolutely everything (laugh). So I do a bit of work on developing, obviously I develop the server. That&amp;rsquo;s my primary background. I also do a bit of work on the apps, just trying to make them more polished. But the bulk of the work on the apps is luckily done by open source developers, &lt;a href=&#34;https://gultsch.de/&#34;&gt;Daniel Gultsch&lt;/a&gt; for &lt;a href=&#34;https://conversations.im/&#34;&gt;Conversations&lt;/a&gt;, and the &lt;a href=&#34;https://tigase.net/&#34;&gt;Tigase&lt;/a&gt; team for &lt;a href=&#34;http://siskin.im&#34;&gt;Siskin&lt;/a&gt;. So Snikket builds on top of both of those. &lt;/p&gt;
&lt;p&gt;I do development across all the different pieces, but I also do lots of non-development tasks. So I have to also do the fundraising, applying for grants, and now I&amp;rsquo;m working on the hosting platform as well. So that also means that I&amp;rsquo;m managing servers, and things like that, as well as trying to manage and help grow the community. A bit of marketing, writing blog posts, managing the website— there&amp;rsquo;s not really much that I don&amp;rsquo;t do. So I definitely don&amp;rsquo;t have a role. It&amp;rsquo;s just Snikket, Snikket, Snikket. All the way through.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec: Did you receive any support from the community?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MW:&lt;/strong&gt; Yeah, I&amp;rsquo;ve had a lot of support, especially from people who are coming from the Prosody community. Obviously I&amp;rsquo;ve been working on Prosody for a long time, so I&amp;rsquo;ve got some good friends there who have been very supportive of Snikket, and they&amp;rsquo;ve helped. For example, one of the community members, Jonas, wrote the whole Snikket web interface, which was remarkable, because I thought the first version of it probably wouldn&amp;rsquo;t have much of a web interface. But it was really important to make it really easy to use, and he just did it. Now it works really well, and people do like it. Also, there is Kim, a longtime Prosody contributor, who continues to help a great deal with things on the server side, the technical parts. As well as everyone who is testing the apps, reporting bugs, and donating. It&amp;rsquo;s been really helpful to have this whole community behind it.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“Every time a user gets confused about something, however small it is, I have to take that feedback on board.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;SimSec:&lt;/strong&gt; What&amp;rsquo;s great in our opinion is that you also make it quite easy for people to send feedback and contribute. You get all the support because you explicitly make the process transparent and everybody can see what the newest updates are and what is currently being worked on if they follow your GitHub! &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MW:&lt;/strong&gt; Exactly. I think that part&amp;rsquo;s important to me because part of the whole point of Snikket is making it easier for the users. So every time a user gets confused about something, however small it is, I have to take that feedback on board and not just think, well, if they knew more technical stuff, they would know why it&amp;rsquo;s like this, or they should learn, they should read the documentation. You really can’t expect that, no one reads documentation to use WhatsApp. They just use it. So I want Snikket to be that easy. If they have any problems, I really want to know about them.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec: What do you think would be the best part of your job?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MW:&lt;/strong&gt;  I would still like to just be working on the technical parts (laugh). I really like lower-level coding. I&amp;rsquo;m not a big fan of working on user interfaces, but I definitely got a good appreciation for it now. I think I am developing a bit of an instinct for “this doesn&amp;rsquo;t look very appealing” or “it doesn&amp;rsquo;t look very user-friendly”. From listening to all the feedback, I can now look at something and think well, this is not going to be very easy for people to use, they will complain that they don&amp;rsquo;t understand this or this is in the wrong place. One of the things that continues to surprise me is that even when you have guessed what the users will think they always come back with different feedback that you never even thought of. So I think I do just like it all. I wouldn&amp;rsquo;t be doing it if I didn&amp;rsquo;t enjoy any of it. But given the choice, I&amp;rsquo;d probably just still be working on it on the server side.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec: What about the least favorite part?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MW:&lt;/strong&gt; Oh, the least favorite part is definitely finding funding and writing grant applications and just dealing with money in general and things like that. I just really, really don&amp;rsquo;t like that part of it. But at the same time, I want the project to be sustainable. So I&amp;rsquo;ve tried working on open source in the past while having a full-time job. It&amp;rsquo;s possible, but it&amp;rsquo;s very, very difficult and the project progresses very slowly and it&amp;rsquo;s always a little bit worse than it could be. So I&amp;rsquo;m hoping that if I can keep getting funding for Snikket then we can help Snikket and related projects grow and help fund more open source development which is, is my dream really: just help making this thing so they can compete with the proprietary messengers and be just as good, or even better.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“It&amp;rsquo;s really about just knowing that the people are contributing, understanding how they work best, and helping them achieve that.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;SimSec: What do you think is the most challenging thing about managing Snikket and how do you overcome it?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MW:&lt;/strong&gt; Yeah, so from my own time management perspective, it&amp;rsquo;s obviously very difficult for me to work on so many different projects. Within Snikket, there&amp;rsquo;s the hosting stuff, there are the apps, there&amp;rsquo;s the server side, there&amp;rsquo;s a web interface. I realistically can&amp;rsquo;t work on all of them at the same time. So I try to split it up into chunks. I do a little sprint of work on the apps for maybe two weeks to a month, then I&amp;rsquo;ll work a bit on the server side for a little while, and I&amp;rsquo;ll work a bit on the hosting for a while. That helps my brain get into a particular mode and be a bit more productive. &lt;/p&gt;
&lt;p&gt;But one of the problems with open source is managing other people who you have to be respectful of their time, because they are volunteers. And although they often are very happy to contribute, you really can&amp;rsquo;t put many strings on it. And you can&amp;rsquo;t say, you know, you have to deliver it by the end of this week. That makes planning a lot more difficult. It&amp;rsquo;s really about just knowing that the people are contributing, understanding how they work best, and helping them achieve that. And, you know, just being very gentle with them. It&amp;rsquo;s very different to working at a company where you&amp;rsquo;re employing someone and you get to set deadlines and be a bit more strict and so on. But when someone&amp;rsquo;s not working full time for you, that’s very different. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec: What is the process of working with volunteers and contributors like?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MW:&lt;/strong&gt; It really varies. One of the things that is quite interesting to me is that people would file bug reports, but oftentimes the people who file the bug reports also have an idea of how they want the problem to be solved. I think part of my job is looking at the bigger picture and thinking well actually, it would be better if we solved it like this, or maybe we don&amp;rsquo;t want to solve this problem at all. &lt;/p&gt;
&lt;p&gt;For example, some people have asked me how to have Snikket groups with over 1000 people in them. Although it&amp;rsquo;s technically possible, you would have to make some changes in the user interface to make that number of people easy to take in for someone to use. So I really want to keep Snikket very focused on a particular use case: smaller groups of people, family, workplace, clubs, and things like that. So one of the things that I have to do daily is when these bug reports come in, this feedback will be translated into tasks for people to work on, whether it&amp;rsquo;s me or some of the contributors. It&amp;rsquo;s not just a case of pointing the contributors to the bug reports, because they don&amp;rsquo;t see the whole picture. I have to try and spend time going through the bug reports and figuring out what one thing that they actually have to work on.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“If something doesn&amp;rsquo;t get delivered in a certain release, it just doesn&amp;rsquo;t. And it&amp;rsquo;s not the end of the world.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;SimSec: How do you guys keep each other accountable?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MW:&lt;/strong&gt; (Laugh) Yeah, we don&amp;rsquo;t. At the end of the day, one of the benefits of working for myself is that I don&amp;rsquo;t have anyone telling me about deadlines. If something doesn&amp;rsquo;t get delivered in a certain release, it just doesn&amp;rsquo;t. And it&amp;rsquo;s not the end of the world. And you know, no one&amp;rsquo;s gonna get fired. So as long as we&amp;rsquo;re making overall progress, which generally we are, and I&amp;rsquo;m happy with that. There&amp;rsquo;s no blame if someone doesn&amp;rsquo;t achieve something that they said they were going to do. I understand that sometimes things get in the way. At the same time, there are things like decisions that I make, being in charge of the project I could just make, often I try to run things past other people to see what they think about it. I like getting feedback from other people in the community about the direction that we&amp;rsquo;re going in. Although I don&amp;rsquo;t have to do that, I feel it&amp;rsquo;s my responsibility because I&amp;rsquo;m not the only one deciding where the project goes, but I am responsible for it. So I try to help as many people participate in decisions as possible.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec: What is your personal approach to project management?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MW:&lt;/strong&gt;  Yeah, to prioritise. It&amp;rsquo;s very difficult because it&amp;rsquo;s a balance between so many things. For example, to prioritise getting the project sustainable, I really ought to be working on the hosting platform full time, because that can actually bring in some income and help get more people onto Snikket. I also try and prioritise things that people report a lot because it&amp;rsquo;s things that a lot of people run into. So, anything to do with usability. When someone keeps complaining about the same bugs, I know that for every person that actually gives me that feedback, there are probably 10 more people who don&amp;rsquo;t bother reporting it. So I try to keep my ears open for even small issues. If they keep coming up more than once, more than twice, then I know, it&amp;rsquo;s a high priority issue. I try and prioritise getting a fix for that, but with limited resources, it can be very difficult. So we just try and do our best.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec: What are the biggest lessons that you&amp;rsquo;ve learned from working on Snikket?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MW:&lt;/strong&gt; I think planning to timescale with a small team of volunteers is very, very difficult. So I try to be very flexible with what goes into each release. I&amp;rsquo;m very reactive in what&amp;rsquo;s going on. One week, one person might say they&amp;rsquo;ve got the week off work, and they want to spend time helping hack on Snikket. And then another week, they are completely not available. It&amp;rsquo;s very difficult to plan for things like that so I try to keep the bureaucracy down to a minimum because it helps us be more flexible and agile. We don&amp;rsquo;t have these weekly planning meetings or anything like that. We just chat in the chat room. And I try to keep it very informal like that because I think that that&amp;rsquo;s definitely what attracts some people to work on the project. They like that kind of level of formality. But I imagine some people might prefer more structure. I don&amp;rsquo;t know, I&amp;rsquo;m not one of those people.&lt;br&gt;
&lt;br&gt;
&lt;strong&gt;SimSec: Is it the first time that you&amp;rsquo;ve got a fund from OTF? What has the process been like for you?&lt;/strong&gt;&lt;br&gt;
&lt;br&gt;
&lt;strong&gt;MW:&lt;/strong&gt; Yeah, it is. It&amp;rsquo;s my first experience doing something like this. The other funding that Snikket got has always been about development work and more technical stuff. And so actually having the freedom to spend some time looking at UX and usability issues has been much fun and very liberating. It&amp;rsquo;s always good to have some people that actually know what they&amp;rsquo;re doing. Because it&amp;rsquo;s one thing to start a project that&amp;rsquo;s designed to make messaging really easy, I don&amp;rsquo;t have a background in UX or UI design. It&amp;rsquo;s great to be able to have other people who have this knowledge helping out. That&amp;rsquo;s been really, really helpful to the project. The feedback from the usability testing, for example, has been really helpful in helping pin down some design decisions and things like that. So yeah, it&amp;rsquo;s been great.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“The goal is not necessarily to become as big as WhatsApp or any of the other massive, proprietary platforms.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;SimSec: Thank you very much. We&amp;rsquo;re all quite fascinated as well seeing the screenshots of the before and after when all testing feedback is taken into consideration and how quickly things got implemented!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MW:&lt;/strong&gt; Yes, it&amp;rsquo;s been really good for me as well. Seeing those screenshots will be interesting sometimes. Because sometimes I&amp;rsquo;m so immersed in it, I can&amp;rsquo;t see the wood for the trees, as we say. So occasionally, I see a screenshot of what the app used to look like. And I can&amp;rsquo;t believe how far we&amp;rsquo;ve come in just a short amount of time. So yes, it&amp;rsquo;s been really good and we have got a lot of positive feedback from users as well!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec: What does the success of Snikket look like to you?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;MW:&lt;/strong&gt; Being decentralised, the goal is not necessarily to become as big as WhatsApp or any of the other massive, proprietary platforms. The goal is just to encourage people to move to open and decentralized networks so that success will be the average person recognising that you don&amp;rsquo;t have to be on the same provider as someone else to chat with them. And just like email, you can just share your chat address. And it doesn&amp;rsquo;t matter which app you&amp;rsquo;re using, you can still message anyone else and that&amp;rsquo;s the overall goal. But I think Snikket is how we get there. I mean, anything that makes it more easy and accessible is the beginning step. And, and I&amp;rsquo;m really looking forward to that.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Get in touch with Matthew Wild and learn more about his work &lt;a href=&#34;https://floss.social/@mattj&#34;&gt;here&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;See Snikket’s most recent updates &lt;a href=&#34;https://snikket.org/blog/&#34;&gt;here&lt;/a&gt; and &lt;a href=&#34;https://github.com/snikket-im&#34;&gt;here&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits &lt;/h2&gt;
&lt;p&gt;Project Contributors: Ngọc Triệu, Ame Elliott, Rae McKelvey, Snikket  &lt;/p&gt;
&lt;p&gt;&lt;br&gt;
With support from &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;The Open Technology Fund Usability Lab&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Making the Mindset Shift: An Interview with Digital Democracy Lead UX Designer, Sabella Flagg</title>
      <link>https://superbloom.design/learning/blog/making-the-mindset-shift-an-interview-with-digital-democracy-lead-ux-designer-sabella-flagg/</link>
      <pubDate>Fri, 03 Dec 2021 17:47:20 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/making-the-mindset-shift-an-interview-with-digital-democracy-lead-ux-designer-sabella-flagg/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/making-the-mindset-shift_hu_2e3de61b352f9c86.png&#34; width=&#34;740&#34; height=&#34;494&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.digital-democracy.org/mapeo/&#34;&gt;Mapeo&lt;/a&gt; - an application by &lt;a href=&#34;https://www.digital-democracy.org/&#34;&gt;Digital Democracy&lt;/a&gt; - enables indigenous communities across the world to document and map all kinds of useful data – from essential resources on their lands to environmental and human rights violations. &lt;/li&gt;
&lt;li&gt;Through the &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;OTF Usability Lab&lt;/a&gt;, we worked with Digital Democracy to examine how to approach design work in challenging circumstances (such as a global pandemic) and support them with customized tools and resources.&lt;/li&gt;
&lt;li&gt;We interviewed Sabella Flagg, Lead of UX Design for Digital Democracy, who we coached and collaborated with on this project. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Through the &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;OTF Usability Lab&lt;/a&gt;, we were fortunate enough to work with &lt;a href=&#34;https://www.digital-democracy.org/&#34;&gt;Digital Democracy&lt;/a&gt; (Dd) on &lt;a href=&#34;https://www.digital-democracy.org/mapeo/&#34;&gt;Mapeo&lt;/a&gt;. Mapeo is a mobile app that enables indigenous communities across the world to document and map all kinds of useful data – from essential resources on their lands to environmental and human rights violations. &lt;/p&gt;
&lt;p&gt;Together, we tackled a range of design challenges and learned a lot along the way. We examined how to approach design work when there’s little or no opportunity for user research (due to, say, being in a global pandemic), and developed a tool that enabled the Dd team to walk through scenarios and surface internal knowledge in order to make informed design decisions. We also developed a resource that explored best practices around recovery keys for low-tech users, and strategies to protect people and data against mobile device seizure. Both of those challenges involved connecting with the &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;Human Rights Centered Design (HRDC)&lt;/a&gt; community and our &lt;a href=&#34;https://simplysecure.org/contact/&#34;&gt;Slack network&lt;/a&gt; of human rights defenders that work in security and design. It was an excellent lesson in uplifting the work of others in our ecosystem who have tackled similar challenges, and we were able to present the Dd team with workable, tested solutions and examples that could work well for Mapeo in different contexts (keep an eye on our resource library for these tools!) &lt;/p&gt;
&lt;p&gt;We also did one-on-one coaching sessions with Dd’s Lead UX Designer Sabella Flagg, which was a wonderful opportunity to learn from and collaborate with a fellow designer working in the internet freedom space. We interviewed Sabella to learn more about her journey, her work, and her experience collaborating with Simply Secure.  &lt;/p&gt;
&lt;p&gt;&lt;br&gt;
This interview was edited for length and clarity. &lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;strong&gt;Simply Secure (SimSec): How has the Usability Lab and your experience working with Simply Secure impacted your work on Mapeo?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sabella Flagg&lt;/strong&gt; &lt;strong&gt;(SF)&lt;/strong&gt;: Coming to Dd meant designing for new audiences that I hadn’t had a lot of exposure to in other parts of my career and so naturally there’s a little bit of uncertainty and learning that comes with that. The one on one coaching sessions with Simply Secure were incredibly useful to have a set of experts to review and double check my work to make sure that I wasn’t introducing harm with any of the concepts I generated and to learn from.&lt;/p&gt;
&lt;p&gt;Also with the world on lockdown it meant I would be unable to lean on our programs team, who would normally be in the field throughout a year, for user feedback and insights. Having Usability Lab and Simply Secure on board felt like having more touch-points for feedback, and from others who worked with similar audiences. When the world opens back up we feel prepared thanks to the interview and workshop guides Simply Secure provided. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec: What resources, tools, and/or experiences from our coaching do you plan to return to going forward?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I am also new to designing for decentralized tech so when SimSec shared &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentpatterns.xyz&lt;/a&gt; it was a resource I immediately saved in my bookmarks. Definitely a super useful asset I know I will return to time and time again. It was great to have a library that I could reference and learn from separately and bring things back to the team that I found compelling and interesting.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec: Could you tell us a little bit about your journey? What did you do before joining Digital Democracy and what motivated you to join the team?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SF:&lt;/strong&gt; Previous to joining Digital Democracy, I&amp;rsquo;d spent most of my career working at innovation consultancies – the small shops that are idea generators behind big corporations. So I got to work on some pretty cool and fun projects, and I definitely learned a lot. That&amp;rsquo;s where I learned about what a UX researcher is and how to work with one. I kind of rotated through different industries throughout the year, so I got exposed to a lot of different things. The last consultancy that I worked with, and what drew me to them and drew me out here to Seattle, had a goal of increasing their social good and nonprofit work, and I was like, “That is what I want to be doing. I&amp;rsquo;m on board.”&lt;/p&gt;
&lt;p&gt;They didn&amp;rsquo;t meet that goal, and at some point, I got burned out of a project that was kind of notorious for burning people out of the agency, and I left to take a sabbatical where I used art therapy to heal from burnout. I restarted my art practice, which kind of fell away after I left college, and then moved into doing freelance design work. And specifically, I was trying to find work in the social good space. It’s rare to find an organization that needs design, and has the funds for a designer. Also being in Seattle, it&amp;rsquo;s very easy to fall back into Big Tech. So it&amp;rsquo;s like, every time my contract ends, like a fight, it&amp;rsquo;s like alright, I have this much time to see if I can find another job. Luckily, my time with Dd keeps getting extended. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec: A lot of that sounds familiar; social good orgs not having the space or funding for designers. Since you’re working directly on a product that human rights defenders on the ground are using, can you tell us how you think design helps human rights defenders do their work?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SF:&lt;/strong&gt; It definitely feels like important work. I&amp;rsquo;ve definitely been on projects [in the corporate world] where I&amp;rsquo;m just like, this quite literally does not matter. Like, is this organization really paying hundreds of thousands of dollars to make people click this button more? I cannot believe it. And so when you move from a place of excess and commercial needs and wants, to one where it&amp;rsquo;s like, your audience is asking for this because if they don&amp;rsquo;t get it, they will literally die. It definitely adds a different sort of weight to the work that you end up doing. &lt;/p&gt;
&lt;p&gt;And, I mean, even that work that “doesn&amp;rsquo;t matter,” I still approach it with the same thoughtfulness and care because this is my career that I&amp;rsquo;ve chosen to do and I like doing design and I think this is important and even on those projects. But the sense that the work will actually help someone progress something that is actually important adds a bit more weight to the decisions that get made. I definitely dealt with getting stuck on decisions when I first joined because it&amp;rsquo;s a completely new space for me to be designing in and a different audience. And again, with the pandemic not being able to ask the person who&amp;rsquo;s in the field, “now can you check and see if this color combination we&amp;rsquo;re using is accessible?” It felt scary working through that, and finding ways to organize the decisions that you do make and knowing that you will get partner feedback – it may take a bit longer because of the way the world is right now, but you will get that feedback. Making your way through the gigantic list of requests is a daunting task, but when you finish one feature, it&amp;rsquo;s a good feeling.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec:  Coming from a commercial space, I’m wondering what you’ve had to learn and unlearn about how you practice design and design thinking entering the “humanitarian” sphere? Do you have any challenges from the transitions that you would like to share?&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SF:&lt;/strong&gt; Yeah, definitely. Oh, before Dd, I was on a project that dealt with organizing data for the general populace. And on that project, I learned so much about how we as designers can show bias when we design graphs that just have data. So you show two graphs, both of them have the exact same data, one of them is biased, because the design is different. And that blew my mind! &lt;/p&gt;
&lt;p&gt;Coming to Dd, I had the exact same experience in looking at some of the patterns that I kind of take for granted, or I think of as very general stock patterns that users are expected to know and to learn. All of that was Western learning and for a Western audience. &lt;/p&gt;
&lt;p&gt;So you know, my first couple of meetings with [Gregor on the tech team], we were gonna have a date picker. I was like, “oh yeah, here&amp;rsquo;s all these stock react date pickers, we could use something cool like this&amp;hellip;” And Gregor told me more about the human factor around the ask, and he mentioned a lot of our users don&amp;rsquo;t just do remote mapping for this project. That&amp;rsquo;s not their job. It&amp;rsquo;s something that they volunteered to do because it&amp;rsquo;s something that’s important to them. They&amp;rsquo;re working in the fields. They&amp;rsquo;re farmers. They do manual labor. They will build up calluses on their hands. So I&amp;rsquo;m looking at these date pickers I&amp;rsquo;m like, oh, yeah, these are standard touch targets, like 40 pixels by 40 on mobile, like that&amp;rsquo;s totally fine. And Gregor tells me: “I have seen users struggle to tap things on their phone, because of the calluses that build up on their hands.” And all these little date pickers I have the little tiny numbers and arrows, more than half of these are unusable in their current state. So that was my first example of something like that. &lt;/p&gt;
&lt;p&gt;So me coming in with Western solutions and then learning about the specific needs of our audience and then adjusting from there. So now I go through this process of: “okay, they asked for my design solution, the first thing that I thought of is…” and inspecting, “is this a very Western solution that does not translate well, for an audience that is potentially has low tech literacy, which is also an audience that I&amp;rsquo;m very new for designing for, that has low access to consistent Wi Fi, that may be in a super remote area?” Often, [none of the solutions] match, you know, the audience that I run into when I walk outside. There&amp;rsquo;s definitely inspection of every idea to make sure that I am meeting the design principles that I need for our users. &lt;/p&gt;
&lt;p&gt;Another thing that helps is to think about solutions in terms of generalized human behavior. Sometimes we start new projects and I spent two weeks just doing research. And I think: “Okay, is this the finding of this research because of the audience? Or is it because of human behavior?” And if it&amp;rsquo;s because of human behavior, then that helps make the solution be more generalized, right? So even if you&amp;rsquo;re dealing with someone who has medium literacy with tech, which means like, they have WhatsApp, they have Facebook and Instagram – you can glean from the apps that they use what human interactions they are comfortable with. And those sometimes match how we use them the Western Hemisphere, or they might be using them in unique ways because of their specific situation. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec: What&amp;rsquo;s on the horizon for you? Anything that you&amp;rsquo;re looking forward to either in life or in your work?&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SF:&lt;/strong&gt; In life, I just got into my first artist residency, which will be happening next year, in early spring. So I&amp;rsquo;m super, super excited about that. I&amp;rsquo;m going to be in remote Washington on the coast. I told everyone, “Okay, 2022, I&amp;rsquo;m going to try and be less afraid and more proactive.” So I have and that happened – I mean, that feels really good. &lt;/p&gt;
&lt;p&gt;And in terms of work, the first program team members are going out in the field, and it&amp;rsquo;s really increased my desire to create a centralized location for Dd for partner feedback. They do an amazing job of recounting their experiences and the things that they&amp;rsquo;ve seen, but I really want to get that into a place where that information lives out of their heads so that they spend less time having to tell it to the next new person that comes. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SimSec: To sum up, do you have any advice or suggestions for designers who also want to move from the formal design industry to work in nonprofits, civil society, or design for good?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SF:&lt;/strong&gt; The main difference with working in this industry is that when you go on job boards, there aren&amp;rsquo;t a plethora of them to look at. Versus like any tech industry job role, you know, I go on LinkedIn, and there&amp;rsquo;s 1000 of them. &lt;/p&gt;
&lt;p&gt;What helps me is to read job descriptions to get the full expanse of what is available in the industry. So other industries have quantity, and nonprofit space does not. So that means if you&amp;rsquo;re not in the nonprofit space now, but you want to be, you should be looking at design for good job boards, social good designers Facebook groups, and things like that – you should be joining those now. So whenever job postings do come up, you start building that idea of what is actually available, because by the time you are ready to make your move from one job to another, it&amp;rsquo;s likely there&amp;rsquo;s going to be like three design jobs available. But just being aware that there are not always a lot of opportunities in this space, and so building a catalogue of what is usually asked for, and also being prepared to be in a startup mentality, in terms of the number of hats you have to wear, but without the startup stock options, like wrap your head around that before you join. It doesn&amp;rsquo;t mean that you should start doing things that you don&amp;rsquo;t want to do, but make sure that you are clear on the value that your skills bring. &lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;em&gt;You can find Sabella’s art on Instagram ​​@themonarq or at &lt;a href=&#34;https://themonarq.com&#34;&gt;https://themonarq.com&lt;/a&gt; &amp;amp; learn about her design work at &lt;a href=&#34;https://www.sabella.is/&#34;&gt;https://www.sabella.is/&lt;/a&gt;&lt;/em&gt; &lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Contributors: Ngọc Triệu, Ame Elliott, Katie Wilson, Digital Democracy&lt;/p&gt;
&lt;p&gt;With support from the &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;OTF Usability Lab&lt;/a&gt;. &lt;/p&gt;
&lt;h2 id=&#34;tags&#34;&gt;Tags&lt;/h2&gt;
&lt;p&gt;UX, Community&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Sustaining Values-Driven Software by Attracting New Users</title>
      <link>https://superbloom.design/learning/blog/sustaining-values-driven-software-by-attracting-new-users/</link>
      <pubDate>Tue, 30 Nov 2021 19:25:49 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/sustaining-values-driven-software-by-attracting-new-users/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/sustaining_values_driven_software_image_1_hu_56528cd4d3d05bc6.jpg&#34; width=&#34;740&#34; height=&#34;494&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;We helped website security service &lt;a href=&#34;https://equalit.ie/portfolio/deflect/&#34;&gt;Deflect&lt;/a&gt; appeal to a larger user base by identifying ways to attract and maintain both human rights organizations and businesses as customers.&lt;/li&gt;
&lt;li&gt;As part of the &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Open Technology Fund Usability&lt;/a&gt; Lab, we used a UX design-driven approach to understand and communicate the benefits of Deflect by deploying an expert review, facilitating a workshop on positioning and value, and testing users. &lt;/li&gt;
&lt;li&gt;The UX design research we completed clarified ways Deflect can attract more paying customers to sustain their work, which models the way Internet Freedom work can be resilient in our economy.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For many organizations, their website is not just an external communication channel, their website is their critical product. This is particularly true for advocacy, human rights, and journalism organizations where their website is their platform on which they organize for their cause and share their work on critical human rights issues. eQualit.ie’s &lt;a href=&#34;https://deflect.ca/&#34;&gt;Deflect&lt;/a&gt; is an example of a website security service that protects websites from the dangerous cyber attacks that would silence voices, restrict communication, and limit organizing.&lt;/p&gt;
&lt;p&gt;The below statement explains how Deflect kept the &lt;a href=&#34;https://blacklivesmatter.com/&#34;&gt;Black Lives Matter&lt;/a&gt; website up during a 2016 cyber attack following the unprovoked killings of Philando Castile in St Paul, Minnesota, and Alton Sterling in Baton Rouge, Louisiana by police:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;“Distributed Denial of Service (DDOS) attacks like this one use a network of computers to simultaneously attempt massive amounts of connections to a website – too many for the site to handle. As a result, the site becomes unavailable. In this case, the Black Lives Matter website was hit with a spectacular number of connections in one day (over 15 million, with an attack network of over 12,000 bots). Most commercial providers immediately shut down websites under this type of attack choosing to give in to attackers to protect the rest of their customers. That has never been May First/People Link’s policy. The attack has been countered and successfully contained using Deflect, and the BLM website has been functional and accessible for much of the weekend.” – &lt;a href=&#34;https://www.apc.org/en/pubs/statement-recent-attacks-black-lives-matters-websi&#34;&gt;Association for Progressive Communications Press Release&lt;/a&gt;, July 12, 2016.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Financial sustainability is the key for digital infrastructure like Deflect to continue providing protection to critical human rights websites. How can Deflect continue to meet the challenge of providing their tried-and-tested website protection and support for free to organizations that are unable to pay for it? Thanks to the Open Tech Fund’s &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Usability Lab&lt;/a&gt;, we had a chance to work with Deflect on their user experience onboarding – a key moment that connects to a product’s business model.&lt;/p&gt;
&lt;h2 id=&#34;no-business-as-usual-the-challenges-of-sustainable-internet-freedom-organizations&#34;&gt;No Business As Usual: The Challenges of Sustainable Internet Freedom Organizations&lt;/h2&gt;
&lt;p&gt;Just as our previous work for Tails described in &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails/&#34;&gt;Open source &amp;amp; branding – a contradiction?&lt;/a&gt; clarifies how concepts from branding can benefit open source projects without succumbing to the manipulative advertising, this project gave the team a chance to explore how to keep more human rights organizations protected by getting paid customers in Deflect. While “business models” typically evoke the extractive profit-driven approach of Silicon Valley’s “Big Businesses,” not all business models are about profit at all costs. Every organization needs to have a framework for sustaining their operations — e.g. paying staff to work, paying for resources such as server space needed to provide the service or product, etc. Relying on uncompensated volunteers for work and profits from t-shirt sales to buy things is one way to run an organization, but the urgent threats to human-rights defenders requires more effort and experimentation in models of sustainability.&lt;/p&gt;
&lt;p&gt;In the Internet Freedom ecosystem, just as in other contexts, the key is to consider diverse mechanisms of financial sustainability and resilience. By not relying on one source of income too heavily, organizations can become more resilient. We consider “organizations” in a broad sense – including for-profit, social good, non-profit, cooperatively owned, and volunteer groups all under this umbrella. So yes, volunteer contributions and t-shirt sales have a place in the Internet Freedom community, but they are not enough to power financial sustainability.&lt;/p&gt;
&lt;p&gt;Many Internet Freedom projects are supported by grants, for example from the &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Tech Fund&lt;/a&gt; who supported this project. However many organizations rely on funding sources other than grants and donations e.g. selling services or software. An organization can offer security audits, consulting services, and software subscriptions to bring in income. Then with that income they can pay for equipment, hosting services, office space, salaries, and other things they need to fulfill their mission – even if part of their mission is providing no-cost or low-cost Internet Freedom software.&lt;/p&gt;
&lt;p&gt;Deflect is an ideal case for exploring financial sustainability in the Internet Freedom community because eQualitie, the organization that created it, has proven that it has staying power while closely adhering to &lt;a href=&#34;https://equalit.ie/values/&#34;&gt;their values&lt;/a&gt;. Deflect is guided by a &lt;a href=&#34;https://deflect.ca/principles/&#34;&gt;Declaration for Distributed Online Services&lt;/a&gt;, proudly proclaiming:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;“Put your clients before profits or funding. Be clear about commercial intention and services provided under free accounts. Give clients viable alternatives before terminating or changing their service.” – Deflect’s &lt;a href=&#34;https://deflect.ca/principles/&#34;&gt;Principles&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Over its ten-year history Deflect has had opportunities to experiment with different pricing models. Variable pricing models, such as pay-what-you-like, buy-one-get-one, or sliding-scale prices are an area ripe for experimentation in the Internet Freedom community, and our project started by building on Deflect’s practice of offering a fully-functional free version to qualified organizations who asked. &lt;/p&gt;
&lt;p&gt;Our challenge was to balance Deflect’s product-before-profit mindset with opportunities to attract more paying customers in order to sustain Deflect for the benefit of high-risk targets unable to pay for it.&lt;/p&gt;
&lt;h2 id=&#34;understanding-the-value-of-deflect-with-user-research&#34;&gt;Understanding the Value of Deflect with User Research&lt;/h2&gt;
&lt;p&gt;We used a UX design-driven approach to understand and communicate the benefits of Deflect and deployed multiple methods, including: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Expert reviews by four different designers/developers of existing and proposed interfaces for&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Onboarding&lt;/li&gt;
&lt;li&gt;Account management/dashboard&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Facilitated workshop with the Deflect team on positioning and value&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;User testing with five potential new users of Deflect&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Think aloud protocols of the existing &lt;a href=&#34;https://deflect.ca/&#34;&gt;Deflect.ca&lt;/a&gt; website&lt;/li&gt;
&lt;li&gt;Reacting to proposed value statements&lt;/li&gt;
&lt;li&gt;Understanding IT purchasing decisions in their organization&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These multiple methods led us to three findings:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Deflect’s services are easily understood and seen as valuable.&lt;/li&gt;
&lt;li&gt;There’s a design opportunity for Deflect to be more transparent about the team, funding, and stability.&lt;/li&gt;
&lt;li&gt;Different customer types vary in how important pricing is to their decision-making process.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;deflects-services-are-easily-understood-and-seen-as-valuable&#34;&gt;Deflect’s services are easily understood and seen as valuable. &lt;/h3&gt;
&lt;p&gt;Demonstrated by its staying power, Deflect gets many things right. The &lt;a href=&#34;https://deflect.ca/&#34;&gt;Deflect.ca&lt;/a&gt; website is visually appealing and effective at making people want Deflect. During our think-aloud sessions, people understood at a glance what a product named Deflect with a website showing a heroine with arrows bouncing off her shield was supposed to do. Even less-technical people unsure about the exact threats of cyber attacks found Deflect desirable and compelling.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/sustaining_values_driven_software_image_2_hu_54f18f8b63abd520.png&#34; width=&#34;740&#34; height=&#34;348&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Paradoxically the perceived value and high quality of Deflect made some non-profit insiders skeptical. They questioned that if the product is this great, how can they give it away for free? &lt;/p&gt;
&lt;h3 id=&#34;theres-a-design-opportunity-for-deflect-to-be-more-transparent-about-the-team-funding-and-stability&#34;&gt;There’s a design opportunity for Deflect to be more transparent about the team, funding, and stability.&lt;/h3&gt;
&lt;p&gt;One way to reassure people skeptical that Deflect can be both desirable and affordable is by sharing more behind-the-scenes information on the website. Potential new users want to know more about the team and the stories motivating the software. Feeling connected to the team and mission will give people confidence that Deflect is stable, and able to live up to its promises.&lt;/p&gt;
&lt;p&gt;The website already contains many of the most important pieces of information, such as the promise not to discontinue free accounts without viable alternatives, but consolidating and highlighting statements about funding and stability will make more people more-willing to try something new. New users need to overcome skepticism that goes beyond Deflect or eQualitie and to the non-profit ecosystem as a whole. In the words of one of our interviewees, the reality of technology for human rights defenders is that budgets are stretched, and “There’s just never going to be enough money for all of us to do our work.”&lt;/p&gt;
&lt;p&gt;Deflect has a long history and impressive track record, but additional information addressing some of the awkward truths of financial sustainability will give people confidence that Deflect is not going anywhere, important information for their purchasing decision.&lt;/p&gt;
&lt;h3 id=&#34;different-customer-types-vary-in-how-important-pricing-is-to-their-decision-making-process&#34;&gt;Different customer types vary in how important pricing is to their decision-making process.&lt;/h3&gt;
&lt;p&gt;When we asked interviewees looking at the Deflect website how much they expected to pay for Deflect, the range was huge: from $5 - $5,000 a month. One of the more provocative comments compared the price of Deflect to email marketing tool MailChimp, which they referred to as a “necessary evil” to keep nonprofit organizations running.&lt;/p&gt;
&lt;p&gt;When digging deeper into the perceived value and acceptable price for Deflect, we heard a range of views about how important pricing is. Some people are strongly motivated by price and an aggressive approach to spending as little money as possible. Convincing those people to purchase Deflect will be difficult, and as long as there is a no-cost alternative. But we also identified two other groups who are not driven primarily by price.&lt;/p&gt;
&lt;h2 id=&#34;purchase-decision-making-personas-one-size-does-not-fit-all&#34;&gt;Purchase Decision-making Personas: One-size Does Not Fit All&lt;/h2&gt;
&lt;p&gt;We contextualized the range of attitudes we heard about purchasing into three personas, or types of users. Each personas has different motivations for making a purchase, but committed self-hosters and non-profit IT administrators are both promising new customers for Deflect.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/sustaining_values_driven_software_image_3_hu_b737b4b4bd48d56d.jpg&#34; width=&#34;740&#34; height=&#34;366&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Price-Conscious Tinkerers.&lt;/strong&gt;&lt;br&gt;
The toughest group to attract. Interested in the technology underlying Deflect, they care about the details and are motivated by functionality. Always working to get the most for their money, they take pride in having everything up to date and in order. Strongly technical and planning to roll up their sleeves and work, performance and price are both important, but it is hard to get this group to pay for anything.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Committed Self-Hosters.&lt;/strong&gt;&lt;br&gt;
A natural fit for Deflect. Driven by values, this group will vote with their wallets to fund projects they believe in. Although they may not face particular DDoS risks, they take pride in feeling part of a movement. Solo or in an informal group of like-minded people, a self-hoster can decide to use Deflect on an impulse. Patient with technical difficulties and keen to build their own tech skills, they could become brand evangelists, and would be proud of Deflect stickers or swag. Knowing their contributions directly support a team doing important work, $10 - $15/month is uncontroversial, but they can be convinced to upgrade to more expensive options.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Non-Profit IT Administrators.&lt;/strong&gt;&lt;br&gt;
Their values motivate them to stay in the sector despite opportunities to earn more elsewhere, but these IT professionals are business- minded. They have many competing demands and need more time in the day to get everything done. Maintaining a vulnerable website is one of many challenges, and their time is valuable. Low cost is appealing because they answer to others and need to justify their decisions, but this purchase is a business decision, not their own money. Benchmarking a price for the service and then offsetting it with a nonprofit credit will appeal to them, but if in the future the non-profit credit offset ends, they may be too busy to re-apply since their attention may be on a more urgent problem.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These purchasing personas are broadly applicable to the Internet Freedom community and are relevant to projects other than Deflect. Committed self-hosters making an active attempt to support organizations they believe are alternatives to Big Tech are an important part of the Internet Freedom community, and their combined purchasing power offers an exciting glimpse into models of economic solidarity. Exploring collaborative and collective solutions, starting with monthly software purchases but potentially extending into membership or cooperative models are a promising area for future research. Their passion speaks for itself:  &lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;“​​I spend more time, pay more money, and get less service to support the organizations I want to support.“ – a committed self-hoster we interviewed&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;In contrast to the individual passion of committed self-hosters, IT professionals at nonprofits are skilled at balancing competing demands on their time, attention, and money. They bring a professional detachment to decisions, but also need to justify their expenditures to others. Under-resourced and stretched-too-thin IT administrators at nonprofits may be too busy to experiment with complicated new tools, but making it easy for them to purchase Internet Freedom tools has a powerful multiplier effect. Their decisions can protect the people and infrastructure of their organizations, and respecting the role that organizations play in the Internet Freedom ecosystem can expand the benefits of a free and open internet to more people.&lt;/p&gt;
&lt;h2 id=&#34;financially-stable-organizations-protect-more-people&#34;&gt;Financially Stable Organizations Protect More People&lt;/h2&gt;
&lt;p&gt;Financial sustainability is the key for organizations like Deflect to continue providing protection to critical human rights websites, and including paid customers as part of their business model will enable them to continue to provide support to those who need it and aren’t able to pay. Deflect’s website already showcases their principles and explains their product, but the UX design research we completed  clarified ways they can attract more paying customers to sustain their work.&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Contributors: Ame Elliott, Georgia Bullen, Cade Diem, K. Rae McKelvey&lt;/p&gt;
&lt;p&gt;Preview image: &lt;a href=&#34;https://unsplash.com/@stri_khedonia&#34;&gt;Image by Alice Pasqual via Unsplash&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;With support from the &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Open Technology Fund&lt;/a&gt; Usability Lab.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Dark Patterns in User Controls: Exploring YouTube’s Recommendation Settings</title>
      <link>https://superbloom.design/learning/blog/dark-patterns-in-user-controls-exploring-youtubes-recommendation-settings/</link>
      <pubDate>Tue, 30 Nov 2021 13:37:52 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/dark-patterns-in-user-controls-exploring-youtubes-recommendation-settings/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dark-patterns-in-user-controls-1_hu_5d1cbd80bb8803a6.png&#34; width=&#34;740&#34; height=&#34;370&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;YouTube &lt;a href=&#34;https://www.buzzfeednews.com/article/richardnieva/youtube-will-hide-dislike-counts-on-videos-to-combat&#34;&gt;will now hide&lt;/a&gt; the downvote count on videos to mitigate harassment — but it’s still unclear what choices users have to control the content they are recommended. &lt;/li&gt;
&lt;li&gt;In collaboration with &lt;a href=&#34;https://foundation.mozilla.org/en/research/library/youtube-regrets-findings/&#34;&gt;Mozilla’s YouTube Regrets project&lt;/a&gt;, Simply Secure mapped and analyzed YouTube’s controls from a usability standpoint to understand if the design supported user experience principles of control, freedom, and transparency.&lt;/li&gt;
&lt;li&gt;Many opportunities for user control are actually masked dark patterns. We must recognize that a lot of the designs users interact with are coming from business interest, and not from the perspective of user care.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Today’s conversation about YouTube is largely centered on engagement. YouTube is one of the original user-generated content platforms that has become everyday infrastructure for web-based video. Platforms that enable users to post and share content present as democratic spaces, enabling users to converse, engage, and see how others react to content, but the design of the platforms themselves impact how these exchanges happen. There’s an assumption that when videos are up-voted, they are shared more widely, and when content is downvoted it’s hidden from public view. In reality, YouTube counts all engagement equally — since their &lt;a href=&#34;https://support.google.com/youtube/answer/2991785?hl=en&#34;&gt;business mode&lt;/a&gt;l is driven by user engagement, the type of engagement doesn’t matter. (To combat the weaponization of the downvote button, YouTube has now &lt;a href=&#34;https://www.buzzfeednews.com/article/richardnieva/youtube-will-hide-dislike-counts-on-videos-to-combat&#34;&gt;hidden the downvote count&lt;/a&gt;, although the functionality remains.) &lt;/p&gt;
&lt;p&gt;When companies make their money through engagement or time spent on their platforms, they are incentivized to employ deceiving design patterns, usually referred to as &lt;a href=&#34;https://www.darkpatterns.org/&#34;&gt;Dark Patterns&lt;/a&gt;, or at the very least, not invest in usable controls.&lt;/p&gt;
&lt;p&gt;It’s not always clear how recommendation engines on sites like YouTube and Instagram choose the content that gets promoted. It’s even less clear if users can do anything to control which types of content are recommended. As reported in Mozilla’s &lt;a href=&#34;https://foundation.mozilla.org/en/research/library/youtube-regrets-findings/&#34;&gt;YouTube Regrets&lt;/a&gt; project, the platform makes it difficult for users to maintain control over content recommendations. In reading over thirty thousand stories from users, Mozilla found that it was unclear if YouTube even acted on their requests to remove undesirable or offensive content. &lt;/p&gt;
&lt;p&gt;This begs the question — what control do YouTube users have? What is the user experience of YouTube’s controls for feedback on content? In collaboration with &lt;a href=&#34;https://foundation.mozilla.org/en/research/library/youtube-regrets-findings/&#34;&gt;Mozilla’s YouTube Regrets&lt;/a&gt; project, we took a deep dive into YouTube’s user controls to analyze how they support user choice — the result was a disappointing but unsurprising maze of loops, deadends, and never-ending paths.  &lt;/p&gt;
&lt;h2 id=&#34;a-bridge-to-nowhere-mapping-youtube-controls-2020&#34;&gt;A Bridge to Nowhere: Mapping YouTube Controls (2020)&lt;/h2&gt;
&lt;p&gt;To understand the recommendation algorithm controls, we created a new YouTube account and mapped the possible paths and options that a user could take to customize their experience. We found that:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;“Settings” don’t actually mean anything — there’s nothing you can control on the Settings page.&lt;/li&gt;
&lt;li&gt;Existing controls are reactive and not proactive, leaving users to catch-up to the recommendation engine rather than designing what they want to see.&lt;/li&gt;
&lt;li&gt;There are multiple ways to get to some pages. This can be helpful if the user doesn’t follow the &lt;a href=&#34;https://en.wikipedia.org/wiki/Happy_path&#34;&gt;happy path&lt;/a&gt;, but excessive use leads to confusion and frustration. &lt;/li&gt;
&lt;li&gt;Options to “teach” the algorithm are few and limited in scope.&lt;/li&gt;
&lt;li&gt;The words describing the outcome of each step are opaque. Various words are used to mean the same thing, and it’s unclear what comes next. &lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;false-settings&#34;&gt;False Settings&lt;/h2&gt;
&lt;p&gt;YouTube Settings claims to allow users to choose what they see on YouTube however, there are actually no such controls on any of the settings sections.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dark-patterns-in-user-controls-2_hu_25cbaf267fa86829.png&#34; alt=&#34;Settings: there aren’t actually controls for “what you see on YouTube”&#34; width=&#34;740&#34; height=&#34;415&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;^ Settings: there aren’t actually controls for “what you see on YouTube”&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;reactive-controls&#34;&gt;Reactive Controls&lt;/h2&gt;
&lt;p&gt;The controls on YouTube Home follow a linear path. Since the controls are next to a video or topic, the &lt;a href=&#34;https://www.nngroup.com/articles/gestalt-proximity/&#34;&gt;law of proximity&lt;/a&gt; helps the user understand that they apply to a video, section or channel and find them easily — this shows us the controls are meant to be seen and used. However, a user would already need to get recommended these videos in order to make adjustments, so these controls are reactive, not proactive. This means users cannot discover and design their experience, but rather must shape it depending on what YouTube shows them.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dark-patterns-in-user-controls-3_hu_6cfbce578103471a.png&#34; alt=&#34;Mapping the path of user control on the YouTube ‘Home’.&#34; width=&#34;740&#34; height=&#34;356&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;^ Mapping the path of user control on the YouTube ‘Home’.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;When the user wants to teach the algorithm that they are no longer interested in the video, there is the option to click on “not interested.” This is separate from ‘reporting’ harmful or offensive content.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dark-patterns-in-user-controls-4_hu_c60dc36bb60f1306.png&#34; width=&#34;740&#34; height=&#34;705&#34;&gt;
&lt;/p&gt;
&lt;p&gt;However, there are few options to explain why they wish to remove that content, which makes it difficult to properly teach the algorithm what further content a user may not want to see.&lt;/p&gt;
&lt;p&gt;When the user selects that they are ‘not interested’ in a video, Youtube will remove the video and give the user the option to ‘undo’ or ‘tell us why.’ When the user selects ‘tell us why,’ they get this box:&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dark-patterns-in-user-controls-5_hu_3c74beb25c5960e3.png&#34; alt=&#34;Home &amp;gt; Not interested [in a video] &amp;gt; Tell us why&#34; width=&#34;740&#34; height=&#34;623&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;^ Home &amp;gt; Not interested [in a video] &amp;gt; Tell us why&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Once the user makes their choice, the response is that YouTube will “tune” their recommendations. The language is unclear and doesn’t explain the outcome — what does it mean to “tune” recommendations?&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dark-patterns-in-user-controls-6_hu_b0d4fb426cdb13e2.png&#34; alt=&#34;Home &amp;gt; Not interested [in a topic]&#34; width=&#34;740&#34; height=&#34;161&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;^ Home &amp;gt; Not interested [in a topic]&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Other confirmation messages are clear and offer more information, which shows YouTube can provide clarity when they want to. This box appears when the user selects ‘Don’t recommend channel’:&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dark-patterns-in-user-controls-7_hu_585e1471e0e47e51.png&#34; alt=&#34;Home &amp;gt; Don’t recommend channel&#34; width=&#34;740&#34; height=&#34;435&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;^ Home &amp;gt; Don’t recommend channel&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In the few places like these, where a user can express their opinion about a YouTube video, the language is unclear and the expected outcomes are unknown. Do these choices make a difference? What is the algorithm really learning? Can the user trust that they won’t see content similar to what they’ve stated they don’t want to see? It creates a confusing experience, and begs the question, are some of these designs intentionally deceptive?&lt;/p&gt;
&lt;h2 id=&#34;a-labyrinth-of-buttons&#34;&gt;A Labyrinth of Buttons&lt;/h2&gt;
&lt;p&gt;An alternative path that a user might try is to review their Watch History or Search History — but when accessing the controls through these views, the paths become more convoluted. There are many pop-ups, each containing several links, and users must traverse multiple pages to find any guidance and documentation. Many of these pages are circular, leading us back to a page we’ve seen before, but not providing additional transparency or clarity to the user. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dark-patterns-in-user-controls-8_hu_16718b8655bd6cd8.png&#34; alt=&#34;Mapping YouTube Watch History and Search History controls&#34; width=&#34;740&#34; height=&#34;254&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;^ Mapping YouTube Watch History and Search History controls&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Many pages and pop-ups contain the same content with few differences:  &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dark-patterns-in-user-controls-9_hu_b4249a6d053d2c52.png&#34; alt=&#34;Pop-ups with similar content appear in different places&#34; width=&#34;740&#34; height=&#34;200&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;^ Pop-ups with similar content appear in different places&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Users follow a loop, without actually changing any settings. In this circular path, there are two pages with the name “YouTube History”.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dark-patterns-in-user-controls-10_hu_c31bf71d6b716d63.png&#34; alt=&#34;Going in circles with YouTube History&#34; width=&#34;740&#34; height=&#34;429&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;^ Going in circles with YouTube History&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The controls for Watch History and Search History both contain links for “My Activity,” yet these links direct users to different pages. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dark-patterns-in-user-controls-11_hu_6c9da322da592fc3.png&#34; alt=&#34;“My Activity” link goes to different pages&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;^ “My Activity” link goes to different pages&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;On the page for YouTube History, there are many paths to arrive at the same pop-up, and some links use different wording. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/dark-patterns-in-user-controls-12_hu_c55140730354866e.png&#34; alt=&#34;Many ways to get to “auto-delete option”&#34; width=&#34;740&#34; height=&#34;362&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;^ Many ways to get to “auto-delete option”&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The more steps and loops that users are asked to go through, the less likely that they will ever actually reach the final page. This labyrinth of buttons makes it clear that YouTube does not prioritize allowing users to control their experience through the Watch History and Search History, and appears to be designing these flows to dissuade users from these controls overall. &lt;/p&gt;
&lt;h2 id=&#34;designing-for-user-agency-a-balance-with-policy&#34;&gt;Designing for User Agency: A Balance with Policy&lt;/h2&gt;
&lt;p&gt;It’s unclear how often these controls are used, but we know that &lt;a href=&#34;https://foundation.mozilla.org/en/research/library/youtube-regrets-findings/&#34;&gt;at least 37,380 users tried&lt;/a&gt;. So while YouTube’s mission might be to “&lt;a href=&#34;https://www.youtube.com/howyoutubeworks/our-mission/&#34;&gt;give everyone a voice,&lt;/a&gt;” they are systematically excluding their users from having a voice in what they want to see. &lt;/p&gt;
&lt;p&gt;Dark patterns are designs that give people the perception of choice, while actually prioritizing and coercing users into the business goals of the tools they’re using. Because the business model is to drive engagement at any cost, we know that these choices are intentional design choices — a business decision to ignore user agency and transparency, even when it comes to harmful and offensive content. Here we’ve focused on the individual experience, but these controls are even more challenging for parents attempting to protect their children. These tactics show the power imbalance between YouTube and their users — but don’t forget that like all user-generated content platforms, without users, YouTube has nothing.&lt;/p&gt;
&lt;p&gt;The consequences of a lack of control — and poorly designed controls — are that harmful content goes unchecked and users have bad experiences while feeling a false sense of security and trust. Interventions into the industry’s use of dark patterns is at the heart of &lt;a href=&#34;https://freedomhouse.org/report/freedom-net/2021/global-drive-control-big-tech&#34;&gt;many policy conversations today,&lt;/a&gt; from GDPR in the EU and CCPA in California to the UK’s Online Harms bill and India’s Intermediary Guidelines and Digital Media Ethics Code. In addition to regulations and policies that are currently in discussion, companies can improve this situation by prioritizing increasing user agency and transparency in these interfaces. As the people using these platforms, we can demand these changes.&lt;/p&gt;
&lt;p&gt;Giving users control, freedom and transparency of how algorithms work may be in conflict with the business model for many platforms, like YouTube — though it doesn’t have to be. If platforms made it easier for users to find and “tune” recommendations, we would likely watch and engage more. &lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Contributors: Kelsey Smith, Georgia Bullen, Ame Elliott.&lt;/p&gt;
&lt;p&gt;With support from &lt;a href=&#34;https://www.reset.tech/&#34;&gt;Reset&lt;/a&gt;, in collaboration with the &lt;a href=&#34;https://www.mozilla.org&#34;&gt;Mozilla Advocacy team&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Bringing the Offline Online: Reviewing the Developer Experience of Awala</title>
      <link>https://superbloom.design/learning/blog/bringing-the-offline-online-reviewing-the-developer-experience-of-awala/</link>
      <pubDate>Mon, 08 Nov 2021 16:32:52 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/bringing-the-offline-online-reviewing-the-developer-experience-of-awala/</guid>
      <description>&lt;ul&gt;
&lt;li&gt;Awala is a new computer network where compatible apps can use the internet when it’s available, and can switch to a secure offline network when it’s not. &lt;/li&gt;
&lt;li&gt;As part of the &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;OTF Usability Lab&lt;/a&gt;, we conducted a UX assessment of Awala apps used by end users and couriers, reviewed the app developer experience and provided UX/UI recommendations to better support developers building apps on Awala.&lt;/li&gt;
&lt;li&gt;Here, we dig into our developer experience review of Awala - which centered around trustworthy experiences, documentation, and suitable use cases. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Internet blackouts are disconcertingly common around the world. Whether due to government censorship, poverty, or geographic limitations, &lt;a href=&#34;https://ourworldindata.org/internet&#34;&gt;billions of people&lt;/a&gt; around the globe do not have reliable access to the internet. As the modern economy and global communication channels exist more and more online, there is a growing divide among those with and without access to high-quality, stable internet. And in cases of government censorship, many cannot share their lived experiences with the broader world. But more infrastructure and better politics won’t solve the challenges alone.&lt;/p&gt;
&lt;p&gt;Awala is a new computer network where compatible apps can use the internet when it’s available, and can switch to a secure offline network when it’s not. This network bridges the world wide web with regions where internet access is highly unreliable or unavailable altogether. Through the &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;OTF Usability Lab&lt;/a&gt;, Awala reached out to Simply Secure to review their user interface for developers and find ways to improve support for developers who are looking to build apps for Awala. &lt;/p&gt;
&lt;p&gt;Currently, as Awala is a new protocol, there are no public-facing apps that are compatible. Good news though - Awala &lt;a href=&#34;https://awala.network/blog/lowering-adoption-barrier&#34;&gt;recently started another contract from OTF&lt;/a&gt;. This new contract will support third-party app developers and users to onboard Awala - as well as to support the development of Letro, a new encrypted messaging app meant to work offline thanks to Awala.&lt;/p&gt;
&lt;p&gt;Below, we share a bit about our methodology and recommendations.&lt;/p&gt;
&lt;h2 id=&#34;what-is-awala-and-how-does-it-work&#34;&gt;What is Awala and how does it Work?&lt;/h2&gt;
&lt;p&gt;Gus Narea, founder and CEO of &lt;a href=&#34;https://relaycorp.tech/&#34;&gt;Relaycorp&lt;/a&gt;, created Awala (formerly Relaynet) to circumvent censorship by repressive governments. The &lt;a href=&#34;https://awala.network/about&#34;&gt;vision&lt;/a&gt; of Awala is to “complement the Internet by providing all human beings with uncensored and timely communication anywhere in the universe – without impairing the &lt;a href=&#34;https://www.un.org/en/universal-declaration-human-rights/&#34;&gt;fundamental rights&lt;/a&gt; of other human beings.” &lt;/p&gt;
&lt;p&gt;When the internet is available, Awala-compatible apps connect like usual to send and receive information. When the internet isn’t available, these apps can send information to ‘&lt;a href=&#34;https://awala.network/couriers&#34;&gt;couriers&lt;/a&gt;’ to give offline users the ability to communicate with a delay. Couriers are able to receive encrypted information, and transfer (relay) the information once they are connected to the internet. &lt;/p&gt;
&lt;p&gt;Awala is designed in such a way that anyone can be a courier — all they need is the courier app and the ability to move from A to B to relay data. The threat model assumes that repressive regimes will manage to compromise or pass off as couriers. The data transported by couriers is end-to-end encrypted, and the routing metadata is obfuscated so that they can&amp;rsquo;t link it to an individual user or service (e.g., Twitter). &lt;/p&gt;
&lt;p&gt;Awala is also capable of detecting when data are lost in transit, and trigger subsequent delivery attempts until the data are eventually acknowledged by the final destination. That means that in the worst case scenario, a malicious courier will only manage to drop the data they collect for/from users. See &lt;a href=&#34;https://www.youtube.com/watch?v=UXuLz3q_6bo&#34;&gt;this helpful video&lt;/a&gt; for a more in-depth explanation of the courier relay process.&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/assets/bringing-the-offline-online-2.png&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;methodology&#34;&gt;Methodology &lt;/h2&gt;
&lt;p&gt;We reviewed the developer experience of the Awala app to provide useful DX recommendations for developers looking to build Awala-compatible apps. Reviews of this type are very important when new protocols are looking to lower the barrier to adoption.&lt;br&gt;
&lt;br&gt;
First, we completed a heuristic review of the Awala Desktop and Mobile applications by utilizing the &lt;a href=&#34;https://simplysecure.org/what-we-do/usable-security-audit/&#34;&gt;10 Heuristics for Responsible Interface Design&lt;/a&gt; with a focus on courier synchronization and configuration of the relay. The UX assessment made recommendations around error prevention, diagnosis, and recovery; efficiency and just-in-time information; and wayfinding and visibility - all key heuristics for enhancing usability with a focus on user privacy. &lt;/p&gt;
&lt;p&gt; Since recruiting third-party app developers is a priority, we also performed an expert review to better understand why and how to build applications using the Awala protocol, and to recommend changes to improve developer usability of the app. Below we dig deeper into the developer experience review. We asked three core questions in our developer experience review, centering trust, documentation, and suitability. &lt;/p&gt;
&lt;h2 id=&#34;findings--recommendations&#34;&gt;Findings &amp;amp; Recommendations&lt;/h2&gt;
&lt;h4 id=&#34;trust-how-can-awala-help-developers-create-a-trustworthy-experience&#34;&gt;Trust: How can Awala help developers create a trustworthy experience? &lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Trust is about people first, tech second&lt;/strong&gt;: Providing context for the user is important. Users must understand both that they need to download Awala and that it needs to be offline.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Couriers are drivers of adoption&lt;/strong&gt;: Couriers are the main drivers of adoption and growth of Awala. Couriers will help users both onboard to Awala, and trust the Awala brand.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Key Recommendations&lt;/strong&gt;: Focus on couriers as the growth center &amp;ndash; make it easy for couriers to deploy  Awala-compatible applications. Think about how Awala can incentivize couriers, and how to increase visibility of the number of couriers active on the network, including location and frequency.&lt;/p&gt;
&lt;h4 id=&#34;documentation-how-can-awala-enable-and-clarify-customization-options&#34;&gt;Documentation: How can Awala enable and clarify customization options? &lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Documentation requires a mental model&lt;/strong&gt;: Developers need to understand how Awala works on a basic level. For example, how can a developer take their existing simple HTTP server and turn it into an Awala app? &lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Limiting new concepts&lt;/strong&gt;: Reduce and simplify the number of new terms and concepts that are needed for developers to get started using Awala. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Key Recommendation&lt;/strong&gt;:  Improve documentation for developers and keep things simple. Provide step-by-step instructions, especially with guidance on how developers can integrate Awala into an existing application.        &lt;/p&gt;
&lt;h4 id=&#34;suitability-what-class-of-applications-are-good-use-cases-for-awala&#34;&gt;Suitability: What class of applications are good use cases for Awala? &lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Hybrid Applications&lt;/strong&gt;: Focusing the business model only on communities with access to the censored internet might limit Awala’s potential reach and user base. Consider some applications (such as video-based apps) that are challenging to use with slow internet. What are some hybrid applications, where Awala can be used for parts of the application that don’t work well with a poor internet connection?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&#34;https://decentpatterns.xyz/library/village-or-city/&#34;&gt;Village or City&lt;/a&gt;&lt;/strong&gt;: Consider the types of interactions e among users of the app. Think of the village or city mode, where in a village people connect via close connections (texting, invite-only chat), and in the city where people are surrounded by strangers (posts are more likely to be public and anonymous by default). &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Key Recommendations&lt;/strong&gt;: Consider growing Awala’s target user base to include those with bad or slow internet, not just those who experience internet blackouts. Provide different use cases to developers so they can imagine apps to be used in different scenarios. Encourage developers to think about the types of interactions their users might have.&lt;/p&gt;
&lt;h2 id=&#34;conclusion&#34;&gt;Conclusion&lt;/h2&gt;
&lt;p&gt;Awala is at an exciting stage of growth. At a time when billions of investment dollars are being poured into infrastructure solutions, Gus and the team are thinking about the gaps between the infrastructure, and the people who live in those spaces. Technologies like Awala bridge digital divides and provide opportunities for people to connect safely, even when traditional infrastructure and politics might block their access. And the team is looking to get more people involved in &lt;a href=&#34;https://awala.network/service-providers/&#34;&gt;building the protocol&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We look forward to seeing how Awala continues to grow its developer and user communities, and follow the development of Letro. &lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Contributors: Gus Narea, Rae McKelvey &lt;/p&gt;
&lt;p&gt;With support from &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;OTF Usability Lab&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>The Limits to Digital Consent</title>
      <link>https://superbloom.design/learning/blog/the-limits-to-digital-consent-understanding-the-risks-of-ethical-consent-and-data-collection-for-underrepresented-communities/</link>
      <pubDate>Mon, 25 Oct 2021 08:18:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/the-limits-to-digital-consent-understanding-the-risks-of-ethical-consent-and-data-collection-for-underrepresented-communities/</guid>
      <description>&lt;h3 id=&#34;understanding-the-risks-of-ethical-consent-and-data-collection-for-underrepresented-communities&#34;&gt;Understanding the Risks of Ethical Consent and Data Collection for Underrepresented Communities&lt;/h3&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/limits-to-digital-consent-title-small_hu_5eada596e37bdcd7.jpg&#34; width=&#34;740&#34; height=&#34;537&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/resources/The_Limits_to_Digital_Consent_FINAL_Oct2021.pdf&#34; class=&#34;button button--secondary read-more&#34; style=&#34;text-decoration: none;&#34;&gt;Read the full report&lt;/a&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Although considerable work has been completed by designers, activists, and aligned policymakers endeavoring to translate data governance policies into comprehensible means of obtaining consent, the question still remains: How well does this work account for the broader socio-technical power structures inherent in all people-centric data collection? &lt;/li&gt;
&lt;li&gt;In partnership with the &lt;a href=&#34;https://newdesigncongress.org/en/&#34;&gt;New Design Congress&lt;/a&gt;, and with support from &lt;a href=&#34;https://www.reset.tech/&#34;&gt;Reset&lt;/a&gt;, our team conducted a series of interviews with advocates for individuals and communities whose lives are often dramatically affected by data surveillance in effort to assess today’s ethical consent paradigms and determine whether they actually achieve the outcomes they seek.&lt;/li&gt;
&lt;li&gt;Our joint &lt;a href=&#34;https://simplysecure.org/resources/The_Limits_to_Digital_Consent_FINAL_Oct2021.pdf&#34;&gt;report&lt;/a&gt; reveals that ongoing attempts to incorporate informed consent into data-driven systems likely fall short of their stated goals due to a host of issues including an insufficient understanding of the power dynamics inherent to organizational politics, second- and third-order effects, network complexity at scale, and political accountability.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Obtaining informed consent is an essential goal for designers. But what is “informed consent” in the context of digital power imbalances and dark patterns designed to convince people to hand over their data unconsciously? Many platform designers and policymakers have begun to focus on transparency, ethics, and trust to work towards creating ethical digital consent systems to communicate their intent and obligation to users. Yet this type of communication and initial design framework is only the beginning. Whether seeking to deploy private analytics or develop research partnerships, the reality is data collection and analysis comes with an astonishingly high degree of ever-evolving risk. Given the complexity of the systems and tools involved, and an often undefined timeline of data stewardship, it is extremely difficult to account for and prevent &lt;a href=&#34;https://ourdataourselves.tacticaltech.org/posts/30-on-weaponised-design/&#34;&gt;weaponised design&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Knowing this, Simply Secure partnered with the &lt;a href=&#34;https://newdesigncongress.org/en/&#34;&gt;New Design Congress&lt;/a&gt; to examine consent paradigms in complex data systems. Through a series of in-depth interviews with advocates for individuals and communities whose lives are often dramatically affected by data surveillance, we set out to determine the extent to which these systems build their desired outcomes. In particular, we wanted to know: Do they truly inform people of the impacts of data collection? And if so, how are changes — in the life of the system as well as the consenting person — accounted for? &lt;/p&gt;
&lt;h2 id=&#34;report-findings&#34;&gt;Report Findings&lt;/h2&gt;
&lt;p&gt;In order to critically assess whether digitally-facilitated consent actually represents a person’s informed understanding of the implication of that consent, we combined in-depth qualitative interviews with a review of the historical and current issues related to data collection. Our report, &lt;a href=&#34;https://simplysecure.org/resources/The_Limits_to_Digital_Consent_FINAL_Oct2021.pdf&#34;&gt;The Limits to Digital Consent: Understanding the risks of ethical consent and data collection for underrepresented communities&lt;/a&gt;, reveals that today’s attempts to cultivate informed consent into data-driven systems likely fall short of their stated goals due to a host of issues including insufficient understanding of the power dynamics inherent to organizational politics, network complexity at scale, political accountability, and the second- or third-order effects of different designs of local-first data strategies. &lt;/p&gt;
&lt;p&gt;Six key findings emerged from our analysis:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;The consent model for tech is outdated.&lt;/strong&gt; Today’s digital consent frameworks are conceptually derived from institutional or academic ethics frameworks, yet digital platforms pose unique challenges that these frameworks are not equipped nor currently designed to address.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Local-first data storage is not inherently safer for people.&lt;/strong&gt; The common assumption that “local is better” does help mitigate issues related to data abuse or company control &amp;ndash; but fails to consider its implications beyond these immediate relationships and how assigning data ownership to an individual can amplify power discrepancies between the user and other non-associated parties. &lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Data creation, including the potential for data creation, is silencing.&lt;/strong&gt; The accelerating rate and scope of data collection, combined with increasing community awareness and savvy surrounding the dangers posed by such datasets, produces a chilling effect on those who wish to speak up and self-advocate but hesitate to do so due to the associated added risk.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Everyone — not just members of underrepresented communities — is at risk.&lt;/strong&gt; Current data collection can &amp;ndash; and almost assuredly will &amp;ndash; be used to feed future technologies whose risks are impossible at present to understand, predict, or mitigate (and time and again, even well-intentioned or purportedly neutral datasets have produced disastrous impacts). &lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Ethical platform designers must consider themselves as the potential bad actor.&lt;/strong&gt; While those who demand design justice and ethical platform development are well-intentioned in their pursuit of empowering people, the reality is many recent dangerous technological advances started out just as well-intentioned before resulting in systemic abuse or worse (and it is simply not possible for even the best-intentioned designer to accurately foresee changes in partnerships or leadership through which carelessness or ulterior motives may poison a platform’s original values).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;People are overwhelmed by both the potential for harm and the indifference of decision-makers.&lt;/strong&gt; Across the globe, communities and individuals are paralyzed by the scale and potential of harm, as well as the real or perceived institutional resistance (by both technology companies and legislators) to tackle consent-related problems.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&#34;looking-forward&#34;&gt;Looking Forward&lt;/h2&gt;
&lt;p&gt;Data accumulation has great power over a person’s agency, their relationships, and the communities within which they operate &amp;ndash; and the associated harms reach almost every human being. Practitioners must therefore examine the systemic shortcomings of digital consent and commit to an ongoing iteration of consent and data governance within platforms. Platform designers and policymakers can no longer assume that collection is safe &amp;ndash; and they must work together to design data storage systems accordingly (including on-device local storage).&lt;/p&gt;
&lt;p&gt;We believe designers should consider unexpected threat scenarios as part of their design process &amp;ndash; leveraging tools like &lt;a href=&#34;https://superbloom.design/learning/resources/persona-non-grata&#34;&gt;Personas Non Grata&lt;/a&gt;, &lt;a href=&#34;https://andrewlb.com/writing/2021-05-16-covid-anxiety/&#34;&gt;Anxiety Games&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/learning/resources/user-experience-toolbox-for-risk-mitigation-and-accessibility&#34;&gt;Usable Security Audits&lt;/a&gt;, or &lt;a href=&#34;https://superbloom.design/learning/resources/data-handling&#34;&gt;data risk analysis&lt;/a&gt;. Doing so allows practitioners to look at the whole socio-technical system and take on a broader understanding of the risks of data accumulation.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/resources/The_Limits_to_Digital_Consent_FINAL_Oct2021.pdf&#34; class=&#34;button button--secondary read-more&#34; style=&#34;text-decoration: none;&#34;&gt;Read the full report&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Leads: Cade Diehm (&lt;a href=&#34;https://newdesigncongress.org/en/&#34;&gt;The New Design Congress&lt;/a&gt;), Kelsey Smith, Ame Elliott, Georgia Bullen&lt;/p&gt;
&lt;p&gt;With support from &lt;a href=&#34;https://www.reset.tech/&#34;&gt;Reset&lt;/a&gt;, an initiative engaged in programmatic work on technology and democracy. Reset seeks to change the way the internet enables the spread of news and information so that it serves the public good over corporate and political interests &amp;ndash; ensuring tech companies once again work for democracy rather than against it.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Using Design to Overcome Structural Inequities in Peer Review</title>
      <link>https://superbloom.design/learning/blog/using-design-to-overcome-structural-inequities-in-peer-review/</link>
      <pubDate>Tue, 19 Oct 2021 13:14:48 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/using-design-to-overcome-structural-inequities-in-peer-review/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/using-design-to-overcome-structural-inequities-in-peer-review-img-3_hu_c34678334ffae035.png&#34; width=&#34;740&#34; height=&#34;178&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;In today’s academic circles, the peer review process is largely conducted behind closed doors by institutional gatekeepers, resulting in an opaque decision-making process that consistently disadvantages researchers from historically marginalized populations and under-resourced institutions. &lt;/li&gt;
&lt;li&gt;We’ve been working with &lt;a href=&#34;https://www.prereview.org/&#34;&gt;PREreview&lt;/a&gt; since 2019 to invert this power imbalance by helping to build a new open source platform that supports a more inclusive, community-oriented form of peer review based on equity, openness, and collaboration.&lt;/li&gt;
&lt;li&gt;Our design work on the ongoing project addressed key systemic problems embedded in the peer review process, including an overreliance on antiquated concepts of prestige, a general inaccessibility for new reviewers, and an unnecessarily high degree of risk for certain scholars who may find themselves the target of harassment in the form of aggressive and harmful feedback. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Note: This post is adapted from a &lt;a href=&#34;https://elifesciences.org/labs/3b77d421/prereview-applying-an-equity-lens-to-tool-design-and-implementation&#34;&gt;blog post&lt;/a&gt; published on eLife Labs by Georgia Bullen (Simply Secure), Daniela Saderi (PREreview), and Katie Wilson (Simply Secure). This is the second post detailing our collaboration with PREreview. For a more general overview on this project, and the power imbalances embedded in academic publishing, click &lt;a href=&#34;https://superbloom.design/learning/blog/inverting-power-imbalances-in-the-peer-review-process-with-prereview/&#34;&gt;here&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Change &amp;ndash; particularly in the digital realm &amp;ndash; must be actioned through design. In working with &lt;a href=&#34;https://www.prereview.org/&#34;&gt;PREreview&lt;/a&gt; to overcome structural inequities in peer review, our team sought to support PREreview’s mission to invert inequitable power imbalances by helping to build a new open source platform that supports a more inclusive, community-oriented form of peer review. Our goal in doing so was to shape a platform that could serve as both a tool on which preprint evaluation work could be performed as well as a space through which community convening could be fostered. Along the way, we identified three primary challenges embedded in the peer review process: (1) an overreliance on antiquated concepts of prestige, (2) a general inaccessibility for new reviewers, and (3) an unnecessarily high degree of risk for certain scholars who may find themselves the target of aggressive and harmful feedback. Below, we detail the design solutions developed with the PREreview team and employed to mitigate these issues and help shape a more equitable way of evaluating scholarly work.&lt;/p&gt;
&lt;h2 id=&#34;overcoming-prestige-as-a-proxy-for-reviewer-worthiness&#34;&gt;Overcoming prestige as a proxy for reviewer worthiness&lt;/h2&gt;
&lt;p&gt;In academia today, traditional publication gatekeepers are disproportionately male and from the United States or Europe. Their affiliated institutions are also almost always well-connected and well-funded. As a result, reviewer “worthiness” is often deemed to be dependent on antiquated concepts of prestige like name recognition, personal connections, and institutional affiliation. But these proxies do not always correlate with true reviewer contribution, ability, or trustworthiness &amp;ndash; which means that many reviewers are excluded from the peer review process despite the fact that they are in fact qualified to participate (and their participation would greatly enhance diversity and inclusion in academia). It also means that certain reviewers may be viewed as integral to the review and publishing process &amp;ndash; despite the fact that their actual contributions may amount to nothing more than a de facto stamp of prestige approval.&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
To help address this problem, we used design to actively highlight individuals on the PREreview platform based on their contributions to the preprint review process, rather than focusing on their status or stage in career. User profiles emphasize participation elements such as badges a PREreviewer received in recognition of their feedback on a project as well as the communities the PREreviewer belongs to on the platform. [See user profile persona in Figma, below.] Notably, career level and institutional affiliation are not removed, but instead de-emphasized in the profile itself and cannot be used as a way to filter reviews. Though these changes might seem subtle, they enable PREreview to underscore the humanity of each reviewer and ensure that they are recognized and valued for their actual contributions to the advancement of knowledge and community on the platform.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/using-design-to-overcome-structural-inequities-in-peer-review-img-2_hu_9d3ca7b43ff942a.png&#34; width=&#34;740&#34; height=&#34;639&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;increasing-accessibility-in-the-peer-review-process&#34;&gt;Increasing accessibility in the peer review process&lt;/h2&gt;
&lt;p&gt;As a result of the systemic inequities in academia, the majority of research submitted for peer review never makes it before a diverse pool of reviewers who would be able to better contextualize it and implement a more comprehensive evaluation of the submitted work’s merits. More researchers from underrepresented groups and regions must be included in the peer review and publication process &amp;ndash; yet such change is unlikely to materialize within the existing system which remains inaccessible to many individuals and communities, and particularly early-career researchers.&lt;/p&gt;
&lt;p&gt;In response to these challenges, we designed to help increase accessibility in several different ways: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;First, login and signup for PREreview was set up to be completed through the &lt;a href=&#34;https://info.orcid.org/documentation/features/public-api/&#34;&gt;ORCID Public API&lt;/a&gt;, which helps to contribute to a future in which all researchers and scholars are uniquely identified and connected to their contributions and work. Looking forward, a potential goal is to also allow PREreviewers to have their preprint reviews listed on their public ORCID profile as a means to further enhance recognition for their contributions. &lt;/li&gt;
&lt;li&gt;Second, in an effort to mitigate the impacts of the general lack of formal peer review training, text-based template guidelines were created as a way to simplify how to write a review and empower early-career researchers who may just be getting started in preprint review. These templates can also be customized by &lt;a href=&#34;https://content.prereview.org/introducing-prereview-communities/&#34;&gt;community managers&lt;/a&gt; to address their own specific needs. &lt;/li&gt;
&lt;li&gt;Third, a system for rapid PREreviews was created to enable swift, structured feedback on preprints. The idea developed out of a partnership between PREreview and &lt;a href=&#34;https://outbreakscience.org&#34;&gt;Outbreak Science&lt;/a&gt;, focused around community needs during outbreaks, but turned out to be of interest and useful to the broader community. Rapid PREreviews allow easy access to provide standardized feedback and contribute to the review process (while also serving as a helpful barometer of a preprint’s credibility and value within a given community). &lt;/li&gt;
&lt;li&gt;Fourth, the PREreview platform was structured so that users and people on other sites can request PREreview feedback directly on the platform or through the platform’s &lt;a href=&#34;https://content.prereview.org/api/&#34;&gt;API&lt;/a&gt;. Together, these and other related design elements serve to lower the barriers to entry in the peer review process which have historically worked to exclude researchers from underrepresented populations and under-resourced institutions.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;protecting-reviewers-from-unnecessarily-harmful-feedback&#34;&gt;Protecting reviewers from unnecessarily harmful feedback&lt;/h2&gt;
&lt;p&gt;Throughout our research, we heard that for some researchers &amp;ndash; and particularly those from underrepresented groups &amp;ndash; the peer review process can involve unnecessarily harmful and antagonistic feedback. This type of hostile treatment can be silencing and perpetuate cycles of exclusion and inequality in academia. &lt;/p&gt;
&lt;p&gt;In response, we sought to ensure we were designing a platform that would protect all of our users while fostering a safe space for feedback and community convening. To achieve this, we worked with the PREreview team on ways to integrate the &lt;a href=&#34;https://content.prereview.org/coc&#34;&gt;Code of Conduct&lt;/a&gt; into the user experience to support the values through the UX, rather than be something that users would agree to once and then forget. Additionally, a reporting feature was also built into the platform, enabling users to flag inappropriate PREreviews for follow up by community moderators and PREreview administrators. Finally, understanding that members of the communities we are seeking to serve can also be the targets of unethical retribution in response to a critical review, we worked with the team to design a pseudonymous profile option that supports users to protect themselves while still adhering to all Code of Conduct requirements.&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Contributors: Georgia Bullen, Katie Wilson, Carissa Yao, Lorraine Chen, Eileen Wagner&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
With support from PREreview, this work was funded by &lt;a href=&#34;https://sloan.org/grant-detail/8729&#34;&gt;The Alfred P. Sloan Foundation&lt;/a&gt;, &lt;a href=&#34;https://wellcome.org/&#34;&gt;The Wellcome Trust&lt;/a&gt;, and the &lt;a href=&#34;https://foundation.mozilla.org/en/&#34;&gt;Mozilla Foundation&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Inverting Power Imbalances in the Peer Review Process with PREreview</title>
      <link>https://superbloom.design/learning/blog/inverting-power-imbalances-in-the-peer-review-process-with-prereview/</link>
      <pubDate>Mon, 18 Oct 2021 14:35:33 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/inverting-power-imbalances-in-the-peer-review-process-with-prereview/</guid>
      <description>&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/prereview-post-one.svg&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;In today’s academic circles, the peer review process is largely conducted behind closed doors by institutional gatekeepers, resulting in an opaque decision-making process that consistently disadvantages researchers from historically marginalized populations and under-resourced institutions. &lt;/li&gt;
&lt;li&gt;We’ve been working with &lt;a href=&#34;https://www.prereview.org/&#34;&gt;PREreview&lt;/a&gt; since 2019 to invert this power imbalance by helping to build a new open source platform that supports a more inclusive, community-oriented form of peer review based on equity, openness, and collaboration.&lt;/li&gt;
&lt;li&gt;Our work on the ongoing project and its equity-based goals served as a strong parallel to our own organizational efforts to shift power imbalances by cultivating community convening, building capacity, and using design to change who technology serves.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Note: a separate post detailing specific design challenges and solutions from our PREreview collaboration is available &lt;a href=&#34;https://superbloom.design/learning/blog/using-design-to-overcome-structural-inequities-in-peer-review/&#34;&gt;here&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Systems of power often work to entrench the status quo in order to maintain the position of those at the top at the expense of everyone else. In the digital world, we see this through Big Tech’s utilization of &lt;a href=&#34;https://www.newstatesman.com/long-reads/2020/02/slouching-towards-dystopia-rise-surveillance-capitalism-and-death-privacy&#34;&gt;surveillance capitalism&lt;/a&gt;, creation of &lt;a href=&#34;https://superbloom.design/learning/resources/popping-the-filter-bubble-design-practices-for-data-donation&#34;&gt;filter bubbles&lt;/a&gt;, and &lt;a href=&#34;https://superbloom.design/learning/blog/mydata&#34;&gt;general negation&lt;/a&gt; of informed user consent. Yet such systems of power are commonplace across virtually all sectors and areas of work &amp;ndash; including academia, where the dissemination of knowledge is centered on a publication model that prioritizes profit over openness and knowledge sharing. The peer review process today is largely conducted behind closed doors by institutional gatekeepers, resulting in an opaque decision-making process that consistently disadvantages researchers from historically marginalized groups and under-resourced institutions. &lt;/p&gt;
&lt;p&gt;In an effort to change that, we&amp;rsquo;ve been working for the past two years with the incredible team at &lt;a href=&#34;https://www.prereview.org/&#34;&gt;PREreview&lt;/a&gt; to help build a new open source platform that supports a more inclusive, community-oriented form of preprint peer review based on equity, openness, and collaboration. PREreview’s efforts focus on bridging &lt;a href=&#34;https://mozilla.github.io/open-leadership-training-series/&#34;&gt;working open&lt;/a&gt; practices with &lt;a href=&#34;https://en.wikipedia.org/wiki/Preprint&#34;&gt;preprints&lt;/a&gt; &amp;ndash; complete versions of research manuscripts that are shared openly online prior to journal-organized peer review. By building these open practices with the community, PREreview aims to increase diversity and support all researchers to build skills around constructive peer review and participate in the peer review processes. With the project continuing to gain traction across a growing community of global researchers, we’re excited to share an overview of our collaboration to date.&lt;/p&gt;
&lt;h2 id=&#34;prereview-power-imbalances-and-the-essential-role-of-equity-in-tool-design&#34;&gt;PREreview, power imbalances, and the essential role of equity in tool design&lt;/h2&gt;
&lt;p&gt;Diversity, equity, and inclusion (DEI) issues abound within academia today, where traditional publication gatekeepers are disproportionately male and from the United States or Europe, and whose affiliated institutions are almost always well-connected and well-funded. As a result of these systemic inequities, research is usually reviewed within networks &amp;ndash; reinforcing biases around which institutions and which researchers get to advance knowledge. To begin addressing this problem, more researchers from underrepresented groups and regions must be included in the peer review and publication process. Yet with the status quo as is, few opportunities exist for this type of change to be implemented within the existing system and technical submission processes.&lt;/p&gt;
&lt;p&gt;In response, &lt;a href=&#34;https://www.prereview.org/&#34;&gt;PREreview&lt;/a&gt; was founded in 2017 with the goal of building a new, more open and equitable way of evaluating scholarly work. In the organization’s &lt;a href=&#34;https://content.prereview.org/mission/&#34;&gt;own words&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;PREreview gives systematically disadvantaged scientists better ways to find a voice, train, and engage in peer review. Our work is a direct response to the flawed way scientific research is evaluated. Behind closed doors, a handful of unpaid reviewers—selected opaquely and mainly through personal connections—use subjective criteria to decide the fate of a research article. This arcane process is slow and disadvantages researchers from historically underrepresented groups. PREreview closes obvious gaps in the process to make research and how it&amp;rsquo;s evaluated more equitable. We train researchers in giving and receiving feedback, we engage communities of underrepresented researchers, and we implement measures to reflect on personal bias.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;PREreview identified preprints &amp;ndash; which are complete versions of scientific manuscripts made freely available online prior to journal-organized peer review &amp;ndash; as a way to separate the dissemination and evaluation of knowledge from the current inequitable system of traditional publication. By creating an open community in which preprints are valued as a source of information that can benefit from a community-oriented and transparent forms of peer review, PREreview is helping to make academia more inclusive and equitable &amp;ndash; while also contributing to speeding the rate of scientific progress around the world. &lt;/p&gt;
&lt;h2 id=&#34;changing-academia-by-changing-who-technology-serves&#34;&gt;Changing academia by changing who technology serves&lt;/h2&gt;
&lt;p&gt;For the past two years, we’ve been collaborating with the PREreview team to help implement their vision of a more equitable and open research and publication process. At the core of this effort was finding a way to build an open source platform that could serve as not only a tool on which the preprint evaluation work could be performed, but also a space through which community could be fostered. &lt;/p&gt;
&lt;p&gt;A review of the systems in place revealed that the inequities present across academia were also embedded in the design of the tools and technology used to prop up the processes of peer review and knowledge dissemination. Our emphasis on shifting power and increasing publishing accessibility therefore required any work we performed to be done with an equity lens in place. In designing the open source platform, we needed to ensure we centered the populations who were being systematically excluded from the traditional publishing process. We needed, in short, to listen to them and prioritize their needs.&lt;/p&gt;
&lt;p&gt;Our team did so by conducting user interviews and testing platform applications, while also supporting the project with product strategy through thought partnership. What are we building? Why are we building it? Who is it serving? These types of questions were emphasized throughout our workshops, coaching, and technology design to ensure that the UI and UX design never lost sight of the researchers who have, until now, been overlooked and excluded in such processes.&lt;/p&gt;
&lt;p&gt;Ultimately, we found our work on the ongoing project and its equity-based goals served as a strong parallel to our own organizational efforts to shift power imbalances in the digital sphere by cultivating community convening, building capacity, and using design to change who technology serves. We’re excited to see what happens next.&lt;/p&gt;
&lt;p&gt;PREreview Co-founder and Director Daniela Saderi said:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Simply Secure has been instrumental not only in centering our values into the design of our preprint review platform, but also in showing us how to best listen to the needs of our communities and work together to shape a more equitable future of scholarly evaluation.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;em&gt;Read more about our PREreview-specific design support and solutions &lt;a href=&#34;https://superbloom.design/learning/blog/using-design-to-overcome-structural-inequities-in-peer-review/&#34;&gt;here&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Contributors: Georgia Bullen, Katie Wilson, Carissa Yao, Lorraine Chen, Eileen Wagner&lt;/p&gt;
&lt;p&gt;With support from PREreview, this work was funded by &lt;a href=&#34;https://sloan.org/grant-detail/8729&#34;&gt;The Alfred P. Sloan Foundation&lt;/a&gt;, &lt;a href=&#34;https://wellcome.org/&#34;&gt;The Wellcome Trust&lt;/a&gt;, and the &lt;a href=&#34;https://foundation.mozilla.org/en/&#34;&gt;Mozilla Foundation&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Reflections on the Mozilla Fellowships and Awards Impact Evaluation: Lessons for the Ecosystem</title>
      <link>https://superbloom.design/learning/blog/reflections-on-the-mozilla-fellowships-and-awards-impact-evaluation-lessons-for-the-ecosystem/</link>
      <pubDate>Wed, 06 Oct 2021 12:52:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/reflections-on-the-mozilla-fellowships-and-awards-impact-evaluation-lessons-for-the-ecosystem/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/reflections-on-the-mozilla-fellowships-and-awards-impact-evaluation-image-2_hu_2ed8065d22506b4d.png&#34; alt=&#34;Mozilla Fellows and Awards Program Timeline&#34; width=&#34;740&#34; height=&#34;568&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;why-a-5-year-impact-evaluation&#34;&gt;Why a 5-Year Impact Evaluation? &lt;/h2&gt;
&lt;p&gt;The public interest technology space has seen an increase in Fellowship programs over the past five years, all focused on helping the public and civil society sectors better understand the impacts of technology on society, and build policies that put people first &amp;ndash; in 2015, &lt;a href=&#34;https://www.techcongress.io/about-us&#34;&gt;TechCongress&lt;/a&gt; launched to place technologists in the halls of Congress as advisors to policy makers; in 2016 the &lt;a href=&#34;https://www.fordfoundation.org/just-matters/just-matters/posts/technologists-for-social-justice-why-ford-is-hiring-more-tech-fellows/&#34;&gt;Ford Foundation&lt;/a&gt; started embedding technologists into their grant-making teams; and in 2017 the &lt;a href=&#34;https://mediademocracyfund.org/public-interest-technology-fellowships&#34;&gt;Media Democracy Fund&lt;/a&gt; paired graduate or PhD students with a tech background and DC-based public interest technology policy organizations. We’ve even piloted a few fellows models ourselves with our &lt;a href=&#34;https://superbloom.design/learning/blog/fellowship/&#34;&gt;Secure Usable Design Fellows&lt;/a&gt; and our &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-2019-recap/&#34;&gt;Underexposed Residency&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&#34;https://foundation.mozilla.org/en/what-we-fund/&#34;&gt;Mozilla Fellowships and Awards&lt;/a&gt; program has been a leader in the tech and civil society sector since their first fellowships in 2014. We have partnered with Mozilla before, on projects such as &lt;a href=&#34;https://rally.mozilla.org/&#34;&gt;Mozilla Rally&lt;/a&gt; and &lt;a href=&#34;https://foundation.mozilla.org/en/research/library/youtube-regrets-findings/&#34;&gt;YouTube Regrets&lt;/a&gt;, and our Executive Director, Georgia Bullen, was a mentor to a 2016 Mozilla Fellow during her Open Technology Institute days. We know how important this program is to the space, and jumped at the chance to support them in reflecting on and maturing their funding arm. Partnering with funders to leverage human-centered design research practices to better understand socio-technical ecosystems is critical work to help further the internet health field. Previously, we’ve worked with funders like Luminate on the &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;‘On Trust and Transparency’&lt;/a&gt; report, published in 2019, and various projects for the Open Technology Fund.&lt;/p&gt;
&lt;p&gt;The evaluation provides an opportunity for the Mozilla Foundation to reflect on what works and what doesn’t in their own programs – and, in the spirit of openness and transparency, it poses useful learnings for the wider digital nonprofit funding ecosystem and internet freedom community.&lt;/p&gt;
&lt;h2 id=&#34;methodology&#34;&gt;Methodology&lt;/h2&gt;
&lt;p&gt;Our team, using human-centered design research methodology, conducted three surveys and held 47 interviews with program alumni, current fellows and awardees, funders, Mozilla Foundation and Corporation staff, and other key stakeholders. We hosted and participated in several workshops with staff and community members, designed to engage iteratively with early findings and challenges. Building on the foundation of internal Mozilla documentation and data, we qualitatively and quantitatively analyzed all of the data into the final evaluation – outlining five years of the programs’ impacts, strengths, and challenges. We also partnered with our friends at &lt;a href=&#34;https://objectively.is/&#34;&gt;Objectively&lt;/a&gt; to create engaging visualizations of program data. (See the Evaluation &lt;a href=&#34;https://foundation.mozilla.org/en/what-we-fund/research/fellowships-awards-evaluation/executive-summary/&#34;&gt;Executive Summary&lt;/a&gt; and &lt;a href=&#34;https://foundation.mozilla.org/en/what-we-fund/research/fellowships-awards-evaluation/impact-narrative-1/&#34;&gt;Impact Narrative&lt;/a&gt; sections for their great work.) The evaluation is supported by a program origin story, an impact narrative, and an interview with Mozilla Foundation management, written by Ayana Byrd and Kenrya Rankin. You can find the full evaluation both on Mozilla’s &lt;a href=&#34;https://foundation.mozilla.org/en/what-we-fund/research/fellowships-awards-evaluation/&#34;&gt;site&lt;/a&gt; and in &lt;a href=&#34;https://foundation.mozilla.org/documents/227/Final_Mozilla_FA_Evaluation.pdf&#34;&gt;PDF&lt;/a&gt; form.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/reflections-on-the-mozilla-fellowships-and-awards-impact-evaluation-image-1_hu_bd10787992410e2a.png&#34; alt=&#34;static image of interative F&amp;amp;A programs sankey&#34; width=&#34;740&#34; height=&#34;404&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;reflections-for-the-ecosystem&#34;&gt;Reflections for the Ecosystem&lt;/h2&gt;
&lt;p&gt;Check out the full evaluation for Insights and Findings around &lt;a href=&#34;https://foundation.mozilla.org/en/what-we-fund/research/fellowships-awards-evaluation/insights-findings-1/&#34;&gt;9 key themes&lt;/a&gt; - ranging from External Perceptions to Program Structure to DEI – as well as &lt;a href=&#34;https://foundation.mozilla.org/en/what-we-fund/research/fellowships-awards-evaluation/key-opportunities/&#34;&gt;12 concluding opportunities&lt;/a&gt; for the Mozilla Foundation, many of which might be useful for the wider digital rights and internet freedom funding landscape. &lt;/p&gt;
&lt;p&gt;The following ecosystem findings were echoed across the interviews and survey results. We identified these themes across our conversations with F&amp;amp;A program alumni, recipients, and staff, as well additional funders and broader community stakeholders. We collected these here as a summary of some reflections the report offers the public interest technology funding ecosystem at large. &lt;/p&gt;
&lt;h3 id=&#34;1-funding-mechanisms--as-exemplified-by-the-success-and-growth-of-mozillas-fellowships-and-awards--are-essential-within-the-digital-rights-ecosystem&#34;&gt;&lt;strong&gt;1. Funding mechanisms – as exemplified by the success and growth of Mozilla’s Fellowships and Awards – are essential within the digital rights ecosystem.&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;In the case of Mozilla, “the impacts of the fellowship program have rippled throughout the internet health movement and ecosystem through narrative shifts and knowledge production.”&lt;/li&gt;
&lt;li&gt;The Mozilla F&amp;amp;A programs are career catalysts for many technologists looking for an entrance into civil society, and for those in civil society looking to expand into digital rights.&lt;/li&gt;
&lt;li&gt;Funding like this opens opportunities for individuals and organizations outside of the for-profit “Big Tech” industry which dominates much of the space.&lt;/li&gt;
&lt;li&gt;Cohorts in fellows and awards create community camaraderie that lasts long beyond the funding period, creating lasting networks in the space. &lt;/li&gt;
&lt;li&gt;Still, there are few follow-on funding opportunities to support the experts who come out of these programs. For-profit companies pay and recruit more than civil society. There is a need to grow the nonprofit sector and prioritize funding so that experts continue working for the public interest  – such as advocacy, open source, and digital equity work.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2-measuring-impact-is-hard&#34;&gt;&lt;strong&gt;2. Measuring impact is hard.&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Every funder struggles to define impact – it’s the nature of the work. It is especially challenging in sectors that are relatively new with significant adversaries – such as the internet freedom community. &lt;/li&gt;
&lt;li&gt;What we can measure are individual stories and narrative shifts. This can be achieved through mapping and networking models, but these strategies must be built-in from the onset of the funding process. This means investing in responsible data collection, but also human connections – equitable opportunities to convene, share work, and network with each other.&lt;/li&gt;
&lt;li&gt;In the report, we propose that Mozilla “leverage the relationships it has built over the last five+ years of programming to develop a network-based model of impact measurement for the ecosystem.” This would not only benefit Mozilla’s modeling and understanding of its impact, but strengthen the growing field of practice with data and open processes. &lt;/li&gt;
&lt;li&gt;Mozilla is exemplifying impact-in-action by publishing the evaluation on a new Learning hub found on their site. Working on change in the open – as an iterative process –- allows everyone to learn and build together. This is a process-oriented approach to impact versus a traditional outcomes-approach - which is a powerful opportunity to build on the evaluation itself.&lt;/li&gt;
&lt;li&gt;Other impact outputs could include: “an in-depth maintained public-facing project database, public speaking and writing about the program design and outputs, funder advocacy around the program design strategies and what they should learn from them, and a “ripple map” that tracks the programs’ influence on individuals and the network” in a consentful and privacy conscious way.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;3-community-is-at-the-core&#34;&gt;3. Community is at the core.&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;One of the chief findings in the evaluation is the importance of community for personal and professional growth. Fellows and awardees widely felt that the cohort experience, opportunities to attend and present at convenings such as &lt;a href=&#34;https://www.mozillafestival.org/en/&#34;&gt;Mozilla Festival (MozFest)&lt;/a&gt;, networking, and supportive relationships with the Mozilla staff were among the most significant benefits of their time as funding recipients.&lt;/li&gt;
&lt;li&gt;On the other hand, this is also something that can be better fostered through the conscious stewardship and building of a network. We proposed that Mozilla “invest in developing, maintaining and supporting a network, inclusive of alumni and key partners/stakeholders, to help fuel the movement and support past participants.” Mozilla has already made big strides in this direction – resourcing new staff to build an alumni network as well as other community and movement building measures. (Check out their &lt;a href=&#34;https://foundation.mozilla.org/en/blog/reflecting-on-the-past-building-for-the-future-mozilla-fellowships-and-awards-impact-evaluation/&#34;&gt;blog post here&lt;/a&gt; for more info!)&lt;/li&gt;
&lt;li&gt;Community networks are spaces for knowledge and resource sharing, which will further strengthen the impact of investments and build this field of practice. “Where previously the idea of an alumni network has had a specific focus on fellows, there is an opportunity for the network to be a broad group of stakeholders who can help inform programs, strategy, and overall priorities and give insights on the space as a whole … Mozilla can leverage all of these partnerships to run a more sustainably engaged, global program. This means the network can be more than just a place to share events and job opportunities, but can be the grounding framework for the movement as a whole.”&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Funders looking to support public interest technology might find useful roadmaps in this in-depth evaluation of Mozilla Fellowships and Awards programs. Funding experts and promoting knowledge sharing community-wide, rather than simply uplifting individual profiles, expands and strengthens the movement at large. Investing in networks means more supported expertise in this sector – toward the goal building more compelling and sustainable avenues beyond Big Tech. The work isn’t just about the outputs we produce, but the communities and ecosystems and resources that we build. Reflections like this evaluation help the broader community design programs and impact measurement tools that support us all.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Building a Toolkit for Funders to Grow their Digital Infrastructure Portfolio</title>
      <link>https://superbloom.design/learning/blog/building-a-toolkit-for-funders-to-grow-their-digital-infrastructure-portfolio/</link>
      <pubDate>Thu, 16 Sep 2021 11:58:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/building-a-toolkit-for-funders-to-grow-their-digital-infrastructure-portfolio/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog-04_hu_c35073cc82520967.png&#34; width=&#34;740&#34; height=&#34;461&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Despite a pressing need for committed and sustained support, the foundational digital infrastructure that underpins much of the world’s software is currently maintained by small and underpaid (or volunteer-based) teams.&lt;/li&gt;
&lt;li&gt;As part of the &lt;a href=&#34;https://techcrunch.com/2021/03/03/1-3m-in-grants-go-towards-making-the-webs-open-source-infrastructure-more-equitable/?guccounter=1&amp;amp;guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&amp;amp;guce_referrer_sig=AQAAAL_ADa0sd-pBleFIWF-e34wGWBTdnWu1RfgM-HBkgTHbcGwAlgTCAmUuZoxRlos7Um-EvTdZdbppMOFIs4rnSsw7wIDffQ8frzCVCQoIE_nnKK_YXHb_0lDfkm9WEdBhTqWidSWoXTapRx0ZdLYcHtATo9_Hsl4paYRoFMi9kNgr&#34;&gt;Digital Infrastructure Grant&lt;/a&gt;, our team is partnering with &lt;a href=&#34;https://superrr.net/&#34;&gt;Superrr Lab&lt;/a&gt; and nine regional partners to design and create the Digital Infrastructure Funders Toolkit &amp;ndash; a global resource to help funders understand the importance of digital infrastructure support and make more impactful funding decisions in the space. Toolkit will be available in 2022.&lt;/li&gt;
&lt;li&gt;The ongoing project builds upon our prior partnership with Superrr Lab, &lt;a href=&#34;https://recommendations.implicit-development.org/&#34;&gt;Roadwork Ahead&lt;/a&gt;, which produced key insights and recommendations for funders and potential funders in the digital infrastructure community.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Just like physical roads and bridges, the digital infrastructure that we all rely on can &amp;ndash; and will &amp;ndash; crumble without committed and sustained support. In 2014 the &lt;a href=&#34;https://en.wikipedia.org/wiki/Heartbleed&#34;&gt;Heartbleed vulnerability&lt;/a&gt; brought this stark reality into focus for millions of people across the globe. Yet still today, the teams that build and maintain the foundational free and open-source software (FOSS) that underpins much of our online world remain small and underpaid (and are often volunteer-based). Fortunately, several civil society funders are now working to change that &amp;ndash; led by the &lt;a href=&#34;https://www.fordfoundation.org/campaigns/critical-digital-infrastructure-research/&#34;&gt;Ford Foundation and Alfred P. Sloan Foundation&lt;/a&gt; who came together in 2018 to “build toward a more diverse and well-funded ecosystem for critical digital infrastructure.” As part of that effort, Simply Secure partnered with &lt;a href=&#34;https://superrr.net/&#34;&gt;Superrr Lab&lt;/a&gt; on &lt;a href=&#34;https://recommendations.implicit-development.org/&#34;&gt;Roadwork Ahead&lt;/a&gt;, an investigation into the needs of FOSS communities working on digital infrastructure in the public interest. The resulting June 2020 &lt;a href=&#34;https://recommendations.implicit-development.org/assets/IDE_REPORT_2020.pdf&#34;&gt;report&lt;/a&gt; shared 10 key insights and 30 recommendations for funders operating or seeking to operate in this space.&lt;/p&gt;
&lt;p&gt;This year, a coalition of funders is putting $1.3 million toward the &lt;a href=&#34;https://techcrunch.com/2021/03/03/1-3m-in-grants-go-towards-making-the-webs-open-source-infrastructure-more-equitable/?guccounter=1&amp;amp;guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&amp;amp;guce_referrer_sig=AQAAAL_ADa0sd-pBleFIWF-e34wGWBTdnWu1RfgM-HBkgTHbcGwAlgTCAmUuZoxRlos7Um-EvTdZdbppMOFIs4rnSsw7wIDffQ8frzCVCQoIE_nnKK_YXHb_0lDfkm9WEdBhTqWidSWoXTapRx0ZdLYcHtATo9_Hsl4paYRoFMi9kNgr&#34;&gt;Digital Infrastructure Grant&lt;/a&gt;, and we are once again partnering with Superrr Lab &amp;ndash; this time to make the Roadwork Ahead &lt;a href=&#34;https://recommendations.implicit-development.org/recommendations/&#34;&gt;recommendations&lt;/a&gt; actionable via the design and creation of a Digital Infrastructure Funders Toolkit, to be published in Q1 2022.  Below, we share our approach to the ongoing project, including identifying funder personas, creating an inclusive geographic scope, and maximizing meaningful funder engagement.&lt;/p&gt;
&lt;h2 id=&#34;identifying-funder-personas&#34;&gt;Identifying funder personas&lt;/h2&gt;
&lt;p&gt;Our primary audience for the Toolkit is funders who are interested in supporting digital infrastructure but who are not currently operating or well-connected in the specific space. The Toolkit’s resources can help provide critical guidance and support to help these funders enter this unique &amp;ndash; and essential &amp;ndash; community of practice. Our secondary audience is funders who are currently supporting digital infrastructure that would like to improve and streamline their model, process, or approach (including, but not limited to, the funders supporting the Toolkit effort).&lt;/p&gt;
&lt;p&gt;These two target audiences can be categorized into four different personas to help identify their specific needs:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The Tech Enthusiast&lt;/li&gt;
&lt;li&gt;The Innovative Philanthropist&lt;/li&gt;
&lt;li&gt;The Compassionate Change-maker &lt;/li&gt;
&lt;li&gt;The Social Advocate &lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;the-tech-enthusiast&#34;&gt;THE TECH ENTHUSIAST&lt;/h4&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/picture-2_hu_fc892dab158e89c1.png&#34; width=&#34;740&#34; height=&#34;223&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Type of funding organization: Funders with a digital profile but limited experience in funding digital infrastructure. They have strong technical expertise and usually tend to see technology as a key catalyst to almost every problem-solving formula.&lt;/p&gt;
&lt;p&gt;Funding needs: A mechanism and/or framework for funding digital infrastructure that works across the globe. &lt;/p&gt;
&lt;h4 id=&#34;the-innovative-philanthropist&#34;&gt;THE INNOVATIVE PHILANTHROPIST&lt;/h4&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/picture-3_hu_56c9aee814d5bc95.png&#34; width=&#34;740&#34; height=&#34;200&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Type of funding organization: Funders from non-tech sectors who are interested in funding technology and digital infrastructure as aligned with their mission. They have little to no prior experience in funding technology, and very little technical expertise. They employ a systemic approach to funding.&lt;/p&gt;
&lt;p&gt;Funding needs: A way to apply their funding knowledge to the digital infrastructure space. They would benefit from a beginner-friendly entrance to the technology funding world, a framework to fund digital infrastructure, and a connection to the FOSS community. &lt;/p&gt;
&lt;h4 id=&#34;the-compassionate-change-maker&#34;&gt;THE COMPASSIONATE CHANGE-MAKER &lt;/h4&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/picture-4_hu_12eff2a92b63dc63.png&#34; width=&#34;740&#34; height=&#34;253&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Type of funding organization: Established funders of technology and digital infrastructure.&lt;/p&gt;
&lt;p&gt;They have strong technical expertise and a funding approach that is often grounded in the community’s needs.&lt;/p&gt;
&lt;p&gt;Funding needs: A streamlined mechanism and framework for funding digital infrastructure so that they can support a wider range of projects. &lt;/p&gt;
&lt;h4 id=&#34;the-social-advocate&#34;&gt;THE SOCIAL ADVOCATE&lt;/h4&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/picture-5_hu_8ebccebc8c0513cd.png&#34; width=&#34;740&#34; height=&#34;226&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Type of funding organization: Funders who have technology and digital infrastructure as part of their programs but aren’t necessarily well-connected with the FOSS community. They often advocate for positive social changes that can be enabled by technology, but don’t focus on the open source community.&lt;/p&gt;
&lt;p&gt;Funding needs: A way of communicating with the community in order to establish a suitable funding mechanism. &lt;/p&gt;
&lt;h2 id=&#34;designing-a-toolkit-for-current-and-potential-funders-of-digital-infrastructure&#34;&gt;Designing a Toolkit for current and potential funders of digital infrastructure&lt;/h2&gt;
&lt;p&gt;The basic approach of the Digital Infrastructure Funders Toolkit is rooted in a human-centered design (HCD) process that generates actionable insights based on research and active experimentation. Through interviews, focus groups, and testing, the Toolkit will be iteratively designed and implemented. This HCD approach allows us to engage funders, applicants, and advisors, and improve the relationship between these stakeholders that shape the health of the ecosystem as a whole.&lt;/p&gt;
&lt;p&gt;Funders that offer better funding models and center the people that are supporting the infrastructure will make better funding decisions. When implemented, the types of changes proposed in the Toolkit will significantly impact the sustainability of open source and foundational software, keep standards and protocols interoperable and up-to-date, and create a more resilient and secure digital infrastructure. Through our Toolkit, it is our hope that more funders will realize the relevance of digital infrastructure to their cause and express their interest in funding this area. &lt;/p&gt;
&lt;h2 id=&#34;creating-an-inclusive-geographic-scope&#34;&gt;Creating an inclusive geographic scope&lt;/h2&gt;
&lt;p&gt;In building out a global resource like the Toolkit, it’s important to acknowledge that regions, languages, and governments articulate and understand “infrastructure” in very different ways. That’s why we’re incorporating a regional team of non-US/non-EU researchers to help ensure we capture and share these nuances, and offer a more global understanding of the needs, wants, and opportunities in service to this work. We’ve partnered with nine individuals and organizations connected with their local funders to help us build localized tools and translate the Toolkits. Our partners are reaching out to funders in cities, countries, and regions with both nascent and developed digital rights and FOSS communities. &lt;/p&gt;
&lt;h3 id=&#34;engaging-with-funders-show-not-tell&#34;&gt;Engaging with Funders: Show not Tell &lt;/h3&gt;
&lt;p&gt;To help funders connect digital infrastructure with their mission-critical social issues, we’re creating a set of narratives that show how digital infrastructure is core to issues like environmental sustainability, healthy democracies, and freedom of speech. These story-based narratives will help convey the relevance of digital infrastructure in a way that is easy for non-technical audiences to understand, while also sharing pictures and illustrations for social media and online content.&lt;/p&gt;
&lt;p&gt;Through our testing and outreach, funding partners will be able to develop a robust understanding of digital infrastructure, and create or iterate on their own framework for funding. The structured guidance and support we will create through the Toolkit will allow funders to work with grantees to develop an effective funding model that works for all parties. This will especially benefit funders that are new to supporting infrastructure projects, which in turn can lower barriers to entry and lead to more funding opportunities for this sector.&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Regional Partners, including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superrr.net/&#34;&gt;Superrr Lab&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://2ic-lab.wowperations.com.br/&#34;&gt;2iC Lab&lt;/a&gt; (&lt;a href=&#34;http://linkedin.com/in/celsobessa/&#34;&gt;Celso Bessa&lt;/a&gt;, &lt;a href=&#34;https://www.linkedin.com/in/bibiana-alarcon-58840232/&#34;&gt;Bibiana Alarcón&lt;/a&gt;, &lt;a href=&#34;https://www.linkedin.com/in/daniela-prada-ardila-researcher/&#34;&gt;Daniela Prada&lt;/a&gt;, &lt;a href=&#34;https://www.linkedin.com/in/juan-carlos-roa-bogota-34aa6319/&#34;&gt;Juan Roa&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.mozillapulse.org/profile/4179&#34;&gt;Amarela&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.linkedin.com/in/michelledbarker/&#34;&gt;Michelle Barker&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/mbunzama&#34;&gt;Narcisse Mbunzama Lokwa&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://theiofoundation.org/&#34;&gt;The IO Foundation&lt;/a&gt; (&lt;a href=&#34;https://www.linkedin.com/in/jfqueralt/&#34;&gt;Jean F. Queralt&lt;/a&gt;, &lt;a href=&#34;https://www.linkedin.com/in/raashi-saxena-18a90684&#34;&gt;Raashi Saxena&lt;/a&gt;, &lt;a href=&#34;https://linkedin.com/in/maryamlee&#34;&gt;Maryam Lee&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://ke.linkedin.com/in/wainainamungai&#34;&gt;Wainaina Mungai&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;With support from &lt;a href=&#34;https://blog.opencollective.com/di-grants/&#34;&gt;the funders of the Digital Infrastructure Fund&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>From Paper to Infinity Whiteboard</title>
      <link>https://superbloom.design/learning/blog/from-paper-to-infinity-whiteboard-inspiring-creativity-and-digital-collaboration-in-online-design-workshops/</link>
      <pubDate>Wed, 08 Sep 2021 12:40:47 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/from-paper-to-infinity-whiteboard-inspiring-creativity-and-digital-collaboration-in-online-design-workshops/</guid>
      <description>&lt;h2 id=&#34;inspiring-creativity-and-digital-collaboration-in-online-design-workshops&#34;&gt;Inspiring Creativity and Digital Collaboration in Online Design Workshops&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;For this past year’s virtual &lt;a href=&#34;https://www.mozillafestival.org/en/&#34;&gt;Mozilla Festival&lt;/a&gt;, we designed and ran “&lt;a href=&#34;https://superbloom.design/learning/blog/mozfest-2021-will-we-see-you-there&#34;&gt;Explain Decentralization To Me&lt;/a&gt;” — a zine-making workshop structured to meet the needs of a global audience while still preserving the in-person experience.&lt;/li&gt;
&lt;li&gt;Our work in selecting an infinity whiteboard platform and designing the event focused on maximizing user accessibility and maintaining the zine community’s creative, do-it-yourself spirit in an online workshop environment.&lt;/li&gt;
&lt;li&gt;When designing your own digital workshop, always anticipate and center the needs of your audience, account for various skill levels, prepare test runs, incorporate feedback in advance, and be flexible during the event itself. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;With design workshops moving increasingly online, it’s important for designers to familiarize themselves with new tools, approaches, and ways of thinking. When doing so, a common concern tends to arise: How can an online workshop be designed for a global audience while still preserving the value of an in-person experience? In preparing for this past year’s virtual edition of &lt;a href=&#34;https://www.mozillafestival.org/en/&#34;&gt;Mozilla Festival&lt;/a&gt;, our team met this challenge head on in designing a zine-making workshop for the festival called “&lt;a href=&#34;https://superbloom.design/learning/blog/mozfest-2021-will-we-see-you-there&#34;&gt;Explain Decentralization To Me&lt;/a&gt;” (a zine is a format of self-publication that affords creators the utmost freedom of self-expression). The zine community often embraces a spirit of DIY (do-it-yourself) in ways that differ from traditional techniques throughout the production process. So as we planned the workshop, we asked ourselves: How might we foster this creative, DIY spirit in an online workshop? &lt;/p&gt;
&lt;h2 id=&#34;selecting-a-platform&#34;&gt;Selecting a platform&lt;/h2&gt;
&lt;p&gt;A unique and exciting production element of zine-making is the ability to experiment with a wide range of materials, visual styles, and formats. From paper type and texture, to page layout and binding technique, there is virtually no limitation on how one can choose to tell their story. Yet the beauty in the diversity of zine aesthetics is difficult for a single digital tool to achieve. In choosing a platform for the workshop, we sketched out a list of criteria in hopes of maintaining and facilitating these diverse aesthetics. The platform needed to: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Be easy to use and fast to learn. &lt;/li&gt;
&lt;li&gt;Allow for effortless digital collaboration.&lt;/li&gt;
&lt;li&gt;Replicate the zine-making process to a certain degree, including working with papers, designing a page layout, and adding photos, texts, folding, and binding.&lt;/li&gt;
&lt;li&gt;Allow for markdown / printable format. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Given these requirements, we selected &lt;a href=&#34;https://miro.com/&#34;&gt;Miro&lt;/a&gt; from the sea of emerging online tools and platforms designed to accommodate the new norm of remote working and digital collaboration. Miro stood out for two reasons: Accessibility and Usability. &lt;/p&gt;
&lt;p&gt;To choose the right tool, we need to know the audience of our workshop. The first thing to consider is accessibility. Our audience was joining from around the world, so we knew that they would have different levels of internet connectivity. Ideally, the platform we chose would either require a minimal bandwidth to join or allow people to access via different devices. Not only did Miro meet these requirements, but it also had the option of granting participants full access to the workshop materials without signing in or signing up. &lt;/p&gt;
&lt;p&gt;The next thing to consider is usability. In comparison, Miro is easier to onboard than other options like &lt;a href=&#34;https://www.figma.com/&#34;&gt;Figma&lt;/a&gt; because it is generally beginner-friendly and requires less technical expertise. Nonetheless, we knew many participants would likely be inexperienced with Miro, so we prepared a Miro walkthrough as part of the workshop agenda and included a clear indication of what technical knowledge was required in the workshop introduction to reduce technical barriers and confusion.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/screenshot-2021-09-07-at-14.34.29_hu_e46951454ea4b1f1.png&#34; width=&#34;740&#34; height=&#34;348&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;A screenshot of our Miro walkthrough&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;designing-the-workshop&#34;&gt;Designing the workshop&lt;/h2&gt;
&lt;p&gt;Board organization plays an important part in the design of any successful workshop. Not only does it present the workshop’s visual aesthetic, it also dictates the flow of activities and how participants should navigate the workshop space when they first arrive. A typical workshop will likely have the following boards:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Welcome &amp;amp; Introduction &lt;/li&gt;
&lt;li&gt;Workshop Goal &amp;amp; Agenda&lt;/li&gt;
&lt;li&gt;Community Guidelines / Rules of Engagement&lt;/li&gt;
&lt;li&gt;Tool Walkthrough&lt;/li&gt;
&lt;li&gt;Main Activities &lt;/li&gt;
&lt;li&gt;Closing &amp;amp; Feedback &lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;In a time-limited workshop, especially those that are under 90 minutes, advance preparation is key. We made sure to eliminate all time-consuming tasks or tasks that add cognitive load, such as external browsing for materials or long lectures. Our goal was to make the workshop as thorough and smooth as possible. To do so, we planned ahead by walking through scenarios where each participant had different needs and designed the board to address them. In advance of the actual workshop, we also performed test runs with our colleagues, whose feedback was then incorporated into the final design of the workshop.&lt;/p&gt;
&lt;p&gt;To help participants more fully immerse themselves in the creative process, we configured the infinite whiteboard as if it was a physical space. We created a “craft station” that featured two sample zine templates, a blank zine template, and a visual library. Each participant had their own work station with the basic materials, instead of having to create their own empty board or copy and paste the template from one place to another. This maximized the use of time and enabled experienced zine-makers and beginners alike to enter the making process with ease.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/3.-zine-template-1_-explanatory_hu_683723dbac6e5dda.jpg&#34; width=&#34;740&#34; height=&#34;523&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Zine template 1: Explanatory&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/4.-zine-template-2_-storytelling-_hu_70ff450e7e95b6c7.jpg&#34; width=&#34;740&#34; height=&#34;523&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Zine template 2: Storytelling&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/7.-library-of-stickers-provided-in-the-workshop.-these-stickers-can-be-easily-copied-and-pasted-or-dragged-and-dropped-from-one-board-to-another.-all-images-are-cc-licensed.-_hu_892c33a91516cce7.jpg&#34; width=&#34;740&#34; height=&#34;523&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Library of stickers provided in the workshop. These stickers can be easily copied and pasted or dragged and dropped from one board to another. All images are CC licensed.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/5.-example-of-a-digitally-finished-zine-before-printing-and-folding.-_hu_8b6d40fb5acbf909.jpg&#34; width=&#34;740&#34; height=&#34;299&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Example of a digitally finished zine before printing and folding.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/6.-printed-outcomes_hu_efe7a673b0a62ee5.jpg&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Printed outcomes&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;key-takeaways--tips&#34;&gt;Key takeaways &amp;amp; tips&lt;/h2&gt;
&lt;p&gt;There are many different ways to measure the success of a workshop, but for us, success reveals itself in the small little things. It is seeing the busy boards with items being added and sticky notes being dragged and moved around. It is feeling the creative energy and the atmosphere of collaboration that everyone exerted despite the barrier of screens between us. It is seeing participants return to the boards and keep working on their zines after the wrap-up. &lt;/p&gt;
&lt;p&gt;Looking to the future, the next time we facilitate a digital-making workshop, we might do a few things differently. While Miro is among one of the most powerful infinity boards available, we would like to test an open-source alternative. In addition, it would be helpful to get more involved with the community of zine-makers, designers, and other interested creatives by establishing a common platform for exchanging ideas and publishing decentralization on-boarding materials. Having a process for sharing, reposting, licensing, and open-sourcing the outcomes of the workshop in place beforehand would be a great way to maximize the workshop’s impact and share knowledge. &lt;/p&gt;
&lt;p&gt;Below, we summarized our top tips for designing a virtual workshop. After you review them, have fun creating your own decentralization zine with our open-sourced template &lt;a href=&#34;https://miro.com/app/board/o9J_lIHr-jM=/&#34;&gt;here&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;General virtual workshop design tips:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Always keep your audience in mind. You’re creating the workshop for them. To help best meet their needs, ask yourself:&lt;/li&gt;
&lt;li&gt;
&lt;ul&gt;
&lt;li&gt;What is their level of technical knowledge?&lt;/li&gt;
&lt;li&gt;What is their tool proficiency?&lt;/li&gt;
&lt;li&gt;What is their internet connection?&lt;/li&gt;
&lt;li&gt;Which browsers do they use?&lt;/li&gt;
&lt;li&gt;What is their language?&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;If you can, hold a test run with colleagues, friends, or family to receive crucial feedback on your design (this is especially helpful at an early stage). Try to incorporate at least two rounds of feedback for your design.&lt;/li&gt;
&lt;li&gt;Time each session in a test run and adjust accordingly. &lt;/li&gt;
&lt;li&gt;Make sure to account for extra time for people to join at the beginning of the workshop (not everyone is going to show up to the call on time!). &lt;/li&gt;
&lt;li&gt;Introduction activities should be inclusive and make people feel welcome. &lt;/li&gt;
&lt;li&gt;Remember, when it comes to the digital world, everything is possible. So keep an open mind and maintain a flexible attitude to help create the best overall experience for everyone!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Tips for infinity whiteboard workshop design:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If your participant is new to infinity whiteboards, try to stick with the main feature (sticky notes). Instead of naming each frame (‘rename frame’), use a seperate big text box on top of each frame &amp;ndash; this helps participants navigate much quicker.&lt;/li&gt;
&lt;li&gt;Use a big black rectangle to hide boards that you will address later in the workshop to avoid distraction.&lt;/li&gt;
&lt;li&gt;Remember to lock your board to avoid people moving everything around.&lt;/li&gt;
&lt;li&gt;Use arrows to help people navigate the boards.&lt;/li&gt;
&lt;li&gt;Provide written direction for each activity.&lt;/li&gt;
&lt;li&gt;Make use of the timer feature. Miro has some great countdown tunes!  &lt;/li&gt;
&lt;li&gt;If you need to take a break to re-set/set-up the board, just let your participants know (but don’t take more than a minute or two!). &lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;selected-zines-from-our-mozfest-workshop&#34;&gt;Selected zines from our MozFest workshop: &lt;/h2&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/anuradha-karissa_hu_7d4b2c9a28945e13.jpg&#34; width=&#34;740&#34; height=&#34;523&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Credit: Anuradha + Karissa&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/ingrid-_-manish_hu_6f39408a5bc7bfa8.jpg&#34; width=&#34;740&#34; height=&#34;523&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Credit: Ingrid + Manish&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/nancy-eileen_hu_8ed8a6b2d5590ec2.jpg&#34; width=&#34;740&#34; height=&#34;523&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Credit: Nancy + Eileen&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/sarah-k-_-ashelsh_hu_4e343115e623b7f0.jpg&#34; width=&#34;740&#34; height=&#34;522&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Credit: Sarah K + Ashelsh&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/shu-ngoc_hu_21bdc7eb17759c7d.jpg&#34; width=&#34;740&#34; height=&#34;523&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Credit: Shu + Ngọc&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;-&amp;ndash;&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Standing Together to Stop Online Bullying: Harassment of Women Journalists is a Community Problem</title>
      <link>https://superbloom.design/learning/blog/standing-together-to-stop-online-bullying-harassment-of-women-journalists-is-a-community-problem/</link>
      <pubDate>Wed, 28 Jul 2021 12:41:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/standing-together-to-stop-online-bullying-harassment-of-women-journalists-is-a-community-problem/</guid>
      <description>&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://lh3.googleusercontent.com/PGbhfoUzxEutc8FdHH-3p16kEw3uILRd1zAQWMVL2XNMChXUjRiUjTD5oPNxbhC2AW54XJagGAIi608R5LPAo0M6kBx933v_ywKCQk6HEnO9ZOq-LDPKB5a2k53D5InUiABTg1Es&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;span style=&#34;font-size:11.0pt&#34;&gt;&lt;em&gt;Quote from Lydia Cacho — Español: “Cuando hablamos de acoso en línea, siempre estamos hablando de violencia. Es una forma de violencia psicológica, de persecución, sin duda.” English: “When we speak about online bullying, we are always talking about violence. It’s a form of psychological violence, of persecution, without a doubt.”&lt;/em&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;From the outset of their careers, women journalists are taught that they need to establish and foster an increasingly recognizable online brand under their real name - yet when their reporting is inevitably met with online bullying and harassment, they are told the problem is an individual one for them to handle on their own.&lt;/li&gt;
&lt;li&gt;As part of the IWMF-led Coalition Against Online Violence, our team sought to help stem this rising tide of intimidation by providing research and design support for the launch of the &lt;a href=&#34;https://onlineviolenceresponsehub.org/&#34;&gt;Online Violence Response Hub&lt;/a&gt;, a new digital resource designed to assist and inform women journalists facing these types of threats.&lt;/li&gt;
&lt;li&gt;Our work on the project aligned with our broader organizational efforts to change who technology serves by shifting the conversation around online bullying and identifying how platform design choices today often enable harassment instead of prevent it.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Three-out-of-four women journalists (73%) &lt;a href=&#34;https://www.icfj.org/sites/default/files/2020-12/UNESCO%20Online%20Violence%20Against%20Women%20Journalists%20-%20A%20Global%20Snapshot%20Dec9pm.pdf&#34;&gt;have experienced&lt;/a&gt; some form of online violence - ranging from sexual and physical threats to the targeting of family and friends. And for 20% of these reporters, online threats end up transitioning into offline attacks and in-person abuse. Alarming statistics like these indicate just how normalized online violence against women journalists has become. Yet such actions are far from normal and cannot be accepted. They represent attacks not only on individuals, but also on society writ large - which suffers in the wake of stifled reporting and an inability of diverse voices to participate freely in news formation.&lt;/p&gt;
&lt;p&gt;Launching today, the &lt;a href=&#34;https://onlineviolenceresponsehub.org/&#34;&gt;Online Violence Response Hub&lt;/a&gt; - a new digital resource designed to assist and inform women journalists facing threats from online bullying and harassment - represents the efforts of a united community against this repugnant and dangerous behavior. Simply Secure is proud to have participated in the creation of this invaluable website, and we ask all members of our community to share this resource and expand its reach.&lt;/p&gt;
&lt;h2 id=&#34;toxic-newsroom-norms&#34;&gt;Toxic Newsroom Norms&lt;/h2&gt;
&lt;p&gt;Starting in journalism school or at their first job, women journalists are taught they need to establish and foster an increasingly recognizable online brand under their true identity. From an online security standpoint, this practice creates an incredibly large online footprint from which these journalists can be attacked. Yet despite direct encouragement to create such a presence, when a woman reporter is inevitably met with online bullying and harassment, they are routinely told the problem is an individual one for them to handle on their own. “This is just a part of your job,” runs a common industry refrain. “Tough it out, or get out.” &lt;/p&gt;
&lt;p&gt;For the reporter and her family and close associates, the psychological and physical toll of these attacks are compounded by the lack of accessible resources available to help. Though several initiatives have been created to address various points of this systemic problem, no universal platform currently exists to which a journalist can turn in a time of need. Left without support from their employer, and unable to locate much-needed resources, women reporters often have little guidance and few allies during these high-stress and dangerous situations. It is beyond time for that to change.&lt;/p&gt;
&lt;h2 id=&#34;creating-the-online-violence-response-hub&#34;&gt;Creating the Online Violence Response Hub&lt;/h2&gt;
&lt;p&gt;In October 2020, Simply Secure joined the &lt;a href=&#34;https://www.iwmf.org/&#34;&gt;International Women’s Media Foundation&lt;/a&gt; (IWMF)’s &lt;a href=&#34;https://www.iwmf.org/coalition-against-online-violence/&#34;&gt;Coalition Against Online Violence&lt;/a&gt;, a diverse group of stakeholders working together to stop online abuse. Five months later, we were engaged to join the team creating an easily accessible online resource that journalists can go to for answers and help when faced with a bullying problem.&lt;/p&gt;
&lt;p&gt;In supporting the design of the &lt;a href=&#34;https://onlineviolenceresponsehub.org/&#34;&gt;Online Violence Response Hub&lt;/a&gt;, we worked with the IWMF team to bolster their needs research by developing an interview and focus group guide, facilitating discussions, synthesizing research findings, co-designing the information architecture, and supporting site development and implementation. Through this human-centered approach, we were able to distill three key findings:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Some form of bullying is accepted as a consequence of being a woman and a journalist.&lt;/li&gt;
&lt;li&gt;Emotional processing is an important first step in getting help.&lt;/li&gt;
&lt;li&gt;Harassment is a community problem, but is treated as an individual one.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alongside other needs- and issue-based findings, we were able to understand the most common challenges and how journalists describe them. These essential takeaways informed the organization of the website’s content and increased accessibility by ensuring users would be able to quickly and accurately find answers to and resources for their most pressing questions and needs in times of crisis. &lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://lh4.googleusercontent.com/KjpWj00e4kUHYNZIlsidxP1cnD_ne187fn6SM-k4Mfgjv4z2qewvy9rIGfYxMgBcWQfL79ej7FRQxZmY2d1rarXghk2vKKRbK-hCDDt-DyiVzv9OKzStf_OI8gxy0hyF7i9DmVqz&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;designing-a-safer-tomorrow---together&#34;&gt;Designing a Safer Tomorrow - Together&lt;/h2&gt;
&lt;p&gt;This project also spoke more broadly to issues of design and how platforms often enable harassment. By failing to design clear content moderation strategies or ways for individuals under attack to get help, social media platforms create ample space for bullying and harassment to thrive. Their algorithms, designed to promote engagement and interaction, actively promote the most sensational and inflammatory interactions - drawing more people into the fray. Powered by the inverted economics of &lt;a href=&#34;https://news.harvard.edu/gazette/story/2019/03/harvard-professor-says-surveillance-capitalism-is-undermining-democracy/&#34;&gt;surveillance capitalism&lt;/a&gt;, which prioritizes profits over people, these companies have no incentive to work on the complicated issues at the intersection of content moderation, censorship, and user experience design. Instead, they complacently pass the impact of platform-enabled harms on to vulnerable users like women journalists.&lt;/p&gt;
&lt;p&gt;When helpful information exists but is inaccessible or undiscoverable, the most vulnerable among us can be left without a lifeline. As a design and tech community, we need to work together and actually engage with these issues - not just as issues for policy and legal teams, but as problems of product and design. We believe that in order to address problems like online harassment, we need to actively work to shift who technology serves. By leveraging a human-centered approach to design and research, and addressing foreseeable stress cases, we can center the needs of people experiencing harms and increase overall project accessibility. One actionable tactic to do this essential work is for designers to plan for the arrival of bad actors (&lt;a href=&#34;https://simplysecure.org/designunderpressure/#methods&#34;&gt;personas non grata&lt;/a&gt;) on their platform, and then design to minimize their harmful effects. When scenarios like these are baked into the design process from the outset, the tech and design community are able to work together to support people like women journalists experiencing harassment. &lt;/p&gt;
&lt;p&gt;Four of the largest tech companies recently &lt;a href=&#34;https://webfoundation.org/2021/07/generation-equality-commitments/&#34;&gt;announced commitments&lt;/a&gt; to address online abuse and protect women, signaling an acknowledgement that these design flaws are communal, not individual, problems. Though the responsibility for a safer tomorrow starts with platforms designing to address these harms, more is still needed. We all must do our part and stand together. That’s why we ask that you do yours today by sharing the &lt;a href=&#34;https://onlineviolenceresponsehub.org/&#34;&gt;Online Violence Response Hub&lt;/a&gt; with your community members, friends, and family.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>What&#39;s next for &#39;Simply Secure&#39;? Part 2: Refreshing our name and identity</title>
      <link>https://superbloom.design/learning/blog/simply-secure-refreshing-our-name-and-identity-part-2/</link>
      <pubDate>Mon, 19 Jul 2021 11:11:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/simply-secure-refreshing-our-name-and-identity-part-2/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;Read part 1 of the &amp;ldquo;What&amp;rsquo;s next for &amp;lsquo;Simply Secure&amp;rsquo;?&amp;rdquo; identity series&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In 2020, we embarked on a community-oriented design process to help shape what’s next for Simply Secure. Our goal: a new name and tagline; a new brand and visuals; and a clearer articulation of who we are as an organization.&lt;/p&gt;
&lt;p&gt;Throughout the process we chose to learn from and have an open dialogue with members of our community. We&amp;rsquo;re here to serve a need in the world – so it was essential to find a name and distill our mission in a way that resonates with those we support (and who support us). We also have so many brilliant minds in our network – people who understand visuals, words, and stories, as well as us and our work. A community-oriented design process allowed our team to leverage this expertise and creativity, and ultimately design our brand in a way that aligns with our values. Though the process remains ongoing, we’d like to take a moment to share how far we’ve come.&lt;/p&gt;
&lt;h2 id=&#34;assembling-an-identity-committee&#34;&gt;Assembling an Identity Committee&lt;/h2&gt;
&lt;p&gt;Una Lee of &lt;a href=&#34;https://www.andalsotoo.net/&#34;&gt;And Also Too&lt;/a&gt; is a key partner in this work, and has helped us to frame our process, using elements of co-design to structure our community collaboration. After conducting an initial community survey about our name and branding, we convened a committee of 10 people to help us dig deeper into the survey results as well as the opportunities/challenges of how we present our organization. We chose these individuals based on their diverse expertise and divergent points of view; we knew they would both support and challenge us.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/aspirationtech&#34;&gt;Allen &amp;ldquo;Gunner&amp;rdquo; Gunn&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/holantonela&#34;&gt;Antonela Debiasi&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/EriolDoesDesign&#34;&gt;Eriol Fox&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.linkedin.com/in/jochaibenavie&#34;&gt;Jochai Ben-Avie&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/j_kloiber&#34;&gt;Julia Kloiber&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/kirstie_j&#34;&gt;Kirstie Whitaker&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/nielstenoever&#34;&gt;Niels ten Oever&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/peterbihr&#34;&gt;Peter Bihr&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Sage Cheng&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/ttcatz&#34;&gt;TTcat&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To each of our Identity Committee members, we want to say: Thank you! We wouldn’t be where we are today without your insight and advice.&lt;/p&gt;
&lt;h2 id=&#34;moving-beyond-what-do-we-do-to-who-are-we&#34;&gt;Moving beyond “what do we do?” to “who are we?”&lt;/h2&gt;
&lt;p&gt;Simply Secure was founded eight years ago with the goal of making secure communication tools more accessible for everyday people. Since then, these tools have finally begun to receive the attention they deserve and, alongside our community, our organization has grown in size and expertise. Yet we’ve also grown in vision. In working to democratize human-centered design principles, our team has increasingly sought out opportunities to further transformational justice and digital equity. &lt;/p&gt;
&lt;p&gt;Unsurprisingly, this expanded vision has expanded our scope of work as well. The name Simply Secure no longer feels representative of all that we do – little of our work is simple, and security is about more than just tools. In line with this, one of the more compelling findings from our identity survey was that many respondents feel that they are only seeing the tip of the Simply Secure iceberg – they know that we do a lot, but the entire breadth of our work remains at least partially obscured. &lt;/p&gt;
&lt;p&gt;Yet as we convened to answer the question “What do we do?”, we soon realized we also had to answer an even more complex question: “Who are we?” &lt;/p&gt;
&lt;h2 id=&#34;café-simply-secure-would-you-like-wireframes-with-that&#34;&gt;Café Simply Secure: &amp;ldquo;Would you like wireframes with that?&amp;rdquo;&lt;/h2&gt;
&lt;p&gt;Between November 2020 and February 2021, we held two series of workshops with our Identity Committee and the Simply Secure core team to help us better articulate who we are. In one exercise, we asked our participants to write a review for Simply Secure by pretending that Simply Secure was a restaurant. Our goal was to have participants disassociate from tech and design to see what lies at the heart of who we are. 
&lt;img class=&#34;image&#34; src=&#34;https://lh6.googleusercontent.com/1d3uUqHIVdcFn5Q91nj8l5rvptpQtBc3hPttMGAlN2M4r-b7tHb_Mu482V396Vvi0FWOzR9nzosdpPs7YG9wvCo6njBZqRHEv8GLdUdH0u2ih126IkM5JaB2cXgOqgq5PTVR8E1G&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;A word cloud shows the descriptors that were the output of the “restaurant review” exercise.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The output of the exercise was the above collection of unique descriptors. Given that we work on technology, the prominence of the top phrase &amp;ldquo;down to earth&amp;rdquo; surprised us! Our &amp;ldquo;café&amp;rdquo; isn&amp;rsquo;t a trendy fast tech hub, but rather a welcoming place that puts people at ease, and helps them connect and learn. This essential feedback confirmed that our identity could focus more on people – and not just tech itself. We also explored various other metaphors through a succession of brainstorming exercises in which we identified images, words, and principles that described Simply Secure. These metaphors helped reveal additional fundamental aspects of our identity and role within the community, as part of a complex, emergent ecological system.&lt;/p&gt;
&lt;h2 id=&#34;interview-insights&#34;&gt;Interview insights&lt;/h2&gt;
&lt;p&gt;As our process continued to evolve, we sought out even more specificity regarding what we should emphasize (or avoid) in formulating our new identity. Through a series of interviews, our Committee and Board Members shared with us what they think we do well, and where we should use caution in describing ourselves. &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Openness is one of our calling cards.&lt;/strong&gt; From early projects focused on security usability to more recent service and organization design work, our openness and transparency is key. We&amp;rsquo;re at our best when we make the results of our engagements as available and usable as possible.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;We&amp;rsquo;re strategic, pragmatic doers, not a “consultancy.”&lt;/strong&gt; We heard this word a lot, and in some ways, it helps people understand that we offer services that help tools, groups, and organizations improve. But &amp;ldquo;consultancy&amp;rdquo; also has capitalist and extractive associations that don&amp;rsquo;t match our values or way of working. We also do so much more than just consulting &amp;ndash; we snap into action, and we blaze a trail for others.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;We excel at centering the human element in technology.&lt;/strong&gt; We heard several times that we are good at listening to, understanding, and supporting the human needs within tech projects. Without devaluing these critical qualities, it’s important to note that they are also frequently gendered traits, and our team has always been majority female-identifying. While we value these qualities, we need to ensure that both our empathy and our overall competence are emphasized as skills.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;We need to be careful when using the term &amp;ldquo;design.&amp;rdquo;&lt;/strong&gt; Many of us are designers, and many of our methodologies are drawn from design disciplines – service, product, UX, transition, and social design. Yet like &amp;ldquo;consultancy,&amp;rdquo; the term &amp;ldquo;design&amp;rdquo; carries different connotations for different people. For some, design means visual art, which isn&amp;rsquo;t one of our core areas of work.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These insights, along with many others, proved invaluable as we moved closer to arriving at a new name, tagline, visual identity, and refreshed understanding of our organization.&lt;/p&gt;
&lt;h2 id=&#34;our-exploration-into-community-led-design&#34;&gt;Our exploration into community-led design&lt;/h2&gt;
&lt;p&gt;For those considering embarking on a community-based design approach to a branding project, we can offer a few observations on what we’ve learned so far.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;You will learn an incredible amount about yourselves as an organization.&lt;/strong&gt; The insights we&amp;rsquo;ve gained from our committee, and even from our own tough internal conversations, have helped us grow and develop. We&amp;rsquo;re not just building our new name and visuals; we&amp;rsquo;re learning who we are, and clarifying who we want to be.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The process will take longer than expected.&lt;/strong&gt; One of the contributing factors is the increase in communication. Being transparent and open about your process means consistently framing progress, requesting feedback, sharing debriefs, and providing updates. You should probably factor in at least twice your usual communication overhead (and likely even more).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Coming up with a decision-making process requires self-awareness.&lt;/strong&gt; Every community is different, and existing groups already have power dynamics and decision-making processes in place. Before selecting a new decision-making model, you’ll first want to look at how your group or community currently makes decisions. Even after selecting the best, you’ll also have to remain flexible: any process you settle on at the beginning is almost guaranteed to change (but that’s a good thing!). &lt;/li&gt;
&lt;li&gt;&lt;strong&gt;It&amp;rsquo;s hard to predict what twists and turns the process will take.&lt;/strong&gt; We originally asked our Committee to take part in a series of three workshops before February. Our process evolved into one workshop, one interview, another workshop, and numerous rounds of asynchronous feedback over email on proposals and even videos. And we’re still not quite done! &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We’ve truly enjoyed and grown from this process. And we know the “Simply Secure” that comes out on the other side will be all the better for it. For your next design process, we encourage you to consider a community-based approach of your own! If you have questions, we’re happy to share. &lt;/p&gt;
&lt;h2 id=&#34;next-steps&#34;&gt;Next steps&lt;/h2&gt;
&lt;p&gt;From here, we are iterating on our name ideas; asking for feedback from the team, Board, and Committee; and developing a short list to share with a lawyer for trademark and legal review. In the next installment, we look forward to sharing our new name and visual identity with you!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Technical Program Manager</title>
      <link>https://superbloom.design/community/opportunities/technical_pm/</link>
      <pubDate>Tue, 29 Jun 2021 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/opportunities/technical_pm/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://superbloom.design/community/opportunities/&#34;&gt;&amp;lt; Back to open positions&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;this-role-has-been-filled&#34;&gt;This role has been filled.&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;We&amp;rsquo;re looking for a  technical program manager to lead design and development teams for our projects, to support our internal infrastructure systems, and to help scope new technical projects for our organization.&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&#34;the-role&#34;&gt;&lt;strong&gt;The role&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The TPM will be the product owner for one multi-stakeholder open source project, and will lead on various other projects within the Internet Freedom space.&lt;/li&gt;
&lt;li&gt;Up to 50% of the time will be focused on leading and managing the design &amp;amp; development teams for an open source, multi-stakeholder project building an application system to serve the broader internet freedom ecosystem.&lt;/li&gt;
&lt;li&gt;Up to 20% you&amp;rsquo;ll help us manage our partnership with the Open Technology Fund Usability Lab, ensuring appropriate projects scoping, bringing the right team together, and advising on more technical projects.&lt;/li&gt;
&lt;li&gt;Another 20% of the time will be focused on managing a number of projects with different partners and engagement models, making sure that we are on top of timelines, communicating effectively, and delivering on the work.&lt;/li&gt;
&lt;li&gt;About 10% of your time will be dedicated to supporting Simply Secure&amp;rsquo;s internal Org Sec infrastructure.&lt;/li&gt;
&lt;li&gt;This is a full-time position at 40 hours per week, from about August 2021 to December 2022, with the opportunity to renew. The salary is approximately USD $80,000 per year. We are a US 501(c)3 organization that has the ability to hire in the US and Germany, and contract internationally.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;about-us&#34;&gt;About us&lt;/h3&gt;
&lt;p&gt;We are a small US 501(c)3 nonprofit organization, founded in 2014 with the goal of making security tools easier to use. We believed – and still do – that security doesn&amp;rsquo;t have to be confusing to end users. We&amp;rsquo;ve contributed design to a variety of tools that enhance security, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We&amp;rsquo;ve held &lt;a href=&#34;https://superbloom.design/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we&amp;rsquo;ve done a lot more than usable security. Just in the last year, we&amp;rsquo;ve launched a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;p&gt;(We&amp;rsquo;re actually doing a rebranding process, moving away from the name &amp;ldquo;Simply Secure.&amp;rdquo; &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;More info over here on the blog!&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&#34;about-you&#34;&gt;About you&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You have experience with product management, and have experience with different software development methodologies such as Agile or Kanban, and most importantly know when and where to use them.&lt;/li&gt;
&lt;li&gt;You have excellent stakeholder management skills, and understand how product development requires balancing the needs — sometimes conflicting needs — of diverse users, and are comfortable with ambiguities.&lt;/li&gt;
&lt;li&gt;You enjoy simplifying complex projects, tracking details, and making sure the project teams are working well together&lt;/li&gt;
&lt;li&gt;You have experience with leading projects and project delivery&lt;/li&gt;
&lt;li&gt;You are familiar with design or development in open source, and are comfortable working in the open&lt;/li&gt;
&lt;li&gt;You like working independently and in collaboration with a fully remote, distributed team&lt;/li&gt;
&lt;li&gt;You have excellent project team communication and meeting facilitation skills&lt;/li&gt;
&lt;li&gt;You are experienced with client-centered communication&lt;/li&gt;
&lt;li&gt;You are comfortable advocating for yourself and your work to make sure that you&amp;rsquo;re getting what you need to be successful&lt;/li&gt;
&lt;li&gt;You are available during our prime work hours (11-6pm Central Europe / 10-5pm UK / 8-6pm US Eastern / 8-3pm US Pacific)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;nice-to-have&#34;&gt;Nice to have&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Experience with research and design work, e.g. human-centered design, design thinking, service design, ux design, or participatory research (specifically field research)&lt;/li&gt;
&lt;li&gt;Experience with supporting organizational IT, including tool audits and administration&lt;/li&gt;
&lt;li&gt;Experience with client-facing account management&lt;/li&gt;
&lt;li&gt;Knowledgeable about one or more of the following areas: open source software, internet freedom, tech criticism and activism, human rights, nonprofit funding&lt;/li&gt;
&lt;li&gt;Comfortable with collaborative work tools (we currently use Notion, Miro, and Google Suite)&lt;/li&gt;
&lt;li&gt;Comfortable with exploring and evaluating new tools&lt;/li&gt;
&lt;li&gt;Comfortable in cross-cultural communication, e.g. experience with international work&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;sound-like-a-good-fit&#34;&gt;Sound like a good fit?&lt;/h3&gt;
&lt;p&gt;Please send us:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Resume&lt;/li&gt;
&lt;li&gt;Examples of your work. With each link or document you send, please tell us about the timeline and process:*
&lt;ul&gt;
&lt;li&gt;How did these outputs get created?&lt;/li&gt;
&lt;li&gt;Who was involved?&lt;/li&gt;
&lt;li&gt;What did the process look like?&lt;/li&gt;
&lt;li&gt;How long did it take?&lt;/li&gt;
&lt;li&gt;How did your work improve the products you worked on?&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Please describe: (100 words max each)
&lt;ul&gt;
&lt;li&gt;What processes do you find useful in different scenarios, and why?&lt;/li&gt;
&lt;li&gt;How do you approach difficult situations?&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Send these documents to us at &lt;strong&gt;&lt;a href=&#34;mailto:jobs@superbloom.design&#34;&gt;jobs@superbloom.design&lt;/a&gt;&lt;/strong&gt; by July 31, 2021.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;To help us combat bias while we review applications, please remove your name from the documents you send.&lt;/strong&gt; One person on our team will keep a list assigning a code name to your application while we review it. If we&amp;rsquo;d like to interview you, we&amp;rsquo;ll match your code name to your real name, and get in touch. (If removing your name from your work screws up the formatting, don&amp;rsquo;t worry, this is not a graphic design job! You can also put an obviously fake name in place of your real name to keep the formatting consistent.)&lt;/p&gt;
&lt;p&gt;We believe that systemic bad behaviors disproportionately hurt the most marginalized people in society — including people of color, people from working class backgrounds, women and LGBTQ people. We believe that these communities must be centered in the work we do. We strongly encourage applications from people with these identities or who are members of other marginalized communities.
31&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Visual/Web Designer (Contract)</title>
      <link>https://superbloom.design/community/opportunities/visual_web_designer/</link>
      <pubDate>Wed, 23 Jun 2021 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/opportunities/visual_web_designer/</guid>
      <description>&lt;h2 id=&#34;this-role-has-been-filled&#34;&gt;This role has been filled.&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;We&amp;rsquo;re looking for a Visual/Web Designer to help us create and deliver an identity and visual/web design.&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&#34;the-project&#34;&gt;&lt;strong&gt;The project&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Simply Secure is looking to contract a visual designer who can bring their expertise in web design and crafting brand identities to a new educational website and resource repository launching in August 2021. The website helps lawmakers, advocates, and concerned citizens get the tech policy information they need.&lt;/li&gt;
&lt;li&gt;The website is currently in development, with IA and UX design work underway.&lt;/li&gt;
&lt;li&gt;Several identity guidelines are already in place, including mission, vision, values, and audience. We&amp;rsquo;re hoping to strike a balance between a tactile, educational feel and a professional and trustworthy polish.&lt;/li&gt;
&lt;li&gt;The design process will be iterative, requiring close collaboration with the project team, including: weekly meetings, asynchronous updates, and willingness to be responsive to team direction and ideas.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;You’ll propose, create, and deliver an identity and visual/web design that includes:&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;A logo for the website (name is already in place)&lt;/li&gt;
&lt;li&gt;Typography&lt;/li&gt;
&lt;li&gt;Illustrations/icons&lt;/li&gt;
&lt;li&gt;Color palette&lt;/li&gt;
&lt;li&gt;Guidelines for usage (dos and don’ts)&lt;/li&gt;
&lt;li&gt;Web design (Working with UX designers to apply your identity guidelines to the UI)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;This is a time-limited contract, from approximately July 2021 through August 2021. We are a US 501(c)3 organization that has the ability to contract internationally.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;about-us&#34;&gt;About us&lt;/h3&gt;
&lt;p&gt;We are a small US 501(c)3 nonprofit organization, founded in 2014 with the goal of making security tools easier to use. We believed – and still do – that security doesn&amp;rsquo;t have to be confusing to end users. We&amp;rsquo;ve contributed design to a variety of tools that enhance security, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We&amp;rsquo;ve held &lt;a href=&#34;https://superbloom.design/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we&amp;rsquo;ve done a lot more than usable security. Just in the last year, we&amp;rsquo;ve launched a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;p&gt;(We&amp;rsquo;re actually doing a rebranding process, moving away from the name &amp;ldquo;Simply Secure.&amp;rdquo; &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;More info over here on the blog!&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&#34;about-you&#34;&gt;About you&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You love and have demonstrated experience designing identity systems. You are really excited to tell the visual story of a tool that helps people.&lt;/li&gt;
&lt;li&gt;You design expressive and accessible screens, logos, and illustrations, meant to be viewed on the web.&lt;/li&gt;
&lt;li&gt;You have experience designing websites.&lt;/li&gt;
&lt;li&gt;You like working independently, in collaboration with a fully remote team.&lt;/li&gt;
&lt;li&gt;You are comfortable advocating for yourself and your work to make sure that you’re getting what you need from us.&lt;/li&gt;
&lt;li&gt;Your meeting availability has sufficient overlap with our working hours of 9am to 5pm Eastern Standard Time. The project team is based on the East Coast of the US.&lt;/li&gt;
&lt;li&gt;You use tools that facilitate easy, remote collaboration (we use Figma, Notion, and Miro, primarily).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;nice-to-have&#34;&gt;Nice to have&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Awareness of and/or interest in one or more of the following areas: tech criticism and activism, tech policy, human rights, international politics, education.&lt;/li&gt;
&lt;li&gt;Knowledge of web accessibility standards.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;sound-like-a-good-fit&#34;&gt;Sound like a good fit?&lt;/h3&gt;
&lt;p&gt;Please send us:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;3 examples of your work. Please highlight the projects with quick turn-around times (less than 3 months) and tell us, briefly, about the &lt;strong&gt;timeline and process&lt;/strong&gt;: how did these projects get created? Who was involved, what did the process look like, how long did it take?&lt;/li&gt;
&lt;li&gt;A (very short!) outline of how you would approach working with us on this project. What phases would this project have, and what would you need from us to make it successful?&lt;/li&gt;
&lt;li&gt;1-2 references. References will be contacted in the last phase of application review.&lt;/li&gt;
&lt;li&gt;The times you are available for meetings within our working hours (9am to 5pm Eastern Standard Time)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Send these documents to &lt;a href=&#34;mailto:jobs-brand@superbloom.design&#34;&gt;jobs-brand@superbloom.design&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Position is open until filled and applications will be evaluated on a rolling review. We will stop accepting applications on July 31, 2021.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We believe that systemic bad behaviors disproportionately hurt the most marginalized people in society — including people of color, people from working class backgrounds, women and LGBTQ people. We believe that these communities must be centered in the work we do. We strongly encourage applications from people with these identities or who are members of other marginalized communities.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Designing for a Global Audience in the Age of Remote Usability Testing</title>
      <link>https://superbloom.design/learning/blog/designing-for-a-global-audience-in-the-age-of-remote-usability-testing/</link>
      <pubDate>Mon, 21 Jun 2021 14:40:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/designing-for-a-global-audience-in-the-age-of-remote-usability-testing/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/riseupvpn_hu_c02b4b4aba25e555.png&#34; alt=&#34;different devices scattered on a world map connecting in/out of a single server &#34; width=&#34;740&#34; height=&#34;638&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://riseup.net/&#34;&gt;Riseup&lt;/a&gt; offers VPN service to anyone online, but focuses primarily on human rights activists, journalists, and social justice workers due to the tool’s location anonymization feature and lack of sign-in, payment, or IP address logging requirements. &lt;/li&gt;
&lt;li&gt;Riseup asked us to redesign their entire user experience on desktop and manual selection (a feature that allows users to choose the exit point of their VPN) to both mobile and desktop.   &lt;/li&gt;
&lt;li&gt;The ultimate goal of the project was not only to design and test the usability of manual selection, but also to position Riseup&amp;rsquo;s development team to be able to incorporate sustainable, user-centered design into their culture.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Though many VPN services charge a user fee or collect at least some sort of potentially identifying information (such as IP address logging or a sign-in), &lt;a href=&#34;https://riseup.net/&#34;&gt;Riseup&lt;/a&gt; does not &amp;ndash; making the VPN a favorite amongst activists and journalists. Riseup was selected to participate in the &lt;a href=&#34;https://usable.tools/blog/2020-10-01-uxfund2020/&#34;&gt;UXFund&lt;/a&gt;, a targeted pool of funding dedicated to improving the usability of open source security and privacy tools used by at-risk communities around the globe. The majority of the UXFund supports work addressing the needs of at-risk persons and/or vulnerable populations.&lt;/p&gt;
&lt;p&gt;While Riseup was interested in receiving assistance to test out the beta version of a new manual selection feature (which allows users to choose their exit point), the ultimate goal in working with Simply Secure was to have us teach their development team how to self-sustain, incorporate user-centered design, and perform their own usability testing in the future. &lt;/p&gt;
&lt;p&gt;To begin the project, we first conducted an initial survey of other commercially available VPNs in order to obtain a sense of how others incorporate manual selection. One notable difference between Riseup and typical commercial VPNs is that Riseup has fewer overall resources and therefore needs to monitor their VPN load more closely. From a design standpoint, that means while many commercial VPNs choose to prominently feature manual selection in their user interface, Riseup is interested instead in encouraging their users to more often use the automatic selection feature.&lt;/p&gt;
&lt;h3 id=&#34;testing-process&#34;&gt;Testing Process&lt;/h3&gt;
&lt;h4 id=&#34;1-privacy-centered-research-process&#34;&gt;1. Privacy-centered research process&lt;/h4&gt;
&lt;p&gt;Because Riseup is centered around a strong value system, we wanted to be sure to design a usability testing process that was aligned with their mission. As a collective, Riseup aims to support freedom of expression and overcome systematic oppression by providing computer resources and communication tools. Accordingly, it was important for us to maintain the privacy of all interviewees while operating in a remote setting. For our video conferencing tool, we chose &lt;a href=&#34;https://jitsi.org/&#34;&gt;Jitsi&lt;/a&gt; &amp;ndash; an open source, end-to-end encrypted service that doesn’t require users to create an account. In addition, video was optional for testers as all of the testing was conducted through a clickable prototype rather than a screen-sharing service. To facilitate this process, we created a high-fidelity clickable prototype (a highly realistic and detailed version of the design that appears and functions just like the real app). This form of testing allowed the team to gather more meaningful feedback during the tests because participants were more likely to behave naturally. Throughout the testing process, we also used the observation mode feature on Figma which allowed our team to follow user actions and track interactions and movement without requiring them to share their screen. Notably, although Figma is not an open-source tool, it works best for team collaboration and real-time tracking. In the future, however, we would like to look into &lt;a href=&#34;https://alternativeto.net/software/figma/?license=opensource&#34;&gt;open source Figma alternatives&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;2-fully-remote-user-research&#34;&gt;2. Fully remote user research&lt;/h4&gt;
&lt;p&gt;Due to the anonymity-oriented nature of VPN services and travel restrictions related to the COVID-19 pandemic, all of our testing sessions had to be conducted remotely. This requirement presented a unique technical challenge because we weren’t able to simply ask users to connect to the VPN and share their feedback through a video conferencing tool due to the fact that internet connections shut off temporarily when users connect to a proxy network like Riseup VPN. To design around this obstacle, we created our hi-fidelity clickable prototype to enable network connections to remain stable throughout usability testing. Using this prototype also allowed us to reliably re-create and test various scenarios (like user redirection or slow connection) without writing a single line of code.&lt;/p&gt;
&lt;h4 id=&#34;3-internet-access-for-a-global-audience&#34;&gt;3. Internet access for a global audience&lt;/h4&gt;
&lt;p&gt;Finally, because Riseup has a user base all over the world, we also needed to target testing with users calling in from different time zones and with different language preferences. In addition, because VPN services are location-based and users connecting from different countries and regions often have different internet regulations and bandwidths, we worked to adjust our testing prototype to address a wide range of scenarios. The Riseup team wanted to explore how to properly balance the load between many different cities and in different scenarios.&lt;/p&gt;
&lt;h3 id=&#34;next-steps&#34;&gt;Next Steps&lt;/h3&gt;
&lt;p&gt;Although the project is still in its user interview and testing phase, we are looking forward to hearing from different users in order to implement some of the changes to the existing prototype and eventually hand it off to Riseup’s development team.&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;Project Leads: Carissa Yao and Rae McKelvey&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Strength In Numbers: Designing to Help At-Risk Users Protect Against Phishing Attacks</title>
      <link>https://superbloom.design/learning/blog/strength-in-numbers/</link>
      <pubDate>Mon, 07 Jun 2021 19:05:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/strength-in-numbers/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/phishdetect1_hu_f14a6bd8809c9340.png&#34; width=&#34;740&#34; height=&#34;412&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Amnesty International asked us to help improve user accessibility and trust for &lt;a href=&#34;https://github.com/phishdetect&#34;&gt;PhishDetect&lt;/a&gt;, an open-source browser extension that helps at-risk users mitigate phishing attacks through a coordinated human network.&lt;/li&gt;
&lt;li&gt;Our team used a research-intensive approach to modernize the tool’s design, clarify its language, and leverage consistent graphics to enhance user comprehension and assurance.&lt;/li&gt;
&lt;li&gt;The result is a safer online experience for those working to advance equality, safety, and transparency around the world &amp;ndash; and therefore a better product for everyone.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Everyone faces risk from online phishing attacks. Due to the nature of their jobs, human rights defenders and activists face a heightened threat level from authoritarian actors who don&amp;rsquo;t uphold human rights. Aware of the increased danger this problem poses to its community members, &lt;a href=&#34;https://www.amnesty.org/&#34;&gt;Amnesty International&lt;/a&gt; recently decided to support &lt;a href=&#34;https://github.com/phishdetect&#34;&gt;PhishDetect&lt;/a&gt; - an open-source browser extension that helps at-risk users mitigate phishing attacks by empowering a coordinated human network to identify, report, and avoid potential threats. Through use of the extension, network members are able to pool their information and collectively reduce the likelihood of successful attacks on their communities. Like a school of fish, a PhishDetect network is stronger when its users work together. &lt;br&gt;
&lt;br&gt;
Because increased community participation makes PhishDetect more effective and keeps more people safe, Amnesty International came to Simply Secure in June 2020 to help improve the tool’s usability and accessibility prior to launch. No strangers to using design to increase user safety and awareness, our team set about modernizing PhishDetect&amp;rsquo;s design, clarifying the tool&amp;rsquo;s language, and leveraging graphics to enhance threat comprehension. Project success would mean not only a better product - but a safer online experience for those working to advance equality, safety, and transparency worldwide.&lt;/p&gt;
&lt;h3 id=&#34;diving-in&#34;&gt;Diving in&lt;/h3&gt;
&lt;p&gt;Our human-centered approach began with a series of initial coaching sessions through which we became familiar with the unique needs of PhishDetect. By analyzing similar tools, studying the user journey, interviewing experts and users, and conducting workshops, we were able to distill four guiding principles for the project, the tool, and its user needs:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;PhishDetect is a &lt;u&gt;practical&lt;/u&gt;, not educational, tool.&lt;/li&gt;
&lt;li&gt;&lt;u&gt;Reassuring&lt;/u&gt; users is just as important as warning them.&lt;/li&gt;
&lt;li&gt;Users have &lt;u&gt;agency&lt;/u&gt; to make their own choices.&lt;/li&gt;
&lt;li&gt;PhishDetect is a &lt;u&gt;community&lt;/u&gt; effort.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Though these key principles were far from obvious at the outset of the project, they proved to be invaluable resources as we iterated, tested, and refined new brand and UX designs. They also helped us solve complex problems like determining how much interference in routine users would accept (PhishDetect is by definition disruptive in preventing people from visiting suspicious websites). We knew we wanted to increase friction in risky situations, but how much friction would be too much? When would too much disruption actually hinder safety by increasing annoyance? Research in hand, we were able to craft a compelling visual identity for PhishDetect (including a mascot, metaphor, and logical ecosystem) and improve overall usability through enhanced UX.&lt;/p&gt;
&lt;h3 id=&#34;changing-tides&#34;&gt;Changing tides&lt;/h3&gt;
&lt;p&gt;In making the web extension more intuitive for users, our team addressed a host of PhishDetect features including the onboarding process, menu icon, in-browser pages, tool settings, email integration, and website. The examples below provide three snapshots into this design work.&lt;/p&gt;
&lt;h4 id=&#34;creating-a-new-visual-identity&#34;&gt;Creating a new visual identity&lt;/h4&gt;
&lt;p&gt;It quickly became clear from our research that PhishDetect needed a new visual identity to help users better recognize the tool, utilize its offerings, and understand their role in the ecosystem. Unlike providing code (which few people have the time or expertise to decipher), a visual metaphor creates stronger lines of communication between the extension and user. Likewise, visual consistency signals trust and can provide assurance in otherwise stressful situations. In partnership with brand designer &lt;a href=&#34;https://www.guillelasarte.com/&#34;&gt;Guille Lasarte&lt;/a&gt;, we therefore created a PhishDetect metaphor, in which the bird and whale (Network admins) help the school of fish (users) work together to avoid pollution (phishing). Though these characters come from different species, they happily work alongside one another to keep the ocean (the community) safe for all.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/phishdetecttwo_hu_6035e99b54539d3.png&#34; alt=&#34;illustrations of a school of fish, whale, and bird&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/phishdetect3_hu_5832cc97183b48c9.png&#34; alt=&#34;illustrations of pollution and dead fish&#34; width=&#34;740&#34; height=&#34;580&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;designing-a-toolbar-pop-up&#34;&gt;Designing a toolbar pop-up&lt;/h4&gt;
&lt;p&gt;With an emphasis on making user goals easier to achieve, we designed PhishDetect’s toolbar pop-up to reassure, save time, and reduce frustration. To help users make quick decisions, we utilized a hierarchy system in which the primary action (“scan”) is prioritized visually through placement and size. This method maintains user agency as the secondary action (“report”) is accessible, although placed lower and smaller on the screen. A “help” button linked to reassuring information on the PhishDetect website is also provided throughout. At each iteration of design, we focused on PhishDetect’s practicality and worked to simplify language and enable images to convey the desired message.&lt;/p&gt;
&lt;p&gt;&lt;i&gt;Toolbar pop-up - Design Iterations:&lt;/i&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/pop-up-iterations_hu_10e60fa3619135db.png&#34; alt=&#34;Sketches of pop up iterations&#34; width=&#34;740&#34; height=&#34;328&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;i&gt;Toolbar pop-up - Final Design:&lt;/i&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/phishdetect5_hu_176790e464158558.png&#34; alt=&#34;Phishing pop-up illustration with a bird and a radar circle&#34; width=&#34;740&#34; height=&#34;777&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;changing-what-users-see-when-a-phishing-webpage-is-blocked&#34;&gt;Changing what users see when a phishing webpage is blocked&lt;/h4&gt;
&lt;p&gt;Thanks to our redesign efforts, when a user clicks to visit a phishing website, PhishDetect automatically redirects them to an interstitial block page that relays the threat without causing panic. Building on the visual identity discussed above, the metaphor image and accompanying text clearly and quickly clarifly what is happening and why. This information enables users to make informed choices by first explaining what happened (“Why is this page blocked?”), and then balancing a warning (“What are the potential risks of phishing?”) with reassurance (“Has anything bad happened?”). Because PhishDetect users ultimately retain discretion to do as they please, the path to “proceed” is located at the bottom of the page (after the warnings), indicating it is not the safest option - but an option nonetheless.&lt;/p&gt;
&lt;p&gt;&lt;i&gt;Phishing block page:&lt;/i&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/phishdetect6_hu_638578e5ca27b5b8.png&#34; alt=&#34;Phishing block page, with illustrations of pollution and dead fish&#34; width=&#34;740&#34; height=&#34;999&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;swimming-forward-together&#34;&gt;Swimming forward together&lt;/h3&gt;
&lt;p&gt;So what&amp;rsquo;s next for PhishDetect and its future users? Going forward, the PhishDetect team is working on implementing the new designs and further testing. After the tool’s official launch, community and organization members will hopefully feel a bit safer online - empowering them to take on new and more challenging tasks, secure in the knowledge that they have the protection of PhishDetect on their side.
Bottom line: When a tool&amp;rsquo;s success hinges on human participation, human-centered design is a must. There&amp;rsquo;s never a more important time to meet users where they are, understand their needs, and then design a solution catered to address them. By taking the time to understandPhishDetect’s users and unique context, our team was able to unlock the tool’s incredible potential to protect not just individuals - but entire networks of frontline defenders and at-risk communities.&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;Project Lead, UX, &amp;amp; UI Designer: &lt;a href=&#34;https://twitter.com/klsyjnn&#34;&gt;Kelsey Smith&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Design Direction: &lt;a href=&#34;https://twitter.com/ameellio&#34;&gt;Ame Elliott&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Brand Designer: &lt;a href=&#34;https://www.guillelasarte.com/&#34;&gt;Guille Lasarte&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Concept &amp;amp; Implementation: &lt;a href=&#34;https://nex.sx/&#34;&gt;Claudio Guarnieri&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>HR Consultant</title>
      <link>https://superbloom.design/community/opportunities/hr_consultant/</link>
      <pubDate>Fri, 04 Jun 2021 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/opportunities/hr_consultant/</guid>
      <description>&lt;h2 id=&#34;apply-to-be-our-hr-consultant&#34;&gt;Apply to be our HR Consultant&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;We’re looking for an experienced HR professional to help us design and implement an equitable and competitive compensation strategy that serves our distributed international team, and consult on our key policy requirements.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You’ll advise our Operations team and Managing Director on the administration of human resources policies and procedures.&lt;/li&gt;
&lt;li&gt;You’ll lead competitive salary analysis on job levels for US and international roles.&lt;/li&gt;
&lt;li&gt;You’ll help us design and implement a performance evaluation and promotion process, to build internal cohesion and stability for the long term.&lt;/li&gt;
&lt;li&gt;This is a part-time 3-month contract for USD $10,000.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;About us&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We are a small US 501(c)3 nonprofit organization, founded in 2014 with the goal of increasing security and usability in technology tools. Our team is spread out across the US and the EU, and we support technologists around the world. We&amp;rsquo;ve contributed design to a variety of tools that enhance security, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; and &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We&amp;rsquo;ve held &lt;a href=&#34;https://superbloom.design/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we&amp;rsquo;ve done a lot more than usable security. Just in the last year, we&amp;rsquo;ve launched a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;p&gt;We’re also working through an open rebranding process, potentially moving away from the name “Simply Secure” and toward an identity that more accurately reflects the diversity of the work we do. &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;Learn more on our blog.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;About you&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You have extensive experience as an HR professional working in the US 501(c)3 non-profit sector.&lt;/li&gt;
&lt;li&gt;You bring expertise and knowledge of compensation surveys and design in different markets to create equity across the organization.&lt;/li&gt;
&lt;li&gt;You have experience in designing and implementing a meaningful performance evaluation process that is appropriate for small organizations.&lt;/li&gt;
&lt;li&gt;You’re a team player with excellent communication and leadership skills&lt;/li&gt;
&lt;li&gt;You’re comfortable working with a distributed team.&lt;/li&gt;
&lt;li&gt;You are able to manage a balance of strategic planning and tactical execution.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Nice to Have&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Experience with researchers and UX designers working on human-centered design, design thinking, service design, or participatory research (specifically field research).&lt;/li&gt;
&lt;li&gt;Knowledgeable about one or more of the following areas: open source software, internet freedom, tech criticism and activism, human rights technology.&lt;/li&gt;
&lt;li&gt;Comfortable with collaborative work tools (we currently use Notion, Miro, and Google Suite).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Sound like a good fit?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Please send us:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Updated resume or CV&lt;/li&gt;
&lt;li&gt;Your responses to the following 2 questions:
&lt;ul&gt;
&lt;li&gt;What are your first 5 questions to help you develop an equitable compensation package for teams across countries, where some have generous social benefits and others are dependent on their employers? (250 words max)&lt;/li&gt;
&lt;li&gt;What do you think are the pros and cons of 360 performance evaluations vs manager-only performance reviews? (250 words max)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Send these documents to &lt;a href=&#34;mailto:hr@superbloom.design&#34;&gt;hr@superbloom.design&lt;/a&gt; by Sept 30th.&lt;/p&gt;
&lt;p&gt;We believe that systemic bad behaviors disproportionately hurt the most marginalized people in society — including people of color, people from working class backgrounds, women and LGBTQ people. We believe that these communities must be centered in the work we do. We strongly encourage applications from people with these identities or who are members of other marginalized communities.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Web Monetization: A Report on Barriers to Adoption</title>
      <link>https://superbloom.design/learning/blog/barriers-to-web-monetization/</link>
      <pubDate>Fri, 28 May 2021 17:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/barriers-to-web-monetization/</guid>
      <description>&lt;ul&gt;
&lt;li&gt;The &lt;a href=&#34;https://webmonetization.org/&#34;&gt;Web Monetization API&lt;/a&gt; has the potential to create a viable alternative to targeted advertising as a means for website content creators to generate revenue.&lt;/li&gt;
&lt;li&gt;Widespread adoption of this innovative technology is currently slow, however, due to common questions surrounding onboarding, explanation, and integration.&lt;/li&gt;
&lt;li&gt;As part of our &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;Decentralization Off The Shelf&lt;/a&gt; project (and with support from &lt;a href=&#34;https://www.grantfortheweb.org/&#34;&gt;Grant for the Web&lt;/a&gt;), our team conducted in-depth design research and prepared a &lt;a href=&#34;https://decentpatterns.xyz/projects/web-monetization/&#34;&gt;report&lt;/a&gt; highlighting common questions and challenges encountered by end users, and offering recommendations for opportunities to increase web monetization adoption in the future.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Ads have been with us since the early beginnings of the internet and are not going away anytime soon. Be it pop-ups or mass targeted advertising, advertising has created a series of societal and safety issues, ranging from coordinated misinformation campaigns to unreadable mobile UIs. Yet as the public discourse shifts toward finding better ways to pay creators, ads remain the dominant monetization model on the web. Despite the introduction of dangerous dark patterns, many users have no choice but to continue to tolerate the internet’s current ad-based structure in an un-bargained-for and unequal exchange to access purportedly “free” information.&lt;/p&gt;
&lt;p&gt;In response, &lt;a href=&#34;https://www.grantfortheweb.org/&#34;&gt;Grant for the Web&lt;/a&gt; (GftW) was created to help find a better way to monetize online content while respecting open standards and individual rights. As part of GftW’s efforts, the Simply Secure team behind &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;Decentralization Off The Shelf&lt;/a&gt; (an open design project supporting practitioners in decentralization through interface, content, and service design) received funding in late 2020 to examine the current barriers to adoption for the Web Monetization API and identify opportunities to help increase adoption and mitigate end-user issues. The ultimate goal? Improved UX for an early-stage API seeking to offer creators the ability to get paid for web traffic without employing targeted advertising.&lt;/p&gt;
&lt;h2 id=&#34;identifying-obstacles&#34;&gt;Identifying Obstacles&lt;/h2&gt;
&lt;p&gt;The &lt;a href=&#34;https://webmonetization.org/&#34;&gt;Web Monetization API&lt;/a&gt; is an innovative proposal for a W3C Standards that has the potential to create a viable alternative to targeted advertising. It offers a piece of technology that has up to this point been absent in web browsers: the ability for users to transfer miniscule amounts of money as an ad-free means to compensate websites and their creators. Yet despite this promising possibility, confusion and significant barriers to adoption remain on behalf of both the sender and receiver of payments. Accordingly, our expert research and design team set out to identify common obstacles and offer solutions to increase and ease adoption.&lt;/p&gt;
&lt;p&gt;In investigating the API’s UX, we spoke with creators, consumers, and developers to better understand their respective barriers to adoption. After learning more about the design patterns that already exist in the space, and unpacking security risks posed to end-users, we then partnered with designers to rethink ways to represent this web monetization model.&lt;/p&gt;
&lt;p&gt;As part of our efforts to &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;develop better UX patterns for decentralization&lt;/a&gt;, we identified recurring UX issues in decentralization that also make an appearance in the Web Monetization API’s decentralized protocol. Because decentralized technologies are often new and complex, and early adopters often find them difficult to understand and navigate, the design problems faced by the Web Monetization API are highly generalizable. Common UX questions encountered include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How is the new technology explained? What mental models can be used (or re-used)?&lt;/li&gt;
&lt;li&gt;Who is doing the explaining (and when)? Are they the right people?&lt;/li&gt;
&lt;li&gt;How do you integrate a new technology into a familiar ecosystem (e.g. web browser) and make it natural and usable?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;offering-solutions&#34;&gt;Offering Solutions&lt;/h2&gt;
&lt;p&gt;After identifying these questions and other common barriers to adoption, our team developed a set of general recommendations to help reduce user confusion, increase transparency, and improve overall retention rates. In doing so, we organized our recommendations by target user group. For example:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Streaming platforms such as Coil should:&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Enhance subscription transparency.&lt;/strong&gt; Provide real-time feedback in the streaming platform website (for creators) and in the web extension (for audience members).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Creators who want to use Web Monetization should:&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Provide an ad-free option.&lt;/strong&gt; Offer users a button that provides the option to “Remove advertisements” as either a banner ad or a blocking pop-up.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Maintainers of the Web Monetization API and Interledger Protocol should:&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Remember developers are users.&lt;/strong&gt; Mobile and desktop applications that support payee-payer relationships on their platforms could be potential early adoption partners if they are targeted and curated through better communication and transparency.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To learn more about the barriers to adoption for the Web Monetization API, or see the full list of our specific recommendations, head over to our project page and check out our &lt;a href=&#34;https://decentpatterns.xyz/projects/web-monetization/&#34;&gt;report and accompanying zine&lt;/a&gt;. It is our hope that the issues identified in our research will be addressed over time through improved documentation, quality control, and increased buy-in from major browsers. Our recommendations are ultimately intended to be a first step in the complex process of achieving a more equitable and less economically invasive internet.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://decentpatterns.xyz/projects/web-monetization/&#34; class=&#34;button button--secondary read-more&#34; style=&#34;text-decoration: none;&#34;&gt;Read the full report&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;Project Leads: Rae McKelvey and Ngọc Triệu&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Call for proposals: Regional partners, funder&#39;s toolkit</title>
      <link>https://superbloom.design/community/opportunities/regional_partners/</link>
      <pubDate>Fri, 07 May 2021 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/opportunities/regional_partners/</guid>
      <description>&lt;h2 id=&#34;the-deadline-for-applying-to-this-role-has-passed&#34;&gt;The deadline for applying to this role has passed.&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;We&amp;rsquo;re looking for 5-7 regional partners to help us produce localized and contextualized tools for funders looking to support open source digital infrastructure.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You&amp;rsquo;ll bring familiarity with funders in your region, and work with our team to ensure the toolkit meets the needs of those funders.&lt;/li&gt;
&lt;li&gt;This is a 6-month freelance contract, from approximately mid-June to mid-December 2021. Each contract pays USD $3,000.&lt;/li&gt;
&lt;li&gt;We are a US 501(c)3 organization. We can contract in many countries, and are limited by the &lt;a href=&#34;https://ofac.treasury.gov/faqs/10&#34;&gt;OFAC sanctions list&lt;/a&gt;. We can pay in currencies supported by &lt;a href=&#34;https://wise.com/gb/multi-currency-account/#coverage&#34;&gt;Transferwise&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;About the project:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Simply Secure is working on a grant-supported Digital Infrastructure Funders’ Toolkit project. We&amp;rsquo;re creating a set of resources for funders around the world who are interested in supporting digital infrastructure and open source technologies but may not yet know how to approach the topic. Funders might include private foundations, government programs, corporations, and high net worth individuals. Our goal is to provide tools for better funding processes in this topic area, and ultimately impact the sustainability of open source and foundational software, keep standards and protocols interoperable and up-to-date, and create a more resilient and secure digital infrastructure.&lt;/p&gt;
&lt;p&gt;We believe it is important to acknowledge that regions, languages, and governments articulate and understand “infrastructure” in very different ways. The creation of a regional team of non-US / non-EU researchers will ensure we capture and share these nuances, and offer a more global understanding of the needs, wants, and opportunities in service to this work.&lt;/p&gt;
&lt;p&gt;To that end, we are looking for 5-7 regional partners who can help us identify, connect, interview, and create region-specific portions of the funding tools. Partners who have expertise and connections in the digital funding ecosystem in the following regions are encouraged to apply:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Eastern Asia&lt;/li&gt;
&lt;li&gt;South Eastern Asia&lt;/li&gt;
&lt;li&gt;South Asia&lt;/li&gt;
&lt;li&gt;Australia and New Zealand&lt;/li&gt;
&lt;li&gt;Arabic-speaking Middle East&lt;/li&gt;
&lt;li&gt;Eastern Africa&lt;/li&gt;
&lt;li&gt;Western Africa&lt;/li&gt;
&lt;li&gt;Southern Africa&lt;/li&gt;
&lt;li&gt;Central America&lt;/li&gt;
&lt;li&gt;South America&lt;/li&gt;
&lt;li&gt;Global&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Each contract is a short-term contract for USD $3,000 running from June 2021 to December 2021, with specific deliverables and milestones throughout. These include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Identify relevant funders&lt;/li&gt;
&lt;li&gt;Conduct interviews with funders (and potentially some of their grantees)&lt;/li&gt;
&lt;li&gt;Facilitate 1-2 workshops&lt;/li&gt;
&lt;li&gt;Manage localizing information, and&lt;/li&gt;
&lt;li&gt;Lead production of locally, contextually relevant resources to include in the toolkit.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Our team is happy to support regional partners with interview methodology, workshop planning, scheduling, and general problem-solving as needed. We expect this to take between 60-80hrs max.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;About us&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We are a small US 501(c)3 nonprofit organization, founded in 2014 with the goal of making security tools easier to use. We believed – and still do – that security doesn&amp;rsquo;t have to be confusing to end users. We&amp;rsquo;ve contributed design to a variety of tools that enhance security, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; and &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We&amp;rsquo;ve held &lt;a href=&#34;https://superbloom.design/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we&amp;rsquo;ve done a lot more than usable security. Just in the last year, we&amp;rsquo;ve launched a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;About you&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You understand the power of open source technologies to drive societal change.&lt;/li&gt;
&lt;li&gt;You&amp;rsquo;ve worked with funders in your region and can work with them to advise them on their portfolios.&lt;/li&gt;
&lt;li&gt;You like working independently, in collaboration with a fully remote team.&lt;/li&gt;
&lt;li&gt;You&amp;rsquo;re comfortable conducting interviews and facilitating (virtual) workshops.&lt;/li&gt;
&lt;li&gt;You can either translate or manage the translation of some resources.&lt;/li&gt;
&lt;li&gt;You have flexibility in your schedule to meet with a global team at times that work for everyone.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Sound like a good fit?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Please send us:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;(for individuals) An updated resume or CV.&lt;/li&gt;
&lt;li&gt;(for organizations) Please tell us why your organization is the right fit, share relevant work with explanations, and list the names and brief bios of the people who will be working on this project.&lt;/li&gt;
&lt;li&gt;Your responses to the following questions:
&lt;ul&gt;
&lt;li&gt;How do you define &lt;em&gt;digital infrastructure&lt;/em&gt;? Why is it important, and what potential does it have for society? (250 words max)&lt;/li&gt;
&lt;li&gt;What is the role of philanthropy in supporting the development, maintenance, and usage of digital infrastructure? (250 words max)&lt;/li&gt;
&lt;li&gt;How do funders in your region or communities address the topic of digital infrastructure? Please describe your impact and/or experience working with them on this topic. (250 words max)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Send these documents to Nicola Pratt at nicola [ at ] superbloom [ dot ] design as soon as possible.&lt;/p&gt;
&lt;p&gt;We believe that systemic bad behaviors disproportionately hurt the most marginalized people in society — including people of color, people from working class backgrounds, women and LGBTQ people. We believe that these communities must be centered in the work we do. We strongly encourage applications from people with these identities or who are members of other marginalized communities.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>MozFest 2021 - Will we see you there?</title>
      <link>https://superbloom.design/learning/blog/mozfest-2021-will-we-see-you-there/</link>
      <pubDate>Fri, 05 Mar 2021 16:54:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/mozfest-2021-will-we-see-you-there/</guid>
      <description>&lt;p&gt;Interested in Decentralization? Want to learn more about the last 5 years of Mozilla’s Fellowships &amp;amp; Awards Programs? Have a project you are stuck on and want to collaborate in a design sprint or get quick UX feedback? &lt;/p&gt;
&lt;p&gt;Over the next 2 weeks, Simply Secure will be hosting five sessions at the first virtual Mozilla Festival. If you’ll be there, we’d love to see you, learn about your work, and collaborate. Come join us!&lt;/p&gt;
&lt;p&gt;You can register for MozFest &lt;a href=&#34;https://www.mozillafestival.org/&#34;&gt;here&lt;/a&gt;, and below are links to each of the sessions.&lt;/p&gt;
&lt;h3 id=&#34;zine-making-explain-decentralization-to-me&#34;&gt;Zine-making: Explain Decentralization To Me&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/QT9W7X-1&#34;&gt;https://schedule.mozillafestival.org/session/QT9W7X-1&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;When: March 10 @ 12 - 1 PM EST; 6 - 7 PM CET&lt;/li&gt;
&lt;li&gt;Decentralization means something different to everyone but what does it mean to you? Join the Decentralization Off The Shelf (DOTS) team in a search for meanings in the decentralized world through creativity and the art of zine-making. This workshop is suitable for designers, developers, learners, and anyone who is curious about how the world functions and wishes to tell their stories. The workshop consists of three parts: 1. DOTS interpretation of decentralization and a short introduction to zine-making 2. Zine-making: A collective interpretation of ‘decentralization’ and individual workspace 3. Online exhibition: Learning and sharing The workshop will be conducted via Figma and Zoom.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;pattern-library-when-designer-meets-developer&#34;&gt;Pattern Library: When Designer Meets Developer&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/3PJAZG-1&#34;&gt;https://schedule.mozillafestival.org/session/3PJAZG-1&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;When: March 12 @ 12-1 PM EST; 6 - 7 P CET&lt;/li&gt;
&lt;li&gt;Design does not hold the key to all the problems out there, but it might help unblock your &amp;ldquo;stuckness&amp;rdquo; and bring new perspectives. Take part in our speed-dating-like session where your decentralized tech problem might just find its perfect design-pattern match. To participate, please bring at least one problem that you are currently struggling with (it doesn’t have to be a technical one), wear a smile, and keep your mind wide open. The good thing is, unlike Tinder, the possibilities are endless. The session will be conducted via Zoom and Miro. It consists of three parts: 1. Check-in and Introduction 2. Problem-Pattern Matching 3. Sharing and Learning.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;fellowships--awards-evaluation-community-workshop&#34;&gt;Fellowships &amp;amp; Awards Evaluation Community Workshop&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/LBBMAY-1&#34;&gt;https://schedule.mozillafestival.org/session/LBBMAY-1&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;When: March 16 @ 1-2pm EST; 6 - 7 PM CET&lt;/li&gt;
&lt;li&gt;Starting in November 2020, Mozilla Foundation started an evaluation of the Fellowships and Awards programs with the support of Simply Secure. The evaluation seeks to understand the program’s strengths and challenges with the goal of improving their efficacy and impact. Community input and guidance is critical to this process, and so as part of the evaluation, we engaged past participants in the programs, funders, host organizations, community members and other stakeholders. At MozFest, we are excited to share some preliminary findings with the community and get feedback as we finalize outputs to share publicly. Please come and share your thoughts, reactions and ideas.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;design-sprint-reimagining-ux-patterns-to-address-ai--surveillance-capitalism-harms&#34;&gt;Design Sprint: Reimagining UX Patterns to address AI &amp;amp; Surveillance Capitalism harms &lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/KFSQ9J-1&#34;&gt;https://schedule.mozillafestival.org/session/KFSQ9J-1&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;When: March 17 @ 1-3pm EST; 6 -7 PM CET&lt;/li&gt;
&lt;li&gt;Simply Secure and the broader Human Rights Centered Design (HRCD) Community would like to host a workshop / design sprint where we invite participants to workshop UX and design ideas in response to the everyday harms caused by AI and surveillance capitalism on internet platforms. At the workshop, participants will have the option of working alone or in groups on a variety of issue areas, e.g. consent, transparency, remediation experiences (e.g. in response to content moderation or online harassment issues) and many more! The session will be very generative with the goal being to create a final collaborative output of ideas to challenge the norms around current user experience patterns.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;ux--design-speed-dating-clinic&#34;&gt;UX &amp;amp; Design Speed Dating Clinic&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://schedule.mozillafestival.org/session/RNJLZF-1&#34;&gt;https://schedule.mozillafestival.org/session/RNJLZF-1&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;When: March 18 @ 2:15 - 3:15 PM EST; 7:15PM - 8:15 PM CET&lt;/li&gt;
&lt;li&gt;Stuck on how to build or communicate a feature? Not sure how to get user feedback? Want to brainstorm some design alternatives for your tool or process? Thinking about how to engage users in your design process? Then this workshop is for you! In the session, participants will have the opportunity to meet with design and usability practitioners in the community. We will set up 10-15 minute &amp;ldquo;speed dating&amp;rdquo; time slots and allow participants to rotate through the presenters so that they can get feedback from multiple perspectives on whatever design and UX challenges they bring to share. Participants should bring something to share their work with the UX practitioners (an idea, a problem to work on, design sketches, a prototype, whatever stage you are at! etc), and will leave with feedback, designs, tools, strategies, and follow up opportunities to get support in their work.&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Call for Proposals — Brand Designer</title>
      <link>https://superbloom.design/community/opportunities/identity-designer-cfp/</link>
      <pubDate>Mon, 11 Jan 2021 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/community/opportunities/identity-designer-cfp/</guid>
      <description>&lt;p&gt;&lt;strong&gt;We’re looking for a designer to create a new visual identity for Simply Secure (name change is on the way!).&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Application deadline: January 21, 2021&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&#34;the-project&#34;&gt;The project&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;We’re looking for a designer to create a new brand identity for Simply Secure. In summer 2020, we decided that we needed a new name and a new identity in order to continue doing, and communicating, our work effectively.&lt;/li&gt;
&lt;li&gt;Instead of doing this work internally, or engaging an external partner to create our identity for us, we are leveraging a &lt;strong&gt;co-design process&lt;/strong&gt;. With support and mentorship from Una Lee of &lt;a href=&#34;https://www.andalsotoo.net/&#34;&gt;And Also Too&lt;/a&gt;, we’ve engaged an advisory committee composed of a diverse group of people from our community who know our work and are invested in our future to help. We’ve also engaged our broader community for feedback, and &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;shared about the process as well as what we&amp;rsquo;ve heard so far on our blog&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;We expect you to build off our current identity redesign process by proposing a visual identity based on our new design brief, and then developing a brand book and design system.&lt;/li&gt;
&lt;li&gt;You’ll propose, create, and deliver an identity and design system including but not limited to:
&lt;ul&gt;
&lt;li&gt;Brand book
&lt;ul&gt;
&lt;li&gt;Personality&lt;/li&gt;
&lt;li&gt;Tone&lt;/li&gt;
&lt;li&gt;Brand story&lt;/li&gt;
&lt;li&gt;Brand metaphor&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Design system
&lt;ul&gt;
&lt;li&gt;Logo, Logotype&lt;/li&gt;
&lt;li&gt;Typography&lt;/li&gt;
&lt;li&gt;Type scale&lt;/li&gt;
&lt;li&gt;Color palette&lt;/li&gt;
&lt;li&gt;Imagery&lt;/li&gt;
&lt;li&gt;Examples of application&lt;/li&gt;
&lt;li&gt;Guidelines for usage (dos and don’ts) including guidelines for accessibility&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Templates
&lt;ul&gt;
&lt;li&gt;Social media graphics&lt;/li&gt;
&lt;li&gt;Slide deck template&lt;/li&gt;
&lt;li&gt;Document templates (letterhead, report template for clients, case study template for public)&lt;/li&gt;
&lt;li&gt;Business card design&lt;/li&gt;
&lt;li&gt;Merchandise, e.g. stickers&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;timeline&#34;&gt;Timeline&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;This is a time-limited contract, starting in &lt;strong&gt;late January 2021&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;One of our next workshops is scheduled for &lt;strong&gt;February 4 at 2-4pm ET / 8-10pm CET&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;In addition, there will be 1-2 co-design workshops in &lt;strong&gt;late winter/early spring 2021&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;We expect, and hope, the overall process to be finished by &lt;strong&gt;summer 2021&lt;/strong&gt;. However, since this project has many stakeholders, we can be flexible with timing. Even if this timing doesn’t work exactly for you, if this seems like the right project for you, please get in touch.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;about-us&#34;&gt;About us&lt;/h3&gt;
&lt;p&gt;We are a small US 501(c)3 nonprofit organization, founded in 2014 with the goal of making security tools easier to use. We believed – and still do – that security doesn&amp;rsquo;t have to be confusing to end users. We&amp;rsquo;ve contributed design to a variety of tools that enhance security, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We&amp;rsquo;ve held &lt;a href=&#34;https://superbloom.design/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we&amp;rsquo;ve done a lot more than usable security. Just in the last year, we&amp;rsquo;ve launched a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;h3 id=&#34;about-you&#34;&gt;About you&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You love designing identity systems and understand how to wield their power. You get really excited about using imagery, color, layout, and type to tell a visual story.&lt;/li&gt;
&lt;li&gt;You design expressive and accessible screens, logos, and colors, meant to be viewed on the web.&lt;/li&gt;
&lt;li&gt;You like working independently, in collaboration with a fully remote team.&lt;/li&gt;
&lt;li&gt;You are comfortable advocating for yourself and your work to make sure that you’re getting what you need from us.&lt;/li&gt;
&lt;li&gt;You are excited about being part of our community-driven design approach. You think it will be fun and interesting to use these workshops as part of your process. It&amp;rsquo;s okay with you that we are coming up with a new name in parallel with creating a visual identity.&lt;/li&gt;
&lt;li&gt;You are able to meet with us during our core hours of 2pm to 6pm Central European Time / 8am to 6pm Eastern Time / 7am to 3pm Pacific Time.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;nice-to-have&#34;&gt;Nice to have&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Awareness of one or more of the following areas: open source software, internet freedom, tech criticism and activism, human rights&lt;/li&gt;
&lt;li&gt;Experience with, and/or interest in learning more about, co-design processes&lt;/li&gt;
&lt;li&gt;Expert in communicating with international audiences&lt;/li&gt;
&lt;li&gt;Knowledge of accessibility standards&lt;/li&gt;
&lt;li&gt;Experience with, and/or interest in, naming organizations&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;sound-like-a-good-fit&#34;&gt;Sound like a good fit?&lt;/h3&gt;
&lt;p&gt;Please send us:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;3-5 examples of your work. Please highlight the projects with turn-around times of 3-6 months and tell us about the &lt;strong&gt;timeline and process&lt;/strong&gt;: how did these projects get created? Who was involved, what did the process look like, how long did it take?&lt;/li&gt;
&lt;li&gt;A (very short!) outline of how you would approach working with us on this project. What phases would this project have, and what would you need from us to make it successful? (We are not looking for design directions yet, so please don&amp;rsquo;t feel the need to pitch us any suggestions. We&amp;rsquo;ll need some time together to bring you up to speed on our co-design process and our design brief.)&lt;/li&gt;
&lt;li&gt;1-2 references. References will be contacted in the last phase of application review.&lt;/li&gt;
&lt;li&gt;The times you are available for meetings within our core hours.&lt;/li&gt;
&lt;li&gt;An estimated budget for the project.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Send these documents to &lt;a href=&#34;mailto:jobs-brand@superbloom.design&#34;&gt;jobs-brand@superbloom.design&lt;/a&gt;. We will be reviewing applications on a rolling basis. We will stop accepting applications on January 21, 2020.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;If you intend to submit a proposal, but are unable to do so by the deadline, please reach out to us.&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Goodbye 2020, Hello 2021</title>
      <link>https://superbloom.design/learning/blog/goodbye-2020-hello-2021/</link>
      <pubDate>Thu, 31 Dec 2020 18:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/goodbye-2020-hello-2021/</guid>
      <description>&lt;p&gt;2020 was certainly different and harder than we all anticipated. Despite the challenges that 2020 brought, the team at Simply Secure has done some amazing work, while also taking time to reflect and grow. We couldn’t have done this without support, collaboration, and solidarity from our community.&lt;/p&gt;
&lt;p&gt;In 2021, you can expect to see some changes — including new team members and a &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;new identity for Simply Secure&lt;/a&gt;, to match how we’ve grown since our inception! We’re hoping to expand on our work supporting consent, diversity and equity, human rights and infrastructure, as well as our growing portfolio of work around program design for supporting and funding trustworthy technology. We plan to continue working with individuals, projects, communities, and funders to  build and inform technology, resources and programs that protect people’s dignity, safety and privacy.&lt;/p&gt;
&lt;h2 id=&#34;2020-highlights&#34;&gt;2020 Highlights&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;We supported the launch of our first fiscally sponsored project, led by &lt;a href=&#34;https://superbloom.design/about/people/cade&#34;&gt;Cade Diehm&lt;/a&gt;, the &lt;a href=&#34;https://newdesigncongress.org/&#34;&gt;New Design Congress&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Alongside Internews, EFF, and Access Now, we hosted monthly convenings, since February 2020, with the &lt;a href=&#34;http://hrcd.pubpub.org/&#34;&gt;Human Rights Centered Design community&lt;/a&gt;, covering topics for practitioners ranging from contract tracing applications to trauma informed design.&lt;/li&gt;
&lt;li&gt;In June 2020, we launched a new report &lt;a href=&#34;https://superbloom.design/learning/blog/decentralization-off-the-shelf-7-maxims&#34;&gt;Decentralization Off The Shelf: 7 Maxims&lt;/a&gt; (DOTS) covering the key changes needed for decentralized technology to gain adoption through easing the developer ecosystem and improving the user experience.&lt;/li&gt;
&lt;li&gt;We worked closely with the &lt;a href=&#34;https://twitter.com/brainwane/status/1202375339332296704&#34;&gt;Python PIP CLI&lt;/a&gt; team to address usability issues with pip and support the development and rollout of a significant new feature — an improved version of the dependency resolver.&lt;/li&gt;
&lt;li&gt;With support from the &lt;a href=&#34;http://opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;, we have been working to improve the &lt;a href=&#34;https://metrics.torproject.org/&#34;&gt;Tor Metrics&lt;/a&gt; data platform, &lt;a href=&#34;https://superbloom.design/learning/blog/globaleaks-case-study&#34;&gt;GlobaLeaks whistleblower platform&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2Ps usability&lt;/a&gt;, and we’ve been working directly with OTF to &lt;a href=&#34;https://www.opentech.fund/news/new-otf-application-form/&#34;&gt;improve their funding application design and process&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;In partnership with &lt;a href=&#34;https://www.mozilla.org/en-US/moss/&#34;&gt;Mozilla’s Open Source Support&lt;/a&gt; (MOSS) program, we developed a plan to improve their website and clarify their program offerings, and are building on that work to support an impact evaluation of the MOSS program since 2015.&lt;/li&gt;
&lt;li&gt;Building on work from 2016-2018, we are working with &lt;a href=&#34;https://internews.org/&#34;&gt;Internews&lt;/a&gt; to improve the feedback loops between end users, trainers, and software development teams through capacity building and support during a new phase of the &lt;a href=&#34;http://usable.tools/&#34;&gt;USABLE&lt;/a&gt; program. This included hosting a month long convening in August 2020 — &lt;a href=&#34;https://usable.tools/axis2020/&#34;&gt;AXIS: A Global Feedback Exchange for Trainers, Auditors, Developers, and Designers&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Through our partnership with &lt;a href=&#34;https://codeforscience.org/&#34;&gt;Code for Science &amp;amp; Society&lt;/a&gt;, we have continued to work with &lt;a href=&#34;https://prereview.org/&#34;&gt;PREreview&lt;/a&gt; and &lt;a href=&#34;https://www.measurementlab.net/&#34;&gt;Measurement Lab&lt;/a&gt;. With &lt;a href=&#34;https://prereview.org/&#34;&gt;PREreview&lt;/a&gt;, we are supporting and helping to lead a significant technical overhaul merging two of their current code bases into one that is more accessible to open source contributions. We are also currently starting a project to explore and co-design improvements to the platform to better support underrepresented communities in science. We completed a &lt;a href=&#34;https://superbloom.design/learning/blog/data-decision-making-design-measuring-internet-performance-for-libraries-and-the-public-sector&#34;&gt;project with Measurement Lab&lt;/a&gt; around supporting libraries with open internet measurement data and tools. &lt;/li&gt;
&lt;li&gt;Supported by &lt;a href=&#34;http://reset.tech/&#34;&gt;Reset.Tech&lt;/a&gt; and others, we have been working with a number of different projects related to mis- and disinformation data collection, supporting research, policy engagement and active intervention around online harms, including &lt;a href=&#34;https://superbloom.design/learning/resources/popping-the-filter-bubble-design-practices-for-data-donation&#34;&gt;Algorithms Exposed&lt;/a&gt;, &lt;a href=&#34;https://docs.digiresilience.org/waterbear/&#34;&gt;CDR’s Waterbear Link&lt;/a&gt;, &lt;a href=&#34;https://www.junkipedia.org/&#34;&gt;Junkipedia&lt;/a&gt;, &lt;a href=&#34;https://meedan.com/check&#34;&gt;Meedan’s Check&lt;/a&gt;, &lt;a href=&#34;&#34;&gt;Mozilla’s Ion Project&lt;/a&gt;, and &lt;a href=&#34;https://themarkup.org/citizen-browser&#34;&gt;The Markup’s Citizen Browser&lt;/a&gt;. Additionally we are supporting efforts to work on platform accountability collectively through workshops with the organizations like &lt;a href=&#34;https://www.consumerreports.org/social-media/social-media-misinformation-policies/&#34;&gt;Consumer Reports&lt;/a&gt;, &lt;a href=&#34;https://pen.org/the-first-wave-social-media-platforms-responding-to-covid-19/&#34;&gt;PEN America&lt;/a&gt; and &lt;a href=&#34;https://docs.google.com/document/d/1-b5b_AgJhz7rAXaSpekwBwZWHx_A7iSleoOGxK0lZto/edit#&#34;&gt;Mozilla&lt;/a&gt; around platform data needed for transparency and advocacy initiatives.&lt;/li&gt;
&lt;li&gt;We supported the Implicit Development research team in their work evaluating the needs of FOSS communities working on digital infrastructure in the public interest. Read more in their final report: &lt;a href=&#34;https://recommendations.implicit-development.org/&#34;&gt;Roadwork Ahead&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Coming out of the Sustain Convening in January 2020, we helped launch a &lt;a href=&#34;https://sustainoss.org/working-groups/design-and-ux/&#34;&gt;working group focused on UX &amp;amp; Design in open source&lt;/a&gt;, which has been meeting monthly to collaborate on resources and coordinate around community needs for sustaining open source through user experience and design.&lt;/li&gt;
&lt;li&gt;We supported the rapid response effort to &lt;a href=&#34;http://saveinternetfreedom.tech/&#34;&gt;Save Internet Freedom Tech&lt;/a&gt; alongside many organizations and individuals in the community fighting to protect internet freedom.&lt;/li&gt;
&lt;li&gt;We spoke, supported, and helped organize over 20 workshops and talks at events like &lt;a href=&#34;https://fosdem.org/&#34;&gt;FOSDEM&lt;/a&gt;, &lt;a href=&#34;https://interaction20.ixda.org/&#34;&gt;Interaction20&lt;/a&gt;, &lt;a href=&#34;https://sustainoss.org/&#34;&gt;SustainOSS&lt;/a&gt;, &lt;a href=&#34;https://moinworld.de/en/&#34;&gt;Moin World Women Tech Makers&lt;/a&gt;, &lt;a href=&#34;https://global.georgetown.edu/georgetown_units/beeck-center-for-social-impact-and-innovation&#34;&gt;Beeck Center&lt;/a&gt;, &lt;a href=&#34;https://mydata.org/&#34;&gt;MyData&lt;/a&gt;, &lt;a href=&#34;https://interactiondesignday.org/&#34;&gt;World Interaction Design Day&lt;/a&gt;, &lt;a href=&#34;https://datanatives.io/&#34;&gt;Data Natives&lt;/a&gt;, the &lt;a href=&#34;https://www.hiig.de/en/&#34;&gt;HIIG&lt;/a&gt;, &lt;a href=&#34;https://www.rightscon.org/&#34;&gt;RightsCon&lt;/a&gt;, &lt;a href=&#34;https://www.breadandnet.org/en/&#34;&gt;Bread &amp;amp; Net&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/search?q=ShareTheMicInCyber&amp;amp;src=typed_query&#34;&gt;#ShareTheMicInCyber&lt;/a&gt;, and joined coalitions such as the &lt;a href=&#34;https://www.iwmf.org/coalition-on-online-abuse/&#34;&gt;Coalition on Online Abuse&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Looking forward to reconnecting with all of you in 2021.&lt;/p&gt;
&lt;p&gt;In solidarity — Georgia &amp;amp; the team at Simply Secure&lt;/p&gt;
&lt;p&gt;-&amp;ndash;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/support-us/&#34;&gt;Donate to support our work&lt;/a&gt; via &lt;a href=&#34;https://www.paypal.com/donate/?token=SeIKuUPaIZoWy469U2tcPvdsYy4Ptwjkg6omagjfRk9kzg02gV9f3FK5-Itwv_UHTF1PIG&amp;amp;country.x=US&amp;amp;locale.x=US&#34;&gt;Paypal&lt;/a&gt;, &lt;a href=&#34;https://opencollective.com/underexposed&#34;&gt;OpenCollective&lt;/a&gt; or check. If your employer uses &lt;a href=&#34;https://causes.benevity.org/causes/840-472462310?lang=en&#34;&gt;Benevity&lt;/a&gt;, please consider setting up a match or a recurring donation. Follow us on &lt;a href=&#34;http://twitter.com/simplysecureorg&#34;&gt;Twitter&lt;/a&gt;, &lt;a href=&#34;http://facebook.com/simplysecureorg/&#34;&gt;Facebook&lt;/a&gt;, &lt;a href=&#34;https://www.linkedin.com/company/simplysecureorg/&#34;&gt;LinkedIn&lt;/a&gt;, &lt;a href=&#34;http://instagram.com/simplysecure/&#34;&gt;Instagram&lt;/a&gt; and &lt;a href=&#34;https://medium.com/simply-secure&#34;&gt;Medium&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Design for Data Journalism: A Case Study</title>
      <link>https://superbloom.design/learning/blog/design-for-data-journalism-a-case-study/</link>
      <pubDate>Mon, 14 Dec 2020 09:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/design-for-data-journalism-a-case-study/</guid>
      <description>&lt;h2 id=&#34;the-project&#34;&gt;The Project&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;http://occrp.org&#34;&gt;OCCRP&lt;/a&gt;, the Organized Crime and Corruption Reporting Project, is a nonprofit that enables &amp;ldquo;follow the money&amp;rdquo; journalism all over the world. They&amp;rsquo;re an invaluable resource for training and supporting journalists who do the dangerous, unpopular work of bringing the shadowy side of international finance to light.&lt;/p&gt;
&lt;p&gt;One tool that OCCRP maintains is &lt;a href=&#34;http://alephdata.org&#34;&gt;Aleph&lt;/a&gt;. Aleph is an open-source portal for exploring datasets related to journalistic investigations into businesses, especially corruption, money laundering, and organized crime. It&amp;rsquo;s a key tool for many journalists, both freelance and newsroom, working on these and related issues.&lt;/p&gt;
&lt;p&gt;The team that maintains Aleph approached us looking for help   with the user experience design of the data portal. They knew it was difficult to use, and they knew that some fundamental aspects of the information architecture and UI needed clarifying, but they weren&amp;rsquo;t yet sure what or how, making this challenge a perfect fit for our human-centered design approach. We rolled up our sleeves and jumped in.&lt;/p&gt;
&lt;h2 id=&#34;the-process&#34;&gt;The Process&lt;/h2&gt;
&lt;p&gt;The research phase started with 5 exploratory interviews with journalists to identify pain points and opportunity areas within OCCRP Aleph. We spoke with 4 freelance journalists and 1 newsroom journalist, and the interviews were a mixture of in-person and remote. We identified three problem areas that kept emerging, and pulled out details and quotations in order to clarify these issues and bring them to life.&lt;/p&gt;
&lt;p&gt;After our interviews were finished, we shared our findings with the OCCRP team and worked together to decide how to prioritize our design time.&lt;/p&gt;
&lt;p&gt;We decided to focus on the following three themes in our design work:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Purpose&lt;/strong&gt;, e.g. What is this tool for? Who makes it? What kind of data does it contain? How is it different than other tools?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Orientation&lt;/strong&gt;, e.g. Where am I in the database? How did I get here? How do I get somewhere else?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sourcing&lt;/strong&gt;, e.g. Where is this data from? How fresh is it? Is it publicly available or private? Who vouches for it? Can I consider it a credible source?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;With these focus areas, we iterated on wireframes and high-fidelty prototypes for the Aleph interface, and then ran 4 remote usability tests with OCCRP journalists to get feedback on how the wireframes addressed these themes and see if our designs improved their workflows.&lt;/p&gt;
&lt;p&gt;Our collaboration formally ended in August 2019, when we handed off our research, our mockups, and our usability test results to the Aleph team. Since then, the Aleph team has been hard at work making these research-based design recommendations into reality. The screenshots you see below aren&amp;rsquo;t just pipe-dream design mockups – they&amp;rsquo;re images of the actual website.&lt;/p&gt;
&lt;p&gt;You can explore these changes for yourself at &lt;a href=&#34;http://aleph.occrp.org&#34;&gt;http://aleph.occrp.org&lt;/a&gt;. (Not sure if this is a benefit or a hazard, but you&amp;rsquo;ll likely learn a bit about the shadowy world of international corporate finance along the way.)&lt;/p&gt;
&lt;h2 id=&#34;unpacking-the-design-problems&#34;&gt;Unpacking The Design Problems&lt;/h2&gt;
&lt;p&gt;In this case study, we&amp;rsquo;ll walk you through some of the design problems we identified in Aleph, as well as how we solved them. You may recognize some of these design problems in your tools and teams, and we hope that our process and solutions are helpful to you.&lt;/p&gt;
&lt;h3 id=&#34;problem-1-what-is-this-tool-called&#34;&gt;Problem 1: What is this tool called?&lt;/h3&gt;
&lt;p&gt;In our post-research meeting with the OCCRP team, we decided to redesign the home page in order to make people&amp;rsquo;s first steps clearer. But we ran into an unexpectedly thorny problem: what name should show up on the home page?&lt;/p&gt;
&lt;p&gt;Obviously, the name of the tool. Easy, right? Well, even in the corporate world, but especially in the nonprofit tech and open source world, it&amp;rsquo;s not so simple.&lt;/p&gt;
&lt;p&gt;What we did to solve this problem is listen carefully to how our interviewees referred to&amp;hellip; well, to the tool. As interviewers, we went to great pains not to put any words in their mouths. We heard the following names:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;data dot occrp dot org&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;OCCRP Data&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;OCCRP&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Aleph&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;OCCRP Aleph&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In reflecting on this challenge with the team, we dug into the name tension and found that the OCCRP team really liked the name that had been reserved to just refer to the code base: Aleph. The name Aleph is actually a literary allusion. The Aleph is a magical object in &lt;a href=&#34;https://en.wikipedia.org/wiki/The_Aleph_(short_story)&#34;&gt;a Jorge Luis Borges story&lt;/a&gt;; discovered under a staircase in an old house, this glowing sphere contains the entirety of the universe, past, present, and future. Aleph, the open source project, also aims to contain a dazzling, head-spinning variety of information.&lt;/p&gt;
&lt;p&gt;OCCRP Aleph is a tool that allows journalists to upload, search, and cross-reference large data sets, often around business structures and property ownership. Datasets like these are crucial to &amp;ldquo;follow the money&amp;rdquo; investigations such as the Panama Papers and the Paradise Papers.&lt;/p&gt;
&lt;p&gt;So why not just call it Aleph? Since Aleph is open-source, anyone can run an instance of it on their own web servers. Newsrooms, such as the Süddeutsche Zeitung, have their own private Alephs.&lt;/p&gt;
&lt;p&gt;Out of these names, we determined that the name OCCRP Aleph should show up on the home page, while the project should still be called Aleph. We all loved the name, and even had some fun with a new logo&amp;hellip; but more on that later.&lt;/p&gt;
&lt;h3 id=&#34;problem-2-orientation--what-goes-on-the-home-page&#34;&gt;Problem 2: Orientation — What goes on the home page?&lt;/h3&gt;
&lt;p&gt;If you visit an Aleph installation to look at datasets, you have two ways of encountering the datasets. Either you can search datasets for certain people or companies, or you can just browse entire datasets and see what you find. But do people actually do both of these things? We learned in our research phase that people use OCCRP Aleph almost exclusively to search. They come to OCCRP Aleph once they already have a lead they want to follow up on, the name of a person or a business. Nobody browses. Nobody starts out by &amp;ldquo;exploring.&amp;rdquo; OCCRP Aleph is rarely the first step in their research process – it&amp;rsquo;s always the second.&lt;/p&gt;
&lt;p&gt;But if people already know what they want to search for, and they aren&amp;rsquo;t interested in seeing anything they weren&amp;rsquo;t looking for, then what shows up on the home page?&lt;/p&gt;
&lt;p&gt;You&amp;rsquo;re familiar with the ways that, for example, an e-commerce website solves this problem. An e-commerce website uses the home page to spotlight sales and deals; they recognize you from your past behavior, and push products to you that they think you&amp;rsquo;ll click on. However, neither of those techniques makes any sense for an open data platform that doesn&amp;rsquo;t track visitors. We had a few different patterns we could try.&lt;/p&gt;
&lt;p&gt;Should we just emulate the classic, minimalist Google homepage, with a single search box? Or should we make the home page a personalized area, a shortcut to a user&amp;rsquo;s private groups and uploaded datasets? Or something in between?&lt;/p&gt;
&lt;p&gt;Most Aleph users are repeat users, so personalization seemed like a good idea. However, usability testing surfaced a few problems that needed to be addressed.&lt;/p&gt;
&lt;p&gt;People found it confusing when the first screen they saw was too customized. They also pointed out that, if personal search history, datasets, and other groups were shown immediately on the front page, somebody looking over their shoulder when they logged in might see sensitive information. So we had to make sure that what they saw was personal, but not &lt;em&gt;too&lt;/em&gt; personal. We settled on a list of events: data added or removed from datasets they follow.&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://lh6.googleusercontent.com/bKhVLTDm04AmF50PQa9_jG1kXm2Sp8LNXXdS7jIxzVoAkb9pJ-iYy0DO0lz5Vk_g45Z5LY6QMT6Wj8f72OqPiVXb-pEZDIg4NUOTh027ljGbVihp86DJzmQ3B1DxA5DMVUPluPzH&#34; alt=&#34;Screenshot of Aleph home page&#34;&gt;
&lt;/p&gt;
&lt;p&gt;This design acknowledges that search is users&amp;rsquo; main task. They come to OCCRP Aleph with a list of names, a list of organizations, or at the very least a question to look into. So we added heavy visual emphasis to the search box at the top of the page.&lt;/p&gt;
&lt;p&gt;We also made a subtle improvement to help people orient themselves: we added a dropdown menu in front of the search box. The dropdown shows the scope of the current search – the dataset(s) to which the search is being applied. When it says &amp;ldquo;OCCRP Aleph,&amp;rdquo; that means all datasets available to that user.&lt;/p&gt;
&lt;p&gt;On the datasets page, the dropdown isn&amp;rsquo;t a dropdown yet, just looks like a label.&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://lh6.googleusercontent.com/FKxZ5mDtvtDDK-qQzrYSV_eQmGJGg1VyylQTyBAsTrdgo7X8xK2n8Ao-paKe33WnlrTufL47T1KMHc8d1W17vLmmVArPfNVH37KPPTA4nC7nJBFQkFI19ZDEC4AmdWP_YKT8DMmQ&#34; alt=&#34;Screenshot of Aleph search box&#34;&gt;
&lt;/p&gt;
&lt;p&gt;However, once you enter a database, the label becomes a dropdown. You can choose whether to search within the database you&amp;rsquo;ve selected (here, &amp;ldquo;Mozambique Persons of Interest&amp;rdquo;) or whether to search the entirety of the Aleph instance. This dropdown offers more than just a choice: it sends a quiet signal to help you build your mental map of where you are.&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://lh6.googleusercontent.com/IvU-a04s8WdPpxGJE5wM2ZH3XPzZYL6Tg0NEazCyLU71Tk9nhVEcMAdPEFbexavV40MvhVTQF7XX8etWeBhyt5Os7yAzIzNDWP0LVYloxR6JQsKKjmtvyTn5eXNrydP_HAPcY4O_&#34; alt=&#34;Screenshot showing dropdown in front of search box that aids in navigating datasets&#34;&gt;
&lt;/p&gt;
&lt;p&gt;This new design gets people right down to business from the beginning, and, as an added benefit, cuts down on that &amp;ldquo;where am I and how did I get here?&amp;rdquo; feeling.&lt;/p&gt;
&lt;h3 id=&#34;problem-3-sourcing--the-heavy-burden-of-verification&#34;&gt;Problem 3: Sourcing — The heavy burden of verification&lt;/h3&gt;
&lt;p&gt;&amp;ldquo;How reliable is this data?&amp;rdquo; This is the crucial question journalists ask whenever they are researching a story. Using outdated, falsified, hacked, or even incomplete data can cause serious consequences.&lt;/p&gt;
&lt;p&gt;Aleph is in a difficult position here. OCCRP can&amp;rsquo;t vouch for each and every data set. OCCRP provides software that helps journalists search datasets and trace connections between datasets, but OCCRP can&amp;rsquo;t curate every dataset on OCCRP Aleph, much less every dataset on every Aleph installation!&lt;/p&gt;
&lt;p&gt;In our research, people expressed a lot of concern about data reliability. They asked for a lot of features that frankly aren&amp;rsquo;t possible: &amp;ldquo;trust scores,&amp;rdquo; verification marks, and automatic updating of datasets. But Aleph isn&amp;rsquo;t supposed to be a data evaluation tool. No software can substitute for the judgment of a trained journalist who is familiar with their subject area.&lt;/p&gt;
&lt;p&gt;Just to give one example: a three-month-old dataset with company addresses might seem recent enough to use&amp;hellip; but not for a seasoned business journalist, who already knows that this dataset is updated monthly!&lt;/p&gt;
&lt;p&gt;This is why our philosophy was &lt;em&gt;Data transparency, not data perfection&lt;/em&gt;. We aimed to spotlight all metadata that could help a trained journalist evaluate a source&amp;rsquo;s recency and provenance. Most of these fields already existed in the data model – it would have been difficult to add new fields – but we used design to draw attention to the most relevant ones. In particular, we recommended a bold callout that shows the dataset&amp;rsquo;s update frequency, if known – and if it&amp;rsquo;s not known, that&amp;rsquo;s also helpful information.&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://lh5.googleusercontent.com/1cUATExcl1A3GRxZnTIXxlzMFTrY8l92vhjgqBMDxsq58kfWYZtho7SuSxOosJ0tuEWBhS6RxoIaR85wrCjFFkELffWtXtTw8PidAev0CoKFfU7zmCPTO3jLo9GFZzzF4eSkQPy-&#34; alt=&#34;Screenshot showing metadata attached to datasets&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Inside the dataset, people can see even more metadata. It&amp;rsquo;s spotlighted with a darker box. This information may not reassure journalists that this dataset is clean, uncompromised, and updated, but it gives them the information they need at a glance in order to make the necessary judgment calls.&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://lh6.googleusercontent.com/MtuwqQe7UoQL-oPzK8nBbmNcVQ05XK12gjhf23qPKJbQO63FxjjQP_5fUP_wsEwCKr3EW1CeHoiVZXOkJmmDjnZu_1w0yR8of20sWB0_bg5YgzOzRACT3vhLomH6HqeRhKN6mpwL&#34; alt=&#34;Screenshot of dataset detail&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;little-design-changes-big-impact&#34;&gt;Little Design Changes, Big Impact&lt;/h2&gt;
&lt;p&gt;Our research and usability testing helped us uncover lots of design opportunities along the way that weren&amp;rsquo;t quite as game-changing as the ones above, but nevertheless led to significant usability improvements. Let&amp;rsquo;s look at a few places where the OCCRP team added a little intervention that makes a big difference.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Search tips.&lt;/strong&gt; Even people who used Aleph often had a hit-and-miss approach to advanced search. Since they use a lot of databases, all of which behave a little differently, they don&amp;rsquo;t remember exactly which conventions Aleph uses. To solve this, we built a giant dropdown advanced search panel that is packed with explicit reminders about how search works. It&amp;rsquo;s always available, right next to the search bar.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/recent-notifications-occrp-aleph-2020-12-11-21-52-05_hu_a66a52acffce2dd7.png&#34; alt=&#34;Screenshot of advanced search&#34; width=&#34;740&#34; height=&#34;772&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Documentation for non-developers.&lt;/strong&gt; Previously, it was much easier to find information about how to contribute code to Aleph than how to use Aleph. Figuring out how to do journalist tasks like searching, parsing, uploading, and sharing datasets was a challenge, since the documentation was geared towards software developers. The new documentation page, located at &lt;a href=&#34;http://docs.alephdata.org&#34;&gt;docs.alephdata.org&lt;/a&gt;, is written for researchers and journalists, and built around the tasks they&amp;rsquo;re likely to do.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/welcome-aleph-2020-12-11-22-10-33_hu_f380e88c7bb68d09.png&#34; alt=&#34;Screenshot of about page&#34; width=&#34;740&#34; height=&#34;394&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Quick links to user settings.&lt;/strong&gt; Accessing various personal settings used to mean first going to a personal home page, then navigating to the place you wanted to be. We designed a menu and architecture that made navigation more efficient by surfacing common user tasks in a dropdown.&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://lh5.googleusercontent.com/JlyR-UN4LNBY0kq3rxbXfhaEnaHQ_zOSsHV0zasJjAE_uWWxU_GeKAYJuXRaXyXJVI2X5I-VUFl4tS0Qef_K_DXH47Dz1oBJhWhdITDUuxZfbTSWLUAyPIYIRVqg-Exy2OFb7qoC&#34; alt=&#34;Screenshot of user menu&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;And finally&amp;hellip;&lt;/strong&gt; We say over and over, &amp;ldquo;design is more than logos.&amp;rdquo; But, yeah&amp;hellip; we did design a new logo for Aleph!&lt;/p&gt;
&lt;p&gt;This simple shape, inspired by the ancient Phoenician glyph for the letter &amp;ldquo;aleph,&amp;rdquo; is a high-contrast emblem that looks great in many different colorways. We work as a team and usually don&amp;rsquo;t emphasize the contributions of individuals, but in this case we have to shout out to &lt;a href=&#34;http://lorrainechuen.com/&#34;&gt;Lorraine Chuen&lt;/a&gt; for her modern take on the ancient symbol.&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://lh4.googleusercontent.com/NArAyLZGebA3CqY4mkgPfZN9CLTW-ABRmIdshLf35vGL4ukFR2s2F5Cvj2UDq-s4LmbzBXKB6ExVJqWZ3YAX3ocG0b4Goop8aCw2mVQhvu0QhFW5EGF3_vWmh5x7BCq9Vj8d0UYe&#34; alt=&#34;Screenshot of new logo&#34;&gt;
&lt;/p&gt;
&lt;p&gt;We hope learning about our approach was useful to you. Would you like to collaborate with us to solve similar design and usability problems? Get in touch!&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Thanks to Emma Prest, Kirk Jackson, Friedrich Lindenberg, Nadine Stammen, Lorraine Chuen, and all research participants.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Managing Director</title>
      <link>https://superbloom.design/community/opportunities/managing-director/</link>
      <pubDate>Mon, 23 Nov 2020 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/community/opportunities/managing-director/</guid>
      <description>&lt;h2 id=&#34;the-deadline-for-applying-to-this-role-has-passed&#34;&gt;The deadline for applying to this role has passed.&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;We’re looking for a leader who can help us design and implement our long-term strategic vision, and support our teams to realize their full potential.&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&#34;the-role&#34;&gt;The role&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You’ll be a critical part of our leadership team, responsible for overseeing staffing and organizational culture, and professional development.&lt;/li&gt;
&lt;li&gt;You’ll grow our programs, business development strategy, network of collaborators, and strengthen our teams to ensure internal cohesion and stability.&lt;/li&gt;
&lt;li&gt;You’ll work with key staff to build a multi-year strategy to support our unique position as collaborative technologists designing for safety &amp;amp; privacy.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;about-us&#34;&gt;About us&lt;/h3&gt;
&lt;p&gt;We are a small US 501(c)3 nonprofit organization, founded in 2014 with the goal of making secure communications tools easier to use. We believed – and still do – that security doesn&amp;rsquo;t have to be confusing to end users. We&amp;rsquo;ve contributed design to a variety of projects, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We&amp;rsquo;ve held &lt;a href=&#34;https://superbloom.design/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we&amp;rsquo;ve done a lot more than usable security. Just in the last year, we&amp;rsquo;ve launched a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;p&gt;We’re also working through an open rebranding process, moving away from the name “Simply Secure” and toward an identity that more accurately reflects the diversity of the work we do.&lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;Learn more on our blog.&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;about-you&#34;&gt;About you&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Are a critical senior leader with strengths as a manager, strategist, and culture builder.&lt;/li&gt;
&lt;li&gt;Have demonstrated organizational strategy, facilitation, and people management skills.&lt;/li&gt;
&lt;li&gt;Have experience and deep understanding of the civil society space in the US and EU as it intersects with technology.&lt;/li&gt;
&lt;li&gt;Have an extensive network of community organizations, nonprofits and advocacy groups, philanthropic partners, and a political understanding of key world regions.&lt;/li&gt;
&lt;li&gt;Are comfortable with cross-cultural communication, collaboration and conflict resolution, through work with international teams.&lt;/li&gt;
&lt;li&gt;Have experience managing and enjoy working with a fully remote, distributed team, across many time zones and cultures.&lt;/li&gt;
&lt;li&gt;Have availability during our prime work hours (11-6pm Central Europe / 10-5pm UK / 8-6pm US Eastern / 8-3pm US Pacific)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;nice-to-have&#34;&gt;Nice to have&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Experience with research and design work, e.g. human-centered design, design thinking, service design, ux design, or participatory research (specifically field research).&lt;/li&gt;
&lt;li&gt;Knowledgeable about one or more of the following areas: open source software, internet freedom, tech criticism and activism, human rights technology.&lt;/li&gt;
&lt;li&gt;Comfortable with collaborative work tools (we currently use Notion, Miro, and Google Suite).&lt;/li&gt;
&lt;li&gt;Proficiency in major world languages other than English &amp;ndash; especially German, French or Spanish.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;sound-like-a-good-fit&#34;&gt;Sound like a good fit?&lt;/h3&gt;
&lt;p&gt;Please send us:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The position is open until filled, and we will begin reviewing resumes on Wednesday, November 25th. Please send your resume and cover letter to Nicola Pratt at nicola [ at ] superbloom [ dot ] design by Monday, December 7, 2020.&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Call for Proposals — Brand/Visual Designer</title>
      <link>https://superbloom.design/community/opportunities/brand-designer-cfp/</link>
      <pubDate>Fri, 20 Nov 2020 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/community/opportunities/brand-designer-cfp/</guid>
      <description>&lt;h2 id=&#34;the-deadline-for-applying-to-this-role-has-passed&#34;&gt;The deadline for applying to this role has passed.&lt;/h2&gt;
&lt;h3 id=&#34;the-project&#34;&gt;The project&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;We are looking for someone who can bring their expertise in crafting product identities to a new, global tool that helps at-risk users (human rights defenders, journalists, activists, NGOs) stay safe online. The tool is launching in February 2021.&lt;/li&gt;
&lt;li&gt;You’ll propose, create, and deliver an identity and design system that includes:
&lt;ul&gt;
&lt;li&gt;A logo&lt;/li&gt;
&lt;li&gt;Logotype&lt;/li&gt;
&lt;li&gt;A brand mascot&lt;/li&gt;
&lt;li&gt;Illustrations&lt;/li&gt;
&lt;li&gt;Typography&lt;/li&gt;
&lt;li&gt;Color palette&lt;/li&gt;
&lt;li&gt;Guidelines for usage (dos and don’ts)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;The identity system for this free tool is not intended to impress investors and convert customers. Instead, it will help users understand the tool and establish consistent patterns and metaphors to increase usability and trustworthiness.&lt;/li&gt;
&lt;li&gt;Several identity guidelines are already in place, including: mission, vision, values, audience, personality.&lt;/li&gt;
&lt;li&gt;The identity system will be implemented into a browser extension, informational website, and extension marketplaces on Chrome and Firefox.&lt;/li&gt;
&lt;li&gt;This is a time-limited contract, from approximately November 2020 to February 2021. We are a US 501(c)3 organization that has the ability to hire in the US and Germany, and contract internationally.&lt;/li&gt;
&lt;li&gt;We are inspired by work like:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.tunnelbear.com/&#34;&gt;Tunnelbear&lt;/a&gt; - Consistent branding with expressive and approachable metaphors&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://signal.org/&#34;&gt;Signal&lt;/a&gt; - Breezy confidence and straight-talking makes the tool approachable to a mainstream audience&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://tails.boum.org/&#34;&gt;Tails&lt;/a&gt; - Strong graphical metaphor for communicating complex functionality, in a human, emotional way&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.mailvelope.com/&#34;&gt;Mailvelope&lt;/a&gt; - Meaningful logo design and integrated, clear concept.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;about-us&#34;&gt;About us&lt;/h3&gt;
&lt;p&gt;We are a small US 501(c)3 nonprofit organization, founded in 2014 with the goal of making security tools easier to use. We believed – and still do – that security doesn&amp;rsquo;t have to be confusing to end users. We&amp;rsquo;ve contributed design to a variety of tools that enhance security, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We&amp;rsquo;ve held &lt;a href=&#34;https://superbloom.design/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we&amp;rsquo;ve done a lot more than usable security. Just in the last year, we&amp;rsquo;ve launched a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;p&gt;(We&amp;rsquo;re actually doing a rebranding process, moving away from the name &amp;ldquo;Simply Secure.&amp;rdquo; &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;More info over here on the blog!&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&#34;about-you&#34;&gt;About you&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You love designing identity systems. You get really excited about telling a visual story of a tool that is designed to help people.&lt;/li&gt;
&lt;li&gt;You design expressive and accessible screens, logos, and illustrations, meant to be viewed on the web&lt;/li&gt;
&lt;li&gt;You like working independently, in collaboration with a fully remote team&lt;/li&gt;
&lt;li&gt;You are comfortable advocating for yourself and your work to make sure that you’re getting what you need from us&lt;/li&gt;
&lt;li&gt;Your meeting availability has sufficient overlap with our working hours of 10am to 6pm Central European Time. The project team is based in Germany.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;nice-to-have&#34;&gt;Nice to have&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Awareness of one or more of the following areas: open source software, internet freedom, tech criticism and activism, human rights&lt;/li&gt;
&lt;li&gt;Experience in developing brands&lt;/li&gt;
&lt;li&gt;Expert in communicating with international audiences&lt;/li&gt;
&lt;li&gt;Knowledge of accessibility standards&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;sound-like-a-good-fit&#34;&gt;Sound like a good fit?&lt;/h3&gt;
&lt;p&gt;Please send us:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;3-5 examples of your work. Please highlight the projects with quick turn-around times (less than 3 months) and tell us about the &lt;strong&gt;timeline and process&lt;/strong&gt;: how did these projects get created? Who was involved, what did the process look like, how long did it take?&lt;/li&gt;
&lt;li&gt;A (very short!) outline of how you would approach working with us on this project. What phases would this project have, and what would you need from us to make it successful?&lt;/li&gt;
&lt;li&gt;1-2 references. References will be contacted in the last phase of application review.&lt;/li&gt;
&lt;li&gt;The times you are available for meetings within our working hours (10am to 6pm Central European Time)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Send these documents to &lt;a href=&#34;mailto:jobs-brand@superbloom.design&#34;&gt;jobs-brand@superbloom.design&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Position is open until filled and applications will be evaluated on a rolling review. We will stop accepting applications on December 4, 2020.&lt;/strong&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Design Researcher, Part Time</title>
      <link>https://superbloom.design/community/opportunities/design-researcher-pt/</link>
      <pubDate>Thu, 12 Nov 2020 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/community/opportunities/design-researcher-pt/</guid>
      <description>&lt;h2 id=&#34;the-deadline-for-applying-to-this-role-has-passed&#34;&gt;The deadline for applying to this role has passed.&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;We&amp;rsquo;re looking for a part-time design researcher to help us with human centered design research.&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&#34;the-project&#34;&gt;The project&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You&amp;rsquo;ll help develop and conduct user interviews, surveys, and focus groups; you&amp;rsquo;ll synthesize research and develop outputs, including a report, to make the findings understandable and actionable by the project team; and you&amp;rsquo;ll work with clients to help them make the most of the research findings.&lt;/li&gt;
&lt;li&gt;This is a part-time position, minimum 20 hours per week, from approximately November 2020 to March 2021, with the opportunity to renew. We are a US 501(c)3 organization that has the ability to hire in the US and Germany, and contract internationally.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;about-us&#34;&gt;About us&lt;/h3&gt;
&lt;p&gt;We are a small US 501(c)3 nonprofit organization, founded in 2014 with the goal of making security tools easier to use. We believed – and still do – that security doesn&amp;rsquo;t have to be confusing to end users. We&amp;rsquo;ve contributed design to a variety of tools that enhance security, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We&amp;rsquo;ve held &lt;a href=&#34;https://superbloom.design/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we&amp;rsquo;ve done a lot more than usable security. Just in the last year, we&amp;rsquo;ve launched a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;p&gt;(We&amp;rsquo;re actually doing a rebranding process, moving away from the name &amp;ldquo;Simply Secure.&amp;rdquo; &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;More info over here on the blog!&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&#34;about-you&#34;&gt;About you&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You love talking to research participants and understanding social and technical systems&lt;/li&gt;
&lt;li&gt;You have experience with human-centered or participatory research (specifically field research)&lt;/li&gt;
&lt;li&gt;You like working independently and in collaboration with a fully remote, distributed team&lt;/li&gt;
&lt;li&gt;You have excellent project team communication and meeting facilitation skills&lt;/li&gt;
&lt;li&gt;You are able to manage a balance of strategic planning and tactical execution&lt;/li&gt;
&lt;li&gt;You are experienced with engaging in client-centered communication&lt;/li&gt;
&lt;li&gt;You are comfortable advocating for yourself and your work to make sure that you&amp;rsquo;re getting what you need to be successful&lt;/li&gt;
&lt;li&gt;You understand the nuances of writing for an international audience and how to make your words direct and accessible without simplifying your message&lt;/li&gt;
&lt;li&gt;You write clear, concise, and engaging research synthesis to be read by a broad non-technical audience&lt;/li&gt;
&lt;li&gt;You are familiar with working in the nonprofit space&lt;/li&gt;
&lt;li&gt;You are available at least 20 hours/week with overlap during our prime work hours (11-6pm Central Europe / 10-5pm UK / 8-6pm US Eastern / 8-3pm US Pacific)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;nice-to-have&#34;&gt;Nice to have&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Knowledgeable about one or more of the following areas: open source software, internet freedom, tech criticism and activism, human rights&lt;/li&gt;
&lt;li&gt;Comfortable with collaborative work tools (we currently use Notion, Miro, and Google Suite)&lt;/li&gt;
&lt;li&gt;Comfortable with exploring and evaluating new tools&lt;/li&gt;
&lt;li&gt;Comfortable in cross-cultural communication, e.g. experience with international work&lt;/li&gt;
&lt;li&gt;Aware of best practices around informed research consent, safeguarding confidential research information, and anonymizing participant data (if this is new to you, we&amp;rsquo;re happy to help you learn!)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;sound-like-a-good-fit&#34;&gt;Sound like a good fit?&lt;/h3&gt;
&lt;p&gt;Please send us:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Resume&lt;/li&gt;
&lt;li&gt;Examples of your work. With each link or document you send, please tell us about the &lt;strong&gt;timeline and process:&lt;/strong&gt; how did these outputs get created? Who was involved, what did the process look like, how long did it take?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Send these documents to Nicola Pratt at nicola [ at ] superbloom [ dot ] design by Wednesday, November 25, 2020.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;To help us combat bias while we review applications, please remove your name from the documents you send.&lt;/strong&gt; One person on our team will keep a list assigning a code name to your application while we review it. If we&amp;rsquo;d like to interview you, we&amp;rsquo;ll match your code name to your real name, and get in touch. (If removing your name from your work screws up the formatting, don&amp;rsquo;t worry, this is not a graphic design job! You can also put an obviously fake name in place of your real name to keep the formatting consistent.)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Project Manager, Part Time</title>
      <link>https://superbloom.design/community/opportunities/project-manager-pt/</link>
      <pubDate>Thu, 12 Nov 2020 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/community/opportunities/project-manager-pt/</guid>
      <description>&lt;h2 id=&#34;the-deadline-for-applying-to-this-role-has-passed&#34;&gt;The deadline for applying to this role has passed.&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;We&amp;rsquo;re looking for a part-time project manager to help us wrangle our projects.&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&#34;the-role&#34;&gt;The role&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You&amp;rsquo;ll help us manage a number of different projects with different partners and engagement models, making sure that we are on top of timelines, communicating effectively, and delivering on the work&lt;/li&gt;
&lt;li&gt;This is a part-time position, minimum 20 hours per week, from approximately November 2020 to March 2021, with the opportunity to renew. We are a US 501(c)3 organization that has the ability to hire in the US and Germany, and contract internationally.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;about-us&#34;&gt;About us&lt;/h3&gt;
&lt;p&gt;We are a small US 501(c)3 nonprofit organization, founded in 2014 with the goal of making security tools easier to use. We believed – and still do – that security doesn&amp;rsquo;t have to be confusing to end users. We&amp;rsquo;ve contributed design to a variety of tools that enhance security, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We&amp;rsquo;ve held &lt;a href=&#34;https://superbloom.design/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we&amp;rsquo;ve done a lot more than usable security. Just in the last year, we&amp;rsquo;ve launched a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;p&gt;(We&amp;rsquo;re actually doing a rebranding process, moving away from the name &amp;ldquo;Simply Secure.&amp;rdquo; &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;More info over here on the blog!&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&#34;about-you&#34;&gt;About you&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You have experience with project management&lt;/li&gt;
&lt;li&gt;You enjoy simplifying complex projects, tracking details, and making sure the project teams are working well together&lt;/li&gt;
&lt;li&gt;You have experience with leading projects and project delivery&lt;/li&gt;
&lt;li&gt;You like working independently and in collaboration with a fully remote, distributed team&lt;/li&gt;
&lt;li&gt;You have excellent project team communication and meeting facilitation skills&lt;/li&gt;
&lt;li&gt;You are able to manage a balance of strategic planning and tactical execution&lt;/li&gt;
&lt;li&gt;You are experienced with client-centered communication&lt;/li&gt;
&lt;li&gt;You are comfortable advocating for yourself and your work to make sure that you&amp;rsquo;re getting what you need to be successful&lt;/li&gt;
&lt;li&gt;You are familiar with working in the nonprofit space&lt;/li&gt;
&lt;li&gt;You are available at least 20 hours/week with overlap during our prime work hours (11-6pm Central Europe / 10-5pm UK / 8-6pm US Eastern / 8-3pm US Pacific)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;nice-to-have&#34;&gt;Nice to have&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Experience with research and design work, e.g. human-centered design, design thinking, service design, ux design, or participatory research (specifically field research)&lt;/li&gt;
&lt;li&gt;Experience with client-facing account management&lt;/li&gt;
&lt;li&gt;Knowledgeable about one or more of the following areas: open source software, internet freedom, tech criticism and activism, human rights&lt;/li&gt;
&lt;li&gt;Comfortable with collaborative work tools (we currently use Notion, Miro, and Google Suite)&lt;/li&gt;
&lt;li&gt;Comfortable with exploring and evaluating new tools&lt;/li&gt;
&lt;li&gt;Comfortable in cross-cultural communication, e.g. experience with international work&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;sound-like-a-good-fit&#34;&gt;Sound like a good fit?&lt;/h3&gt;
&lt;p&gt;Please send us:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Resume&lt;/li&gt;
&lt;li&gt;Examples of your work. With each link or document you send, please tell us about the &lt;strong&gt;timeline and process:&lt;/strong&gt; how did these outputs get created? Who was involved, what did the process look like, how long did it take?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Send these documents to Nicola Pratt at nicola [ at ] superbloom [ dot ] design by Wednesday, November 25, 2020.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;To help us combat bias while we review applications, please remove your name from the documents you send.&lt;/strong&gt; One person on our team will keep a list assigning a code name to your application while we review it. If we&amp;rsquo;d like to interview you, we&amp;rsquo;ll match your code name to your real name, and get in touch. (If removing your name from your work screws up the formatting, don&amp;rsquo;t worry, this is not a graphic design job! You can also put an obviously fake name in place of your real name to keep the formatting consistent.)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>What&#39;s next for &#39;Simply Secure&#39;? Part 1: Revisiting our name and identity</title>
      <link>https://superbloom.design/learning/blog/simply-secure-rebranding-survey/</link>
      <pubDate>Sat, 24 Oct 2020 16:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/simply-secure-rebranding-survey/</guid>
      <description>&lt;p&gt;&amp;ldquo;Security doesn&amp;rsquo;t have to be confusing to people.&amp;rdquo; That&amp;rsquo;s been Simply Secure&amp;rsquo;s rallying cry since our founding in 2014. To make our vision of usable security a reality, we&amp;rsquo;ve contributed design to a variety of tools that enhance security, from &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We&amp;rsquo;ve held &lt;a href=&#34;https://superbloom.design/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security.&lt;/p&gt;
&lt;p&gt;But we&amp;rsquo;ve done a lot of work that is better described more broadly as &lt;strong&gt;design for trustworthy technology&lt;/strong&gt;. Just in the last year, we&amp;rsquo;ve launched a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/resources/popping-the-filter-bubble-design-practices-for-data-donation&#34;&gt;set of workshops on design for data donation&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;h2 id=&#34;outgrowing-our-name&#34;&gt;Outgrowing our name&lt;/h2&gt;
&lt;p&gt;This is why we started to feel that the name Simply Secure was getting in our way. We explained again and again to potential collaborators, to funders, and to our community that we work on more than just security-focused tech (and also that we don&amp;rsquo;t think security is simple!). We clarified over and over that we have nothing to do with a &lt;a href=&#34;http://simplisafe.com&#34;&gt;certain IoT home security company&lt;/a&gt;. We realized that we needed a name that helped us share and communicate our vision. Personally explaining our name to everyone just isn&amp;rsquo;t a great use of our time.&lt;/p&gt;
&lt;p&gt;We held internal retreats to clarify our mission and vision. We had fun brainstorming wacky name ideas. But just coming up with a new brand by ourselves, or with the help of an outside firm, felt risky.&lt;/p&gt;
&lt;p&gt;Because we&amp;rsquo;re not actually the &amp;ldquo;end users&amp;rdquo; of our name, our logo, or our color palette.
We&amp;rsquo;re not the most important stakeholders.
We&amp;rsquo;re not the people whose opinion most matters.
&lt;em&gt;You are&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;If we rename ourselves and you, reading this, don&amp;rsquo;t get what we did and why, if you don&amp;rsquo;t groove on it&amp;hellip; well, then we can&amp;rsquo;t really serve our community effectively, and we&amp;rsquo;ve done something wrong.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s why we reached out to Una Lee of &lt;a href=&#34;https://www.andalsotoo.net/&#34;&gt;And Also Too&lt;/a&gt;. Una and her team are experts in co-design: the process of designing and deciding together with a community, rather than behind closed doors. We were delighted when Una agreed to mentor us through our own co-design process. In September 2020, we officially launched the search for Simply Secure&amp;rsquo;s new name, and we committed ourselves to sharing our process publicly as we go. So hold on tight, and welcome aboard!&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/refresh-crane-horiz@1x_hu_19781bd763ff062f.png&#34; alt=&#34;Simply Secure logo being built or unbuilt by a construction crane&#34; width=&#34;740&#34; height=&#34;431&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;we-asked-you--heres-what-you-said&#34;&gt;We asked you – here&amp;rsquo;s what you said&lt;/h2&gt;
&lt;p&gt;Our first step was to send out a 5-minute survey asking what our community thought of Simply Secure&amp;rsquo;s current name and visual style. The survey was open for 3 weeks and received 54 responses. Here&amp;rsquo;s what we found out.&lt;/p&gt;
&lt;h3 id=&#34;our-name&#34;&gt;Our name&lt;/h3&gt;
&lt;p&gt;For a large majority of respondents, our name doesn&amp;rsquo;t capture what we do. They say that &amp;ldquo;Simply Secure&amp;rdquo; sounds like we only do security, and we do a lot more. Our name doesn&amp;rsquo;t imply anything about design or UX, anything about education, anything about human rights, or anything about being a nonprofit. It&amp;rsquo;d be impossible to think of a name that communicates all these things! But we also don&amp;rsquo;t want a name that only has to do with part of our work.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This could be anything about security or safety. How would anyone know it&amp;rsquo;s about design/UX?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;It&amp;rsquo;s not holistic or broad enough. The people I&amp;rsquo;ve worked with bring elegance and clarity to projects.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;No, because you work on many more issues than just security, and it doesn&amp;rsquo;t speak to the community-oriented dynamic that you cultivate as an org&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Not everyone dislikes our name. However, when describing what we do, those respondents say, &amp;ldquo;you make security technology easier to use.&amp;rdquo; So it makes sense to us that these folks think our name is a good fit for us – for the security usability portion of our work, &amp;ldquo;Simply Secure&amp;rdquo; actually is a pretty good description.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Good name - it&amp;rsquo;s about making security simple.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;[I don&amp;rsquo;t like the name for you] because I think your work has broadened beyond a focus on security. But I do think it is a good name.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Five respondents mentioned the similarity to SimpliSafe, a US-based IoT home security company. Given that &lt;a href=&#34;https://simplisafe.com/privacy&#34;&gt;SimpliSafe&amp;rsquo;s privacy policy gives the company license to store and analyze recordings of your home&lt;/a&gt;, we&amp;rsquo;re not particularly happy about this association.&lt;/p&gt;
&lt;h3 id=&#34;our-logo&#34;&gt;Our logo&lt;/h3&gt;
&lt;p&gt;One big surprise for us: five respondents said that they like the sticky notes on the logo. The funny thing is, sticky notes actually weren&amp;rsquo;t at all what we had in mind. The proportions of the squares in the logo are supposed to represent the Fibonacci sequence, which is a key part of many cryptography algorithms. But now that we see the &amp;ldquo;sticky notes&amp;rdquo; in the logo, we kind of love it.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/simply-secure-sticker_hu_3c70f848f9ef8905.png&#34; alt=&#34;Simply Secure logo&#34; width=&#34;740&#34; height=&#34;996&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Five more respondents said the logo reminds them of various corporate apps; Slack came up a few times, as did Google. Given the type of work we do, these aren&amp;rsquo;t exactly the mental connections we want folks to have when they think of us.&lt;/p&gt;
&lt;h3 id=&#34;our-visual-style&#34;&gt;Our visual style&lt;/h3&gt;
&lt;p&gt;Respondents generally appreciated that our look is not dark, scary, or self-important. But we heard a lot of adjectives like &amp;ldquo;childish,&amp;rdquo; &amp;ldquo;kindergarten-ish,&amp;rdquo; and &amp;ldquo;playful.&amp;rdquo; Many people told us that our imagery was too fun and light for the heavy, intense, and even dangerous topics we deal with.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/audience-funders_hu_7f074d3dbe0323f5.png&#34; alt=&#34;Colorful balloons&#34; width=&#34;740&#34; height=&#34;631&#34;&gt;
&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;It&amp;rsquo;s not very memorable. I get children&amp;rsquo;s birthday party from it.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;Too happy and bright - your work is about serious and concerning topics.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The message we heard was: it&amp;rsquo;s refreshing that we present ourselves as welcoming and humble! But we also need to show that we take our work seriously. Imagery like balloons and cookies, and an aesthetic based on big, flat, brightly colored shapes, don&amp;rsquo;t communicate that we are a trustworthy, experienced partner for sensitive design and facilitation work.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/audience-developers_hu_1309f5bfce5f8c48.png&#34; alt=&#34;Rabbit coming out of a top hat&#34; width=&#34;740&#34; height=&#34;931&#34;&gt;
&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I worry that the rabbit ears in the hat makes a gesture toward being bewildering, rather than simple.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Out of 54 respondents, not a single person said that they liked our visual style in general, or that they thought it was a good representation of us. This confirms our hunch that we really need to rethink our look and feel.&lt;/p&gt;
&lt;h3 id=&#34;what-we-do&#34;&gt;What we do&lt;/h3&gt;
&lt;p&gt;We sought out survey responses from people who already knew at least a little bit about us, either as individuals or as an organization. Respondents were very consistent in how they described our values and attitudes: putting people first, breaking down boundaries around how tech gets created, and paying attention to the &amp;ldquo;edges&amp;rdquo; often neglected by mainstream tech.&lt;/p&gt;
&lt;p&gt;Their answers to &amp;ldquo;what does Simply Secure do?&amp;rdquo; were more varied, and depended on the work they&amp;rsquo;d done with us. Here are the most prominent types of answers we got.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Some folks painted us as conveners, networkers, and facilitators, bringing together people in the nonprofit tech space and creating connections between people and organizations. These people had often attended one of our workshops, or were part of our Slack.&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;Great listeners and communicators.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;A convener, a facilitator, a co-designer with a diverse outlook and commitment to security.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;Convening design thought, resources, and processes.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
&lt;li&gt;Some people saw us as experts in usable security. These people tended to have been aware of us for a longer time. This makes a lot of sense, because a few years ago, a larger percentage of our work was in fact directly related to security usability.&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;They help tech projects think carefully about how to design projects with security and usability in mind.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;Human-centered approach to design, security, and internet freedom.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
&lt;li&gt;Several people mentioned that we promote and share resources about thoughtful, responsible human-centered UX practices – not necessarily just about security. These tended to be people who found out about us more recently.&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;Digital agency with values for the future: transparency, security, ethics, environment.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;Design research and training agency focused on human rights centered design.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
&lt;li&gt;People who were in a managerial role tended to mention our work using design research to support other nonprofits.&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;Use data and storytelling to support organizational growth.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;Research design, helping people think about communities.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;Honest brokers for organizational planning and design.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;One of the most common responses was the feeling that people are seeing the tip of the iceberg.  There&amp;rsquo;s a feeling that we do &amp;ldquo;more,&amp;rdquo; but it&amp;rsquo;s not always clear what.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Design + so much more!!&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;I know about some of the work around design, but honestly I am not sure what the day-to-day of Simply Secure looks like.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;You do great projects but don&amp;rsquo;t get a lot of opportunity to talk about them.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The intangible attributes that respondents mentioned were lovely to read, and a nice pick-me-up in tough times. Please remember to actually verbalize your compliments to the people you admire – it means a lot. We all need the boost right now.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Trustworthy and practical.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;Super inspired by your work!&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;I gotta lotta love for Simply Secure.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&#34;who-responded&#34;&gt;Who responded?&lt;/h3&gt;
&lt;p&gt;54 people responded to the survey. Here are some charts showing the demographic breakdown.&lt;/p&gt;
&lt;p&gt;For the multiple-response questions, we didn&amp;rsquo;t include responses checked by only 1 respondent, in order to keep the chart size manageable. We occasionally omitted custom responses from the charts in order to protect respondents&amp;rsquo; privacy.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/refresh-survey-1_hu_a3ed7f78abf76939.png&#34; alt=&#34;Breakdown of how people know about us (multi-select). Top answers: through a person who works with SimSec (29), at a workshop (23), on Twitter (21), on Slack (20), at a conference (20, on the SimSec website (20))&#34; width=&#34;740&#34; height=&#34;365&#34;&gt;



    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/refresh-survey-2_hu_c1842d5650eecb80.png&#34; alt=&#34;Breakdown of how long people have been aware of us. 9% for &amp;lt; 6 months, 17% for 6 months-1 year, 26% for 1-2 years, 24% from 2-4 years, 24% for 4&amp;#43; years.&#34; width=&#34;740&#34; height=&#34;365&#34;&gt;



    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/refresh-survey-3_hu_5acae8d2a1278d15.png&#34; alt=&#34;Breakdown of how people are personally impacted by issues of digital privacy and security. 2% say these issues don&amp;rsquo;t impact their safety and well-being and are not important to them. 34% say they don&amp;rsquo;t impact their safety and well-being but are important to them. 43% say these issues sometimes impact their safety and well-being. 21% say these issues constantly impact their safety and well-being.&#34; width=&#34;740&#34; height=&#34;365&#34;&gt;



    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/refresh-survey-4_hu_c12aa604a8f47a52.png&#34; alt=&#34;Breakdown of what kind of work respondents do (multi-select). Most common answers: Researcher (27), Activist (17), Manager (16), Developer (15), Designer (14), Facilitator(9)&#34; width=&#34;740&#34; height=&#34;365&#34;&gt;



    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/refresh-survey-5_hu_cbbb8a5059c12eff.png&#34; alt=&#34;Breakdown of location. 60% Americas, 38% Europe, 2% Asia.&#34; width=&#34;740&#34; height=&#34;365&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;conclusions&#34;&gt;Conclusions&lt;/h3&gt;
&lt;p&gt;We can&amp;rsquo;t draw conclusions about our &lt;strong&gt;community&lt;/strong&gt; from this survey, since we used a convenience sample, drawn from Slack, Twitter, and some mailing lists. However, among the people who filled out the survey, we can draw some conclusions about &lt;strong&gt;ourselves&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;We need a new name.&lt;/strong&gt; The name Simply Secure is misleading. It only refers to part of our work, and it has some unfortunate associations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;We need a new color palette.&lt;/strong&gt; Our logo, color palette, and visual style are inappropriately playful. However, we shouldn&amp;rsquo;t swing too far in the other direction and go super serious.&lt;/li&gt;
&lt;li&gt;People who have known us longer are more likely to think our current branding is okay; people newer to us are more likely to be confused by it. Thus, &lt;strong&gt;changing our branding makes sense if we want our community to grow.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;We need to do a better job communicating the full range of what we do.&lt;/strong&gt; UX design, community work, and work with nonprofits and open source are all important parts of our identity that don&amp;rsquo;t come through clearly with our current branding.&lt;/li&gt;
&lt;li&gt;People (at least, the people who took the time to answer the survey) &lt;strong&gt;appreciate and understand our work!&lt;/strong&gt; Yay.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;next-steps&#34;&gt;&lt;strong&gt;Next steps&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;We&amp;rsquo;re going to undertake this process together with an advisory committee, made up of people who are part of our community. Through a series of workshops, they&amp;rsquo;ll help us generate ideas, narrow down our options, and recommend a new name and visual style. We&amp;rsquo;ll announce the advisory committee on this blog shortly.&lt;/p&gt;
&lt;p&gt;Any questions? Any thoughts? Drop a line anytime to Molly Wilson and Kelsey Smith at &lt;a href=&#34;mailto:refresh@superbloom.design&#34;&gt;refresh@superbloom.design&lt;/a&gt;. We&amp;rsquo;re looking forward to going on this journey with you!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Call for proposals, writer and storyteller, 5-year report</title>
      <link>https://superbloom.design/community/opportunities/writer-5-year-report/</link>
      <pubDate>Sat, 24 Oct 2020 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/community/opportunities/writer-5-year-report/</guid>
      <description>&lt;h2 id=&#34;the-deadline-for-applying-to-this-role-has-passed&#34;&gt;The deadline for applying to this role has passed.&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;We&amp;rsquo;re looking for a storycrafter to help us shape and share the tale of our organization&amp;rsquo;s last five years. Is it you?&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&#34;the-project&#34;&gt;The project&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You&amp;rsquo;ll create a written report that tells the story of Simply Secure&amp;rsquo;s projects and impact over the last 5 years. The report will be published in an interactive digital format. (You don&amp;rsquo;t need to be a web designer as well; right now we&amp;rsquo;re primarily looking for a writer.)&lt;/li&gt;
&lt;li&gt;This is a 3-month freelance contract, from approximately November 2020 to February 2021 (timing negotiable). We are a US 501(c)3 organization that has the ability to hire in the US and in the EU.&lt;/li&gt;
&lt;li&gt;We are inspired by work like:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://youngfeministfund.org/annual-reports/&#34;&gt;Frida&amp;rsquo;s annual reports&lt;/a&gt; (we love the energy of the yearly themes and the fresh, engaging, inspiring tone)&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://datasociety.net/annualreport/&#34;&gt;Data and Society&amp;rsquo;s annual report&lt;/a&gt; (we love the way this report makes it easy to see the highlights while also going in-depth about the organization&amp;rsquo;s work)&lt;/li&gt;
&lt;li&gt;The &lt;a href=&#34;https://foundation.mozilla.org/en/blog/when-content-moderation-hurts/&#34;&gt;Mozilla Internet Health Report&lt;/a&gt; (we love the way this brings an empathetic, human perspective to abstract topics)&lt;/li&gt;
&lt;li&gt;The &lt;a href=&#34;https://prototypefund.de/wp-content/uploads/2019/03/190319_der_prototype_fund_in_zahlen_DE.pdf&#34;&gt;Prototype Fund annual report&lt;/a&gt; (we love the way this shows the variety and long history of the org using simple, clear graphics)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;about-us&#34;&gt;About us&lt;/h3&gt;
&lt;p&gt;We are a small US 501(c)3 nonprofit organization, founded in 2014 with the goal of making security tools easier to use. We believed – and still do – that security doesn&amp;rsquo;t have to be confusing to end users. We&amp;rsquo;ve contributed design to a variety of tools that enhance security, such as &lt;a href=&#34;https://superbloom.design/learning/blog/branding-tails&#34;&gt;Tails&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/i2p-case-study&#34;&gt;I2P&lt;/a&gt; to &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;. We&amp;rsquo;ve held &lt;a href=&#34;https://superbloom.design/underexposed/2017-workshop&#34;&gt;salons&lt;/a&gt; and a &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-fellows&#34;&gt;residency&lt;/a&gt; around designing for security. But we&amp;rsquo;ve done a lot more than usable security. Just in the last year, we&amp;rsquo;ve launched a &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;decentralization pattern library&lt;/a&gt;; a &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report on trust and transparency in nonprofit funding&lt;/a&gt;; a &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;campaign to save internet freedom tech&lt;/a&gt;; a &lt;a href=&#34;https://hrcd.pubpub.org/&#34;&gt;community around human rights centered design&lt;/a&gt;; a &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;series of videos about trust and responsibility in design&lt;/a&gt;; and much, much more.&lt;/p&gt;
&lt;p&gt;(We&amp;rsquo;re actually doing a rebranding process, moving away from the name &amp;ldquo;Simply Secure.&amp;rdquo; &lt;a href=&#34;https://superbloom.design/learning/blog/simply-secure-rebranding-survey&#34;&gt;More info over here on the blog!&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&#34;about-you&#34;&gt;About you&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You love finding and telling stories. You get really excited about telling the story of a group of people growing a nonprofit organization that uses design to make the internet a more humane place&lt;/li&gt;
&lt;li&gt;You write clear, concise, and engaging prose meant to be read on the web&lt;/li&gt;
&lt;li&gt;You like working independently, in collaboration with a fully remote team&lt;/li&gt;
&lt;li&gt;You show up to remote meetings on time, prepared, with a list; you do what you say you&amp;rsquo;re going to do, on time and accurately&lt;/li&gt;
&lt;li&gt;You are comfortable advocating for yourself and your work to make sure that you&amp;rsquo;re getting what you need from us&lt;/li&gt;
&lt;li&gt;You understand the nuances of writing for an international audience and how to make your words direct and accessible without simplifying your message&lt;/li&gt;
&lt;li&gt;You are available to meet during our prime time hours (4-6pm Central Europe / 3-5pm UK / 10-12pm US Eastern / 7-9am US Pacific)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;nice-to-have&#34;&gt;Nice to have&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Knowledgeable about one or more of the following areas: open source software, internet freedom, tech criticism and activism, human rights&lt;/li&gt;
&lt;li&gt;Experienced in writing annual reports&lt;/li&gt;
&lt;li&gt;Expert in communicating with an international audience (ideally with fluency in languages other than English)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;sound-like-a-good-fit&#34;&gt;Sound like a good fit?&lt;/h3&gt;
&lt;p&gt;Please send us:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Examples of work you have written. With each link or document you send, please tell us about the &lt;strong&gt;timeline and process:&lt;/strong&gt; how did these pieces get created? Who was involved, what did the process look like, how long did it take?&lt;/li&gt;
&lt;li&gt;A (very short!) outline of how you would approach working with us on this report. What phases would this project have, and what would you need from us to make it successful?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Send these documents to Nicola Pratt at nicola [ at ] superbloom [ dot ] design by Monday, November 15, 2020.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;To help us combat bias while we review applications, please remove your name from the documents you send.&lt;/strong&gt; One person on our team will keep a list assigning a code name to your application while we review it. If we&amp;rsquo;d like to interview you, we&amp;rsquo;ll match your code name to your real name, and get in touch. (If removing your name from your work screws up the formatting, don&amp;rsquo;t worry, this is not a graphic design job! You can also put an obviously fake name in place of your real name to keep the formatting consistent.)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Design Under Pressure Slides (Molly Wilson, World Interaction Design Day 2020) (PDF)</title>
      <link>https://superbloom.design/learning/resources/slides-design-under-pressure-09-2020/</link>
      <pubDate>Tue, 01 Sep 2020 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/slides-design-under-pressure-09-2020/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Popping the Filter Bubble: Design Practices for Data Donation</title>
      <link>https://superbloom.design/learning/resources/popping-the-filter-bubble-design-practices-for-data-donation/</link>
      <pubDate>Thu, 06 Aug 2020 16:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/popping-the-filter-bubble-design-practices-for-data-donation/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/data_governance_graphic_hu_602679589f3c3e13.png&#34; alt=&#34;graphic linking data governance surveillance capitalism elections discrimination and polarization&#34; width=&#34;740&#34; height=&#34;329&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Algorithmic personalization affects everyone, whether we know it or not. It impacts the way we get our news, how we shop, and, concerningly, our &lt;a href=&#34;https://www.nytimes.com/2014/06/30/technology/facebook-tinkers-with-users-emotions-in-news-feed-experiment-stirring-outcry.html&#34;&gt;mental health&lt;/a&gt;. By determining what we read, algorithms shape our worldview. Most web users know little about the underlying technology that powers these algorithms, in part because they are proprietary trade secrets closely guarded by their companies.&lt;/p&gt;
&lt;p&gt;One proposal to shift the power dynamic is to support people to learn more about their “filter bubble” (&lt;a href=&#34;https://en.wikipedia.org/wiki/Filter_bubble&#34;&gt;a term coined by Eli Pariser&lt;/a&gt; to refer to the highly selective snapshot of the internet that people see). If more users safely share some of their data, researchers can investigate these personalization algorithms based on lived experience. This idea — people sharing their data for research — is frequently referred to as “data donation”.&lt;/p&gt;
&lt;p&gt;Though data donation is being used to explore interventions in decoding this closely guarded technology, it poses usability challenges as the concept is frequently counterintuitive.  People might reasonably think that the best way to protect themselves from the influence of these inscrutable algorithms is to shield their data, not share it. For one thing, donated data — without strong privacy protections — could be directly linked to individuals, and there is no good way for people to know exactly what they are giving up.&lt;/p&gt;
&lt;p&gt;Before you enthusiastically endorse a data donation program, you need to do some homework. Here are some key questions to keep in mind:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Can users be confident that the data collectors (e.g. researchers, application developers, organizations) have good intentions? Are the risks worth it? It’s important to think about these questions even if collectors&amp;rsquo; credentials and affiliations seem trustworthy.&lt;/li&gt;
&lt;li&gt;Who owns the donated data? What can the data be used for? For how long? Then what happens?&lt;/li&gt;
&lt;li&gt;Can these intentions and promises be verified and enforced?&lt;/li&gt;
&lt;li&gt;What will users know about the research and how will they agree to it? Could it be standardized? For example: I share x data for y reason with the oversight of z group.&lt;/li&gt;
&lt;li&gt;Would the findings drawn from the donated data serve everyone, or just a small percentage of people? Not everyone is equally likely to donate data, so how can we ensure we aren’t excluding the most vulnerable groups of society?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;how-can-we-design-for-data-donation&#34;&gt;How can we design for data donation?&lt;/h2&gt;
&lt;p&gt;In February 2020, we hosted a workshop with the &lt;a href=&#34;&#34;&gt;ALgorithms.EXposed&lt;/a&gt; (ALEX) team. The ALEX team is building browser extensions that enable people to learn more about how they are targetted by algorithms. As part of the workshop, our goal was to find out if people are interested in the idea of donating data about their lived experience online and how we can provide a safe and transparent experience to do so. Our [workshop report](/resources/S implySecure-ALEX-Workshop-Report.pdf) outlines our key findings in detail. Here are four key guidelines for data donation design in 2020 based on these findings:&lt;/p&gt;
&lt;h3 id=&#34;1-transparency-ensure-participant-awareness-in-every-step-of-the-process&#34;&gt;1. Transparency: Ensure participant awareness in every step of the process&lt;/h3&gt;
&lt;p&gt;Complete transparency is key to giving people the information they need to make informed choices. People need to know about the investigators, the research, the risks, and the future of their data. Participants’ comfort with sharing data depends not just on the goal, but also on the approach, especially the clarity and honesty of the communication around data sharing.&lt;/p&gt;
&lt;h3 id=&#34;2-consent-uphold-participant-control&#34;&gt;2. Consent: Uphold participant control&lt;/h3&gt;
&lt;p&gt;Informed consent is complicated — participants need to understand what their data is and where it’s going. But how can you collect informed consent without becoming a burden to the user? By offering a variety of controls, like reminders, repetition, and customization, people can choose the control model that works for them.&lt;/p&gt;
&lt;h3 id=&#34;3-consistency-reinforce-trust-by-relying-on-standards-of-interaction&#34;&gt;3. Consistency: Reinforce trust by relying on standards of interaction&lt;/h3&gt;
&lt;p&gt;Understandably, most people are unable to evaluate the trustworthiness of a system’s code, so will often rely on the visual and interaction design. The trust that comes from a standardized visual identity contributes to trust in the technology and organization.&lt;/p&gt;
&lt;h3 id=&#34;4-delivery-involve-participants-in-the-process&#34;&gt;4. Delivery: Involve participants in the process&lt;/h3&gt;
&lt;p&gt;Users are looking for an experience that gives back, whether through tools, resources, updates, results, or recognition. Simply being involved in the process can be an excellent means for people to educate themselves about the security and privacy of their data.&lt;/p&gt;
&lt;p&gt;As part of a community of researchers passionate about unveiling the mysteries of corporate algorithms, we want to give power back to the people. Reverse-engineering through data donation has a lot of potential to foster transparency and understanding. But as UX designers, developers, and researchers, we must do more than just support the idea of data donation; we must actively design better data processes. The issues of privacy and security of data are more important than ever, and we hope that with well-designed flows, everyone can start to see past the edges of their own filter bubbles.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Data, Decision-Making, &amp; Design: Measuring Internet Performance for Libraries and the Public Sector</title>
      <link>https://superbloom.design/learning/blog/data-decision-making-design-measuring-internet-performance-for-libraries-and-the-public-sector/</link>
      <pubDate>Mon, 03 Aug 2020 10:17:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/data-decision-making-design-measuring-internet-performance-for-libraries-and-the-public-sector/</guid>
      <description>&lt;p&gt;&lt;em&gt;Learn how we helped a group of libraries to make better decisions about their own internet services through the development of an independent data visualization tool.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;With the world changing around them, public libraries are working on the front lines of a fraying social safety net, supporting at-risk adults and children with everything from housing to criminal justice. This new role - relying heavily on web access - requires strong digital infrastructure, from internet speed to computer performance, from internet speed to software performance.&lt;/p&gt;
&lt;p&gt;However, public institutions like libraries don’t have access to data about their infrastructure as the private telecommunications companies that serve them. Without transparency of information, how can they ensure they’re making the most of their often-limited resources?&lt;/p&gt;
&lt;p&gt;This is where Simply Secure stepped in to help. Through tight collaboration and research with the group, our team set out to design a visualization tool that would allow users to access, understand, and ultimately make positive decisions based on the measurement data.&lt;/p&gt;
&lt;p&gt;Read on to learn more. &lt;a href=&#34;https://superbloom.design/resources/case_studies/Simply_Secure_M-Lab_Data_Decision-Making_Design.pdf&#34;&gt;Download the Case Study to explore the project in-depth&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;project-overview&#34;&gt;Project overview&lt;/h2&gt;
&lt;p&gt;To consistently and automatically measure internet performance, participating libraries installed small measurement devices — called ‘MLBN Murakami Devices’, developed by &lt;a href=&#34;https://measurementlab.net&#34;&gt;Measurement Lab&lt;/a&gt; — connected to wired and wireless ports in the library.&lt;/p&gt;
&lt;h2 id=&#34;the-work&#34;&gt;The work&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Research&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The team held an in-person workshop with 30 librarians from across the US, learning about the infrastructure, services, and providers at the libraries. Over the first year of the program, the research team conducted ten site visits to libraries across the US, engaging in focus groups with the community and interviews with the library staff.&lt;/p&gt;
&lt;p&gt;These sessions allowed us to see the overview of librarians’ jobs, patron needs, and the models of libraries, giving us the crucial context needed to create a more useful tool. It also taught us to leave our assumptions at the door - where we’d expected the tool to be most beneficial in cases of troubleshooting a poor connection, we learned that most libraries have quality internet connections. This allowed us to shift our scope of the tool’s development significantly.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Development&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Whenever there is collaboration — especially remote — communication is vital and the design deliverables make an impact on the efficiency of communication. This is where personas, user flows, and sketches come in handy.&lt;/p&gt;
&lt;p&gt;We crafted personas and user flows to communicate the various account types (admin, editor, viewer), define system goals, and plan for features.&lt;/p&gt;
&lt;p&gt;Next, we drafted and analyzed initial sketches, adding further scope of the tool until we were ready to create our first wireframes.&lt;/p&gt;
&lt;p&gt;From here, we worked with some libraries to test a prototype, collecting feedback and identifying key findings.&lt;/p&gt;
&lt;h2 id=&#34;the-impact&#34;&gt;The Impact&lt;/h2&gt;
&lt;p&gt;With version 1 of the MLBN Visualization website going live in Summer of 2020, libraries in the pilot program have the ability to view their internet performance data.&lt;/p&gt;
&lt;p&gt;Key positive applications of this tool include empowering libraries to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Monitor their performance day-to-day for a better experience for their users&lt;/li&gt;
&lt;li&gt;Understand their current service capacity, and when to make the decision to spend more on an upgraded service&lt;/li&gt;
&lt;li&gt;Enhance their reporting when it comes to transparency with stakeholders, from taxpayers to donors, to help build trust and make a case for greater investment when needed&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It’s rewarding to give our users something that will not only improve their jobs, but also help the community that they serve. We are excited to see the uses of the data in the future and make improvements through future phases and research. Finally, we learned that library workers are a wonderful group of people to work with and we look forward to future collaborations!&lt;/p&gt;
&lt;p&gt;&lt;em&gt;This work was supported through “&lt;a href=&#34;https://slis.simmons.edu/blogs/mlbn/&#34;&gt;Measuring Library Broadband Networks for the National Digital Platform&lt;/a&gt;,” a grant (award #&lt;a href=&#34;https://www.imls.gov/grants/awarded/lg-71-18-0110-18&#34;&gt;LG-71-18-0110-18&lt;/a&gt;) from by the Institute of Museum and Library Services (IMLS) National Leadership Grant for Libraries program. The research is led by Dr. Colin Rhinesmith, Assistant Professor and Director of the &lt;a href=&#34;https://comminformatics.net/&#34;&gt;Community Informatics Lab at the Simmons University School of Library and Information Science&lt;/a&gt;, along with &lt;a href=&#34;https://measurementlab.net&#34;&gt;Measurement Lab&lt;/a&gt; (M-Lab) and Internet2 to examine how advanced broadband measurement capabilities can support the infrastructure and services needed to respond to the digital demands of public library users across the U.S.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Defaults and Customization: When Design Meets Open Source</title>
      <link>https://superbloom.design/learning/blog/globaleaks-case-study/</link>
      <pubDate>Fri, 03 Jul 2020 14:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/globaleaks-case-study/</guid>
      <description>&lt;p&gt;GlobaLeaks is a browser-based platform that enables whistleblowers to securely submit documents to companies, newspapers, government bodies, and other organizations. It also enables these organizations to host a secure platform for handling, viewing, responding to, and administering whistleblower-submitted documents. It has grown steadily and successfully since 2012 and is currently used by over 600 organizations worldwide.&lt;/p&gt;
&lt;p&gt;Our design project, a collaboration between Simply Secure and Ura Design, aimed to further improve GlobaLeaks&amp;rsquo;s usability by focusing on the following areas: interface design, user journeys, accessibility, and localization. While Simply Secure focused on design research and UX recommendations, Ura Design took on the high-fidelity interface design and the GlobaLeaks brand guideline going forward.&lt;/p&gt;
&lt;p&gt;The following three themes emerged from our design work:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Customization&lt;/li&gt;
&lt;li&gt;Accessibility and Localization&lt;/li&gt;
&lt;li&gt;Brand and Trust&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;how-might-we-encourage-customization-while-improving-the-defaults&#34;&gt;How might we encourage customization while improving the defaults?&lt;/h2&gt;
&lt;p&gt;The biggest challenge for GlobaLeaks is to offer sensible defaults while allowing for a large degree of customization. Since the practice of whistleblowing varies in different contexts, we need to customize the whistleblower interface that adapts to the cultural background and communicates trustworthiness. This versatility is vital for establishing a relationship between the whistleblowers and the organizations that use GlobaLeaks.&lt;/p&gt;
&lt;p&gt;There are three roles for any GlobaLeaks installation: the Whistleblower who sends submission anonymously, the Administrator who sets up and maintains a copy of the platform (called an installation), and the Recipient who reads and processes the submissions. Allowing for customization shouldn’t distract from the need to provide “out-of-the-box” default options that make sense, not only to the Whistleblower but also to the people working behind a GlobaLeaks installation.&lt;/p&gt;
&lt;p&gt;To establish priority and clarity of customization options, we mapped out the relationship and points of contact among the main stakeholders of the platform. This allowed us to gain a deeper understanding of each role&amp;rsquo;s needs and identify their most-used features.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/gl-roles_hu_8a0e2c30c45890cf.png&#34; alt=&#34;gl-roles.png&#34; width=&#34;740&#34; height=&#34;316&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The relationship between the main stakeholders of a typical GlobaLeaks installation.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;As we realized that customization is key to communication, we wanted the new information architecture to encourage the Recipient to customize actively but also provide a default that is sufficient for those who don’t adjust settings. When it became clear that only certain options are relevant for certain contexts, it was easier to organize options with a card sorting exercise. For example, as Recipient directly communicates with Whistleblower, they should have permission to customize the questionnaires (submission form) and the text on the whistleblower interface, not the network and other technical settings.&lt;/p&gt;
&lt;p&gt;There are many open-source platforms that can be installed on various instances hosted by different organizations. Deciding on these defaults is perhaps the single most important task for any team working on highly customizable platforms.&lt;/p&gt;
&lt;h2 id=&#34;accessibility-and-localization&#34;&gt;Accessibility and Localization&lt;/h2&gt;
&lt;p&gt;There is no single design solution that will work for everyone. The global nature of GlobaLeaks means that it needs to be culturally and linguistically agnostic and customizable to a variety of contexts. Thorough research into the cultural, political, and social context of the target region reveals significant insights that help strengthen a design and enable it to serve better in a high-risk environment.&lt;/p&gt;
&lt;p&gt;In the case of GlobaLeaks, the credit card image shown after the submission was perceived differently depending on the whistleblower’s cultural background and knowledge. For example, during our user interviews, we found out whistleblowers from Vietnam weren&amp;rsquo;t confused by the credit card while whistleblowers from the USA believed that payment was required.&lt;/p&gt;
&lt;p&gt;To avoid miscommunication and misunderstanding, we recommend that organizations be considerate about their aesthetic choices and work closely with a native speaker of the language of installation or those who are familiar with the Whistleblowers&amp;rsquo; process.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/credit-card_hu_e4da6402935b53ac.png&#34; alt=&#34;credit-card.png&#34; width=&#34;740&#34; height=&#34;408&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Screenshot of the credit card image on the demo platform.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;branding-and-trust-how-might-we-create-a-trustworthy-experience-for-whistleblowers&#34;&gt;Branding and Trust: How might we create a trustworthy experience for whistleblowers?&lt;/h2&gt;
&lt;p&gt;GlobaLeaks faces a branding challenge: they provide the open-source platform but do not control the individual installations. Questions like “What is GlobaLeaks?” vs “What is the New York Times whistleblowing platform?” will arise for people who are curious about the platform. GlobaLeaks shouldn’t assume that people who are willing to trust the New York Times, will also trust a platform chosen by the New York Times to host whistleblower submissions.&lt;/p&gt;
&lt;p&gt;Organizations which use GlobaLeaks must develop an understanding of their whistleblower users and with that, establish a trust to increase engagement. Allowing for customization of CSS styles is only one part of the equation; it is equally important to help organizations adjust the language and manage cultural expectations.&lt;/p&gt;
&lt;p&gt;As an open-source submission framework, Globaleaks already provides source code that is more transparent and secure than closed-source technology. Open-source technology in itself is trustworthy, but potential whistleblowers need to be certain they know who they are sending a report to, and what is likely to happen afterwards. The whistleblower is unlikely to be familiar with GlobaLeaks and Hermes Center for Transparency and Digital Human Rights (the organization behind GlobaLeaks) so relying on GlobaLeaks/Hermes brand credibility alone isn&amp;rsquo;t sufficient.&lt;/p&gt;
&lt;p&gt;The appearance of a design should match the user&amp;rsquo;s emotional state. Yet, a professional look doesn’t always mean that it is trustworthy. Therefore, efficient communication and transparency are key for better user experience.&lt;/p&gt;
&lt;p&gt;We leveraged concise language and clean visuals to communicate trustworthiness and increase the transparency of the submission process. We wanted the mock-ups for the Whistleblower interface to be simple, clean, and easy to navigate. Additionally, we chose language that is friendly, easy to understand and be customizable to various geographical and cultural contexts.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/stop-it_hu_b7641de689213d89.png&#34; alt=&#34;stop-it.png&#34; width=&#34;740&#34; height=&#34;463&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;A whistleblower landing page mockup experimenting with a different tone of language.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In most open-source designs, the option to customize is often extensive. Customization should be easy while taking into consideration the power of defaults—especially in a highly sensitive platform like GlobaLeaks where trust and security are intertwined.&lt;/p&gt;
&lt;p&gt;With these three key takeaways, we hope to highlight the importance of research and the versatility of open-source design in projects that seek to serve a larger community.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/documentation/GlobaLeaks%20Report_May%202020.pdf&#34; class=&#34;button button--secondary read-more&#34; style=&#34;text-decoration: none;&#34;&gt;Read the full report&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This project was funded through OTF&amp;rsquo;s Usability Lab.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>A message to our community: save internet freedom tech</title>
      <link>https://superbloom.design/learning/blog/save-internet-freedom-tech/</link>
      <pubDate>Mon, 22 Jun 2020 09:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/save-internet-freedom-tech/</guid>
      <description>&lt;p&gt;&lt;em&gt;Our request to Congress to continue the fight to protect internet freedom worldwide - and how you can help.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Since our inception, the Simply Secure team has been committed to supporting people impacted by threats to privacy and safety through usability and design support. For several years, we have worked alongside the &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;, and its support and funding have allowed us to collaborate with many internet freedom projects. We have seen first hand how these resources have contributed to a stronger, safer, healthier, freer, and more open internet.&lt;/p&gt;
&lt;p&gt;This week, alongside more than 350 public interest and human rights organizations, we’ve &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;called on Congress&lt;/a&gt; to show real support to that same cause by committing to the protection of the Open Technology Fund and the crucial part it plays in defending global internet freedom.&lt;/p&gt;
&lt;h2 id=&#34;what-is-the-open-technology-fund&#34;&gt;What is the Open Technology Fund?&lt;/h2&gt;
&lt;p&gt;In the past eight years, the &lt;a href=&#34;https://www.opentech.fund/about/&#34;&gt;Open Technology Fund&lt;/a&gt; (OTF) and the projects it supports have allowed more than 2 billion people in over 60 countries to safely access the internet, free of censorship and surveillance. Through the development of open-source technologies and wider networks, the fund is one of the most prominent protectors of democracy and freedom of speech online. Until recently, the fund has also experienced widespread bipartisan support for its innovation, efficiency, and leadership.&lt;/p&gt;
&lt;h2 id=&#34;so-why-does-it-need-help&#34;&gt;So why does it need help?&lt;/h2&gt;
&lt;p&gt;Despite this track record of success, Michael Pack - newly appointed head of the U.S. Agency for Global Media (USAGM) - has this week dismissed the leadership and dissolved the board of the OTF alongside a number of other well-regarded institutions. &lt;a href=&#34;https://www.dw.com/en/trump-backed-us-global-media-agency-chief-under-fire-for-purge/a-53870348&#34;&gt;USAGM spending has also been frozen&lt;/a&gt;, sparking concerns that the agency plans to reallocate all government funding for the OTF.&lt;/p&gt;
&lt;p&gt;These drastic moves have also raised alarm bells around the chances of success for the proposed “&lt;a href=&#34;https://www.opentech.fund/news/introducing-open-technology-fund-authorization-act/&#34;&gt;Open Technology Fund Authorization Act&lt;/a&gt;”, which would establish the Open Technology Fund (OTF) as an independent grantee of the US Agency for Global Media. The act has long been supported across party lines, but now stands under threat.&lt;/p&gt;
&lt;h2 id=&#34;what-can-we-do&#34;&gt;What can we do?&lt;/h2&gt;
&lt;p&gt;As one of many organizations supported by the vital work of the OTF, the team at Simply Secure are dedicated to building a democratic online world. Please join us in requesting that congress continue to protect freedom of speech, thought, and education online. Sign the letter - and explore other ways you can help - at &lt;a href=&#34;https://saveinternetfreedom.tech/&#34;&gt;saveinternetfreedom.tech&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.opentech.fund/about/&#34;&gt;Learn more about the Open Technology Fund&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/what-we-do/&#34;&gt;Learn more about Simply Secure&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Introducing Decentralization Off The Shelf: 7 Maxims</title>
      <link>https://superbloom.design/learning/blog/decentralization-off-the-shelf-7-maxims/</link>
      <pubDate>Mon, 15 Jun 2020 09:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/decentralization-off-the-shelf-7-maxims/</guid>
      <description>&lt;p&gt;Our design research for a &lt;a href=&#34;https://superbloom.design/learning/blog/decentral-patterns-project&#34;&gt;decentralization pattern library&lt;/a&gt; has resulted in a report outlining the obstacles to decentralization as a whole.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://decentpatterns.xyz/report/&#34;&gt;Read the full report&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The potential of decentralization to contribute to a more equal society is huge. Where government and corporate control of information are causing harm, decentralized technologies can give power back through new data ownership and governance models. So why are these technologies not more widely adopted? What are the main obstacles to decentralization, and how can we solve them?&lt;/p&gt;
&lt;p&gt;In our latest research report, &lt;em&gt;Decentralization Off the Shelf: 7 Maxims&lt;/em&gt;, we interviewed 53 practitioners and led workshops with a total of 85 participants to find out. Here are the 7 key changes we need.&lt;/p&gt;
&lt;h3 id=&#34;1-we-need-to-collaborate-to-challenge-existing-power-structures-and-build-usable-technologies&#34;&gt;1: We need to collaborate to challenge existing power structures and build usable technologies.&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;The problem:&lt;/strong&gt; A focus on bespoke solutions to common problems results in missed opportunities for collaboration, a lack of common vocabulary, and higher access barriers for users.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The solution:&lt;/strong&gt; Practitioners need to seek collaboration with other projects targeting the same users and use cases, and pattern match with regard to design and architecture choices.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The problem:&lt;/strong&gt; The threat posed by decentralization to existing power structures means we can expect political and legal backlash as decentralized technologies become more popular. However, many projects are focused on their own products and not on this collective concern.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The solution:&lt;/strong&gt; In order to effectively challenge the status quo, we need to build a decentralization &lt;em&gt;movement&lt;/em&gt;. A movement involves collaborative strategizing and community organizing around a shared mission and values. Decentralization can learn here from adjacent movements.&lt;/p&gt;
&lt;h3 id=&#34;2-we-need-to-ensure-accessibility-and-usability-by-employing-best-practices-in-human-centered-design&#34;&gt;2: We need to ensure accessibility and usability by employing best practices in human centered design.&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;The problem:&lt;/strong&gt; Decentralization introduces concepts that may not be familiar to users who are used to centralized technologies. This can be confusing and discouraging for users. Explanations of decentralized technologies are often not clear and accessible, and there is a general lack of design and product thinking in the space.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The solution:&lt;/strong&gt; We need to work towards adopting shared language and interfaces across projects. Practitioners need to consistently apply best practices in human-centred design, and test products early and often with end users.&lt;/p&gt;
&lt;h3 id=&#34;3-we-need-investment-to-improve-the-independent-verifiability-and-resilience-of-our-infrastructure&#34;&gt;3: We need investment to improve the independent verifiability and resilience of our infrastructure.&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;The problem:&lt;/strong&gt; Decentralized protocols are still dependent on centralized points of failure such as cloud infrastructure, web browsers, app stores, and proprietary hardware.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The solution:&lt;/strong&gt; We need funder investment in solutions for closing these gaps and improving the independent verifiability and resilience of our shared infrastructure. We also need a more collaborative approach: for example, crafting protocols on a variety of modular libraries and collaborating on connectivity toolkits.&lt;/p&gt;
&lt;h3 id=&#34;4-we-need-better-onboarding-training-and-education-for-developers&#34;&gt;4: We need better onboarding, training, and education for developers.&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;The problem:&lt;/strong&gt; As the past decade has brought a revolution of content for upskilling and onboarding developers to build client-server applications, there has not been a similar educational movement for decentralized applications. Current educational materials are highly technical and disparate, with a steep learning curve requiring significant time investment.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The solution:&lt;/strong&gt; To attract and engage more developers, there is a dire need for clear and accessible educational content. We need better user experience for application developers with a focus on toolkits, query languages, and modular libraries. We also need to support projects to share more about their approach through the creation of accessible content.&lt;/p&gt;
&lt;h3 id=&#34;5-we-need-better-threat-modeling-for-safety-and-privacy&#34;&gt;5: We need better threat modeling for safety and privacy.&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;The problem:&lt;/strong&gt; While there is increased interest in decentralized technology as a response to surveillance capitalism, security breaches, and tech monopolization, few projects offer the security and service that end users are looking for from an alternative. Many decentralized projects do not have the resources to implement, communicate, and research good privacy and safety guarantees.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The solution:&lt;/strong&gt; We need to train more developers and designers on privacy and security approaches and skills, as well as funding research and development on security and anonymity innovations. We need to better communicate with end users about who they are trusting with their data and be more transparent about the privacy trade-offs we make.&lt;/p&gt;
&lt;h3 id=&#34;6-we-need-more-sustainable-funding-business-development-and-recruiting-models&#34;&gt;6: We need more sustainable funding, business development, and recruiting models.&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;The problem:&lt;/strong&gt; Sustainable funding is the biggest factor in the successful delivery and maintenance of any project, yet projects often fail to identify their target audience and develop sustainable funding models. Without sustainable funding, it is difficult to attract talent.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The solution:&lt;/strong&gt; We need to research, develop, and test community-driven funding models as they relate to the sustainability of people, projects, and protocols. We also need to work with project managers who can introduce business cases, prototyping processes, and more.&lt;/p&gt;
&lt;h3 id=&#34;7-we-need-clear-governance-and-decision-making-models-that-foster-diversity&#34;&gt;7: We need clear governance and decision-making models that foster diversity.&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;The problem:&lt;/strong&gt; Decision-making processes are often unclear and poorly communicated, resulting in conflicts in interests and expectations, as well as challenges when it comes to protocol updates.&lt;/p&gt;
&lt;p&gt;Practitioners operate within a relatively homogenized environment with respect to demographics and values, resulting in technologies that meet the needs of only a small part of the world’s population.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The solution:&lt;/strong&gt; We need open governance structures with strong social rules for decision-making that are communicated clearly to contributors and end users. Project leads should focus on diversifying their decision-making teams and the community as a whole.&lt;/p&gt;
&lt;br&gt;
&lt;p&gt;Making these changes would lead to better usability and wider adoption of decentralized technologies. To find out more about the solutions and how to implement them, &lt;a href=&#34;https://decentpatterns.xyz/&#34;&gt;read our report&lt;/a&gt;. Join the conversation on social media with #decentpatterns&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Designing From the Ground Up: A Case Study on I2P</title>
      <link>https://superbloom.design/learning/blog/i2p-case-study/</link>
      <pubDate>Thu, 04 Jun 2020 14:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/i2p-case-study/</guid>
      <description>&lt;h2 id=&#34;about-the-project&#34;&gt;About the project&lt;/h2&gt;
&lt;p&gt;The Invisible Internet Project (I2P) is a network layer that allows for censorship-resistant, peer-to-peer communication. Anonymous connections are achieved by encrypting the user&amp;rsquo;s traffic and sending it through a volunteer-run network of roughly 55,000 computers distributed around the world. It is similar to the Tor network, but focuses more on accessing hidden services than the Clearnet.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/mascot_hu_7ee04ee64a39f090.png&#34; alt=&#34;/mascot.png&#34; width=&#34;740&#34; height=&#34;740&#34;&gt;

&lt;em&gt;&amp;ldquo;itoopie&amp;rdquo;, I2P&amp;rsquo;s mascot.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This project, a collaboration between Simply Secure and Ura Design, provided usability feedback and strategic proposals for I2P. The goal was to make I2P a more usable tool for novice users, thereby adding to network traffic and anonymity guarantees for all users. While Simply Secure focused on a heuristics review and a workshop on information architecture, Ura Design will take on I2P&amp;rsquo;s brand identity as well as the console redesign.
̨̨̨̨̨&lt;/p&gt;
&lt;h2 id=&#34;design-problems-we-addressed&#34;&gt;Design problems we addressed&lt;/h2&gt;
&lt;h3 id=&#34;documentation-ux-and-website-ia&#34;&gt;Documentation UX and website IA&lt;/h3&gt;
&lt;p&gt;I2P&amp;rsquo;s biggest challenge in onboarding new users is explaining its complex technology in an accessible yet accurate fashion. The website provides a lot of information, but both the content and the navigation confuses new users.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/old_IA_hu_41a5714f233fd9cd.png&#34; alt=&#34;/old_IA.png&#34; width=&#34;740&#34; height=&#34;403&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;2017 version of I2P&amp;rsquo;s IA, which has since seen many updates.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The reasons for this are all-too-familiar: I2P&amp;rsquo;s long history as a volunteer-run open source project, the many different user groups it serves, and the inherent complexity of the technology itself all contribute to a large body of information on the website. Among the core audiences, we have new users, returning users, network operators, contributing developers, academic researchers, and the press. Contributing developers sub-divide into: core protocol developers, application developers, and router developers. Needless to say, that is a lot of technical information that needs to be documented and communicated, and the lack of a separate documentation only exacerbates the architecture here.&lt;/p&gt;
&lt;h3 id=&#34;terminology&#34;&gt;Terminology&lt;/h3&gt;
&lt;p&gt;Is a toot different from a tweet? Mastodon, a decentralised alternative to Twitter, is helping and not helping by using alternative terminology. Yes, a toot is different from a tweet—a toot is often only shared with people in your Mastodon community, whereas a tweet is always public; and no, tooting is just the cool kid&amp;rsquo;s word for tweeting, the core idea is the same.&lt;/p&gt;
&lt;p&gt;I2P has a similar issue with its relationship to the Tor project. Both are network layers operating on top of the internet, both aim to preserve user&amp;rsquo;s privacy and anonymity, both are community-run open source projects, and have an academic following. However, the Tor project much more known and used, and having &lt;a href=&#34;https://geti2p.net/en/comparison/tor&#34;&gt;diverging terminology&lt;/a&gt; for these two projects is confusing to most users, who will be more familiar with Tor.&lt;/p&gt;
&lt;h3 id=&#34;what-is-i2p&#34;&gt;What is &amp;ldquo;I2P&amp;rdquo;?&lt;/h3&gt;
&lt;p&gt;Related to terminology, there is a deeper question of what the term &amp;ldquo;I2P&amp;rdquo; stands for. Is it an &lt;a href=&#34;https://en.wikipedia.org/wiki/Twenty_Questions&#34;&gt;animal, a vegetable, or a mineral&lt;/a&gt;? Users need to create a working mental model of the technology to use it confidently. Right now I2P stands for both a network, a protocol, a community, a collection of websites (&amp;ldquo;eepsites&amp;rdquo;) and is associated with tools like the &amp;ldquo;I2P router&amp;rdquo;, &amp;ldquo;I2P console&amp;rdquo;, and &amp;ldquo;I2P browser&amp;rdquo;. How do things fit together in this universe? What are the nouns and the verbs that people absolutely need to understand to operate in this universe?&lt;/p&gt;
&lt;p&gt;When users encounter new technology, they are asking four kinds of questions:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;What is it? - Is it a community, an application, a database, a protocol, a platform, a service? Who&amp;rsquo;s behind it? Do I pay for it?&lt;/li&gt;
&lt;li&gt;How does it work? - What kind of technology is at work here? Does it use machine learning? Does it work offline? Does it collect data from me?&lt;/li&gt;
&lt;li&gt;How do I use it? - How do I connect? Do I need a smart phone? Do I need an account?&lt;/li&gt;
&lt;li&gt;Why should I use it? - What features does it provide? Does it meet my needs? Does it align with my values?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;It&amp;rsquo;s important that these questions are answered — not necessarily in this order, and not necessarily at the same level of detail, but ideally in separate, navigable sections on the homepage or &amp;ldquo;about&amp;rdquo; page. This could also come in form of a high-level guide to the ecosystem (a diagram, a glossary, an example workflow), as well as clear explanations that use metaphors and illustrations to support building new mental models.&lt;/p&gt;
&lt;h2 id=&#34;activities&#34;&gt;Activities&lt;/h2&gt;
&lt;p&gt;We worked with the I2P team in March/April 2020 on two items:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://github.com/uracreative/works/files/4445483/I2P.Heuristics.Review.SimSec.pdf&#34;&gt;heuristics review&lt;/a&gt; [PDF] with two designers testing I2P on their devices and systematically reviewing usability&lt;/li&gt;
&lt;li&gt;2 three-hour-long IA workshops with two I2P team members and two designers working through a new information architecture&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/context_IA_hu_8028ab8405de112a.jpg&#34; alt=&#34;/context_IA.jpg&#34; width=&#34;740&#34; height=&#34;473&#34;&gt;

&lt;em&gt;Understanding different use cases of the same content.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;results&#34;&gt;Results&lt;/h2&gt;
&lt;h3 id=&#34;new-information-architecture&#34;&gt;New Information Architecture&lt;/h3&gt;
&lt;p&gt;I2P is a complex project with many moving pieces—and that won&amp;rsquo;t change anytime soon. To help users navigate the website, we want to distinguish three larger contexts going forward: &lt;strong&gt;learning&lt;/strong&gt; (for learning about the project), &lt;strong&gt;guides&lt;/strong&gt; (for installation and network operation), and &lt;strong&gt;documentation&lt;/strong&gt; (for code contributions). Furthermore, we applied a generic navigation for standardized way-finding. The result is a sitemap that is deep rather than shallow: fewer items are surfaced at first to not overwhelm users.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/1-level_sitemap_hu_d6c632f4ec56b042.jpg&#34; alt=&#34;1-level_sitemap.jpg&#34; width=&#34;740&#34; height=&#34;467&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/old_menu_hu_d4520fa2a7c636d4.jpg&#34; alt=&#34;old_menu.jpg&#34; width=&#34;740&#34; height=&#34;393&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/new_menu_hu_ffaa992c9d92b92d.jpg&#34; alt=&#34;new_menu.jpg&#34; width=&#34;740&#34; height=&#34;455&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/homepage_hu_b9f6fd024f1a9246.jpg&#34; alt=&#34;homepage.jpg&#34; width=&#34;740&#34; height=&#34;693&#34;&gt;
&lt;/p&gt;
&lt;p&gt;The console&amp;rsquo;s architecture also received an update. Most of the changes revolve around grouping settings and configurations in a way that reduce the information presented at the same time (resulting in &amp;ldquo;deeper&amp;rdquo; trees again). One design question concerns &amp;ldquo;help and support&amp;rdquo; within the I2P console vs on the website (not always accessible once you are connecting over I2P). Should both sites have the same content for familiarity? Or should they differ because not every FAQ item is equally relevant? For instance, you wouldn&amp;rsquo;t lookup how to install I2P if you made it onto the I2P console. This is open to testing, but for now we opted for a &amp;ldquo;help and support&amp;rdquo; that is more relevant for the current context.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/console_IA_hu_49069e41f9f0f8ab.jpg&#34; alt=&#34;console_IA.jpg&#34; width=&#34;740&#34; height=&#34;837&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/console1_hu_96f74984246fcde5.jpg&#34; alt=&#34;console1.jpg&#34; width=&#34;740&#34; height=&#34;643&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/console2_hu_66fe07cea112e87a.jpg&#34; alt=&#34;console2.jpg&#34; width=&#34;740&#34; height=&#34;635&#34;&gt;
&lt;/p&gt;
&lt;p&gt;To support implementation, we also sketched first wireframes, both for the website and the console. The console&amp;rsquo;s main function is to control the connection over I2P; that will remain on the left as a side bar. The rest of the console is now a center stage with tabs—all familiar UI patterns. That allows the user to navigate different, additional functions of the console: a dashboard, a &amp;ldquo;browser&amp;rdquo; to explore other eepsites, an email client, and other applications. Configuration and support remain on the top right for constant reference.&lt;/p&gt;
&lt;h3 id=&#34;controlled-vocabulary&#34;&gt;Controlled Vocabulary&lt;/h3&gt;
&lt;p&gt;From now on, I2P will adopt more consistent language around its many tools. We have started working on a controlled vocabulary:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;I2P: a protocol for a network layer&lt;/li&gt;
&lt;li&gt;Eepsite -&amp;gt; I2P site: a website only accessible over the I2P&lt;/li&gt;
&lt;li&gt;I2P network: the active number of peers connected over I2P&lt;/li&gt;
&lt;li&gt;I2P launcher: an application that allows you to open an I2P-ready browser&lt;/li&gt;
&lt;li&gt;I2P console: an in-browser application that controls how you connect over I2P&lt;/li&gt;
&lt;li&gt;I2P browser: a browser that connects over I2P automatically (inactive project)&lt;/li&gt;
&lt;li&gt;Router -&amp;gt; I2P router: a translator for IP to I2P&lt;/li&gt;
&lt;li&gt;Peer/ Node -&amp;gt; Peer&lt;/li&gt;
&lt;li&gt;User -&amp;gt; Participant&lt;/li&gt;
&lt;li&gt;SusiMail -&amp;gt; I2P Mail&lt;/li&gt;
&lt;li&gt;SusiDNS -&amp;gt; I2P DNS Server&lt;/li&gt;
&lt;li&gt;Hidden Services -&amp;gt; I2P Network&lt;/li&gt;
&lt;li&gt;Hidden Services Manager -&amp;gt; I2P Network Manager&lt;/li&gt;
&lt;li&gt;I2P services -&amp;gt; I2P apps/applications&lt;/li&gt;
&lt;li&gt;Bote/I2PBote/i2p-Bote -&amp;gt; I2P bote&lt;/li&gt;
&lt;li&gt;itoopie: I2P&amp;rsquo;s mascot&lt;/li&gt;
&lt;li&gt;Clearnet -&amp;gt; the Internet&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;browser-extension-direction&#34;&gt;Browser extension direction&lt;/h3&gt;
&lt;p&gt;In the course of our design, questions around mental models kept resurfacing. Current users are expected to download a package installing the I2P launcher which in turn opens a browser console which in turn allows you to connect over I2P&amp;hellip; Anything reducing the number of steps required to get started would go toward wider adoption. The choice of UI depends on the scope of the console. If the I2P console should change all network connections over to I2P, then new users should install a general console application (similar to, for example, &lt;a href=&#34;https://mullvad.net/en/&#34;&gt;Mullvad&amp;rsquo;s VPN menu control&lt;/a&gt;). If the I2P console should only change the protocol for a specific browser, then new users should only have to install a browser extension. That way, users only have to make changes within one context to use the I2P network.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2020/browser_extension_hu_eb94511b59fc5799.jpg&#34; alt=&#34;browser_extension.jpg&#34; width=&#34;740&#34; height=&#34;649&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;process-recommendations&#34;&gt;Process recommendations&lt;/h3&gt;
&lt;p&gt;Going forward, the I2P team will do well adopting the following design practices.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Journey mapping&lt;/strong&gt;. What are the steps required to download and install I2P? Where are the pain points, and what could a guide/wizard do to prevent errors?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;User testing&lt;/strong&gt;. New ideas—be it words, UI, or entirely new products (such as a browser extension) would benefit from early testing. This needn&amp;rsquo;t be more than a few simple mockups. Make sure to test with your target users (not just the power users who are more easily available for testing).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;lessons&#34;&gt;Lessons&lt;/h2&gt;
&lt;p&gt;This project began as an information architecture project: in sorting through how information is classified and presented, and in analyzing different users and contexts, we arrived at a cleaner and more focused version of the website&amp;rsquo;s and console&amp;rsquo;s information architecture. But looking at IA is also looking at how things fundamentally fit together, and that surfaced &lt;strong&gt;underlying questions around strategy&lt;/strong&gt;. What tools and processes make most sense together? Which users and use cases do we want to prioritize? Answering these questions ultimately made decisions about terminology, content, and architecture easier.&lt;/p&gt;
&lt;p&gt;Another insight was that the typical user question around &amp;ldquo;how does it work&amp;rdquo; isn&amp;rsquo;t just about the underlying technology, but also about how one should use it. A protocol can be realized in many ways; the decisions of the I2P community to use a launcher, a browser, and a console is just one way of using the I2P protocol. While users need to learn about the features of I2P, it is equally important to &lt;strong&gt;explain how these different tools and processes work together&lt;/strong&gt;. To that end, diagrams or videos could help illustrate these concepts.&lt;/p&gt;
&lt;p&gt;Finally, a tactical design recommendation: when technology is new, &lt;strong&gt;rely on familiar patterns as much as possible&lt;/strong&gt;. New users will be struggling with concepts around routers, peers, and I2P sites. Designers should give users a handrail to grab onto, even if it&amp;rsquo;s just calling the Internet &amp;ldquo;the Internet&amp;rdquo; (rather than &amp;ldquo;the Clearnet&amp;rdquo; from the vantage point of I2P).&lt;/p&gt;
&lt;p&gt;This project was funded through OTF&amp;rsquo;s Usability Lab.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Persona Template with Threat Model (PDF)</title>
      <link>https://superbloom.design/learning/resources/persona-threat-model/</link>
      <pubDate>Mon, 27 Apr 2020 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/persona-threat-model/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Tarot Cards of Tech (Artefact Group)</title>
      <link>https://superbloom.design/learning/resources/tarot-cards-of-tech/</link>
      <pubDate>Mon, 27 Apr 2020 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/tarot-cards-of-tech/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Anxiety Game (Andrew Lovett-Barron)</title>
      <link>https://superbloom.design/learning/resources/anxiety-game/</link>
      <pubDate>Mon, 20 Apr 2020 19:15:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/anxiety-game/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Rapid Virtual Meeting Prototyping in the Age of a Pandemic</title>
      <link>https://superbloom.design/learning/blog/virtual-meetings/</link>
      <pubDate>Mon, 06 Apr 2020 10:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/virtual-meetings/</guid>
      <description>&lt;p&gt;&lt;em&gt;&lt;a href=&#34;https://foundation.mozilla.org/en/blog/rapid-virtual-meeting-prototyping-age-pandemic/&#34;&gt;Read the full post on Mozilla Foundation&amp;rsquo;s blog.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The public health crisis surrounding COVID-19 has escalated the need to create environments online for productive, collaborative, and spontaneous community work and convenings. And in many ways, the approaches and practices we’re experimenting with now will serve as a foundation for improved virtual collaboration well into the future.&lt;/p&gt;
&lt;p&gt;With that in mind, we wanted to share some learnings from a recent summit for 25+ &lt;a href=&#34;https://foundation.mozilla.org/en/what-we-fund/fellowships/&#34;&gt;Mozilla Fellows&lt;/a&gt; from all over the world that we had to move online in a very short timeframe (10 days to be exact). In this post, we’ll share:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;things we considered as we were having to switch gears quickly&lt;/li&gt;
&lt;li&gt;how we engaged with our community of participants and collaborators in that process, and&lt;/li&gt;
&lt;li&gt;things we learned as a result of this virtual event experiment.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;While this is an example of a rapid prototype for putting on a virtual convening for participants from multiple time zones around the world, many of the things we learned are applicable to events being planned without the same time constraints.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;a href=&#34;https://foundation.mozilla.org/en/blog/rapid-virtual-meeting-prototyping-age-pandemic/&#34;&gt;Read the full post on Mozilla Foundation&amp;rsquo;s blog.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Design Under Pressure Slides (Molly Wilson, Design Thinking Barcamp 2020) (PDF)</title>
      <link>https://superbloom.design/learning/resources/slides-design-under-pressure-04-2020/</link>
      <pubDate>Wed, 01 Apr 2020 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/slides-design-under-pressure-04-2020/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Recoding.Tech</title>
      <link>https://superbloom.design/work/projects/recoding_tech/</link>
      <pubDate>Sun, 05 Jan 2020 20:49:41 +0100</pubDate>
      <guid>https://superbloom.design/work/projects/recoding_tech/</guid>
      <description></description>
    </item>
    
    <item>
      <title>What are stress cases?</title>
      <link>https://superbloom.design/learning/resources/what-are-stress-cases/</link>
      <pubDate>Wed, 01 Jan 2020 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/what-are-stress-cases/</guid>
      <description>&lt;h3 id=&#34;what-are-stress-cases&#34;&gt;What are stress cases?&lt;/h3&gt;
&lt;p&gt;When an aspect of a person or a context is pushed to an extreme, that&amp;rsquo;s a stress case.&lt;/p&gt;
&lt;p&gt;Some people refer to a stress case as an &amp;ldquo;edge case.&amp;rdquo; We prefer the term &amp;ldquo;stress case&amp;rdquo; (which we learned about from Eric Meyer and Sara Wachter-Boettcher&amp;rsquo;s &lt;a href=&#34;https://abookapart.com/products/design-for-real-life&#34;&gt;Design for Real Life&lt;/a&gt;) because an &amp;ldquo;edge case&amp;rdquo; sounds like something that doesn&amp;rsquo;t happen very often.&lt;/p&gt;
&lt;p&gt;In fact, stress cases happen all the time! &lt;a href=&#34;https://aeon.co/essays/is-it-time-to-abandon-the-medical-construct-of-being-normal&#34;&gt;Nobody is normal&lt;/a&gt;. As appealing as your &amp;ldquo;target demographic&amp;rdquo; looks, you don&amp;rsquo;t actually control who will show up to use your design, and people are&amp;hellip; well, human. That patient, reasonable, calm, healthy, able-bodied, literate, accurate, safe, well-intentioned, and happy user in your mind&amp;rsquo;s eye doesn&amp;rsquo;t actually exist.&lt;/p&gt;
&lt;p&gt;And, of course, people and environments that aren&amp;rsquo;t &amp;ldquo;users&amp;rdquo; in the classical sense are very much part of your design. Has your rent been driven up by Airbnb, have stray dockless scooters made it hard for you to navigate your sidewalks, or has someone accidentally uncovered your family secrets because of a mail-in DNA test? (&lt;a href=&#34;&#34;&gt;Yes, this happens – a lot.&lt;/a&gt;) Systemic effects can cause even more stress cases than what you could find out from individual users.&lt;/p&gt;
&lt;p&gt;If you like doing the right thing for fellow humans, you need to design using stress cases. If the moral argument doesn&amp;rsquo;t convince you&amp;hellip; well, we doubt you like lawsuits, all-nighters, or bad PR. You can&amp;rsquo;t afford to ignore this.&lt;/p&gt;
&lt;h3 id=&#34;how-stress-cases-can-help-you&#34;&gt;How stress cases can help you&lt;/h3&gt;
&lt;p&gt;Stress cases are guideposts for decision-making. They guide your design research and your usability testing. And they can inspire great ideas that might not otherwise have occurred to you.&lt;/p&gt;
&lt;p&gt;A common misconception about stress cases is that they make you add extra features, which costs time and money. If this is happening, you&amp;rsquo;re thinking about stress cases too late in your process.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s say you&amp;rsquo;re working on a device, and you discover one month before release that it needs to be waterproof. At this late stage, waterproofing feels like an &amp;ldquo;extra feature.&amp;rdquo; But if you&amp;rsquo;d known a year ago that waterproofing was important, waterproofing would simply be part of your plan.&lt;/p&gt;
&lt;p&gt;Another common misconception is that stress cases are a big bummer that take the fun out of your creative process. This is only the case if you want it to be! For us, thinking creatively about how we can make solutions work for people, come rain or shine, fills us with energy and purpose.&lt;/p&gt;
&lt;h3 id=&#34;what-youll-find-here&#34;&gt;What you&amp;rsquo;ll find here&lt;/h3&gt;
&lt;p&gt;We&amp;rsquo;ve put together some methods to help you use stress cases with your product, service, or experience design teams.&lt;/p&gt;
&lt;p&gt;We can also offer you individual help with various aspects of stress cases.&lt;/p&gt;
&lt;p&gt;This page is a work in progress, and we&amp;rsquo;d love to hear your feedback so far. Email molly [ at ] superbloom [ dot ] design.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Happy New Year from Simply Secure: 2019 Reflections</title>
      <link>https://superbloom.design/learning/blog/year-end-2019/</link>
      <pubDate>Tue, 31 Dec 2019 10:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/year-end-2019/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/2019-yearinreview_hu_cabf2bac60c21563.png&#34; alt=&#34;Cookie banner&#34; width=&#34;740&#34; height=&#34;463&#34;&gt;
&lt;/p&gt;
&lt;p&gt;It’s hard to believe it, but 2019 is coming to an end! It’s been a big year at Simply Secure, leveraging design and usability to make tools safer and better protect user privacy. We’ve been trying out new ideas, working with new projects, experimenting with new formats, engaging in new spaces, and all with an eye towards supporting the community where they need it. I’ve been honored to &lt;a href=&#34;https://superbloom.design/learning/blog/hello-georgia&#34;&gt;lead the team&lt;/a&gt; for a full year now (!!!), and I can’t wait to see what’s to come in 2020. Our mission feels more critical than ever now, so I hope you’ll consider supporting us this year, and sharing our work with your network.&lt;/p&gt;
&lt;h2 id=&#34;2019-accomplishments&#34;&gt;2019 Accomplishments&lt;/h2&gt;
&lt;h3 id=&#34;design--ux-support&#34;&gt;Design &amp;amp; UX Support&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;We worked with projects like &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;, an extension that gives users control over the scripts that run in their browsers, and &lt;a href=&#34;https://aleph.occrp.org/&#34;&gt;OCCRP Aleph&lt;/a&gt;, a data tool for journalists focused on organized crime and corruption. These tools are now easier to use, safer, and more effective for their users’ needs.&lt;/li&gt;
&lt;li&gt;Through a partnership with &lt;a href=&#34;https://codeforscience.org/&#34;&gt;Code for Science &amp;amp; Society&lt;/a&gt;, we started new collaborations with &lt;a href=&#34;https://prereview.org/&#34;&gt;PREreview&lt;/a&gt;, a tool aiming to diversify and open science by enabling open review of preprints, and &lt;a href=&#34;https://www.measurementlab.net/&#34;&gt;Measurement Lab&lt;/a&gt;, an open internet measurement platform.&lt;/li&gt;
&lt;li&gt;In collaboration with &lt;a href=&#34;https://www.mozilla.org/en-US/&#34;&gt;Mozilla&lt;/a&gt; and many industry partners, the University of Dundee launched the Open Design of Trusted Technology (Open DoTT) PhD program!&lt;/li&gt;
&lt;li&gt;Of course, we continued our core partnerships, coaching projects in the &lt;a href=&#34;https://prototypefund.de/en/&#34;&gt;Prototype Fund&lt;/a&gt; &amp;amp; working with teams through the &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Open Tech Fund’s Usability Lab&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;As the year comes to a close, we’ve been working with the &lt;a href=&#34;https://www.globaleaks.org/&#34;&gt;GlobaLeaks&lt;/a&gt; team to improve the usability of their whistleblowing platform and kicking off a project with &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;OTF&lt;/a&gt; to improve their application process.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;open-research--tools&#34;&gt;Open Research &amp;amp; Tools&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;We released two video series: &lt;a href=&#34;https://superbloom.design/learning/blog/intro-design-spots&#34;&gt;Design Spots&lt;/a&gt;, supported by the &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Tech Fund&lt;/a&gt;, and &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;Tea Time&lt;/a&gt;, supported by &lt;a href=&#34;https://www.adobe.com/&#34;&gt;Adobe&lt;/a&gt;. &lt;a href=&#34;https://superbloom.design/learning/blog/intro-design-spots&#34;&gt;Design Spots&lt;/a&gt; introduces human-centered design for people who are new at design and usability work, while bringing a focus on security and high-risk users. In Tea Time, we dig into issues around trust, responsibility, ethics and externalities in design.&lt;/li&gt;
&lt;li&gt;In June, we released &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;On Trust and Transparency&lt;/a&gt;, a report on our research with Luminate’s portfolio projects on the complex environment and relationships of the funding experience. Nine insights and thirty-four recommendations emerged from the work with themes around the &lt;a href=&#34;https://ontrustandtransparency.report/themes/funding-approach-process&#34;&gt;funding approach and process&lt;/a&gt;, &lt;a href=&#34;https://ontrustandtransparency.report/themes/trust-power&#34;&gt;trust and power&lt;/a&gt;, &lt;a href=&#34;https://ontrustandtransparency.report/themes/funder-identity-culture&#34;&gt;funder identity and culture&lt;/a&gt;, and &lt;a href=&#34;https://ontrustandtransparency.report/themes/assessing-impact&#34;&gt;assessing impact&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;We started research on &lt;a href=&#34;https://superbloom.design/learning/blog/decentral-patterns-project&#34;&gt;UX patterns in decentralized applications&lt;/a&gt;, working to build a library that can help the community learn from each other and make decentralized tools easier to understand and use.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;building-community--convening&#34;&gt;Building Community &amp;amp; Convening&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;In January, we ran &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-2019-recap&#34;&gt;our first-ever residency&lt;/a&gt;, hosting 10 fellows working on projects at critical intersections of technology and society.&lt;/li&gt;
&lt;li&gt;We presented our work all over the world, giving talks at conferences, meetups and events including &lt;a href=&#34;https://archive.fosdem.org/2019/schedule/event/designing_for_security/&#34;&gt;FOSDEM&lt;/a&gt;, &lt;a href=&#34;https://media.ccc.de/v/Camp2019-10368-beyond_the_pile_of_knobs&#34;&gt;CCCamp&lt;/a&gt;, &lt;a href=&#34;https://www.meetup.com/dweb-berlin/events/266070278/&#34;&gt;DWeb&lt;/a&gt;, &lt;a href=&#34;https://internetfreedomfestival.org/&#34;&gt;Internet Freedom Festival&lt;/a&gt;, &lt;a href=&#34;https://www.rightscon.org/&#34;&gt;RightsCon&lt;/a&gt;, &lt;a href=&#34;https://www.mozillafestival.org/en/&#34;&gt;Mozilla Festival&lt;/a&gt;, &lt;a href=&#34;&#34;&gt;Front Conference&lt;/a&gt;, &lt;a href=&#34;https://www.youtube.com/watch?v=iS9bMIWx4dQ&#34;&gt;AMUSE&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/learning/blog/mydata&#34;&gt;MyData&lt;/a&gt;, &lt;a href=&#34;&#34;&gt;Personal Democracy Forum&lt;/a&gt;, and on &lt;a href=&#34;https://podcasts.apple.com/us/podcast/privacy-trust-and-good-design/id1437677219?i=1000450089010&#34;&gt;Adobe’s Wireframe podcast&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;We worked with &lt;a href=&#34;http://accessnow.org/&#34;&gt;Access Now&lt;/a&gt;, &lt;a href=&#34;https://www.eff.org/&#34;&gt;EFF&lt;/a&gt;, and &lt;a href=&#34;https://internews.org/&#34;&gt;Internews&lt;/a&gt; to organize and host convenings around human rights centered design at &lt;a href=&#34;https://www.rightscon.org/&#34;&gt;RightsCon&lt;/a&gt;, &lt;a href=&#34;https://www.mozillafestival.org/&#34;&gt;MozFest&lt;/a&gt; (&lt;a href=&#34;https://ti.to/simply-secure/human-rights-centered-design-ai-mozhouse/en&#34;&gt;#HRCD4AI&lt;/a&gt;), the &lt;a href=&#34;https://aspirationtech.org/events/devsummit19&#34;&gt;Nonprofit Developer Summit&lt;/a&gt;, and &lt;a href=&#34;https://radicalnetworks.org/&#34;&gt;Radical Networks&lt;/a&gt;, bringing together people from digital security, human rights, tech and design to talk about how we can better center human rights in our work and support each other as a community.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2020-looking-ahead&#34;&gt;2020 Looking Ahead&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;We’re excited to be planning projects with &lt;a href=&#34;https://delta.chat/en/&#34;&gt;delta.chat&lt;/a&gt;, &lt;a href=&#34;https://metrics.torproject.org/&#34;&gt;Tor Metrics&lt;/a&gt;, &lt;a href=&#34;https://www.mozilla.org/en-US/moss/&#34;&gt;Mozilla’s Open Source Support&lt;/a&gt; (MOSS) program, &lt;a href=&#34;https://internews.org/&#34;&gt;Internews&lt;/a&gt;, and &lt;a href=&#34;https://twitter.com/brainwane/status/1202375339332296704&#34;&gt;Python’s PIP CLI&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;We are piloting a fiscally sponsored projects model (&lt;em&gt;more soon!&lt;/em&gt;)&lt;/li&gt;
&lt;li&gt;We hope to expand our community of advisors (&lt;em&gt;reach out if you’d like to learn more!&lt;/em&gt;)&lt;/li&gt;
&lt;li&gt;And we hope to run another Underexposed residency and more human rights centered design (#HRCD) convenings, supporting a growing community of people working to build usable tools that protect our safety and privacy.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;With support from people like you, we are able to support more people and projects around the world through design and ux support, mentoring, resources, open research, events, workshops, and an online community.&lt;/p&gt;
&lt;p&gt;Let’s keep working to &lt;em&gt;build trustworthy technology&lt;/em&gt; together.&lt;/p&gt;
&lt;p&gt;See you in 2020!&lt;/p&gt;
&lt;p&gt;Georgia&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/support-us/&#34;&gt;Donate to support our work&lt;/a&gt; via &lt;a href=&#34;https://www.paypal.com/donate/?token=SeIKuUPaIZoWy469U2tcPvdsYy4Ptwjkg6omagjfRk9kzg02gV9f3FK5-Itwv_UHTF1PIG&amp;amp;country.x=US&amp;amp;locale.x=US&#34;&gt;Paypal&lt;/a&gt;, &lt;a href=&#34;https://opencollective.com/underexposed&#34;&gt;OpenCollective&lt;/a&gt; or check. If your employer uses &lt;a href=&#34;https://causes.benevity.org/causes/840-472462310?lang=en&#34;&gt;Benevity&lt;/a&gt;, please consider setting up a match or a recurring donation. Follow us on &lt;a href=&#34;http://twitter.com/simplysecureorg&#34;&gt;Twitter&lt;/a&gt;, &lt;a href=&#34;http://facebook.com/simplysecureorg/&#34;&gt;Facebook&lt;/a&gt;, &lt;a href=&#34;https://www.linkedin.com/company/simplysecureorg/&#34;&gt;LinkedIn&lt;/a&gt;, &lt;a href=&#34;http://instagram.com/simplysecure/&#34;&gt;Instagram&lt;/a&gt; and &lt;a href=&#34;https://medium.com/simply-secure&#34;&gt;Medium&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Iconography of Security</title>
      <link>https://superbloom.design/learning/blog/iconography-of-security/</link>
      <pubDate>Sat, 07 Dec 2019 10:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/iconography-of-security/</guid>
      <description>&lt;p&gt;&lt;em&gt;&lt;a href=&#34;https://24ways.org/2019/iconography-of-security/&#34;&gt;Read the full post at 24ways.org&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;congratulations-youre-locked-out-the-paradox-of-security-visuals&#34;&gt;Congratulations, you’re locked out! The paradox of security visuals&lt;/h3&gt;
&lt;p&gt;Designers of technology are fortunate to have an established visual language at our fingertips. We try to use colors and symbols in a way that is consistent with people’s existing expectations. When a non-designer asks a designer to “make it intuitive,” what they’re really asking is, “please use elements people already know, even if the concept is new.”&lt;/p&gt;
&lt;h3 id=&#34;lots-of-options-for-security-icons&#34;&gt;Lots of options for security icons&lt;/h3&gt;
&lt;p&gt;We’re starting to see more consistency in the symbols that tech uses for privacy and security features, many of them built into robust, standardized icon sets and UI kits. To name a few: we collaborated with Adobe in 2018 to create the &lt;a href=&#34;https://blog.adobe.com/en/publish/2018/06/19/free-adobe-xd-ui-kit-private-file-sharing-prioritizes-security&#34;&gt;Vault UI Kit&lt;/a&gt;, which includes UI elements for security, like touch ID login and sending a secure copy of a file. Adobe has also released a UI kit for &lt;a href=&#34;https://blog.adobe.com/en/publish/2019/09/19/cookie-banner-ui-kit-design-consent-and-disclaimers-users-can-trust&#34;&gt;cookie banners&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;a href=&#34;https://24ways.org/2019/iconography-of-security/&#34;&gt;Read the full post at 24ways.org&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Open source &amp; branding – a contradiction?</title>
      <link>https://superbloom.design/learning/blog/branding-tails/</link>
      <pubDate>Thu, 21 Nov 2019 10:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/branding-tails/</guid>
      <description>&lt;p&gt;Previously at Simply Secure, we&amp;rsquo;ve talked about the &lt;a href=&#34;https://superbloom.design/learning/resources/tea-time-trust-consistency&#34;&gt;power of consistent visual design&lt;/a&gt;, how to use &lt;a href=&#34;https://superbloom.design/learning/resources/color-message&#34;&gt;color schemes&lt;/a&gt; and &lt;a href=&#34;https://superbloom.design/learning/resources/nostalgia-trust-and-brand&#34;&gt;logos&lt;/a&gt;, and what a &lt;a href=&#34;https://superbloom.design/learning/resources/how-to-name-your-app&#34;&gt;good name&lt;/a&gt; can do for a project. All of these elements help make a tool trustworthy and easy to use. What we don&amp;rsquo;t usually say is that these elements make up what, in the for-profit world, is often called &lt;em&gt;branding&lt;/em&gt;.&lt;/p&gt;
&lt;h2 id=&#34;why-branding-is-a-dirty-word&#34;&gt;Why branding is a dirty word&lt;/h2&gt;
&lt;p&gt;&amp;ldquo;Branding&amp;rdquo; is a dirty word in open source for several reasons. We would like people to be able to make technically-informed, feature-centric decisions untainted by smooth advertising; most open-source teams would prefer their work to speak for itself. It would be counterproductive and in bad taste for an open-source project to appear to be competing against other projects—ideally, we don&amp;rsquo;t see similar tools as &amp;ldquo;the competition,&amp;rdquo; but as potential collaborators and partners. It&amp;rsquo;s easy to see why &amp;ldquo;branding&amp;rdquo; sounds like a manipulative side effect of capitalism that we&amp;rsquo;d prefer not to associate ourselves with.&lt;/p&gt;
&lt;p&gt;However, if open-source teams can get beyond our instinctive dislike of the term &amp;ldquo;branding,&amp;rdquo; some of the goals and principles of branding are nonetheless quite relevant to us. Among other things, a strong brand can:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;make you seem professional and trustworthy enough to use&lt;/li&gt;
&lt;li&gt;help you be recognized across different platforms and devices&lt;/li&gt;
&lt;li&gt;communicate your principles and your ethical stance, both internally and externally&lt;/li&gt;
&lt;li&gt;help people find you in the first place, and help them recommend you to others&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Here at Simply Secure, we use the word &amp;ldquo;identity&amp;rdquo; instead of &amp;ldquo;branding&amp;rdquo; when talking about open-source and nonprofit projects. This choice not only reflects the non-commercial nature of our approach, but also the fact that our goals aren&amp;rsquo;t the same as classical branding: we&amp;rsquo;re trying to clearly and accurately communicate the essence of a project, but we&amp;rsquo;re not trying to sell, convince, or manipulate.&lt;/p&gt;
&lt;h2 id=&#34;the-problem-with-we-need-a-logo&#34;&gt;The problem with &amp;ldquo;we need a logo&amp;rdquo;&lt;/h2&gt;
&lt;p&gt;When open-source projects approach designers, their request is often for a logo, a color scheme, an explainer illustration or diagram, or maybe a name or tagline. These are, after all, the elements that will be visible in the end product. Unfortunately, this work runs into several common pitfalls:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Teams waste time in long discussions because they have no heuristics or basis for decision-making. Endless loops of &amp;ldquo;I like this, I don&amp;rsquo;t like this&amp;hellip;&amp;rdquo; mean trying to deal with random, disconnected preferences instead of consensus based on agreed-upon principles.&lt;/li&gt;
&lt;li&gt;The designer doesn&amp;rsquo;t know where to start, so just makes educated guesses. The rest of the team doesn&amp;rsquo;t love the design work, but can&amp;rsquo;t really explain why.&lt;/li&gt;
&lt;li&gt;The designs don&amp;rsquo;t create a coherent look and feel, and the tool ends up looking as mismatched and patched-together as before (which doesn&amp;rsquo;t exactly enhance the project&amp;rsquo;s trustworthiness or visibility).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Laying the foundation for identity work can help any team avoid these problems. What&amp;rsquo;s more, identity work helps with so much more than visuals. How people perceive your project is also determined by the voice and tone that you adopt when interacting with people. Are you a serious project offering professional services, or are you a playful team engaging with people interested in your topic? Are you politically driven, or do you remain as impartial as possible? Getting answers to these questions will serve as the basis for making many future decisions, from how to organize your FAQ page to how to phrase an important alert.&lt;/p&gt;
&lt;h2 id=&#34;tails-a-case-study-of-open-source-identity-work&#34;&gt;Tails: a case study of open-source identity work&lt;/h2&gt;
&lt;p&gt;As a case study of how identity work can happen in open source, we&amp;rsquo;re going to dive into the work we recently did with &lt;a href=&#34;https://tails.boum.org/&#34;&gt;Tails&lt;/a&gt;. Tails is an operating system that you can stick into any computer and boot from a USB stick. It&amp;rsquo;s a powerful tool for privacy, anonymity, and circumvention, so it needs to be understandable by activists, journalists, and other citizens who may not be experts in tech.&lt;/p&gt;
&lt;p&gt;Tails approached Simply Secure to help create an accessible explanation of how Tails works. We quickly realized that, before we could fine-tune an explanation of Tails, we needed to understand the voice, tone, and visuals that would be appropriate for Tails&amp;rsquo; audience. sajolida, who led and shepherded this project from the Tails side, framed the goals of the work by paraphrasing Mozilla&amp;rsquo;s questions about &lt;a href=&#34;https://design.firefox.com/values/&#34;&gt;Firefox&amp;rsquo;s values&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Is this Tailsy? Is what we&amp;rsquo;re making a clear expression of what it means to be Tails? What will make it more Tails? What will we not do because it&amp;rsquo;s not true to Tails?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Starting an open discussion about these questions in an unstructured forum could take months, even years, with no endpoint in sight. We wanted actionable answers, so we opted for a highly &lt;strong&gt;collaborative&lt;/strong&gt; yet &lt;strong&gt;structured&lt;/strong&gt; process.&lt;/p&gt;
&lt;p&gt;We began with a half-day identity and values workshop in August 2018, conducted onsite near Berlin with the entire core Tails team. The goal of the workshop was to align around Tails&amp;rsquo; mission and values. We chose exercises that encouraged us to capture not just what Tails is as a technology, but &lt;strong&gt;who&lt;/strong&gt; Tails is for and &lt;strong&gt;how&lt;/strong&gt; Tails helps them. Here are a few of them:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What, how, why. We asked everyone in the workshop to define &lt;strong&gt;what&lt;/strong&gt; Tails does, &lt;strong&gt;how&lt;/strong&gt; Tails does this, and &lt;strong&gt;why&lt;/strong&gt; Tails does it.&lt;/li&gt;
&lt;li&gt;Values. We asked each member of the team to choose the top 4 words that, to them, described the essence of Tails. Is Tails serious? Modern? Accessible? Reliable? Complex? Versatile? We provided a list of words, but also encouraged everyone to come up with their own words.&lt;/li&gt;
&lt;li&gt;X but not Y. Most successful identities fall in the happy medium between two extremes. We asked team members to frame Tails as &amp;ldquo;X but not Y,&amp;rdquo; for example, &amp;ldquo;accessible but not playful&amp;rdquo; or &amp;ldquo;diverse but not fragmented.&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;After the workshop, we collected all this input and translated it into 4 possible identities for Tails. They all capture different aspects of Tails, exaggerating these aspects somewhat in order to elicit strong feedback:&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Tails_all_four_hu_c851f5c322e8f824.png&#34; alt=&#34;Tails suggestions&#34; width=&#34;740&#34; height=&#34;1033&#34;&gt;
&lt;/p&gt;
&lt;p&gt;We posted these identities online and gathered feedback from the Tails community. Then we synthesized that feedback into a final draft, together with the core Tails team, and the end result was this mission and value statement for Tails:&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Tails_final_hu_f9fd4d4a11fc2de6.png&#34; alt=&#34;Tails identity&#34; width=&#34;740&#34; height=&#34;748&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;See everything at &lt;a href=&#34;https://tails.boum.org/contribute/mission/&#34;&gt;https://tails.boum.org/contribute/mission/&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This identity document serves as the basis for all design decisions related to Tails. &amp;ldquo;How do we explain Tails to people?&amp;rdquo; might previously have been difficult to answer, especially for a diverse and distributed core team. But now it&amp;rsquo;s much more straightforward to evaluate colors, layouts, illustrations, and writing, even for people who don&amp;rsquo;t have a lot of experience making decisions like these. Instead of a question of personal preference, it becomes a question of &amp;ldquo;does this fit Tails?&amp;rdquo; As sajolida puts it, identity work is the way to help other decisions move forward.&lt;/p&gt;
&lt;p&gt;Want to try it yourself? Here&amp;rsquo;s our &lt;a href=&#34;https://superbloom.design/resources/identity_worksheet.pdf&#34;&gt;template for an identity worksheet&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>I Read About &#34;Design For Trust&#34;; So You Don&#39;t Have To</title>
      <link>https://superbloom.design/learning/blog/design-trust/</link>
      <pubDate>Thu, 10 Oct 2019 10:08:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/design-trust/</guid>
      <description>&lt;p&gt;What is &amp;ldquo;design for trust&amp;rdquo;? I&amp;rsquo;d heard this phrase at enough design and design thinking conferences, and &lt;a href=&#34;https://uxdesign.cc/design-for-trust-building-products-47113c90e8d2&#34;&gt;all&lt;/a&gt; &lt;a href=&#34;https://www.forbes.com/sites/marcelasapone/2018/06/08/scaling-a-human-tech-startup/#3e2897456f37&#34;&gt;over&lt;/a&gt; &lt;a href=&#34;https://uxdesign.cc/8-ux-surefire-ways-to-design-for-trust-7d3720b57a4c&#34;&gt;design&lt;/a&gt; &lt;a href=&#34;https://blog.prototypr.io/how-to-design-for-trust-in-digital-services-ae4f9f82f7a4?gi=70f66ab2bd64&#34;&gt;and innovation blogs&lt;/a&gt;, but the more I read, the less the phrase seemed to mean. I really &lt;em&gt;wanted&lt;/em&gt; this to be more than a buzzword! So I started to comb through what people were saying on the internet, hoping that I&amp;rsquo;d find something I could both use and believe in.&lt;/p&gt;
&lt;p&gt;My starting point was design for trust&amp;rsquo;s big break in 2016. 2016 was when Joe Gebbia, one of the founders of Airbnb, gave a &lt;a href=&#34;https://www.ted.com/talks/joe_gebbia_how_airbnb_designs_for_trust?language=en&#34;&gt;TED talk entitled &amp;ldquo;Design for Trust,&amp;rdquo;&lt;/a&gt; neatly staking a claim to the phrase. Gebbia describes how Airbnb uses design to make people overcome their inhibitions to let strangers stay in their homes. As an exercise, Gebbia asks people to unlock their phones and hand them to the people next to them. &amp;ldquo;That tiny sense of panic you feel right now is exactly how hosts feel the first time they open their home,&amp;rdquo; he says, to a laughing audience.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/airbnb-ted_hu_f75c39e0f611dc9f.png&#34; alt=&#34;Airbnb talk at TED about design for trust,  2016&#34; width=&#34;740&#34; height=&#34;397&#34;&gt;

&lt;em&gt;Image: TED.com&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In order for Airbnb to work, Gebbia needed people to become comfortable doing something that previously made them uncomfortable. You can see why his definition of &amp;ldquo;design for trust&amp;rdquo; had instant appeal. If designers can make people do stuff they otherwise wouldn&amp;rsquo;t want to do, to disclose information normally kept private, that provides all kinds of value to a company. Framed this way, &amp;ldquo;designing for trust&amp;rdquo; is just a benevolent-sounding mask for using design to market, upsell, and manipulate. Is this really all that &amp;ldquo;design for trust&amp;rdquo; means – convincing people to take actions they&amp;rsquo;d rather not?&lt;/p&gt;
&lt;p&gt;Well. That&amp;rsquo;s depressing. We can, and need to, do better. So I combed the internet for writing about design and trust, as well as &lt;a href=&#34;https://superbloom.design/learning/blog/Trust-Responsibility-Tea-Time&#34;&gt;shooting some videos on the topic&lt;/a&gt; with my colleague Eileen Wagner (thanks to Adobe and IxDD 2019 for the support!). If you&amp;rsquo;ve also been wondering what else &amp;ldquo;design for trust&amp;rdquo; can mean, join me on my journey through countless design blogs, stopping by business and CS academia, and ending up (as we often do) at human-centered design. Let&amp;rsquo;s go!&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/trust-pyramid@2x_hu_67d5ab7388b90a30.png&#34; alt=&#34;Trust Pyramid&#34; width=&#34;740&#34; height=&#34;279&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;One note before we dive in: I&amp;rsquo;m oversimplifying greatly by modeling trust as a two-party relationship, an interaction between the product being designed and the person using it. In reality, we interact simultaneously with multiple products, tools, and services. Do you trust an article in your Facebook news feed enough to click on it? That requires asking whether you trust the person posting it, whether you trust the source of the article, and whether you trust Facebook. Oh, also – do you trust your internet connection? Do you trust your government? In order to investigate trust, let&amp;rsquo;s pretend briefly that only one of these relationships is active at a time.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;be-professional&#34;&gt;Be professional&lt;/h3&gt;

      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/349079211?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;p&gt;You can&amp;rsquo;t nail a job interview unless you&amp;rsquo;ve brushed the dandruff off your shoulders and picked the spinach out of your teeth. That&amp;rsquo;s the message of 75% of the how-to articles I found about design and trust. You need to look like the kind of organization that has its act together. Only then will people fill out your form, pay you money, install your app.&lt;/p&gt;
&lt;p&gt;The most prevalent theme in these articles is consistency and attention to detail. They recommend using a style guide or a &lt;a href=&#34;https://uxplanet.org/inside-a-design-system-what-you-need-to-know-and-why-198ab645d5a3&#34;&gt;design system&lt;/a&gt;: consistent colors, consistent visual language, consistent naming, consistent corner radius on every last button. They tell you to make sure that users have an impression of care and quality, and yes, it&amp;rsquo;s incumbent on design, especially visual and UI design, to manage that first impression.&lt;/p&gt;
&lt;p&gt;They have a good point. A company that doesn&amp;rsquo;t use matching fonts in its marketing emails seems like a company that isn&amp;rsquo;t paying attention to other things. They might bill inaccurately. Their product might not be updated. It might crash. It might break other tools people have installed. This might not be fair, but it&amp;rsquo;s true: you need to keep your visual design looking consistent and updated, otherwise your product seems like a possible threat.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s not just visual design. Make sure your links aren&amp;rsquo;t broken (the digital version of food stuck in your teeth!). Don&amp;rsquo;t prominently feature reviews in your product descriptions when none of your products actually have any reviews. &amp;ldquo;From print ad, to in-store experience, to mobile, Target looks and feels like Target, which provides a strong sense of consistency and trust,&amp;rdquo; says &lt;a href=&#34;https://medium.com/nerdwallet-design/designing-for-trust-c7455896432b&#34;&gt;this article from NerdWallet&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;So yes, most of what the internet calls &amp;ldquo;design for trust&amp;rdquo; is basically charm school for tech products. They don&amp;rsquo;t mention being worthy of the trust you&amp;rsquo;re trying to earn. Not only is this a shady way to operate, but it shows a superficial understanding of how trust works, as we&amp;rsquo;re about to see.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Tools you&amp;rsquo;ll need: consistent branding; design systems; voice and tone guide. Get started with the advice and articles in &lt;a href=&#34;https://www.designsystems.com/&#34;&gt;Figma&amp;rsquo;s Design Systems magazine&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;meet-real-needs&#34;&gt;Meet real needs&lt;/h3&gt;

      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/349080146?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;p&gt;Earning trust isn&amp;rsquo;t a one-time event. It&amp;rsquo;s intuitively obvious: anything we call &amp;ldquo;trust&amp;rdquo; comes from accumulated interactions, not just a first impression. Let&amp;rsquo;s dive in to the literature: what else goes into trust, besides that initial gut-check?&lt;/p&gt;
&lt;p&gt;For a long time, researchers had studied trust by looking at the phenomena that surround it – like knowing that the sun is out by seeing light and shadow through the window curtains, they measured trust with experiments around interpersonal risk-taking. &lt;a href=&#34;https://people.wku.edu/richard.miller/Mayer%20Trust%20article.pdf&#34;&gt;Mayer et al., in their 1995 paper &amp;ldquo;An Integrative Model of Organizational Trust,&amp;rdquo;&lt;/a&gt; wanted to describe how trust actually works between two people. They also didn&amp;rsquo;t like the fact that a lot of models of trust ignored that trustworthiness is personal and situational. Yes, some people are overall more trustworthy than others, but that&amp;rsquo;s a result of many individual interactions that build or destroy trust. Trust is dynamic and reinforces itself; it&amp;rsquo;s not a setting you can turn on and forget about.&lt;/p&gt;
&lt;p&gt;Though trust is contextual and relational, agreeing on some broad features of trust helps us understand it. Mayer proposes a model of trustworthiness that hinges on three factors in any interaction:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Ability&lt;/strong&gt; – is the other party capable of doing what they say they&amp;rsquo;ll do?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Integrity&lt;/strong&gt; – is the other party going to do what they say they&amp;rsquo;ll do?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Benevolence&lt;/strong&gt; – do they have your interests in mind?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Consistent, professional design is a reasonably good indicator for the first factor, &lt;strong&gt;ability&lt;/strong&gt;. A modern-looking website that doesn&amp;rsquo;t crash feels like a reflection of a capable organization.&lt;/p&gt;
&lt;p&gt;The most straightforward way to incorporate the second factor, &lt;strong&gt;integrity&lt;/strong&gt;, in a design is to illustrate results. That might mean showcasing and encouraging user reviews, showing the results or products in action, or offering a freebie or guarantee as collateral. (No, &lt;a href=&#34;https://thenextweb.com/dd/2016/08/26/creating-trust-with-ux-design/&#34;&gt;a promise from you&lt;/a&gt;, no matter how sincere, doesn&amp;rsquo;t really help here. Spare me your pictures of locks and shields. Show, don&amp;rsquo;t tell.)&lt;/p&gt;
&lt;p&gt;The third factor, &lt;strong&gt;benevolence&lt;/strong&gt;, seems simple but is actually the most complex to design for. Figuring out what people really want and need is a field unto itself; design researchers are trained in using ethnographic techniques to figure out what people&amp;rsquo;s needs actually are, and what features and products would actually address them. It&amp;rsquo;s not enough to offer a product or service at a low price. People value less tangible qualities like convenience, flexibility, emotional connection, and security. This explains why somebody might well pay for Amazon Prime even if they have figured out that the cost of the Prime membership is more than they usually pay per year in normal shipping: they value a short turnaround between &amp;ldquo;place order&amp;rdquo; and a package on their doorstep.&lt;/p&gt;
&lt;p&gt;So here, &amp;ldquo;designing for trust&amp;rdquo; means offering what people actually need and value. It might be something that doesn&amp;rsquo;t seem related to, or even conflicts with, your business model. I like, but don&amp;rsquo;t particularly trust, &lt;a href=&#34;https://www.mcfit.com/de/&#34;&gt;my gym&lt;/a&gt;, because they make it very difficult to cancel my membership. And I would trust the workplace messaging platform Slack a lot more if I were able to &lt;a href=&#34;https://qz.com/1641708/slack-doesnt-care-that-you-cant-block-a-workplace-harasser/&#34;&gt;report harassment&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Academics who study website credibility have &lt;a href=&#34;http://mmi.tudelft.nl/~joostb/files/detweiler_broekens_09.pdf&#34;&gt;taken this model up as well&lt;/a&gt;, and practitioners have found that it applies in real-world use cases. A study of a mockup of California health exchange websites found that the version that featured price prominently was rated by users as the most trustworthy. If price was buried, users felt the website was trying to bury the most important piece of information. Put another way, it seemed like the website didn&amp;rsquo;t have their interests in mind.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Tools you&amp;rsquo;ll need: design ethnography, user research, personas, open-ended observations and interviews. Get started with the methods in &lt;a href=&#34;https://www.designkit.org/&#34;&gt;IDEO&amp;rsquo;s Design Kit&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;offer-control&#34;&gt;Offer control&lt;/h3&gt;

      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/349076200?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;p&gt;Even the best design research won&amp;rsquo;t uncover people&amp;rsquo;s every need. People know themselves and their situations better than you, the designer, will ever know them. So how can you communicate this in your designs?&lt;/p&gt;
&lt;p&gt;The final key to designing for trust is to think about where you can give people control. Flexibility in their settings. Choices about their workflow. Options around their personal data. The last thing you want is for them to feel like part of a funnel, or to realize that you&amp;rsquo;re using so-called &amp;ldquo;&lt;a href=&#34;https://www.darkpatterns.org/&#34;&gt;dark patterns&lt;/a&gt;&amp;rdquo; (I prefer the term &amp;ldquo;&lt;a href=&#34;https://twitter.com/mollyclare/status/1174630208860819456?s=20&#34;&gt;manipulative patterns&lt;/a&gt;&amp;rdquo;) to tug them through a product. What&amp;rsquo;s the opposite of a manipulative pattern? The last parts of Nathan Kinch&amp;rsquo;s &lt;a href=&#34;https://medium.com/greater-than-experience-design/data-trust-by-design-principles-patterns-and-practices-part-2-up-front-terms-and-conditions-337c6b37552d&#34;&gt;long but well-thought-out essay on data trust&lt;/a&gt; shows some interface patterns that give people choice, control, and agency.&lt;/p&gt;
&lt;p&gt;Of course, you&amp;rsquo;re already imagining the alternative: too many choices, confusion, overcomplexity. This is a very real problem: [Eileen Wagner and I gave a presentation recently](link to noscript) about our redesign of a complex content-blocking browser extension, a situation where we deeply cared about user control, but needed to reduce options; we learned from our research that even die-hard experts were scratching their heads. The answer, though, wasn&amp;rsquo;t to remove options. Instead, we burned through piles of post-its trying to figure out how to preserve choice and complexity without sacrificing usability. It is possible (&lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;here&amp;rsquo;s our case study&lt;/a&gt;), and we designers need to be up for the challenge.&lt;/p&gt;
&lt;p&gt;A journey map is a common tool that designers use to help visualize how people experience a product or platform. Most journey maps are linear and emphasize the &amp;ldquo;happy path&amp;rdquo;. Designing for control means thinking through some less ideal, less typical journeys and giving these side roads some love. You might ask:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Do people really need to provide all the information you ask for? Are you clear about what they do and don&amp;rsquo;t need to provide, and why that is?&lt;/li&gt;
&lt;li&gt;Do people need to do every one of your ideal steps?&lt;/li&gt;
&lt;li&gt;Can any of your content be skipped or repeated?&lt;/li&gt;
&lt;li&gt;Where do you ask for blanket, product-wide permissions? Is it possible and easy for people drill down into those permissions and give more granular answers?&lt;/li&gt;
&lt;li&gt;Does part of your product look like machine-learning or algorithmic &amp;ldquo;magic&amp;rdquo;? If so, can you give people a peek into how it works? Even better, can you let them tweak the way the &amp;ldquo;magic&amp;rdquo; works?&lt;/li&gt;
&lt;li&gt;Can you imagine anybody being put at risk by using your tool? Can you give them an option that eliminates that risk?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Tools you&amp;rsquo;ll need: journey maps, flowcharts, threat modeling. Get started with the methods in &lt;a href=&#34;http://dft.sri.com/method/&#34;&gt;SRI&amp;rsquo;s Design for Trust toolkit&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;hr/&gt;
&lt;p&gt;By the time you&amp;rsquo;re thinking about how to meet people&amp;rsquo;s needs, and how to offer people control and agency, you&amp;rsquo;ve come far beyond what Joe Gebbia had in mind in his TED talk. Not only are you designing something people will trust, you&amp;rsquo;re designing something worthy of their trust.&lt;/p&gt;
&lt;p&gt;So stop thinking of trust as a party you&amp;rsquo;re trying to crash. Don&amp;rsquo;t settle for &amp;ldquo;trustwashing&amp;rdquo; your designs with smooth branding and empty promises. And start &lt;em&gt;really&lt;/em&gt; designing for trust.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;a href=&#34;https://medium.com/simply-secure/i-read-about-design-for-trust-so-you-dont-have-to-1337d4efa6bc&#34;&gt;Cross-posted to Medium.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>My Data, Your Data, Our Data</title>
      <link>https://superbloom.design/learning/blog/mydata/</link>
      <pubDate>Thu, 03 Oct 2019 10:08:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/mydata/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/vegas-cookie-banner_hu_674c0ae1fa8499e.png&#34; alt=&#34;Cookie banner&#34; width=&#34;740&#34; height=&#34;193&#34;&gt;
&lt;/p&gt;
&lt;p&gt;When was the last time you actually read one of these alerts? Have you ever clicked through to read the full policy? Have you tried to make changes, or say &amp;ldquo;no&amp;rdquo; to the trackers? I know I sometimes don&amp;rsquo;t – too often, I find myself just looking for the &amp;ldquo;Accept&amp;rdquo; button.&lt;/p&gt;
&lt;p&gt;If you are in Europe, you probably see an alert like this &lt;em&gt;every time&lt;/em&gt; you load a new webpage or install a new app. These are the result of increased regulation in Europe around privacy (&lt;a href=&#34;https://gdpr.eu/&#34;&gt;read more about the General Data Protection Regulation, or GDPR&lt;/a&gt;). This legislation requires that companies get your explicit consent before they use your personal data. &amp;ldquo;Personal data&amp;rdquo; isn&amp;rsquo;t just your demographic, health or banking data — it&amp;rsquo;s also the behavioral tracks you leave behind every time you use digital devices, like your browsing behavior, the type of device you&amp;rsquo;re using, the language you view content in, where you&amp;rsquo;re connected from, and more.&lt;/p&gt;
&lt;p&gt;Getting our consent every time companies use this data sounds like a great idea. So what&amp;rsquo;s the catch?&lt;/p&gt;
&lt;p&gt;Unfortunately, the way that companies are actually implementing this consent process is often less about making sure you understand what&amp;rsquo;s going on, and more about satisfying the law&amp;rsquo;s bare minimum requirements. &lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/consent/what-is-valid-consent/&#34;&gt;Much of the &amp;ldquo;consent&amp;rdquo; that you&amp;rsquo;re likely to give online doesn&amp;rsquo;t even meet the GDPR&amp;rsquo;s standards&lt;/a&gt;. Overwhelming you with legalese, or manipulating you with misleading design, is a strategy to get you to click &amp;ldquo;accept&amp;rdquo; – &lt;a href=&#34;https://uxdesign.cc/dark-patterns-in-ux-design-7009a83b233c&#34;&gt;designers often call this a &amp;ldquo;dark pattern.&amp;rdquo;&lt;/a&gt; But this tactic is actually &lt;strong&gt;illegal&lt;/strong&gt; in the EU – the GDPR requires that consent be &amp;ldquo;informed&amp;rdquo; and &amp;ldquo;explicit.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/ok-ok-ok-ok_hu_ce53738e9b953e86.png&#34; alt=&#34;Man bombarded with OK buttons&#34; width=&#34;740&#34; height=&#34;479&#34;&gt;
&lt;/p&gt;
&lt;p&gt;There&amp;rsquo;s a deeper issue too, though: even if every company did design a perfectly informed, explicit consent process, we&amp;rsquo;re still relying on every individual to make decisions where they can&amp;rsquo;t know the future and don&amp;rsquo;t have all the information. Does my clicking &amp;ldquo;accept&amp;rdquo; in the moment mean that I am okay with my data being used forever? What if my identity is stolen in the future? What if I&amp;rsquo;m a target of harassment? What recourse do I have, if I already said &amp;ldquo;yes&amp;rdquo; to sharing my data? &lt;a href=&#34;https://www.newyorker.com/tech/annals-of-technology/the-gdpr-europes-new-privacy-law-and-the-future-of-the-global-data-economy&#34;&gt;As Julia Powles writes in the New Yorker&lt;/a&gt;: &amp;ldquo;the actions of any one person are unlikely to effect change, and so it is comparatively easy for us, as a collective, to yield certain concessions out of convenience, ignorance, or resignation.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;So what if, instead of asking how we can improve these alerts, we stepped back and asked questions like:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How might we consent to sharing our private data in a meaningful and engaged way?&lt;/li&gt;
&lt;li&gt;How might we build technology and systems where less private data is needed to begin with?&lt;/li&gt;
&lt;li&gt;How might we design a better digital world where technology protects us while helping us achieve our goals?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These questions have been on my mind a lot lately. They were a major topic of the discussions I had recently as a guest on the &lt;a href=&#34;https://podcasts.apple.com/us/podcast/privacy-trust-and-good-design/id1437677219?i=1000450089010&#34;&gt;Wireframe podcast (by Adobe/Gimlet)&lt;/a&gt;, and also in my talk at the &lt;a href=&#34;https://mydata2019.org/presenter/georgia-bullen/&#34;&gt;MyData conference&lt;/a&gt; in Helsinki. As practitioners in field known for innovation, we aren&amp;rsquo;t approaching this problem like a design challenge. And as people using these technologies, we need to stand up and demand better. Given the daily deluge of data breach notices, all of us — companies, end users, governments — should have similar interests here. Our data is becoming more and more valuable, so the risk of breaches is getting higher and higher. Why not rethink and redesign the whole system with privacy, not just consent, in mind?&lt;/p&gt;
&lt;p&gt;One way that we&amp;rsquo;ve approached this at Simply Secure is by &lt;a href=&#34;https://superbloom.design/learning/blog/sensitive-interviews&#34;&gt;incorporating techniques like threat modeling which we&amp;rsquo;ve learned from the information security communities into our design practice&lt;/a&gt; — making privacy, security and safety central to design. By thinking through risks and threats, and when possible working with and co-designing with people from at-risk or vulnerable communities, we can work together to design for not just normal-use best cases but also stressful, higher-risk scenarios. By bringing more diverse perspectives to the design process and incorporating real world experience and user feedback, we have the opportunity to design responsible interfaces that take into account not just user needs but user safety and privacy.&lt;/p&gt;
&lt;p&gt;Redesigning the tools, systems, and norms we&amp;rsquo;ve grown accustomed to is an uphill battle, but there truly is hope and potential for better more responsible technology.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Designing for Power Users: A Case Study on NoScript</title>
      <link>https://superbloom.design/learning/blog/noscript-case-study/</link>
      <pubDate>Mon, 16 Sep 2019 14:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/noscript-case-study/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://superbloom.design/resources/case_studies/NoScript_CaseStudy_2019.pdf&#34;&gt;PDF version&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://media.ccc.de/v/Camp2019-10368-beyond_the_pile_of_knobs&#34;&gt;Talk at #cccamp19&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;about-this-project&#34;&gt;About this project&lt;/h3&gt;
&lt;p&gt;&lt;a href=&#34;https://noscript.net/&#34;&gt;NoScript&lt;/a&gt; is a browser extension for Firefox and Chrome/Chromium that blocks executable web content based on JavaScript, Java, Flash, Silverlight and other plugins, unless the site host is considered trusted by its user and has been previously added to a whitelist. It is considered a trusted open source tool, and regarded as an integral part of a larger suite of browser extensions for additional security. Along with HTTPS Everywhere, NoScript is embedded in Tor Browser by default.&lt;/p&gt;
&lt;p&gt;NoScript has 1.5 million users on Firefox and around 50k users on Chrome, in addition to all Tor Browser users (currently around 2.5 million). It is used by activists, governments and corporations alike, and was the first (and is, as of August 2019, the &lt;em&gt;only&lt;/em&gt;) browser extension to offer client-side protection against cross-site scripting attacks.&lt;/p&gt;
&lt;p&gt;NoScript 10 &amp;ldquo;Quantum&amp;rdquo;, a full rewrite of NoScript 5 &amp;ldquo;Classic&amp;rdquo; using the new WebExtensions API, was released at the end of 2018. This was necessary for NoScript to survive past Firefox 57, which deprecated and disabled all legacy add-ons. There was a significant backlash from the existing user base due to the unfamiliar UI.&lt;/p&gt;
&lt;h4 id=&#34;high-priority-usability-issues&#34;&gt;High-priority usability issues&lt;/h4&gt;
&lt;p&gt;Although many improvements have been made since the initial release of the new version, many usability issues still required attention. Specifically, we identified three problem areas at the start of the project:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Given the technical impossibility to reproduce verbatim the old UI, NoScript took the chance of a complete overhaul including long requested features (such as customizable presets) which couldn&amp;rsquo;t cleanly fit in the previous menu-based model. This, however, resulted in an excessive density of the layout, an excessive use of icons with no labels and therefore a generalized discoverability problem.&lt;/li&gt;
&lt;li&gt;The switch from XUL to HTML led to accessibility issues, especially regarding keyboard navigation. There is the additional option to display NoScript in &amp;ldquo;high-contrast mode&amp;rdquo;, but that led to an extremely complex interface.&lt;/li&gt;
&lt;li&gt;The documentation is outdated, still mostly referring to NoScript 5 &amp;ldquo;Classic&amp;rdquo;. Community-provided tutorials and guides are available, but have proven not to be easy to discover. An &amp;ldquo;official&amp;rdquo; up-to-date guide is sorely needed, but even better would be the tool to be more self-explanatory.&lt;/li&gt;
&lt;/ol&gt;
&lt;h4 id=&#34;familiar-patterns-in-open-source-design&#34;&gt;Familiar patterns in open-source design&lt;/h4&gt;
&lt;p&gt;In addition to the problem areas, we see familiar patterns that many open source security tools face. NoScript was first released in May 2005, and has been developed and maintained by one developer as a side project. It has an active community of enthusiastic users who rely on it for security both personally and professionally, and wouldn&amp;rsquo;t hesitate to contact the developer or the community for help and discussion. Changes to NoScript were mostly reactive: they were directly based on unstructured incoming user feedback or feature requests. Sometimes changes needed to be fast, as researchers file security issues that were just being discovered (and potentially exploited). &lt;em&gt;Incredibly, NoScript has always responded within 24 hours to these security fixes in the past 14 years.&lt;/em&gt; However, when it came to UX/UI issues, the fix was not always immediate. This feedback setup only resulted in NoScript reacting to superficial UI/UX problems, rather than offering a coherent and thought-through foundation.&lt;/p&gt;
&lt;p&gt;Unstructured incoming feedback meant that NoScript was always one step behind user needs.&lt;/p&gt;
&lt;p&gt;Another common issue we see is what has been referred to as the &lt;a href=&#34;https://opensource.com/article/17/4/itch-to-scratch-model-user-problems&#34;&gt;Itch-to-Scratch Model&lt;/a&gt;, a developer-centric mindset that prevents valuable open source tools from having wider adoption. The developer of NoScript will readily admit that he &lt;em&gt;built NoScript for himself, and will always make it work for him first&lt;/em&gt;. At the same time, he and other people working in the information security sector agree that &lt;strong&gt;everyone should use security tools like NoScript&lt;/strong&gt;. But how does one design a tool for all when the needs of the developer are the driving force behind the project?&lt;/p&gt;
&lt;p&gt;NoScript is caught between &lt;em&gt;designing for developers&lt;/em&gt; and &lt;em&gt;making it work for everyone&lt;/em&gt;—it is difficult to balance the needs of very different user groups.&lt;/p&gt;
&lt;p&gt;To address the problem areas as well as these underlying issues, Simply Secure was tasked to go back to the drawing board and develop a new and usable UI that fits NoScript users&amp;rsquo; needs.&lt;/p&gt;
&lt;h3 id=&#34;methodology&#34;&gt;Methodology&lt;/h3&gt;
&lt;p&gt;Our &lt;a href=&#34;https://simplysecure.org/what-we-do/usable-security-audit/&#34;&gt;framework&lt;/a&gt; for secure usability audits looks at security from a human-centered perspective. Our driving questions are: What do people want? What do people need? What can people use?&lt;/p&gt;
&lt;p&gt;Our research and synthesis focuses on user needs by conducting user interviews and usability tests to get get rich, qualitative feedback. In our prototyping and testing phase, our primary focus was that the tool made sense to people.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Untitled-7827f84f-a937-4e0c-9625-b73837718d50_hu_9c349a45a81af655.png&#34; width=&#34;740&#34; height=&#34;345&#34;&gt;
&lt;/p&gt;
&lt;p&gt;For this research, we conducted five qualitative interviews in early May 2019. The interviewees identified themselves as: novice users (2), experienced users (2), and security trainers (2). The interview guide is in our appendix.&lt;/p&gt;
&lt;h4 id=&#34;scope&#34;&gt;Scope&lt;/h4&gt;
&lt;p&gt;We have limited our redesign to the desktop browser extension as it appears on Firefox and Chrome/Chromium. The evaluation and redesign of the mobile interface for Firefox will follow the next release, and minor changes specific to mobile environments are possible.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A note about Tor Browser&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We did not, as originally planned, speak to Tor Browser users about their NoScript experience. As of May 2019, Tor Browser is planning to integrate NoScript settings into its general security settings interface (the s&lt;em&gt;lider&lt;/em&gt;), and thus we did not think that evaluating current pain points in the Tor Browser would be helpful. However, we did sketch out some UI designs for Tor use cases that are in line with the redesign. Thanks are due to the Tor Browser team for providing us with feedback they had collected from Tor Browser users, and for many great discussions on design issues and directions in the secure browser extensions space.&lt;/p&gt;
&lt;h3 id=&#34;findings&#34;&gt;Findings&lt;/h3&gt;
&lt;h3 id=&#34;1-things-that-work&#34;&gt;1. Things that work&lt;/h3&gt;
&lt;h4 id=&#34;noscript-functions-as-a-browser-extension-for-security&#34;&gt;NoScript functions as a browser extension for security&lt;/h4&gt;
&lt;p&gt;The users we spoke to understood that NoScript offers state-of-the-art script blocking, and is probably the most secure choice out there, even if not the most usable one. Users also understood how NoScript might interact with other browser extensions, and generally like &amp;ldquo;fiddling around with the knobs&amp;rdquo; to see how things interacted.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;NoScript is the last line of defence on my browser. I trust it to be working in my interest at all times.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;I think everyone needs something like that. But not everyone will understand this tool.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id=&#34;noscript-also-provides-information&#34;&gt;NoScript also provides information&lt;/h4&gt;
&lt;p&gt;For many users, seeing the scripts themselves is already a feature. If a site uses a lot of scripts, especially scripts that look like they are trackers, users lower their trust to a site.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;You can see how much cruft is implemented on the website–just seeing this with the slider pushed over gives me a good feeling—and I get a bad feeling if the slider is on the wrong side!&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id=&#34;people-know-how-to-use-noscript-effectively&#34;&gt;People know how to use NoScript effectively&lt;/h4&gt;
&lt;p&gt;Experienced users had an established workflow of visiting a site → evaluating breakage → temporarily allowing scripts from the parent site → reloading → scrutinising other scripts and toggling their controls for the site to display/function correctly. &lt;strong&gt;This is not a straightforward process&lt;/strong&gt;—yet experienced users are able to achieve their respective goals.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Untitled-45ebc90f-082a-4f34-9d23-b5ff20ade8e3_hu_d108405f23aadf3d.png&#34; width=&#34;740&#34; height=&#34;463&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Experienced users understood the NoScript workflow.&lt;/p&gt;
&lt;p&gt;Users often manage to achieve their goals, though the steps they take may not be the most efficient. Some people always change settings in the &lt;code&gt;per-site permissions&lt;/code&gt; tab, while others prefer the menu interface with its &lt;code&gt;allow all temporarily&lt;/code&gt; option.&lt;/p&gt;
&lt;p&gt;While novice users understood that NoScript blocks scripts on the website you visit, few of them were able to verbalise NoScript&amp;rsquo;s blocking behavior (that blocking one domain on one site means blocking this domain for all sites, unless settings are temporarily revoked). Relatedly, novice users could only guess that temporary changes are changes &lt;strong&gt;in this current browser session&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;To novice users, the key questions were:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Which domains are ok? How do I know whether something is a tracker?&lt;/li&gt;
&lt;li&gt;Does NoScript help me decide which scripts are OK? Are there defaults?&lt;/li&gt;
&lt;li&gt;Does NoScript learn from my behavior? From other users&amp;rsquo; behavior?&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2-things-that-dont-work&#34;&gt;2. Things that don&amp;rsquo;t work&lt;/h3&gt;
&lt;h4 id=&#34;system-states-and-icons-do-not-match&#34;&gt;System states and icons do not match&lt;/h4&gt;
&lt;p&gt;NoScript uses three main icons to indicate differences in states:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;❗️ means that restrictions are disabled (i.e. scripts are allowed),&lt;/li&gt;
&lt;li&gt;❌  means restrictions are enabled (i.e. scripts are blocked),&lt;/li&gt;
&lt;li&gt;🕒  means temporary, with the options &lt;code&gt;temporarily allow&lt;/code&gt; and &lt;code&gt;revoke temporary allowance&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These icons were confusing to all users we talked to, most likely because system state (&lt;code&gt;allow&lt;/code&gt; and &lt;code&gt;block&lt;/code&gt;) were mixed with recommendations (&lt;code&gt;secure&lt;/code&gt; and &lt;code&gt;danger&lt;/code&gt;). This is a phenomenon that happens throughout the interface, and the most obvious place for this was the use of &lt;em&gt;color&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;If one were to assign a color for UI elements related to blocking, what would it be? Green is commonly associated with &amp;ldquo;GOOD!&amp;rdquo;, &amp;ldquo;DO THAT!&amp;rdquo;, &amp;ldquo;GO!&amp;rdquo;, while red is associated with &amp;ldquo;BAD!&amp;rdquo;, &amp;ldquo;DON’T DO THAT!&amp;rdquo;, &amp;ldquo;STOP!&amp;rdquo;. But adding additional meaning to color complicates things.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Untitled-b338ea39-0782-4904-8dd3-c688a82a715b_hu_31022785873ee08b.png&#34; width=&#34;740&#34; height=&#34;814&#34;&gt;
&lt;/p&gt;
&lt;p&gt;When we encounter a good or harmless script, we should allow it. If it is a bad or harmful script, we should block it. However, when we attach the GOOD and BAD to security practices, the colors are flipped: a good or recommended security practice is to block things by default, and a bad or not recommended security practice is to allow scripts in general. Suddenly, a simple color can carry meaning on three levels: the action, the system state, or the recommendation.&lt;/p&gt;
&lt;p&gt;NoScript does not use red and green in combination (at least not with regard to &lt;code&gt;block&lt;/code&gt; and &lt;code&gt;allow&lt;/code&gt;), but the same problem stills exists in a more nuanced form. An icon with a crossed-out item is usually BAD, and a sign without anything is usually GOOD. But of course, here blocking something is actually GOOD, while blocking nothing is actually BAD. So whichever indicators NoScript chooses, they should &lt;strong&gt;either&lt;/strong&gt; aim to indicate system state [allow/block] &lt;strong&gt;or&lt;/strong&gt; recommendation [good/bad], but &lt;strong&gt;not both&lt;/strong&gt;. And in any case, NoScript should probably stay away from standard colors and icons.&lt;/p&gt;
&lt;h4 id=&#34;when-to-block-when-to-allow&#34;&gt;When to block, when to allow&lt;/h4&gt;
&lt;p&gt;In general, people tripped over allowing and blocking across the interface. For example, the &lt;code&gt;CUSTOM&lt;/code&gt; preset has checkboxes for &lt;strong&gt;allowing&lt;/strong&gt; certain scripts on sites; but users have unilaterally interpreted the checkboxes to be for &lt;strong&gt;blocking&lt;/strong&gt; scripts of different kinds. The word &amp;ldquo;allow&amp;rdquo; at the top left was not always seen. (Moreover, having the &lt;code&gt;script&lt;/code&gt; option as a checkbox in that tab was confusing—people rightly asked, &amp;ldquo;isn&amp;rsquo;t everything a script?&amp;rdquo;) Similarly, users stumbled over the phrase &amp;ldquo;disable restrictions&amp;rdquo; as a &lt;em&gt;double negative&lt;/em&gt; for pausing NoScript on a particular tab. We&amp;rsquo;ve seen multiple NoScript users guessing at the meaning of these buttons, only to then test the difference in settings themselves and try to infer the behavior of particular features.&lt;/p&gt;
&lt;p&gt;Another source of confusion comes from the usage of &amp;ldquo;trust&amp;rdquo;. Experienced users know that sites you trust should generally be set to &lt;code&gt;allowed&lt;/code&gt;, but sometimes it is necessary to allow scripts from sites you don&amp;rsquo;t trust for things to function correctly. Equating the two concepts (blocking and distrusting) was not helpful. Novice users sometimes expect NoScript to be making decisions about trust for them, due to the passive phrasing (&amp;ldquo;trusted&amp;rdquo; and &amp;ldquo;untrusted&amp;rdquo;).&lt;/p&gt;
&lt;p&gt;Finally, the green or red lock icon indicating HTTPS status was mistaken as an indicator for a NoScript-trusted site for novice users. Neither novice users nor experienced users knew what it meant.&lt;/p&gt;
&lt;h4 id=&#34;unclear-language-makes-actions-confusing&#34;&gt;Unclear language makes actions confusing&lt;/h4&gt;
&lt;p&gt;We found that some of the labels were unclear to both novice and experienced users. For example, none of the 6 people we talked to could describe what &lt;code&gt;Cascade top-level documents&lt;/code&gt; or &lt;code&gt;Match HTTPS content&lt;/code&gt; meant.&lt;/p&gt;
&lt;p&gt;After installing NoScript, people often open it while on a tab that is &amp;ldquo;privileged&amp;rdquo; (browser settings, for example the &lt;code&gt;add-ons&lt;/code&gt; page), which does not allow content blocking. The screen for this warning was a first hurdle for novice users, who didn&amp;rsquo;t understand the warning, nor where to go from here.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Screenshot_2019-04-23_at_12-b9808301-12ad-44f4-9442-1056bcd98b12.36.31_hu_e2c2546a244e2126.png&#34; width=&#34;740&#34; height=&#34;136&#34;&gt;
&lt;/p&gt;
&lt;p&gt;This is often the first screen that new NoScript users will see.&lt;/p&gt;
&lt;h4 id=&#34;strict-tone-and-voice-along-with-dated-ui-made-people-feel-insecure&#34;&gt;Strict tone and voice, along with dated UI, made people feel insecure&lt;/h4&gt;
&lt;p&gt;NoScript&amp;rsquo;s language on security is divisive. On the one hand, we repeatedly heard that running NoScript is making its users feel &lt;strong&gt;safer&lt;/strong&gt; online. On the other hand, some users reported that they feel guilty when turning it off; or worse, they believed they were completely unprotected and insecure when it&amp;rsquo;s off. This was most evident when novice users confronted the interface. They were baffled by the fact that not using NoScript was deemed &amp;ldquo;dangerous&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Untitled-54f9aaf2-fb56-4258-977e-371123ad8fef_hu_e15640c1efc5939b.png&#34; width=&#34;740&#34; height=&#34;230&#34;&gt;
&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;5 minutes ago I was browsing without it, putting &amp;lsquo;dangerous&amp;rsquo; here sounds life-threatening&amp;hellip;&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The visual design stood out to many novice users. Upon seeing the settings page, novice users commented that the design looks dated, and does not inspire trust.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;I cannot judge whether the tech is good or not, I have to rely on the design to tell me that.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Users repeatedly commented on the icon design (the in-browser NoScript badge). It is too small for many devices, and not always as informative as they had hoped.&lt;/p&gt;
&lt;p&gt;Most people found the logo cute, albeit old-fashioned. Some knew the reference to Ghostbusters. However, the logo is not consistent (store vs app vs settings), and that has thrown some people off.&lt;/p&gt;
&lt;h4 id=&#34;page-breakage-means-people-abandon-noscript-too-soon&#34;&gt;Page breakage means people abandon NoScript too soon&lt;/h4&gt;
&lt;p&gt;Even though experienced users understood the ideal workflow of NoScript, few people follow it consistently throughout their web browsing. Page breakage happens frequently even with fine-tuned NoScript settings: either the display of certain elements is removed or altered, or interactive elements don&amp;rsquo;t function correctly. Most people abandon the process of assessing page breakage and adjusting script blocking after one or two attempts, and either allow everything temporarily, or close the tab they wanted to view.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Untitled-7fa32754-fcf3-47b2-818c-3ef292e7918d_hu_e057fee146dad330.png&#34; width=&#34;740&#34; height=&#34;463&#34;&gt;
&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;If I haven&amp;rsquo;t found the right thing to turn off after the second try, I&amp;rsquo;ll just turn NoScript off.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Sadly, whenever pages work, the success is attributed to the website that uses javascript wisely; whenever pages break, the failure is attributed to NoScript for breaking the website. By design, NoScript is always associated with frustration.&lt;/p&gt;
&lt;h2 id=&#34;recommendations&#34;&gt;Recommendations&lt;/h2&gt;
&lt;p&gt;Based on our user research, we developed five main design recommendations for NoScript.&lt;/p&gt;
&lt;h3 id=&#34;1-focus-on-visualisation-and-customisability&#34;&gt;1. Focus on visualisation and customisability&lt;/h3&gt;
&lt;p&gt;NoScript users value the ability to &lt;strong&gt;see&lt;/strong&gt; which scripts are being used on a site, and to &lt;strong&gt;adjust&lt;/strong&gt; settings to only allow the scripts needed for a site to function correctly. Most active users only use the menu interface on the website they are visiting, improving that interface and the visualisation of script information will be most crucial.&lt;/p&gt;
&lt;p&gt;As such, NoScript is a tool that &lt;em&gt;creates friction&lt;/em&gt; rather than removing it, and this sort of friction is seen as valuable and necessary for people who care about security.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;I always pause before I [allow] a script—what is it, and can I trust it? NoScript makes me think about the websites I visit.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;Design for:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.notion.so/d8c2c90d8e25448fb9dd5b033cce8a1e&#34;&gt;Rose the Super User&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Potentially design for:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.notion.so/500c0eef3ff1415a82fc660188ba6e09&#34;&gt;Emil the Privacy Advocate&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Don&amp;rsquo;t design for:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.notion.so/e71cde80a0ab46dda9c61b223844ecec&#34;&gt;Chris the Curious&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;We recommend sticking with the core offering (surfacing information on scripts, and allowing for individual blocking) and making that more intuitive, rather than offering a script blocker that works silently and frictionlessly. &lt;strong&gt;NoScript is inherently interactive, and not for everyone.&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&#34;2-communicate-system-state-better&#34;&gt;2. Communicate system state better&lt;/h3&gt;
&lt;p&gt;Current system states can be opaque or ambiguous, and don&amp;rsquo;t always match the user&amp;rsquo;s mental model. NoScript is a complex tool, and the goal isn&amp;rsquo;t to simplify the options; however, a clear communication around system states and tool behavior that doesn&amp;rsquo;t leave the user guessing is vital for people to achieve their goals.&lt;/p&gt;
&lt;p&gt;We recommend using clear language and indicators for &lt;code&gt;blocking&lt;/code&gt; and &lt;code&gt;allowing&lt;/code&gt;, instead of trusting and untrusting. New and readable icons could help to indicate system states. We also recommend going through all labels and making sure functions are described in clear, simple and consistent language.&lt;/p&gt;
&lt;pre&gt;
Sample text explaining NoScript
===

When you visit a `site`, it can have a `script`, from a `script owner`.

The script could present a security risk, or a privacy infringement, or just make browsing unnecessarily slow and cluttered.

But you can decide on what gets loaded into your browser! You can block scripts.

Deciding on what to block, and how to block it, requires some knowledge about scripts and their owners.

Though there are some general rules of thumb, decisions always depend on the site, the type of script, and the owner of that script.

**NoScript is a tool that allows you to make these decisions easily.**

You can `block` or `allow` a script based on the `site` you&#39;re visiting, the `type of script`, and the `owner of that script`.

When you do any of the three things above, you can do it temporarily (on a tab), or permanently (across all visits).

Moreover, you can also save your specific `settings for the sites you visit`, so you don&#39;t have to fine-tune your blocking when you visit your most frequent sites.

NoScript blocks every script by default. When you change this behavior for an individual script, or for scripts on a specific site, the new rules get saved. You can view and edit these rules in the settings.
&lt;/pre&gt;
&lt;h3 id=&#34;3-supply-better-defaults-and-explain-why&#34;&gt;3. Supply better defaults and explain why&lt;/h3&gt;
&lt;p&gt;While we want to focus on making toggling choices and seeing site/script information easier, it&amp;rsquo;s vital to also consider the default settings for users who will not fine-tune NoScript to their needs. It is important to have on-screen helper texts (for example, hover-overs or information boxes) explaining features and defaults.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;It would be great if NoScript would take a stand and prescribe settings for people who just wanted to be safer and not mess with it every single minute.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;People also wanted to know why certain defaults were chosen. While the documentation is not the appropriate place to understand how and why things work, it is a good place to look up background information—experienced users said the documentation &amp;ldquo;made them feel safer&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;We recommend default settings that work out-of-the-box, and a walk-through of the main NoScript features in the onboarding process. Background information around browsing security as well as default choices should be provided in the documentation.&lt;/p&gt;
&lt;h3 id=&#34;4-update-the-visual-and-interface-design&#34;&gt;4. Update the visual and interface design&lt;/h3&gt;
&lt;p&gt;The choice of colours, typeface, layout and UI elements could use an upgrade—for a state-of-the-art tool, NoScript &lt;em&gt;looks&lt;/em&gt; like it was last updated a decade ago.&lt;/p&gt;
&lt;p&gt;This may seem like a cosmetic problem that doesn&amp;rsquo;t impact the way the tool works for users. However, users mentioned that an outdated interface:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Reduces their trust in the tool, and makes them wonder if it has bugs or malware&lt;/li&gt;
&lt;li&gt;Makes them worry that it will not be compatible with their browser&lt;/li&gt;
&lt;li&gt;Leaves them confused as to whether they have the latest version or need to update&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Beyond the general update, there are some specific changes we think could address some issues with the interface.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;I could shoot myself in the foot accidentally with one of these toggle settings and it wouldn&amp;rsquo;t warn me.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Enable/restrict temporarily&lt;/code&gt; should be a toggle with appropriate labels. Toggles should be used with care, making options clear and also throwing good alerts when needed.&lt;/li&gt;
&lt;li&gt;The presets under &lt;code&gt;Options/General&lt;/code&gt; should be communicated clearer, for example by renaming the tab to “Configure presets” and pushing it further back. (Make sure it&amp;rsquo;s understood as &lt;em&gt;redefining&lt;/em&gt; &lt;code&gt;block&lt;/code&gt; &lt;code&gt;allow&lt;/code&gt; etc.)&lt;/li&gt;
&lt;li&gt;When you change settings that affect the current site, the menu interface should reflect that.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We recommend a complete re-design of the UI, using a simple and clear style that does not distract from the existing complexity.&lt;/p&gt;
&lt;h3 id=&#34;5-add-a-per-site-settings-feature&#34;&gt;5. Add a &amp;ldquo;per-site settings&amp;rdquo; feature&lt;/h3&gt;
&lt;p&gt;As of now, changing the preferences around a script/domain means changing the preference for that script/domain for all tabs, for all sites visited. But that does not cover site-specific settings. For example, if a user wanted to allow scripts from &lt;code&gt;googleanalytics.com&lt;/code&gt; when visiting a trusted site, but does not want to allow them when visiting an untrusted site, this change has to be made manually each time. It would be convenient for the user to set these per-site preferences manually and have them saved as well.&lt;/p&gt;
&lt;p&gt;A related use case is when people want to allow &lt;code&gt;first-party&lt;/code&gt; scripts but not &lt;code&gt;third-party&lt;/code&gt; scripts, e.g. when visiting &lt;a href=&#34;http://facebook.com&#34;&gt;Facebook.com&lt;/a&gt; you want to allow scripts from Facebook.com; but when visiting your local news site you don&amp;rsquo;t want to allow scripts from Facebook.com. This could fall under saved per-site settings, or could be enabled with a shortcut, for example &lt;code&gt;first-party&lt;/code&gt; or &lt;code&gt;affiliated scripts&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;We recommend a new interface design for allowing per-site settings. This interface should communicate clearly which domains are allowed or blocked A) permanently and globally, B) permanently for this site, C) temporarily for this tab.&lt;/p&gt;
&lt;h3 id=&#34;design-decisions--testing&#34;&gt;Design decisions &amp;amp; testing&lt;/h3&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Untitled-6c8b5397-9011-4c9a-9e60-8215fad86308_hu_7d9872d18c6ade07.png&#34; width=&#34;740&#34; height=&#34;1480&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Untitled-32a2faa8-b619-449f-a176-3c4c0b87418a_hu_4495006734091443.png&#34; width=&#34;740&#34; height=&#34;1480&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Untitled-96c763ea-75dd-4f7b-8a5b-06b20d4508bf_hu_5ccc559e47f24a67.png&#34; width=&#34;740&#34; height=&#34;1480&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Untitled-d6437ba8-4cf1-4206-a7f2-a29b086bd516_hu_faf1d14315528e7a.png&#34; width=&#34;740&#34; height=&#34;1249&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Untitled-fef88c14-576d-42d3-ac8c-4714d146265d_hu_a9fd99957dd494be.png&#34; width=&#34;740&#34; height=&#34;1249&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/Untitled-258e9d9d-dd31-4c23-8ad5-892a2789f60b_hu_e9f52bdf6616337e.png&#34; width=&#34;740&#34; height=&#34;1249&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;accessibility&#34;&gt;Accessibility&lt;/h4&gt;
&lt;p&gt;In updating the UI style, we made sure that the contrast ratios of the colors are AAA-compliant. Moreover, we will add keyboard shortcuts to make NoScript more accessible for other input formats, as well as test our helper/hover text with screen readers.&lt;/p&gt;
&lt;h4 id=&#34;testing&#34;&gt;Testing&lt;/h4&gt;
&lt;p&gt;Our designs (wireframes and clickable prototypes) were tested with experienced NoScript users in July 2019. Iterations have focused on the interfaces surrounding per-site settings. As a next step, we plan to release an alpha version in the fall of 2019. The feedback from this release will further inform the design.&lt;/p&gt;
&lt;p&gt;If you would like to participate in alpha testing with us, please get in touch: ux [at] noscript.net&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Eileen Wagner&lt;/strong&gt;, Design Lead&lt;br&gt;
&lt;strong&gt;Lorraine Chuen&lt;/strong&gt;, Visual Design&lt;br&gt;
With help from &lt;strong&gt;Molly Wilson&lt;/strong&gt; and &lt;strong&gt;Georgia Bullen&lt;/strong&gt;&lt;br&gt;
Special thanks to &lt;strong&gt;Susan Farrell&lt;/strong&gt;, UX researcher and OTF Advisory Board member&lt;br&gt;
Infinite gratitude to &lt;strong&gt;Giorgio Maone&lt;/strong&gt;, developer and maintainer of NoScript&lt;br&gt;
CC BY-SA 4.0 Simply Secure, 2019&lt;br&gt;
Funded by Open Technology Fund&amp;rsquo;s Usability Lab&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>SOUPS 2019 Roundup</title>
      <link>https://superbloom.design/learning/blog/soups-2019/</link>
      <pubDate>Wed, 04 Sep 2019 10:08:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/soups-2019/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/soups2019_logo_380x403_hu_66ad75b03f56ffb.png&#34; alt=&#34;SOUPS 2019 Logo&#34; width=&#34;740&#34; height=&#34;785&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Contributors: &lt;a href=&#34;https://twitter.com/global_ashm&#34;&gt;Ashley Fowler&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/gusandrews&#34;&gt;Gus Andrews&lt;/a&gt;, &lt;a href=&#34;https://twitter.com/bernardtyers&#34;&gt;Bernard Tyers&lt;/a&gt;, and Georgia Bullen&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.usenix.org/conference/soups2019&#34;&gt;SOUPS 2019&lt;/a&gt;, the 15th Symposium on Usable Privacy and Security, was held in Santa Clara, CA, alongside &lt;a href=&#34;https://www.usenix.org/conference/usenixsecurity19&#34;&gt;USENIX Security&lt;/a&gt;, &lt;a href=&#34;https://www.usenix.org/conference/pepr19&#34;&gt;PePR&lt;/a&gt;, &lt;a href=&#34;https://www.usenix.org/conference/foci19&#34;&gt;FOCI&lt;/a&gt; and a few other conferences. For those not familiar with these events, they are the conferences hosted by &lt;a href=&#34;https://www.usenix.org/&#34;&gt;USENIX&lt;/a&gt;, the advanced computing systems association, focused on supporting the advanced computing systems communities and furthering the reach of innovative research. The sessions range from deep technical research to industry presentations to usability research and attitudinal surveys. A few members of the Simply Secure community were in attendance, so we wanted to pull together some quick takeaways, either for other folks in attendance or for people who weren&amp;rsquo;t able to come.&lt;/p&gt;
&lt;p&gt;All of the SOUPS 2019 &lt;a href=&#34;https://www.usenix.org/conference/soups2019/technical-sessions&#34;&gt;papers and presentations are available online&lt;/a&gt;, as well as the other USENIX events.&lt;/p&gt;
&lt;h3 id=&#34;workshop-designing-for-extremes-of-risk&#34;&gt;Workshop: &lt;a href=&#34;https://usable.tools/events/usable-at-soups/&#34;&gt;Designing for Extremes of Risk&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;The USABLE team at Internews (&lt;a href=&#34;https://usable.tools/&#34;&gt;https://usable.tools/&lt;/a&gt;) facilitated a half-day workshop at SOUPS. The workshop, entitled “Designing for Extremes of Risk,” was an interactive exploration of what it means to work with at-risk communities, particularly in the context of designing and developing privacy and security tools. The nearly 25 attendees represented a diverse range of professions, from academics to UX researchers to product teams and engineers.&lt;/p&gt;
&lt;p&gt;Main takeaways from the workshop included:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;From a product perspective, it can be difficult to identify at-risk communities, connect with them, and build the level of trust needed to collect accurate feedback. Using trusted intermediaries, such as digital security trainers, can provide tool teams with access to relevant feedback without jeopardizing the safety of at-risk communities.&lt;/li&gt;
&lt;li&gt;Tool teams can consider offering incentives (such as small stipends) for individuals to participate in user research. If offering incentives, be sure to research local implications for end users. For example, will accepting a stipend impact any government support that low-income participants may be receiving?&lt;/li&gt;
&lt;li&gt;International events and UX convenings are a good entry point for interested parties to meet at-risk users and begin to build trust. It is helpful for people outside the existing Internet Freedom (IF) community to understand what events exist, who attends each one, and what the purpose of these events are.&lt;/li&gt;
&lt;li&gt;Always be clear about what will be shared from meetings or gatherings (participant list, notes, attribution, etc.) and set clear ground rules from the beginning to foster a sense of trust among attendees.&lt;/li&gt;
&lt;li&gt;Co-design is most effective when it is implemented throughout the entire process. Utilize the co-design process not just for feature or tool development, but also developing the larger feedback collection process.&lt;/li&gt;
&lt;li&gt;User personas allow design and development teams to understand users without requiring direct access or communication.&lt;/li&gt;
&lt;li&gt;User engagements or any feedback collection activities should always take place in a trusted environment or location.&lt;/li&gt;
&lt;li&gt;When designing alerts, it is important to consider the cross-cultural interpretation of the language/design. Images and graphics can be used to send a more universal message or serve users who may be illiterate.&lt;/li&gt;
&lt;li&gt;There is no universal catalog for usability security bugs, analogous to the &lt;a href=&#34;https://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures&#34;&gt;Common Vulnerabilities and Exposures (CVE) catalog for security threats&lt;/a&gt;. Are there ways to identify and/or automate the testing of usability failures by referencing “chaos engineering” style approaches (see &lt;a href=&#34;https://en.wikipedia.org/wiki/Chaos_engineering#10-18_Monkey&#34;&gt;https://en.wikipedia.org/wiki/Chaos_engineering#10-18_Monkey&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;Reframe “edge cases” as “stress cases.” Account for how people operate under stress, as this is a more universally applicable approach. Though levels of stress can differ, all users face stress at some point.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;paper-why-people-dont-use-password-managers-effectively&#34;&gt;Paper: &lt;a href=&#34;https://www.usenix.org/conference/soups2019/presentation/pearman&#34;&gt;Why people (don’t) use password managers effectively&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Authors: Sarah Pearman, Shikun Aerin Zhang, Lujo Bauer, Nicolas Christin, and Lorrie Faith Cranor, Carnegie Mellon University&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Participants in the study used password managers built into web browsers or operating systems (12) and 3rd-party separately installed password managers (9).&lt;/li&gt;
&lt;li&gt;They “were reluctant to use password managers for [….] concerns over the single point of failure (i.e. the master password required to use password managers)” and they were “reluctant to give up control of their passwords” to the point where people don’t know their passwords.&lt;/li&gt;
&lt;li&gt;Participants did not feel that their passwords are at much risk and they don’t know where “save this password?” prompts are coming from.&lt;/li&gt;
&lt;li&gt;Some participants who used 3rd-party password managers were using old passwords for their master password, or kept copies of their master passwords in an email folder or on a notepad.&lt;/li&gt;
&lt;li&gt;The researchers recommended that password manager developers focus deeply on user experience design and usability testing.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.cylab.cmu.edu/news/2019/08/16-password-manager-soups-2019.html&#34;&gt;Another summary, on cmu.edu&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;paper-&#34;&gt;Paper: &lt;a href=&#34;https://www.usenix.org/conference/soups2019/presentation/wu&#34;&gt;&amp;ldquo;Something isn&amp;rsquo;t secure, but I&amp;rsquo;m not sure how that translates into a problem&amp;rdquo;: Promoting autonomy by designing for understanding in Signal&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Authors: Justin Wu, Cyrus Gattrell, Devon Howard, and Jake Tyler, Brigham Young University; Elham Vaziripour, Utah Valley University; Kent Seamons and Daniel Zappala, Brigham Young University&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The researchers mapped out all the flows in the application that trigger users to confirm the identity of other chat participants, known as the “authentication ceremony”.&lt;/li&gt;
&lt;li&gt;The participants in the study were paired up and given different scenarios that prompted the need to go through the authentication ceremony; different designs for this process were tested.&lt;/li&gt;
&lt;li&gt;Overall, participants didn’t really understand the process. They did not tend to get around to it organically.&lt;/li&gt;
&lt;li&gt;The alternative design developed by the researchers was more effective than the existing designs. Among the alterations they suggested were letting the user know they may want to exchange security numbers in person or through another channel; explaining what it means when the numbers don’t match; and getting rid of the “this number has been verified” toggle.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;paper-personal-information-leakage-by-abusing-the-gdpr&#34;&gt;Paper: &lt;a href=&#34;https://www.usenix.org/conference/soups2019/presentation/dimartino&#34;&gt;Personal Information Leakage by Abusing the GDPR &amp;lsquo;Right of Access&amp;rsquo;&lt;/a&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The researchers evaluated the GDPR identity verification process of 55 organizations in finance, entertainment, retail and others. They attempted to impersonate targeted individuals who have their data processed by these organizations, using only forged or publicly available information extracted from social media and other public data sources.&lt;/li&gt;
&lt;li&gt;For 15 out of the 55 organizations, the researchers were able to successfully impersonate a subject and obtained full access to their personal data.&lt;/li&gt;
&lt;li&gt;The leaked personal data contained a wide variety of sensitive information, including financial transactions, website visits, and physical location history.&lt;/li&gt;
&lt;li&gt;The researchers shared recommendations for consumer and organizational practices to limit leaking personal data, such as requiring login credentials, strictly verifying ownership of email address, and calling subjects to request specific user data.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;paper-cooperative-privacy-and-security-learning-from-people-with-visual-impairments-and-their-allies&#34;&gt;Paper: &lt;a href=&#34;https://www.usenix.org/conference/soups2019/presentation/hayes&#34;&gt;Cooperative Privacy and Security: Learning from People with Visual Impairments and Their Allies&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Authors: Jordan Hayes, Smirity Kaushik, Charlotte Emily Price, and Yang Wang, Syracuse University&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Researchers shadowed people with visual impairments and their allies (e.g. family members, friends and professional support) to understand how they protect their privacy and security.&lt;/li&gt;
&lt;li&gt;Existing tools are designed for individuals and focused on independence, often lacking accessibility support.&lt;/li&gt;
&lt;li&gt;Multifaceted disability identities need to be considered in design and research. Participatory action research and design can support inclusive design practices that address otherwise marginalized groups.&lt;/li&gt;
&lt;li&gt;Allies (friends, family, support staff) are important for privacy/security.&lt;/li&gt;
&lt;li&gt;We need to think about designs that allow for cooperative privacy &amp;amp; security, rather than just individual-centric use cases.&lt;/li&gt;
&lt;li&gt;For more, see the &lt;a href=&#34;http://www.inclusiveprivacy.org/index.html&#34;&gt;Privacy for All Project&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;paper-privacy-and-security-threat-models-and-mitigation-strategies-of-older-adults&#34;&gt;Paper: &lt;a href=&#34;https://www.usenix.org/conference/soups2019/presentation/frik&#34;&gt;Privacy and Security Threat Models and Mitigation Strategies of Older Adults&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Authors: Alisa Frik, International Computer Science Institute (ICSI) and University of California, Berkeley; Leysan Nurgalieva, University of Trento; Julia Bernd, International Computer Science Institute (ICSI); Joyce Lee, University of California, Berkeley; Florian Schaub, University of Michigan; Serge Egelman, International Computer Science Institute (ICSI) and University of California, Berkeley&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The researchers did semi-structured interviews with 46 participants from senior centers and senior residences in the San Francisco Bay Area, aged 65-95.&lt;/li&gt;
&lt;li&gt;The themes of the interviews were common security and privacy concerns, threat models, behaviors and strategies to mitigate perceived risks, usability issues with current protections, learning and troubleshooting approaches, and misconceptions regarding security and privacy.&lt;/li&gt;
&lt;li&gt;They found that older adults had similar attitudes and concerns to general population, but amplified risks, particularly due to complex trade-offs of privacy, safety, and autonomy. Older adults’ misconceptions about data flows lead to blind spots in mitigation strategies, and that the difficulty they experience in using technology decreases their self-efficacy around privacy &amp;amp; security.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;paper--1&#34;&gt;Paper: &lt;a href=&#34;https://www.usenix.org/conference/soups2019/presentation/simoiu&#34;&gt;&amp;ldquo;I was told to buy a software or lose my computer. I ignored it&amp;rdquo;: A study of ransomware&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Authors: Camelia Simoiu, Stanford University; Christopher Gates, Symantec; Joseph Bonneau, New York University; Sharad Goel, Stanford University&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The researchers ran a detailed survey of a representative sample of 1,180 American adults.&lt;/li&gt;
&lt;li&gt;Based on that, they estimated that 2-3% of respondents were affected by ransomware over a 1-year period (2016 - 2017).&lt;/li&gt;
&lt;li&gt;The average ransom amount demanded was $530, and only a small fraction of affected users (about 4% of those affected) reported paying.&lt;/li&gt;
&lt;li&gt;Cryptocurrencies were typically only one of several payment options, which suggests that they may not be a primary driver of ransomware attacks.&lt;/li&gt;
&lt;li&gt;The paper includes a proof-of-concept method for ransomware risk-assessment based on self-reported security habits.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;paper-from-usability-to-secure-computing-and-back-again&#34;&gt;Paper: &lt;a href=&#34;https://www.usenix.org/conference/soups2019/presentation/qin&#34;&gt;From Usability to Secure Computing and Back Again&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Authors: Lucy Qin, Andrei Lapets, Frederick Jansen, Peter Flockhart, Kinan Dak Albab, and Ira Globus-Harris, Boston University; Shannon Roberts, University of Massachusetts Amherst; Mayank Varia, Boston University&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Researchers worked with the &lt;a href=&#34;https://thebwwc.org/&#34;&gt;Boston Women’s Workforce Council&lt;/a&gt; on technical strategies for an open data effort around gender wage equity in Boston.&lt;/li&gt;
&lt;li&gt;They used multi-party computation (MPC) techniques to blind and anonymize sensitive (wage) data, allowing companies to share data securely and privately, but the public effort to collect city-wide data for a large study.&lt;/li&gt;
&lt;li&gt;Their platform for data collection focused on the usability of privacy-enhancing technologies (MPC).&lt;/li&gt;
&lt;li&gt;They focused not only on the security and privacy of the data, but also on developing analytics tools in privacy-enhanced ways.&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Persona Template for Security Tools</title>
      <link>https://superbloom.design/learning/resources/persona-security/</link>
      <pubDate>Thu, 22 Aug 2019 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/persona-security/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Trust &amp; Responsibility &#39;Tea Time&#39;: New video series with World Interaction Design Day exploring design and trust</title>
      <link>https://superbloom.design/learning/blog/trust-responsibility-tea-time/</link>
      <pubDate>Wed, 21 Aug 2019 14:08:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/trust-responsibility-tea-time/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/tt-trustresponsibilityheader_hu_6911cdd8587b48cb.png&#34; alt=&#34;Trust &amp;amp; Responsibility Tea Time Header&#34; width=&#34;740&#34; height=&#34;389&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;How do we design for trust? What is our responsibility as designers?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;These questions have been popping up in the global design conversation lately, and not a moment too soon. This year, &lt;a href=&#34;http://adobe.ly/xd&#34;&gt;Adobe&lt;/a&gt; and &lt;a href=&#34;https://ixda.org/&#34;&gt;IxDA&lt;/a&gt; have named &lt;strong&gt;Trust and Responsibility&lt;/strong&gt; as the theme for &lt;a href=&#34;https://interactiondesignday.org/&#34;&gt;World Interaction Design Day&lt;/a&gt; (IxDD) 2019.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://interactiondesignday.org/&#34;&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/banner-ixdd_hu_9820bcec290d7374.png&#34; alt=&#34;World Interaction Design Day Banner&#34; width=&#34;740&#34; height=&#34;91&#34;&gt;
&lt;/a&gt;
We at Simply Secure couldn&amp;rsquo;t be more delighted: our mission is to practice and support responsible design, and &lt;a href=&#34;https://interactiondesignday.org/&#34;&gt;IxDD&lt;/a&gt; is an opportunity for designers around the world to organize events and start discussions around how we, the design community, need to frame our mission, our philosophy, and our craft. Not only do we grapple with these questions in our daily work, we&amp;rsquo;re also confronted with them on a larger scale whenever we read or listen to the news.&lt;/p&gt;
&lt;p&gt;So, as we approach &lt;a href=&#34;https://interactiondesignday.org/&#34;&gt;IxDD&lt;/a&gt; this September, we wanted to share how we at Simply Secure grapple with some of the most complex topics designers face. In this series of video shorts, we&amp;rsquo;re inviting you into our living room for a cup of our favorite beverage. We&amp;rsquo;ll be sharing more of our research and resources over the course of the summer. But for now, please accept our invitation to set your work down for a moment and put the kettle on – it&amp;rsquo;s tea time.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.youtube.com/watch?v=UMj8lGxmJoM&amp;amp;t=6s&#34;&gt;Trust &amp;amp; Consistency&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.youtube.com/watch?v=Htp3bqhavjY&amp;amp;t=10s&#34;&gt;Trust &amp;amp; Transparency&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.youtube.com/watch?v=9ovQKObSrag&#34;&gt;Trust &amp;amp; User Needs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.youtube.com/watch?v=Omk92KgQtgU&#34;&gt;Responsibility &amp;amp; Ethics&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.youtube.com/watch?v=Omk92KgQtgU&#34;&gt;Responsibility &amp;amp; Externalities&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/learning/collections/tea-time/&#34; class=&#34;button button--secondary read-more&#34; style=&#34;text-decoration: none;&#34;&gt;All Videos: Tea Time — Trust &amp;amp; Responsibility&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Interested in engaging in the conversation? Propose an event for &lt;a href=&#34;https://interactiondesignday.org/&#34;&gt;World Interaction Design Day&lt;/a&gt;, join the conversation online (#IxDD), reach out, or join us in our [community slack](mailto:slack@superbloom.design?subject=I’d like to join the Simply Secure Slack).&lt;/p&gt;
&lt;p&gt;| 

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/logo-adobe_hu_270c600c6a8fdd33.png&#34; alt=&#34;Adobe logo&#34; width=&#34;740&#34; height=&#34;1019&#34;&gt;
 |


    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/logo-IXDA_hu_f727576b1b2608a2.png&#34; alt=&#34;Interaction Day Logo&#34; width=&#34;740&#34; height=&#34;294&#34;&gt;
 |


    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/simplysecure-logo_hu_6c1f69db775471cd.png&#34; alt=&#34;Simply Secure logo&#34; width=&#34;740&#34; height=&#34;118&#34;&gt;
 |&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Responsibility &amp; Ethics</title>
      <link>https://superbloom.design/learning/resources/tea-time-responsibility-ethics/</link>
      <pubDate>Wed, 21 Aug 2019 12:04:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/tea-time-responsibility-ethics/</guid>
      <description>
      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/349077436?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;br&gt;
&lt;p&gt;Continue the conversation on trust and responsibility. Host or attend an event on 24 September 2019 for &lt;a href=&#34;https://interactiondesignday.org&#34;&gt;World Interaction Design Day&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/banner-ixdd_hu_9820bcec290d7374.png&#34; alt=&#34;World Interaction Design Day Banner&#34; width=&#34;740&#34; height=&#34;91&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Presented by:&lt;/p&gt;
&lt;p&gt;| 
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/logo-adobe.jpg&#34; alt=&#34;Missing alt text&#34;&gt;
 | 

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/logo-IXDA_hu_f727576b1b2608a2.png&#34; width=&#34;740&#34; height=&#34;294&#34;&gt;
 | 

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/simplysecure-logo_hu_6c1f69db775471cd.png&#34; width=&#34;740&#34; height=&#34;118&#34;&gt;
 |&lt;/p&gt;
&lt;h3 id=&#34;resources&#34;&gt;Resources&lt;/h3&gt;
&lt;h4 id=&#34;principles-and-background&#34;&gt;Principles and Background&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Books&lt;/em&gt;&lt;br&gt;
&lt;a href=&#34;https://www.future-ethics.com/&#34;&gt;Future Ethics, Cennydd Bowles&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://thamesandhudson.com/design-for-the-real-world-human-ecology-and-social-change-9780500273586&#34;&gt;Design for the Real World, Viktor Papanek&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Automating-Inequality-High-Tech-Profile-Police/dp/1250215781/&#34;&gt;Automating Inequality: How High-Tech Tools Profile, Police, and Punish the Poor, Virginia Eubanks&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/gp/product/0262038889/ref=ox_sc_act_title_3?smid=ATVPDKIKX0DER&amp;amp;psc=1&#34;&gt;Mismatch: How Inclusion Shapes Design, Kat Holmes&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Invisible-Women-Data-World-Designed/dp/1419729071/&#34;&gt;Invisible Women: Data Bias in a World Designed for Men, Caroline Criado Perez&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Technically-Wrong-Sexist-Algorithms-Threats/dp/0393356043&#34;&gt;Technically Wrong: Sexist Apps, Biased Algorithms, and Other Threats of Toxic Tech, Sara Wachter-Boettcher&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://ruinedby.design&#34;&gt;Ruined by Design, Mike Monteiro&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Articles&lt;/em&gt;&lt;br&gt;
&lt;a href=&#34;https://ourdataourselves.tacticaltech.org/posts/30-on-weaponised-design/&#34;&gt;On Weaponized Design, Cade Diehm&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.ethicsfordesigners.com/articles&#34;&gt;Ethics for Designers, Jet Gispen&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;tools-and-templates&#34;&gt;Tools and Templates&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;http://www.servicedesigntools.org/tools/14&#34;&gt;Tomorrow Headlines Exercise&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;http://tarotcardsoftech.artefactgroup.com/&#34;&gt;Tarot Cards of Tech&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.transfeministech.codingrights.org/&#34;&gt;Transfeminist Design Oracle&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://humanebydesign.com/&#34;&gt;Humane by Design&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://github.com/leeange/DSPPUX-Checklist&#34;&gt;Digital Security and Privacy Design UX Checklist&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.designforsustainability.studio/signals/the-copenhagen-catalog&#34;&gt;The Copenhagen Catalog&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;with&lt;/strong&gt; Eileen Wagner, Molly Wilson&lt;br&gt;
&lt;strong&gt;Produced by&lt;/strong&gt; Ben Mergelsberg, Eileen Wagner, Molly Wilson, Georgia Bullen&lt;br&gt;
&lt;strong&gt;Directed by&lt;/strong&gt; Ben Mergelsberg&lt;br&gt;
&lt;strong&gt;Art Direction by&lt;/strong&gt; Ana Sol Alvarez&lt;br&gt;
&lt;strong&gt;Camera assistents:&lt;/strong&gt; Sarnt Utamachote, Nicolas Simkin&lt;br&gt;
&lt;strong&gt;Art:&lt;/strong&gt; Molly Wilson&lt;br&gt;
&lt;strong&gt;Filmed at&lt;/strong&gt; &lt;a href=&#34;https://www.stattlab.net&#34;&gt;Stattlab&lt;/a&gt; and &lt;a href=&#34;http://wrangelfilm.com&#34;&gt;Wrangelfilm&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Supported by&lt;/strong&gt; &lt;a href=&#34;https://www.adobe.com&#34;&gt;Adobe&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Special thanks to&lt;/strong&gt; Clarote&lt;br&gt;
&lt;strong&gt;Simply Secure CC-BY&lt;/strong&gt; (Georgia Bullen, Ame Elliott, Eileen Wagner, Molly Wilson)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Responsibility &amp; Externalities</title>
      <link>https://superbloom.design/learning/resources/tea-time-responsibility-externalities/</link>
      <pubDate>Wed, 21 Aug 2019 12:04:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/tea-time-responsibility-externalities/</guid>
      <description>&lt;iframe src=&#34;https://player.vimeo.com/video/349078448&#34; width=&#34;640&#34; height=&#34;338&#34; frameborder=&#34;0&#34; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;
&lt;br&gt;
&lt;p&gt;Continue the conversation on trust and responsibility. Host or attend an event on 24 September 2019 for &lt;a href=&#34;https://interactiondesignday.org&#34;&gt;World Interaction Design Day&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/banner-ixdd_hu_9820bcec290d7374.png&#34; alt=&#34;World Interaction Design Day Banner&#34; width=&#34;740&#34; height=&#34;91&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Presented by:&lt;/p&gt;
&lt;p&gt;| 
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/logo-adobe.jpg&#34; alt=&#34;Missing alt text&#34;&gt;
 | 

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/logo-IXDA_hu_f727576b1b2608a2.png&#34; width=&#34;740&#34; height=&#34;294&#34;&gt;
 | 

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/simplysecure-logo_hu_6c1f69db775471cd.png&#34; width=&#34;740&#34; height=&#34;118&#34;&gt;
 |&lt;/p&gt;
&lt;h3 id=&#34;resources&#34;&gt;Resources&lt;/h3&gt;
&lt;h4 id=&#34;principles-and-background&#34;&gt;Principles and Background&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Books&lt;/em&gt;&lt;br&gt;
&lt;a href=&#34;https://www.future-ethics.com/&#34;&gt;Future Ethics, Cennydd Bowles&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://thamesandhudson.com/design-for-the-real-world-human-ecology-and-social-change-9780500273586&#34;&gt;Design for the Real World, Viktor Papanek&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Automating-Inequality-High-Tech-Profile-Police/dp/1250215781/&#34;&gt;Automating Inequality: How High-Tech Tools Profile, Police, and Punish the Poor, Virginia Eubanks&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/gp/product/0262038889/ref=ox_sc_act_title_3?smid=ATVPDKIKX0DER&amp;amp;psc=1&#34;&gt;Mismatch: How Inclusion Shapes Design, Kat Holmes&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Invisible-Women-Data-World-Designed/dp/1419729071/&#34;&gt;Invisible Women: Data Bias in a World Designed for Men, Caroline Criado Perez&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Technically-Wrong-Sexist-Algorithms-Threats/dp/0393356043&#34;&gt;Technically Wrong: Sexist Apps, Biased Algorithms, and Other Threats of Toxic Tech, Sara Wachter-Boettcher&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://ruinedby.design&#34;&gt;Ruined by Design, Mike Monteiro&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Articles&lt;/em&gt;&lt;br&gt;
&lt;a href=&#34;https://ourdataourselves.tacticaltech.org/posts/30-on-weaponised-design/&#34;&gt;On Weaponized Design, Cade Diehm&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.ethicsfordesigners.com/articles&#34;&gt;Ethics for Designers, Jet Gispen&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;tools-and-templates&#34;&gt;Tools and Templates&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;http://www.servicedesigntools.org/tools/14&#34;&gt;Tomorrow Headlines Exercise&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;http://tarotcardsoftech.artefactgroup.com/&#34;&gt;Tarot Cards of Tech&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.transfeministech.codingrights.org/&#34;&gt;Transfeminist Design Oracle&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.designethically.com/toolkit&#34;&gt;Design Ethically: Toolkit&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;with&lt;/strong&gt; Eileen Wagner, Molly Wilson&lt;br&gt;
&lt;strong&gt;Produced by&lt;/strong&gt; Ben Mergelsberg, Eileen Wagner, Molly Wilson, Georgia Bullen&lt;br&gt;
&lt;strong&gt;Directed by&lt;/strong&gt; Ben Mergelsberg&lt;br&gt;
&lt;strong&gt;Art Direction by&lt;/strong&gt; Ana Sol Alvarez&lt;br&gt;
&lt;strong&gt;Camera assistents:&lt;/strong&gt; Sarnt Utamachote, Nicolas Simkin&lt;br&gt;
&lt;strong&gt;Art:&lt;/strong&gt; Molly Wilson&lt;br&gt;
&lt;strong&gt;Filmed at&lt;/strong&gt; &lt;a href=&#34;https://www.stattlab.net&#34;&gt;Stattlab&lt;/a&gt; and &lt;a href=&#34;http://wrangelfilm.com&#34;&gt;Wrangelfilm&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Supported by&lt;/strong&gt; &lt;a href=&#34;https://www.adobe.com&#34;&gt;Adobe&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Special thanks to&lt;/strong&gt; Clarote&lt;br&gt;
&lt;strong&gt;Simply Secure CC-BY&lt;/strong&gt; (Georgia Bullen, Ame Elliott, Eileen Wagner, Molly Wilson)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Trust &amp; Consistency</title>
      <link>https://superbloom.design/learning/resources/tea-time-trust-consistency/</link>
      <pubDate>Wed, 21 Aug 2019 12:04:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/tea-time-trust-consistency/</guid>
      <description>
      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/349079211?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;br&gt;
&lt;p&gt;Continue the conversation on trust and responsibility. Host or attend an event on 24 September 2019 for &lt;a href=&#34;https://interactiondesignday.org&#34;&gt;World Interaction Design Day&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/banner-ixdd_hu_9820bcec290d7374.png&#34; alt=&#34;World Interaction Design Day Banner&#34; width=&#34;740&#34; height=&#34;91&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Presented by:&lt;/p&gt;
&lt;p&gt;| 
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/logo-adobe.jpg&#34; alt=&#34;Missing alt text&#34;&gt;
 | 

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/logo-IXDA_hu_f727576b1b2608a2.png&#34; width=&#34;740&#34; height=&#34;294&#34;&gt;
 | 

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/simplysecure-logo_hu_6c1f69db775471cd.png&#34; width=&#34;740&#34; height=&#34;118&#34;&gt;
 |&lt;/p&gt;
&lt;h3 id=&#34;resources&#34;&gt;Resources&lt;/h3&gt;
&lt;h4 id=&#34;principles-and-background&#34;&gt;Principles and Background&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Books&lt;/em&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Design-Systems-Smashing-eBooks-Kholmatova-ebook/dp/B076H49W1G/&#34;&gt;Design Systems, Alla Kholmatova&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.future-ethics.com/&#34;&gt;Future Ethics, Cennydd Bowles&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Thinking-Systems-Donella-H-Meadows-ebook/dp/B005VSRFEA/&#34;&gt;Thinking in Systems, Donella Meadows&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Users-Journey-Storymapping-Products-People-ebook/dp/B01D95U8UO/&#34;&gt;The User&amp;rsquo;s Journey: Storymapping Products That People Love, Donna Lichaw&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.goodreads.com/book/show/21406547-innovating-for-people&#34;&gt;Innovating for People: Handbook of Human-Centered Design Methods, Luma Institute&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.de/Manipulation-Beeinflussung-suhrkamp-taschenbuch-wissenschaft/dp/3518298283/&#34;&gt;Manipulation: Zur Theorie und Ethik einer Form der Beeinflussung, Alexander Fischer (in German)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Articles &amp;amp; Games&lt;/em&gt;&lt;br&gt;
&lt;a href=&#34;https://www.interaction-design.org/literature/article/trust-building-the-bridge-to-our-users&#34;&gt;Trust – Building the Bridge to Our Users, by John Geddes&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://hbr.org/2015/05/customer-data-designing-for-transparency-and-trust&#34;&gt;Customer Data: Designing for Transparency and Trust, by Timothy Morey, Theodore “Theo” Forbath, and Allison Schoop&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://ncase.me/trust/&#34;&gt;The Evolution of Trust, a playable simulation, by Nicky Case&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://medium.com/greater-than-experience-design/heres-what-airbnb-missed-when-designing-for-trust-3ded2d7fa15d&#34;&gt;Here’s What AirBnB Missed When Designing for Trust, by Nathan Kinch&lt;/a&gt; in reponse to &lt;a href=&#34;https://airbnb.design/designing-for-trust/&#34;&gt;Designing for Trust at Airbnb, by Charlie Aufmann&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://uxmag.com/articles/designing-to-build-trust-the-factors-that-matter&#34;&gt;Designing to Build Trust, by Ilana Westereman&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;http://makinggood.ac.nz/media/1270/mayeretal_1995_organizationaltrust.pdf&#34;&gt;An Integrative Model of Organizational Trust, by Roger Mayer, James H. Davis, and F. David Schoorman&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;with&lt;/strong&gt; Eileen Wagner, Molly Wilson&lt;br&gt;
&lt;strong&gt;Produced by&lt;/strong&gt; Ben Mergelsberg, Eileen Wagner, Molly Wilson, Georgia Bullen&lt;br&gt;
&lt;strong&gt;Directed by&lt;/strong&gt; Ben Mergelsberg&lt;br&gt;
&lt;strong&gt;Art Direction by&lt;/strong&gt; Ana Sol Alvarez&lt;br&gt;
&lt;strong&gt;Camera assistents:&lt;/strong&gt; Sarnt Utamachote, Nicolas Simkin&lt;br&gt;
&lt;strong&gt;Art:&lt;/strong&gt; Molly Wilson&lt;br&gt;
&lt;strong&gt;Filmed at&lt;/strong&gt; &lt;a href=&#34;https://www.stattlab.net&#34;&gt;Stattlab&lt;/a&gt; and &lt;a href=&#34;http://wrangelfilm.com&#34;&gt;Wrangelfilm&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Supported by&lt;/strong&gt; &lt;a href=&#34;https://www.adobe.com&#34;&gt;Adobe&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Special thanks to&lt;/strong&gt; Clarote&lt;br&gt;
&lt;strong&gt;Simply Secure CC-BY&lt;/strong&gt; (Georgia Bullen, Ame Elliott, Eileen Wagner, Molly Wilson)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Trust &amp; Transparency</title>
      <link>https://superbloom.design/learning/resources/tea-time-trust-transparency/</link>
      <pubDate>Wed, 21 Aug 2019 12:04:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/tea-time-trust-transparency/</guid>
      <description>
      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/349076200?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;br&gt;
&lt;p&gt;Continue the conversation on trust and responsibility. Host or attend an event on 24 September 2019 for &lt;a href=&#34;https://interactiondesignday.org&#34;&gt;World Interaction Design Day&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/banner-ixdd_hu_9820bcec290d7374.png&#34; alt=&#34;World Interaction Design Day Banner&#34; width=&#34;740&#34; height=&#34;91&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Presented by:&lt;/p&gt;
&lt;p&gt;| 
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/logo-adobe.jpg&#34; alt=&#34;Missing alt text&#34;&gt;
 | 

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/logo-IXDA_hu_f727576b1b2608a2.png&#34; width=&#34;740&#34; height=&#34;294&#34;&gt;
 | 

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/simplysecure-logo_hu_6c1f69db775471cd.png&#34; width=&#34;740&#34; height=&#34;118&#34;&gt;
 |&lt;/p&gt;
&lt;h3 id=&#34;resources&#34;&gt;Resources&lt;/h3&gt;
&lt;h4 id=&#34;principles-and-background&#34;&gt;Principles and Background&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Books&lt;/em&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Design-Systems-Smashing-eBooks-Kholmatova-ebook/dp/B076H49W1G/&#34;&gt;Design Systems, Alla Kholmatova&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.future-ethics.com/&#34;&gt;Future Ethics, Cennydd Bowles&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Thinking-Systems-Donella-H-Meadows-ebook/dp/B005VSRFEA/&#34;&gt;Thinking in Systems, Donella Meadows&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Users-Journey-Storymapping-Products-People-ebook/dp/B01D95U8UO/&#34;&gt;The User&amp;rsquo;s Journey: Storymapping Products That People Love, Donna Lichaw&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.goodreads.com/book/show/21406547-innovating-for-people&#34;&gt;Innovating for People: Handbook of Human-Centered Design Methods, Luma Institute&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Articles &amp;amp; Games&lt;/em&gt;&lt;br&gt;
&lt;a href=&#34;https://www.interaction-design.org/literature/article/trust-building-the-bridge-to-our-users&#34;&gt;Trust – Building the Bridge to Our Users, by John Geddes&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://hbr.org/2015/05/customer-data-designing-for-transparency-and-trust&#34;&gt;Customer Data: Designing for Transparency and Trust, by Timothy Morey, Theodore “Theo” Forbath, and Allison Schoop&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://ncase.me/trust/&#34;&gt;The Evolution of Trust, a playable simulation, by Nicky Case&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://medium.com/greater-than-experience-design/heres-what-airbnb-missed-when-designing-for-trust-3ded2d7fa15d&#34;&gt;Here’s What AirBnB Missed When Designing for Trust, by Nathan Kinch&lt;/a&gt; in response to &lt;a href=&#34;https://airbnb.design/designing-for-trust/&#34;&gt;Designing for Trust at Airbnb, by Charlie Aufmann&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://uxmag.com/articles/designing-to-build-trust-the-factors-that-matter&#34;&gt;Designing to Build Trust, by Ilana Westereman&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;http://makinggood.ac.nz/media/1270/mayeretal_1995_organizationaltrust.pdf&#34;&gt;An Integrative Model of Organizational Trust, by Roger Mayer, James H. Davis, and F. David Schoorman&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;with&lt;/strong&gt; Eileen Wagner, Molly Wilson&lt;br&gt;
&lt;strong&gt;Produced by&lt;/strong&gt; Ben Mergelsberg, Eileen Wagner, Molly Wilson, Georgia Bullen&lt;br&gt;
&lt;strong&gt;Directed by&lt;/strong&gt; Ben Mergelsberg&lt;br&gt;
&lt;strong&gt;Art Direction by&lt;/strong&gt; Ana Sol Alvarez&lt;br&gt;
&lt;strong&gt;Camera assistents:&lt;/strong&gt; Sarnt Utamachote, Nicolas Simkin&lt;br&gt;
&lt;strong&gt;Art:&lt;/strong&gt; Molly Wilson&lt;br&gt;
&lt;strong&gt;Filmed at&lt;/strong&gt; &lt;a href=&#34;https://www.stattlab.net&#34;&gt;Stattlab&lt;/a&gt; and &lt;a href=&#34;http://wrangelfilm.com&#34;&gt;Wrangelfilm&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Supported by&lt;/strong&gt; &lt;a href=&#34;https://www.adobe.com&#34;&gt;Adobe&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Special thanks to&lt;/strong&gt; Clarote&lt;br&gt;
&lt;strong&gt;Simply Secure CC-BY&lt;/strong&gt; (Georgia Bullen, Ame Elliott, Eileen Wagner, Molly Wilson)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Trust &amp; User Needs</title>
      <link>https://superbloom.design/learning/resources/tea-time-trust-user-needs/</link>
      <pubDate>Wed, 21 Aug 2019 12:04:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/tea-time-trust-user-needs/</guid>
      <description>&lt;iframe src=&#34;https://player.vimeo.com/video/349080146&#34; width=&#34;640&#34; height=&#34;338&#34; frameborder=&#34;0&#34; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;
&lt;br&gt;
&lt;p&gt;Continue the conversation on trust and responsibility. Host or attend an event on 24 September 2019 for &lt;a href=&#34;https://interactiondesignday.org&#34;&gt;World Interaction Design Day&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/banner-ixdd_hu_9820bcec290d7374.png&#34; alt=&#34;World Interaction Design Day Banner&#34; width=&#34;740&#34; height=&#34;91&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Presented by:&lt;/p&gt;
&lt;p&gt;| 
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/logo-adobe.jpg&#34; alt=&#34;Missing alt text&#34;&gt;
 | 

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/logo-IXDA_hu_f727576b1b2608a2.png&#34; width=&#34;740&#34; height=&#34;294&#34;&gt;
 | 

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/simplysecure-logo_hu_6c1f69db775471cd.png&#34; width=&#34;740&#34; height=&#34;118&#34;&gt;
 |&lt;/p&gt;
&lt;h3 id=&#34;resources&#34;&gt;Resources&lt;/h3&gt;
&lt;h4 id=&#34;principles-and-background&#34;&gt;Principles and Background&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Books&lt;/em&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Design-Systems-Smashing-eBooks-Kholmatova-ebook/dp/B076H49W1G/&#34;&gt;Design Systems, Alla Kholmatova&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.future-ethics.com/&#34;&gt;Future Ethics, Cennydd Bowles&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Thinking-Systems-Donella-H-Meadows-ebook/dp/B005VSRFEA/&#34;&gt;Thinking in Systems, Donella Meadows&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.amazon.com/Users-Journey-Storymapping-Products-People-ebook/dp/B01D95U8UO/&#34;&gt;The User&amp;rsquo;s Journey: Storymapping Products That People Love, Donna Lichaw&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://www.goodreads.com/book/show/21406547-innovating-for-people&#34;&gt;Innovating for People: Handbook of Human-Centered Design Methods, Luma Institute&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Articles &amp;amp; Games&lt;/em&gt;&lt;br&gt;
&lt;a href=&#34;https://www.interaction-design.org/literature/article/trust-building-the-bridge-to-our-users&#34;&gt;Trust – Building the Bridge to Our Users, by John Geddes&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;http://nxhx.org/dfa/&#34;&gt;Design for Agency, Joe Edelman&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://hbr.org/2015/05/customer-data-designing-for-transparency-and-trust&#34;&gt;Customer Data: Designing for Transparency and Trust, by Timothy Morey, Theodore “Theo” Forbath, and Allison Schoop&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://ncase.me/trust/&#34;&gt;The Evolution of Trust, a playable simulation, by Nicky Case&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://medium.com/greater-than-experience-design/heres-what-airbnb-missed-when-designing-for-trust-3ded2d7fa15d&#34;&gt;Here’s What AirBnB Missed When Designing for Trust, by Nathan Kinch&lt;/a&gt; in response to &lt;a href=&#34;https://airbnb.design/designing-for-trust/&#34;&gt;Designing for Trust at Airbnb, by Charlie Aufmann&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;https://uxmag.com/articles/designing-to-build-trust-the-factors-that-matter&#34;&gt;Designing to Build Trust, by Ilana Westereman&lt;/a&gt;&lt;br&gt;
&lt;a href=&#34;http://makinggood.ac.nz/media/1270/mayeretal_1995_organizationaltrust.pdf&#34;&gt;An Integrative Model of Organizational Trust, by Roger Mayer, James H. Davis, and F. David Schoorman&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;credits&#34;&gt;Credits&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;with&lt;/strong&gt; Eileen Wagner, Molly Wilson&lt;br&gt;
&lt;strong&gt;Produced by&lt;/strong&gt; Ben Mergelsberg, Eileen Wagner, Molly Wilson, Georgia Bullen&lt;br&gt;
&lt;strong&gt;Directed by&lt;/strong&gt; Ben Mergelsberg&lt;br&gt;
&lt;strong&gt;Art Direction by&lt;/strong&gt; Ana Sol Alvarez&lt;br&gt;
&lt;strong&gt;Camera assistents:&lt;/strong&gt; Sarnt Utamachote, Nicolas Simkin&lt;br&gt;
&lt;strong&gt;Art:&lt;/strong&gt; Molly Wilson&lt;br&gt;
&lt;strong&gt;Filmed at&lt;/strong&gt; &lt;a href=&#34;https://www.stattlab.net&#34;&gt;Stattlab&lt;/a&gt; and &lt;a href=&#34;http://wrangelfilm.com&#34;&gt;Wrangelfilm&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Supported by&lt;/strong&gt; &lt;a href=&#34;https://www.adobe.com&#34;&gt;Adobe&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Special thanks to&lt;/strong&gt; Clarote&lt;br&gt;
&lt;strong&gt;Simply Secure CC-BY&lt;/strong&gt; (Georgia Bullen, Ame Elliott, Eileen Wagner, Molly Wilson)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Identity and Values</title>
      <link>https://superbloom.design/learning/resources/identity_worksheet/</link>
      <pubDate>Wed, 21 Aug 2019 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/identity_worksheet/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Qualitative Interview Cheat Sheet</title>
      <link>https://superbloom.design/learning/resources/qualitative_interviews/</link>
      <pubDate>Wed, 21 Aug 2019 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/qualitative_interviews/</guid>
      <description></description>
    </item>
    
    <item>
      <title>User Testing Cheat Sheet</title>
      <link>https://superbloom.design/learning/resources/user-testing-cheat-sheet/</link>
      <pubDate>Wed, 21 Aug 2019 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/user-testing-cheat-sheet/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Value Proposition Generator</title>
      <link>https://superbloom.design/learning/resources/value_proposition_worksheet/</link>
      <pubDate>Wed, 21 Aug 2019 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/value_proposition_worksheet/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Persona Template for Tech Tools</title>
      <link>https://superbloom.design/learning/resources/persona/</link>
      <pubDate>Sat, 17 Aug 2019 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/persona/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Post-Interview Debrief</title>
      <link>https://superbloom.design/learning/resources/interview_synthesis/</link>
      <pubDate>Thu, 15 Aug 2019 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/interview_synthesis/</guid>
      <description></description>
    </item>
    
    <item>
      <title>App Feedback Gathering Exercise</title>
      <link>https://superbloom.design/learning/resources/app_feedback_gathering/</link>
      <pubDate>Sun, 04 Aug 2019 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/app_feedback_gathering/</guid>
      <description></description>
    </item>
    
    <item>
      <title>On Trust and Transparency: Perspectives from Luminate&#39;s portfolio</title>
      <link>https://superbloom.design/learning/blog/on-trust-and-transparency/</link>
      <pubDate>Wed, 17 Jul 2019 00:08:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/on-trust-and-transparency/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/rowing_hu_8f41a4280b0b1ccb.jpg&#34; alt=&#34;rowing&#34; width=&#34;740&#34; height=&#34;310&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Over the last year, in partnership with &lt;a href=&#34;https://luminategroup.com/&#34;&gt;Luminate&lt;/a&gt; (&lt;em&gt;formerly known as Government &amp;amp; Citizen Engagement, part of the &lt;a href=&#34;https://www.omidyar.com/&#34;&gt;Omidyar Network&lt;/a&gt;&lt;/em&gt;), we delved into the complex environment and relationships of the funding experience, leveraging a human-centered research approach. The goal was to better understand an organization&amp;rsquo;s experience in the funding process with the Government &amp;amp; Citizen Engagement (GCE) team at the Omidyar Network. &lt;a href=&#34;https://ontrustandtransparency.report/insights/&#34;&gt;Nine insights&lt;/a&gt; and &lt;a href=&#34;https://ontrustandtransparency.report/recommendations/&#34;&gt;thirty-four recommendations&lt;/a&gt; emerged from the work, which you can explore on the &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;report website&lt;/a&gt; or by reading the report, &lt;em&gt;&amp;quot;&lt;a href=&#34;https://superbloom.design/resources/ott/On_Trust_and_Transparency.pdf&#34;&gt;On Trust &amp;amp; Transparency: Perspectives from Luminate&amp;rsquo;s portfolio&lt;/a&gt;.&amp;quot;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Understanding the experience of the funding process is a perfect fit for the human-centered approach we specialize in. Our interviews used the same topic structure and started in the same place, but by the halfway point, each interview had turned into a semi-structured conversation. Forsaking the predictability of a cookie-cutter approach allowed us to learn the needs, histories, priorities, pain points, hopes, and fears of each interviewee. Then, our follow-up survey zeroed in on particularly hot topics from our interviews. This two-phase research process allowed us to report on what grantees actually felt was important.&lt;/p&gt;
&lt;h3 id=&#34;whats-the-big-deal-about-trust-and-transparency&#34;&gt;What&amp;rsquo;s the big deal about trust and transparency?&lt;/h3&gt;
&lt;p&gt;We think one reason that trust and transparency kept coming up is that these are complex topics in any business relationship, but particularly in one with a baked-in &lt;a href=&#34;https://ontrustandtransparency.report/insights/power-dynamics/&#34;&gt;power asymmetry&lt;/a&gt;. No matter how honest and genuine the conversations between an executive director and an investment lead, one of them is responsible for the other&amp;rsquo;s organizational survival. But even though it&amp;rsquo;s not an easy playing field, both Luminate and grantees expressed over and over their hope and their optimism that the relationship actually could be a healthy and open one.&lt;/p&gt;
&lt;p&gt;In a &lt;a href=&#34;https://ontrustandtransparency.report/insights/deep-trusting-relationships/&#34;&gt;trusting relationship&lt;/a&gt;, both parties are confident that the other has their interests in mind. In this case, grantees need to see that Luminate truly understands their point of view, and they need to be involved in determining what kind of support is best for them. And, again and again, they brought up the theme of transparency. Transparency doesn&amp;rsquo;t always lead to trust in relationships, but in most cases, it&amp;rsquo;s certainly a big step in the right direction.&lt;/p&gt;
&lt;p&gt;One major way to bring trust to this challenging area is by sharing as much information as possible about the &lt;a href=&#34;https://ontrustandtransparency.report/insights/structure-and-clarity/&#34;&gt;funding process&lt;/a&gt;, the &lt;a href=&#34;https://ontrustandtransparency.report/insights/reporting-and-metrics/&#34;&gt;choice of metrics&lt;/a&gt;, &lt;a href=&#34;https://ontrustandtransparency.report/insights/diversity-equity-and-inclusion/&#34;&gt;diversity/equity/inclusion issues&lt;/a&gt;, and &lt;a href=&#34;https://ontrustandtransparency.report/insights/funder-roles/&#34;&gt;funders&amp;rsquo; dual personal and professional role&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;when-trust-and-transparency-clash&#34;&gt;When trust and transparency clash&lt;/h3&gt;
&lt;p&gt;Not many funders would have the courage to commission a study that was bound to lead into some of the most sensitive areas of their work. The Luminate team was deeply curious about their grantees&amp;rsquo; experience, and they saw this study as a way to learn.&lt;/p&gt;
&lt;p&gt;In order to help Luminate learn about trust and transparency, we actually needed to develop strong practices around privacy and anonymity in our research process. Our commitment to strong security practices during the research process meant that, Luminate didn&amp;rsquo;t have visibility into who said what, but they were able to engage deeply in the research design process. Our methods, process, and approach were all transparent with Luminate, with participants, and now with you. If you are interested in following a similar process, definitely dig into the &lt;a href=&#34;https://ontrustandtransparency.report/project-details/&#34;&gt;methods and the guides&lt;/a&gt;, as well as our blog posts about &lt;a href=&#34;https://superbloom.design/learning/resources/data-handling&#34;&gt;threat modeling and data practices&lt;/a&gt; and &lt;a href=&#34;https://superbloom.design/learning/blog/sensitive-interviews&#34;&gt;earning trust in sensitive interviews&lt;/a&gt;. Security threat modeling and ethical practices in design research complement each other beautifully, and we hope that by sharing our tools, others researching sensitive topics can take this approach as well.&lt;/p&gt;
&lt;h3 id=&#34;an-inspiring-collaboration-for-us-and-we-hope-for-you&#34;&gt;An inspiring collaboration for us – and, we hope, for you&lt;/h3&gt;
&lt;p&gt;We hope that both the insights and &lt;a href=&#34;https://ontrustandtransparency.report/project-details/&#34;&gt;methodology&lt;/a&gt; are useful and inspiring to you. And we want to express our warmest admiration to the team at Luminate, for their openness throughout this challenging process. One last thanks to &lt;a href=&#34;https://objectively.is/&#34;&gt;Objectively&lt;/a&gt; for helping to breathe life into the report on the web. We hope that this report will spark a spirited conversation about how funders and grantees can work together more mindfully, holistically, and, in the end, effectively.&lt;/p&gt;
&lt;h3 id=&#34;additional-resources&#34;&gt;Additional Resources&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Report (&lt;a href=&#34;https://superbloom.design/resources/ott/On_Trust_and_Transparency.pdf&#34;&gt;PDF&lt;/a&gt;, &lt;a href=&#34;https://ontrustandtransparency.report/&#34;&gt;website&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/resources/ott/OTT-InterviewGuide-AppendixA.pdf&#34;&gt;Interview Guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/resources/ott/OTT-SurveyGuide-AppendixB.pdf&#34;&gt;Survey Guide&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Photo Credit: &lt;a href=&#34;https://www.flickr.com/photos/singapore2010/4892838185/in/photolist-8sn5k4-LY7F9B-LR35Fe-9nHY45-LNvLi5-9nEW7i-LNvBsj-5eazXt-LNvLHJ-4NkUd4-yboWue-85L4aa-dNi16P-85Pia9-LR35eT-LwvTVo-LwvSEN-LV6jnY-Mf9Etz-85PbGN-LY7Ga4-efsYCd-85Pch9-85L5iX-LV6pdu-85L3nr-85PaZh-85L3WX-85PfUJ-CbjSwo-85PaRq-85L7z2-pjK1en-85Pb6o-LwvWf3-85L7AP-85L3ZP-85L2np-85L3yF-85PfEW-85L2BV-85PfHm-wkmf8M-85P9aq-8dp8Tz-a8z6DX-NmGBQE-4fjzMa-ooMrve-hohjLw/&#34;&gt;XINHUA/SYOGOC-Pool/Liu Jie&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Earning Trust in Sensitive Interviews</title>
      <link>https://superbloom.design/learning/blog/sensitive-interviews/</link>
      <pubDate>Thu, 20 Jun 2019 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/sensitive-interviews/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/statues_talking_hu_c6b534d2f6ea7dbe.jpg&#34; alt=&#34;photo of statues talking&#34; width=&#34;740&#34; height=&#34;419&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Most of the time, honest conversations about sensitive topics happen between people who have known each other a long time, who&amp;rsquo;ve worked together, who&amp;rsquo;ve built up a foundation of trust. They don&amp;rsquo;t happen when some unknown people cold-email you and ask to make a one-hour appointment with you – right?&lt;/p&gt;
&lt;h2 id=&#34;setting-up-a-sensitive-interview&#34;&gt;Setting up a sensitive interview&lt;/h2&gt;
&lt;p&gt;At Simply Secure, we often find ourselves in the challenging position of needing to ask people we&amp;rsquo;ve just met about sensitive topics. Most recently, we&amp;rsquo;ve been working on a year-long project exploring the topic of power dynamics in the funder-grantee relationship. We set out to ask organizations about their funding experience – on behalf of the organization that, in many cases, holds the key to their survival. How could we have an honest conversation about a topic as core, and as fraught, as funding?&lt;/p&gt;
&lt;p&gt;We did have one advantage going in: as a neutral third party, we were in a better position than a staff member from the funder to get honest answers from organizations. However, as a completely unknown quantity, we were at a disadvantage: nobody knew us well enough to trust us with sensitive information. We needed to build trust, and fast.&lt;/p&gt;
&lt;p&gt;Our tactic was to lean on our expertise in two pretty different fields: security and design research. We used careful &lt;a href=&#34;https://superbloom.design/learning/resources/data-handling&#34;&gt;security practices&lt;/a&gt; to ensure confidentiality and privacy in our interviews, and made sure to make these practices were transparent to our interviewees. And we used &lt;a href=&#34;https://superbloom.design/learning/blog/feedback-gathering-guide&#34;&gt;design research techniques&lt;/a&gt; to set the tone for an open conversation.&lt;/p&gt;
&lt;h3 id=&#34;lessons-from-security-identifying-a-threat-model-and-mitigating-the-risks&#34;&gt;Lessons from security: Identifying a threat model and mitigating the risks&lt;/h3&gt;
&lt;p&gt;The concept of a &amp;ldquo;threat model&amp;rdquo; is key to designing effective security: in order to make something safer for somebody, you need to proactively defend against the most likely threats to that person in their context. The threat model for our participants was centered around attribution of feedback, meaning that keeping their participation in the research private from both the funder and other participants was critical.&lt;/p&gt;
&lt;p&gt;To accommodate this threat model, we used a variety of techniques. We took notes only on paper, and did most of our synthesis on paper in person in our Berlin office. We used encrypted email and other encrypted messaging. We used animal pseudonyms (Narwhal, Wombat, etc.) when contacting participants, when entering appointments into our Google calendar, and when discussing the interviews on our internal Slack. All documents that linked pseudonyms to actual identities were kept on a single encrypted drive in a safe in our office.&lt;/p&gt;
&lt;p&gt;Just as important as the actual techniques we used was the fact that we told participants about them. We always led with a sentence like, &amp;ldquo;it&amp;rsquo;s very important to us that the funder doesn&amp;rsquo;t know we talked to you or what you said, so we&amp;rsquo;re taking these precautions.&amp;rdquo; We prepared a sheet giving examples of our practices for anonymizing quotations in our report. The fact that we had correctly identified our participants&amp;rsquo; threat model and were taking steps to address it went a long way towards helping us gain their trust. In many cases, participants didn&amp;rsquo;t seem particularly interested in the specifics of our security practices; just knowing that we understood their threat model and had a thought-through set of practices was enough for them.&lt;/p&gt;
&lt;h3 id=&#34;lessons-from-design-research&#34;&gt;Lessons from design research&lt;/h3&gt;
&lt;p&gt;Design research is different from many other kinds of qualitative research in that it has an exploratory, human-centered focus. Rather than a list of questions to ask, we came to each interview with a list of topic areas to explore together. We wanted to ask about a few core areas: the organization&amp;rsquo;s history with the funder, their perception of the funder, and the process of applying for and receiving funding. But every interview was different: sometimes we ended up talking a lot about personal relationships, sometimes we ended up focusing more on financial reporting.&lt;/p&gt;
&lt;p&gt;We told participants this at the very beginning of each interview. We told them that we were hoping to have a conversation, not an interrogation. We told them that we wanted to learn their story, whether or not it was &amp;ldquo;average&amp;rdquo; or &amp;ldquo;representative.&amp;rdquo; We told them that it was our responsibility to redirect the conversation if necessary, and that they should just talk.&lt;/p&gt;
&lt;p&gt;Because our interviews were flexible rather than rigid, participants could tell that we were listening. If they brought up a pain point, rather than moving on to the next question, we asked them to dive into it. If they seemed particularly preoccupied with a certain aspect of the funding experience, we asked them more about it. Being listened to as an individual, rather than being shepherded through a one-size-fits-all process, helped each participant realize that we wanted and needed to hear their story, a story literally nobody else could tell.&lt;/p&gt;
&lt;p&gt;We also made sure to thank participants as specifically as possible. &amp;ldquo;Thanks for your time&amp;rdquo; is generic; &amp;ldquo;thanks for opening our eyes to the unique situation in your country&amp;rdquo; shows that we heard their story.&lt;/p&gt;
&lt;p&gt;—&lt;/p&gt;
&lt;p&gt;We are grateful for the trust that every participant placed in us, and we hope our final report reflects this. If you find yourself in a position where you need to build trust in a complex or sensitive research situation, feel free to reach out to us; we&amp;rsquo;re happy to share more insights from both security and design.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Photo Credit: &lt;a href=&#34;https://www.flickr.com/photos/infomatique/47261164321/in/photolist-h8dVxn-MyN2xQ-edTXsw-AZkTHG-h4rFZD-2dUnxuU-2dBuE6Z-2f1iPAH-h4sSke-85MQDD-h4sSw6-bFHo3Z-9jbHAg-edTXkm-rcnEyP-7bPCsc-E3UpNh-p5gybD-8TtnmB-dCagG1-9jeckT-2miM67-iuCEXD-bzEXuM-24oSeVi-5Chmjd-ec7cAU-ec1wse-6tpndW-ec1wmF-edNhTt-9mCxyP-ec7cxE-edTXd5-9n7C6t-edNhuP-9naF3f-85oi1K-89kZ3e-edNhVx-ec7czQ-WcyGcM-9mCxzv-DWZ39g-D8vcYs-nUa1Wz-ec7cz7-ec1wp4-9mFAMG-ec7cyu&#34;&gt;William Murphy&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Data Handling Best Practices</title>
      <link>https://superbloom.design/learning/resources/data-handling/</link>
      <pubDate>Tue, 04 Jun 2019 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/data-handling/</guid>
      <description>&lt;p&gt;While a lot of our work focuses on bringing human-centered approaches to privacy and security projects, we also try to incorporate privacy and security best practices in our human-centered research on a daily basis. In previous posts, we have outlined how to supplement your research with a &lt;a href=&#34;https://superbloom.design/learning/blog/participant-rights&#34;&gt;participant bill of rights&lt;/a&gt; or a &lt;a href=&#34;https://superbloom.design/learning/blog/model-release&#34;&gt;model release form&lt;/a&gt;. We also shot a video about &lt;a href=&#34;https://superbloom.design/learning/resources/design-spot-high-risk-research&#34;&gt;doing research with at-risk participants&lt;/a&gt;. This post outlines some of our best practices in data handling for user research.&lt;/p&gt;
&lt;p&gt;Doing data handling with privacy and security in mind means spending some time to identify different threats, culminating in a threat model, and coming up with strategies that fit the particular threat model. We’ve compiled some best practices for both risk assessment and security strategies.&lt;/p&gt;
&lt;h2 id=&#34;risk-assessment&#34;&gt;Risk assessment&lt;/h2&gt;
&lt;p&gt;Any risk assessment begins with considering what data you will be collecting for the research. Some guiding questions are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What is the most sensitive data you are collecting?
&lt;ul&gt;
&lt;li&gt;Is there a copy of this data anywhere else?&lt;/li&gt;
&lt;li&gt;Who else knows where it is?&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Is the data easy to relate to an individual?&lt;/li&gt;
&lt;li&gt;Where do you store data, and who else has access to it?&lt;/li&gt;
&lt;li&gt;Who knows how much of the research, and when? (Think about team, organization, client, public.) Are there policies about what you can disclose, and to whom?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Next, evaluate the risks your data collection would pose to the participants. Risks can mean (but aren’t limited to):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Risk of personal data leaking&lt;/li&gt;
&lt;li&gt;Risk of research content leaking&lt;/li&gt;
&lt;li&gt;Risk of association with this tool/research&lt;/li&gt;
&lt;li&gt;Risk of association with stakeholders involved&lt;/li&gt;
&lt;li&gt;Risk of participants knowing about each other&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Write down a list of risks based on stakeholders in the research you are conducting, and consider both the severity (how bad the situation would be) and the likelihood of that situation occurring. (We are attaching an example at the end of this post.)&lt;/p&gt;
&lt;p&gt;&lt;mark&gt;risk = severity x likelihood&lt;/mark&gt;&lt;/p&gt;
&lt;p&gt;(To read more about this specifically, check out our &lt;a href=&#34;https://simplysecure.org/what-we-do/usable-security-audit/&#34;&gt;usable security methodology&lt;/a&gt;.)&lt;/p&gt;
&lt;h2 id=&#34;security-strategies-for-mitigating-risks&#34;&gt;Security strategies for mitigating risks&lt;/h2&gt;
&lt;p&gt;Depending on the output of your risk assessment, you will want to alter the process and tooling of your research. Here are, roughly, the strategies you might choose to mitigate the risks.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Differentiate&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Treat different aspects of your research differently &amp;ndash; personal notes from your interview should be treated differently from a contact list. Knowing how sensitive different data is can help you differentiate your strategies.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Minimise data&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Reflect on what data you actually need to complete the research, and only collect what you need. For personal information, ask yourself: does it matter how old participants are, what gender they identify with, or where they live? Do you need their email address or phone number? If you are offering a compensation, can you do that without their bank account information?&lt;/li&gt;
&lt;li&gt;What tools are you using to coordinate the work? What information do your tools collect? You need to assess how the tools you are using also collect data and think about how that intersects with the risks you’ve identified. Choose privacy-friendly tools for online surveys, scheduling, and click-testing (this means &lt;strong&gt;no tracking&lt;/strong&gt; by default.)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Go local&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Does your data need to live on a cloud? Do you need remote access to the data? Or can access to the data be limited in physical location? If you and your team are working from the same location, there’s no need to use cloud services to facilitate access to the data. Even if you have remote team members, they might not need direct access to the data.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Go analogue&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Does your data need to be on a digital medium? Consider using pen and paper to document your research. In many cases, we found that it doesn’t make sense to have video or audio recordings.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Encrypt&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Encrypt hard drives as well as external drives for sharing, and only give out passwords to team members who need access to the data.&lt;/li&gt;
&lt;li&gt;Encrypt communication with participants and team members alike.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Anonymize&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Use pseudonyms or handles for participants from the beginning. (We like using memorable animal names.)&lt;/li&gt;
&lt;li&gt;Anonymize how you present the information. For example, you should redact or edit quotes that could potentially identify individuals. If you take pictures, focus on people’s hands and feet rather than their faces.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Segment&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Set up infrastructure that is easy to remove later. For example, a separate calendar and email account for each research project means it’s easy to remove the data afterwards.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Secure&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Physical security matters just as much: who has access to your office, and how easy is it to get information from your office? (Also consider “sticky note walls” as potentially leaking information to visitors.)&lt;/li&gt;
&lt;li&gt;Back up a copy of your most important data at a trusted location in case your office gets searched by police or other adversaries.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Communicate&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Be transparent about your security decisions to all participants. Ask for their consent before you begin the research.&lt;/li&gt;
&lt;li&gt;Clarify what information is OK to share with whom, and when, with your client and team members, as well as participants. Where necessary, supplement it with an NDA.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Delete&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Set a data retention time period. We recommend deleting all research data 6 months after the research is done (and published).&lt;/li&gt;
&lt;li&gt;Schedule a “data review” regularly to see if there is any unnecessary information on your devices / your cloud.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;example&#34;&gt;Example&lt;/h2&gt;
&lt;p&gt;To see how these principles interact, let’s look at a case from some of our recent research on the grantee experience with a funder. First and foremost, we wanted to protect confidentiality with our participants&amp;ndash;organizations and businesses who are receiving funding from the funder, and were willing to speak to us about their funding relationship. Participants are putting a lot of trust in us, and we wanted to be extra sure that our research was not putting their funding relationship at risk. Based on what we knew, we drafted a simple matrix:&lt;/p&gt;
&lt;table cellspacing=&#34;0&#34; cellpadding=&#34;0&#34;&gt;
  &lt;tr&gt;
    &lt;th&gt;Adversarial scenario&lt;/th&gt;&lt;th&gt;Level of risk&lt;/th&gt;&lt;th&gt;Reasoning&lt;/th&gt;
  &lt;/tr&gt;
  &lt;tr&gt;
    &lt;td&gt;Funder finding out participants’ identities&lt;/td&gt;&lt;td&gt;HIGH&lt;/td&gt;&lt;td&gt;Given that we are incorporating the funder at every stage of the research, it’s conceivable that through accidentally sharing email invites or not properly redacting interview transcripts we could reveal who said what, and that may have negative repercussions for participants.&lt;/td&gt;
  &lt;/tr&gt;
  &lt;tr class=&#34;even&#34;&gt;
    &lt;td&gt;Participants finding out about each others’ participation&lt;/td&gt;&lt;td&gt;MEDIUM&lt;/td&gt;&lt;td&gt;Even if Simply Secure did well with anonymizing the information, it is possible that participants who know each other would be talking about this research. This information could A) get back to the funder, or B) influence participation in the research, e.g. who participates in the research, what they would tell us, and if they might try to intentionally influence the research in some way.&lt;/td&gt;
  &lt;/tr&gt;
  &lt;tr&gt;
    &lt;td&gt;Public finding out content of the interviews&lt;/td&gt;&lt;td&gt;LOW&lt;/td&gt;&lt;td&gt;Even though the content will go through synthesis and eventually be published, we wouldn’t want sensitive issues to be disclosed to the public without the funder’s consent. However, we don’t expect people interested in this data to engage in criminal activities.&lt;/td&gt;
  &lt;/tr&gt;
  &lt;tr&gt;
    &lt;td&gt;Governments finding out participant’s funding sources&lt;/td&gt;&lt;td&gt;LOW&lt;/td&gt;&lt;td&gt;Most participants list openly their funding sources anyway.&lt;/td&gt;
  &lt;/tr&gt;
&lt;/table&gt;
&lt;p&gt;We assigned pseudonyms to everyone who answered our call for participation. This list of assignments was the most sensitive piece of data and arguably more important to keep safe rather than the content of the interviews. We protected it on an encrypted external drive that only two team members had access to. The content of the interviews were in turn documented on paper, and we did the synthesis on paper in our office, which we then destroyed.&lt;/p&gt;
&lt;p&gt;Based on the risk assessment, we decided that the channel of communication might not have to be the most secure (though we would always prefer end-to-end encrypted video chats), but the calendaring tool that details &lt;strong&gt;who&lt;/strong&gt; we are talking to is more important to keep safe. We thus decided to use pseudonyms on the calendar invitations that we used, and sent out calendar files that did not link email addresses.&lt;/p&gt;
&lt;h2 id=&#34;data-handling-statement&#34;&gt;Data handling statement&lt;/h2&gt;
&lt;p&gt;Once you have decided on a data handling strategy, it’s time to write up a statement that you should attach to any invitation for participation. We have drafted a &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/research_tools/data-handling-statement.md&#34;&gt;data handling template&lt;/a&gt; for you to use.&lt;/p&gt;
&lt;p&gt;This is a rough outline of our data handling practices. Of course, trust is something that has to be earned, and merely safeguarding your research with consent forms and data handling statements isn’t enough. You earn trust by following through with these policies, and by listening to your participants and being receptive to their privacy and security needs during the entire research period.&lt;/p&gt;
&lt;h2 id=&#34;resources&#34;&gt;Resources:&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Template: &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/research_tools/data-handling-statement.md&#34;&gt;Data Handling Statement&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://simplysecure.org/what-we-do/usable-security-audit/&#34;&gt;Usable Security Audit framework&lt;/a&gt; for risk assessment&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/resources/design-spot-high-risk-research&#34;&gt;Our Design Spot&lt;/a&gt; on user research with at-risk participants&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.theengineroom.org/wp-content/uploads/2018/03/Ties-that-Bind-Full-Report.pdf&#34;&gt;Ties That Bind&lt;/a&gt; report on organizational security&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://github.com/leeange/DSPPUX-Checklist&#34;&gt;UX Checklist&lt;/a&gt; for privacy-aware user research&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Tell us about your experience with investigative journalism tools</title>
      <link>https://superbloom.design/learning/blog/occrp/</link>
      <pubDate>Mon, 20 May 2019 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/occrp/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/zeitung_hu_6d7550f826435c58.jpg&#34; alt=&#34;photo of German newspapers&#34; width=&#34;740&#34; height=&#34;326&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Simply Secure is partnering with the &lt;a href=&#34;https://www.occrp.org/en&#34;&gt;Organized Crime and Corruption Reporting Project (OCCRP)&lt;/a&gt; to develop their data platform, &lt;a href=&#34;http://data.occrp.org&#34;&gt;data.occrp.org&lt;/a&gt;. The site is probably the largest data archive in nonprofit investigative journalism, and it’s built on an open source tool that anyone can re-use. We are also working with OCCRP to re-build VIS, a network visualisation tool for investigators.&lt;/p&gt;
&lt;p&gt;These tools need to be better, quicker, more precise. That&amp;rsquo;s why we, and OCCRP, want to take a step back and get some systematic feedback from investigators, journalists, and researchers. Whether you’re new to OCCRP’s tools or experienced with them, we would be grateful for the chance to talk to you about your processes and tools.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Do you work with data in a journalistic capacity – as a researcher, an investigator, a freelance journalist, or as part of a newsroom or news organization – or do you know somebody who does?&lt;/li&gt;
&lt;li&gt;Do you have 30-60 minutes to donate in May or June for a conversation with Simply Secure? Interviews can be remote (using screen-sharing) or in person in Berlin or London. We can provide a small gift in exchange for your help.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you can help, please contact SimplySecure’s researcher, Molly Wilson, at molly [ at ] superbloom [ dot ] design (PGP ID: 3427 2860 D066 35CB) by mid-June 2019.&lt;/p&gt;
&lt;p&gt;Both Simply Secure and OCCRP are grateful for your feedback and help!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Creating Patterns for Decentralized Systems</title>
      <link>https://superbloom.design/learning/blog/decentral-patterns-project/</link>
      <pubDate>Tue, 30 Apr 2019 14:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/decentral-patterns-project/</guid>
      <description>&lt;p&gt;Exciting news! Simply Secure was awarded a &lt;a href=&#34;https://www.samsungnext.com/&#34;&gt;SamsungNEXT grant&lt;/a&gt; for design in decentralization. This allows us to develop our long-standing idea of a pattern library for decentralized systems.&lt;/p&gt;
&lt;p&gt;What do we mean by that?&lt;/p&gt;
&lt;p&gt;By &amp;ldquo;design patterns&amp;rdquo;, we mean a best practice user flow or interaction that projects can use or draw from. An example of a design pattern would be a pop-up window for &lt;a href=&#34;https://catalogue.projectsbyif.com/patterns/just-in-time-consent&#34;&gt;just-in-time consent&lt;/a&gt;. A pattern library, of course, is a collection of patterns. By &amp;ldquo;decentralised systems&amp;rdquo;, we mean protocols, apps, and services that are non-centralised&amp;ndash;that includes both federated networks and the stronger concept of distributed networks (p2p).&lt;/p&gt;
&lt;p&gt;We’ve been seeing some common challenges across the board for decentralization projects, such as communicating privacy, key management, and even just explaining what decentralized systems are. (&lt;a href=&#34;https://superbloom.design/learning/blog/decentral-patterns&#34;&gt;Read more in our post.&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;All projects working in this area are facing similar issues, and these issues don&amp;rsquo;t have to (and can&amp;rsquo;t!) be solved individually. Our hope is to get projects in this space to work together and come up with common solutions, and agree on design patterns to implement in a decentralised system. (The paradox!) This would also have the added benefit that users new to the decentralised world will only have to learn few new design patterns to participate in these projects.&lt;/p&gt;
&lt;h2 id=&#34;looking-for-collaborators&#34;&gt;Looking for collaborators!&lt;/h2&gt;
&lt;p&gt;Have you been thinking about similar problems in the past? We’re looking for collaborators to create UX/UI elements for decentralized systems. Write us at &lt;a href=&#34;mailto:contact@superbloom.design&#34;&gt;contact@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Are you working on a decentralization project? Get in touch &amp;ndash; we’d love to speak to you about your needs and challenges for design and usability issues.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Design Under Pressure Video (Molly Wilson, Design Thinking Barcamp 2020)</title>
      <link>https://superbloom.design/learning/resources/video-design-under-pressure-04-2020/</link>
      <pubDate>Sat, 27 Apr 2019 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/video-design-under-pressure-04-2020/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Design Challenges in Decentralization</title>
      <link>https://superbloom.design/learning/blog/decentral-patterns/</link>
      <pubDate>Fri, 12 Apr 2019 14:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/decentral-patterns/</guid>
      <description>&lt;p&gt;In working with decentralization projects funded by the Prototype Fund, I&amp;rsquo;ve been thinking more about overall design patterns for decentralized systems. By &amp;ldquo;decentralized systems&amp;rdquo;, I mean protocols, apps, and services that are non-centralized&amp;ndash; including both federated networks, e.g. &lt;a href=&#34;https://airtable.com/tblguwlssa8xEDOLj/viwDC90VUCwKo01gD/recdiyiRMKxV0mrsw&#34;&gt;Mastodon&lt;/a&gt;, and peer to peer networks, e.g. &lt;a href=&#34;https://github.com/beakerbrowser/fritter/blob/master/README.md&#34;&gt;Fritter&lt;/a&gt;&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;. By “design patterns”, I mean recurring concepts we see in interfaces, workflows, and writing. For example, Projects by IF has a catalogue of patterns on &lt;a href=&#34;https://catalogue.projectsbyif.com/&#34;&gt;Data Permissions&lt;/a&gt; that collects many design concepts related to privacy.&lt;/p&gt;
&lt;p&gt;In looking at the decentralized space, the big question is what about our existing mental models as well as existing design patterns changes. For example, the pattern of account authentication (the trio of &amp;ldquo;login&amp;rdquo;/&amp;ldquo;signup&amp;rdquo;/&amp;ldquo;password reset&amp;rdquo;) is almost everywhere in centralized and decentralized tools. But in a decentralized system, authentication can work differently — it’s possible that the service you are connecting to doesn’t have your account information to complete the authentication. How do we communicate that difference consistently? Do users need to know that a system has decentralized technology under the hood? And when it comes to the interfaces we build: what new patterns can we develop to make decentralized systems easier to understand? Are there existing patterns that work well? With so many new decentralized tools emerging lately, the technology is (often) new, non-mainstream, and sometimes counterintuitive for experienced users of the centralized web.&lt;/p&gt;
&lt;p&gt;In trying to tackle some of these challenges across the board, I’ve started compiling some emerging themes in decentralized systems design. I will give four areas as examples.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Explanation and terminology&lt;/strong&gt;
How do you explain the difference between centralized and decentralized systems? What do users expect, what should be communicated without overwhelming people? What kinds of metaphors can we use to talk about this technology?&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Onboarding to Federation&lt;/strong&gt;
When onboarding new users to a federated system, what do they need to know about the federation? Does the system need them to choose which community to join? If so, what are the factors that should influence such a decision? What happens when they want to move from one community to another?&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Privacy/Discoverability&lt;/strong&gt;
There is a known trade-off between privacy and discoverability in p2p contexts&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;. What choices does that present to the user experience? How do you communicate unusual privacy properties such as exposing people’s IPs? What settings should be allowed? On the other end of that spectrum: what UX options are there when there is no look-up table for privacy reasons?&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Identity Management&lt;/strong&gt;
Without a central authority in place, it can be hard to manage identities across different communities, or encryption keys across different devices. What are sensible UX flows that protect the user’s security without adding to their cognitive load? And how can our digital identity be framed differently to match the constraints and possibilities in decentralized contexts?&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h4 id=&#34;whats-next&#34;&gt;What’s next?&lt;/h4&gt;
&lt;p&gt;Many of these issues are sector-wide. Some of them require a joint effort from different decentralization projects to solve. And others present a huge and exciting playground for people interested in designing a totally different digital space. For now, I’m researching and compiling the patterns I see. Watch this space!&lt;/p&gt;
&lt;br&gt;
&lt;h4 id=&#34;acknowledgments&#34;&gt;Acknowledgments&lt;/h4&gt;
&lt;p&gt;Thanks to everyone at #35C3 who pitched in, esp. Jan from Nextcloud, Ben from Matrix, Roel from XMPP, Elio from Ura Design, Ksenia from Delta Chat, Cade from Tactical Tech.&lt;/p&gt;
&lt;div class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;
&lt;hr&gt;
&lt;ol&gt;
&lt;li id=&#34;fn:1&#34;&gt;
&lt;p&gt;My definitions are largely based on &lt;a href=&#34;https://medium.com/@VitalikButerin/the-meaning-of-decentralization-a0c92b76a274&#34;&gt;this article&lt;/a&gt;, which also introduces the distinction between technical, political, and logical decentralization. I will mostly talk about technical decentralization, and specify when I mean political or logical decentralization.&amp;#160;&lt;a href=&#34;#fnref:1&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li id=&#34;fn:2&#34;&gt;
&lt;p&gt;See the &lt;a href=&#34;https://github.com/dat-ecosystem-archive/whitepaper/blob/master/dat-paper.pdf&#34;&gt;dat whitepaper&lt;/a&gt; for an excellent description of the trade-off.&amp;#160;&lt;a href=&#34;#fnref:2&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>Underexposed: Residency Pilot Recap</title>
      <link>https://superbloom.design/learning/blog/underexposed-2019-recap/</link>
      <pubDate>Sun, 31 Mar 2019 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/underexposed-2019-recap/</guid>
      <description>&lt;p&gt;Building responsible user experience (UX) into the world’s technology is easier said than done. At Simply Secure, we believe that this goes beyond the work itself, it’s also about supporting the community of practitioners trying to build more responsible technology. Starting with a dedication to privacy, security, transparency, and ethics, we engage user experience designers, researchers, and developers to hone their skills through workshops, mentorship and coaching.&lt;/p&gt;
&lt;h3 id=&#34;why-pilot-a-residency&#34;&gt;Why pilot a residency?&lt;/h3&gt;
&lt;p&gt;For the last four years, we have held convenings as part of our program, Underexposed, which have created space to hold conversations on the challenges of technology and design, with topics ranging from privacy and security to transparency and ethics. Although the convening model can foster valuable new ideas, this year, we wanted to experiment with our model and instead try something that would provide more time and space for practitioners, while still creating the opportunity for a dynamic and diverse collaboration. With this in mind, we decided to pilot a &lt;strong&gt;residency&lt;/strong&gt; model. A residency, would allow us to pilot working with a small group, for a longer period of time, and create a structure to allow them to work collaboratively and have access to mentors and experts for support, advice and feedback. We envision the residency as a replicable model that can create a supportive environment and structure needed to work on these hard problems.&lt;/p&gt;
&lt;p&gt;In our community, one of the challenges we have identified is that many projects don’t have a team member who focuses on the user experience at all; or if they do have someone whose focus is design or user experience, that person tends to work as a team of one on many different projects or needs for a given project. For the fellows, the goal was to provide the unique opportunity to get a full week to focus on one of their projects, to have the support of the other fellows, mentors, and Simply Secure staff, and to develop a community to allow that support to extend beyond the residency. Additionally, we hoped to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Support building user-centered design practices into key projects in the community.&lt;/li&gt;
&lt;li&gt;Provide education and resources for designers and developers on how to build tools that support and protect users’ security and privacy.&lt;/li&gt;
&lt;li&gt;Connect designers and developers with users who can contribute time and resources towards testing, giving feedback, and help with co-designing.&lt;/li&gt;
&lt;li&gt;Raise visibility of the fellows’ work.&lt;/li&gt;
&lt;li&gt;Help leaders in the space form peer-support networks.&lt;/li&gt;
&lt;li&gt;Share the learnings from the model itself.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;underexposed-2019&#34;&gt;Underexposed 2019&lt;/h3&gt;
&lt;p&gt;For the pilot in January 2019, we hosted &lt;a href=&#34;https://simplysecure.org/who-we-are/#underexposed-fellows-2019&#34;&gt;11 fellows&lt;/a&gt; for a week-long residency in Berlin, Germany. All of the fellows applied through our &lt;a href=&#34;https://superbloom.design/underexposed/&#34;&gt;open call&lt;/a&gt;, which invited practitioners in the space to propose projects in the areas of ethical technology, responsible AI, civic technology, and internet freedom. In the 3-week application period, we received 52 applications, representing 12 countries and 8 regions.&lt;/p&gt;
&lt;p&gt;During the residency week, fellows had time for user research, independent work, lectures, critical discussions, and design critiques. We invited leaders in the space to facilitate sessions on a range of topics and hold time to work one-on-one with fellows on their projects. The week culminated in a public event at the Mozilla Berlin office with over 70 people in attendance, where fellows presented their projects, the progress they made during the week, and their plans for next steps with their work.&lt;/p&gt;
&lt;p&gt;Overall, based on feedback from the fellows and mentors, the residency model seems to have been successful in providing them a supportive environment to make progress on their projects or pursue new ideas that came from the activities of the residency week. In the months following the residency, the cohort of fellows are still collaborating with each other and the mentors remotely — chatting about design challenges, sharing ideas, discussing opportunities to reconnect or collaborate in the future. Going forward, we are thinking about how to expand on the pilot to host more residencies and prototype different aspects of the residency model, e.g. length of time or diversity of the cohort projects.
Interested in exploring more?&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://simplysecure.org/who-we-are/#underexposed-fellows-2019&#34;&gt;Read about the fellows and their work more&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Read &lt;a href=&#34;https://superbloom.design/learning/blog/underexposed-reflection-dark-crystal&#34;&gt;Dan Hassan’s post&lt;/a&gt; about takeaways for Dark Crystal around Trust and User Experience.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://ura.design/en/blog/underexposed-2019/&#34;&gt;Ura Design’s Elio and Anxhelo&lt;/a&gt; reflected on their experience.&lt;/li&gt;
&lt;li&gt;Watch some of the &lt;a href=&#34;https://vimeo.com/album/5846228&#34;&gt;videos&lt;/a&gt; of the final presentations!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Thank you!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Underexposed 2019 would not have been possible without our financial and in-kind support from a number of funders and community organizations. Underexposed 2019 was supported financially by the &lt;a href=&#34;https://web.archive.org/web/20210116213737/https://www.opentech.fund/labs/community-lab/&#34;&gt;Open Technology Fund Community Lab&lt;/a&gt;, &lt;a href=&#34;https://www.fordfoundation.org/&#34;&gt;Ford Foundation&lt;/a&gt;, &lt;a href=&#34;https://www.internetsociety.org/&#34;&gt;Internet Society&lt;/a&gt;, and &lt;a href=&#34;https://www.getkeepsafe.com/&#34;&gt;KeepSafe&lt;/a&gt;. Wikimedia Germany donated their community space, WikiBär, for the full week to the program, &lt;a href=&#34;https://www.mozilla.org/en-US/contact/spaces/berlin/&#34;&gt;Mozilla Berlin&lt;/a&gt; hosted for the public event on Friday evening, and &lt;a href=&#34;https://www.stickermule.com/&#34;&gt;StickerMule&lt;/a&gt; provided stickers. Some fellows were also able to leverage existing support from Mozilla Foundation and Freedom of the Press Foundation to enable their participation. Thank you as well to volunteer Emma Callahan for her support throughout the week, and all of our mentors: Nasma Ahmed (&lt;a href=&#34;https://makeway.org/project/digital-justice-lab/&#34;&gt;Digital Justice Lab&lt;/a&gt;), &lt;a href=&#34;https://blog.vincentahrend.com/&#34;&gt;Vincent Ahrend&lt;/a&gt;, &lt;a href=&#34;https://shiba.computer/&#34;&gt;Cade Diehm&lt;/a&gt; (Tactical Tech), &lt;a href=&#34;https://www.accessnow.org/profile/sage-cheng/&#34;&gt;Sage Cheng&lt;/a&gt; (Access Now), Elio Qoshi &amp;amp; Anxhelo Lushka (&lt;a href=&#34;https://ura.design/&#34;&gt;Ura Design&lt;/a&gt;), and &lt;a href=&#34;https://github.com/ei8fdb&#34;&gt;Bernard Tyers&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Underexposed Reflection: Dark Crystal</title>
      <link>https://superbloom.design/learning/blog/underexposed-reflection-dark-crystal/</link>
      <pubDate>Tue, 26 Mar 2019 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/underexposed-reflection-dark-crystal/</guid>
      <description>&lt;p&gt;&lt;em&gt;This guest post comes from a Dark Crystal contributor; one of the Underexposed 2019 Fellows.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;intro--trust&#34;&gt;Intro ~ Trust&lt;/h3&gt;
&lt;p&gt;This is the first in a series of reflections about Simply Secure&amp;rsquo;s &lt;a href=&#34;https://superbloom.design/underexposed/&#34;&gt;Underexposed 2019 Residency&lt;/a&gt;. When thinking about how to frame this reflection an emergent thought was to focus on some of the themes which arose throughout the experience. Trust was one of these themes.&lt;/p&gt;
&lt;h3 id=&#34;what-is-darkcrystalpw--how-does-it-relate-to-trust&#34;&gt;What is darkcrystal.pw &amp;amp; how does it relate to Trust?&lt;/h3&gt;
&lt;p&gt;&lt;a href=&#34;https://darkcrystal.pw&#34;&gt;Dark Crystal&lt;/a&gt; is a pattern of secure data management fusing an established cryptographic algorithm with new peer-to-peer technologies. A proof of concept application has been built on top of the offline-first &lt;a href=&#34;https://scuttlebutt.nz/&#34;&gt;scuttlebutt protocol&lt;/a&gt;. Said another way Dark Crystal is an app which supports people to back up their secrets using the trust in their social fabric. The ethical enquiry, the seed, at the heart of the project was exploring how to make darkcrystal more inclusive, so that more people can &lt;a href=&#34;https://issuu.com/instituteofnetworkcultures/docs/moneylabreader2overcomingthehype&#34;&gt;participate as peers&lt;/a&gt; in the new &lt;a href=&#34;http://distributedweb.care/posts/racial-justice/&#34;&gt;decentralised web&lt;/a&gt; and attempting to extend who gets to benefit from privacy preserving/enhancing technologies.&lt;/p&gt;
&lt;p&gt;This is important because the price of entry into the P2P web is secure management of your &lt;a href=&#34;https://en.wikipedia.org/wiki/Public-key_cryptography&#34;&gt;private keys&lt;/a&gt;, be it &lt;a href=&#34;https://en.wikipedia.org/wiki/Pretty_Good_Privacy&#34;&gt;PGP&lt;/a&gt;, &lt;a href=&#34;https://bitcoin.org&#34;&gt;bitcoin&lt;/a&gt;, &lt;a href=&#34;https://briarproject.org/&#34;&gt;Briar&lt;/a&gt;, &lt;a href=&#34;https://beakerbrowser.com/&#34;&gt;Beaker Browser&lt;/a&gt; (built on &lt;a href=&#34;https://datproject.org/&#34;&gt;DAT&lt;/a&gt;) or &lt;a href=&#34;https://www.scuttlebutt.nz/&#34;&gt;scuttlebutt&lt;/a&gt;. If the new distributed web is to achieve its hopes of becoming a foundational tool in people&amp;rsquo;s digital lives and society&amp;rsquo;s civic fabric then we need to reduce the costs of this key data loss. Imagine not only losing your family photos during a hard disk failure but your life-savings and your digital identity - forever. Figuring out this key problem is an open design problem which has yet to be cracked in a meaningful way.&lt;/p&gt;
&lt;h3 id=&#34;along-which-lines-of-trust-did-darkcrystalpw-hear-about-the-residency&#34;&gt;Along which lines of Trust did darkcrystal.pw hear about the residency?&lt;/h3&gt;
&lt;p&gt;The team behind Dark Crystal have been using the p2p social media protocol scuttlebutt since Jan 2018. We have been organising there in the open since before we spiralled around to private key management as our focus. At that time we were primarily communicating in the #mmt channel (which is short for magic money tree, the handle we&amp;rsquo;d been referring to the proto-project) on scuttlebutt. Without diving too deep into scuttlebutt it&amp;rsquo;s worth noting that everything outside of private messages are globally viewable[1] (if you want to learn more about how the protocol works you can look at this excellent &lt;a href=&#34;https://ssbc.github.io/scuttlebutt-protocol-guide/&#34;&gt;protocol guide&lt;/a&gt;). This attribute of the system led to our critic-in-residence expressing that organising on SSB had the quality of setting up your office in the middle of a building site, with no walls. Over the course of 2018 the #mmt channel became one of the most subscribed to channels in the scuttleverse. This radical openness of communications, processes and research was experienced differentially. For some it was an overwhelming firehose and for others it was a compost of trust in which different seeds could be planted.&lt;/p&gt;
&lt;p&gt;All this is a long way of saying that cameralibre from scuttlebutt was at at the &lt;a href=&#34;https://opensourcedesign.net/summit/&#34;&gt;Open Source Design summit&lt;/a&gt; in Tirana, Albania met &lt;a href=&#34;https://superbloom.design/about/people/eileen&#34;&gt;Eileen&lt;/a&gt; from Simply Secure who told him about the Underexposed residency and cameralibre trusted the Dark Crystal team enough to pass on the recommendation to apply.&lt;/p&gt;
&lt;h3 id=&#34;simply-secure-built-trust-with-its-team-even-before-we-arrived-in-berlin&#34;&gt;Simply Secure built Trust with its Team even before We arrived in Berlin&lt;/h3&gt;
&lt;p&gt;After applying and being accepted onto the residency (yay!) the Simply Secure team built trust with our team by accommodating some of our constraints. We&amp;rsquo;re six people spread over 4 countries in two continents. Two thirds of us have kids under 2. The folx at Simply Secure enabled us to access the residency by offering two members of the team to join so as to allow flexibility around childcare. This introduction to the Simply Secure team established that the concept of design extended well beyond the boundaries of the digital and supported the call for the residency &lt;strong&gt;in action&lt;/strong&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Responsible technology is about helping. It’s about meeting its users’ needs and making their lives better. It depends on design, co-design, research, and user engagement. It depends on an ethical orientation and values-driven decision making. And these things are only possible in the context of a community that provides insight, feedback, and accountability. &lt;a href=&#34;&#34;&gt;/underexposed/&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&#34;establishing-trust-at-the-residency&#34;&gt;Establishing Trust at the Residency&lt;/h3&gt;
&lt;p&gt;The opening presentation by Simply Secure laid out some of the ground rules such as Chatham House Rules, anti-harassment and code of conduct rules and how they would be enforced and the vibe care of &amp;ldquo;if something takes your mind out of the room, then take your body out of the room also&amp;rdquo;. Food was arranged and most of the other logistics such as expenses were set up. The framework had been established.&lt;/p&gt;
&lt;h3 id=&#34;examples-of-projects-working-on-trust&#34;&gt;Examples of projects working on Trust&lt;/h3&gt;
&lt;p&gt;Like us there were a number of other projects which were working on themes in and around the neighbourhood of trust. From getting people to back up their secrets during the set up phase for secure cloud computing, to establishing trusted entropy of keys using dice, to 2FA and password managers to resources around PGP and also HTTPS everywhere.&lt;/p&gt;
&lt;p&gt;One of the interesting themes which emerged was the &lt;strong&gt;distrust and scepticism&lt;/strong&gt; which can arise &lt;strong&gt;when introducing new patterns and approaches&lt;/strong&gt; to people. This is particularly exacerbated &lt;strong&gt;when there is an existing way of doing things&lt;/strong&gt; (resetting passwords through your email for example) &lt;strong&gt;even if they are less secure&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;What is clear is that whether there are existing insecure ways of doing things or if there are no existing prior art, patterns or approaches is that many of the design challenges are common in and around these neighbourhoods. Within the P2P space projects are either admitting that private key management are not at the top of their list and that someone else will do it or there are teams all trying to figure this out in isolation.&lt;/p&gt;
&lt;p&gt;The value of a residency such as Underexposed is that those of us working in industry or within the open source realm of distributed technologies we rarely get these opportunities to network and collectively put our heads together. This is the first time that Simply Secure have run a residency over a week and were explicit in their communications that this format was an experiment. Having attended our team feels that they are carving out what feels like important common ground to afford participants connections which can persist over distance. From the perspective of an open source distributed team working with open source distributed technologies this pattern feels like a productive one from which we have already derived great value.&lt;/p&gt;
&lt;h3 id=&#34;selected-highlights&#34;&gt;Selected Highlights&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Meeting the rest of the fellows. When I arrived in the Slack group my gut was like: &amp;ldquo;Oooooh this is where you all are!&amp;rdquo;&lt;/li&gt;
&lt;li&gt;Early in the life of Dark Crystal Prof. George Danezis (one of our &lt;a href=&#34;https://darkcrystal.pw/about&#34;&gt;advisors&lt;/a&gt;) gave us &lt;a href=&#34;https://doi.org/10.1145/1572532.1572581&#34;&gt;a paper&lt;/a&gt; which he described as the earliest seminal work in the space. I was speaking with one of the fellows and due to brain fog was struggling to remember the name of the paper. So I went around ham-handedly describing the contents of the paper. The fellow in question had a big smile on their face by the end of my attempt and revealed that they had written that paper. We&amp;rsquo;ll hopefully get continue the dialogue in an episode of Dark Crystal Diaries (the first episode was with another of our advisors &lt;a href=&#34;&#34;&gt;Cory Doctorow&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;Meeting another Ethereum Foundation Grant recipient working in the same problem domain&lt;/li&gt;
&lt;li&gt;Having sessions with folx involved in research around &lt;a href=&#34;https://ourdataourselves.tacticaltech.org/posts/30-on-weaponised-design/&#34;&gt;Weaponized Design&lt;/a&gt;, who have helped with design within Freedom of the Press Foundation (which has their own offering of &lt;a href=&#34;https://github.com/freedomofpress/sunder&#34;&gt;Sunder&lt;/a&gt;) and Briar (we&amp;rsquo;d actually met around a pub table some 5 or 6 years prior for some early user testing).&lt;/li&gt;
&lt;li&gt;We had some very impactful sessions with folx from &lt;a href=&#34;https://ura.design&#34;&gt;Ura Design&lt;/a&gt; in detangling some of the design interface complexity with social backup mechanisms. We&amp;rsquo;ve actually been able to apply to &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Open Technology Fund&amp;rsquo;s Usability Lab&lt;/a&gt; to potentially be able to continue this work.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;conclusion&#34;&gt;Conclusion&lt;/h3&gt;
&lt;p&gt;It&amp;rsquo;s only a couple of weeks since the residency and our team is still riding the ripples. The connections made have been invaluable and we have high hopes that the seeds sown could contribute towards advancing the art of secure data management in the field of distributed systems. Proponents of the distributed web often speak about putting the power of computer networks back into the hands of the people and if we&amp;rsquo;re going to expand the stakeholders who have a seat at the table as these technologies mature and the cultures and processes within which they come up, then these common problems are best served by people working together. I personally feel that this residency and other efforts in the same spirit lay the common soil in which the mycelial human connections can be woven to strengthen the social fabric being interwoven with these new cypher driven computing patterns and networks.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;[1] global in the sense anyone who has downloaded a client could see this data or through portals which expose the content from cypherspace to www&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>New: 3-minute video skill shares we call &#39;Design Spots&#39; </title>
      <link>https://superbloom.design/learning/blog/intro-design-spots/</link>
      <pubDate>Tue, 05 Mar 2019 14:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/intro-design-spots/</guid>
      <description>&lt;p&gt;Simply Secure is a non-profit, and our mission is educational. We support practitioners in design and technology by running workshops, creating open resources, and gathering a community around ux design and trustworthy technology. Over the past five years, we’ve been exploring different ways to share our knowledge with the community. Today we’re excited to present our next iteration of knowledge and skill sharing: short videos that answer specific community questions. We call them &lt;em&gt;Design Spots&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;We conceived Design Spots out of two separate thoughts. First, we wanted to offer another medium of communication — specifically one that would be accessible to folks asynchronously, so videos seemed like a sensible thing to try out. Second, we wanted to address specific needs in the community, i.e. questions we’ve heard from you. Some of that happens in our Slack, in person at coachings or workshops, but with these videos, we can open up our answers to a wider audience and hopefully benefit more people.&lt;/p&gt;
&lt;p&gt;So without further ado, here are our first five videos!&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/tags/design-spots/&#34; class=&#34;button button--secondary read-more&#34; style=&#34;text-decoration: none;&#34;&gt;Design Spots&lt;/a&gt;&lt;/p&gt;
&lt;!-- \* \[Getting Started with Human-Centered Design](/learning/blog/design-spot-getting-started)
\* \[Tool Feedback](/learning/blog/design-spot-tool-feedback)
\* \[Research With High-Risk Participants](/learning/resources/design-spot-high-risk-research)
\* \[Designing For Security](/learning/blog/design-spot-design-security)
* \[Onboarding New Users](/learning/blog/design-spot-onboarding) --&gt;
&lt;p&gt;Get in touch if you have ideas for more topics, or questions you’d like to see us answer!&lt;/p&gt;
&lt;p&gt;We’ve started holding open office hours monthly, the first Wednesday of the month at 10AM Eastern / 4PM CET. We also host a [community slack](mailto:slack@superbloom.design?subject=I’d like to join the Simply Secure Slack), where you are welcome to join, connect with others, and get support from the community as a whole.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Human-centered Design, Where to Start?</title>
      <link>https://superbloom.design/learning/resources/design-spot-getting-started/</link>
      <pubDate>Tue, 05 Mar 2019 12:05:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/design-spot-getting-started/</guid>
      <description>
      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/321251611?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;h3 id=&#34;resources&#34;&gt;Resources&lt;/h3&gt;
&lt;h4 id=&#34;design-mindset&#34;&gt;Design Mindset&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Books&lt;/em&gt;
&lt;a href=&#34;https://mitpress.mit.edu/books/design-everyday-things&#34;&gt;The Design of Everyday Things&lt;/a&gt; (Don Norman, 1998)
Books by &lt;a href=&#34;http://www.kerismith.com/&#34;&gt;Keri Smith&lt;/a&gt;, including &lt;a href=&#34;https://www.amazon.com/How-Be-Explorer-World-Portable/dp/0399534601/&#34;&gt;“How to be an Explorer of the World”&lt;/a&gt;
&lt;a href=&#34;https://www.abebooks.com/9780811847759/Thoughtless-Acts-Observations-Intuitive-Design-0811847756/plp&#34;&gt;Thoughtless Acts?&lt;/a&gt; (Jane Fulton Suri, 2005)
&lt;a href=&#34;https://mitpress.mit.edu/books/mismatch&#34;&gt;Mismatch: How Inclusion Shapes Design&lt;/a&gt; (Kat Holmes, 2018)&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Podcasts&lt;/em&gt;
&lt;a href=&#34;https://99percentinvisible.org/&#34;&gt;99% Invisible&lt;/a&gt;
&lt;a href=&#34;https://itunes.apple.com/us/podcast/design-matters-with-debbie-millman/id328074695?mt=2&#34;&gt;Design Matters&lt;/a&gt;
&lt;a href=&#34;https://xd.adobe.com/ideas/perspectives/wireframe-podcast/&#34;&gt;Wireframe&lt;/a&gt;
&lt;a href=&#34;https://uxdesign.cc/my-top-5-ux-ui-podcasts-3011f51017c9&#34;&gt;More Suggestions from UX Collective&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Websites&lt;/em&gt;
&lt;a href=&#34;https://www.cs.umd.edu/users/ben/goldenrules.html&#34;&gt;The 8 Golden Rules of Usability&lt;/a&gt;
&lt;a href=&#34;https://www.oreilly.com/ideas/ux-for-beginners-key-ideas&#34;&gt;UX for Beginners&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;design-methods&#34;&gt;Design Methods&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Books&lt;/em&gt;
&lt;a href=&#34;http://www.101designmethods.com/&#34;&gt;101 Design Methods&lt;/a&gt;
&lt;a href=&#34;https://www.amazon.com/Universal-Methods-Design-Innovative-Effective/dp/1592537561&#34;&gt;Universal Methods of Design&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Websites&lt;/em&gt;
&lt;a href=&#34;https://www.designkit.org/methods.html&#34;&gt;Design Kit&lt;/a&gt; by ideo.org
&lt;a href=&#34;https://www.usability.gov/how-to-and-tools/methods/index.html&#34;&gt;Design methods&lt;/a&gt; by usability.gov
&lt;a href=&#34;http://www.universalusability.com/resources.html&#34;&gt;Universal Usability&lt;/a&gt;
Simply Secure&amp;rsquo;s &lt;a href=&#34;https://superbloom.design/learning/blog/self-starter&#34;&gt;&amp;lsquo;User Experience Self-Education Resources&amp;rsquo;&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;with&lt;/strong&gt; Molly Wilson, Emma Callahan, Ana Sol Alvarez
&lt;strong&gt;Produced by&lt;/strong&gt; Eileen Wagner, Ben Mergelsberg, Molly Wilson
&lt;strong&gt;Directed by&lt;/strong&gt; Ben Mergelsberg
&lt;strong&gt;Camera assistent:&lt;/strong&gt; Luciana Damiao
&lt;strong&gt;Art:&lt;/strong&gt; Molly Wilson
&lt;strong&gt;Music:&lt;/strong&gt; &amp;ldquo;Downtown&amp;rdquo; by bensound.com
&lt;strong&gt;Filmed at&lt;/strong&gt; &lt;a href=&#34;https://www.stattlab.net&#34;&gt;Stattlab&lt;/a&gt; and &lt;a href=&#34;http://wrangelfilm.com&#34;&gt;Wrangelfilm&lt;/a&gt;
&lt;strong&gt;Supported by&lt;/strong&gt; &lt;a href=&#34;https://www.opentech.fund&#34;&gt;Open Technology Fund&lt;/a&gt;
&lt;strong&gt;Special thanks to&lt;/strong&gt; Scout Brody, Maya Wagoner, Brett Gaylor
&lt;strong&gt;Simply Secure CC-BY&lt;/strong&gt; (Georgia Bullen, Ame Elliott, Eileen Wagner, Molly Wilson)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Quick Tool Feedback</title>
      <link>https://superbloom.design/learning/resources/design-spot-tool-feedback/</link>
      <pubDate>Tue, 05 Mar 2019 12:04:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/design-spot-tool-feedback/</guid>
      <description>
      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/321474068?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;br&gt;
&lt;h3 id=&#34;resources&#34;&gt;Resources&lt;/h3&gt;
&lt;h4 id=&#34;principles-and-background&#34;&gt;Principles and Background&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Books&lt;/em&gt;
&lt;a href=&#34;https://www.amazon.com/User-Experience-Team-One-Research-ebook/dp/B00DUITE5Q/&#34;&gt;The User Experience Team of One&lt;/a&gt; (Leah Buley, 2013)
&lt;a href=&#34;https://www.amazon.com/Moderators-Survival-Guide-Handling-Situations-ebook/dp/B00FOVX5O8/&#34;&gt;The Moderator’s Survival Guide&lt;/a&gt; (Donna Tedesco, Fiona Tranquada, 2013)
&lt;a href=&#34;https://www.amazon.com/Observing-User-Experience-Practitioners-Research/dp/1558609237/&#34;&gt;Observing the User Experience&lt;/a&gt; (Mike Kuniavsky, 2003)&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Articles&lt;/em&gt;
&lt;a href=&#34;https://uxdesign.cc/asking-the-right-questions-on-user-research-interviews-and-testing-427261742a67&#34;&gt;How to ask the right questions&lt;/a&gt; (Fabricio Teixera)
&lt;a href=&#34;https://www.linkedin.com/pulse/body-language-user-research-nikki-anderson-ma/&#34;&gt;Body Language and User Interviewing&lt;/a&gt; (Nikki Anderson)
&lt;a href=&#34;https://medium.com/@DesignMap.com/being-the-crystal-goblet-706b6c3522a&#34;&gt;Being the Crystal Goblet&lt;/a&gt; (Audrey Crane)
Georgia&amp;rsquo;s talk on &lt;a href=&#34;http://georgiamoon.github.io/ux-bugs-talk/&#34;&gt;UX bugs&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;tools-and-templates&#34;&gt;Tools and Templates&lt;/h4&gt;
&lt;p&gt;Molly’s &lt;a href=&#34;https://superbloom.design/learning/blog/user-testing-cheatsheet&#34;&gt;user testing cheat sheet&lt;/a&gt;
Simply Secure&amp;rsquo;s &lt;a href=&#34;https://superbloom.design/learning/blog/feedback-gathering-guide&#34;&gt;feedback gathering guide&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;with&lt;/strong&gt; Ame Elliott, Marie Kochsiek, Vincent Ahrend
&lt;strong&gt;Produced by&lt;/strong&gt; Eileen Wagner, Ben Mergelsberg, Molly Wilson
&lt;strong&gt;Directed by&lt;/strong&gt; Ben Mergelsberg
&lt;strong&gt;Camera assistent:&lt;/strong&gt; Luciana Damiao
&lt;strong&gt;Art:&lt;/strong&gt; Molly Wilson
&lt;strong&gt;Music:&lt;/strong&gt; &amp;ldquo;Downtown&amp;rdquo; by bensound.com
&lt;strong&gt;Filmed at&lt;/strong&gt; &lt;a href=&#34;https://www.stattlab.net&#34;&gt;Stattlab&lt;/a&gt; and &lt;a href=&#34;http://wrangelfilm.com&#34;&gt;Wrangelfilm&lt;/a&gt;
&lt;strong&gt;Supported by&lt;/strong&gt; &lt;a href=&#34;https://www.opentech.fund&#34;&gt;Open Technology Fund&lt;/a&gt;
&lt;strong&gt;Special thanks to&lt;/strong&gt; Scout Brody, Maya Wagoner, Brett Gaylor
&lt;strong&gt;Simply Secure CC-BY&lt;/strong&gt; (Georgia Bullen, Ame Elliott, Eileen Wagner, Molly Wilson)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>High-Risk User Research</title>
      <link>https://superbloom.design/learning/resources/design-spot-high-risk-research/</link>
      <pubDate>Tue, 05 Mar 2019 12:03:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/design-spot-high-risk-research/</guid>
      <description>&lt;p&gt;topics:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;user-research&lt;/li&gt;
&lt;/ul&gt;

      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/321474097?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;br&gt;
&lt;h3 id=&#34;resources&#34;&gt;Resources&lt;/h3&gt;
&lt;h4 id=&#34;background-and-principles&#34;&gt;Background and Principles&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Books and Academic Publications&lt;/em&gt;
&lt;a href=&#34;https://www.ideo.com/journal/the-little-book-of-design-research-ethics&#34;&gt;Little Book of Design Research Ethics&lt;/a&gt; (IDEO, 2016)
Forum Qualitative Sozialforschung (FQS) Quarterly, &lt;a href=&#34;http://www.qualitative-research.net/index.php/fqs/issue/view/62&#34;&gt;Special Issue on Research Ethics in Qualitative Research&lt;/a&gt; (2018, 19:3)&lt;/p&gt;
&lt;p&gt;&lt;em&gt;News&lt;/em&gt;
&lt;a href=&#34;https://www.theguardian.com/technology/2014/jun/30/facebook-emotion-study-breached-ethical-guidelines-researchers-say&#34;&gt;Arthur, Charles. Facebook emotion study breached ethical guidelines, researchers say.&lt;/a&gt; The Guardian, 30 June 2014.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Websites&lt;/em&gt;
&lt;a href=&#34;https://www.interaction-design.org/literature/article/conducting-ethical-user-research&#34;&gt;Conducting Ethical User Research&lt;/a&gt; (Ditte Mortensen)
&lt;a href=&#34;https://uxpa.org/uxpa-code-of-professional-conduct/&#34;&gt;UXPA Code of Professional Conduct&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;tools-and-methods&#34;&gt;Tools and Methods&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Websites&lt;/em&gt;
&lt;a href=&#34;https://responsibledata.io/&#34;&gt;Responsible Data&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Forms and Templates&lt;/em&gt;
UX Checklist &lt;a href=&#34;https://github.com/leeange/DSPPUX-Checklist&#34;&gt;GitHub&lt;/a&gt;/&lt;a href=&#34;https://docs.google.com/presentation/d/1snDclSxKsyfUlqIH7HBWv9rdT6gIRPHqAuhaUjFZCoU/edit?usp=sharing&#34;&gt;Google Slide&lt;/a&gt;
Simply Secure&amp;rsquo;s &lt;a href=&#34;https://superbloom.design/learning/blog/participant-rights&#34;&gt;participant bill of rights&lt;/a&gt;
Simply Secure&amp;rsquo;s &lt;a href=&#34;https://superbloom.design/learning/blog/model-release&#34;&gt;participant release form&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;with&lt;/strong&gt; Molly Wilson, Cade Diehm
&lt;strong&gt;Produced by&lt;/strong&gt; Eileen Wagner, Ben Mergelsberg, Molly Wilson
&lt;strong&gt;Directed by&lt;/strong&gt; Ben Mergelsberg
&lt;strong&gt;Camera assistent:&lt;/strong&gt; Luciana Damiao
&lt;strong&gt;Art:&lt;/strong&gt; Molly Wilson
&lt;strong&gt;Music:&lt;/strong&gt; &amp;ldquo;Downtown&amp;rdquo; by bensound.com
&lt;strong&gt;Filmed at&lt;/strong&gt; &lt;a href=&#34;https://www.stattlab.net&#34;&gt;Stattlab&lt;/a&gt; and &lt;a href=&#34;http://wrangelfilm.com&#34;&gt;Wrangelfilm&lt;/a&gt;
&lt;strong&gt;Supported by&lt;/strong&gt; &lt;a href=&#34;https://www.opentech.fund&#34;&gt;Open Technology Fund&lt;/a&gt;
&lt;strong&gt;Special thanks to&lt;/strong&gt; Scout Brody, Maya Wagoner, Brett Gaylor
&lt;strong&gt;Simply Secure CC-BY&lt;/strong&gt; (Georgia Bullen, Ame Elliott, Eileen Wagner, Molly Wilson)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Designing For Security</title>
      <link>https://superbloom.design/learning/resources/design-spot-design-security/</link>
      <pubDate>Tue, 05 Mar 2019 12:02:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/design-spot-design-security/</guid>
      <description>
      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/321474122?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;br&gt;
&lt;h3 id=&#34;resources&#34;&gt;Resources&lt;/h3&gt;
&lt;h4 id=&#34;principles-and-background&#34;&gt;Principles and Background&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/talking-across-divide&#34;&gt;Designing For More Than &amp;ldquo;It&amp;rsquo;s Secure&amp;rdquo;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;learn-about-contexts&#34;&gt;Learn about contexts&lt;/h4&gt;
&lt;p&gt;Simply Secure&amp;rsquo;s &lt;a href=&#34;https://superbloom.design/learning/blog/personas&#34;&gt;persona template&lt;/a&gt;
&lt;a href=&#34;https://medium.com/@gusandrews/user-personas-for-privacy-and-security-a8b35ae5a63b&#34;&gt;User Personas for Privacy and Security&lt;/a&gt; (Gus Andrews)&lt;/p&gt;
&lt;h4 id=&#34;mental-models&#34;&gt;Mental models&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://www.amazon.com/Mental-Models-Aligning-Strategy-Behavior-ebook/dp/B004VFUOQ0/&#34;&gt;Mental Models: Aligning Design Strategy with Human Behavior&lt;/a&gt; (Indi Young, 2008)
&lt;a href=&#34;https://superbloom.design/learning/blog/whatsapp-update&#34;&gt;Tradeoffs In Seamlessness&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;with&lt;/strong&gt; Eileen Wagner, Casey Callendrello
&lt;strong&gt;Produced by&lt;/strong&gt; Eileen Wagner, Ben Mergelsberg, Molly Wilson
&lt;strong&gt;Directed by&lt;/strong&gt; Ben Mergelsberg
&lt;strong&gt;Camera assistent:&lt;/strong&gt; Luciana Damiao
&lt;strong&gt;Art:&lt;/strong&gt; Molly Wilson
&lt;strong&gt;Music:&lt;/strong&gt; &amp;ldquo;Downtown&amp;rdquo; by bensound.com
&lt;strong&gt;Filmed at&lt;/strong&gt; &lt;a href=&#34;https://www.stattlab.net&#34;&gt;Stattlab&lt;/a&gt; and &lt;a href=&#34;http://wrangelfilm.com&#34;&gt;Wrangelfilm&lt;/a&gt;
&lt;strong&gt;Supported by&lt;/strong&gt; &lt;a href=&#34;https://www.opentech.fund&#34;&gt;Open Technology Fund&lt;/a&gt;
&lt;strong&gt;Special thanks to&lt;/strong&gt; Scout Brody, Maya Wagoner, Brett Gaylor
&lt;strong&gt;Simply Secure CC-BY&lt;/strong&gt; (Georgia Bullen, Ame Elliott, Eileen Wagner, Molly Wilson)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Onboarding New Users</title>
      <link>https://superbloom.design/learning/resources/design-spot-onboarding/</link>
      <pubDate>Tue, 05 Mar 2019 12:01:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/design-spot-onboarding/</guid>
      <description>
      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/321474152?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;h3 id=&#34;resources&#34;&gt;Resources&lt;/h3&gt;
&lt;h4 id=&#34;explain-your-tool&#34;&gt;Explain your tool&lt;/h4&gt;
&lt;p&gt;Simply Secure&amp;rsquo;s &lt;a href=&#34;https://github.com/simplysecure/resources/tree/master/design_tools/ValueProp-Generator&#34;&gt;value proposition generator&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;onboarding-process&#34;&gt;Onboarding process&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://lawsofux.com/&#34;&gt;Laws of UX&lt;/a&gt;
&lt;a href=&#34;http://uipatterns.io/&#34;&gt;UI Patterns&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;language-and-visuals&#34;&gt;Language and visuals&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://www.amazon.com/AWeb-Everyone-Designing-Accessible-Experiences-ebook/dp/B00HCREJZ6/&#34;&gt;A Web for Everyone: Designing Accessible Experiences&lt;/a&gt; (Sarah Horton &amp;amp; Whitney Quesenbery, 2014)
&lt;a href=&#34;https://superbloom.design/learning/blog/style-guide&#34;&gt;Why Style Guides&lt;/a&gt;
&lt;a href=&#34;http://styleguides.io/examples.html&#34;&gt;Styleguides.io&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;information-architecture&#34;&gt;Information architecture&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://www.amazon.com/Information-Architecture-Beyond-Louis-Rosenfeld/dp/1491911689/&#34;&gt;Information Architecture: For the Web and Beyond&lt;/a&gt;
&lt;a href=&#34;https://superbloom.design/learning/blog/documentation-ux&#34;&gt;Improving your Documentation IA&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;credits&#34;&gt;Credits&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;with&lt;/strong&gt; Eileen Wagner, Vincent Ahrend
&lt;strong&gt;Produced by&lt;/strong&gt; Eileen Wagner, Ben Mergelsberg, Molly Wilson
&lt;strong&gt;Directed by&lt;/strong&gt; Ben Mergelsberg
&lt;strong&gt;Camera assistent:&lt;/strong&gt; Luciana Damiao
&lt;strong&gt;Art:&lt;/strong&gt; Molly Wilson
&lt;strong&gt;Music:&lt;/strong&gt; &amp;ldquo;Downtown&amp;rdquo; by bensound.com
&lt;strong&gt;Filmed at&lt;/strong&gt; &lt;a href=&#34;https://www.stattlab.net&#34;&gt;Stattlab&lt;/a&gt; and &lt;a href=&#34;http://wrangelfilm.com&#34;&gt;Wrangelfilm&lt;/a&gt;
&lt;strong&gt;Supported by&lt;/strong&gt; &lt;a href=&#34;https://www.opentech.fund&#34;&gt;Open Technology Fund&lt;/a&gt;
&lt;strong&gt;Special thanks to&lt;/strong&gt; Scout Brody, Maya Wagoner, Brett Gaylor
&lt;strong&gt;Simply Secure CC-BY&lt;/strong&gt; (Georgia Bullen, Ame Elliott, Eileen Wagner, Molly Wilson)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Video Series: Designing For Security</title>
      <link>https://superbloom.design/learning/resources/designing-for-security/</link>
      <pubDate>Tue, 05 Mar 2019 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/designing-for-security/</guid>
      <description>&lt;p&gt;How can design help make your tool more secure? We have three places to start. From our video series, Design Spots.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Video Series: High-Risk User Research</title>
      <link>https://superbloom.design/learning/resources/high-risk-user-research/</link>
      <pubDate>Tue, 05 Mar 2019 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/high-risk-user-research/</guid>
      <description>&lt;p&gt;These are additional considerations for conducting user research involving high-risk participants. From our video series, Design Spots.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Video Series: Human-centered Design, Where to Start?</title>
      <link>https://superbloom.design/learning/resources/human-centered-design-where-to-start/</link>
      <pubDate>Tue, 05 Mar 2019 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/human-centered-design-where-to-start/</guid>
      <description>&lt;p&gt;Instead of learning methods and tools, you can start by developing a design mindset. From our video series, Design Spots.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Video Series: Onboarding New Users</title>
      <link>https://superbloom.design/learning/resources/onboarding-new-users/</link>
      <pubDate>Tue, 05 Mar 2019 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/onboarding-new-users/</guid>
      <description>&lt;p&gt;A complex tool can be hard to understand for new users. Here are four tips around designing for their specific needs. From our video series, Design Spots.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Video Series: Quick Tool Feedback</title>
      <link>https://superbloom.design/learning/resources/design-spots-video-1/</link>
      <pubDate>Tue, 05 Mar 2019 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/design-spots-video-1/</guid>
      <description>&lt;p&gt;Designing alongside your users will make your tools respond best to their needs. We&amp;rsquo;ll show you how to get instant input from your users. From our video series, Design Spots.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>How to improve the UX of your documentation</title>
      <link>https://superbloom.design/learning/blog/documentation-ux/</link>
      <pubDate>Wed, 20 Feb 2019 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/documentation-ux/</guid>
      <description>&lt;p&gt;Many projects we work with involve new, unusual or complex technologies, and it is challenging to present information about the tool that respects both beginners and experts alike. This problem is especially difficult when it comes to the documentation.&lt;/p&gt;
&lt;p&gt;Documentation serves many different needs. For first-time users, it is the place that provides guides and manuals for your initial set-up and onboarding. After successfully setting up the tool, many users will likely never return to the documentation again. If you have contributors to your tools, e.g. from developers, translators, writers, and others, it is a place people go to understand  the technical specification, tweak or extend their set-up, or potentially even develop an interoperable service. When these groups of people meet in the same place in the documentation, they might get frustrated and confused, and work around your carefully documented process to find their own solution if the documentation isn’t clear and approachable. In extreme cases, this can present a security risk, as it did with the case of &lt;a href=&#34;https://saschafahl.de/static/paper/stackoverflow2017.pdf&#34;&gt;developers copying code from Stack Overflow&lt;/a&gt; instead of reading the documentation.&lt;/p&gt;
&lt;p&gt;When you work in an environment that regularly tells people to RTFM*, it’s really important to get the documentation right. Good documentation is skimmable, up-to-date, and thoroughly tested by its audiences. What’s more, good documentation is easy to navigate, and helps people find the relevant information quickly. This is where working on the information architecture of your documentation comes in.&lt;/p&gt;
&lt;p&gt;We’ve made a quick design exercise to help you figure out who needs to know what, and what’s missing from your documentation so far.&lt;/p&gt;
&lt;div class=&#34;single-post__related&#34;&gt;
    &lt;ul&gt;
      &lt;li&gt;On post-it notes or cards, write the titles of the pieces of information about your tool you already published -- for example: a glossary, what to do if you found a bug, how to install…&lt;/li&gt;
      &lt;li&gt;Think about, and write up, three different use cases or &lt;a href=&#34;https://superbloom.design/learning/blog/personas&#34;&gt;personas&lt;/a&gt;: first-time users, general users, and power users. Arrange these cards near the user they most apply to.&lt;/li&gt;
      &lt;li&gt;Is anything missing? For each users, write what’s missing on a different color post-it.&lt;/li&gt;
      &lt;li&gt;Within the clusters for each user, what’s the natural or appropriate sequence of these cards?&lt;/li&gt;
      &lt;li&gt;Reorganize your documentation according to the cards. For first-time users: use diagrams and visuals, define terms they might not know. For power users: use action words to organize your sections, for example: &#34;set-up self-hosted version&#34;, &#34;report a bug&#34;, &#34;test the latest version&#34;.&lt;/li&gt;
    &lt;/ul&gt;
&lt;/div&gt;
&lt;p&gt;Card sorting exercises can seem simple or boring, but are an extremely effective way to help you sort your information. Sometimes the best interventions are the simplest ones!&lt;/p&gt;
&lt;p&gt;Here is an example of using card sorting to &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/documentation/Card%20Sorting%20with%20Tails.pdf&#34;&gt;simplify and organize Tails’s documentation&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;To learn more about the theory and practice behind documentation writing, we highly recommend the Write the Docs community and their &lt;a href=&#34;https://www.writethedocs.org/guide/&#34;&gt;guide for beginners&lt;/a&gt;. To learn more about card sorting, visit the tools section of &lt;a href=&#34;https://www.usability.gov/how-to-and-tools/methods/card-sorting.html&#34;&gt;usability.gov&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;*an elegant way of spelling “read the f***ing manual”&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>User Testing Cheat Sheet</title>
      <link>https://superbloom.design/learning/blog/user-testing-cheatsheet/</link>
      <pubDate>Tue, 08 Jan 2019 10:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/user-testing-cheatsheet/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;br&gt;
What do you see here?&lt;br&gt;
What can you do here?&lt;br&gt;
What do you think is going on here?&lt;br&gt;
What do you think that does?&lt;br&gt;
Why do you think that’s there?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Feelings&lt;/strong&gt;
What’s your opinion of ___ ?&lt;br&gt;
What do you think of ___ ?&lt;br&gt;
Why do you say that?&lt;br&gt;
Why?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Flow&lt;/strong&gt;&lt;br&gt;
What do you think will happen next?&lt;br&gt;
What do you want to do next?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Keeping it moving&lt;/strong&gt;&lt;br&gt;
What are you wondering?&lt;br&gt;
What are you looking for?&lt;br&gt;
Is there a particular word you’re looking for?&lt;br&gt;
What would you do to figure this out if I weren’t here?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Clarification&lt;/strong&gt;&lt;br&gt;
Are you saying that ___ ?&lt;br&gt;
I think I heard you say ____. Does that capture it?&lt;br&gt;
Is it fair to say that ___ ?&lt;br&gt;
Is it accurate that ___ ?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Wrap-up&lt;/strong&gt;&lt;br&gt;
How was that experience overall?&lt;br&gt;
Anything confusing? Anything difficult?&lt;br&gt;
Anything missing?&lt;br&gt;
How was that compared to your expectations?&lt;br&gt;
What would you change?&lt;/p&gt;
&lt;p&gt;&lt;small&gt;By Molly Wilson, 2015. Thanks to Mia O’Neill, Julie Stanford, Kim Ladin, and Jenny Mailhot.&lt;/small&gt;&lt;br&gt;
&lt;small&gt;License: Creative Commons Attribution-NonCommercial-ShareAlike.&lt;/small&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Announcing our 2019 Underexposed Design Fellows</title>
      <link>https://superbloom.design/learning/blog/underexposed-fellows/</link>
      <pubDate>Wed, 02 Jan 2019 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/underexposed-fellows/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2019/philharmonic_hu_75ec04b68b26f35c.jpg&#34; alt=&#34;photo of viewer at beach&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Happy New Year! For 2019, Simply Secure is trying something new. We iterated on our event series, &lt;a href=&#34;https://superbloom.design/underexposed&#34;&gt;Underexposed&lt;/a&gt;, and are bringing you the first Underexposed Residency in January 2019! Fellows from around the world will spend one week with the Simply Secure team focused on a project that they propose. Together, the cohort will use the residency to workshop their specific design challenge. Over the week they will have time for user research, independent work, lectures, critical discussions, design critiques and office hours with leaders in the field.&lt;/p&gt;
&lt;p&gt;We are incredibly happy to have received over 50 excellent applications, and had a hard time selecting the small cohort for our pilot programme. It is with pride and pleasure that we are announcing our first cohort of Design Fellows today. They are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Sarah Fox, Care &amp;amp; IoT&lt;/li&gt;
&lt;li&gt;Dan Hassan &amp;amp; Mu, Dark Crystal&lt;/li&gt;
&lt;li&gt;Alexander Morley, remix.science&lt;/li&gt;
&lt;li&gt;Iohanna Nicenboim, Unpredictable Things&lt;/li&gt;
&lt;li&gt;Soraya Okuda, HTTPS Everywhere&lt;/li&gt;
&lt;li&gt;Tiffany Ou, Least Authority - GridSync&lt;/li&gt;
&lt;li&gt;Valentina Pavel, Privacy &amp;amp; GDPR Tools&lt;/li&gt;
&lt;li&gt;Stuart Schecter, Revisolution │ 2FA&lt;/li&gt;
&lt;li&gt;Caroline Sinders, Ethical Mechanical Turk&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We are extremely excited to spend the week with them and learn from one another. We are also thankful to our friends Bernard Tyers, Cade Diehm, Nasma Ahmed, Elio Qoshi, Anxhelo Lushka, Angel Lee, and Vincent Ahrend, for volunteering their time as mentors to the residency program. Special thanks also to our &lt;a href=&#34;https://superbloom.design/underexposed#partners&#34;&gt;partners and sponsors&lt;/a&gt;, and everyone who donated on Open Collective &amp;ndash; this event would be unthinkable without your support!&lt;/p&gt;
&lt;p&gt;Follow us on Twitter to get the latest update from our week! &lt;a href=&#34;https://twitter.com/search?q=%23underexposed2019&#34;&gt;#underexposed2019&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Using Personas in Open-Source Projects</title>
      <link>https://superbloom.design/learning/blog/personas/</link>
      <pubDate>Thu, 18 Oct 2018 09:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/personas/</guid>
      <description>&lt;p&gt;Design is all about making decisions. From a rebrand to a feature specification, from a new product to a new logo, every design change presents you with a fresh set of decisions.&lt;/p&gt;
&lt;p&gt;In open-source software, we often start out with the admirable goal of basing these decisions on the needs and preferences of our community. As a user-centered designer, this makes me feel like half the battle is already won – many companies would prefer to make these decisions entirely internally, and need a lot of convincing in order to take outside input seriously!&lt;/p&gt;
&lt;p&gt;However, open-source projects can lean too far in the other direction. It’s not always practical to have the entire community weigh in on every decision. This can lead to a slower pace and to discussion fatigue, and can also cause louder or more urgent voices in your community to take on more weight than you’d like.&lt;/p&gt;
&lt;p&gt;Personas are a way to crystallize your goals, keeping your focus on people without needing to call a meeting or ask for input at every turn. You can use them as a heuristic to help you make decisions. They’ll remind you of your mission, and keep you honest during your internal conversations.&lt;/p&gt;
&lt;p&gt;In this article, we’ll take you through how to create personas for your open-source project. If you’re able to do actual user research, definitely base your personas on actual people you talked to. If you’re not able to do research or testing with users, we think you should – everyone should learn a few quick, basic tools for engaging with their users. If you’ve never done any engagement with your users and have been creating your product based on hypotheticals, you may be wasting your time.&lt;/p&gt;
&lt;h4 id=&#34;what-a-persona-is-and-what-it-isnt&#34;&gt;What a persona is (and what it isn’t)&lt;/h4&gt;
&lt;p&gt;“Renee would love this,” my colleague said, pointing to a mockup of a redesigned file browser. Renee wasn’t our boss. Renee wasn’t a user we’d interviewed. Renee wasn’t even real! Renee was a &lt;strong&gt;persona&lt;/strong&gt; we’d developed. If you’re curious, Renee was an experienced, savvy admin who had an encyclopedic knowledge of keyboard shortcuts and hated touching a mouse. She was a combination of several people we’d interviewed, our best guess at an iconic user for this particular piece of software.&lt;/p&gt;
&lt;p&gt;A persona is a slight abstraction of a human who might use your product or service. It often takes the form of a quick portrait: a name, an age, a job, an appearance, enough to give you a sense of who this person is.&lt;/p&gt;
&lt;p&gt;“Our audience is more than just a few people,” you might be thinking, “so why get so specific?” At first glance, defining a broad target demographic might seem more pragmatic, because you’re including more users in your intended audience – and, in the world of open source, we often strive to make our products inclusive and widely usable.&lt;/p&gt;
&lt;p&gt;However, defining your audience broadly has a couple of pitfalls. First, it’s hard to use demographics to make decisions. Try and picture a woman between 18 and 35. Not so easy, is it? You certainly can’t think “would a woman between 18 and 35 understand this branding?” Second, using demographics to make product decisions can lead to stereotyping. Answers to questions like “would a woman between 18 and 35 use this feature?” might veer uncomfortably close to implying that a young woman would prefer pastel colors and a simpler interface. Nope. Not going there.&lt;/p&gt;
&lt;p&gt;This is why we say that a persona is a “slight” abstraction: if you abstract too much, you’ll end up with a vague demographic description that isn’t actually useful to you. (Just like every article ever about “millennials.”)&lt;/p&gt;
&lt;p&gt;You will probably want to make multiple personas. You can give them nicknames in order to keep them straight: a team at the UK Digital Service &lt;a href=&#34;https://dataingovernment.blog.gov.uk/2016/06/15/performance-platform-5-themes-and-7-personas/&#34;&gt;created 7 personas during a project to evaluate their Perfomance Platform&lt;/a&gt;, and named them (among other things) “Bart the Active Citizen,” “Anna the Strategist,” and “Eric the Guide.” Don’t make too many, though, or you’ll have too many “people” in the room.&lt;/p&gt;
&lt;h4 id=&#34;what-to-include-in-a-persona&#34;&gt;What to include in a persona&lt;/h4&gt;
&lt;p&gt;Your persona will have three parts. The first part is demographic. Give your persona a &lt;strong&gt;name&lt;/strong&gt;, an &lt;strong&gt;age&lt;/strong&gt;, a &lt;strong&gt;location&lt;/strong&gt;, and an &lt;strong&gt;occupation&lt;/strong&gt;, no matter what. Be specific – “John Doe” or “Max Mustermann” won’t be very helpful to you! If it helps, pretend you are describing a character in a book or movie.&lt;/p&gt;
&lt;p&gt;Then, depending on your product, you may want to answer some behavioral questions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Is this person a current user of your product?&lt;/li&gt;
&lt;li&gt;What communities is this person a part of?&lt;/li&gt;
&lt;li&gt;What are this person’s hobbies, or their family situation? (Include this only if it’s relevant.)&lt;/li&gt;
&lt;li&gt;What technologies does this person use, and why?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The third part of your persona has to do with their goals. You may want to answer the following questions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What are this person’s goals in life?&lt;/li&gt;
&lt;li&gt;What are their goals at work?&lt;/li&gt;
&lt;li&gt;What makes them feel good when using a technical product? And what makes them feel bad?&lt;/li&gt;
&lt;li&gt;If they use this product, why? And if not, why not?&lt;/li&gt;
&lt;li&gt;What do they want this product to do for them?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2018/simsec_basic_persona_hu_e87fb34f222059cd.png&#34; alt=&#34;preview of persona template&#34; width=&#34;740&#34; height=&#34;523&#34;&gt;
&lt;/p&gt;
&lt;p&gt;We’ve made these sections into a template that you can use (and modify). Download it here: &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/research_tools/simsec_basic_persona.pdf&#34;&gt;PDF&lt;/a&gt; and &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/research_tools/simsec_basic_persona.ai&#34;&gt;AI&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Not all personas need to follow this format – in fact, it’s better if personas have information specific to the product or project you’re working on. Our former fellow Gus Andrews put together a set of &lt;a href=&#34;https://medium.com/@gusandrews/user-personas-for-privacy-and-security-a8b35ae5a63b&#34;&gt;security usability personas&lt;/a&gt;. They include sections like access locations, technology threats, and physical threats, effectively building a threat model into each persona. So, feel free to customize the sections you include. Our suggestions are just a starting point.&lt;/p&gt;
&lt;h4 id=&#34;further-links&#34;&gt;Further links:&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://www.usability.gov/how-to-and-tools/methods/personas.html&#34;&gt;https://www.usability.gov/how-to-and-tools/methods/personas.html&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Leading with Empathy</title>
      <link>https://superbloom.design/learning/blog/hello-georgia/</link>
      <pubDate>Tue, 02 Oct 2018 09:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/hello-georgia/</guid>
      <description>&lt;p&gt;Hello.&lt;/p&gt;
&lt;p&gt;Some of you may know me from our collaborations in the internet freedom community over the last six years or from my time in the open mapping and data visualization communities before that, but for those who don’t — Hello! And nice to meet you! My name is Georgia Bullen, and I’m excited to take the baton from Scout as the new Executive Director of Simply Secure. If you want to read more about my past work, &lt;a href=&#34;https://superbloom.design/about/people/georgia&#34;&gt;please do&lt;/a&gt;, but for now I’d like to focus on what’s next at Simply Secure.&lt;/p&gt;
&lt;p&gt;For the last four years, Simply Secure has been critical in helping to bring design and user experience into the focus for many communities working on issues of security, privacy, transparency, or other ethical implications. Scout and the team have established a really strong base of resources, support, and relationships that I&amp;rsquo;m excited to build on going forward. The issues that we face in tech are not getting easier, in fact everyday they seem to become increasingly challenging as tech reaches into new places and contexts around the world. As usability is being realized as a necessity, our movement needs support, mentorship and leadership through open educational resources, open research, and a growing network with which to work through these challenges.&lt;/p&gt;
&lt;p&gt;Building on what Scout talked about in her &lt;a href=&#34;https://superbloom.design/learning/blog/transition-time&#34;&gt;recent post&lt;/a&gt;, here are some things I see as important over the next few years:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;To scale with the challenges, we need to build our networks of practitioners to work together, learn from each other, and help locally.&lt;/strong&gt; We are a small team, but part of a growing community. Our hope is that we can work with the network of practitioners in the ecosystem to build more connections — and grow to create local networks that can help each other address local, cultural challenges together. Having a strong diverse community will allow us to help each address local and global issues in scalable ways.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;If you don&amp;rsquo;t leverage human-centered design in your process, you could be putting your system and your community of users at risk.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;We will work to be even louder advocates for usability in security tools, critical infrastructure, and new technology. Good security requires usability.&lt;/strong&gt; If your technology isn&amp;rsquo;t usable, users will work around your system to do what they need to do, or they&amp;rsquo;ll use something else. If you don&amp;rsquo;t leverage human-centered design in your process, you could be putting your system and your community of users at risk. At a minimum, usability needs to be a part of security audits, and even more importantly as part of the development process.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;As technology becomes central to human rights, empathy becomes even more important to an ethical design approach.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;Empathy is the first step to ethical design.&lt;/strong&gt; Human-centered design builds from the base assumption that through empathy, participation, and intentionality we can understand the needs of our users by embedding ourselves in their context — observing how they live their lives, what challenges they encounter, asking questions to understand them and their perspectives better. By focusing on individual experiences, we can be sure to design to people&amp;rsquo;s needs. This is particularly important when we are working in the human rights space. As technology becomes central to human rights, empathy becomes even more important to an ethical design approach.&lt;/p&gt;
&lt;p&gt;As a community, we have the power to envision a more ethical and just future, through human-centered design. Simply Secure is ready to help, and I&amp;rsquo;m excited to help lead the team in that work.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>A Guide to Gathering Feedback</title>
      <link>https://superbloom.design/learning/blog/feedback-gathering-guide/</link>
      <pubDate>Thu, 27 Sep 2018 11:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/feedback-gathering-guide/</guid>
      <description>&lt;p&gt;A human-centered approach to software means a lot of qualitative research &amp;ndash; that’s research that focuses on small-scale, in-person feedback-gathering. While bigger companies have entire departments that do product design and market research, it can be difficult for smaller, distributed teams on a budget to get user feedback. (Difficult, but not impossible: [we interviewed Tails](/learning/blog/formative-testing) about their formative testing practices, for example.)&lt;/p&gt;
&lt;p&gt;To that end, Simply Secure created a generic guide to a roughly 1-hour session to gather feedback on your mobile or web app. Individuals and teams can use this to test copy, visuals, and new designs. It’s easy to imagine running a session like this at conferences or meetups where your main audience convenes.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/resources/app_feedback_gathering.pdf&#34;&gt;PDF version&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/research_tools/app_feedback_gathering.md&#34;&gt;Markdown version&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Questions, comments, pull requests? Write us at &lt;a href=&#34;mailto:&amp;#99;&amp;#111;&amp;#110;&amp;#116;&amp;#97;&amp;#99;&amp;#116;&amp;#64;&amp;#115;&amp;#105;&amp;#109;&amp;#112;&amp;#108;&amp;#121;&amp;#115;&amp;#101;&amp;#99;&amp;#117;&amp;#114;&amp;#101;&amp;#46;&amp;#111;&amp;#114;&amp;#103;&#34;&gt;contact@simplysecure.org&lt;/a&gt;!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Thank You and Farewell</title>
      <link>https://superbloom.design/learning/blog/transition-time/</link>
      <pubDate>Fri, 01 Jun 2018 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/transition-time/</guid>
      <description>&lt;p&gt;&lt;em&gt;Today we are &lt;a href=&#34;https://superbloom.design/community/opportunities//&#34;&gt;announcing our search for our next Executive Director&lt;/a&gt;. Outgoing Executive Director Sara &amp;ldquo;Scout&amp;rdquo; Sinclair Brody shares her thoughts as we approach this transition.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2018/viewer_hu_5c22dd34fcceffd4.jpg&#34; alt=&#34;photo of viewer at beach&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;
&lt;/p&gt;
&lt;p&gt;It’s easy to talk about how the world is moving faster today than in yesteryear, especially in communities that focus on technology. But when I began my role as founding Executive Director of Simply Secure almost four years ago, the world that we work in was in many ways a different place.&lt;/p&gt;
&lt;p&gt;Simply Secure started as an idea between &lt;a href=&#34;https://en.wikipedia.org/wiki/Meredith_Whittaker&#34;&gt;Meredith&lt;/a&gt; and &lt;a href=&#34;https://en.wikipedia.org/wiki/Ben_Laurie&#34;&gt;Ben&lt;/a&gt;. Their vision was to make secure-communications tools – i.e., chat and email applications that support end-to-end encryption – more usable and approachable for non-expert people. We &lt;a href=&#34;https://superbloom.design/learning/blog/why-hello-world&#34;&gt;launched&lt;/a&gt; as an independent organization in 2014, with commitments of support for our first few years from &lt;a href=&#34;https://opensource.google.com/&#34;&gt;Google&lt;/a&gt;, the &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt;, and &lt;a href=&#34;https://www.dropbox.com/&#34;&gt;Dropbox&lt;/a&gt;. Our team &lt;a href=&#34;https://superbloom.design/learning/blog/hello-again&#34;&gt;grew&lt;/a&gt;, and we diligently set about the work of effecting change. We began collaborations with organizations such as &lt;a href=&#34;https://www.mozilla.org/en-GB/&#34;&gt;Mozilla&lt;/a&gt; and the &lt;a href=&#34;https://prototypefund.de/&#34;&gt;Prototype Fund&lt;/a&gt;, and extended our collaboration with the Open Technology Fund through the &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Usability Lab&lt;/a&gt;. Our focus expanded to include supporting people working not just on secure communications, but on any topic with security, privacy, transparency, or other ethical implications.&lt;/p&gt;
&lt;p&gt;In the intervening years &amp;ldquo;usability&amp;rdquo; and good user-experience (UX) design have gone from seemingly unattainable ideals to necessary parts of the development process for the internet freedom and other ethical-tech communities. While our efforts to support developers and designers with educational resources, open research and consulting, and peer mentorship have helped this transition, the movement has come from practitioners themselves. It has been a pleasure and an honor to collaborate with a such a diverse and committed group of people, and to help them find ways to improve their products and their teams.&lt;/p&gt;
&lt;p&gt;Here are some observations that have manifested time and again during these years.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Practitioners want to put people first.&lt;/strong&gt; Very few people build technology for technology’s sake. Most people do it because they believe on some level that they can make the world a better place. This is especially true in communities that have human-rights, internet-freedom, or other civic-minded goals. However, the gap between wanting to put people first and finding good ways to do so in practice can be a big one.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Professional and cultural barriers can get in the way.&lt;/strong&gt; Employees of big companies want to do the right thing, but don’t know how to get past a business-as-usual mentality. Open-source developers want to broaden their appeal, but don’t want to get trapped in a corporate mindset – and often don’t know how to move forward when a project is leanly resourced to begin with. When you’re working hard to deliver the parts of a project you understand, it’s hard to find the time and energy to explore dimensions where the right course of action is less apparent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Human-centered design can help with all sorts of problems.&lt;/strong&gt; Whether you’re a software developer seeking to make your tool more friendly, a designer advocating for change within your organization, or a funder worried about the effectiveness of a program or project, design and design-research methods can help bring new insights and directions to bear. Even a short conversation can help &amp;ldquo;unstick&amp;rdquo; a team faced with challenges involving users, external communication, or internal processes. Everyone can benefit from a little human-centered thinking.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;While bearing witness to these lessons as Simply Secure has grown and changed through the years, so too has my personal landscape changed, most notably through the birth of my two sons. As I look forward to the future of our community, the work it has ahead of it, and to the needs of my growing family, I have decided it is time to pass this leadership of Simply Secure on to someone else. In August I will start as a Lecturer in the &lt;a href=&#34;https://www.swarthmore.edu/computer-science&#34;&gt;Computer Science Department&lt;/a&gt; of &lt;a href=&#34;https://www.swarthmore.edu/&#34;&gt;Swarthmore College&lt;/a&gt;, where I will have the opportunity to share human-centered thinking with the next generation of technologists.&lt;/p&gt;
&lt;p&gt;The person who comes after me as Executive Director has exciting yet daunting challenges ahead of them. We are a small team with big ambitions. We are making the world a better place through human-centered design, and have shown that even small engagements can have a big impact. We need a leader who can navigate the sometimes-dizzying diversity of our communities (from global north to south, hackers to funders, corporate to counter-culture, geek to design critique). We need someone who can negotiate the challenge of building a financially sustainable organization while fulfilling our non-profit, educational mission. We need someone who dives into details and finds satisfaction in spreadsheets, but who can simultaneously chart a long-term strategic vision. Most of all, we need someone who leads through empathy – for the practitioners we serve, for colleagues within the team, and for the members of the public who ultimately benefit from what we do.&lt;/p&gt;
&lt;p&gt;Looking back on my years at Simply Secure, I am pleased to say that I have relished the opportunity to grow the organization from the ground up. I see the difference we have made, and am hopeful for the future. Most of all, I am enthusiastic to support my successor in leading our organization through its next stage of growth and evolution.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;If you know someone that would be a great candidate, please share &lt;a href=&#34;https://superbloom.design/community/opportunities//&#34;&gt;our job posting&lt;/a&gt;. We’re relying on you to help us find our next Executive Director!&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>A Curated List of GDPR Resources</title>
      <link>https://superbloom.design/learning/blog/gdpr-resources/</link>
      <pubDate>Fri, 18 May 2018 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/gdpr-resources/</guid>
      <description>&lt;p&gt;Simply Secure is dedicated to helping designers and developers build technology that protects people&amp;rsquo;s privacy and security. Thus we welcome the upcoming EU regulations for data protection, the General Data Protection Regulation (GDPR), as a promising step in taking seriously people&amp;rsquo;s rights to privacy and security online.&lt;/p&gt;
&lt;p&gt;Over the past few weeks (and leading up to the deadline of May 25, 2018), we have collected some resources and examples that we found helpful or interesting. We hope that these tools and checklists will help smaller organizations get some last-minute advice and explainers.&lt;/p&gt;
&lt;p&gt;GDPR-compliance is the minimum of what we need to do as ethical designers, and it is only the start of a conversation we all need to engage in. These are exciting times!&lt;/p&gt;
&lt;h4 id=&#34;general-privacy--ux&#34;&gt;General Privacy + UX&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://simplysecure.org/knowledge-base/&#34;&gt;Simply Secure Knowledge Base&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;overview&#34;&gt;Overview&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://www.fastcodesign.com/90171699/what-is-gdpr-and-why-should-designers-care&#34;&gt;What is GDPR, and why should designers care? (Fast Company)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/&#34;&gt;Guide to GDPR&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.kau.se/cs/pbd&#34;&gt;Course from Karlstad University&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;privacy-by-design&#34;&gt;Privacy By Design&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;&#34;&gt;PBD Primer&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://iab.org/wp-content/IAB-uploads/2011/03/fred_carter.pdf&#34;&gt;Foundational Principles&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.smashingmagazine.com/2017/07/privacy-by-design-framework/&#34;&gt;Privacy by Design Framework&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;ad-tech--gdpr&#34;&gt;Ad Tech + GDPR&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;http://blogs.harvard.edu/doc/2018/05/12/gdpr/&#34;&gt;GDPR Will Pop the Adtech Bubble (Doc Searles)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework&#34;&gt;Interactive Advertising Framework&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;patterns-and-catalogues&#34;&gt;Patterns and Catalogues&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://catalogue.projectsbyif.com/&#34;&gt;Data Permissions Catalogue (Projects By If)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://newdigitalrights.projectsbyif.com/&#34;&gt;New Digital Rights (Projects By If)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://dataportability.projectsbyif.com/&#34;&gt;Data Portability (Projects By If)&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;assessment-plans&#34;&gt;Assessment Plans&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://gdprchecklist.io/&#34;&gt;GDPR Checklist&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://docs.google.com/spreadsheets/d/1uu9XRXExRQXD5Z3RpcGyRdIu2OUbyHTeeUmw4aR5Xs8/edit#gid=512308730&#34;&gt;GDPR assessment and implementation plan - Processors (Corrick, Wales, Partners)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://docs.google.com/spreadsheets/d/1U0Bfjrz4GbB5VREkh44nKE5-WJlqpvqc5yoymNJu0m4/edit#gid=512308730&#34;&gt;GDPR assessment and implementation plan - Controllers (Corrick, Wales, Partners)&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;in-practice&#34;&gt;In Practice&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://docs.google.com/document/d/1FpKNHdGcPTt7UxUEraAqrcfojGwvnHkFgZjetHwP06E/edit&#34;&gt;GDPR and The Engine Room (The Engine Room)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://jacquesmattheij.com/gdpr-hysteria-part-ii-nuts-and-bolts&#34;&gt;GDPR Actionable Advice&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/opengdpr/opengdpr&#34;&gt;OpenGDPR Framework&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://techcrunch.com/2018/04/17/facebook-gdpr-changes/&#34;&gt;A Flaw-By-Flaw Guide to Facebook’s GDPR Changes (TechCrunch)&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Formative Testing, with Tails</title>
      <link>https://superbloom.design/learning/blog/formative-testing/</link>
      <pubDate>Fri, 27 Apr 2018 11:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/formative-testing/</guid>
      <description>&lt;p&gt;&lt;em&gt;We spoke with sajolida from Tails about design methods, user research, and particular challenges in open source.&lt;/em&gt;&lt;/p&gt;
&lt;h4 id=&#34;before-we-begin-could-you-tell-us-what-tails-is-and-what-its-used-for&#34;&gt;Before we begin, could you tell us what Tails is and what it’s used for?&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;https://tails.boum.org/&#34;&gt;Tails&lt;/a&gt; is a live operating system that you can start on any computer from a USB stick. It provides a secure computing environment out of the box.&lt;/p&gt;
&lt;p&gt;Activists and journalists use Tails to create dissident books and videos, chat off-the-record, browse the web anonymously, and share sensitive documents. It is free software and is used by more than 20,000 people daily.&lt;/p&gt;
&lt;h4 id=&#34;what-is-it-that-you-do-for-tails&#34;&gt;What is it that you do for Tails?&lt;/h4&gt;
&lt;p&gt;Even though I have a background in computer science, I never really jumped into writing core but do a lot of the work needed around the code itself. We are a small team and people are doing many different things. I started doing documentation and website. We always had a strong policy to have an extensive documentation. By necessity I&amp;rsquo;m also doing fundraising and accounting, and more recently I started doing UX, checking whether our interfaces actually work for people, etc.&lt;/p&gt;
&lt;h4 id=&#34;how-did-your-ux-work-come-about-in-the-first-place&#34;&gt;How did your UX work come about in the first place?&lt;/h4&gt;
&lt;p&gt;In 2014, we got in touch with a startup incubator in Paris called &lt;a href=&#34;https://paris.numa.co/en/&#34;&gt;NUMA&lt;/a&gt;. They wanted to contribute to open source projects and we organized some user testing sessions together. That was the start of our UX journey. For that event we prepared a list of tasks, e.g. &amp;ldquo;how to chat securely with your friends&amp;rdquo;, and they organised the space and recruiting. For us it was a big eye-opener, because people were not able to complete any of the tasks we posed to them! The problems were elsewhere and people had serious problem starting Tails and getting connected to the network.&lt;/p&gt;
&lt;p&gt;Then we worked with them on mapping the installation process. The website was very badly organized back then and people were constantly getting lost. We sat down and tried to make the process more streamlined. While doing this, we also started incorporating early testing of our designs. For example, had people click through very rough prototypes created using interactive slide shows. We were two people, so we did &lt;a href=&#34;https://www.usability.gov/how-to-and-tools/methods/parallel-design.html&#34;&gt;parallel design&lt;/a&gt; and had people test different solutions. That was the beginning!&lt;/p&gt;
&lt;h4 id=&#34;so-you-learned-design-methods-along-the-way&#34;&gt;So you learned design methods along the way?&lt;/h4&gt;
&lt;p&gt;Across the process of designing the installation instructions, we worked with NUMA and then on our own. It really had opened our eyes, using just very simple methodologies. We continued learning more UX methods on our own, reading books and online resources, and listening to the advice of experienced UX designers every time we could.&lt;/p&gt;
&lt;h4 id=&#34;designers-are-notoriously-hard-to-find-in-open-source-how-is-ux-in-open-source-different-from-ux-in-the-industry&#34;&gt;Designers are notoriously hard to find in open source. How is UX in open source different from UX in the industry?&lt;/h4&gt;
&lt;p&gt;I think that UX is becoming more and more important in the software industry, because a lot of revenue is directly tied to UX. Oftentimes companies are competing with very similar services, and a better UX, even just by a little bit, might be the deciding factor. Of course, in open source we&amp;rsquo;re not fighting for market shares and money and I have the feeling that the importance of UX is neglected, because the survival of a project does not depend so strongly on your product being useful and usable. In the case of Internet freedom tools, it&amp;rsquo;s often external funding that determines your survival, not so much your success over the competition.&lt;/p&gt;
&lt;h4 id=&#34;and-of-course-success-is-hard-to-measure-in-open-source-to-begin-with&#34;&gt;And of course success is hard to measure in open source to begin with!&lt;/h4&gt;
&lt;p&gt;Yes. We don’t ask people to subscribe, we don’t collect usage data, there’s no payment, etc. So it’s hard to have success metrics, especially if you want to respect the privacy of your users! One technique we experimented with was to do a &lt;a href=&#34;https://tails.boum.org/blueprint/veracrypt/#survey&#34;&gt;survey from our website&lt;/a&gt;. If you ask respectfully, and if people understand how useful it is, people are ready to participate!&lt;/p&gt;
&lt;h4 id=&#34;you-recently-had-an-uxui-design-sprint-in-berlin-can-you-tell-us-more-about-it&#34;&gt;You recently had an UX/UI design sprint in Berlin, can you tell us more about it?&lt;/h4&gt;
&lt;p&gt;Actually we had two sprints of three days each this winter. We are working on two new features for Tails and wanted to check our designs with users right from the start. We were two people in each sprint: the main developer of the feature and me.&lt;/p&gt;
&lt;p&gt;We arrived on the first day with our prior research on the feature, for example the results of a user survey or feasibility studies on the technical issues, but zero design. We started by doing a &lt;a href=&#34;https://articles.uie.com/design_studio_workshop/&#34;&gt;design studio&lt;/a&gt; the two of us to come up with a candidate design that we could draw and print on paper.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2018/prototyping_hu_982d27a1e77f2139.jpg&#34; alt=&#34;paper prototype&#34; width=&#34;740&#34; height=&#34;417&#34;&gt;
&lt;/p&gt;
&lt;p&gt;In the afternoon of the first day we had our first users come over and test our paper prototype. On the second and third day we continued inviting people to come and test our prototype as we improved our design. We had 7 users come over for each sprint, counting two hours per participants to have time to debrief and prepare the prototype for the next participant.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s for the initial sprint. After the feature is developed, we also do some moderated user testing with a beta version of the feature. But if I could only do one set of tests I would keep the early paper prototyping. Because if you only test at the end, you&amp;rsquo;ll find out too late that thing you&amp;rsquo;ve built is bad!&lt;/p&gt;
&lt;p&gt;I can&amp;rsquo;t see myself building anything in the future without going through a process like this.&lt;/p&gt;
&lt;h4 id=&#34;we-at-simply-secure-are-big-believers-in-paper-prototypes-what-role-did-they-play-in-your-testing&#34;&gt;We at Simply Secure are big believers in paper prototypes. What role did they play in your testing?&lt;/h4&gt;
&lt;p&gt;With paper prototypes, you draw or print your interface on paper. You create pieces of paper for each moving part of your interface: a menu that opens, a dialog box that appears, a checkbox that gets selected, etc. You give the user a pencil and pretend that it&amp;rsquo;s their mouse, to click, and keyboard, to write. The pieces of paper and the pencil are like a magic computer: they can click anywhere, write anything, and you are playing the computer, changing and moving the pieces of paper as the person uses the interface. It&amp;rsquo;s surprising how fast people get it.&lt;/p&gt;
&lt;p&gt;Something that&amp;rsquo;s tricky for us: since Tails is a full operating system, most of the time we&amp;rsquo;re not building the tools ourselves. We are relying on Debian, on GNOME, and on all sorts of preexisting tools. In the two sprints we did, it was mostly integration work. Paper prototypes were especially useful in this case, since we could print out mockups of existing GNOME interfaces and several other tools and test the changes that we wanted to make to them.&lt;/p&gt;
&lt;p&gt;All-in-all, the new things that we designed represented maybe 10% of the overall experience. Doing even a rough code prototype for all this would have been impossible. You would have to change things all over the place!&lt;/p&gt;
&lt;h4 id=&#34;how-useful-were-these-sessions-for-you-and-your-team&#34;&gt;How useful were these sessions for you and your team?&lt;/h4&gt;
&lt;p&gt;We involved our developers in this process. I was mainly facilitating the feedback, preparing the prototypes etc. And the developers were just observing. That was super useful, mostly for four reasons:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Often when you tell developers that what they&amp;rsquo;re designing is going to be too complicated, they don&amp;rsquo;t believe you. But when they see one person being confused, they go back and really want to fix the problem.&lt;/li&gt;
&lt;li&gt;You also make sure that what you are designing is possible for them to implement. Sometimes they also come up with solutions that you wouldn&amp;rsquo;t have considered yourself because they know better the technical implications.&lt;/li&gt;
&lt;li&gt;If you disagree on a design choice, you avoid endless debates by testing any of the proposed solutions with the next user and learning from that. You can even show two different versions to the same user, have them comment on both, and learn even more.&lt;/li&gt;
&lt;li&gt;We are a remote team and being in an office working on the same sheet of paper is so much better. Once the sprint is over, you don&amp;rsquo;t have to explain your design because the developers saw it in action. The drawings from the sprint are the only specification that they need to write the code.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;it-wasnt-hard-to-find-participants&#34;&gt;It wasn’t hard to find participants?&lt;/h4&gt;
&lt;p&gt;Not at all! The interest we found in Berlin was overwhelming. People wanted to help. It was so easy to recruit people. We had 100 and 175 people, respectively, answer our call on our website for both our sprints. This is really amazing!&lt;/p&gt;
&lt;h4 id=&#34;what-were-some-of-your-findings-how-has-that-informed-your-design&#34;&gt;What were some of your findings? How has that informed your design?&lt;/h4&gt;
&lt;p&gt;It&amp;rsquo;s fascinating how often the problems that you identify with user testing are really not were you expected them to be&amp;hellip;&lt;/p&gt;
&lt;p&gt;Our first sprint was about integrating VeraCrypt in GNOME, the desktop environment in Tails. Instead of having a dedicated application to unlock VeraCrypt volumes, for example an encrypted USB stick, we integrated that in the native GNOME environment like you would do to open a regular USB stick. But this made the whole thing too transparent for people who were otherwise used to have a dedicated VeraCrypt application in Windows for example.&lt;/p&gt;
&lt;p&gt;We solved that by adding a little wrapper in our applications menu that has the word &amp;ldquo;VeraCrypt&amp;rdquo; in it. It provides shortcuts to the most common operations and a link to our documentation. It will teach people how to do it seamlessly the next time.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;You&amp;rsquo;re not testing to see if it works; you&amp;rsquo;re testing to evolve and change as much as you want and as best as you can.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id=&#34;do-you-observe-or-record-your-tests&#34;&gt;Do you observe or record your tests?&lt;/h4&gt;
&lt;p&gt;I don&amp;rsquo;t record. We are changing the prototype between each test. It&amp;rsquo;s a formative process. For example, participants might misunderstand some interface widgets or labels that we designed. We would draw new widgets or change the labels on the fly until it works for them. You&amp;rsquo;re not testing to see if it works; you&amp;rsquo;re testing to evolve and change as much as you want and as best as you can. You also get ideas or suggestions directly from the participants.&lt;/p&gt;
&lt;h4 id=&#34;what-are-you-plans-next&#34;&gt;What are you plans next?&lt;/h4&gt;
&lt;p&gt;Most of the UX things we&amp;rsquo;ve been doing are task-oriented. Something we&amp;rsquo;d like to do more in the project is storytelling and explaining what Tails is and why people should use it. This is more complicated for me, after all I am a scientist and I more used to solving problem. Finding a narrative is a challenge! Communication, branding, design&amp;mdash;maybe that’s a next gap to fill.&lt;/p&gt;
&lt;h4 id=&#34;thank-you-sajolida&#34;&gt;Thank you, sajolida!&lt;/h4&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2018/sajolida_hu_df511b528b306487.jpg&#34; alt=&#34;sajolida&#34; width=&#34;740&#34; height=&#34;712&#34;&gt;
&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Innovation Is About Putting People First</title>
      <link>https://superbloom.design/learning/blog/innovation-about-people/</link>
      <pubDate>Tue, 20 Feb 2018 12:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/innovation-about-people/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2018/MIC_hu_621364562c3562b3.png&#34; alt=&#34;Fast Company&amp;rsquo;s Top 10 Most Innovative Companies in Design for 2018&#34; width=&#34;740&#34; height=&#34;208&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Simply Secure is thrilled to be named as one of &lt;em&gt;Fast Company&lt;/em&gt;’s &lt;a href=&#34;https://www.fastcompany.com/most-innovative-companies/2018/sectors/design&#34;&gt;Top 10 Most Innovative Companies in Design for 2018&lt;/a&gt; and to have our focus on “helping designers be more transparent and ethical” recognized.&lt;/p&gt;
&lt;p&gt;Fast Company calls their list of innovative companies a “guide to the businesses that matter most.” We live in a time where much of the technology industry seems focused on monetizing clicks and likes, on tracking users to optimize conversions, and on warehousing data to train opaque AI models. We believe that truly innovative design is about more than clicks, conversions, and models. We need to focus the technology community not just on what’s good for companies, but good for people. This is the work that matters most.&lt;/p&gt;
&lt;p&gt;All practitioners, from open-source software developers to brand designers and UX researchers, can work to make responsible and ethical technology. We’re here to support them, and to learn from them.&lt;/p&gt;
&lt;p&gt;So if you are just finding out about us and the work we do now, welcome! We are happy to talk to teams seeking help at the intersection of design and thorny challenges in privacy, security, transparency, and ethics. We believe that designers and design should have a leadership role in shaping the conversation on these issues.&lt;/p&gt;
&lt;p&gt;We help organizations large and small, so whether you’re at a big company and need a bespoke workshop to kickstart your design team in a new area, or whether you’re a cryptographer volunteering for an open-source project and need help with your design strategy, we want to hear from you. Connect with us &lt;a href=&#34;https://twitter.com/simplysecureorg&#34;&gt;on Twitter&lt;/a&gt; or at  &lt;a href=&#34;mailto:contact@simplysecure.org&#34;&gt;contact@simplysecure.org&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Prototyping Transparency: A Smart Charging Station</title>
      <link>https://superbloom.design/learning/blog/transparent/</link>
      <pubDate>Thu, 18 Jan 2018 11:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/transparent/</guid>
      <description>&lt;p&gt;&lt;em&gt;Here at Simply Secure we love to share the good work that others are doing. Our interview series is a way for us to spread current ideas, insights, and experiments to anyone interested in ethical design.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Marcel Schouwenaar is part of the team behind the &lt;a href=&#34;https://responsiblesensinglab.org/projects/transparent-charging-station&#34;&gt;Transparent Charging Station&lt;/a&gt;, a device that visualizes &amp;ldquo;smart&amp;rdquo; charging at charging stations. He spoke with us about fair allocation of resources, visualizing algorithms, and the role of transparency in design.&lt;/em&gt;&lt;/p&gt;
&lt;h4 id=&#34;in-designing-this-transparent-charging-station-what-was-your-underlying-assumption&#34;&gt;In designing this Transparent Charging Station, what was your underlying assumption?&lt;/h4&gt;
&lt;p&gt;Electric power is a resource that fluctuates a lot, especially with renewable resources. Sometimes too much power is generated, and sometimes there is a scarcity; and similarly, depending on the time of day, a lot of power is needed sometimes, and none at all at other times. Grid operators have to constantly decide how to allocate the available energy, and it is no different with electric charging stations around the city. So when there is not enough energy available to charge all the hooked up cars, the company has to prioritize charging according to certain parameters. The challenge here is to build a reliable provision of power, a reliable &lt;em&gt;network&lt;/em&gt; so that everyone&amp;rsquo;s mobility is guaranteed.&lt;/p&gt;
&lt;h4 id=&#34;so-electric-power-is-a-public-good-and-the-question-you-posed-was-how-to-distribute-that-public-good-was-this-the-goal-of-the-project&#34;&gt;So electric power is a public good, and the question you posed was how to distribute that public good. Was this the goal of the project?&lt;/h4&gt;
&lt;p&gt;Basically, yes. We have to decide how to prioritize some people over other people. But then the question is &amp;ldquo;to which people, and why?&amp;rdquo; As a design challenge we actually got the problem wrong for weeks. We were building UX for people to express their urgency in this scenario, or some sort of voting system for decision making. But that was all wrong. The problem here isn&amp;rsquo;t so much deciding on those parameters, but understanding how algorithms are making those decisions in the first place. The design challenge, therefore, is to make that decision process transparent to the public. People will be affected by these decisions, so we need to have a way to communicate. And this project is an attempt to visualizes resource allocation according to whatever algorithm is in charge. The problem here isn&amp;rsquo;t so much deciding on those parameters, but understanding how algorithms are making those decisions in the first place.&lt;/p&gt;
&lt;h4 id=&#34;how-did-you-come-up-with-the-idea&#34;&gt;How did you come up with the idea?&lt;/h4&gt;
&lt;p&gt;This project was commissioned by a client, a grid operator in the Netherlands that saw the urgency of having a public conversation around algorithmic decision making in smart cities. As a &lt;a href=&#34;https://en.wikipedia.org/wiki/B_Corporation_(certification)&#34;&gt;B Corp&lt;/a&gt; charged with the task of distributing energy across the Netherlands, they have de facto no competition on the market, but an even greater responsibility to the public. Companies like them are therefore interested in making the process as transparent as possible, and the transparent charging station is just the latest incarnation of that in the &amp;ldquo;smart city&amp;rdquo;.&lt;/p&gt;
&lt;!-- ![charging machine prototype](https://the-incredible-machine.com/img/projects/chargingstation/4.jpg)  --&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://responsiblesensinglab.org/img/a464d4ed-a7b4-440e-86ce-5343bc8f574b/transparante-laadpaal.jpg&#34; alt=&#34;charging machine prototype&#34;&gt;
&lt;/p&gt;
&lt;h4 id=&#34;what-were-some-of-the-challenges-in-designing-this-machine&#34;&gt;What were some of the challenges in designing this machine?&lt;/h4&gt;
&lt;p&gt;First of all, humans are not used to algorithmic decision making. We&amp;rsquo;d like to think that decisions are very singular, that at one particular moment, there is a clear number of choices, and a determinate decision on those choices. However, with an algorithm like this, things are very different. It&amp;rsquo;s many tiny decisions over time, and much harder to picture.&lt;/p&gt;
&lt;p&gt;Secondly, a decision based on parameters is hard to communicate, because it&amp;rsquo;s very abstract. So we thought we might have a way for people to experience these parameters. In our prototype, we had two of them: stress and privilege. By interacting with the machine, you can express how much stress you have (&amp;ldquo;I need this much charge before this hour&amp;rdquo;), and also identify yourself via an ID that has a level of privilege attached to it. This was our way to explain the abstract idea of parameters to the general public.&lt;/p&gt;
&lt;h4 id=&#34;and-how-does-your-machine-communicate-these-decisions&#34;&gt;And how does your machine communicate these decisions?&lt;/h4&gt;
&lt;p&gt;The machine shows the amount of charge available in the upcoming four hours, as well as who it will be distributed to and why. So if you&amp;rsquo;re asking yourself, why am I getting so little charge, you might see that the person who&amp;rsquo;s charging now has more &amp;ldquo;privilege&amp;rdquo;. It also records a history of the power distribution. Of course, in practice, nothing goes according to plan, ever. I might see a certain plan for the next four hours, but then someone else might arrive in the meantime and get all the power instead. That&amp;rsquo;s why the recording is important, too. We thought long and hard about this, because there are many ways to give people something like a digital receipt. However, we felt that another app made by the company or the city is not as trustworthy. For some time we were even experimenting with thermal paper that could be a physical (and unalterable) imprint of your charge history. But we settled for the less cumbersome solution: your own phone camera. It&amp;rsquo;s a more intuitive way to engage with the physical world. So if decisions seem unfair, the idea here is that customers can take a quick video of the “replay” to document it for a possible complaint. We call it an actionable perspective.&lt;/p&gt;
&lt;h4 id=&#34;so-will-we-see-machines-like-this-on-future-street-corners&#34;&gt;So will we see machines like this on future street corners?&lt;/h4&gt;
&lt;p&gt;We don&amp;rsquo;t think a machine like this will be built, at least not in this form. But it&amp;rsquo;s a good conversation starter for entities that operate in both the private and public sector. They are eager to prove that they are doing the right thing, and this is, we think, one possible way to do it.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Transparency is not a solution for data governance, but it is a way to give users of the system some leverage points.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id=&#34;one-central-idea-here-is-that-discrimination-is-not-determined-by-bad-intentions-but-only-by-bad-outcomes-you-only-need-to-look-at-the-results-of-a-program-to-see-whether-discrimination-exists-or-not-what-do-you-think-about-this-approach&#34;&gt;One central idea here is that discrimination is not determined by bad intentions, but only by bad outcomes. You only need to look at the results of a program to see whether discrimination exists or not. What do you think about this approach?&lt;/h4&gt;
&lt;p&gt;This was also a revelation to our client. For one, modern-day applications are never that easy where you can look at a piece of code and &amp;ldquo;see&amp;rdquo; the inequality. Systems can become complex and interdependent, you don&amp;rsquo;t always know what influences what. Also consider optimization algorithms, used in machine learning or artificial intelligence. It&amp;rsquo;s constantly changing and trying to come up with the best possible output. But doing so is letting in lots of bias of course&amp;mdash;this is old news. However, that cannot be traced back to one particular input, or to one decision. So the scrutiny has to be on a different level. Transparency is not a solution for data governance, but it is a way to give users of the system some leverage points.&lt;/p&gt;
&lt;h4 id=&#34;do-you-think-that-this-principle-of-transparency-can-be-applied-in-other-domains-also&#34;&gt;Do you think that this principle of transparency can be applied in other domains also?&lt;/h4&gt;
&lt;p&gt;We think that similar prototypes could also be developed for, say, internet traffic monitoring. If you&amp;rsquo;re home and trying to watch Netflix, and you realize your internet speed is very slow, a system like ours could help to communicate the reasons. Right now there is just no way to see why! It could be the dust accumulating in your computer, some websites mining Bitcoins in the background, your ISP screwing you over&amp;hellip;&lt;/p&gt;
&lt;p&gt;I suspect we will see more and more of that in the future. &amp;ldquo;Smart cities&amp;rdquo; are just trying to optimize allocation of different scarcities, be it energy, water, safety, internet traffic, clean streets etc. How we allocate resources is and should be a political choice. Just because the IBMs and Ciscos of this world are informing the government on how we do it doesn&amp;rsquo;t make it any less political, especially when the methods amplify discrimination and bias. The role of transparency here is to make an open, political discussion around these issues possible in the first place.&lt;/p&gt;
&lt;h4 id=&#34;youve-been-touring-europe-with-this-prototype-recently-what-was-the-response-from-people-working-in-this-area&#34;&gt;You&amp;rsquo;ve been touring Europe with this prototype recently. What was the response from people working in this area?&lt;/h4&gt;
&lt;p&gt;A lot of the discussion around these topics have been very academic, and I&amp;rsquo;m proud to have a physical prototype that I can show. There is a lot of commitment from the cities, from academia, the industry. They got the message. It doesn&amp;rsquo;t matter if they discard this prototype, because what matters is that the point got across, and people are actively thinking and designing new stuff. As for the machine: three cities are ready to make smart and transparent charging systems, it has also sparked quite a few research projects, and will be part of an exhibition in the &lt;a href=&#34;http://www.ams-institute.org/&#34;&gt;AMS Institute&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;thank-you-marcel&#34;&gt;Thank you, Marcel!&lt;/h4&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2018/marcel_hu_31e3ffea1b43cd93.jpg&#34; alt=&#34;Headshot of Marcel&#34; width=&#34;740&#34; height=&#34;944&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Marcel Schouwenaar, a designer and strategist at &lt;a href=&#34;https://the-incredible-machine.com/&#34;&gt;The Incredible Machine&lt;/a&gt;. In 2012 he co-founded this company together with partner Harm van Beek. In their work they research opportunities in the realm of internet connected products and services for clients like LEGO Group, Zodiac Aerospace, Festool and Alliander. With a strong focus on experiment and validation, The Incredible Machine is most often involved in the earliest stages of innovation.&lt;/p&gt;
&lt;p&gt;It is in these stages that Harm and Marcel encountered ethical dilemmas where the interest of business conflicted with those of people and society. This friction led to the writing of the &lt;a href=&#34;https://www.iotmanifesto.com/&#34;&gt;IoT Design Manifesto&lt;/a&gt; – in collaboration with fellow designers and researchers – and the establishment of the Just Things Foundation. Both of these efforts are aimed at addressing what it means to create products in a data-driven society and empowering professionals to act in the interests of people, society, and the environment. Marcel is also a co-organizer of ThingsCon Amsterdam.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>User Feedback Activities</title>
      <link>https://superbloom.design/learning/resources/gather-feedback/</link>
      <pubDate>Thu, 28 Sep 2017 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/gather-feedback/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Retail Apps and Data Collection</title>
      <link>https://superbloom.design/learning/blog/loyalty/</link>
      <pubDate>Sun, 30 Jul 2017 17:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/loyalty/</guid>
      <description>&lt;p&gt;In 2017 we did user research in San Francisco to speak with people who used store branded loyalty and couponing apps, such as the Starbucks or GroupOn apps. Our eight participants were selected on the basis of frequent use of shopping and loyalty apps and regional diversity. We did not ask invasive questions about income, and instead recruited people from a range of professions and communities, such as chef from San Rafael and UX designer from Palo Alto. Two of our participants used Android, although one of them also used an iPhone as a personal phone. The remaining 6 used iPhones.&lt;/p&gt;
&lt;p&gt;The goal was to understand why people used these apps and to explore ideas for personal data markets that would give individuals more control over how their data was used and who benefited financially.&lt;/p&gt;
&lt;p&gt;Our participants were enthusiastic users of:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Shopping apps:&lt;/strong&gt; Including apps for coffee and cafes, grocery shopping,liquor delivery, household supplies, clothing, entertainment, and party supply delivery. Two participants were hosting March Madness basketball parties and used apps to purchase supplies.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Service apps:&lt;/strong&gt; Including dog-walking, laundry delivery, and social events (wine-tasting, outdoor activities, etc.).&lt;/p&gt;
&lt;h2 id=&#34;no-surprises-about-data-sharing&#34;&gt;No Surprises About Data Sharing&lt;/h2&gt;
&lt;p&gt;Our hypothesis was that people would not understand what data apps gather about them, and once they did might feel that they were not getting a good deal by exchanging their data for coupons. We expected showing participants their app settings for location tracking and contact sharing would lead to surprise and outrage, and that would be a catalyst for a discussion about what apps data collect. Our hypothesis was wrong. None of the participants were surprised about the data being gathered by their apps. All of them were all familiar with privacy settings and had made some changes in configuration. A common pattern was to deny at least one app permission because they didn’t trust one particular app, but granting it to others.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2017/permissions_hu_d72e015ec7bdc90c.jpg&#34; alt=&#34;Summary: iPhone privacy setting showing contact sharing denied for Messenger but granted for other apps like Uber, LinkedIn, and Pintrest.&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;iPhone privacy setting showing contact sharing denied for Messenger but granted for other apps like Uber, LinkedIn, and Pintrest.*&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;communal-economic-benefits-made-data-collection-worth-it&#34;&gt;Communal Economic Benefits Made Data Collection Worth It&lt;/h2&gt;
&lt;p&gt;Our participants were familiar with privacy settings and had no surprise or outrage about the data apps gathered about them. Not only were they not surprised, our participants had &lt;em&gt;positive&lt;/em&gt; feelings about how these apps was beneficial not only to themselves, but to their communities. We were surprised that participants generally framed the benefits not only in terms of personal savings, but in terms of communal benefits. All eight participants said that they wouldn’t be able to stay in the Bay Area if they didn’t work hard to save money. Getting discounts on necessities like groceries and coffee by purchasing through the app was a common money saving strategy. People had strong positive feelings about grocery store chain Safeway’s app and the Starbucks app because they believed they helped them continue living in their communities.&lt;/p&gt;
&lt;p&gt;We were surprised that people also saw the Safeway and Starbucks app as helping them give back to their communities.&lt;/p&gt;
&lt;h3 id=&#34;apps-support-volunteer-donations&#34;&gt;Apps support volunteer donations&lt;/h3&gt;
&lt;p&gt;One participant used the Safeway app to buy food for a residential treatment facility where he volunteered. He shared that he could not afford to purchase and donate extra food without the app, so he credits the app with helping his community.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2017/safeway_hu_aef71993a7ce8c3f.jpg&#34; alt=&#34;Summary: Screenshot of grocery store Safeway’s app.&#34; width=&#34;740&#34; height=&#34;566&#34;&gt;
&lt;br&gt;
&lt;em&gt;A participant who uses the Safeway app to donate food to a residential treatment facility reviews his latest money saving offers in the app.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;apps-support-worker-pay-by-enabling-tipping&#34;&gt;Apps support worker pay by enabling tipping&lt;/h3&gt;
&lt;p&gt;Our participants rarely used cash for their purchases. In San Francisco, companies such as Square shaped a culture of credit and debit card use, even for purchases as small as a cup of coffee. Now apps and watches are quickly becoming standard ways to pay. We heard the expected stories of personal convenience when ordering coffee via the Starbuck’s app. Anecdotal observation at three Starbucks in downtown San Francisco during morning rush hour showed lines of more than twenty people mostly paying with cards, and separate, faster queues for people paying by app. We were surprised to learn than there is no way to add a tip to a credit card or debit card payment at Starbucks. Two participants shared that the &lt;em&gt;only&lt;/em&gt; way to give tips was through the app. When asked about leaving cash tips, they were puzzled and said it was possible, but unusual.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;You can’t tip if you pay with a card because there’s no signing. I worked in food service, and the ability to tip is very important, so pay with app is a better choice. Pay with cash? No. That’s not really common anymore. &lt;em&gt;– 33-year-old freelance graphic designer from Alameda, California.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2017/starbucks_hu_dd5f7067655d202e.jpg&#34; alt=&#34;Summary: Advertisement for the Starbucks app in downtown San Francisco.&#34; width=&#34;740&#34; height=&#34;568&#34;&gt;

&lt;em&gt;Sign for the dedicated line for orders made through the app at a Starbucks in downtown San Francisco.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;tech-startups-as-good-for-communities&#34;&gt;Tech startups as good for communities&lt;/h3&gt;
&lt;p&gt;Our participants believe the tech industry is an important part of San Francisco and were proud to support it, both by working in it, but also by contributing their data via apps. Three of our participants worked in tech marketing and felt strongly that the industry helped keep neighborhoods vibrant and provided work to people. They were proud that startups “stood up for the little guy” and talked about how apps such as Cups, which gives discounts at multiple independent neighborhood coffee stores, were a way to help “mom and pop, brick and mortar” stores stand up against chain stores.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2017/pridehat_hu_1fae993d2909a92e.jpg&#34; alt=&#34;California gay pride hat.&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;

&lt;em&gt;Study participant who worked in marketing for a startup and was unconcerned about data collection.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;reconsidering-our-assumptions&#34;&gt;Reconsidering Our Assumptions&lt;/h2&gt;
&lt;p&gt;The participants’ strong positive feelings about the apps and their perceived community benefits were surprising. Our discussion about risks of data collection by private companies or consequences of government data collection faltered. Even though four of our eight participants told stories about being profiled or harassed for being non-white, a religious minority, or LGBT, they were unconcerned about personal risks from apps.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I hate when people say ‘well what do you have to hide?’.
I have a Muslim name and get regularly asked where I’m &lt;em&gt;really&lt;/em&gt; from. I do not take it lightly. But using these services [retail apps] is a requirement for participating in modern society. That’s the way it is now. &lt;em&gt;– 26-year-old graduate student from San Jose, California.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Simply Secure is a nonprofit focused on security, privacy, transparency, and ethical software, so hearing strong opposition to privacy measures was disappointing. It made us appreciate how complex the technical, social, and economic systems are and how much additional work is necessary to raise awareness and change the culture of data sharing.&lt;/p&gt;
&lt;p&gt;We look forward to delving deeper into this research, and trying alternate approaches to uncover opportunities for personal data marketplaces.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Lessons from Architecture School for IoT Security</title>
      <link>https://superbloom.design/learning/resources/lessons-architecture-school-iot-security/</link>
      <pubDate>Wed, 05 Jul 2017 17:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/lessons-architecture-school-iot-security/</guid>
      <description>&lt;p&gt;Software is impermanent; its underlying code will always need updating. Architecture is enduring, meant to last for generations. But both strive to be intuitive, and architecture can teach security and UX professionals how to build IoT applications that balance seamless experience and upgradable infrastructure.&lt;/p&gt;
&lt;p&gt;Security for the Internet of Things (IoT) needs design, and appropriate complexity is the key UX challenge for IoT. Architecture school teaches problem finding over problem solving and prepares professionals to work on complex systems.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2017/ArchSchool-IoTLessons_hu_e3f43934a8f422fb.jpg&#34; alt=&#34;Summary: Start with people in context, understand unspoken needs, homes are more than houses.&#34; width=&#34;740&#34; height=&#34;316&#34;&gt;

&lt;em&gt;Summary slide from presentation at &lt;a href=&#34;https://conferences.oreilly.com/solid/internet-of-things-2015&#34;&gt;O&amp;rsquo;Reilly Solid&lt;/a&gt; in 2015. All slides are available for &lt;a href=&#34;https://superbloom.design/resources/OReillyUXIoTElliott.pdf&#34;&gt;download&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Our three-part series discusses how lessons from architecture school can inform IoT security.&lt;/p&gt;
&lt;h2 id=&#34;lessons-from-architecture-school-for-iot-security&#34;&gt;Lessons from architecture school for IoT security&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Part 1: &lt;a href=&#34;https://superbloom.design/learning/resources/lessons-from-architecture-school-1&#34;&gt;Start with People, in Context&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Part 2: &lt;a href=&#34;https://superbloom.design/learning/resources/lessons-from-architecture-school-2&#34;&gt;Understand Unspoken Needs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Part 3: &lt;a href=&#34;https://superbloom.design/learning/resources/lessons-from-architecture-school-3&#34;&gt;Homes Are More than Houses&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Participant Bill of Rights</title>
      <link>https://superbloom.design/learning/resources/participant-bill-of-rights/</link>
      <pubDate>Thu, 29 Jun 2017 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/participant-bill-of-rights/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Example Screener</title>
      <link>https://superbloom.design/learning/resources/example-screener/</link>
      <pubDate>Wed, 28 Jun 2017 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/example-screener/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Model Release</title>
      <link>https://superbloom.design/learning/resources/model-release/</link>
      <pubDate>Wed, 28 Jun 2017 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/model-release/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Research Consent Form</title>
      <link>https://superbloom.design/learning/resources/research-consent-form/</link>
      <pubDate>Wed, 28 Jun 2017 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/research-consent-form/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Simply Secure Style Guide</title>
      <link>https://superbloom.design/learning/resources/simply-secure-style-guide/</link>
      <pubDate>Wed, 28 Jun 2017 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/simply-secure-style-guide/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Tor Project Style Guide</title>
      <link>https://superbloom.design/learning/resources/tor-project-style-guide/</link>
      <pubDate>Wed, 28 Jun 2017 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/tor-project-style-guide/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Security is a “Design in Tech” Trend</title>
      <link>https://superbloom.design/learning/blog/security-design-in-tech/</link>
      <pubDate>Wed, 22 Mar 2017 17:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/security-design-in-tech/</guid>
      <description>&lt;p&gt;We’re honored to see Simply Secure included in the &lt;a href=&#34;https://designintechreport.wordpress.com/&#34;&gt;Design in Tech Report 2017&lt;/a&gt;. I’ve learned a lot from previous versions of the reports, which describe design trends from a business ecosystem perspective. I wrote up &lt;a href=&#34;https://superbloom.design/learning/blog/maeda-report&#34;&gt;highlights from the 2016 Report&lt;/a&gt;, and it’s exciting to see how far the industry has come in a year.&lt;/p&gt;
&lt;p&gt;John Maeda presented this year’s report on trends in design and business at the SXSW festival. Simply Secure is mentioned at 56:00 of the video.&lt;/p&gt;
&lt;p&gt;
      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/208035080?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;em&gt;John Maeda presenting the &lt;a href=&#34;https://vimeo.com/208035080&#34;&gt;Design In Tech Report 2017&lt;/a&gt; at SXSW.&lt;/em&gt;&lt;/p&gt;
&lt;h1 id=&#34;making-progress&#34;&gt;Making Progress&lt;/h1&gt;
&lt;p&gt;We still have lots of hard work ahead of us to reach the &lt;a href=&#34;https://superbloom.design/learning/blog/maeda-report&#34;&gt;vision I described&lt;/a&gt; last year of Silicon Valley shifting focus away from customer data as a commodity and toward user privacy as a core value proposition, but I’m glad to see this attention on security. Designers are urgently needed to help build products and services people trust. And there are clear connections between security and several of the other trends highlighted in the 2017 Design in Tech Report including inclusive design and voice- and chat-based interfaces.&lt;/p&gt;
&lt;h1 id=&#34;start-here&#34;&gt;Start Here&lt;/h1&gt;
&lt;p&gt;If you’re new to security, and want to start by improving your digital footprint, start by reading our &lt;a href=&#34;https://superbloom.design/learning/blog/new-year-tips&#34;&gt;Four Concrete Security Tips&lt;/a&gt;, or &lt;a href=&#34;https://medium.com/tinfoil-press/securing-your-digital-life-like-a-normal-person-a-hasty-and-incomplete-guide-56437f127425#.1g5d9s7v0&#34;&gt;Securing Your Digital Life Like a Normal Person&lt;/a&gt; by Martin Shelton. Designers getting started with security challenges can also check out &lt;a href=&#34;https://superbloom.design/learning/resources/fight-phishing&#34;&gt;How to Fight Phishing: Security for Designers&lt;/a&gt;.&lt;/p&gt;
&lt;h1 id=&#34;lets-keep-this-going&#34;&gt;Let’s Keep This Going&lt;/h1&gt;
&lt;p&gt;Simply Secure has a public Slack channel for discussing issues related to user experience, security, privacy, and design. Email &lt;a href=&#34;mailto:slack@superbloom.design&#34;&gt;slack@superbloom.design&lt;/a&gt; for an invitation.&lt;/p&gt;
&lt;p&gt;More in these interviews:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ame on &lt;a href=&#34;https://www.oreilly.com/ideas/ame-elliott-on-making-security-usable-and-delightful&#34;&gt;Making Security Usable and Delightful&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Scout on &lt;a href=&#34;https://www.oreilly.com/ideas/better-security-starts-and-ends-with-humans&#34;&gt;Better Security Starts and Ends with Humans&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Professional Knowledge and IoT</title>
      <link>https://superbloom.design/learning/blog/professional-knowledge-iot/</link>
      <pubDate>Fri, 03 Mar 2017 16:30:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/professional-knowledge-iot/</guid>
      <description>&lt;p&gt;This year&amp;rsquo;s Consumer Electronics Show (&lt;a href=&#34;http://www.ces.tech/&#34;&gt;CES ‘17&lt;/a&gt;) showcased numerous internet of things (IoT) devices but was found wanting when it came to security concerns. In his &lt;a href=&#34;https://medium.com/@scottjenson/ces-ux-of-iot-report-c75fb7f49aee#.8g0ybnegy&#34;&gt;&lt;em&gt;UX of IoT&lt;/em&gt; report from CES&lt;/a&gt;, Scott Jenson assesses that “companies really, really, REALLY want to make home automation systems,” but how can we begin to consider the ethics when developers don’t even consider security risks?&lt;/p&gt;
&lt;p&gt;IoT systems pose two security challenges. First, they can be manipulated as surveillance infrastructure to target vulnerable people. Second, insecure devices can be turned into remotely controlled networks that cause harm, such as taking websites offline. In fall 2016, malicious actors harnessed about 500,000 hacked devices such as CCTV cameras to comprise the &lt;a href=&#34;https://www.wired.com/2016/12/botnet-broke-internet-isnt-going-away/&#34;&gt;Mirai botnet&lt;/a&gt;. This botnet used distributed-denial-of-service (DDoS) attacks to take parts of the internet offline. This included Twitter and all top-level domains from the country of Liberia.&lt;/p&gt;
&lt;h2 id=&#34;understanding-risks&#34;&gt;Understanding risks&lt;/h2&gt;
&lt;p&gt;When people put IoT devices in their homes, they open themselves up to the risk that those devices could be used by a malicious actor to learn more about them. As former U.S. Intelligence Chief James Clapper &lt;a href=&#34;https://www.theguardian.com/technology/2016/feb/09/internet-of-things-smart-home-devices-government-surveillance-james-clapper&#34;&gt;has said&lt;/a&gt;, “in the future, intelligence services might use the [Internet of Things] for identification, surveillance, monitoring, location-tracking, and targeting.”&lt;/p&gt;
&lt;p&gt;Some people may not be concerned about governments spying on them, but if they enjoy using the internet, they should consider how their devices can be harnessed as bots to affect the greater good. Botnets are a direct threat to the open internet, as the cost to secure sites against such an attack is estimated at $150,000 or more per year. Since such protection is unaffordable for both individuals and most organizations, DDoS attacks are effectively a form of censorship. It’s not a far stretch to see how hacked devices could be commandeered to silence journalists.&lt;/p&gt;
&lt;h2 id=&#34;an-insights-toolkit-for-people-who-build-connected-things&#34;&gt;An insights toolkit for people who build connected things&lt;/h2&gt;
&lt;p&gt;The upsides of IoT are self-explanatory, but at Simply Secure, we want IoT systems to be built with a bias toward protecting people’s privacy. As a first step, we have been working with &lt;a href=&#34;https://wiki.mozilla.org/Open_IoT&#34;&gt;Mozilla’s Open IoT Studio&lt;/a&gt; to identify gaps in professional knowledge. Our shared goal is to assemble tools that developers can use to protect people’s privacy and the open internet.&lt;/p&gt;
&lt;p&gt;At MozFest in London and ThingsCon in Amsterdam, Simply Secure conducted research to understand participants’ priorities around IoT and privacy. We created what we call the &lt;a href=&#34;https://github.com/simplysecure/resources/tree/master/Trustworthy_IOT&#34;&gt;&lt;em&gt;Insights Toolkit for Building a Trustworthy IoT&lt;/em&gt;&lt;/a&gt;. This toolkit is meant to guide discussions that will help developers and technologists identify technologies that inspire and worry them and to learn where they can go for more information. The &lt;a href=&#34;https://github.com/simplysecure/resources/tree/master/Trustworthy_IOT&#34;&gt; toolkit&lt;/a&gt; is on GitHub and includes questions, worksheets, and other assets. It can be forked, translated into other languages, adapted, localized, and continually improved.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2017/MozFestPhotos_hu_9afcbac0d915c658.jpeg&#34; alt=&#34;Photos of study materials, such as colored bits of paper and user responses on a visual survey.
&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;br&gt;
&lt;em&gt;A workshop we facilitated at MozFest in London, where we used the &lt;em&gt;Insights Toolkit&lt;/em&gt; to understand developers’ priorities for IoT security. (October 2016)&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;top-insights-resources-and-fighting-botnets&#34;&gt;Top insights: Resources and fighting botnets&lt;/h2&gt;
&lt;p&gt;Based on discussions with about 30 developers at MozFest, the greatest challenges to get IoT developers to consider better security practices are 1) identifying reliable sources of security information (e.g., blogs) to respond to their skepticism and 2) equipping developers who are already on board with stories to convince their colleagues of the benefits of good security practices.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“Stackoverflow isn&amp;rsquo;t going to cut it for security.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Developers are curious and eager to get more information, but there is no consensus about reliable sources of security information. MozFest and ThingsCon were consistently mentioned as places where professionals expect to get information about privacy-preserving technology, but there is still a need for more specific, actionable recommendations that developers can deploy immediately. &lt;a href=&#34;http://stackoverflow.com/&#34;&gt;Stackoverflow&lt;/a&gt;, a knowledge-sharing website that is popular among developers, was mentioned as a useful resource for some questions but viewed as unreliable for security information.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“What’s the problem with using a Raspberry Pi to get a cat to come to a web cam?”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;One of the most evocative stories during our MozFest workshop was a developer whose colleague programmed a Raspberry Pi to move a mechanical arm and make a rattling noise that would summon his cat to a home video camera. This participant scoffed at the possibility that his home was vulnerable because he had not programmed any security into his device. To the colleague, this Raspberry Pi hack was a bit of harmless fun. It didn’t occur to him that his program could be manipulated by a third party either to gather private data about his home devices or to become part of a botnet that would harm other parts of the internet. When challenged about these security risks, he retorted, “it’s just scaremongering by people who want your money.”&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“It’s just scaremongering by people who want your money.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The colleague made a fair point. Both consumers and developers question the value of privacy due to the assumption that companies manufactured concerns to increase sales of security products. For years, marketing teams told consumers that antivirus products were essential for their computers. However, research reports such as Google’s &lt;a href=&#34;https://security.googleblog.com/2015/07/new-research-comparing-how-security.html&#34;&gt;comparison of experts’ and novices’ behavior&lt;/a&gt; for online safety showed that experts don’t consider antivirus protection to be an important element of security. Those kinds of mixed messages can make people distrustful.&lt;/p&gt;
&lt;h2 id=&#34;conclusion-building-professional-knowledge&#34;&gt;Conclusion: Building professional knowledge&lt;/h2&gt;
&lt;p&gt;There is a lot of commercial hype about IoT applications (brilliantly skewered by the &lt;a href=&#34;https://twitter.com/internetofshit&#34;&gt;Internet of Shit Twitter&lt;/a&gt; account). Developers who want to build their professional reputations intensify the hype in their eagerness to master new frameworks and APIs. From their vantage point, privacy advocates bring an unwelcoming message that quashes good-natured enthusiasm for building new things. However, no one doubts that IoT devices can benefit society in many ways (i.e., saving energy and conserving natural resources). The challenge for people who care about an ethical IoT is to support developers in building things they want to build by incorporating security practices into their workflows.&lt;/p&gt;
&lt;p&gt;Simply Secure’s initial research indicates that developers can be skeptical of security claims and unsure where to go for accurate technical advice. At Simply Secure, we want to distribute open resources to help developers do their best work while preserving privacy for IoT applications and beyond. If you’re working on an IoT project, use our &lt;a href=&#34;https://github.com/simplysecure/resources/tree/master/Trustworthy_IOT&#34;&gt;Trustworthy IoT toolkit&lt;/a&gt; to build awareness with your colleagues about security.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Initial Usable Security Methodology</title>
      <link>https://superbloom.design/learning/resources/initial-usable-security-methodology/</link>
      <pubDate>Wed, 01 Mar 2017 00:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/resources/initial-usable-security-methodology/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Four Concrete Security Tips for the New Year</title>
      <link>https://superbloom.design/learning/blog/new-year-tips/</link>
      <pubDate>Thu, 26 Jan 2017 15:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/new-year-tips/</guid>
      <description>&lt;h2 id=&#34;in-november-i-had-the-opportunity-to-speak-at-the-oreilly-security-conference-in-new-york-city&#34;&gt;In November, I had the opportunity to speak at the &lt;a href=&#34;https://conferences.oreilly.com/security/network-data-security-ny/public/schedule/detail/55105&#34;&gt;O’Reilly Security Conference&lt;/a&gt; in New York City.&lt;/h2&gt;
&lt;p&gt;I shared a number of insights that we have discussed here on the Simply Secure blog, including findings from Ame’s &lt;a href=&#34;https://superbloom.design/resources/techreports/NYC15-MobMsg.pdf&#34;&gt;New York City study&lt;/a&gt; on privacy for mobile messaging.&lt;/p&gt;
&lt;p&gt;I also sat down with &lt;a href=&#34;https://www.oreilly.com/people/0d2c1-mac-slocum&#34;&gt;Mac Slocum&lt;/a&gt; to talk about the importance of human factors in security (you can watch the interview &lt;a href=&#34;https://www.oreilly.com/ideas/better-security-starts-and-ends-with-humans&#34;&gt;here&lt;/a&gt;). Our conversation focused on security from a software developer’s perspective, advice on how to make tools more human-centric (e.g., talk to your actual users), and perspectives on big challenges in security (e.g., the Internet of Things).&lt;/p&gt;
&lt;p&gt;However, most people aren’t security-focused software developers and aren’t intimately familiar with the technology that can help protect their online data. If you’re a UX expert and interested in learning more about security and privacy, your own digital footprint is a great place to start. Here are some concrete steps that you and your loved ones can take in the new year.&lt;/p&gt;
&lt;h3 id=&#34;steps-for-better-privacy--security&#34;&gt;Steps for better privacy &amp;amp; security&lt;/h3&gt;
&lt;p&gt;As I have &lt;a href=&#34;https://superbloom.design/learning/resources/not-binary-properties&#34;&gt;said before&lt;/a&gt;, security isn’t a binary property. Unlike Santa’s clear-cut naughty vs. nice list, the analysis of whether a system or app is secure has many shades of gray. Different people worry about different threats to their data; to use security terminology, everyone has their own threat model. To help you thoroughly consider the risks facing your data, the suggestions below dissect the kinds of threat each tip is meant to protect against.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2017/google-2fa-garden_hu_3a7d4cae62a27d22.jpg&#34; alt=&#34;Illustration showing Google product icons behind both a gated fence and a high-tech locked forcefield bubble.&#34; width=&#34;740&#34; height=&#34;378&#34;&gt;

&lt;em&gt;Two-factor authentication adds an extra layer of security to your account by requiring both your password and a second bit of information to sign in. Image from Google’s &lt;a href=&#34;https://www.google.com/landing/2step/&#34;&gt;2-step verification page&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;1-use-two-factor-authentication&#34;&gt;1. Use two-factor authentication&lt;/h3&gt;
&lt;p&gt;Whether it’s called &lt;a href=&#34;https://www.google.com/landing/2step/&#34;&gt;two-step verification&lt;/a&gt;, &lt;a href=&#34;https://www.facebook.com/help/148233965247823&#34;&gt;login approvals&lt;/a&gt;, or &lt;a href=&#34;https://support.twitter.com/articles/20170388&#34;&gt;login verification&lt;/a&gt;, two-factor authentication requires you to have both your password and a “second factor” before you can sign in to your account. In most cases, this second factor is a code generated on your mobile phone or sent to you as an SMS message, but some systems (including Google, Dropbox, and Github) support special &lt;a href=&#34;https://www.yubico.com/start/&#34;&gt;USB devices&lt;/a&gt; or voice calls.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Protects against:&lt;/strong&gt; Two-factor authentication prevents an attacker who has access to your password from gaining access to your account. You don’t have to be a famous person or have especially sensitive data to be a target of this kind of attack; most victims are everyday people. The vast majority of the online public would benefit from using two-factor authentication, especially for their email account, which can serve as a gateway to all their other accounts. If you are an activist or person facing dedicated attackers, it is even more essential that you sign up as many accounts as possible – and that you generate codes on your phone rather than receive them via SMS.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Words of caution:&lt;/strong&gt; If you lose your phone or second factor, be prepared, as it may take up to a week or more to regain access to some accounts. Many services provide a set of single-use codes that you can print out and save for emergencies. Tucking them into your sock drawer is generally sufficient, but if you’re worried about targeted threats, you might consider writing them down by hand in a place that is harder for others to find.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2017/1password-meter_hu_faba756d061e3239.png&#34; alt=&#34;Screenshots of a password-generation interface, one where strength meter is low and one where the strength meter is high.&#34; width=&#34;740&#34; height=&#34;398&#34;&gt;

&lt;em&gt;1Password is one of the more reputable password managers. In addition to following best practices around security (the company has collaborated in a number of &lt;a href=&#34;https://support.1password.com/security-assessments/&#34;&gt;third-party audits&lt;/a&gt; and &lt;a href=&#34;https://1password.com/files/1Password%20for%20Teams%20White%20Paper.pdf&#34;&gt;documented&lt;/a&gt; the application’s security architecture publicly), it features handy details like a password generator with an engaging strength meter. Screenshot from 1Password 6.5.3.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;2-use-a-password-manager&#34;&gt;2. Use a password manager&lt;/h3&gt;
&lt;p&gt;I was a late convert to using a password manager. I thought that my own schemes for remembering passwords (and in some cases, reusing them for low-value sites) were sufficient. But at a certain point – after a big data breach became public or almost falling for a phishing attempt – I realized that I needed to admit my limitations. I now recommend &lt;a href=&#34;https://1password.com/&#34;&gt;1Password&lt;/a&gt; to my friends and family. The default is their cloud-based version, which allows you to easily sync passwords across devices. As of this writing, they also offer versions for teams and for families as well as a non-synced edition for a flat license fee.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Protects against:&lt;/strong&gt; Password managers make it easy for you to use long, complex passwords that are hard for attackers to crack. They also allow you to use a unique password for every site or application, which makes it impossible for an attacker to use a data breach on one platform to compromise your data on another. Finally, they make it less painful to change your password if a breach happens. They thus protect you from malicious attackers seeking to gain access to your personal information online through a compromised password. Again, most attacks against passwords aren’t targeted at famous people but common members of the population. Even your “low value” accounts, such as old social media profiles or email addresses, are worth protecting. Attackers often use them to try and extort money from your friends or to harvest personal information that they can then use in attacking a higher-value target.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Words of caution:&lt;/strong&gt; Don’t use the first free password manager you come across. If you use a cloud-based password manager, try to avoid accessing it from a public computer that may be infected with spyware, such as one in an internet café or a hotel business center. If you are in a pinch and have to do so, change your vault password (the password that you use to unlock your password manager) as soon as you can get to your own computing device. If you are an activist who is worried that your government might be able to compel the password management company to share your data, consider using a version that isn’t based in the cloud. For example, since &lt;a href=&#34;http://keepass.info/&#34;&gt;KeePass&lt;/a&gt; is an open-source password manager built by a decentralized, borderless community of developers, it would be hard to legally compel them to share your data.&lt;/p&gt;
&lt;h3 id=&#34;3-lock-and-encrypt-your-devices&#34;&gt;3. Lock and encrypt your devices&lt;/h3&gt;
&lt;p&gt;When you turn on or wake up your computer or phone, do you use a password, PIN, pattern, or fingerprint to sign in? If not, even casual attackers can get access to your data when left alone with your device for just a few moments. While having to unlock your screen multiple times per day can be annoying, it is an important protective step for many people. Similarly, encrypting your device’s long term storage (e.g., its hard drive) prevents slightly more dedicated attackers from stealing your data by plugging it into their computer and scanning it. This method can allow them to access even devices that have a screen lock.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Protects against:&lt;/strong&gt; Screen locks prevent would-be attackers from getting into your device when they have physical access to it. This includes cases where you forgot your phone in a taxi or where your computer was stolen from your home. It may also include cases where your device is in a locked environment that others have access to, such as a locked hotel room, or during targeted searches such as at international border crossings. Encryption also protects against more dedicated attacks by people who have physical access to your device for an extended period of time. With the important caveat noted below, both device encryption and screen locks pose very little downside and significant upside.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Words of caution:&lt;/strong&gt; If you encrypt your device, it’s important to write down the password, PIN, or pattern you use to unlock it in a safe place. Losing access to your unlock code means that you permanently lose access to the data on the device. If you are worried about targeted in-person threats, screen locks that employ codes or passphrases may be a better choice than fingerprints, as there’s evidence that biometric readers &lt;a href=&#34;http://www.theverge.com/2016/5/2/11540962/iphone-samsung-fingerprint-duplicate-hack-security&#34;&gt;can be fooled&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2017/windows-update-notification_hu_850b0aaeef10b8f6.jpg&#34; alt=&#34;Screenshot of a dialog box prompting the user to install a Windows update.&#34; width=&#34;740&#34; height=&#34;424&#34;&gt;

&lt;em&gt;It’s easy to ignore update notifications when you’re busy. Don’t postpone them for too long! Screenshot by &lt;a href=&#34;https://www.flickr.com/photos/mynetx/4758472876&#34;&gt;mynetx&lt;/a&gt;, &lt;a href=&#34;https://creativecommons.org/licenses/by-sa/2.0/&#34;&gt;CC BY-SA 2.0&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;4-install-updates&#34;&gt;4. Install updates&lt;/h3&gt;
&lt;p&gt;Writing software is a human process, which means that all software can have flaws. Software updates decrease the likelihood of your data falling prey to known vulnerabilities. Just as a homeowner regularly changes the batteries on a smoke detector and cleans out the gutters, it’s important to make sure the devices and software you rely on have up-to-date software and firmware. This includes your phone and computer operating systems, your web browser, and your apps. It also includes smart TVs, game consoles, and routers. If you’re not sure how to tell whether something is up to date, a web search for “check to see whether [product name] is up to date” often yields good instructions.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Protects against:&lt;/strong&gt; Software updates protect against digital attacks that target known vulnerabilities. These can be manual, such as a malicious hacker trying to steal your data, or automated attacks, including worms that jump from device to device. Once again, these attacks aren’t designed just for famous or powerful people but anyone who has devices on the internet.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Words of caution:&lt;/strong&gt; Make sure that you’re using the official channel to get authentic software updates. Don’t download updates from links that you see in emails, which may be phishing attacks, or in online advertisements, which may be vectors for malware infection.&lt;/p&gt;
&lt;h2 id=&#34;more-resources&#34;&gt;More resources&lt;/h2&gt;
&lt;p&gt;The beginning of a new year is always a great time to pick up new habits and new knowledge. For some additional guides on getting started with privacy- and security-conscious practices, check out &lt;a href=&#34;https://medium.com/@mshelton&#34;&gt;Martin Shelton’s Medium stream&lt;/a&gt;. To learn more about the big picture of protecting your data from surveillance, which can be especially important if you’re an activist or someone who might be subject to particular scrutiny by your government, check out &lt;a href=&#34;https://ssd.eff.org/en&#34;&gt;EFF’s site on surveillance self-defense&lt;/a&gt;. Many of its resources are also useful for everyday people, too, such as its overview animation on &lt;a href=&#34;https://ssd.eff.org/en/module/animated-overview-using-password-managers-stay-safe-online&#34;&gt;password managers&lt;/a&gt; or its tutorial on &lt;a href=&#34;https://ssd.eff.org/en/module/how-encrypt-your-iphone&#34;&gt;encrypting your iPhone&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Are you a designer or UX researcher interested in learning more and integrating a greater awareness of privacy and security into your practice? &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;Join our&lt;/a&gt; Slack community!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Essential Non-technical Skills for Working in Security</title>
      <link>https://superbloom.design/learning/blog/nontechnical-security-skills/</link>
      <pubDate>Fri, 16 Dec 2016 15:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/nontechnical-security-skills/</guid>
      <description>&lt;p&gt;There’s a misconception that highly technical skills like cryptography are required to work in security. That’s not true. With critical threats to internet freedom and individual privacy, there is an urgent need for &lt;em&gt;designers&lt;/em&gt; to get involved with security projects.&lt;/p&gt;
&lt;p&gt;UX designers are an important part of reframing the conversation about security. Instead of assuming that security’s UX needs to start with ways to discourage undesirable behavior, we should start from a positive mindset of elucidating its benefits to users. Here are three ways that non-technical UX skills can improve security.&lt;/p&gt;
&lt;h2 id=&#34;privacy-as-part-of-a-brand-promise&#34;&gt;Privacy as part of a brand promise&lt;/h2&gt;
&lt;p&gt;Copywriters and brand strategists have a role to play in protecting privacy, so think of their skills as part of the UX toolbox. Canadian VPN TunnelBear uses gentle humor and illustrations to convey the benefits of security to customers. Instead of the militaristic language of defensive cyber-security, TunnelBear communicates a warm but firm commitment to privacy.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/tunnelbear_hu_e67ec425697aacd7.jpg&#34; alt=&#34;Screenshot of the TunnelBear website, which describes its security and privacy benefits in detail.&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;

&lt;em&gt;Description from the TunnelBear.com website&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Other places where skilled writing can communicate how your service protects privacy include the product description in app stores and during new feature updates.&lt;/p&gt;
&lt;h2 id=&#34;service-design-for-two-factor-authentication&#34;&gt;Service design for two-factor authentication&lt;/h2&gt;
&lt;p&gt;Composing messages and notifications is hard, but instead of being generic and detached, copywriters can cultivate a more personable presence.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/smart-oven_hu_5b424cac011666d1.jpg&#34; alt=&#34;Screenshots of a smart oven companion app. There are lots of notifications, many of which are contradictory or hard to understand.&#34; width=&#34;740&#34; height=&#34;664&#34;&gt;

&lt;em&gt;Image from Mark Wilson’s &lt;a href=&#34;https://www.fastcodesign.com/3065667/this-1500-toaster-oven-is-everything-thats-wrong-with-silicon-valley-design&#34;&gt;review&lt;/a&gt; of the June oven in Fast Company&lt;/em&gt;&lt;br&gt;
&lt;em&gt;These notifications from an IoT oven (which have since been rewritten) show just how difficult it is to write copy for an alert&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Coming at security from a &lt;a href=&#34;https://en.wikipedia.org/wiki/Service_design&#34;&gt;service-design&lt;/a&gt; lens would improve the UX of two-factor authentication (2FA), which adds an extra layer of protection beyond a password. For example, Google accounts with 2FA enabled will send a code to users’ phones. But these messages are a missed opportunity to build a relationship with users who are taking positive steps to protect their privacy.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/google-2fa-messages_hu_2a07fb5de8bcd045.PNG&#34; alt=&#34;Screenshot showing a series of messages containing authentication codes from Google.&#34; width=&#34;740&#34; height=&#34;1312&#34;&gt;

&lt;em&gt;Google’s periodic text messages for 2FA codes&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Interrupting people’s workflow when they are trying to access their accounts isn’t ideal, but 2FA messages are an overlooked touch point. Considering the rise of SMS chatbots, these messages could be opportunities to applaud people for secure behavior or to act as a concierge for security practices. For example, it might answer questions such as “How do I make sure my router has the latest security patches?” or “Are other people getting a warning when they try to login to the Bank of America website?”&lt;/p&gt;
&lt;h2 id=&#34;interaction-design-to-communicate-system-behavior&#34;&gt;Interaction design to communicate system behavior&lt;/h2&gt;
&lt;p&gt;Visual design and animation are powerful mechanisms for communicating how systems work. Giving users insight into messaging systems could increase demand for privacy-preserving systems. For example, messaging systems such as Facebook use an animated graphic to let users know that someone is typing a comment, thereby making an invisible action visible. What kinds of new graphics could convey that a message has been encrypted? Or delivered? Or expose where the data are stored?&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/writing-a-comment_hu_18effeb3fba31b85.jpg&#34; alt=&#34;Screenshot of a notification from Facbook that reads: A friend is writing a comment&amp;hellip;&#34; width=&#34;740&#34; height=&#34;355&#34;&gt;

&lt;em&gt;Facebook use an animated graphic to indicate when someone else is typing a comment&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Many apps, including WhatsApp and iOS iMessage, use read receipts to reveal that someone has seen a message. These simple visual vocabularies are powerful in communicating how the system works. iMessage displays the words “read” and “delivered” to indicate status while WhatsApp uses check marks to indicate if the message has been seen.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/whatsapp-chat_hu_c2a8082f33dbbf37.PNG&#34; alt=&#34;Screenshot of the WhatsApp chat interface&#34; width=&#34;740&#34; height=&#34;1312&#34;&gt;

&lt;em&gt;WhatsApp uses two check marks to indicate that both the sender and receiver have seen the message&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Read receipts demonstrate how UX can change and normalize new behaviors. In the past, users who didn’t have time to respond to text messages could still read them. Now, users who don’t know that they can disable read receipts may avoid opening WhatsApp until they have the time to respond. This way, they can maintain plausible deniability for a slow response time. Designers can help users develop behaviors that protect their security and privacy in a similar fashion.&lt;/p&gt;
&lt;p&gt;For example, the Google Chrome team takes UX seriously and has done &lt;a href=&#34;https://www.usenix.org/conference/soups2016/technical-sessions/presentation/weinberger&#34;&gt;research&lt;/a&gt; on how the visual design of browser warnings impacts user behavior. The browser currently displays a neutral “information” icon for sites that don’t support encryption, or that have problems with their encryption. The team has announced that this will change to a scarier, more prominent &lt;a href=&#34;https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html&#34;&gt;warning icon&lt;/a&gt; next month; they are using this as an opportunity to engage users in understanding risks to their security.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/chrome-warning_hu_45b24250e09a1205.jpg&#34; alt=&#34;Screenshot of the Chrome browser showing an icon in the URL bar which consists of an i with a circle around it. A menu extends from the icon and contains a variety of information about the webpage.&#34; width=&#34;740&#34; height=&#34;838&#34;&gt;

&lt;em&gt;Chrome currently warns users that they are visiting an insecure site with an information icon&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;security-and-positive-design&#34;&gt;Security and positive design&lt;/h2&gt;
&lt;p&gt;Security teams often have a reputation for saying “no” because they think that the best way to protect users is to limit their behavior. But a good UX can also impress the benefits of security upon users through an affirmative approach. Non-technical UX skills such as brand strategy, copywriting, and visual design all have pivotal roles to play in helping people protect their privacy.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Fighting Phishing in the Browser: Security for Designers</title>
      <link>https://superbloom.design/learning/resources/fighting-phishing-browser/</link>
      <pubDate>Fri, 28 Oct 2016 14:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/fighting-phishing-browser/</guid>
      <description>&lt;p&gt;My previous posts (&lt;a href=&#34;https://superbloom.design/learning/resources/one-phish-two-phish&#34;&gt;part one&lt;/a&gt; and &lt;a href=&#34;https://superbloom.design/learning/resources/fight-phishing&#34;&gt;part two&lt;/a&gt;) explored what phishing attacks are and ways that designers can help prevent their products from becoming a target. In this post, I’d like to examine some more technical countermeasures. If you’re a designer interested in fighting phishing, this can be useful background information, and it can help prepare you for discussions with your more technical teammates. I also hope this post will highlight that current technical solutions alone are not enough to help users fight phishing.&lt;/p&gt;
&lt;h2 id=&#34;how-browser-companies-fight-phishing&#34;&gt;How browser companies fight phishing&lt;/h2&gt;
&lt;p&gt;Web-browser companies work hard to fight phishing. Services such as the &lt;a href=&#34;https://en.wikipedia.org/wiki/Google_Safe_Browsing&#34;&gt;Safe Browsing initiative&lt;/a&gt; provide a continually updated catalog of probable phishing sites and help users of Chrome, Firefox, and Safari avoid them. These browsers pop up a warning message when users navigate to a site in the catalog. Some anti-virus companies provide software that performs a similar function. These services work best against phishing sites that have been around for a few hours or days but are less effective for ones that just launched or that target a limited number of high-value users (such as the spear phishing attacks I described in my first post).&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/ff-phishing-warning_hu_449e369dba191e47.png&#34; alt=&#34;Screenshot of an eye-catching browser warning.&#34; width=&#34;740&#34; height=&#34;363&#34;&gt;

&lt;em&gt;An example of Firefox’s phishing warning for a site that was registered on the Safe Browsing blacklist. Adapted from &lt;a href=&#34;https://www.flickr.com/photos/pejrm/6481288929&#34;&gt;this image&lt;/a&gt; by &lt;a href=&#34;https://www.flickr.com/photos/pejrm/&#34;&gt;Paul Jacobson&lt;/a&gt;, which was released under a &lt;a href=&#34;https://creativecommons.org/licenses/by-nc-sa/2.0/&#34;&gt;CC BY-NC-SA 2.0&lt;/a&gt; license.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In considering the browser’s efforts to protect users, one common misconception is that the lock icon in the URL bar communicates the authenticity of a website. For example, some people might think that a lock next to a URL containing the word “Amazon” means that you’re viewing a page legitimately owned by Amazon.com. In fact, the lock symbol is meant to convey whether the connection between your computer and the web server is encrypted. It’s entirely possible for the creator of a phishing site to set up encryption on a bogus site, so relying on the presence of a lock icon alone can’t keep you from falling for an attack.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/https-lock_hu_c9d87c04ee5dea43.png&#34; alt=&#34;Image of a green lock and https prompt.&#34; width=&#34;740&#34; height=&#34;200&#34;&gt;

&lt;em&gt;While reassuring, a lock icon in the URL of a browser does necessarily mean that the site in question is legitimate.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Although the lock itself isn’t necessarily meaningful in the fight against phishing, the information you get when you click on it can be if you know what to look for. For most modern web browsers, clicking on the lock will show you security details about the site, including information about its &lt;a href=&#34;https://en.wikipedia.org/wiki/SSL_certificate&#34;&gt;SSL certificate&lt;/a&gt;. This certificate includes information about the organization’s name, its location, and what website(s) are affiliated with it. In theory, these certificates are only issued to an organization after a &lt;em&gt;certification authority&lt;/em&gt; such as &lt;a href=&#34;https://letsencrypt.org/&#34;&gt;Let&amp;rsquo;s Encrypt&lt;/a&gt; or &lt;a href=&#34;https://www.entrust.com/ssl-certificates/&#34;&gt;Entrust&lt;/a&gt; verifies these aspects of its identity. When the identify-verification process works well, it means that someone pretending to be Amazon.com Inc. and located in Seattle, WA will be prevented from getting an SSL certificate tying their website to that company’s name and location.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/ssl-certificate-view_hu_1d6d602acfc17434.png&#34; alt=&#34;Screenshot of a SSL certificate, composed of data fields with values indicating that the certificate belongs to the Bank of America.&#34; width=&#34;740&#34; height=&#34;723&#34;&gt;

&lt;em&gt;The SSL certificate I received when viewing Bank of America’s website. It is issued by the Symantec Corporation’s “certification authority” and has a specific assurance level.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In practice, the process can be very messy and subject to corruption or subversion. This was the case in 2011 when the webmail of up to 300,000 Iranians was compromised after a &lt;a href=&#34;http://www.theregister.co.uk/2011/09/06/diginotar_audit_damning_fail/&#34;&gt;certification authority was hacked&lt;/a&gt;. By issuing fraudulent SSL certificates, the attackers were able to more accurately impersonate domains such as gmail.com, compromise a number of Iranian users’ credentials, and spy on them. Even sophisticated users were fooled.&lt;/p&gt;
&lt;p&gt;When the classic certificate-based system fails, there are newer lines of defense such as &lt;a href=&#34;https://en.wikipedia.org/wiki/HTTP_Public_Key_Pinning&#34;&gt;key pinning&lt;/a&gt; and &lt;a href=&#34;https://www.certificate-transparency.org/&#34;&gt;certificate transparency&lt;/a&gt;. Key pinning is a browser feature to verify that the SSL certificates for a company&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Blink and You’ll Miss It: Notifications in an AI World</title>
      <link>https://superbloom.design/learning/resources/notifications-in-ai/</link>
      <pubDate>Thu, 13 Oct 2016 17:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/notifications-in-ai/</guid>
      <description>&lt;p&gt;I’ve been enjoying the videos from &lt;a href=&#34;#&#34;&gt;AI Now&lt;/a&gt;, an exploration of artificial intelligence and ethics hosted by the U.S. White House and NYU’s Information Law Institute. Co-chairs Kate Crawford and Simply Secure co-founder Meredith Whittaker put together a program focused on issues of social inequality, labor, and ethics in artificial intelligence.&lt;/p&gt;
&lt;h2 id=&#34;ai-inspiration&#34;&gt;AI inspiration&lt;/h2&gt;
&lt;p&gt;Looking at the program through a UX design lens, there were abundant design opportunities to make AI systems more effective, transparent, and fair. For example, Human-Computer Interaction pioneer Lucy Suchman called for the demystification of artificial intelligence in the video below.&lt;/p&gt;
&lt;p&gt;&lt;div style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
      &lt;iframe allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen&#34; loading=&#34;eager&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; src=&#34;https://www.youtube.com/embed/ilKPYH94JSg?start=1650?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0&#34; style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; title=&#34;YouTube video&#34;&gt;&lt;/iframe&gt;
    &lt;/div&gt;

Lucy Suchman’s presentation from the AI Now plenary begins at 27:30.&lt;/p&gt;
&lt;p&gt;Suchman also showed two photos side-by-side, one of an elderly woman with her caregiver and the other of an elderly man with a robot caregiver. She described the ways in which the human caregiver dynamically orients herself to the elderly woman whereas the robot cannot do the same. To me, her example illuminated how a human-centered design approach could offer improvements in the way robot caregivers interact with their human patients. One way to put Suchman’s observations to work is to design the robot with longer arms so that the man doesn’t need to lean so far forward to reach it.&lt;/p&gt;
&lt;h2 id=&#34;notifications-as-a-ux-challenge&#34;&gt;Notifications as a UX challenge&lt;/h2&gt;
&lt;p&gt;Beyond hardware, there are many design opportunities for software as well, one of which is the ethical design of on-screen interfaces for AI interactions. I encourage you to read the entire &lt;a href=&#34;https://assets.ctfassets.net/8wprhhvnpfc0/3JOy5k4f1YSCQOi8MCCmA2/97010d04fbc7892662ce8b2469dc1601/AI_Now_2016_Report.pdf&#34;&gt;AI Now summary report&lt;/a&gt;. In particular, the following recommendation stood out as a clear opportunity for design.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Support research to develop the means of measuring and assessing AI systems’ accuracy and fairness during the design and deployment stage. Similarly, support research to develop means of measuring and addressing AI errors and harms once in ­use, including &lt;em&gt;accountability mechanisms involving notification&lt;/em&gt;, rectification, and redress for those subject to AI systems’ automated decision making.&lt;/strong&gt;
– from The AI Now Report: The Social and Economic Implications of Artificial Intelligence Technologies in the Near-Term (emphasis mine)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Notification is critical to helping people understand how their data are accessed and used, but the UX of notification is a hard design problem. On mobile phones, managing notifications is complex. Let’s begin with a few relatively inconsequential examples from everyday apps.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/Notification-examples.001_hu_ad3eec1e8f91ec0a.jpeg&#34; alt=&#34;iOS notifications from food delivery service Foodora and language learning app Duolingo&#34; width=&#34;740&#34; height=&#34;635&#34;&gt;

iOS notifications from food delivery service Foodora and language learning app Duolingo&lt;/p&gt;
&lt;p&gt;These notifications sit on the border between being useful and being spam. My phone is set up to get very few notifications, but when I was experimenting with location-based services, I was flooded with spam notifications. Frequent notifications that [someone I barely know] is going to [an event I don’t care about] at [a time when I’m preoccupied] were frustrating.&lt;/p&gt;
&lt;p&gt;Even without sophisticated context detection, these apps seem to be using the intersection of my past behaviors and the time to make inferences. For example, I might flinch when Foodora thinks that I’m at home and craving pizza at 8 P.M. on a Saturday night, but I can’t dispute that my order history makes it a reasonable assumption.&lt;/p&gt;
&lt;p&gt;A better example of accounting for past behavior when designing notifications is Duolingo’s reminder feature. You can set reminder notifications in Duolingo, but if you don’t log in after receiving alerts over several days, Duolingo will cease to send them. Duolingo’s designers predicted that I might ignore the alerts and then designed for it. Many other spam creators could learn from Duolingo’s approach.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/StopAlerts_hu_b99598ec11d7cac2.jpg&#34; alt=&#34;Alert from Duolingo, saying: These reminders don&amp;rsquo;t seem to be working. We&amp;rsquo;ll stop sending them for now.&#34; width=&#34;740&#34; height=&#34;236&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;ux-for-user-control&#34;&gt;UX for user control&lt;/h2&gt;
&lt;p&gt;Notifications are invitations to interact with systems. They suggest that an app or process needs the user’s attention. Consider the iPhone’s settings for managing alerts. On a per-app basis, users can control which kind of notifications they want to see and how they want to see them. At first glance, it may seem like fine-grained control, but this style of notification control is already at the end of its utility.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/notification-control-panel.001_hu_e41a6962776d135f.jpeg&#34; alt=&#34;iOS notifications settings. Left: list of applications that generate notifications. Right: controls for an individual application.&#34; width=&#34;740&#34; height=&#34;635&#34;&gt;

iOS notifications settings. Left: list of applications that generate notifications. Right: controls for an individual application.&lt;/p&gt;
&lt;p&gt;Instagram notifications for popular accounts expose how the current UX can’t scale. Notifications work fine as long as an Instagrammer has a bounded number of followers, but the below video shows how overwhelming notifications can become when an account has 8 million followers. The account holder behind &lt;a href=&#34;https://www.instagram.com/433/?hl=en&#34;&gt;@433&lt;/a&gt;, a popular soccer Instagram account, captured what it’s like to receive so many notifications. Since posting the video, @433 has accrued another 4 million followers.&lt;/p&gt;
&lt;div style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
      &lt;iframe allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen&#34; loading=&#34;eager&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; src=&#34;https://www.youtube.com/embed/zGl796352RI?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0&#34; style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; title=&#34;YouTube video&#34;&gt;&lt;/iframe&gt;
    &lt;/div&gt;

&lt;p&gt;Overwhelming Instagram alerts for accounts with many followers demonstrate challenges in scaling notifications.&lt;/p&gt;
&lt;h2 id=&#34;towards-ux-for-ai&#34;&gt;Towards UX for AI&lt;/h2&gt;
&lt;p&gt;In my examples, getting alerts to order food, use a language app, or interact with Instagram followers may be annoying, but the consequences of ignoring them are relatively minor. Skeptics might suggest management strategies such as not using annoying apps or having fewer followers, but people will have no choice but to use some AI systems. For some applications such as credit scoring or medical care, the consequences of ignoring a notification may be drastic, even life-or-death. As part of a larger ecosystem, poor app notification practices by less “consequential” apps threaten the utility of notifications overall. If your notifications feed is crowded with spam about your Instagram followers, you’re bound to miss a critical health alert or two.&lt;/p&gt;
&lt;p&gt;Privacy, ethics, and consent come into play when considering scenarios such as how to alert people to automatic facial recognition in public places. Just as we have “video surveillance in use” signs, a design suggestion I have encountered is for cameras to broadcast their presence to anyone within their recording radius. The alert could also invite people to interact with the recorded data. There are already numerous challenges across law, economics, and hardware manufacturing that make this unrealistic. Even if we set those aside, when drones with cameras are as small as bugs, a person could be on tens of thousands of cameras at once. It would trigger a notification nightmare akin to Instagrammer @433’s video.&lt;/p&gt;
&lt;p&gt;Mobile alert mechanisms aren’t designed for users to interact comfortably with a high volume of notifications. Without better UX, people can’t be effectively notified of how their faces are being recognized and the different ways their data are being used. What if they are misrecognized once in a thousand times? How would they wade through all the messages to identify and rectify the error? A poor UX will limit people’s ability to hold systems accountable.&lt;/p&gt;
&lt;p&gt;Without better notifications, people will not be able to identify misjudgments by automated systems and redress them, and this has potentially devastating personal consequences.&lt;/p&gt;
&lt;h2 id=&#34;challenges-for-tomorrows-designers&#34;&gt;Challenges for tomorrow’s designers&lt;/h2&gt;
&lt;p&gt;The social, economic, and ethical implications of AI systems are critically important, and as designers, we must push the frontiers of UX to accommodate these new and proliferating systems. UX for AI is an emerging field, and we need to reimagine training and support for designers who are building their professional practice in this area. What projects are doing a good job at UX for AI or notifications in general? Let us know at &lt;a href=&#34;mailto:contact@simplysecure.org&#34;&gt;contact@simplysecure.org&lt;/a&gt; or tweet us @simplysecureorg&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>How to Fight Phishing: Security for Designers</title>
      <link>https://superbloom.design/learning/resources/fight-phishing/</link>
      <pubDate>Fri, 30 Sep 2016 15:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/fight-phishing/</guid>
      <description>&lt;p&gt;My &lt;a href=&#34;https://superbloom.design/learning/resources/one-phish-two-phish&#34;&gt;last post&lt;/a&gt; examined the concept of phishing, which is a type of social-engineering attack to con people into divulging private information like passwords or credit card numbers. &lt;/p&gt;
&lt;p&gt; When you look for advice on how to protect against phishing, most of what you’ll find is tired wisdom such as “check the email carefully” or “never click on links in emails.” This type of advice assumes that the burden is entirely on would-be victims to protect themselves. While there are important steps that everyone should take, design and security professionals must do more than simply blame users. &lt;/p&gt;
&lt;p&gt;In this post we’ll examine some things that you can do to fight phishing and help your users develop healthy security habits. In a future post, we will explore some of the technical ways web browsers do the same.&lt;/p&gt;
&lt;h2&gt;How designers and front-end devs can help&lt;/h2&gt;
&lt;p&gt;Phishing isn’t just a technical problem, it’s a human problem. Here are some concrete human-centered tips for fighting phishing. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1. Consistently polish your designs. &lt;/strong&gt;One simple action is to make sure that the UX of your organization’s emails and websites are consistently polished. While this is not foolproof (it’s easy for a phisher to hire an unethical designer to replicate what you do), polished designs raise the bar for phishers and make it easier for users to recognize poorly-crafted impersonations. Make sure that not just the welcome email and the homepage are refined and on-brand but also lesser-used designs such as those for password resets. Defining and adhering to a formal &lt;a href=&#34;https://superbloom.design/learning/blog/style-guide&#34;&gt;style guide&lt;/a&gt; can help you maintain consistent polish. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/password-reset_hu_34c2c34b48019c42.png&#34; alt=&#34;Mockup of two password-reset pages, one that has a polished design and one that does not.&#34; width=&#34;740&#34; height=&#34;281&#34;&gt;

&lt;em&gt;It’s harder for users to fall for a phishing attempt if they’re used to seeing refined designs everywhere (left) than if they are used to seeing the occasional page whose design has been neglected (right).&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2. Consider the habits you encourage.&lt;/strong&gt; Many social-network companies use email updates to increase user engagement. These emails can unintentionally condition users to click on links that will prompt them to sign in. For example, Facebook sends me an email whenever someone tags me in a post or photo (it’s possible that newer users of the service have to opt in to these notifications), and this has habituated me to seeing notifications in my inbox. It would be easy for a phisher to lull me in by crafting an attack based on this message. If the linked page mimicked the real Facebook site, I might end up falling for the attack. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/fb-email_hu_4295ef9dcad1cf7d.png&#34; alt=&#34;An example email notification from Facebook.&#34; width=&#34;740&#34; height=&#34;355&#34;&gt;

&lt;em&gt;Email messages like these train users to click on links and sign in to their account on the web page that pops up. Phishers can easily craft a message that takes advantage of this habit.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3. Tell users what you don’t do. &lt;/strong&gt;Emails from financial institutions frequently append anti-phishing boilerplate to their emails. While these additions communicate important information about things that the bank will never do (in particular, ask for sensitive information over email), few users probably ever read or learn from them. Work with your design team to brainstorm ways to communicate this information more clearly. For example, would it make sense to send a brief and engaging email to your users on an annual basis? Are there opportunities to share similar information at key points in your users’ workflows, such as after they’ve reset their password? Or are there ways to make the email footer more eye-catching? &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/boilerplate_hu_fbb6b84ca6f32a3b.png&#34; alt=&#34;Sample Boilerplate text from TD Bank and Bank of America emails.&#34; width=&#34;740&#34; height=&#34;321&#34;&gt;

&lt;em&gt;Boilerplate anti-phishing text from TD Bank and Bank Of America, followed by a potentially more eye-catching alternative.&lt;/em&gt;&lt;/p&gt;
&lt;br&gt;
&lt;p&gt;&lt;strong&gt;4. Make user-friendly URLs. &lt;/strong&gt;People who are equipped to assess the authenticity of your site by looking at its URLs find it a valuable signal. Try to identify the URLs that people are likely to link to, and make them short and reasonably easy to decode. People have a harder time evaluating long URLs when they wrap to multiple lines or scroll off the screen in a browser window. For example, if you’re trying to track click-throughs on your most recent email campaign, consider a system that allows you to use a link like http://acmebank.com/signup/?id=43289s32, rather than http://acm.us2.list-manage.com/track/click?u=db7c289db00f46d096f56f14a&amp;id=e70bf2b789&amp;e=c0e9ebec4f. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;5. Don’t use shady alternative domains.&lt;/strong&gt; If your organization’s main website lives at https://acmebank.com, don’t send your users to sites such as https://acmebank.billpay.com or https://billpay.com/acmebank. Using third-party vendor domains can train users to expect unfamiliar websites as part of your communications and make phishing attacks with shady domains seem more credible. The cost savings associated with using these domains may be outweighed by the frustration that your users experience from getting phished.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;6. Support two-factor authentication.&lt;/strong&gt; Allowing users to configure two-factor authentication &lt;a href=&#34;https://en.wikipedia.org/wiki/Multi-factor_authentication#Mobile_phone_two-factor_authentication&#34;&gt;using their mobile phones&lt;/a&gt; is the single strongest protection that you can offer. Two-factor authentication requires users to sign in with both their password and a one-time code either generated with a smartphone app or received by SMS. (Note: members of the security community consider app-generated codes to be much more secure than those received over SMS, especially when users live in countries where the cellular network may be surveilled.) Even if users fall prey to a phishing attack, the attacker will not be able to use their password to access their account at a later date. It can take a significant investment to support two-factor authentication, but the protection it offers is unparalleled.&lt;/p&gt;
&lt;p&gt;These are just some ideas of how you might protect your users from phishing. Happily, you aren’t alone in the anti-phishing fight; there’s a lot going on in users’ web browsers, too. I’ll explore some of this work in my next post.&lt;/p&gt;
&lt;p&gt;In the meantime, tell us about your experiences. If you’re a designer, what have you been doing to fight phishing? Do you have a particularly egregious example of a third-party vendor site? &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;Share it with us&lt;/a&gt; on Twitter or in our Slack channel.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>What ‘90s London Raves Can Teach Us About Infosec</title>
      <link>https://superbloom.design/learning/blog/90s-raves-infosec/</link>
      <pubDate>Tue, 13 Sep 2016 15:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/90s-raves-infosec/</guid>
      <description>&lt;p&gt;One of the highlights of HybridConf 2016 was hearing writer &lt;a href=&#34;https://twitter.com/stevyncolgan?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor&#34;&gt;Stevyn Colgan&lt;/a&gt; talk about his time as a police officer at London&amp;rsquo;s Scotland Yard. He entertained the audience of UX designers and front-end developers with stories from his book, &lt;a href=&#34;https://unbound.com/books/why-did-the-policeman-cross-the-road/&#34;&gt;&lt;em&gt;Why Did the Policeman Cross the Road?&lt;/em&gt;&lt;/a&gt;. As someone who is concerned about the state of policing (in line with &lt;a href=&#34;http://mashable.com/2016/08/10/black-lives-matter-mike-brown-ferguson-timeline/#_4rcJTFBJZqPrecent&#34;&gt;recent protests&lt;/a&gt; in the United States), I did not expect to be impressed, but Colgan&amp;rsquo;s design-thinking approach to crime prevention took me by surprise.&lt;/p&gt;
&lt;h2 id=&#34;design-thinking--policing&#34;&gt;Design Thinking + Policing&lt;/h2&gt;
&lt;p&gt;Colgan was a founding member of the Problem Solving Unit, which operated differently from the rest of Scotland Yard. Instead of solving crimes, they made it their duty to prevent them. Colgan didn&amp;rsquo;t use dystopic tools to identify future criminals. Rather, his team borrowed techniques from cognitive science, marketing, urban planning, and other fields to consider the influence of environmental factors. It is this holistic approach - contemplating physical, technical, and social systems - that makes him a design thinker.&lt;/p&gt;
&lt;p&gt;Colgan shared many stories about his 30 years with the police force, and a few of them were particularly relevant to the security crowd. Information security is about keeping unauthorized people from accessing sensitive content, so in a sense, infosec overlaps with law enforcement in its commitment to crime prevention. Instead of only taking a classic defensive-security stance, borrow from Colgan&amp;rsquo;s Problem Solving Unit and find inspiration by thinking like a creative cop. Here are a few pieces of advice from Colgan&amp;rsquo;s stories:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Make your stuff less attractive&lt;/strong&gt; - Something as simple as covering a motorcycle decreases the likelihood that it will be stolen. The added friction of needing to uncover the motorcycle will redirect thieves to other more-accessible targets nearby.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/motorcycle-cover_hu_fb62d828308739c5.JPG&#34; alt=&#34;A covered motorcycle is less attractive to thieves than uncovered motorcycles nearby (from Stevyn Colgan&amp;rsquo;s Hybrid Conf talk)&#34; width=&#34;740&#34; height=&#34;416&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Identify the weakness&lt;/strong&gt; - In many enclaves, trash collection happens on a set day. Residents wheel their garbage bins to the curb and bring them back after they&amp;rsquo;ve been emptied. In Colgan&amp;rsquo;s city, the only distinguishing factor across these bins is the owner&amp;rsquo;s house number scrawled on the side. Uncollected bins signal that people aren&amp;rsquo;t home; with one glance, thieves can deduce which houses would make the best targets for daytime break-ins.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/numbered-bin_hu_692e979761c334b4.JPG&#34; alt=&#34;Garbage bins are identical except for the house number written on the side (from Stevyn Colgan&amp;rsquo;s Hybrid Conf talk)&#34; width=&#34;740&#34; height=&#34;417&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Constantly adapt your techniques&lt;/strong&gt; - In the 1990s, London was a center for raves. While these gatherings were a mainstay of cultural life for many people during that era, the police considered them to be dangerous because of illegal drug use, sexual assaults, and overcrowding in the case of fire. Before the internet, people relied on posters to learn when and where raves would be held. The Problem Solving Unit made it difficult for promoters to attach posters by adding diagonal braces to walls, which meant that fewer people learned of the raves. Inclement weather played a role, too. The posters were easily damaged when it was wet or windy because they were posted on uneven surfaces.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/diagonal_hu_8dc032e7be0dc646.jpg&#34; alt=&#34;Diagonal bracing made it more difficult for promoters to attach posters to the wall wall (from Stevyn Colgan&amp;rsquo;s Hybrid Conf talk)&#34; width=&#34;740&#34; height=&#34;408&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;implications-for-infosec&#34;&gt;Implications for infosec&lt;/h2&gt;
&lt;p&gt;Colgan&amp;rsquo;s stories of social engineering drew on observations of human behavior and environmental signals, and the Problem Solving Unit&amp;rsquo;s successes and can be applied to infosec UX. Key takeaways include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Basic precautions are good enough for most people&lt;/strong&gt; - Withstanding a targeted attack by a powerful adversary is difficult, but deflecting crime is easier. Just as covering your motorcycle redirects attention, simple deterrents can save your data from harm.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Look with fresh eyes&lt;/strong&gt; - Identical garbage bins are unremarkable features in many landscapes because they&amp;rsquo;re so common. Thinking like a designer means looking past the surface and seeing what can be tweaked. Removing bin numbers - the superficial solution - would have been a complex and impractical response, but nudging people to change their behavior worked just as well.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Consider the entire user journey&lt;/strong&gt; - Rather than focusing only on undesirable behavior at raves, Colgan mapped the entire user journey from the very moment that people learn of a rave. By looking for the starting point, Colgan&amp;rsquo;s team came up with the clever solution to use &amp;ldquo;cancelled&amp;rdquo; stickers.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I was surprised to find a police officer at a design conference, but Colgan&amp;rsquo;s stories demonstrate that a design mindset always has a place, and technical problems don&amp;rsquo;t always need technical solutions. Colgan&amp;rsquo;s solutions may have been in plain sight, but they were elegant. Instead of signaling a lack of originality, tactics like the &amp;ldquo;cancelled&amp;rdquo; stickers are markers of success.&lt;/p&gt;
&lt;p&gt;Sometimes, the best adjustments are so trivial that we overlook or discount them. When crafting new technologies, what simple solutions have been sitting in front of you, waiting to be discovered?&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>One Phish, Two Phish: Security for Designers</title>
      <link>https://superbloom.design/learning/resources/one-phish-two-phish/</link>
      <pubDate>Tue, 30 Aug 2016 17:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/one-phish-two-phish/</guid>
      <description>&lt;p&gt;Most people who spend time online have a general idea of what &amp;ldquo;phishing&amp;rdquo; is, but it can be hard for folks outside of the security community to pin down an exact definition. Understanding the threat that phishing attacks pose can help designers and other UX experts become effective advocates for experiences that protect users. In this post, we will explore the basics of how phishing attacks work, and in a follow-up post, we will examine some of the mechanisms that protect users against them.&lt;/p&gt;
&lt;h2 id=&#34;phishing-is-social-engineering&#34;&gt;Phishing is social engineering&lt;/h2&gt;
&lt;p&gt;As of this writing, Wikipedia defines phishing as &amp;ldquo;the attempt to obtain sensitive information such as usernames, passwords, and credit card details (and sometimes, indirectly, money), often for malicious reasons, by masquerading as a trustworthy entity in an electronic communication.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/phishing-definition_hu_a3175b41ca092ff9.png&#34; alt=&#34;Image defining phishing as an attempt to obtain sensitive information such as usernames, passwords, or credit card details by masquerading as a trustworthy entity in an electronic communication.&#34; width=&#34;740&#34; height=&#34;571&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A definition of the term &amp;ldquo;phishing,&amp;rdquo; adapted from &lt;a href=&#34;https://en.wikipedia.org/wiki/Phishing&#34;&gt;Wikipedia&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;What does this really mean? Implicit in this definition is the idea that phishing attacks target people; they are an example of what security experts call a &lt;a href=&#34;https://en.wikipedia.org/wiki/Social_engineering_(security)&#34;&gt;social engineering attack&lt;/a&gt;. This is in contrast to many of the other digital threats we hear about, such as exploits that take advantage of flaws in particular software programs (e.g.: &lt;a href=&#34;https://en.wikipedia.org/wiki/Buffer_overflow&#34;&gt;buffer overflows&lt;/a&gt;, &lt;a href=&#34;https://en.wikipedia.org/wiki/SQL_injection&#34;&gt;SQL injection points&lt;/a&gt;, or &lt;a href=&#34;https://en.wikipedia.org/wiki/Cross-site_scripting&#34;&gt;cross-site scripting opportunities&lt;/a&gt;) or assaults that take aim at the limitations of a computer system (e.g.: &lt;a href=&#34;https://en.wikipedia.org/wiki/Denial-of-service_attack&#34;&gt;denial-of-service attacks&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;Social engineering attacks are just a modern take on the classic &lt;a href=&#34;https://en.wikipedia.org/wiki/Confidence_trick&#34;&gt;confidence trick&lt;/a&gt;, which derives its name from the attacker&amp;rsquo;s methodology of building false confidence – or trust – with the target before attempting to defraud them.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/confidence-definition_hu_3d55a51e56565091.png&#34; alt=&#34;Image with text defining the term confidence trick as an attempt to defraud a person or group after first gaining their confidence.&#34; width=&#34;740&#34; height=&#34;614&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A definition of the term &amp;ldquo;confidence trick,&amp;rdquo; adapted from &lt;a href=&#34;https://en.wikipedia.org/wiki/Confidence_trick&#34;&gt;Wikipedia&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Other examples of social-engineering attacks include &lt;a href=&#34;https://en.wikipedia.org/wiki/Advance-fee_scam&#34;&gt;advance-fee scams&lt;/a&gt; (beware of people claiming to be &lt;a href=&#34;https://www.bbb.org/article/news-releases/16915-bbb-tip-foreign-money-exchange-scams&#34;&gt;Nigerian royalty!&lt;/a&gt;) and the &lt;a href=&#34;https://en.wikipedia.org/wiki/Mary_McDonnell&#34;&gt;elaborate scheme&lt;/a&gt; that &lt;a href=&#34;https://en.wikipedia.org/wiki/Mary_McDonnell&#34;&gt;Mary McDonnell&lt;/a&gt;&amp;rsquo;s character uses to steal a key card, thus allowing &lt;a href=&#34;https://en.wikipedia.org/wiki/Robert_Redford&#34;&gt;Robert Redford&lt;/a&gt;&amp;rsquo;s character to access a locked building in the movie &lt;em&gt;&lt;a href=&#34;https://en.wikipedia.org/wiki/Sneakers_(1992_film)&#34;&gt;Sneakers&lt;/a&gt;&lt;/em&gt;.&lt;/p&gt;
&lt;h2 id=&#34;a-sample-attack&#34;&gt;A sample attack&lt;/h2&gt;
&lt;p&gt;Again, the aim of a phishing attack is to harvest confidential information from users. Let&amp;rsquo;s walk through a hypothetical example to see what this looks like in practice.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Juanita gets an email that looks like it&amp;rsquo;s from Bank of America, saying her password needs to be reset, and it offers a link that allows her to take this action.&lt;/li&gt;
&lt;li&gt;Juanita clicks on the link and sees a webpage that looks similar to the one she is used to using.&lt;/li&gt;
&lt;li&gt;She enters in her username and her password.&lt;/li&gt;
&lt;li&gt;The page returns an error, saying that the password she entered is incorrect. Like many people, Juanita has a small number of passwords that she reuses across many sites. She tries a few different passwords, trying to find one that works.&lt;/li&gt;
&lt;li&gt;Juanita eventually gives up, clicks the &amp;ldquo;Forgot Passcode&amp;rdquo; link, and sees that the site returns an error message asking her to sign in again later.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;At this point, the attackers have probably gotten:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Juanita&amp;rsquo;s bank username&lt;/li&gt;
&lt;li&gt;Juanita&amp;rsquo;s bank password&lt;/li&gt;
&lt;li&gt;The passwords of several other services Juanita uses, potentially including the one she uses on her email account&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;They accomplished this because:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;They sent a message pretending to be from Bank of America to an actual Bank of America customer.&lt;/li&gt;
&lt;li&gt;They spoofed the &amp;ldquo;from&amp;rdquo; address in the email, so it looked like it was really coming from Juanita&amp;rsquo;s bank.&lt;/li&gt;
&lt;li&gt;They created an email that looked and felt similar to the emails Juanita regularly gets from her bank.&lt;/li&gt;
&lt;li&gt;They created a webpage that looked and felt similar to the one she&amp;rsquo;s accustomed to.&lt;/li&gt;
&lt;li&gt;They took advantage of Juanita&amp;rsquo;s uncomfortable relationship with passwords; she wasn&amp;rsquo;t sure that she was typing the right one, so inadvertently shared several others as well.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/phishing-example_hu_3365c920dd3137b.png&#34; alt=&#34;Image of a mocked-up phishing email and sign-in page.&#34; width=&#34;740&#34; height=&#34;537&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A mocked-up phishing email and sign-in page.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;the-practical-threats-of-phishing&#34;&gt;The practical threats of phishing&lt;/h2&gt;
&lt;p&gt;For their attacks to be successful, phishers must create an environment where people feel comfortable sharing confidential details. Attackers harvesting credit card numbers might create a fake version of a popular online retailer or a government website to collect social security numbers.&lt;/p&gt;
&lt;p&gt;Email credentials – the username and password you enter when you sign in to your email account – are a particularly juicy target because most sites use email as a password-reset mechanism (for example, when you click the &amp;ldquo;Forgot your password?&amp;rdquo; link on Amazon.com&amp;rsquo;s sign-in page, they send a code to your email account as the first step in resetting your password). Thus, attacks against your email account are about more than getting access to your email messages; they&amp;rsquo;re about using your email account as a jumping-off point to get access to the rest of your digital life, too. There are also other ways in which a phishing attack may be just the first of a multi-step attack; if you reuse passwords, one successful phish can end up compromising many accounts.&lt;/p&gt;
&lt;p&gt;Similarly, if you reuse passwords from one account to another, a successful phishing attack against one account can easily end up escalating into something more serious. Where possible, try to use unique passwords for your high-value accounts and consider using a reputable password manager that isn&amp;rsquo;t based in the cloud, like &lt;a href=&#34;https://1password.com/&#34;&gt;1Password&lt;/a&gt; (stay tuned for my next post on phishing, where I will explore this and other defensive mechanisms in more detail).&lt;/p&gt;
&lt;h2 id=&#34;advanced-attacks&#34;&gt;Advanced attacks&lt;/h2&gt;
&lt;p&gt;Early phishers focused on compromising a large number of random accounts, but their attacks quickly evolved to become more targeted. Rather than send emails to a million hotmail.com accounts, attackers will sometimes do meticulous research and craft a message specifically designed to appeal to the staff of a particular organization. This message might be designed to look like the sign-in page for the organization&amp;rsquo;s internal web portal or for its health insurance provider. If the attacker is an employee or knows someone who works at the organization, they may reference information that only insiders would know.&lt;/p&gt;
&lt;p&gt;For example, imagine that Hamidou works for Collective Insurance of Brooklyn, a large company that conducts much of its business online. He recently started working there and is still learning how to navigate the company&amp;rsquo;s employee benefits website, which he thinks looks very outdated. This benefits site is managed by a firm called BenefitsDigital, which specializes in benefits management but hasn&amp;rsquo;t updated the styling on their site for a long time. While accessing it during new-employee orientation, Hamidou noticed that it has a strange URL like collectiveinsurancebrooklyn.benefitsdigital.com.  his HR representative explained that this is to be expected because the site is hosted by the benefits administration company.&lt;/p&gt;
&lt;p&gt;An attacker saw Collective Insurance of Brooklyn listed on BenefitsDigital&amp;rsquo;s &amp;ldquo;Our Clients&amp;rdquo; page, and used a LinkedIn search to discover that Hamidou and a few other people started working there recently. Further sleuthing revealed that most employees at the company have email addresses of the form firstname.lastname@. From there, it was easy for the attackers to send this small group of employees a customized message that looked like it came from BenefitsDigital. The message tells them that they need to sign in to the website and perform their quarterly benefits review to prevent a discontinuation of their 401(k) matching, and helpfully reminds them that they are eligible for a $200/month commuting reimbursement.&lt;/p&gt;
&lt;p&gt;Hamidou clicks on the link in the email, which brings him to collectiveinsurancebrooklyn.ebenefitsdigital.com. His eyes skim over the long URL and he doesn&amp;rsquo;t notice that the site is hosted at ebenefitsdigital.com (a site the attackers set up to mimic the legitimate benefits administrator), not benefitsdigital.com. The website is just as weirdly outdated and buggy as ever, so nothing seems out of place to Hamidou. When he tries to sign in, he gets an error message that the site is down for maintenance. He decides he will try again a few days later.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/spear-phishing_hu_7c136e603145dd33.png&#34; alt=&#34;Image defining spear phishing as a personalized phishing attack against a high-value target, either an individual or an organization.&#34; width=&#34;740&#34; height=&#34;611&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A definition of the term &amp;ldquo;spear phishing.&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Attacks similar to this example is not just believable, but becoming increasingly common. As you might imagine, a customized message that references an organization&amp;rsquo;s cultural touchstones is less likely to set off alarm bells for its victims and has a higher probability of success. If the phisher&amp;rsquo;s goal is to gain access to the organization&amp;rsquo;s internal systems, a customized attack can can be successful if just a single employee bites.&lt;/p&gt;
&lt;p&gt;Even more sophisticated attacks combine inside knowledge with a sense of social pressure by making the emails personalized to individual targets, and making it seem like the message is coming from a senior member of the organization, such as its CEO (apparently, this kind of attack is now called &amp;ldquo;&lt;a href=&#34;http://www.v3.co.uk/v3-uk/news/2448905/snapchat-hit-by-ceo-email-scam-as-whaling-attacks-increase&#34;&gt;whaling&lt;/a&gt;&amp;rdquo;). If you&amp;rsquo;re a lowly payroll processor and you get an urgent email from someone six levels above you in the corporate hierarchy – on the day where the rest of the department is at a retreat! – it can be hard to keep your cool and tune in to the possibility that the inquiry may not be legitimate. And, even if you do get a sense that the request may not be legitimate, how do you verify your hunch without simultaneously insulting a bigwig and torpedoing your career?&lt;/p&gt;
&lt;h2 id=&#34;phishing-is-about-confidence&#34;&gt;Phishing is about confidence&lt;/h2&gt;
&lt;p&gt;As I remarked before, phishing is just one modern take on the idea of a confidence game. A successful attack depends on the user developing confidence that the request for their information is legitimate. Social pressures, such as in the whaling example, can make it hard for users to see an attack for what it is. So can general discomfort with computers or a lack of experience dealing with sensitive information.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/abagnale_hu_ca7245900b4ec621.png&#34; alt=&#34;Still image from the movie Catch Me If You Can, picturing Leonardo DiCaprio dressed as an airline pilot surrounded by eight young women dressed as stewardesses.&#34; width=&#34;740&#34; height=&#34;410&#34;&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The 2002 movie &lt;em&gt;&lt;a href=&#34;https://www.youtube.com/watch?v=71rDQ7z4eFg&#34;&gt;Catch Me If You Can&lt;/a&gt;&lt;/em&gt; publicized &lt;a href=&#34;https://en.wikipedia.org/wiki/Frank_Abagnale&#34;&gt;Frank Abagnale Jr.&amp;rsquo;s&lt;/a&gt; adventures as a young confidence trickster. Frank (played by Leonardo DiCaprio) is the epitome of the term &amp;ldquo;confidence man,&amp;rdquo; or &amp;ldquo;con man&amp;rdquo; for short.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It&amp;rsquo;s important to note that falling for a phishing attack does not indicate any kind of failing in a person&amp;rsquo;s intelligence. The skills we&amp;rsquo;ve evolved over millennia for developing trust in other human beings – evaluating appearance, behavior, and pattern-matching – do not serve us well in a digital context. The channels we have for receiving trust information from computers, such as the visual design of a website or the &amp;ldquo;from&amp;rdquo; header of an email, are simply too easily spoofed. When push comes to shove, if you create a website that is a faithful replica of &lt;a href=&#34;https://www.bankofamerica.com/&#34;&gt;bankofamerica.com&lt;/a&gt;, you will find people who will trust it based on its visual design alone.&lt;/p&gt;
&lt;p&gt;In a future post, I will review some of the mechanisms that exist to help users and organizations protect against phishing attacks and explore ways that designers can contribute safeguards through their products. In the meantime, do you have a favorite story about phishing or other forms of social engineering? Connect with us on &lt;a href=&#34;https://twitter.com/simplysecureorg&#34;&gt;Twitter&lt;/a&gt; and tell us all about it!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Learning from Drones</title>
      <link>https://superbloom.design/learning/blog/learning-from-drones/</link>
      <pubDate>Tue, 16 Aug 2016 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/learning-from-drones/</guid>
      <description>&lt;p&gt;Last week, I encountered discussions of drones in two unimaginably different contexts: in an academic presentation at &lt;a href=&#34;https://www.usenix.org/conference/usenixsecurity16&#34;&gt;USENIX Security 2016&lt;/a&gt; and on the TV comedy &lt;a href=&#34;https://www.ifc.com/shows/portlandia/explore--1000011&#34;&gt;&lt;em&gt;Portlandia&lt;/em&gt;&lt;/a&gt;. As distant genres, they offer different perspectives that have equally important UX implications for privacy preservation.&lt;/p&gt;
&lt;p&gt;In the &lt;a href=&#34;https://www.usenix.org/conference/usenixsecurity16/technical-sessions/presentation/wing&#34;&gt;opening keynote&lt;/a&gt; of USENIX Security, Dr. Jeannette Wing examined the trustworthiness of cyber-physical systems, which are engineered systems with tight coordination between the computational and physical worlds. Some of her examples included the Nest thermostat and the Apple watch, which are very exciting user experiences to UX designers. To a designer like me, her concrete, design-based examples set an inviting tone for such a technical conference.&lt;/p&gt;
&lt;h2 id=&#34;drones-from-a-technical-security-perspective&#34;&gt;Drones from a technical security perspective&lt;/h2&gt;
&lt;p&gt;Dr. Wing spent time exploring points of vulnerability in which the integrity of systems, such as drones, could be compromised. This uncertainty needs management at multiple levels. For example, drones need to manage unexpected atmospheric conditions and sensor malfunctions while still operating safely. However, when flying and data collection already draw on limited battery life, there&amp;rsquo;s barely power left for anything else. Dr. Wing called for securing the full set of software running on IoT devices, from low-level device identity in hardware through secure boot and storage up to encrypted communications and secure configuration.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/JeannetteWingSlide_hu_1868dd0043849591.jpg&#34; alt=&#34;Slide from Jeannette Wing&amp;rsquo;s keynote at USENIX Security 2016.&#34; width=&#34;740&#34; height=&#34;408&#34;&gt;

&lt;em&gt;Slide from Jeannette Wing&amp;rsquo;s &amp;ldquo;Crashing Drones&amp;rdquo; keynote at USENIX Security 2016.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;But preserving privacy is more than just a technical stack; the challenges that users have when operating drones contain UX lessons for privacy preservation. For that, we turn to Portlandia, which picks up where Dr. Wing dropped off.&lt;/p&gt;
&lt;h2 id=&#34;drones-in-pop-culture&#34;&gt;Drones in Pop Culture&lt;/h2&gt;
&lt;p&gt;In the &amp;ldquo;Pickathon&amp;rdquo; episode of &lt;a href=&#34;https://www.ifc.com/shows/portlandia/explore--1000011&#34;&gt;&lt;em&gt;Portlandia&lt;/em&gt;&lt;/a&gt;, the two protagonists use drones to experience the Pickathon music festival virtually. By flying their drones to the front row of the concert, the two operators can see and hear everything from their couch. Although they manage to avoid long lines and smelly port-a-potties, their impact on the physical world is still felt: They injure other concert-goers—intentionally or not—as they navigate the festival.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/Portlandia-Ad_hu_d4b6af78e2bc5b9f.jpg&#34; alt=&#34;Fake advertisement in the Portlandia Pickathon episode for drone rentals.&#34; width=&#34;740&#34; height=&#34;448&#34;&gt;

&lt;em&gt;Fake advertisement in the Portlandia &amp;ldquo;Pickathon&amp;rdquo; episode for drone rentals.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The plot points of the sketch unpack UX for privacy in a humorous way:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Bystanders don&amp;rsquo;t know who&amp;rsquo;s operating them or why&lt;/strong&gt;
It&amp;rsquo;s unclear at the beginning that remote concert-goers are in control of the drones and that they have nothing to do with the official music festival.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bystanders don&amp;rsquo;t know what data is being collected&lt;/strong&gt;
In the sketch, concert-goers assume that the drones contain cameras but are uncertain whether audio and other data are also being captured.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Subjects under observation are unsure of how to interact with remote operators&lt;/strong&gt;
The operators can broadcast their voices through the drones, and one annoyed concert-goer was surprised to discover that &amp;ldquo;this thing can talk.&amp;rdquo; The operator taunted the concert-goer into a fist fight in which the concert-goer curses the absent operator all the while getting beat up by the drone.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bystanders and subjects don&amp;rsquo;t know where the drone operator is located&lt;/strong&gt;
When the freshly bruised concert-goer breaks open the drone, he sees a label with the operators&amp;rsquo; address. He shows up at their house to beat up the operator who goaded him during the fight.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;When operating a third-party drone, an external carrier might be able to both monitor and override control of the drone from afar&lt;/strong&gt;
At the end of the episode, the bruised concert-goer makes peace with the operators and joins them on their couch. While all three enjoy the concert via drone operation, the entrepreneur who rented the drone to the operators appears in the background. In his quest to make music festivals appealing to music fans over age 40, he had snuck into their home to watch them and gather data points.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/drone-injury_hu_256c25ba45aaf531.jpg&#34; alt=&#34;The concert-goer who was cut up by the operator&amp;rsquo;s drone in Portlandia&amp;rsquo;s Pickathon episode.&#34; width=&#34;740&#34; height=&#34;437&#34;&gt;

&lt;em&gt;The concert-goer who was cut up by the operator&amp;rsquo;s drone in Portlandia&amp;rsquo;s &amp;ldquo;Pickathon&amp;rdquo; episode.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;how-drones-challenge-us-to-design-for-privacy&#34;&gt;How drones challenge us to design for privacy&lt;/h2&gt;
&lt;p&gt;Drones are a useful example when considering privacy because they make every actor in the system visible. In contrast to contexts such as mobile messaging on a phone, drones are less abstract because you can see the operator, owner, and subjects under observation.&lt;/p&gt;
&lt;p&gt;Here are two key UX design challenges for people working on IoT applications more broadly:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;How can embedded sensors disclose the data they are collecting, who is collecting it, and for what purposes?&lt;/strong&gt;
Without a service design component, policies such as a hypothetical drone registration service won&amp;rsquo;t help people understand the who, what, where, and why behind the drone&amp;rsquo;s operation. As an analogy, many commercial trust don&amp;rsquo;t just have a license plate to identify them. They also display decals that ask, &amp;ldquo;How&amp;rsquo;s my driving? Call 1-800-XXX-XXXX for complaints about vehicle number N.&amp;rdquo; Because of the decal, other drivers now know of another channel to learn more and hold truck drivers accountable. Nothing similar exists for drones.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What best practices for zero-UI or design-beyond-the-screen can be used to help bystanders interact with drones?&lt;/strong&gt;
Dismantling a drone to find a physical street address like in Portlandia may be comedic, but it is neither common nor scalable. With weight and power at a premium on drones, there is no space to add instructions on how bystanders should interact with the drone. One solution is to use bystanders&amp;rsquo; cell phones displays, but that approach is also problematic. It is highly unlikely that we can scale the use of mobile notifications to inform bystanders of their rights and the drones&amp;rsquo; purpose. Even if notifications were mandatory, the thousands of IoT devices alerting bystanders through their smartphones would be an unnavigable user experience. We need to explore these issues more deeply.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;drones-lead-the-way&#34;&gt;Drones lead the way&lt;/h2&gt;
&lt;p&gt;Drones are complex cyber-physical systems with poor ability to disclose how they work to bystanders. In contrast to the relatively well-understood domains of email and mobile messaging, privacy-preserving measures for drones are significantly more complicated. Because the challenges for drones are new to both the public and the technical community, they provide an opportunity to engage a mass audience in critical thinking about how we want to interact with the systems.&lt;/p&gt;
&lt;p&gt;Through drones, designers can explore particular challenges such as alert management. By thinking about how multiple parties (owner, operator, subjects under observation, privacy advocates, etc.) want to interact with drones, thoughtful UX design can empower people to manage their privacy in a variety of contexts.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Your Software Can Help At-risk People, Too</title>
      <link>https://superbloom.design/learning/blog/your-software-can-help/</link>
      <pubDate>Tue, 02 Aug 2016 20:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/your-software-can-help/</guid>
      <description>&lt;p&gt;Web browsers are utility software; they are designed to work for all people. Not only must their features meet the needs of average members of a population, they must also work for people with special needs. As Firefox says on its &lt;a href=&#34;https://support.mozilla.org/en-US/kb/mobile-accessibility-features&#34;&gt;mobile accessibility features&lt;/a&gt; page, the browser has been &amp;ldquo;designed to meet the needs of the broadest population possible,&amp;rdquo; but &amp;ldquo;sometimes that is not enough.&amp;rdquo; In particular, software that is built for everyone can too often leave people with specific security or privacy needs at risk.&lt;/p&gt;
&lt;p&gt;As a counterexample, I recently noticed that Chrome&amp;rsquo;s Android app has a small but tremendously valuable feature for people at risk of in-person surveillance. At-risk users might include someone whose phone is subject to regular inspection at government checkpoints, which has been &lt;a href=&#34;http://www.nytimes.com/2015/08/26/world/europe/a-21st-century-migrants-checklist-water-shelter-smartphone.html&#34;&gt;reported to be the case&lt;/a&gt; in Syria. It could also be someone whose boss requires them to hand over their phone at the start of each retail-job shift, as Ame learned in her &lt;a href=&#34;https://superbloom.design/resources/techreports/NYC15-MobMsg.pdf&#34;&gt;New York City study&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The feature is part of Chrome&amp;rsquo;s &lt;a href=&#34;https://support.google.com/chrome/answer/7005900&#34;&gt;incognito mode&lt;/a&gt;, which lets users browse the web without worrying that their device will record the history or cookies from their session. The browser automatically deletes this information when all incognito tabs are closed. Now, on phones running recent versions of the Android operating system, Chrome can push a message to the notification shade and to the lock screen that allows you to easily close all incognito tabs in a single action.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/incognito-notification_hu_adb376e924ec247b.png&#34; alt=&#34;Images depicting the Chrome notification.&#34; width=&#34;740&#34; height=&#34;121&#34;&gt;

&lt;em&gt;Chrome&amp;rsquo;s &amp;ldquo;Close all incognito tabs&amp;rdquo; notification, as an icon in the notification bar (left), expanded in the notification shade (center), and on the lock screen (right).&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This hits the sweet spot for features that are incredibly useful for a subset of an app&amp;rsquo;s user population:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;It&amp;rsquo;s unobtrusive&lt;/strong&gt;. If you don&amp;rsquo;t use incognito mode, you won&amp;rsquo;t ever encounter or be confused by this feature.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;It&amp;rsquo;s automatic&lt;/strong&gt;. If you do use incognito mode, you don&amp;rsquo;t have to take extra steps to enable it; it&amp;rsquo;s on by default.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;It&amp;rsquo;s simple and elegant&lt;/strong&gt;. Since it&amp;rsquo;s a notification, it&amp;rsquo;s easily available from anywhere in the operating system. Its functionality is immediately apparent and immediately effective.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Of course, not everyone is a fan of this feature; a quick web search reveals that some users who keep incognito tabs open for extended periods find this notification annoying. In creating this feature, the designers had to choose whether to build in more protection (having the notification on by default) or less, and they erred on the side of more. Given the goals of incognito mode, I think this is appropriate. That said, Google might address criticizers&amp;rsquo; concerns by offering a setting to opt out of the notifications.&lt;/p&gt;
&lt;h2 id=&#34;learning-from-this-example&#34;&gt;Learning from this example&lt;/h2&gt;
&lt;p&gt;While we often cheer the loudest when apps integrate features like end-to-end encryption (e.g.: &lt;a href=&#34;https://superbloom.design/learning/blog/whatsapp-update&#34;&gt;Whatsapp&lt;/a&gt;), smaller features can make a big impact, too. This Chrome feature shows that apps designed for a general population can directly help people concerned about their data security in simple, elegant ways.&lt;/p&gt;
&lt;p&gt;Right now, members of the western technology community often perceive at-risk users as being a niche population. It&amp;rsquo;s easy to envision opposition fighters in Syria, activists like &lt;a href=&#34;https://en.wikipedia.org/wiki/Ai_Weiwei&#34;&gt;Ai Weiwei&lt;/a&gt;, or journalists like &lt;a href=&#34;https://en.wikipedia.org/wiki/Laura_Poitras&#34;&gt;Laura Poitras&lt;/a&gt;, who worked with Edward Snowden to publish his documents. But as you learn more about the prevalence of surveillance and the concerns that people have about intrusions on their private data, you will discover that this group is larger than you think – and it&amp;rsquo;s growing. At-risk users are people who worry about their security, either physical or digital. As online data plays an ever-increasing role in life around the globe, its potential for exploitation by corrupt officials, domestic abusers, and organized crime escalates as well.  It&amp;rsquo;s important to get a jump-start thinking about these users now.&lt;/p&gt;
&lt;p&gt;What small features can your project add to help at-risk people? If you need help brainstorming or have released a successful project in this vein, &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;let us know&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Respecting Participants in Privacy-related User Studies</title>
      <link>https://superbloom.design/learning/blog/respecting-participants/</link>
      <pubDate>Tue, 26 Jul 2016 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/respecting-participants/</guid>
      <description>&lt;p&gt;I was in Darmstadt for Privacy and Security Week last week to present Simply Secure&amp;rsquo;s work on ethics in user research at &lt;a href=&#34;https://petsymposium.org/2016/spw-mirror/pets-2016/hotpets/&#34;&gt;HotPETS&lt;/a&gt;. You can check out the &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Talks-and-Slides/2016/HotPETS-2016-paper.pdf&#34;&gt;paper&lt;/a&gt; and &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Talks-and-Slides/2016/HotPETS-2016-slides.pdf&#34;&gt;slides&lt;/a&gt; on GitHub.&lt;/p&gt;
&lt;h2 id=&#34;resources-for-ethical-research&#34;&gt;Resources for ethical research&lt;/h2&gt;
&lt;p&gt;In 2015, we did a field study that we named &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Research/2015_NYC_Mobile_Messaging/NYCMobMsgTechReport.pdf&#34;&gt;Straight Talk: New Yorkers on Mobile Messaging and Implications for Privacy&lt;/a&gt;. We have since used it as a case study to demonstrate how to work with study participants. Here is a list of &lt;a href=&#34;https://github.com/simplysecure/resources/tree/master/Research/2015_NYC_Mobile_Messaging&#34;&gt;resources&lt;/a&gt; for user studies that draws from the case.&lt;/p&gt;
&lt;p&gt;Additionally, our previous blog posts explain how to use &lt;a href=&#34;https://superbloom.design/learning/blog/recruiting-screeners&#34;&gt;participant recruiting screeners&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/learning/blog/model-release&#34;&gt;model releases&lt;/a&gt; for photography, and the &lt;a href=&#34;https://superbloom.design/learning/blog/participant-rights&#34;&gt;participant&amp;rsquo;s bill of rights&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;participating-in-research-shouldnt-harm-people&#34;&gt;Participating in research shouldn&amp;rsquo;t harm people&lt;/h2&gt;
&lt;p&gt;The Internet Freedom community is keenly aware of the need to protect sources who speak with journalists, but we tend to overlook how to protect research participants as well. Here are some questions to ask yourself next time you do a study:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Do you need to record audio and video — are they necessary for publishing results — or will handwritten notes suffice?&lt;/li&gt;
&lt;li&gt;Are the research participants representative of your target user population? Think not only demographics but also attitudes. If your participants are willing to install logging software and be recorded, are they reasonable approximations of your intended users?&lt;/li&gt;
&lt;li&gt;Site analytics can encroach on privacy. Given this, what alternatives can you consider that will also help you quantify usability?&lt;/li&gt;
&lt;li&gt;What&amp;rsquo;s the threat model? What could happen to your participants if others find out that they participated in your research?&lt;/li&gt;
&lt;li&gt;If your organization requires standard language on an informed consent document, are there options to include a second page that&amp;rsquo;s written in human-centered, accessible language?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/participant-discussion_hu_b1b2cd099692a3a2.jpg&#34; alt=&#34;Photo of Ame looking at papers with a research participant.&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;

&lt;em&gt;In this interview, the consent forms and model release forms were visibly laid out on the table.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;safeguarding-participants-is-important&#34;&gt;Safeguarding participants is important&lt;/h2&gt;
&lt;p&gt;It was encouraging at &lt;a href=&#34;https://eurousec.secuso.org/&#34;&gt;EuroUSEC&lt;/a&gt;, &lt;a href=&#34;https://petsymposium.org/2016/spw-mirror/pets-2016/index.html&#34;&gt;PETS&lt;/a&gt;, and &lt;a href=&#34;https://petsymposium.org/2016/spw-mirror/pets-2016/hotpets/&#34;&gt;HotPETS&lt;/a&gt; to see so many presenters who shared the results of their user studies. At Simply Secure, we want to assist researchers in approaching their studies mindfully. Please adapt our &lt;a href=&#34;https://github.com/simplysecure/resources/tree/master/Research/2015_NYC_Mobile_Messaging&#34;&gt;resources&lt;/a&gt; for your use. Our goal is to provide tools that match the needs of a global audience, so let us know where they can use improvement.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Don&#39;t Let Color Drown Out Your Message</title>
      <link>https://superbloom.design/learning/resources/color-message/</link>
      <pubDate>Tue, 19 Jul 2016 16:45:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/color-message/</guid>
      <description>&lt;p&gt;Last month, I &lt;a href=&#34;https://superbloom.design/learning/resources/compelling-color&#34;&gt;wrote&lt;/a&gt; about the importance of visual design for creating compelling software and shared resources for learning about color and choosing a good color scheme.&lt;/p&gt;
&lt;p&gt;I also cautioned readers that using color in &amp;ldquo;moderation can go a long way toward making your project look professional and credible.&amp;rdquo; Today&amp;rsquo;s post will dissect that advice in greater detail.&lt;/p&gt;
&lt;h2 id=&#34;use-color-as-an-accent&#34;&gt;Use color as an accent&lt;/h2&gt;
&lt;p&gt;Color is great for logos and accents — it makes a statement, it conveys personality — but it can also overwhelm users when it dominates the main body of the interface. Designers use color to focus people&amp;rsquo;s attention on the most important content, and a little bit can go a long way. Whites, grays, and blacks may seem visually boring when you have a rainbow of options to choose from, but they provide a neutral basis that allows the colorful elements of your UI to stand out.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/weather-newsletter_hu_24998e6ca1d69ae3.png&#34; alt=&#34;Two mockups of a weather newsletter, one with a dark blue background and the other with a white background.&#34; width=&#34;740&#34; height=&#34;306&#34;&gt;

&lt;em&gt;Newsletters and other information-heavy designs are particularly well-served by light backgrounds. When choosing a color for a graphic element, don&amp;rsquo;t just select an attractive hue; first examine the importance of the information it conveys and whether it deserves to be highlighted.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/acme-email-bright_hu_d325a9780cefe968.png&#34; alt=&#34;Two mockups of an email sign-in page, one with a bright purple background and one with a white background.&#34; width=&#34;740&#34; height=&#34;290&#34;&gt;

&lt;em&gt;A white background and gray text in the text fields makes the sign-in flow to the right more approachable and professional. This color combination also helps the actionable elements – the button and the &amp;ldquo;Learn more&amp;rdquo; link – stand out more. &lt;a href=&#34;https://commons.wikimedia.org/wiki/File:Indian_woman_smiles.jpg&#34;&gt;Photograph&lt;/a&gt; used under &lt;a href=&#34;https://creativecommons.org/licenses/by-sa/2.5/deed.en&#34;&gt;CC BY-SA 2.5.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;neither-too-bright-nor-too-dark&#34;&gt;Neither too bright nor too dark&lt;/h2&gt;
&lt;p&gt;In order to present your user with an engaging and warm experience, try to use light, neutral tones as the background for the majority of your interface. Unlike software developers, who may find light text on dark backgrounds easier to read, members of the general public can interpret dark colors as unfriendly — sometimes threatening — which just makes things harder if you&amp;rsquo;re trying to build software that inspires confidence and trust with new users. Avoid using black or dark gray unless you are confident that your target audience will interpret it as a cultural reference (as is the case when you&amp;rsquo;re &lt;a href=&#34;https://www.blackhat.com/&#34;&gt;catering to hackers&lt;/a&gt; or there is a functional reason for a dark background (e.g. when it&amp;rsquo;s a tool for working with &lt;a href=&#34;https://color.adobe.com/&#34;&gt;color&lt;/a&gt; or when it&amp;rsquo;s an optional customization in a text editor).&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/acme-dark_hu_c252704c7513fb6b.png&#34; alt=&#34;Two mockups of an email sign-in page, one with a dark background and bright colors, the other with a white background and darker colors.&#34; width=&#34;740&#34; height=&#34;290&#34;&gt;

&lt;em&gt;Avoid dark backgrounds as a general rule. If you want to convey a serious feeling, consider using darker shades for your accent colors.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;dont-over-saturate&#34;&gt;Don&amp;rsquo;t over-saturate&lt;/h2&gt;
&lt;p&gt;Highly saturated colors should be used carefully. Saturated colors can suggest liveliness and cheer but can easily go too far and make it painful to look at the interface.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/cat-infographic_hu_e0615583381e3694.png&#34; alt=&#34;Two mockups of an infographic with a red background; one uses a very saturated red, the other uses a less-saturated red.&#34; width=&#34;740&#34; height=&#34;291&#34;&gt;

&lt;em&gt;The graphic to the left uses #FF0000 for its red, which has a saturation of 100%. The graphic on the right uses #FF4040, which is a tone of the same hue and brightness that has a saturation of 75%. The difference is subtle, but it makes the contrast with the colors and repeated pattern of the cat outlines a little less jarring.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;If you don&amp;rsquo;t know how saturated a color is, look at the &amp;ldquo;S&amp;rdquo; value on an HSB (hue, saturation, brightness) color picker in an image-editing program. The more saturated a color is, the closer its value is to 100. The Simply Secure color palette is bright and cheerful with a variety of hues but balances this brightness by dampening the saturation.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/color-saturation_hu_f254340e820a6351.png&#34; alt=&#34;An image of a color picker and an image of the five shades of Simply Secure&amp;rsquo;s color palette.&#34; width=&#34;740&#34; height=&#34;354&#34;&gt;

&lt;em&gt;To the left, the Sketch color picker displays the values for hue (H), saturation (S), and brightness (B). To the right, Simply Secure&amp;rsquo;s color palette has been labeled with each color&amp;rsquo;s saturation value.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;think-expansively-and-find-a-friend&#34;&gt;Think expansively and find a friend&lt;/h2&gt;
&lt;p&gt;Even people who have spent years studying the subject have a hard time getting color right. When you&amp;rsquo;re working on a new palette or layout, we recommend that you ask a color-savvy friend who is removed from the work to give you feedback. Instead of a single design that they have to give a thumbs-up or thumbs-down to, present multiple design directions and have a conversation about the advantages and disadvantages of each. When possible, repeat this process several times, ideally with different critics.&lt;/p&gt;
&lt;p&gt;Privacy-preserving technology is important, and color can make it approachable to a broad audience. As with many aspects of software, aiming for simplicity and elegance in color is usually a safe bet. If you don&amp;rsquo;t know where to start, try finding inspiration from other technologies that are designed to appeal to a broad audience. Otherwise stick to the basics: use a clean and light background, don&amp;rsquo;t over-saturate, and focus on using color to accent the most important information. This will help you create a design that is approachable, useful, and conveys trustworthiness.&lt;/p&gt;
&lt;p&gt;If you need a friendly pair of eyes to take a look at your latest creation, please consider joining the #design channel of our Slack community! You can request an invitation by emailing us at &lt;a href=&#34;mailto:slack@superbloom.design&#34;&gt;slack@superbloom.design&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Illustrated Quick-start Intro to Wireframing</title>
      <link>https://superbloom.design/learning/blog/wireframing-intro/</link>
      <pubDate>Tue, 12 Jul 2016 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/wireframing-intro/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;re new to UX design, &lt;a href=&#34;http://www.experienceux.co.uk/faqs/what-is-wireframing/&#34;&gt;wireframing&lt;/a&gt; is a powerful tool to understand how users experience your software. People with technical backgrounds benefit from wireframing because it forces them to take a step back from their coding mentality. Rather than focusing on the technical architecture, wireframing exposes the user-experience structure: how the user moves from one screen to another.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/wireframe-example_hu_864c987539c15d95.jpg&#34; alt=&#34;Image showing one wireframe with a set of buttons representing options, and another with a drop-down menu of options.&#34; width=&#34;740&#34; height=&#34;281&#34;&gt;

&lt;em&gt;Example wireframes taken &lt;a href=&#34;http://www.goodui.org/&#34;&gt;from GoodUI.org&lt;/a&gt;. Both show the same content organized with two different structures, but the left wireframe is better because it discloses choices rather than keeping them hidden.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Wireframes are useful because they offer a stripped-down, visual experience made up of plain boxes and lines—no formatting, no styling, no graphic design. That&amp;rsquo;s right; improving your UX skills starts with abandoning colors and styles. If you can draw mostly straight lines, you&amp;rsquo;ve got what it takes.&lt;/p&gt;
&lt;h2 id=&#34;why-wireframe&#34;&gt;Why wireframe?&lt;/h2&gt;
&lt;p&gt;Teams use wireframes at many points during the design process. They can use it to conceptualize a design, to critique their design internally, and to get reactions from testers. Here are three advantages of wireframing:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Start off right.&lt;/strong&gt;&lt;br&gt;
If you&amp;rsquo;re implementing a new feature, start by analyzing how a different app handled a similar challenge. The act of sketching wireframes can trigger different thought processes and impart a deeper understanding than what you would get by just looking at an interface on screen.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Get user feedback faster than with code.&lt;/strong&gt;&lt;br&gt;
It only takes an afternoon to complete a set of wireframes. If you&amp;rsquo;re not sure which features need to be implemented first, experimenting with wireframes and seeing how testers react is a smart investment.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Find the problem.&lt;/strong&gt;&lt;br&gt;
Is something about your app confusing to people, but you can&amp;rsquo;t figure out how to fix it? Support tickets and pull-requests can only go so far. Sitting down to wireframe some alternatives can help your team untangle its thinking.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&#34;the-90-minute-no-drawing-skills-needed-wireframe-boot-camp&#34;&gt;The 90-minute-no-drawing-skills-needed wireframe boot camp&lt;/h2&gt;
&lt;p&gt;Wireframing is a quick way to validate your design. It saves on wasted development time, and anyone can do it. When you are ready to test out a new interface, wireframing will help you drill down to the best UI and help you organize your development priorities.&lt;/p&gt;
&lt;p&gt;You can start wireframing with little more than an hour and some basic office supplies. There are numerous apps such as &lt;a href=&#34;https://balsamiq.com/&#34;&gt;Balsamiq&lt;/a&gt; and &lt;a href=&#34;https://www.sketchapp.com/&#34;&gt;Sketch&lt;/a&gt; for making wireframes, but doing it by hand is more effective when you&amp;rsquo;re new to the process. Don&amp;rsquo;t waste time mastering wireframe software; spend that time building your UX acumen.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Materials needed:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Paper&lt;/li&gt;
&lt;li&gt;Black Sharpie marker&lt;/li&gt;
&lt;li&gt;Grey Sharpie (could be something like a highlighter, too)&lt;/li&gt;
&lt;li&gt;Different color marker for callouts (traditionally red)&lt;/li&gt;
&lt;li&gt;Optional: window to the outside for easy tracing&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;First, pick the website or app you want to analyze. I picked Twitter&amp;rsquo;s iOS app as the basis for my wireframes in this exercise. Even though I know the app well, taking the time to wireframe it helped me see the app more critically, and what I learned from wireframing will inform my design choices for similar apps.&lt;/p&gt;
&lt;h3 id=&#34;make-paper-printouts&#34;&gt;Make Paper Printouts&lt;/h3&gt;
&lt;p&gt;This tutorial works by tracing an existing app or website. To do that, you need paper printouts. If you&amp;rsquo;re analyzing a website, just print every page. If you picked an iOS app like me, here&amp;rsquo;s one way to print from iOS:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Capture screenshots of the screens you want to work on. I did this on my iPhone by pressing the power button and soft button at the same time. I sent the screenshots to my laptop, which is connected to a printer.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On a laptop, open every screenshot image and merge them into one file. You can do this on a Mac by using the Preview application to open the images. Go to View -&amp;gt; Thumbnail menu option and drag thumbnail images from different files into one thumbnail tray. Now you have a multipage file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide what scale or size works best for your needs.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Below, you can see what the screens look like when printed in the &amp;ldquo;4 up&amp;rdquo; setting from the Preview application. This is a good layout for mobile apps because it mimics a small screen and is easy to cut down to size.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/4up-color_hu_9c7c338afd80aac9.jpg&#34; alt=&#34;Image of four screenshots printed in greyscale on a single page.&#34; width=&#34;740&#34; height=&#34;987&#34;&gt;

&lt;em&gt;Image of screenshots in &amp;ldquo;4-up&amp;rdquo; setting.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/architecture_hu_a74d2f63865f86ba.jpg&#34; alt=&#34;Image of several screenshots pinned up on a board.&#34; width=&#34;740&#34; height=&#34;731&#34;&gt;

&lt;em&gt;Image of pinned-up architecture.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Cut out each screen to lay out the architecture. The typical way to lay out architecture is to make every item in the top row a global navigation choice. In the top row of my cutouts, I drew red squares around specific global navigation buttons to indicate the current state of the app. Each item underneath the top row represents a substate. In this example, only the &amp;ldquo;Me&amp;rdquo; column to the far right has other substates beneath it.&lt;/p&gt;
&lt;p&gt;Sometimes it&amp;rsquo;s easier to work with enlarged wireframes so there&amp;rsquo;s plenty of room to write out button names. In this example, I use words instead of icons to indicate what the buttons do.&lt;/p&gt;
&lt;p&gt;If you want to work with an enlarged version of the screen, you can sketch based on what you see on screen, but if you&amp;rsquo;re not used to sketching, you can start by tracing your printouts. You don&amp;rsquo;t need any equipment other than a window to do this. It works best if it&amp;rsquo;s brighter outside than inside. You can see the result of my tracing below.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/AmeAtWindow_hu_223ad48c35baa3e.jpg&#34; alt=&#34;Image of the author working with screenshots held up against a window.&#34; width=&#34;740&#34; height=&#34;987&#34;&gt;

&lt;em&gt;Tracing at a window.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/TracedImage_hu_c3315801475303eb.jpg&#34; alt=&#34;Image of a traced wireframe.&#34; width=&#34;740&#34; height=&#34;1008&#34;&gt;

&lt;em&gt;Tracing result.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;wireframing-at-the-right-level-of-abstraction&#34;&gt;Wireframing at the right level of abstraction&lt;/h3&gt;
&lt;p&gt;Since navigation is the focus of my wireframe, I only use color (gray shading in this case) to indicate what state the UI is in. Use abstractions such as wavy lines or lorem ipsum copy to represent user-generated content. Abstract representations keep testers focused on the navigation.&lt;/p&gt;
&lt;p&gt;Other elements can also cause confusion, even if users are generally familiar with them. When getting user feedback on a Twitter wireframe, things like &amp;ldquo;Name @handle&amp;rdquo; can be distracting. To avoid this, use something made up but recognizable like &amp;ldquo;Marie Curie @mcurie&amp;rdquo; if you plan to show that element to testers. If the audiences for your wireframe are people who are comfortable with pseudocodes, using &amp;ldquo;Name @handle&amp;rdquo; probably won&amp;rsquo;t throw them off, and in those cases, that level of abstraction is fine.&lt;/p&gt;
&lt;p&gt;These images show a progression from screen printout at left to the most abstract zones of activity.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/levels-of-abstraction_hu_5957839c7be90ccc.jpg&#34; alt=&#34;Three wireframes at varying levels of abstraction.&#34; width=&#34;740&#34; height=&#34;363&#34;&gt;

&lt;em&gt;Levels of abstraction.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/CloseUpAbstract_hu_31096b4d3398f4a8.jpg&#34; alt=&#34;A close-up image of one of the more abstract wireframes.&#34; width=&#34;740&#34; height=&#34;885&#34;&gt;

&lt;em&gt;An more abstract wireframe.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The red writing are callouts that describe what activity happens in each zone, with an emphasis on navigation.&lt;/p&gt;
&lt;p&gt;The next image is even more abstract, and it raises the question: Why are there four different button blocks spread across multiple zones?&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/zones-of-activity_hu_94cff1c41d784898.jpg&#34; alt=&#34;Image of a wireframe that highlights zones of activity.&#34; width=&#34;740&#34; height=&#34;987&#34;&gt;

&lt;em&gt;Zones of activity.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This wireframe of the Twitter iOS app really spotlights the trade-offs in navigation. There are four different areas of navigation (why?), and instead of using hamburger-, sidebar-, or other types of menus, the designers settled on buttons. There are positive and negative tradeoffs here. On the one hand, the buttons are self-disclosing, and it is immediately clear what sort of operations are possible. On the other hand, there&amp;rsquo;s a lot of clutter, and users have to look in multiple places to perform the operation they want.&lt;/p&gt;
&lt;p&gt;To practice wireframing, I suggest:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Draw whatever you&amp;rsquo;ve been working on, regardless of its state. Much like handwritten notes, even an hour of drawing helps me understand the logic behind the system.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Look for a widely admired version of the feature you&amp;rsquo;ve been working on. Sketch out a wireframe of what you find and then sketch out your version. Tools that have mass adoption have generally achieved high usability. Wireframing Amazon&amp;rsquo;s shopping cart gives a good understanding of what a successful cart needs. In this case, Twitter is a reasonable place to start if you want to understand the logic behind a complex communication app.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Analyze the similarities and differences between the other version and your version of the feature. What considerations underlie those design choices?&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;To set a benchmark for user profiles, you can make a series of wireframes by looking at popular services that have user profiles and using them as points of comparison.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Take a look at guides like this one on &lt;a href=&#34;http://www.dtelepathy.com/blog/design/learning-to-wireframe-10-best-practices&#34;&gt;10 best practices for wireframing&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;wireframes-trigger-insights&#34;&gt;Wireframes Trigger Insights&lt;/h2&gt;
&lt;p&gt;Have you ever given a slide presentation only to see a typo that you didn&amp;rsquo;t catch beforehand? Even though you rehearsed many times, the typo didn&amp;rsquo;t leap out at you until now. When it comes to UI, wireframing ensures against this. Like the exercise in this post, wireframing an app that you&amp;rsquo;re building will quickly reveal problems that you didn&amp;rsquo;t expect. Wireframing takes you out of the code and offers another context to critically examine engineering and design choices.&lt;/p&gt;
&lt;p&gt;Whether you&amp;rsquo;re working solo or on a team, wireframing is a quick and powerful way to think about the structure of your app and to prioritize improvements.&lt;/p&gt;
&lt;h2 id=&#34;going-deeper&#34;&gt;Going Deeper&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;http://eleganthack.com/&#34;&gt;Christina Wodke&lt;/a&gt; is one of the first information architects. She has years&amp;rsquo; worth of excellent posts on &lt;a href=&#34;http://boxesandarrows.com/&#34;&gt;Boxes and Arrows&lt;/a&gt;. &lt;a href=&#34;http://boxesandarrows.com/mythic-design/&#34;&gt;Mythic Design&lt;/a&gt;, one example of her many thought-provoking pieces, addresses the limits of wireframes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Abby Covert&amp;rsquo;s &lt;a href=&#34;http://abbytheia.com/makesense/&#34;&gt;How to Make Sense of Any Mess&lt;/a&gt; is a quick read and a classic resource on how to structure content.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Talking Across The Divide: Designing For More Than &#34;It&#39;s Secure&#34;</title>
      <link>https://superbloom.design/learning/blog/talking-across-divide/</link>
      <pubDate>Tue, 05 Jul 2016 19:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/talking-across-divide/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;re coming to the study of security and privacy from another field, it can sometimes be tough to get a clear answer to what seems like a simple question: Is this app secure? However, if you&amp;rsquo;re working on the user experience for that software, it&amp;rsquo;s critical that you understand the assumptions that security experts are making about your users and their behavior – and not just take the experts&amp;rsquo; word that all is well.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve written before that neither security nor usability are &lt;a href=&#34;https://superbloom.design/learning/resources/not-binary-properties&#34;&gt;binary properties&lt;/a&gt;. In a nutshell, this means that there&amp;rsquo;s a lot of gray area when it comes to deciding whether something is secure or insecure. Security enthusiasts often come at the problem by answering one question: Is this the most secure solution available? Meanwhile, non-experts are actually asking a different one: Is this secure enough for what I want to do? Like usability, security is defined as a function of a particular set of users and their needs – more specifically, as a function of the threats they face.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/buckets_hu_2c684074b820167c.png&#34; alt=&#34;Image of two buckets, labeled &amp;lsquo;secure&amp;rsquo; and &amp;lsquo;insecure&amp;rsquo;, with a marble labeled app and a question mark.&#34; width=&#34;740&#34; height=&#34;653&#34;&gt;

&lt;em&gt;It&amp;rsquo;s often hard to classify an app as being secure or insecure without additional context about the user and their goals.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re a designer, usability researcher, or other UX professional collaborating with a security engineer for the first time, it may be uncomfortable to push back and ask for more information about the app&amp;rsquo;s security features, especially if the answers are full of unfamiliar acronyms and buzzwords. And it&amp;rsquo;s tempting as a security expert to say something along the lines of, &amp;ldquo;trust me; this is secure.&amp;rdquo; But digging in to this kind of cross-discipline dialogue can be essential for identifying places that users will get tripped up. Talking across the divide can prevent an app that is secure in theory from becoming seriously flawed in practice.&lt;/p&gt;
&lt;p&gt;Here are some questions that teams of security experts and UX professionals should be able to answer about the software they are building together. This kind of conversation is best held in front of a whiteboard, where team members can communicate visually as well as verbally. Security experts should challenge themselves to offer complete explanations in accessible terms. Their partners should be vocal when a concept is not clear.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;What is the threat model (probable set of attacks) that the software protects against? Who are the &amp;ldquo;adversaries&amp;rdquo; that are likely to try and subvert the software, and what features are in place to protect against them? Include both attackers interested in your infrastructure (either for monetary gain or for &lt;a href=&#34;http://www.nytimes.com/2008/08/03/magazine/03trolls-t.html?_r=2&amp;amp;ref=technology&#34;&gt;the lulz&lt;/a&gt;) and in your users&amp;rsquo; data (whether they&amp;rsquo;re harvesting large quantities or carrying out a personal vendetta).&lt;/li&gt;
&lt;li&gt;What threats is the software currently vulnerable to? Don&amp;rsquo;t forget to consider users who are at risk of targeted attacks, such as domestic abuse survivors, investigative journalists, or LGBTQ activists around the world (one resource to help you get started is our former fellow Gus Andrews&amp;rsquo; &lt;a href=&#34;https://medium.com/@gusandrews/user-personas-for-privacy-and-security-a8b35ae5a63b#.gmcvkdhkt&#34;&gt;set of user personas for privacy and security&lt;/a&gt;). Remember in particular that some people are targeted by their telecom providers and even their governments.&lt;/li&gt;
&lt;li&gt;How does the UX help users understand both the protections the software offers and the protections it does not offer? Given the people who use the software (or are likely to use it in the future), does the UX do an accurate and reasonable job at conveying how it aims to keep its users secure? For example, if the software advertises encryption, is it truly to inform users or simply to smooth over their fears (pro tip: the phrase &amp;ldquo;military-grade encryption&amp;rdquo; is never a good sign for users)? If your chat app&amp;rsquo;s messages automatically disappear, do people understand that there are ways those messages may still be retained?&lt;/li&gt;
&lt;li&gt;Are there things that users can do – or fail to do – that will expose them to additional risk? Does the UX help shape their behavior appropriately to counter this eventuality? For example, does the app periodically encourage users to protect their accounts with basic features like two-factor authentication? Does it just send two-factor codes by SMS or also support alternatives like app-generated codes or hardware tokens?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This is just a starting point in what we hope will become an ongoing conversation between UX professionals and their security-minded colleagues. Great software is built around excellent user experiences, and keeping users&amp;rsquo; data safe is a core (if often implicit) user need. For this reason, we believe designers and UX researchers can be important advocates for user security. Conversations across the divide are an important first step to making this a reality.&lt;/p&gt;
&lt;p&gt;Would your team like help talking through these types of issues? We can lend a hand. Drop us a line at &lt;a href=&#34;mailto:contact@simplysecure.org&#34;&gt;contact@simplysecure.org&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Safeguarding Research Participants With A Bill Of Rights</title>
      <link>https://superbloom.design/learning/blog/participant-rights/</link>
      <pubDate>Tue, 28 Jun 2016 13:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/participant-rights/</guid>
      <description>&lt;p&gt;In this installment of our series on resources for field research, we discuss the &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Research/2015_NYC_Mobile_Messaging/NYCMobMsgParticipantBillofRights.pdf&#34;&gt;participant&amp;rsquo;s bill of rights&lt;/a&gt;. Additional resources include &lt;a href=&#34;https://superbloom.design/learning/blog/recruiting-screeners&#34;&gt;screeners&lt;/a&gt; and &lt;a href=&#34;https://superbloom.design/learning/blog/model-release&#34;&gt;model releases for photography&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;why-consent-matters&#34;&gt;Why Consent Matters&lt;/h2&gt;
&lt;p&gt;Field research such as interviews and observations are an important part of Human-Centered Design. As important as learning about first-person, lived experiences is to the design process, the act of participating in an interview can feel awkward. There is an inherent power dynamic that puts researchers in a dominant position; for all that participants know, once they share a personal story, researchers are free to use it as they please.&lt;/p&gt;
&lt;p&gt;While an interview may seem innocuous, it can put participants in harm&amp;rsquo;s way when handled improperly. Consent is a safeguard that stems from a collection of unethical scientific studies such as the &lt;a href=&#34;https://en.wikipedia.org/wiki/Tuskegee_syphilis_experiment#Ethical_implications&#34;&gt;Tuskegee experiment&lt;/a&gt;, where Black men who had syphilis were not told that they were infected, and not told that their condition was the primary reason for the study. This and other experiments from earlier eras caused lifelong trauma for their participants.&lt;/p&gt;
&lt;p&gt;While research on technology projects may seem less dangerous than medical experiments, they can also harm participants. For example, people can suffer serious consequences from online behavior, including lowered credit scores, loss of livelihood, and threats to their safety or the safety of their loved ones. When a researcher shares participants&amp;rsquo; stories, they are vulnerable to similar consequences if those stories can be traced back to participants through personally-identifiable details.&lt;/p&gt;
&lt;p&gt;Ethical researchers generally use a consent form that both informs and assures participants that they have rights. This is called &amp;ldquo;informed consent,&amp;rdquo; and by signing the consent form, participants acknowledge that they understand what kinds of data are being gathered and how the data will be used.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/participant-discussion_hu_b1b2cd099692a3a2.jpg&#34; alt=&#34;Photo of the author looking at papers with a study participant.&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;balancing-the-power-dynamic&#34;&gt;Balancing the power dynamic&lt;/h2&gt;
&lt;p&gt;We use the phrase &amp;ldquo;participant&amp;rsquo;s bill of rights&amp;rdquo; for our informed consent document to convey that the participant has control over aspects of the process. There are three main areas in the bill of rights:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The power to ask questions:&lt;/strong&gt; Participants are empowered to ask questions and give feedback about the interviewer, including speaking to a superior. The form should include contact information for the interviewer&amp;rsquo;s superior.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Compensation just for showing up:&lt;/strong&gt; Participants can refuse to answer individual questions, refuse to participate, or leave, but still be compensated.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Controlling what&amp;rsquo;s captured and how it&amp;rsquo;s shared:&lt;/strong&gt; Participants understand that researchers will not record the interview, take their photo, or quote them unless participants give their consent. Researchers will take appropriate measures to contact participants about any media they want to use publicly, and participants can review the media content before it is shared. They can also request the removal of any materials that have already been shared publicly.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;example-bill-of-rights&#34;&gt;Example bill of rights&lt;/h2&gt;
&lt;p&gt;Below is an example of a participant&amp;rsquo;s &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Research/2015_NYC_Mobile_Messaging/NYCMobMsgParticipantBillofRights.pdf&#34;&gt;bill of rights&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;We respect you and appreciate your time. Everyone participating in an interview has the following rights:&lt;/em&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;I can ask questions about the interview, the organization, or the interviewer at any time&lt;/li&gt;
&lt;li&gt;I do not have to answer any question that I do not want to&lt;/li&gt;
&lt;li&gt;I can refuse for the interview to be recorded by video or audio, and I will still be compensated&lt;/li&gt;
&lt;li&gt;I can leave at any time, and I will still be compensated&lt;/li&gt;
&lt;li&gt;I can provide confidential feedback about my interview experience to the interviewer&amp;rsquo;s manager&lt;/li&gt;
&lt;li&gt;I must approve the use of any photos, audio, video, or anonymized quotes that are used publicly, whether on a website, on a blog, or in the press&lt;/li&gt;
&lt;li&gt;Even after a photo, video, or quote has been published, I have the right to request its removal at any point in the future&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;em&gt;You can reach us anytime by calling or texting to [x] or by email at [x].&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;tips-to-consider&#34;&gt;Tips to Consider&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Select an approachable name for the document:&lt;/strong&gt; In medical or psychological contexts, these consent documents are reviewed by Committees for the &lt;a href=&#34;https://en.wikipedia.org/wiki/National_Commission_for_the_Protection_of_Human_Subjects_of_Biomedical_and_Behavioral_Research&#34;&gt;Protection of Human Subjects&lt;/a&gt;. As a term, &amp;ldquo;human subjects&amp;rdquo; may be technically correct, but it is distant and off-putting. At Simply Secure, we intentionally selected &amp;ldquo;participant&amp;rsquo;s bill of rights&amp;rdquo; to provide clear language and to empower participants.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Print the bill of rights on letterhead:&lt;/strong&gt; Use your organization&amp;rsquo;s name and logo to make this look official.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Be accessible:&lt;/strong&gt; Bring two copies of the consent form so that participants can take one with them. This should include contact information for someone in your organization who is not the interviewer in case the participant wants to discuss a negative experience.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Take only what you need:&lt;/strong&gt; Be mindful of appropriately secure channels for communication. Safeguard necessary physical documentation in a locked cabinet, and shred anything that you have no reason to keep.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We invite you to adapt this bill of rights to suit your needs.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Model Release: Respectfully Sharing Stories</title>
      <link>https://superbloom.design/learning/blog/model-release/</link>
      <pubDate>Tue, 21 Jun 2016 16:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/model-release/</guid>
      <description>&lt;p&gt;This post is part of a series explaining our publicly available &lt;a href=&#34;https://github.com/simplysecure/resources/tree/master/Research/2015_NYC_Mobile_Messaging&#34;&gt;resources&lt;/a&gt; for user research. The previous installment covered &lt;a href=&#34;https://superbloom.design/learning/blog/recruiting-screeners&#34;&gt;how to write screeners&lt;/a&gt; to recruit participants. This week, we discuss how to get &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Research/2015_NYC_Mobile_Messaging/NYCMobMsgModelRelease.pdf&#34;&gt;model releases&lt;/a&gt; to share photos from user studies.&lt;/p&gt;
&lt;h2&gt;One approach among many&lt;/h2&gt;&lt;p&gt;At Simply Secure, we strive to balance study participants&#39; privacy with building  empathy in an audience of developers, policymakers, and designers by sharing study photos and stories. Meanwhile, many startups have used exploitative and borderline unethical user testing methods that make extensive use of behavior tracking. Privacy-preserving technology is evolving. Now is the time to develop best practices that both enable meaningful data collection on user experience and respect users&#39; privacy. There are many ethical ways to handle data collection, and the following is an approach we used in one of our studies.&lt;/p&gt;
&lt;p&gt;We recently conducted a user study about participants&#39; experience with surveillance and the strategies they use to preserve their privacy. There&#39;s an inherent paradox in recording a conversation about surveillance, and to acknowledge this, we decided that handwritten notes were sufficient to capture attitudes towards surveillance and personal strategies to get around it. Instead of recording audio or video during the interviews, our researchers only took notes on paper. In situations where anonymity is critical to our participants&#39; safety, we asked them to tell us what they&#39;d like to be called rather than collecting their names and contact details.
&lt;/p&gt;
&lt;h2&gt;Why take photographs?&lt;/h2&gt;
&lt;p&gt;As a designer, I&#39;m a visual person and find photos to be a powerful note-taking tool and memory aid. When I look at a photo from a user study from 10 years ago, I can remember specific details of the conversation and insights from the study even though I haven&#39;t interacted with the participant since then. Not only are photos useful to designers as memory aids, they are powerful in inviting an audience into a user&#39;s story. They help the audience internalize learnings from a study. &lt;/p&gt;
&lt;h2&gt;Photography is always an opt-in process&lt;/h2&gt;
&lt;p&gt;Despite its benefits as a mnemonic, participants should never feel pressured to have their photo taken. At the beginning of Simply Secure interviews, participants are given a Participant&#39;s Bill of Rights that outlines consent procedures, including the ability to refuse any questions, quit and still be compensated, and refuse photography.&lt;/p&gt;
&lt;p&gt;In a winter 2015 study, we helped participants understand how the photos could be used by showing them photos from the &lt;a href=&#34;https://www.instagram.com/humansofny/?hl=en&#34;&gt;Humans of New York&#39;s (HONY)&lt;/a&gt; Instagram feed. HONY combines photos of people in public space, with descriptions of what they are doing or thinking. These powerful stories are akin to bite-sized doses of user research. We used HONY&#39;s feed to demonstrate how we might share their stories and personally ­identifiable photos on the public web.&lt;/p&gt;
&lt;p&gt;In the final 5-10 minutes of our session, we asked if people were comfortable posing for photos. Doing this at the end is beneficial because participants have a clearer idea of who we are and are conscious of the stories they&#39;ve shared. Participants could choose from three types of photographic participation: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;No photography&lt;/li&gt;
&lt;li&gt;Being photographed in a personally meaningful but non-­identifiable way (such as their shoes or purses)&lt;/li&gt;
&lt;li&gt;Being photographed in an identifiable way &lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What a model release means&lt;/h2&gt;
&lt;p&gt;Our default is to avoid collecting personally-identifiable information, but in instances where we do, we ask study participants to sign our model release. This step is central to how Simply Secure balances building audience empathy and protecting participants&#39; privacy. &lt;/p&gt;
&lt;p&gt;There are clear concerns that modeling is exploitative and harmful to people, and the choice of using a model release—and calling it a &#34;model release&#34;—is an intentional one. &lt;/p&gt;
&lt;p&gt;An important ethical consideration of model releases is that models &lt;a href=&#34;https://medium.com/@AndyKimy/things-i-learned-doing-stock-photography-modeling-9b5812d832b5#.2cfxfddng&#34;&gt;lose control&lt;/a&gt; of their images and cannot choose how their narratives will be paired with them. When using HONY as an example, we showed a photo of &lt;a href=&#34;https://www.instagram.com/p/96lwfutrC9/?taken-by=humansofny&amp;hl=en&#34;&gt;a man who talked about the aftermath of his domestic violence conviction&lt;/a&gt;. By talking through this provocative example, we were confident that our participants appreciated how hard it can be to get a nuanced picture of people&#39;s stories.&lt;/p&gt;
&lt;p&gt;We explained that although we had no plans to put the images on Instagram, we would like to share them on our blog and in presentations. That&#39;s a much smaller audience than popular Instagram feeds, but there are implications of sharing photos anywhere on the open web.
&lt;/p&gt;
&lt;h2&gt;Some examples&lt;/h2&gt;
&lt;p&gt;Of the 12 participants in our study, three signed model releases, five agreed to non-personally-identifiable photos, and four did not want to be photographed. We took photos with an iPhone, and everyone was offered a chance to review them. Rather than candid shots, we took staged photos to portray the participants as powerful, positive people. After some minor photo filtering and cropping, we sent copies of the photos to participants who signed model releases to get their approval for public use. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/SignedRelease_hu_87defa5728f6bbf7.jpg&#34; alt=&#34;Missing alt text&#34; width=&#34;740&#34; height=&#34;285&#34;&gt;

&lt;br/&gt;
&lt;em&gt;Study participants who signed model releases for sharing photos.&lt;/em&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/Non-Identifiable_hu_5f3eb24bdb5e264b.jpg&#34; alt=&#34;Missing alt text&#34; width=&#34;740&#34; height=&#34;311&#34;&gt;

&lt;br/&gt;
&lt;em&gt;Non-personally identifiable photos, taken with verbal consent, but not a signed model release.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;We&#39;re still learning&lt;/h2&gt;
&lt;p&gt;Since our study was about surveillance and personal strategies to preserve privacy, we asked participants to show us examples of how they use their phones. With their permission, we photographed their phones. We blurred out their names and personal information before sharing any photos publicly, but photos with homescreens, photos, and wallpaper required extra sensitivity.&lt;/p&gt;
&lt;p&gt;Consider the photos below. One of the participants had a photo of herself as the wallpaper. She was comfortable sharing the photo and signed a model release. But what should we do if her wallpaper were a photo of another private individual? How should we approach photography when the wallpaper is a photo of a child? Complicating matters, does it change things if the participant is the parent versus a relative of the child?&lt;/p&gt;
![Missing alt text](/images/blog/2016/VarietyOfPhones.jpg)
&lt;br/&gt;
&lt;em&gt;Participants&#39; phones. Photos shared by consent with identifiable text blurred. &lt;/em&gt;
&lt;p&gt;We are still learning at Simply Secure, and we believe that a human-centered approach should be a best practice in developing privacy-preserving software. We welcome discussion about best practices for ethical research. &lt;/p&gt;
&lt;p&gt;Tell us what you think of how a background image of other private individuals fits into personally identifiable information. If you are a researcher and want to join the research dialogue on our Slack channel, email &lt;a href=&#34;mailto:slack@superbloom.design&#34;&gt;slack@superbloom.design&lt;/a&gt;. &lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Event: UX in a High-Risk World</title>
      <link>https://superbloom.design/community/events/ux-high-risk/</link>
      <pubDate>Fri, 17 Jun 2016 14:30:00 -0400</pubDate>
      <guid>https://superbloom.design/community/events/ux-high-risk/</guid>
      <description>&lt;p&gt;As you know, building great software depends on a deep knowledge of users. If you&#39;re working on a project targeted at people who operate in high-risk situations, such as activists and journalists, it can be hard to get the quality insight you need to design features and experiences that will work for them. &lt;/p&gt;
&lt;p&gt;If you&#39;re based in the San Francisco Bay area, there&#39;s an exciting event happening in July that focuses especially on user experiences for this population. &lt;a href=&#34;https://www.eventbrite.com/e/ux-in-a-high-risk-world-tickets-25739389206&#34;&gt;UX in a High-Risk World&lt;/a&gt;, hosted by Internews on Thursday July 14th, will bring together &#34;visionary leaders who are piloting and developing solutions for activists facing censorship, hacking, surveillance, and suppression in some of the world&#39;s most challenging environments&#34;. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/ux-high-risk_hu_18e62b75c68de72f.png&#34; alt=&#34;Missing alt text&#34; width=&#34;740&#34; height=&#34;448&#34;&gt;
&lt;/p&gt;
&lt;p&gt;This is a great opportunity to talk not just about building secure, privacy-preserving software, but about the lived experiences of users who have an urgent need for it. We think that this is an important conversation, and we&#39;re offering support by sharing it with our community of partners and volunteers. &lt;/p&gt;
&lt;p&gt;Internews will also announce the UXFund Call for Proposals at the event. As the event description notes, &#34;UXFund is a small-grants program to support usability and accessibility improvements for open-source digital security tools.&#34;&lt;/p&gt;
&lt;p&gt;Attendance is free but admission is limited, so if you want to go, &lt;a href=&#34;https://www.eventbrite.com/e/ux-in-a-high-risk-world-tickets-25739389206&#34;&gt;register&lt;/a&gt; before the July 6th deadline!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Event: UX in a High-Risk World</title>
      <link>https://superbloom.design/learning/blog/ux-high-risk/</link>
      <pubDate>Fri, 17 Jun 2016 14:30:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/ux-high-risk/</guid>
      <description>&lt;p&gt;As you know, building great software depends on a deep knowledge of users. If you&amp;rsquo;re working on a project targeted at people who operate in high-risk situations, such as activists and journalists, it can be hard to get the quality insight you need to design features and experiences that will work for them.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re based in the San Francisco Bay area, there&amp;rsquo;s an exciting event happening in July that focuses especially on user experiences for this population. &lt;a href=&#34;https://www.eventbrite.com/e/ux-in-a-high-risk-world-tickets-25739389206&#34;&gt;UX in a High-Risk World&lt;/a&gt;, hosted by Internews on Thursday July 14th, will bring together &amp;ldquo;visionary leaders who are piloting and developing solutions for activists facing censorship, hacking, surveillance, and suppression in some of the world&amp;rsquo;s most challenging environments&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/ux-high-risk_hu_18e62b75c68de72f.png&#34; alt=&#34;Missing alt text&#34; width=&#34;740&#34; height=&#34;448&#34;&gt;
&lt;/p&gt;
&lt;p&gt;This is a great opportunity to talk not just about building secure, privacy-preserving software, but about the lived experiences of users who have an urgent need for it. We think that this is an important conversation, and we&amp;rsquo;re offering support by sharing it with our community of partners and volunteers.&lt;/p&gt;
&lt;p&gt;Internews will also announce the UXFund Call for Proposals at the event. As the event description notes, &amp;ldquo;UXFund is a small-grants program to support usability and accessibility improvements for open-source digital security tools.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Attendance is free but admission is limited, so if you want to go, &lt;a href=&#34;https://www.eventbrite.com/e/ux-in-a-high-risk-world-tickets-25739389206&#34;&gt;register&lt;/a&gt; before the July 6th deadline!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Compelling Color</title>
      <link>https://superbloom.design/learning/resources/compelling-color/</link>
      <pubDate>Fri, 10 Jun 2016 19:30:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/compelling-color/</guid>
      <description>&lt;p&gt;Great user experiences are born through the hard work of professionals with a variety of skills. As illustrated by the UX unicorn we&amp;rsquo;ve &lt;a href=&#34;https://superbloom.design/learning/blog/self-starter&#34;&gt;seen before&lt;/a&gt;, there&amp;rsquo;s a lot that goes into what we call &amp;ldquo;design&amp;rdquo; or &amp;ldquo;usability.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/UXUnicorn_hu_e01443dc5f39ab.png&#34; alt=&#34;Image of a unicorn composed of different elements of the user-experience process&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The skills and responsibilities of an effective UX team. Originally published in &lt;a href=&#34;http://blog.invisionapp.com/building-an-enterprise-ux-team&#34;&gt;Building an enterprise UX team&lt;/a&gt; by &lt;a href=&#34;https://twitter.com/RainbowliciousD&#34;&gt;Rachel Daniel&lt;/a&gt; (also on &lt;a href=&#34;https://www.linkedin.com/in/racheldaniel&#34;&gt;LinkedIn&lt;/a&gt;), UX Director at MaxPoint. Used by permission.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Looking at this unicorn illustration, it may be tempting to dismiss visual design as a &amp;ldquo;nice to have&amp;rdquo; skill. After all, it&amp;rsquo;s possible to make a basically functional piece of software without paying any particular attention to the visual design (just as a horse can get by without a horn). And unlike interaction design, which is possible to evaluate empirically through user studies, it can be hard to pin down exactly what makes a visual design &amp;ldquo;good.&amp;rdquo; This subjectivity can be compounded by visual design’s tendency to evolve and trend over time.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/ios67_hu_e15f1588918af0b3.png&#34; alt=&#34;Screenshots of iOS 6 and iOS 7&#34; width=&#34;740&#34; height=&#34;657&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Observe the difference in the visual design in the icons of iOS6 (left) and iOS 7 (right). This change would appear to be driven largely by a desire to have the apps look fresh, new, and modern.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;But visual design is about more than just making something pretty or trendy. Visual design includes typography, iconography, and color, all of which can contribute or detract from usability. These basic elements of visual design usually follow well-understood rules.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/visual-design-is-key_hu_dc3e9c92e432ffaa.png&#34; alt=&#34;Two versions of the phrase visual design is key, one of which is easily legible and the other of which is not.&#34; width=&#34;740&#34; height=&#34;391&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Typography and color selection can make or break a user&amp;rsquo;s experience.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s focus for now on some basic ideas around color. A consistent and tasteful palette can be a great way to make your software, website, newsletter, and print materials more usable and attractive to your users. Simply Secure worked with a professional visual designer to come up with our colors (as documented in a post about our &lt;a href=&#34;https://superbloom.design/learning/blog/style-guide&#34;&gt;style guide&lt;/a&gt;), but it&amp;rsquo;s possible for even people new to design to select a set of tasteful hues. Here are some tips to get you started.&lt;/p&gt;
&lt;h2 id=&#34;read-up-on-the-basics&#34;&gt;Read up on the basics&lt;/h2&gt;
&lt;p&gt;Are you confused by terms like &lt;em&gt;hue&lt;/em&gt;, &lt;em&gt;saturation&lt;/em&gt;, and &lt;em&gt;brightness&lt;/em&gt;, and what bearing they have on making a color scheme attractive? Ria Carmin&amp;rsquo;s &lt;a href=&#34;https://blog.prototypr.io/design-for-programmers-d38c56982cd0&#34;&gt;developer-targeted post&lt;/a&gt; addresses exactly that. (See &amp;ldquo;Rule 3: Color&amp;rdquo;.) She does a great job of breaking down different types of color palettes, such as those that follow a monochromatic, analogous, complementary, or triad scheme.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/color-pickers_hu_5736a4f530a7e9be.png&#34; alt=&#34;Screenshots of three color picker interfaces.&#34; width=&#34;740&#34; height=&#34;275&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Traditional color pickers can be limiting, imprecise, or hard for color novices to understand.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;choose-your-tool-carefully&#34;&gt;Choose your tool carefully&lt;/h2&gt;
&lt;p&gt;When making a color palette, don&amp;rsquo;t work with individual colors in isolation. Many traditional color pickers in graphics software can be limiting, imprecise, or hard to understand. Free online tools such as &lt;a href=&#34;https://color.adobe.com/&#34;&gt;Adobe Color&lt;/a&gt;, &lt;a href=&#34;http://paletton.com/&#34;&gt;Paletton&lt;/a&gt;, and &lt;a href=&#34;https://coolors.co/&#34;&gt;Coolors&lt;/a&gt; can help you identify a collection of colors that work well together. To play it safe, use the default settings and carefully modify one color at a time to watch the rest of the palette adjust.&lt;/p&gt;
&lt;h2 id=&#34;dont-go-to-the-extreme&#34;&gt;Don&amp;rsquo;t go to the extreme&lt;/h2&gt;
&lt;p&gt;While it&amp;rsquo;s tempting to try and send a strong message about your software by using lots of intense colors, remember that moderation can go a long way toward making your project look professional and credible. Developers in the security community seem particularly drawn toward dark shades, which can feel unapproachable to some users. Another tendency is to pick the brightest, most saturated colors available, which can also be off-putting. Finally, remember that color is often used best as a highlight, not as the main body. Whites and greys with a small, coherent selection of accent colors allow the user&amp;rsquo;s eyes to quickly identify what belongs in the background and what needs their attention. For example, Simply Secure uses lots of bright colors on our webpage, but the main body of each page is a neutral white or off-white.&lt;/p&gt;
&lt;p&gt;Has your team been struggling with color? Did you recently go through a redesign that you&amp;rsquo;re proud of? We&amp;rsquo;d like to hear from you; please &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;get in touch!&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Selecting Research Participants for Privacy and Beyond</title>
      <link>https://superbloom.design/learning/blog/recruiting-screeners/</link>
      <pubDate>Fri, 03 Jun 2016 14:30:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/recruiting-screeners/</guid>
      <description>&lt;p&gt;A screener is a questionnaire that helps researchers recruit the most appropriate participants for their user study research.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Research/2015_NYC_Mobile_Messaging/NYCMobMsgScreener.pdf&#34;&gt;Here&lt;/a&gt; is an example we used for our mobile messaging study in NYC. Blue Ridge Labs handled the recruiting. Most of this screener&amp;rsquo;s questions are a standard part of how they work with potential participants. Our questions, in red, focus on messaging and attitudes towards privacy. Additional questions about VPN use, email, and getting online were for our Fellow &lt;a href=&#34;https://medium.com/@gusandrews&#34;&gt;Gus Andrews&amp;rsquo;s research.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This example question sorts candidates into how frequently they message:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;About how many messages would you say you send via your phone in an average week? This includes text, Facebook messages, WhatsApp, etc.&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Less than 10&lt;/li&gt;
&lt;li&gt;Between 11-30&lt;/li&gt;
&lt;li&gt;31-50&lt;/li&gt;
&lt;li&gt;More than 50&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Questions like this can allow researchers to select a balanced mix of participants – for example, a few who message infrequently and a few who message heavily. In our case, we wanted frequent messagers, and used this question to meet with people sending 31 or more messages per week. (In practice most participants sent more than 50.) In recruiting terms, we screened out people sending 30 or fewer messages.&lt;/p&gt;
&lt;p&gt;Screeners are a regular part of user research for studies on everything from breakfast-cereal selection to the usability of enterprise software. Professional recruiters rely on screeners to match participants with projects. Even if a team handles their own recruiting, such as by posting a listing in a café or on a message board, screeners can still be helpful. The process of creating one helps a team be very specific about who they want to talk to, and forces them to clarify who they think will use (or not use) their product.&lt;/p&gt;
&lt;h2 id=&#34;tips-for-effective-screeners&#34;&gt;Tips for Effective Screeners&lt;/h2&gt;
&lt;p&gt;Here are some considerations for writing effective screeners for privacy-preserving technologies and beyond.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Don&amp;rsquo;t ask for information you don&amp;rsquo;t need.&lt;/strong&gt;
When you complete a screener, you gather personally-identifiable information about people and are responsible for storing it securely. Is gender identity relevant? Income? Zip code? Nationality? There are good reasons for collecting answers to those questions, but if they aren&amp;rsquo;t directly relevant to your study, don&amp;rsquo;t ask. Potential participants are more likely to complete a shorter, more-targeted questionnaire. The faster you get enough completed questionnaires, the sooner you can recruit enough candidates to start your study. Our example screener included questions from our partner Blue Ridge Labs that weren&amp;rsquo;t immediately relevant to our work. The disadvantage of having extra questions was offset by the advantage of having our partner manage participants&amp;rsquo; information. Simply Secure has no way to identify or contact the participants since we never had access to the data.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Instead of yes/no questions, ask multiple choice or open-ended questions.&lt;/strong&gt;
Yes/no questions tend to be more leading and encourage the potential participant to answer correctly rather than truthfully. For example, ask &amp;ldquo;How many text messages do you send in a week?&amp;rdquo; instead of &amp;ldquo;Do you send more than X messages?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;People are more than their demographics.&lt;/strong&gt;
Think of ways to ask questions about behaviors or attitudes, not just descriptive demographics like age. &amp;ldquo;So easy your mother could use it&amp;rdquo; assumes that mothers have more trouble using technology than other groups. Don&amp;rsquo;t assume that people in a particular demographic will all be the same or have the behaviors you&amp;rsquo;re looking for. Tech enthusiasts and tech-avoidant people come in all ages, sizes, colors, and genders.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;If the research is in-person, rather than on-line, screen for people who want to share their stories.&lt;/strong&gt;
Screeners are used for both qualitative, in-person research and quantitative, online research like surveys. If you&amp;rsquo;re recruiting for in-person research, you&amp;rsquo;ll want to talk to potential candidates first to see how comfortable they are responding to questions. Having a thick accent, making grammar mistakes, or being shy shouldn&amp;rsquo;t be barriers to participating in an interview. But someone who is ambivalent about the topic or uninterested in answering questions won&amp;rsquo;t be as good at inspiring a design team empathize with them. Our screener with Blue Ridge Labs used &amp;ldquo;must talk in more than one-word answers&amp;rdquo; as a criterion.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Availability questions can shorten time between screener and study.&lt;/strong&gt;
Ask which of several times participants are available for a feedback session. For example, consider this question:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Select all times you are available to meet at [address]:&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Monday, June 3 at 1:00pm&lt;/li&gt;
&lt;li&gt;Monday, June 3 at 2:30pm&lt;/li&gt;
&lt;li&gt;Tuesday, June 4 at 6:00pm&lt;/li&gt;
&lt;li&gt;Tuesday, June 4 at 7:30pm&lt;/li&gt;
&lt;li&gt;None of the above&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Questions like this remove the need for an extra step in determining availability. Be sure to ask how people want to be contacted for follow up for their available times. If you plan to meet someone Monday, don&amp;rsquo;t send emails to a work address they don&amp;rsquo;t check over the weekend.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Make room for non-users.&lt;/strong&gt;
Teams can learn a lot from carefully listening to people who aren&amp;rsquo;t already interested in their projects. Making room in the screener to capture people who, for example, haven&amp;rsquo;t heard of two-factor authentication can lead to important insights about designing broadly-appealing, generally-accessible software.&lt;/p&gt;
&lt;h2 id=&#34;get-the-right-people&#34;&gt;Get the Right People&lt;/h2&gt;
&lt;p&gt;Screeners are helpful for making sure studies get the right mix of participants. They are also part of the foundation of a process for getting critical user feedback early and often. Taking the time to ask a few basic questions up front can set up the whole study – and project – for success.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/participant-discussion_hu_b1b2cd099692a3a2.jpg&#34; alt=&#34;Ame and a participant sitting at a table.&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;br&gt;
&lt;em&gt;Learning from a Blue Ridge Labs participant recruited using our screener.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;resources&#34;&gt;Resources:&lt;/h3&gt;
&lt;p&gt;Simply Secure&amp;rsquo;s &lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Research/2015_NYC_Mobile_Messaging/NYCMobMsgScreener.pdf&#34;&gt;NYC Mobile Messaging Screener&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;further-reading&#34;&gt;Further Reading:&lt;/h3&gt;
&lt;p&gt;GV&amp;rsquo;s &lt;a href=&#34;https://library.gv.com/how-to-find-great-participants-for-your-user-study-da20f98dad9e#.bxovavq37&#34;&gt;How to Find Great Participants&lt;/a&gt; (includes screener worksheet)
Spring UX&amp;rsquo;s &lt;a href=&#34;https://medium.com/@SpringUX/amy-and-susans-research-management-tips-and-tricks-the-recruit-9e646f1706e9#.2kv2w2k76&#34;&gt;Managing the Recruit&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Meeting Users&#39; Needs: The Necessary Is Not Sufficient</title>
      <link>https://superbloom.design/learning/blog/necessary-not-sufficient/</link>
      <pubDate>Fri, 27 May 2016 16:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/necessary-not-sufficient/</guid>
      <description>&lt;p&gt;Building great software requires understanding what users want and need. If you’re building privacy-preserving software, this includes understanding the privacy threats that your users face. &lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/nyc-participant_hu_3663ba13b335d0a1.jpg&#34; alt=&#34;Photo of a woman standing on a city sidewalk.&#34; width=&#34;740&#34; height=&#34;987&#34;&gt;

&lt;br/&gt;&lt;em&gt;One of the participants in Ame’s NYC study.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;When Ame &lt;a href=&#34;https://superbloom.design/learning/blog/straight-talk&#34;&gt;set out to talk&lt;/a&gt; to people in the New York City neighborhoods of Brownsville and Harlem about their experiences with mobile messaging, she wanted to amplify voices that are frequently underrepresented in the software community. (Many thanks again to &lt;a href=&#34;https://www.labs.robinhood.org/dig&#34;&gt;Blue Ridge Labs&lt;/a&gt; for helping her connect with study participants.)&lt;/p&gt;
&lt;p&gt;Big tech companies usually end up focusing their user research on the affluent Silicon-Valley dwellers that resemble their employees. Many funders of internet-freedom software are interested in the needs of activists and journalists. As a result, the software requirements of other people – folks who aren’t activists, but who have modest financial means – are not heard by developers, product managers, and other decision-makers who shape the features and presentation of software today. &lt;/p&gt;
&lt;h2&gt;Important nuances&lt;/h2&gt;
&lt;p&gt;Ame began sharing findings of the study with researchers, developers, and members of our Slack community to seek feedback. We were excited and gratified to see it referenced in a &lt;a href=&#34;https://vnhacker.blogspot.com/2016/05/security-and-privacy-in-google-allo.html&#34;&gt;recent blog post&lt;/a&gt; by a Google security engineer who contributed to &lt;a href=&#34;https://allo.google.com/&#34;&gt;Allo&lt;/a&gt;, the new instant-messaging app that the company announced during I/O. (Note: the engineer wrote the post as a personal opinion, not in his official capacity as a Google employee. He subsequently made several changes to the wording of the post, we assume at his employer’s request.) &lt;/p&gt;
&lt;p&gt;The blog post highlights that study participants expressed concern around physical threats like shoulder surfing, and that they see disappearing messaging (where messages are automatically deleted after a certain amount of time) as a key protective feature. &lt;/p&gt;
&lt;p&gt;We were pleased, because the post signified that this research was already reaching software decision-makers. It validated our belief that this kind of study, which amplifies the voices of underrepresented users, holds real potential to influence the features and priorities of software teams.&lt;/p&gt;
&lt;p&gt;However, we were less pleased by this part of the post: “Most people focus on end-to-end encryption, but I think the best privacy feature of Allo is disappearing messaging. This is what users actually need when it comes to privacy.”&lt;/p&gt;
&lt;p&gt;It’s true that our writeups of the study thus far have talked about the mismatch between privacy enthusiasts’ priorities (e.g. end-to-end encryption) and participants’ requested security features (e.g. disappearing messaging). However, we have never argued that disappearing messages should come at the expense of end-to-end encryption.&lt;/p&gt;
&lt;p&gt;Participants in the study saw disappearing messaging as an important feature because it combats a set of threats that they feel they have some control over. That doesn’t mean that those are the only threats that they care about. Indeed, participants also expressed concern about government surveillance, while simultaneously conveying a sense of inevitability. If you believe the government will always have the power to spy on you, why would you waste time trying to find software that prevents that spying?&lt;/p&gt;
&lt;h2&gt;False dichotomies&lt;/h2&gt;
&lt;p&gt;The Allo team has faced significant criticism by members of the security community because they plan to make its end-to-end encryption opt-in rather than on by default. They argue that this allows users to upgrade their security if they want, but otherwise have immediate access to chatbot-style, AI-powered features. Until we can actually use the product, it’s hard to know whether this dichotomy – privacy vs. chatbot goodness – is really a necessary one. Is it truly impossible to both provide end-to-end encryption for interpersonal channels and offer an advanced bot interface on another? &lt;/p&gt;
&lt;p&gt;If it is the case that users have to choose between a feature that offers chatbot functionality and one that works to preserve their privacy, let’s all be honest about the decision that’s being made. Don’t imply that disappearing messaging is sufficient because it’s what users are already asking for. Meeting user demands is a necessary part of building software, just as protecting against the threats they’re familiar with is a necessary part of ensuring their privacy. But that doesn’t make either sufficient. Software teams need to use their expert knowledge to offer users features that they demonstrably need, even if they don’t know to ask for them. Software that truly meets users’ privacy needs will protect them against the spectrum of threats they genuinely face, not just the ones they know to talk about.&lt;/p&gt;
&lt;h2&gt;Connect &amp; share your thoughts&lt;/h2&gt;
&lt;p&gt;Seeing this study interpreted by one software engineer has already taught us a lot. We now know that the way we’ve been presenting these findings has not gone far enough to contextualize how they should be interpreted. This is something we will work to improve.&lt;/p&gt;
&lt;p&gt;In the meantime, we are eager to get your thoughts and opinions on this work as well. Please take a look at a draft technical report describing it – available &lt;a href&#34;/resources/techreports/NYC15-MobMsg.pdf&#34;&gt;here&lt;/a&gt; and in our &lt;a href=&#34;https://github.com/simplysecure/resources/tree/master/Research/2015_NYC_Mobile_Messaging&#34;&gt;Github repo&lt;/a&gt; – and &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;let us know&lt;/a&gt; what you think.&lt;/p&gt;
&lt;p&gt;Finally, if you live in NYC and you’re interested in connecting with some great people doing outreach around security and cryptography, we encourage you to check out &lt;a href=&#34;https://twitter.com/cryptoharlem&#34;&gt;@cryptoharlem&lt;/a&gt;. It is one of many groups around the world working with their local communities to improve access to privacy-preserving tools. If you are part of such a group, we’d love to hear about your experiences, and talk about the possibility of working with you to amplify the needs of people in your community.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>How to Name Your App</title>
      <link>https://superbloom.design/learning/resources/how-to-name-your-app/</link>
      <pubDate>Fri, 20 May 2016 19:30:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/how-to-name-your-app/</guid>
      <description>&lt;p&gt;Naming software is hard because the name needs to convey a lot of meaning about what the program does to an unfamiliar audience, and do it all using only a word or short phrase. You want something memorable and easy to say – which becomes more complex when designing with a global audience in mind.&lt;/p&gt;
&lt;p&gt;Android&amp;rsquo;s recently-announced &lt;a href=&#34;https://www.android.com/versions/name-n/&#34;&gt;competition&lt;/a&gt; to name the latest operating system has been met with &lt;a href=&#34;https://news.fastcompany.com/what-could-possibly-go-wrong-with-googles-android-naming-contest-4007780&#34;&gt;skepticism&lt;/a&gt;. The accompanying &lt;a href=&#34;https://www.youtube.com/watch?v=v1IocBl_5UM&#34;&gt;parody video&lt;/a&gt; pokes fun at naming as an unskilled and silly exercise. The name for something like the latest version of an operating system doesn&amp;rsquo;t really matter from an end-user point of view. Only super-technical people will notice or care. Call it Nutella McNutella face, as Tech Crunch &lt;a href=&#34;http://techcrunch.com/2016/05/18/nutella-mcnutellaface/&#34;&gt;suggested&lt;/a&gt;, or version 9.9.4.1, and a general audience will be satisfied that it&amp;rsquo;s the latest choice.&lt;/p&gt;
&lt;h2 id=&#34;why-names-matter&#34;&gt;Why Names Matter&lt;/h2&gt;
&lt;p&gt;In contrast to an established operating system, an app&amp;rsquo;s name is an important way to differentiate what the program does and to encourage end-users to try it. Names are particularly important for internet-freedom projects where people may have limited bandwidth, be searching for information in a language they don&amp;rsquo;t speak well, or trying to make a quick choice between similarly-named apps in an app store. A strong name can help build trust and drive adoption among users who need the project most, and get more people communicating securely.&lt;/p&gt;
&lt;p&gt;Even open-source software developers need to consider their &amp;ldquo;brand&amp;rdquo; – that is, the way they express their project’s benefits and values. Coming up with a memorable, compelling, and differentiated name for an app is a skill practiced by &lt;em&gt;brand strategists&lt;/em&gt;. Most brand strategists work in the highly-commercial world of advertising – i.e., encouraging people to buy things. However, that same skill can help developers of all kinds reach a general audience and enable them to better protect their privacy. Here are a set of practices practices from commercial naming than can be adapted to an open-source context.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/mcdonalds_hu_59088a301c4fe543.jpg&#34; alt=&#34;Photo of a McDonald&amp;rsquo;s restaurant&#34; width=&#34;740&#34; height=&#34;336&#34;&gt;

&lt;br/&gt;&lt;em&gt;McDonald’s is one of the most-recognized name brands in the world. Imagine a world where privacy-preserving software names are as identifiable. &lt;a href=&#34;https://www.flickr.com/photos/jeepersmedia/14341391157/&#34;&gt;Image&lt;/a&gt; by Mike Mozart, &lt;a href=&#34;https://creativecommons.org/licenses/by/2.0&#34;&gt;CC-BY 2.0&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;clarify-your-purpose&#34;&gt;Clarify Your Purpose&lt;/h2&gt;
&lt;p&gt;A successful name conveys something about the app, either functional benefits or an attitude. Clarifying the values the app represents is an important first step. Naming conversations can be difficult because they can expose differences in opinion among contributors about the most important benefits of the app.&lt;/p&gt;
&lt;p&gt;To get everyone on the same page, try filling in the following sentence, leaving the name blank for now.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;For [type of user], [name] is a [frame of reference] that [key benefit] because [reasons to believe].&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;E.g., &amp;ldquo;For teenagers, Snapchat is a photo messaging app that hides messages from your parents because the interface is too confusing for adults.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Here are some thought-starter questions adapted from &lt;a href=&#34;http://www.brandingstrategyinsider.com/2012/12/the-trinity-of-brand-strategy.html&#34;&gt;Brand Strategy Insider&lt;/a&gt; to help you complete the above sentence.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Capabilities:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What does the app do?&lt;/li&gt;
&lt;li&gt;When the app does a better job than competitors, how is it different? (e.g. Faster? Cheaper? More fun? More reliable?)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Culture and Purpose:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What will the development team never compromise on?&lt;/li&gt;
&lt;li&gt;What are the team&amp;rsquo;s the core beliefs?&lt;/li&gt;
&lt;li&gt;What larger goal or cause does this app serve?&lt;/li&gt;
&lt;li&gt;What does this app want to change in people&amp;rsquo;s lives?&lt;/li&gt;
&lt;li&gt;What are the ideas that the customer and development team agree are important?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Personality:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Is the product serious or playful?&lt;/li&gt;
&lt;li&gt;If the app were a drink, what would it be? (E.g. home-brewed oolong tea versus a Starbuck&amp;rsquo;s mocha?)&lt;/li&gt;
&lt;li&gt;If this project were a person (or celebrity), who would it be?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Aspirational Self-Image:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What does using the app tell others about the customer?&lt;/li&gt;
&lt;li&gt;How do customers want to be seen?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;generating-ideas&#34;&gt;Generating Ideas&lt;/h2&gt;
&lt;p&gt;After you&amp;rsquo;ve answered the questions above, work with your team to identify a list of three to five adjectives that describe your app’s brand. It may take some time to get to agreement on the adjectives.&lt;/p&gt;
&lt;p&gt;Once you have the adjectives, brainstorm a list of at least 20 name options that reflect those adjectives. Let the list sit for a few days, then review your choices with fresh eyes. Select your top choices and move on to the exercises below in Choosing a Name.&lt;/p&gt;
&lt;p&gt;If you have time and can find willing participants, it&amp;rsquo;s a good idea to go through this brainstorming process again, starting over from your adjective list, and including different people. A second, independent round of brainstorming before moving on to choosing a final candidate is a good way to get comprehensive coverage.&lt;/p&gt;
&lt;p&gt;To help seed ideas for brainstorming, look at example naming resources, such as Wolf Olin&amp;rsquo;s &lt;a href=&#34;https://www.scribd.com/document/390837342/Naming-Handbook&#34;&gt;Naming Handbook&lt;/a&gt; for inspiration. Here are some categories of possible names, with U.S.-centric &lt;a href=&#34;http://www.slideshare.net/andrepo/brand-name-proposal&#34;&gt;examples&lt;/a&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Acronyms (UPS, IBM)&lt;/li&gt;
&lt;li&gt;Descriptive (Whole Foods, Airbus)&lt;/li&gt;
&lt;li&gt;Alliteration and Rhyme (Reese&amp;rsquo;s Pieces, Dunkin&amp;rsquo; Donuts)&lt;/li&gt;
&lt;li&gt;Evocative (Amazon, Crest)&lt;/li&gt;
&lt;li&gt;Neologisms (Wii, Kodak)&lt;/li&gt;
&lt;li&gt;Foreign words (Volvo, Samsung)&lt;/li&gt;
&lt;li&gt;Founders&amp;rsquo; names (Hewlett-Packard, Disney)&lt;/li&gt;
&lt;li&gt;Geography (Cisco, Fuji Film)&lt;/li&gt;
&lt;li&gt;Personification (Nike, other myths)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Take a critical look at the apps on your phone. What kind of names do they have?&lt;/p&gt;
&lt;p&gt;My home screen has&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Translations from analogue: 7 apps. (e.g. Clock, Notes)&lt;/li&gt;
&lt;li&gt;Descriptive: 3 apps. (e.g. Headspace, Lyft)&lt;/li&gt;
&lt;li&gt;Evocative:  3 apps. (e.g. Kindle, Signal)&lt;/li&gt;
&lt;li&gt;Neologisms: 6 apps. (e.g. Instagram, Trello)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;choosing-a-name&#34;&gt;Choosing a Name&lt;/h2&gt;
&lt;p&gt;Once you have a list of candidate names, start vetting them.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open the door and shout out the name.&lt;/strong&gt;
Saying the name out loud, such as &amp;ldquo;Hey, come look at this thing on XYZ&amp;rdquo; is a way to bring your project to life. If it&amp;rsquo;s hard to say or you feel embarrassed saying it, then it&amp;rsquo;s probably not the right name.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Try using the name in a sentence.&lt;/strong&gt;
Is it hard to spell or type? How does it fare with speakers of other languages?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What&amp;rsquo;s the verb that means to use the app?&lt;/strong&gt;
Right now in San Francisco, WhatsApp is starting to become a verb, but I hear &amp;ldquo;message me in WhatsApp&amp;rdquo; or &amp;ldquo;text me in WhatsApp&amp;rdquo; as well as &amp;ldquo;WhatsApp me.&amp;rdquo; Consider if you want your name to work as a verb. For example, Google Drive &lt;a href=&#34;http://www.gottabemobile.com/2014/05/05/confusing-google-drive-update-gets-even-more-confusing/&#34;&gt;confuses&lt;/a&gt; many people, in part because no one knows what verb to use. Even habitual users struggle to describe using it. &amp;ldquo;Link it to me on Google Drive?&amp;rdquo; or &amp;ldquo;Share it with me on Google Drive?&amp;rdquo; &amp;ldquo;Drive&amp;rdquo; works as an analogue for a disk drive, but the verb phrase probably isn&amp;rsquo;t &amp;ldquo;Drive it to me.&amp;rdquo; The poor name choice makes it difficult to talk about and form a mental model of how the sharing features of the program work.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Is the name already in use?&lt;/strong&gt;
Is the domain name available? What search results come up on websites and app stores? Are there legal conflicts? (A rigorous review may require the help of an attorney.)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Is it good enough?&lt;/strong&gt;
Keep in mind, naming is often anti-climatic. It&amp;rsquo;s fine to settle on an option that elicits a neutral reaction rather than love-at-first-site enthusiasm. The best names are often straight-forward or obvious. &amp;ldquo;Dropbox&amp;rdquo; is one example of an app with a clear, straightforward name.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Does it make sense to potential users?&lt;/strong&gt;
Get user feedback on your choices. This can be as simple as saying that you&amp;rsquo;re working on an app called X, and if someone asks you what it does, turn the question around and ask them what they would expect at app called X to do.  Making side-by-side comparisons of app store descriptions or websites introducing the app can help clarify how end-users perceive different names.&lt;/p&gt;
&lt;h2 id=&#34;whats-in-a-name&#34;&gt;What&amp;rsquo;s in a Name?&lt;/h2&gt;
&lt;p&gt;The name and the values your “brand” expresses are how people find your app in a sea of similar alternatives. It helps them distinguish between options that are trustworthy and those made with snake-oil. Sharing the name is how they encourage their friends to use it, too. If your goal is to get a privacy-preserving app into the hands of as many people as possible, having a strong, memorable, and evocative name is an essential step that your team must take.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Straight Talk: New Yorkers on Mobile Messaging and Implications for Privacy</title>
      <link>https://superbloom.design/learning/resources/straight-talk-new-yorkers-privacy/</link>
      <pubDate>Mon, 16 May 2016 00:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/straight-talk-new-yorkers-privacy/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Developers Are People, Too: Supporting Cryptographic Agility</title>
      <link>https://superbloom.design/learning/blog/developers-people-too/</link>
      <pubDate>Fri, 13 May 2016 19:50:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/developers-people-too/</guid>
      <description>&lt;p&gt;On Monday I had the pleasure of speaking at a &lt;a href=&#34;https://nap.nationalacademies.org/read/24636/chapter/2&#34;&gt;Workshop on Cryptographic Agility and Interoperability&lt;/a&gt; held at the &lt;a href=&#34;http://www.nationalacademies.org/&#34;&gt;National Academies&lt;/a&gt; by the &lt;a href=&#34;http://sites.nationalacademies.org/DEPS/CYBER/index.htm&#34;&gt;Forum on Cyber Resilience&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The assembled group of academics, policy-makers, and practitioners touched on a variety of problems around the practical application of cryptography in production software. The main focus was on the challenges and benefits associated with cryptosystems that can be updated or swapped out over time (and thus exhibit “agility”). The organizers asked us to consider questions such as the following.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Why is cryptographic agility useful and what are its potential risks and impacts?&lt;/li&gt;
&lt;li&gt;What approaches have been attempted for improving cryptographic agility, and how successful have they been?&lt;/li&gt;
&lt;li&gt;How might privacy and human rights be affected by cryptographic agility?&lt;/li&gt;
&lt;li&gt;What are the consequences of cryptographic agility for the interoperability and usability of communications systems?&lt;/li&gt;
&lt;li&gt;What are the key opportunities for standards bodies, governments, researchers, systems developers, and other stakeholders with regard to cryptographic agility?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The Forum will issue an official report of what was said in due time; for now, here are some of the thoughts I shared with the group.&lt;/p&gt;
&lt;h2 id=&#34;who-are-the-users&#34;&gt;Who are the users?&lt;/h2&gt;
&lt;p&gt;Whenever I encounter a group of security experts talking about designing user-facing systems, I like to remind them that their users are almost certainly less experienced with security than they themselves are. This doesn’t mean that their users are stupid or ill-informed, and nine times out of ten it doesn’t mean that the experts should go about trying to educate their users to achieve a shared worldview, either. But it does mean that the experts need to put effort into building empathy with their users, and into setting them up for success.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/developer-hands_hu_72c279f3eba87742.jpg&#34; alt=&#34;Photo of hands on a keyboard&#34; width=&#34;740&#34; height=&#34;495&#34;&gt;

&lt;em&gt;Developers are users, too – of APIs, standards, and libraries. Image &lt;a href=&#34;https://creativecommons.org/licenses/by/2.0/&#34;&gt;CC-BY 2.0&lt;/a&gt; &lt;a href=&#34;http://www.wocintechchat.com/&#34;&gt;WOCInTechChat&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In the case of cryptographic agility, “users” aren’t just the consumers buying and using mass-market software. They are also the software developers, architects, and decision-makers who are trying to decide whether and how to integrate cryptography into their systems. These developers are the ones who must benefit first from policies, standards, and practices if we are to use cryptographic agility to achieve resilience against software vulnerabilities.&lt;/p&gt;
&lt;h2 id=&#34;how-to-help-end-users&#34;&gt;How to help end users&lt;/h2&gt;
&lt;p&gt;Developers want to do the right thing for their users. Users want to do the right thing to protect their data, too, but are often even less experienced with security than developers. One big risk of cryptographically-agile systems is that developers force decisions onto users who are ill-equipped to make them. (“Hmm, we support three different encryption schemes because we’re agile. Which one should we use? Let’s ask the user!”) What can developers do to help users?&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Good defaults&lt;/strong&gt;: Developers should choose default settings for users that are secure, and that strike a balance with performance. This goes against a custom of security-expert culture: without knowing the user’s threat model, it may feel wiser to set no default and let the user choose. However, many users find such decisions daunting; asking users to choose among unfamiliar options can lead to them being frustrated and giving up on the program, or guessing at an answer. At the other extreme, some developers may be tempted to set the default to the most conservative, cryptographically-strong setting. This can be problematic in cases where there is a significant performance impact.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Choices come with recommendations&lt;/strong&gt;: In cases where the user must make a choice – or may be inclined to alter the default setting – the developer should offer guidance to help them. In some cases, this may involve simply stack-ranking the options (“Most secure” through “least secure”). In cases where there is not a clear ordering, another approach may be scenario-based menus that highlight the relative pros and cons of each option (“Strong data protection, with a 10% slowdown on uploads”).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Transparency&lt;/strong&gt;: Developers should provide a mechanism by which curious users can identify exactly which cryptographic library is being used in a program. This will help ease users’ minds when a vulnerability is discovered – ”Ah, this is running OpenSSL X.X, so I’m safe!” – and can help the community more easily hold developers accountable for updates. It can also be useful increasing the visibility of closed-source, country-mandated cryptographic suites, which many security experts worry may contain backdoors.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;developers-we-3-you&#34;&gt;Developers, we &amp;lt;3 you&lt;/h2&gt;
&lt;p&gt;There’s more that the security-expert community can do to help developers. Here are some broader-reaching ideas.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Algorithm guidance&lt;/strong&gt;: It’s not enough to simply say “these are the algorithms available”, or “these are the algorithms approved for use”. Authoritative entities – be they government agencies like &lt;a href=&#34;https://en.wikipedia.org/wiki/National_Institute_of_Standards_and_Technology&#34;&gt;NIST&lt;/a&gt;, standards bodies like &lt;a href=&#34;https://en.wikipedia.org/wiki/International_Organization_for_Standardization&#34;&gt;ISO&lt;/a&gt;, or educational materials like textbooks – should try whenever possible to offer unambiguous guidance as to the relative benefits and drawbacks of algorithms. There is broad consensus in the security community on which algorithms are reaching their end-of-life and which ones are still fresh, but average developers don’t have easy access to this information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Programming education&lt;/strong&gt;: It is a time-honored tradition for practitioners to complain that academic institutions aren’t preparing students well for “the real world”. There are many critical areas of programming practice that receive no attention in many undergraduate programs, such as writing automated tests for code. For what it’s worth, I would like to add the cryptography lifecycle to this list. In addition to offering guidance around the pros and cons of different algorithms, security courses should require students to spend time thinking about how a program’s architecture impacts its resilience in the face of cryptographic vulnerabilities over time. It’s not enough to design a system that uses a cryptographic library well; students must also learn to plan for a library’s obsolescence.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Study developers&lt;/strong&gt;: In the user-experience community, we understand that studying our users is an essential part of building systems that work for them. If we are to understand the current practice of cryptographic agility – what’s really working for developers, what challenges they face, and why they make the decisions they do – we can’t just convene experts to talk about the problem. We must use social-science qualitative-research methods to actually talk to developers in the context of their work, probe their practices, and uncover their lived experiences.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;bridging-the-people-tech-gap&#34;&gt;Bridging the people-tech gap&lt;/h2&gt;
&lt;p&gt;Simply Secure has multiple stakeholders, and in technical circles we often try to be the voice of the user when users aren’t in the room. We bring that same passion in advocating for the needs of cryptographers, software engineers, and fledging computer scientists. We work on tools for people who just want to communicate with their friends – who treat computers as black boxes – &lt;em&gt;and&lt;/em&gt; people who are passionate about writing good, secure, usable code. &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;Let us know&lt;/a&gt; how we can do more.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Chatbots, UX, and Privacy</title>
      <link>https://superbloom.design/learning/blog/chatbots-ux-privacy/</link>
      <pubDate>Fri, 06 May 2016 17:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/chatbots-ux-privacy/</guid>
      <description>&lt;p&gt;Chatbots, or conversational programs that simulate interactive human speech patterns, are a hot topic in UX right now. Microsoft CEO Satya Nadella recently claimed that “&lt;a href=&#34;http://www.wired.co.uk/news/archive/2016-03-31/microsoft-build-bots-ai-cortana-keynote-conference&#34;&gt;bots are the new apps&lt;/a&gt;”, and that they are the interface of the future for tasks like ordering food and booking transportation. In San Francisco, tech elites use a multitude of oft-parodied services like Wag to find dog walkers and Rinse to have their laundry done. However, the appeal of a single integrated interface to multiple apps is obvious from a UX point of view, even as the social implications of so much “efficiency” are still being debated.&lt;/p&gt;
&lt;h2 id=&#34;back-to-the-command-line&#34;&gt;Back to the Command Line&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;http://www.promptapp.io/&#34;&gt;Prompt&lt;/a&gt; bills itself as the “command line for the real world”. It uses text to integrate with over 1,000 services – including commerce (e.g. Domino’s Pizza), productivity (e.g. Evernote), and home automation (e.g. Nest). With Prompt, it’s possible to get directions from Google Maps or order an Uber to drive you there simply by sending text commands.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/Prompt-small_hu_f9a8facf82ef4810.jpg&#34; alt=&#34;Screenshot of a conversational UI.&#34; width=&#34;740&#34; height=&#34;601&#34;&gt;

&lt;br/&gt;&lt;em&gt;Screenshot from &lt;a href=&#34;https://www.promptapp.io/&#34;&gt;Prompt.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Driving everyone from the interactive world of apps to the visually impoverished world of the command line feels like a step backward to many designers, including me. But we can interpret this shift as a response to the usability challenges of working across multiple apps on a mobile OS.&lt;/p&gt;
&lt;h2 id=&#34;chatbots-versus-better-apps&#34;&gt;Chatbots versus Better Apps&lt;/h2&gt;
&lt;p&gt;Dan Grover’s excellent post &lt;a href=&#34;http://dangrover.com/blog/2016/04/20/bots-wont-replace-apps.html&#34;&gt;Bots Won’t Replace Apps, Better Apps Will Replace Apps&lt;/a&gt; clearly illustrates the UX implications of what he describes as “Silicon Valley phone OS makers’ growing failure to fully serve users’ needs, particularly in other parts of the world.” I recommend reading the whole article, but the screenshots alone tell a compelling story.&lt;/p&gt;
&lt;p&gt;Dan is a product manager at Chinese mobile messaging platform WeChat, which works to embed services in its core interface graphically rather than textually. His examples offer a view into the world of the Chinese-language mobile experience and serve as a counterpoint to the hype around chatbot interfaces. For example, he contrasts a pizza ordered via 73 keystroke taps in a conversational UI with 16 taps in the graphical WeChat equivalent. Even though click/tap counts are an imperfect way to evaluate usability, they are one illustration that advocates of the so-called efficiency of chatbots might not have the whole story. Textual interfaces work well for some users in some contexts (system administrators and programmers have embraced them for decades!), but that doesn’t mean that they will work everywhere for everything.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/MSPizzaBot_hu_cb4cc187ff87bb02.png&#34; alt=&#34;Screenshot of a conversational UI with a corresponding column of tap counts on the right.&#34; width=&#34;740&#34; height=&#34;399&#34;&gt;

&lt;br/&gt;&lt;em&gt;Example transaction from Microsoft Bot Framework showing 73 taps to order pizza. &lt;a href=&#34;https://dev.botframework.com/&#34;&gt;Image&lt;/a&gt; from Microsoft.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/pizza-hut-ordering_hu_4df221d0a495a003.png&#34; alt=&#34;Screenshot of a GUI interface with tap counts indicated.&#34; width=&#34;740&#34; height=&#34;522&#34;&gt;

&lt;br/&gt;&lt;em&gt;WeChat interface for in-app ordering Pizza Hut, showing 16 taps needed to complete the transaction. &lt;a href=&#34;http://dangrover.com/blog/2016/04/20/bots-wont-replace-apps.html&#34;&gt;Image&lt;/a&gt; from Dan Grover.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;These chatbot-versus-graphical interactions show different relationships between messaging apps and other special-purpose apps. For example, ride-sharing service Lyft uses the phone’s native text-messaging app to notify passengers that their ride has arrived, but passengers can’t order a ride from within the native messaging app. WeChat started as a messaging app and has expanded to take on activities done by special-purpose apps in other contexts.&lt;/p&gt;
&lt;h2 id=&#34;security-implications-of-chatbots&#34;&gt;Security Implications of Chatbots&lt;/h2&gt;
&lt;p&gt;Telegram, which tries to position itself as a platform that keeps users’ data secure in a credible way (despite significant challenges on that front), gives developers &lt;a href=&#34;https://telegram.org/blog/bots-2-0&#34;&gt;tools for building bots&lt;/a&gt;. It even offers &lt;a href=&#34;https://telegram.org/blog/botprize&#34;&gt;prize money&lt;/a&gt; to developers using the Telegram Bot API. But how do privacy and security fit into this landscape? Should we be advocating for the equivalent of end-to-end encryption in this kind of chatbot universe?&lt;/p&gt;
&lt;p&gt;From a human-centered point of view, we can expect that communicating with a bot sets end-user expectations that their messages are being read by machines. It’s an easy inference that their messages are saved and archived by the bot owner and used as training material to improve the program over time. Just as people who call a customer hotline are informed that “This call may be monitored or recorded for training purposes,” people have an expectation that some unseen entity is eventually reading the message. Otherwise, how would they know what kind of pizza to send to which house?&lt;/p&gt;
&lt;p&gt;The expectation that “secure” chats are read by unknown parties has the potential to change users’ mental models of privacy and confuse their understanding of what “secure messaging” means in other contexts. Further research is needed to understand the implications and how to communicate security properties of different platforms.&lt;/p&gt;
&lt;h2 id=&#34;chatbots-as-security-coaches&#34;&gt;Chatbots as Security Coaches?&lt;/h2&gt;
&lt;p&gt;Chatbots are an intriguing output format for explaining security concepts. In this example from Slack, a bot messages me to let me know that a file’s actual sharing permissions have changed.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/Slackbot-Shared_hu_d2ee75f4f1299fb2.jpg&#34; alt=&#34;Screenshot from a Slack’s conversational interface indicating that a private file was shared in a particular channel by a particular user.&#34; width=&#34;740&#34; height=&#34;154&#34;&gt;

&lt;br/&gt;&lt;em&gt;Screenshot from Slack.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This is an effective message because it’s actionable. The proactive information (which appeared to me in a private channel, with accompanying notification) gives a sense of immediacy. I know who shared what file with whom, and it’s easy to check the contents of the file. I am one click away from being able to ask Scout about the action she has just taken.&lt;/p&gt;
&lt;p&gt;This approach could be adapted to a number of contexts. Many large service providers send notifications by email when a user’s password has been modified or other important account details have changed. A conversational UI could not only be a prompt and friendly way to share this information with users but could offer users an opportunity to take immediate action if the change was unwanted. Thinking more aspirationally to connected homes, smart cities, and IoT applications, chatbots could help people understand the chain of custody of their data. For example, they could notify people that their image has been captured on video and shared with a third party – or offer them an opportunity to opt out of such a recording. The details of such systems would be complex, but new interfaces could help make the exchange of complicated information more easy and accessible.&lt;/p&gt;
&lt;p&gt;I’m optimistic that chatbots can help people understand how their data is being used. I’m especially excited by the potential to use chatbots not just to control commerce but to empower us to manage our personal data. Privacy-minded people should look for opportunities to make chatbots more than just glorified mechanisms of corporate surveillance. We should strive to instead create tools that will help people understand their data and their capacity to control it in an actionable, friendly way.&lt;/p&gt;
&lt;h2 id=&#34;further-reading-on-chatbots--ux&#34;&gt;Further Reading on Chatbots + UX&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Connie Chan, &lt;a href=&#34;https://twitter.com/conniechan/status/715773848147374080&#34;&gt;Tweetstorm on WeChat Mobile Commerce&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Alistair Croll, &lt;a href=&#34;#&#34;&gt;What Is A Bot OS?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Benedict Evans, &lt;a href=&#34;#&#34;&gt;Messaging and Mobile Platforms&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Design Matters: 2016 Design in Tech Report</title>
      <link>https://superbloom.design/learning/blog/maeda-report/</link>
      <pubDate>Fri, 29 Apr 2016 17:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/maeda-report/</guid>
      <description>&lt;p&gt;For the past two years &lt;a href=&#34;http://www.maedastudio.com/index.php&#34;&gt;John Maeda&lt;/a&gt; (whose previous roles include Professor at the MIT Media Lab and President of the Rhode Island School of Design) has issued a &lt;a href=&#34;https://www.kleinerperkins.com/perspectives/design-in-tech-report-2016/&#34;&gt;Design In Tech Report&lt;/a&gt;. This influential analysis, which Maeda presents at &lt;a href=&#34;https://www.youtube.com/watch?v=5k2FHLPyfUc&#34;&gt;SXSW&lt;/a&gt; and has also been picked up by outlets like &lt;a href=&#34;http://www.wired.com/2016/03/john-maeda-really-matters-world-design/&#34;&gt;Wired&lt;/a&gt;, has helped Silicon Valley understand how design is valuable to companies and their customers. It is situated in the context of venture capital, as Maeda is currently Design Partner at VC firm Kleiner Perkins Caufield and Byers. However, his attention to industry trends backed with carefully-reported figures has implications for the broader world of tech – including nonprofit and open-source efforts.&lt;/p&gt;
&lt;h2 id=&#34;design-as-a-force-for-good&#34;&gt;Design as a Force for Good&lt;/h2&gt;
&lt;p&gt;My three biggest take-aways from the 2016 Design in Tech Report are that market trends of the past year prove that design:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;is about more than beauty,&lt;/li&gt;
&lt;li&gt;has deep ethical implications, and&lt;/li&gt;
&lt;li&gt;can be a force for economic inclusion.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;more-than-beauty&#34;&gt;More than beauty&lt;/h3&gt;
&lt;p&gt;As a trained designer, I have to grit my teeth to report that &amp;ldquo;design is more than beauty&amp;rdquo;. The heart of my practice is not visual design but user experience flows, so this take-away seems painfully obvious. Design is about making things that work well for real people. However, it&amp;rsquo;s helpful for me to remember just how much patient explanation can be necessary to communicate the broad range of activities encompassed by design to people who aren&amp;rsquo;t familiar with it – from research, to information architecture, to organizational design and beyond. In that sense, it&amp;rsquo;s gratifying that market trends are bearing out the value of design beyond the simple creation of pretty pictures. How do we spread this understanding further?&lt;/p&gt;
&lt;h3 id=&#34;ethical-implications&#34;&gt;Ethical implications&lt;/h3&gt;
&lt;p&gt;The ethical implications of design are particularly important to consider in the context of the current technology industry, which is heavy on VC-fueled startups. That community is interested in design because design shapes behavior, and is effective at driving &amp;ldquo;conversions&amp;rdquo;, or sales. From creating addicting products that encourage spending, such as &lt;a href=&#34;http://press.princeton.edu/titles/9156.html&#34;&gt;Addiction by Design: Machine Gambling in Las Vegas&lt;/a&gt;, to &lt;a href=&#34;http://darkpatterns.org/&#34;&gt;Dark Patterns&lt;/a&gt; that trick users out of unsubscribing from services, irresponsible design harms people. How do we harness this deep understanding of user motivation and behavior for good rather than just for profit?&lt;/p&gt;
&lt;h3 id=&#34;economic-inclusion&#34;&gt;Economic inclusion&lt;/h3&gt;
&lt;p&gt;Happily, the report also highlights instances of design being used in ways that benefit society. For example, the UK Government&amp;rsquo;s Digital Service Agency saved &lt;a href=&#34;https://gds.blog.gov.uk/2015/10/23/how-digital-and-technology-transformation-saved-1-7bn-last-year/&#34;&gt;£1.7 billion&lt;/a&gt; ($2.5 trillion) by re-designing digital services and making them more accessible to all people. Design is an amplifier of values, and can build systems that are more equal or more unequal. The report showcases examples of market success that design for diverse audiences, such as gay social networks and gender-neutral children&amp;rsquo;s toys. How can we help the security and privacy communities meet the needs of a broader group of people?&lt;/p&gt;
&lt;h2 id=&#34;from-design-for-trust-to-design-for-privacy&#34;&gt;From Design for Trust to Design for Privacy&lt;/h2&gt;
&lt;p&gt;The 2016 Design in Tech Report touches on cybersecurity startups delivering network monitoring solutions, but the more encouraging point is that it positions them within a bigger framework of designing for trust. Considering everything from AI interfaces to startups in the so-called sharing economy, the 2016 report states that &amp;ldquo;design&amp;rsquo;s fundamental impact rests in the ability to engender trust&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;I am optimistic that the 2017 Design in Tech Report will address privacy in a more explicit way. The Apple vs FBI case is a turning point for how companies handle customers&amp;rsquo; data, and with Apple&amp;rsquo;s strong heritage as a design-driven company, other design companies are taking note. I hope that this time next year we will be examining how design leaders within Silicon Valley&amp;rsquo;s VC-culture are shifting their focus away from customer data as a commodity and toward user privacy as a core value proposition.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>When User News Is Bad News: Tactical Advice On User Feedback</title>
      <link>https://superbloom.design/learning/blog/when-user-news-bad/</link>
      <pubDate>Fri, 22 Apr 2016 15:30:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/when-user-news-bad/</guid>
      <description>&lt;p&gt;When you&amp;rsquo;re putting your heart and soul into designing, building, or improving a piece of software, tuning in to feedback from users can sometimes get you down.&lt;/p&gt;
&lt;p&gt;Imagine waking up one morning and finding your project is being mentioned on Twitter in a slew of messages like these:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Thanks Snapchat. Your app officially sucks.
— Michael (@michaellorelei) &lt;a href=&#34;https://twitter.com/michaellorelei/status/723170934442459137&#34;&gt;April 21, 2016&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;The Facebook app sucks
— em (@emma0wczarzak) &lt;a href=&#34;https://twitter.com/emma0wczarzak/status/722461510195290114&#34;&gt;April 19, 2016&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;You know, the YouTube app really kind of sucks.
— Samuel Ford (@samuelwford) &lt;a href=&#34;https://twitter.com/samuelwford/status/710110100430655488&#34;&gt;March 16, 2016&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;netflix&amp;rsquo;s windows app sucks
— Nico (@nico_satria18) &lt;a href=&#34;https://twitter.com/nico_satria18/status/708907048939851776&#34;&gt;March 13, 2016&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;The weather channel&amp;rsquo;s app sucks. It clearly says it&amp;rsquo;s clear in &lt;a href=&#34;https://twitter.com/hashtag/ATX?src=hash&#34;&gt;#ATX&lt;/a&gt;. Nah.
— jhem (@jhem_unfiltrd) &lt;a href=&#34;https://twitter.com/jhem_unfiltrd/status/707595481673703424&#34;&gt;March 9, 2016&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;New &lt;a href=&#34;https://twitter.com/hashtag/uber?src=hash&#34;&gt;#uber&lt;/a&gt; app update sucks. Horrible usability.
— Kyle (@DerWetterWunder) &lt;a href=&#34;https://twitter.com/DerWetterWunder/status/675761725677764610&#34;&gt;December 12, 2015&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;Dear &lt;a href=&#34;https://twitter.com/Nike&#34;&gt;@Nike&lt;/a&gt;,
The snkrs app sucks. Please do something about that
— Chip Zoller (@CocainaKeem) &lt;a href=&#34;https://twitter.com/CocainaKeem/status/717100438265442304&#34;&gt;April 4, 2016&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://twitter.com/McDonalds&#34;&gt;@McDonalds&lt;/a&gt; your app totally sucks! Never works! &lt;a href=&#34;https://twitter.com/hashtag/TechFail?src=hash&#34;&gt;#TechFail&lt;/a&gt; &lt;a href=&#34;https://twitter.com/hashtag/McFailure?src=hash&#34;&gt;#McFailure&lt;/a&gt;
— Dawn Duncan (@Duncan03Dawn) &lt;a href=&#34;https://twitter.com/Duncan03Dawn/status/687623070702563328&#34;&gt;January 14, 2016&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Whether they&amp;rsquo;re saying it &amp;ldquo;kinda sucks&amp;rdquo;, &amp;ldquo;officially sucks&amp;rdquo;, or that it is a full-on #McFailure, it&amp;rsquo;s easy to find tweets like this for just about any app. With few details and lots of negative attitude, this sort of message is always discouraging to the team working on the app in question.&lt;/p&gt;
&lt;p&gt;That doesn&amp;rsquo;t mean it&amp;rsquo;s reasonable to just ignore negative feedback, however. Unless you know why the user is frustrated and a fix to their problem is just waiting to be pushed in the next release, all user feedback is always an opportunity to learn something.&lt;/p&gt;
&lt;h2 id=&#34;a-positive-spin&#34;&gt;A positive spin&lt;/h2&gt;
&lt;p&gt;First, it&amp;rsquo;s important to have the right mindset when approaching negative user feedback. No matter how strongly you identify with the software project in question, the comments aren&amp;rsquo;t about you as a person, so be mindful of your emotional reaction when you&amp;rsquo;re reading it. It&amp;rsquo;s very common to feel angry, frustrated, and even hurt. Try to find a balance between taking the feedback so seriously that it upsets you, and discounting it to the point that you lose motivation to understand what&amp;rsquo;s going on.&lt;/p&gt;
&lt;p&gt;If your project is new or under-resourced (as many so many often are), remember that these kinds of messages are a sign that people care about what you&amp;rsquo;re doing. They are trying to use your software. It excites them enough that they&amp;rsquo;re even trying to tell you when it disappoints them. They may not have the vocabulary, time, design understanding, or technical acumen to explain what they dislike, but they want you to hear them so you have a chance to make things better.&lt;/p&gt;
&lt;h2 id=&#34;tactical-advice&#34;&gt;Tactical advice&lt;/h2&gt;
&lt;p&gt;So, how do you actually go about turning negative feedback into useful insight? Here&amp;rsquo;s a set of questions and ideas to get you started.&lt;/p&gt;
&lt;h3 id=&#34;provide-a-forum&#34;&gt;Provide a forum&lt;/h3&gt;
&lt;p&gt;Do users have a place to go when they want to &lt;a href=&#34;https://en.wiktionary.org/wiki/kvetch&#34;&gt;kvetch&lt;/a&gt; or &lt;a href=&#34;https://en.wiktionary.org/wiki/kvell&#34;&gt;kvell&lt;/a&gt; in the first place? Feedback channels don&amp;rsquo;t have to be elaborate or high-maintenance; while it&amp;rsquo;s great if your team can support online user forums localized in 23 languages, a simple email address that is prominently advertised on your website is an effective place to start.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pro tip:&lt;/strong&gt; don&amp;rsquo;t just tell users to file a bug on GitHub. That&amp;rsquo;s a great way to get highly-technical users to submit feedback, but a lousy way to get insights from just about anyone else. Social-media sites like Twitter and Facebook can be an effective way to connect with users, although it&amp;rsquo;s important to try and help users understand the risks that such platforms pose. (For example, it&amp;rsquo;s a bad idea to post publicly on Twitter about using VPN software from a country where such programs are prohibited.)&lt;/p&gt;
&lt;h3 id=&#34;muster-the-troops&#34;&gt;Muster the troops&lt;/h3&gt;
&lt;p&gt;Making sense of user feedback is critically important to software projects, because your users&amp;rsquo; opinions will ultimately determine the success of your software. (If they don&amp;rsquo;t like it, eventually they&amp;rsquo;ll find a better alternative; if they do like it, they&amp;rsquo;ll tell their friends and your userbase will grow.) Monitoring and analyzing user feedback is therefore worth investing non-trivial amounts of time and energy.&lt;/p&gt;
&lt;p&gt;Do you have one or more team members who are responsible for this work? Do those people actually have time to engage with the data that is coming in? Do they have time during team meetings to share their findings? Does the team use this information to help it prioritize near- and long-term work?&lt;/p&gt;
&lt;h3 id=&#34;gather-a-baseline&#34;&gt;Gather a baseline&lt;/h3&gt;
&lt;p&gt;If you have a software project that people outside the team are using, it&amp;rsquo;s past time to start gathering data on what those users are saying about it. Even if your userbase is small and the feedback is mostly positive, an accurate picture today will provide the basis for future evaluation.&lt;/p&gt;
&lt;p&gt;What are the top known issues? Are you trying to keep track of individual pieces of feedback, or have you leveled up to clustering pieces into related groups? Are there clusters of complaints that can&amp;rsquo;t be explained by any known bug? How many users are providing feedback: do you think it&amp;rsquo;s ten different people saying similar things, or one person trying to reach out ten different times with the same issue?&lt;/p&gt;
&lt;p&gt;In addition to your official feedback channel, don&amp;rsquo;t forget to monitor your project&amp;rsquo;s social-media accounts on a regular basis. Even if you don&amp;rsquo;t think of it as a way for users to send feedback, they almost certainly do. And there&amp;rsquo;s nothing more demoralizing to a user than landing on a Facebook page and finding that there are complaints that have been ignored for months (or years!) on end.&lt;/p&gt;
&lt;h3 id=&#34;track-comments-over-time&#34;&gt;Track comments over time&lt;/h3&gt;
&lt;p&gt;You don&amp;rsquo;t have to instrument your app or gather analytics to get longitudinal data. Checking in on your feedback channels on a regular basis (daily, weekly, or monthly, depending on the size of your userbase and the volume of feedback) will help you build a picture of how you&amp;rsquo;re doing, and provide a &amp;ldquo;user heartbeat&amp;rdquo; to help motivate and direct the team&amp;rsquo;s efforts.&lt;/p&gt;
&lt;p&gt;Are you monitoring how many new complaints you get in each thematic cluster per month? Did your latest update cause complaints to go down, or have they remained constant? Are your development priorities successfully addressing top complaints over time?&lt;/p&gt;
&lt;h3 id=&#34;engage-for-information--community&#34;&gt;Engage for information &amp;amp; community&lt;/h3&gt;
&lt;p&gt;The tweets quoted above are an extreme example, but many users provide feedback that isn&amp;rsquo;t exactly useful. After all, how can you debug a problem if you don&amp;rsquo;t even know what version of the software the user is running? Depending on the feedback channel through which the user connected, you may be able to reach out and ask for more information.&lt;/p&gt;
&lt;p&gt;When a user submits feedback (even the inactionable kind), do they get a response thanking them for taking the time to share their thoughts? Does your project website have a page describing what information makes a good bug report?&lt;/p&gt;
&lt;p&gt;Just a brief automated reply can make your users feel like you care about them, even if you don&amp;rsquo;t have the time to write them personally. &amp;ldquo;Thank you so much for your feedback, it means a lot to us. We will do our best to read it soon. We are busy trying to ship the next version of the software, so probably can&amp;rsquo;t reply in detail. But if you&amp;rsquo;re willing to go the extra mile for us, would you consider sharing more detailed feedback using these instructions?&amp;rdquo;&lt;/p&gt;
&lt;h3 id=&#34;invite-critics-to-a-beta-testing-group&#34;&gt;Invite critics to a beta-testing group&lt;/h3&gt;
&lt;p&gt;This may be beyond the organizational means of many small projects, but: have you considered starting a beta-testing group? Some distribution platforms like Google Play have features to make this easier. Beta-testing can help you prevent huge waves of negative feedback by providing more eyes on software updates, and can serve as a great way to channel the enthusiasm of some of your biggest user critics. We work with a number of organizations that connect with users interested in privacy-preserving software, so let us know if you need help connecting with more potential users.&lt;/p&gt;
&lt;h2 id=&#34;its-all-about-the-empathy&#34;&gt;It&amp;rsquo;s all about the empathy&lt;/h2&gt;
&lt;p&gt;At the end of the day, we all care about how our users feel. We may get frustrated when they chew us out for honest mistakes, or berate us for problems that are ultimately out of our control. But these moments are always an opportunity to put ourselves in their shoes, try to see our project through their eyes, and learn our craft anew.&lt;/p&gt;
&lt;p&gt;Do you do a great job channeling your users&amp;rsquo; feedback into amazing software improvements? Are you struggling and looking for more help than the above ideas provide? Please &lt;a href=&#34;https://superbloom.design/contact&#34;&gt;get in touch&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Comfortable UX, Not Just Open APIs</title>
      <link>https://superbloom.design/learning/blog/comfortable-ux-open-apis/</link>
      <pubDate>Fri, 15 Apr 2016 19:30:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/comfortable-ux-open-apis/</guid>
      <description>&lt;p&gt;Simply Secure focuses its collaborative efforts on open-source, privacy-preserving software projects. In my conversations with designers, developers, and end users, I&amp;rsquo;m often struck by a divergence in their understanding of what &amp;ldquo;openness&amp;rdquo; means in software. For example, last December during a &lt;a href=&#34;https://superbloom.design/learning/blog/straight-talk&#34;&gt;user study&lt;/a&gt;, participants reading app store descriptions of secure messaging apps consistently thought that &amp;ldquo;open source&amp;rdquo; meant that their messages were public.&lt;/p&gt;
&lt;p&gt;The distinction between &amp;ldquo;source code&amp;rdquo; and &amp;ldquo;content generated in apps&amp;rdquo; isn&amp;rsquo;t always clear to a mass audience, and this confusion has implications for privacy preservation. Many people know that their Facebook login credentials give them access to other services and apps, as &amp;ldquo;Login With Facebook&amp;rdquo; is common on everything from babysitter finder Urban Sitter to dating app Tinder. However, most people don&amp;rsquo;t understand connecting Facebook functionality to other apps often allows their personal data to flow between services as well.&lt;/p&gt;
&lt;p&gt;Provocative services like &lt;a href=&#34;https://www.cheaterbuster.net/&#34;&gt;Swipebuster&lt;/a&gt;, whose creator says they intended to build awareness about privacy issues, illustrate the confusion many people experience about what &amp;ldquo;open&amp;rdquo; and &amp;ldquo;public&amp;rdquo; mean in the context of the apps they use.&lt;/p&gt;
&lt;h2 id=&#34;is-tinder-data-public&#34;&gt;Is Tinder data public?&lt;/h2&gt;
&lt;p&gt;Swipebuster allows you to search for Tinder profiles based on certain criteria. Armed only with a first name, age, approximate location, and $5, you can get a list of matching Tinder users, complete with their photos, last logins, and whether they&amp;rsquo;re looking for men or women.&lt;/p&gt;
&lt;p&gt;The anonymous creator explains, &amp;ldquo;There is too much data about people that people themselves don&amp;rsquo;t know is available,&amp;rdquo; Vanity Fair &lt;a href=&#34;http://www.vanityfair.com/news/2016/04/check-tinder-cheater-swipe-buster&#34;&gt;reports&lt;/a&gt;. &amp;ldquo;Not only are people oversharing and putting out a lot of information about themselves, but companies are also not doing enough to let people know they&amp;rsquo;re doing it.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;According to Vanity Fair, Tinder responded that &amp;ldquo;searchable information on the Web site is public information that Tinder users have on their profiles. If you want to see who&amp;rsquo;s on Tinder we recommend saving your money and downloading the app for free.&amp;rdquo;&lt;/p&gt;
&lt;h2 id=&#34;paying-money-to-not-deal-with-tinder&#34;&gt;Paying money to not deal with Tinder&lt;/h2&gt;
&lt;p&gt;Let&amp;rsquo;s put aside for a moment the potential moral or social implications of trying to access Tinder data for purposes other than finding a date, and explore why Swipebuster is so disturbing. I believe that it resonates as an example of the cultural divergence around openness because it occupies a middle ground between two undesirable options. Engaging with Tinder directly as a user – installing the app to see if someone else is using it – can be undesirable if you don&amp;rsquo;t want others to know you&amp;rsquo;re browsing Tinder data (e.g., because you&amp;rsquo;re already in a romantic relationship). The apparent openness of the Tinder APIs presents a nice alternative if you can write code to query them, but this path requires a level of technical knowledge that makes it all but impossible for most people. $5 seems like a bargain when compared to learning Python from scratch or making your neighbors think you&amp;rsquo;re cheating on your spouse.&lt;/p&gt;
&lt;p&gt;Swipebuster is what I would call a &lt;em&gt;comfortable user&lt;/em&gt; experience. A comfortable UX opens the possibility of accessing data to a broad spectrum of users. An open API may make the underlying app possible, but data alone isn&amp;rsquo;t enough for users to engage. In the case of Swipebuster, filling out a form with a credit card is an easy, routine experience for someone trying to get information. A $5 price adds another barrier, but it is a familiar interaction.&lt;/p&gt;
&lt;p&gt;This ease contrasts with Tinder users&amp;rsquo; perceptions. Many consider the data they share with the dating service to be confidential on some level. The existence of Swipebuster makes many Tinder users feel shocked and vulnerable.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/Swipebuster_hu_65b658ab858a67a5.png&#34; alt=&#34;Form from Swipebuster.com.&#34; width=&#34;740&#34; height=&#34;727&#34;&gt;

&lt;em&gt;Form from Swipebuster.com.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;As The Guardian&amp;rsquo;s &lt;a href=&#34;https://www.theguardian.com/technology/2016/apr/05/tinder-swipebuster-spy-on-users-privacy-dating-app&#34;&gt;Alex Hearn&lt;/a&gt; writes,&amp;ldquo;Even if it might seem obvious that Tinder, a site which works by showing name, gender, age and location to strangers, doesn&amp;rsquo;t consider that information secret, it&amp;rsquo;s a very different matter to be confronted with a searchable database of that information. Your home is not secret, for example – people see you come and go all the time – but that doesn&amp;rsquo;t mean posting your address online is advisable.&amp;rdquo;&lt;/p&gt;
&lt;h2 id=&#34;what-happens-in-vegas-does-not-stay-in-vegas&#34;&gt;What happens in Vegas does not stay in Vegas&lt;/h2&gt;
&lt;p&gt;The Las Vegas tourist bureau has lured visitors with the promise that &amp;ldquo;what happens in Vegas stays in Vegas,&amp;rdquo; encouraging people to engage in behavior they wouldn&amp;rsquo;t want to be associated with in other contexts. By extension, people may believe that what happens in an app like Tinder stays in that app. It may be more realistic to assume is that everything that happens in an app is ultimately accessible on the open web.&lt;/p&gt;
&lt;p&gt;Along with confusing permissions, badly-communicated or poorly-designed API integration can be another vector of privacy risk. &lt;a href=&#34;http://www.vice.com/read/you-can-pay-5-to-find-out-if-your-significant-other-is-secretly-using-tinder-vgtrn&#34;&gt;Vice&lt;/a&gt; (and Tinder itself, as quoted above) describe Tinder&amp;rsquo;s web-based API as &amp;ldquo;open, or &amp;ldquo;public&amp;rdquo;, but when examined more closely, it appears that it is actually what software developers call &amp;ldquo;undocumented&amp;rdquo; or &amp;ldquo;private&amp;rdquo;. This means that Tinder developers probably neither intended the API to be used by third parties nor made particular efforts to prevent such use; Swipebuster is the result of what many would call &amp;ldquo;reverse engineering&amp;rdquo;. Part of the shock with Swipebuster is because it shows that security through obscurity isn&amp;rsquo;t working. Whatever social contract of mutual accountability might work when a Tinder user encounters someone they know in the app, or when an app&amp;rsquo;s interface limits access to the data contained within, doesn&amp;rsquo;t hold when it&amp;rsquo;s easy to pay for information from a database.&lt;/p&gt;
&lt;h2 id=&#34;building-more-comfortable-experiences&#34;&gt;Building more comfortable experiences&lt;/h2&gt;
&lt;p&gt;At Simply Secure, we want better privacy-preserving tools that empower people to protect their data. Although Swipebuster may occupy shaky moral ground, it demonstrates that a good UX will always enable more people to access data than an open API (even in cases where the API is more elegant). Programmatic interfaces aren&amp;rsquo;t enough; to get people truly engaged, we need initiatives that work to open not only data but also make truly comfortable experiences for non-expert users as well.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Tradeoffs In Seamlessness: The WhatsApp Update</title>
      <link>https://superbloom.design/learning/blog/whatsapp-update/</link>
      <pubDate>Fri, 08 Apr 2016 20:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/whatsapp-update/</guid>
      <description>&lt;p&gt;I was originally planning on continuing today the series I &lt;a href=&#34;https://superbloom.design/learning/blog/facebook-p1&#34;&gt;started&lt;/a&gt; last month, but it&amp;rsquo;s hard to pass up the opportunity to talk about Tuesday&amp;rsquo;s exciting &lt;a href=&#34;https://blog.whatsapp.com/10000618/end-to-end-encryption&#34;&gt;WhatsApp’s  update&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The new version of the messaging service&amp;rsquo;s apps now offers users a glimpse into a feature that has been quietly rolling out for months: end-to-end-encryption. A number of other groups have written about the update&amp;rsquo;s technical strengths and weaknesses – c.f. &lt;a href=&#34;https://www.eff.org/deeplinks/2016/04/whatsapp-rolls-out-end-end-encryption-its-1bn-users&#34;&gt;the EFF&lt;/a&gt; and &lt;a href=&#34;https://threatpost.com/whatsapp-encryption-a-good-start-but-far-from-a-security-cure-all/117230/&#34;&gt;ThreatPost&lt;/a&gt;, and WhatsApp&amp;rsquo;s &lt;a href=&#34;https://www.whatsapp.com/security/WhatsApp-Security-Whitepaper.pdf&#34;&gt;own whitepaper&lt;/a&gt; – but I&amp;rsquo;d like to spend a moment on the updated user experience, and lessons that UX designers and developers can take from the decisions WhatsApp has made.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Users don&amp;rsquo;t have to take any action at all – it just works!&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&#34;always-on-for-everyone&#34;&gt;Always on for everyone&lt;/h2&gt;
&lt;p&gt;As long as both you and your messaging partner are running recent versions of the program, WhatsApp&amp;rsquo;s end-to-end-encryption is on by default, with no apparent way for the user to turn it off. This means that people don&amp;rsquo;t have to fuss with generating or exchanging cryptographic keys; it happens silently in the background. In fact, users don&amp;rsquo;t have to take any action at all – it just works!&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://twitter.com/FredericJacobs/status/717382059589836800&#34; alt=&#34;Update your WhatsApp.&#34;&gt;

&lt;em&gt;Fredric Jacobs shares the error message he saw when his messaging partner was running an old version of the software (left) and the menu option to turn on notifications around encryption (right).&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;an-exercise-in-tradeoffs&#34;&gt;An exercise in tradeoffs&lt;/h2&gt;
&lt;p&gt;Of course, this seamlessness doesn&amp;rsquo;t come for free. Security enthusiasts are quick to point out limitations of this approach – in particular, that an application without mandatory &lt;a href=&#34;https://ssd.eff.org/en/module/key-verification&#34;&gt;key verification&lt;/a&gt; can be susceptible &lt;a href=&#34;https://en.wikipedia.org/wiki/Man-in-the-middle_attack&#34;&gt;man-in-the-middle attacks&lt;/a&gt;. WhatsApp mitigates this limitation in two ways: by providing an optional key verification facility (which the &lt;a href=&#34;https://www.eff.org/deeplinks/2016/04/whatsapp-rolls-out-end-end-encryption-its-1bn-users&#34;&gt;EFF analyzes&lt;/a&gt; quite nicely) and by allowing users to opt-in to getting warning messages when their messaging partner&amp;rsquo;s key has changed (i.e., key-continuity detection).&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/WA-key-message_hu_77e2b7c4acd87321.png&#34; alt=&#34;Screenshot from WhatsApp interface.&#34; width=&#34;740&#34; height=&#34;219&#34;&gt;

&lt;em&gt;The message WhatsApp displays when the other user&amp;rsquo;s key has changed.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;noticing-notifications&#34;&gt;Noticing notifications&lt;/h2&gt;
&lt;p&gt;The current release of WhatsApp does not prompt users to opt-in to encryption-related notifications. The option to do so is a bit hidden in the Settings &amp;gt; Account &amp;gt; Security, but given how few options are in that menu, it&amp;rsquo;s reasonable to expect that someone poking around will discover it without too much trouble. I am curious whether WhatsApp did any user research before or during their design of this interface (which is pictured in Fred&amp;rsquo;s tweet above) to make it discoverable and appealing to users who aren&amp;rsquo;t necessarily looking for it. It should at least be easy to find for users who are seeking it out.&lt;/p&gt;
&lt;p&gt;Designers working with security settings often have to be cautious about pushing users too hard to turn on things that won&amp;rsquo;t be useful to them. Time and again, intrusive security notifications have caused users to be frustrated to the point of turning off the security feature or switching to a less secure product. WhatsApp has done a good job on this front; in the absence of an attack, the notification is both rare (it should only occur when the other person has switched phones or uninstalled and reinstalled the app) and discrete once enabled.&lt;/p&gt;
&lt;p&gt;However, I worry that it may be a little &lt;em&gt;too&lt;/em&gt; discrete. When we were testing it, we actually managed to miss the inline message (pictured above) at first, even though we were explicitly looking for it! This may be because the chat thread wasn’t open when it appeared. Other messages came in after it, pushing it out of the user&amp;rsquo;s focus area, which is centered on the bottom of the screen. It took scrolling back up into the message history to see the inline message. Could an attacker exploit this focus issue with some users by intentionally sending a slew of distracting messages after signing on?&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/WA-key-dialog_hu_ade0846d98968a3a.png&#34; alt=&#34;Screenshot from WhatsApp interface.&#34; width=&#34;740&#34; height=&#34;824&#34;&gt;

&lt;em&gt;The dialog that appears when you tap the inline notification.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Furthermore, while the dialog that pops up when you &amp;ldquo;tap for more info&amp;rdquo; offers reasonable detail (and a &amp;ldquo;learn more&amp;rdquo; option), neither it nor the inline message itself help the user realize that &amp;ldquo;security code changed&amp;rdquo;  means &amp;ldquo;your communication may be at risk&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;I understand that the cases where users are being attacked will be far, far outnumbered by the cases where their messaging partner has simply gotten a new phone. And it&amp;rsquo;s important to not overwhelm users with useless messages. At the same time, when the user chose to turn on these security notifications, they gave a strong signal that they were concerned about security. Perhaps the designers assumed that any user who turned this feature on would know what the warning meant? But if that&amp;rsquo;s the case, why use a term (&amp;ldquo;security code&amp;rdquo;) that is so friendly to security novices, rather than the one that experts are accustomed to (&amp;ldquo;key&amp;rdquo;)?&lt;/p&gt;
&lt;h2 id=&#34;heres-hoping-the-importance-of-research-and-iteration&#34;&gt;Here&amp;rsquo;s hoping: the importance of research and iteration&lt;/h2&gt;
&lt;p&gt;I am so pleased and impressed that WhatsApp has invested the time and energy necessary to release this feature that I am going assume (hope?) that this is just the first of several iterative improvements to this experience. Once they have a chance to look at how the feature has been received and get more data about how often people are engaging with it – likely through both in-app analytics and user research – they can work to make it even more discoverable and useful to users who want to learn more about their security status.&lt;/p&gt;
&lt;p&gt;Here are some concrete suggestions that I would love to see explored.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Are there ways to &lt;strong&gt;surface the notification feature&lt;/strong&gt; to users who haven&amp;rsquo;t opened their account settings? This might itself be a one-time (or once-yearly) notification, ideally some time after the user has completed the initial setup flow so as not to get lost in dialog fatigue. Users could have the option to (1) go directly to their security settings, (2) be reminded to do so later, (3) or dismiss the suggestion permanently.&lt;/li&gt;
&lt;li&gt;Are there patterns of behavior that might indicate that the user is under attack, and be used to &lt;strong&gt;enable the notifications automatically&lt;/strong&gt;? For example, sudden key changes by a number of the users&amp;rsquo; contacts, or the user blocking a number of new contacts.&lt;/li&gt;
&lt;li&gt;Could the inline notification do more to indicate that the change in security code is &lt;strong&gt;worthy of investigation&lt;/strong&gt;? Any solution would need to be coherent in the app&amp;rsquo;s visual design language, of course, but color or iconography could go a long way here.&lt;/li&gt;
&lt;li&gt;Is there some way to prevent users from &lt;strong&gt;missing the inline notification&lt;/strong&gt; as we did in our experiments? The obvious choice would be to have the notification be a modal dialog the first time it appears for a given messaging partner (in addition to the inline message so the user could easily access it again if they accidentally dismissed it), but there are likely other options as well.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;the-perfect-is-the-enemy-of-the-good&#34;&gt;The perfect is the enemy of the good&lt;/h2&gt;
&lt;p&gt;All apps have room for improvement, and designing for both general users (who currently are unlikely to be subject to a MITM attack) and users at risk (who may be targeted by government-level attackers on a daily basis)  is extremely hard to do. WhatsApp and &lt;a href=&#34;https://whispersystems.org/&#34;&gt;Signal&lt;/a&gt; have pushed the envelope of UX design for cryptography to new territories, and have brought end-to-end encrypted messaging to over a billion people. We therefore applaud them for this accomplishment wholeheartedly, and enthusiastically await their future efforts in this realm!&lt;/p&gt;
&lt;p&gt;Are there other design patterns that you have experienced that you think would work well in a context like WhatsApp? Have you tackled similar problems, and would you like to share your efforts with the public? Are you working on a software project and seeking help designing or researching similar experiences? Please &lt;a href=&#34;https://superbloom.design/contact&#34;&gt;get in touch&lt;/a&gt;!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>How UX Excludes or Includes</title>
      <link>https://superbloom.design/learning/blog/ux-includes-excludes/</link>
      <pubDate>Fri, 01 Apr 2016 15:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/ux-includes-excludes/</guid>
      <description>&lt;p&gt;Software communicates its values via its user experience (UX) by making some actions easy and others harder. For example, mobile apps can be configured to automatically opt users in to location sharing, and require people to dig through multiple layers of menus to opt out. This design choice reflects the developer&amp;rsquo;s belief that it&amp;rsquo;s ok to collect location data about users without asking their permission. But this is just one example; values are encoded in software in many ways beyond default settings.&lt;/p&gt;
&lt;p&gt;In 2016 Twitter has come under fire for UX changes, most notably &lt;a href=&#34;http://thenextweb.com/twitter/2015/11/04/why-i-dont-like-twitters-new-heart-button/&#34;&gt;switching their classic star icon&lt;/a&gt; (meaning &amp;ldquo;favorite&amp;rdquo;) to the heart icon (meaning &amp;ldquo;like&amp;rdquo;). Other changes in Twitter&amp;rsquo;s UX send strong messages about what Twitter believes their platform is for.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The GIFs are coming! Get ready to search and send GIFs in Tweets and Direct Messages: &lt;a href=&#34;https://t.co/uk75stt1zN&#34;&gt;https://t.co/uk75stt1zN&lt;/a&gt; &lt;a href=&#34;https://twitter.com/twitter/status/700002208306171904&#34;&gt;pic.twitter.com/1dDD1B4CW2&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The addition of GIFs to the compose window tells users that animated images are an expected, normal part of Twitter. This may come as surprise to long-time Twitter users who see it primarily as a professional or news-sharing communication platform. (These may be many of the same people who felt that hearts were inappropriate or unprofessional replacements to stars.) Normalizing the use of GIFs is probably a way to encourage new users or to encourage new behaviors by current users.&lt;/p&gt;
&lt;p&gt;However, the implementation choices in the GIF search feature also send a more subtle message about how users are expected to express themselves.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/twitter-gif_hu_97688fcb46a5ae4b.jpg&#34; alt=&#34;Screenshot showing a GIF-selection menu.&#34; width=&#34;740&#34; height=&#34;933&#34;&gt;

&lt;em&gt;Inserting a GIF into a tweet with Twitter&amp;rsquo;s web interface. Screenshot from the Twitter interface as viewed in Chrome on OSX.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;ux-shapes-behavior&#34;&gt;UX Shapes Behavior&lt;/h2&gt;
&lt;p&gt;Looking at the options presented, we see that they have included only emotions in the top choices. This shapes user behavior by encouraging them to express strong agreement or dissent. The message that &amp;ldquo;Twitter is for arguing on the internet&amp;rdquo; is encoded into the UX. Of the 8 choices showing, four are positive (Agree, Applause, Awww, and Dance) and four are negative (Deal With It, Do Not Want, Ewww, and Eye Roll). The latter options tell users that they should expect to not only see things they do not want to on the platform, but to also share things that others don&amp;rsquo;t want to see. If someone questions your tweet, the UX suggests adding a &amp;ldquo;Deal With It&amp;rdquo; GIF as a response and moving on.&lt;/p&gt;
&lt;p&gt;Twitter partnered with &lt;a href=&#34;http://techcrunch.com/2016/02/17/here-come-the-gif-twetes/&#34;&gt;Giphy and Riffsy&lt;/a&gt; to provide the GIFs, which focus on pop culture in the United States. It&amp;rsquo;s not clear if or how either the selections of illustrated emotions or the default GIFS are localized for a global audience. The first image illustrating applause is a take from The Lord of the Rings fantasy movie showing white actors dressed in costumes similar to 19th-century British clothes. I have watched that movie many times, but it strikes me as an odd choice to illustrate &amp;ldquo;applause.&amp;rdquo; What does it feel like to not know who those people are? How does that impact diverse users&amp;rsquo; comfort sharing that GIF? Any GIF? Using Twitter in general?&lt;/p&gt;
&lt;p&gt;More fundamentally, what messages do the choice of images and titles for the GIFs send? How do they set the tone for conversation on Twitter? How do they welcome or exclude participation by different groups?&lt;/p&gt;
&lt;p&gt;Communicating with graphics presents challenges for cross-cultural miscommunication in apps beyond Twitter. One example is the choice of words to describe emoji in Slack. I was surprised that the fist icon, which I had used for years on my iPhone in text and WhatsApp messages, is labeled &amp;ldquo;facepunch&amp;rdquo; in Slack. I thought of it as fist-bump, or a modern high five. So every time I thought I was sending a supportive &amp;ldquo;right on, you go, well done&amp;rdquo; message, the recipient may have thought I was punching them in the face.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/punch_hu_4ff4eb3905fb975b.png&#34; alt=&#34;Slack app emoji of face punch&#34; width=&#34;740&#34; height=&#34;350&#34;&gt;

&lt;em&gt;Facepunch sounds less supportive than fist-bump.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;designing-for-inclusion-from-the-beginning&#34;&gt;Designing for Inclusion, From the Beginning&lt;/h2&gt;
&lt;p&gt;I live and work in San Francisco and am familiar with many of same the Gen-X cultural memes that the people working at Twitter, Facebook, or Google are steeped in. I want to make tools approachable and accessible to a global audience, but struggle with ways to make my own biases and cultural assumptions visible so they can be questioned.&lt;/p&gt;
&lt;p&gt;UX designers have an opportunity to &lt;a href=&#34;http://www.fastcompany.com/3058051/the-future-of-work/how-ordinary-tech-workers-can-improve-the-industrys-diversity&#34;&gt;design for inclusion&lt;/a&gt; from the beginning and to challenge their teams to make software welcoming to all kinds of people. Even just thinking about the hands that you show in your product can be informative. Facebook&amp;rsquo;s repository of &lt;a href=&#34;https://design.facebook.com/toolsandresources/diverse-device-hands/&#34;&gt;diverse hand&lt;/a&gt; images is just one visual ways to remind your team and the world who you&amp;rsquo;re designing for (though I&amp;rsquo;d still like to see some painted nails, jewelry, and tattoos in the bunch).&lt;/p&gt;
&lt;p&gt;Rizwan Javid created a &lt;a href=&#34;https://www.rizwanjavaid.com/blog/multicultural-names-for-invisions-craft-plugin-sketch-photoshop/&#34;&gt;set of multicultural names&lt;/a&gt; for InVision&amp;rsquo;s Craft plugins (which integrate with Photoshop and Sketch) to help designers make prototypes that reflect a global userbase. Using this list can help address some practical considerations: can your UI handle a name like &amp;ldquo;Juan Carlos Gutiérrez De La Paz&amp;rdquo; without wrapping when displayed under a profile photo? But it also sends an important message to the team if they know they are designing for Shamika Thompson and Le Ly, instead of just the John Does and Jane Smiths of the world. The small step of including diverse names in an early interface can build empathy and send a message to designers that they are creating something for a global audience.&lt;/p&gt;
&lt;h2 id=&#34;technology-builders&#34;&gt;Technology Builders&lt;/h2&gt;
&lt;p&gt;Beyond designing &lt;em&gt;for&lt;/em&gt; a global audience, look for ways to celebrate the leadership of people of color building technology. Slack designer and developer Diógenes Brito&amp;rsquo;s choice to use a &lt;a href=&#34;https://medium.com/@uxdiogenes/just-a-brown-hand-313db35230c5#.h2p4pw6lp&#34;&gt;brown hand&lt;/a&gt; to unveil a feature in Slack reflects a world where the people creating websites and integrating APIs have brown hands.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;What a lovely day! Why? The new Add to Slack Button—connecting apps to Slack is easy as pie! 🍕&lt;a href=&#34;http://t.co/wSA6bZY3UR&#34;&gt;http://t.co/wSA6bZY3UR&lt;/a&gt; &lt;a href=&#34;https://twitter.com/SlackHQ/status/636223893431160832&#34;&gt;pic.twitter.com/4p1TxVkjBQ&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://twitter.com/radiomorillo&#34;&gt;Stephanie Morillo&lt;/a&gt; and &lt;a href=&#34;https://twitter.com/divinetechygirl&#34;&gt;Christina Morillo&lt;/a&gt; have created a set of &lt;a href=&#34;https://www.flickr.com/photos/wocintechchat&#34;&gt;stock photography&lt;/a&gt; showing women of color tech leaders, developers, and designers — and released it under a Creative Commons license. So next time you need an illustration of a developer or a designer, use them.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/woc-designer-developer_hu_9e6ebc6c890b54e2.png&#34; alt=&#34;Photos of a woman of color standing in front of a whiteboard and of a woman of color using a laptop.&#34; width=&#34;740&#34; height=&#34;545&#34;&gt;

&lt;em&gt;Sample &lt;a href=&#34;https://www.flickr.com/photos/wocintechchat/25677210462/&#34;&gt;UX Designer&lt;/a&gt; and &lt;a href=&#34;https://www.flickr.com/photos/wocintechchat/25703142551/&#34;&gt;Developer&lt;/a&gt; images from &lt;a href=&#34;https://www.flickr.com/photos/wocintechchat/25703142551/&#34;&gt;WOC Tech Chat&lt;/a&gt;, shared under a &lt;a href=&#34;https://creativecommons.org/licenses/by/2.0/&#34;&gt;CC BY 2.0 license.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Download Javid&amp;rsquo;s text files of names from our &lt;a href=&#34;https://github.com/simplysecure/resources/tree/master/UI_text_assets&#34;&gt;GitHub repository&lt;/a&gt; (added there by permission), and &lt;a href=&#34;https://superbloom.design/contact&#34;&gt;tell us&lt;/a&gt; about your favorite resources on designing for diversity!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Contracting Creatives, in Brief</title>
      <link>https://superbloom.design/learning/blog/creative-briefs/</link>
      <pubDate>Fri, 25 Mar 2016 19:15:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/creative-briefs/</guid>
      <description>&lt;p&gt;Your team has reached the stage where you need to hire a professional designer. Maybe you want to finally get a great-looking logo, make a website that doesn&amp;rsquo;t look like it was &lt;a href=&#34;http://www.dolekemp96.org/main.htm&#34;&gt;designed in 1996&lt;/a&gt;, or create a really compelling video for your Kickstarter campaign. In any case, you know that it might be tricky to express what you&amp;rsquo;re looking for – especially if you come from a technical background and aren&amp;rsquo;t used to dealing with folks who work in pixels.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re hiring a designer, you need to write a &lt;a href=&#34;https://articles.uie.com/short_form_creative_brief/&#34;&gt;creative brief&lt;/a&gt;. Briefs can take many forms, but the basic idea is to communicate both what the project is, and give some indication of how the resulting work should &lt;em&gt;feel&lt;/em&gt; – but without getting too detailed or prescriptive.&lt;/p&gt;
&lt;h2 id=&#34;ask-an-expert-a-conversation-with-anne-trausch&#34;&gt;Ask an expert: a conversation with Anne Trausch&lt;/h2&gt;
&lt;p&gt;Ame sat down this week with &lt;a href=&#34;https://www.linkedin.com/in/anne-trausch-5787431&#34;&gt;Anne Trausch&lt;/a&gt;, a veteran content strategist, writer, and designer currently at IDEO San Francisco, to talk about the role a brief plays in a creative process.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Q: What is the essence of a creative brief?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;A creative brief clarifies the restrictions and the opportunity of a particular challenge. It&amp;rsquo;s a call to arms and also a map of where to focus efforts. Briefs answer why the project matters, and what the audience will get out of it.&lt;/p&gt;
&lt;p&gt;They should be short — ideally a page in length — with a simple statement of the problem, objective, audience, main message, reasons to believe the message, and tone.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Briefs put a box around a problem and say, &amp;ldquo;Go wild within this box.&amp;rdquo;
– Anne Trausch&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;em&gt;Q: What words of wisdom do you have about helping organizations communicate their spirit and vision, and in bridging the divide with creative professionals?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;For a creative team to succeed it&amp;rsquo;s vital to clarify a strategic direction and foster agreements around any limits to the approach. Briefs outline what criteria a good solution will have to adhere to. Understanding the restrictions of a project can be liberating. Briefs put a box around a problem and say, &amp;ldquo;Go wild within this box.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The best solutions are often unfamiliar, bold, and new. In those cases, a team could be anxious trusting something seemingly unproven. A good brief reminds everyone of the strategic intent and can help keep conversations and discussions focused on how well the proposed solution addresses the challenge, and not get bogged down in how the team feels about it.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I have never been forced to accept compromises, but I have willingly accepted constraints.
– Charles Eames&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&#34;to-review-briefs-in-practice&#34;&gt;To review: briefs in practice&lt;/h2&gt;
&lt;p&gt;Building on Anne&amp;rsquo;s wisdom, here are some practical tips for people new to writing creative briefs.&lt;/p&gt;
&lt;p&gt;Keep it &lt;em&gt;brief&lt;/em&gt;. When in doubt, focus on the basics.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What problem are you trying to solve with this creative endeavor?&lt;/li&gt;
&lt;li&gt;What outcomes do you want to see as a result?&lt;/li&gt;
&lt;li&gt;Who is your audience for this project?&lt;/li&gt;
&lt;li&gt;What message do you want to convey?&lt;/li&gt;
&lt;li&gt;What reasons does someone have to believe your message?&lt;/li&gt;
&lt;li&gt;How do you want the project to &lt;em&gt;feel&lt;/em&gt; – what&amp;rsquo;s the emotion, the spirit, or the values that you want to convey?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Remember, successful briefs not only convey your hopes and dreams for a project, but also provide some creative breathing room. After all, you&amp;rsquo;re not hiring a printer to manufacture an artifact you&amp;rsquo;ve already fully envisioned, but a creative professional whose talent will, if all goes well, bring something new and beautiful into the world.&lt;/p&gt;
&lt;p&gt;Once you have your brief in hand, you can work to find someone who will use it as a starting place for a conversation on what can be achieved on your budget and timeline. One tip for finding a designer is to look at the work they&amp;rsquo;ve already done, and try and find someone whose past projects have a similar scope and spirit to what you&amp;rsquo;re looking to accomplish. Personal referrals can be great, but only if the person&amp;rsquo;s experience is also in line with the work you want to have done.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re an open-source team looking to collaborate on a design project for the first time and need a hand writing a brief or finding a designer, &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;get in touch&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://player.vimeo.com/video/107567840?badge=0&#34; alt=&#34;Learn about creative briefs from the perspective of creative professionals themselves in Briefly from Bassett &amp;amp; Partners&#34;&gt;

&lt;em&gt;Learn about creative briefs from the perspective of creative professionals themselves in &lt;a href=&#34;https://vimeo.com/107567840&#34;&gt;Briefly&lt;/a&gt; from &lt;a href=&#34;https://vimeo.com/bassettandpartners&#34;&gt;Bassett &amp;amp; Partners&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Contracting Creatives, in Brief</title>
      <link>https://superbloom.design/learning/resources/creative-briefs/</link>
      <pubDate>Fri, 25 Mar 2016 19:15:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/creative-briefs/</guid>
      <description>&lt;p&gt;Your team has reached the stage where you need to hire a professional designer. Maybe you want to finally get a great-looking logo, make a website that doesn&amp;rsquo;t look like it was &lt;a href=&#34;http://www.dolekemp96.org/main.htm&#34;&gt;designed in 1996&lt;/a&gt;, or create a really compelling video for your Kickstarter campaign. In any case, you know that it might be tricky to express what you&amp;rsquo;re looking for – especially if you come from a technical background and aren&amp;rsquo;t used to dealing with folks who work in pixels.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re hiring a designer, you need to write a &lt;a href=&#34;https://articles.uie.com/short_form_creative_brief/&#34;&gt;creative brief&lt;/a&gt;. Briefs can take many forms, but the basic idea is to communicate both what the project is and give some indication of how the resulting work should &lt;em&gt;feel&lt;/em&gt; – but without getting too detailed or prescriptive.&lt;/p&gt;
&lt;h2 id=&#34;ask-an-expert-a-conversation-with-anne-trausch&#34;&gt;Ask an expert: a conversation with Anne Trausch&lt;/h2&gt;
&lt;p&gt;Ame sat down this week with &lt;a href=&#34;https://www.linkedin.com/in/anne-trausch-5787431&#34;&gt;Anne Trausch&lt;/a&gt;, a veteran content strategist, writer, and designer currently at IDEO San Francisco, to talk about the role a brief plays in a creative process.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Q: What is the essence of a creative brief?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;A creative brief clarifies the restrictions and the opportunity of a particular challenge. It&amp;rsquo;s a call to arms and also a map of where to focus efforts. Briefs answer why the project matters and what the audience will get out of it.&lt;/p&gt;
&lt;p&gt;They should be short — ideally a page in length — with a simple statement of the problem, objective, audience, main message, reasons to believe the message, and tone.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Briefs put a box around a problem and say, &amp;ldquo;Go wild within this box.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;– Anne Trausch&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;em&gt;Q: What words of wisdom do you have about helping organizations communicate their spirit and vision, and in bridging the divide with creative professionals?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;For a creative team to succeed, it&amp;rsquo;s vital to clarify a strategic direction and foster agreements around any limits to the approach. Briefs outline what criteria a good solution will have to adhere to. Understanding the restrictions of a project can be liberating. Briefs put a box around a problem and say, &amp;ldquo;Go wild within this box.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The best solutions are often unfamiliar, bold, and new. In those cases, a team could be anxious trusting something seemingly unproven. A good brief reminds everyone of the strategic intent and can help keep conversations and discussions focused on how well the proposed solution addresses the challenge, and not get bogged down in how the team feels about it.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I have never been forced to accept compromises, but I have willingly accepted constraints.&lt;/p&gt;
&lt;p&gt;– Charles Eames&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&#34;to-review-briefs-in-practice&#34;&gt;To review: briefs in practice&lt;/h2&gt;
&lt;p&gt;Building on Anne&amp;rsquo;s wisdom, here are some practical tips for people new to writing creative briefs.&lt;/p&gt;
&lt;p&gt;Keep it &lt;em&gt;brief&lt;/em&gt;. When in doubt, focus on the basics.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What problem are you trying to solve with this creative endeavor?&lt;/li&gt;
&lt;li&gt;What outcomes do you want to see as a result?&lt;/li&gt;
&lt;li&gt;Who is your audience for this project?&lt;/li&gt;
&lt;li&gt;What message do you want to convey?&lt;/li&gt;
&lt;li&gt;What reasons does someone have to believe your message?&lt;/li&gt;
&lt;li&gt;How do you want the project to &lt;em&gt;feel&lt;/em&gt; – what&amp;rsquo;s the emotion, the spirit, or the values that you want to convey?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Remember, successful briefs not only convey your hopes and dreams for a project but also provide some creative breathing room. After all, you&amp;rsquo;re not hiring a printer to manufacture an artifact you&amp;rsquo;ve already fully envisioned, but a creative professional whose talent will, if all goes well, bring something new and beautiful into the world.&lt;/p&gt;
&lt;p&gt;Once you have your brief in hand, you can work to find someone who will use it as a starting place for a conversation on what can be achieved on your budget and timeline. One tip for finding a designer is to look at the work they&amp;rsquo;ve already done, and try and find someone whose past projects have a similar scope and spirit to what you&amp;rsquo;re looking to accomplish. Personal referrals can be great, but only if the person&amp;rsquo;s experience is also in line with the work you want to have done.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re an open-source team looking to collaborate on a design project for the first time and need a hand writing a brief or finding a designer, &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;get in touch&lt;/a&gt;!&lt;/p&gt;

      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/107567840?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;p&gt;&lt;em&gt;Learn about creative briefs from the perspective of creative professionals themselves in &lt;a href=&#34;https://vimeo.com/107567840&#34;&gt;Briefly&lt;/a&gt; from &lt;a href=&#34;https://vimeo.com/bassettandpartners&#34;&gt;Bassett &amp;amp; Partners&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Notes from the Internet Freedom Festival</title>
      <link>https://superbloom.design/learning/blog/notes-iff-2016/</link>
      <pubDate>Fri, 18 Mar 2016 19:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/notes-iff-2016/</guid>
      <description>&lt;p&gt;I really enjoyed my time at the &lt;a href=&#34;https://internetfreedomfestival.org/&#34;&gt;Internet Freedom Festival&lt;/a&gt; in Valencia, Spain. I was inspired and humbled to meet so many talented people as part of a global event about internet freedom. From powerful conversations about privilege to UX design jam sessions, it was a great week. With more than 600 people registered and 160+ sessions, there was more terrific discussion than I could be part of, but here are some themes that stuck with me.&lt;/p&gt;
&lt;h2 id=&#34;designing-with-and-designing-for&#34;&gt;Designing With and Designing For&lt;/h2&gt;
&lt;p&gt;IFF is the &lt;a href=&#34;https://team.cartodb.com/u/jsanz/viz/5044e12c-e473-11e5-ae2b-0e98b61680bf/public_map&#34;&gt;most global event&lt;/a&gt; I&amp;rsquo;ve attended, with people from 43+ countries. It was an eye-opening exposure to what the global internet is like in 2016, and how much work is needed to make it better. I&amp;rsquo;m a practitioner of Human-Centered Design who believes that empathy should be the foundation for building technology, and some of my most memorable discussions were about privilege, power, and my own biases. From observations on white-knighting, the minimization of lived experiences, and more, I came away with a renewed appreciation for the distinction between designing with people by involving them as partners versus designing for people in ways that are disrespectful and take away agency. I&amp;rsquo;m looking forward to listening and learning more. Thank you to the people who challenged me and encouraged me to grow.&lt;/p&gt;
&lt;h2 id=&#34;data-algorithms--you&#34;&gt;Data, Algorithms, &amp;amp; You&lt;/h2&gt;
&lt;p&gt;As an example of this, Tara Adiseshan&amp;rsquo;s &lt;a href=&#34;https://web.archive.org/web/20220121120311/https://internetfreedomfestival.org/wiki/index.php/Designing_Participatory_Algorithmic_Decision-Making_Processes&#34;&gt;Designing Participatory Algorithmic Decision-Making Processes&lt;/a&gt; challenged me to think more broadly about structural discrimination, and how dangerous the myth of &amp;ldquo;neutral data&amp;rdquo; is in an era when algorithms determine so much of our experiences – pricing, credit scores, and more. There is a powerful design opportunity to give people agency to understand what data about them is collected and how to participate in the outcomes. Check out the &lt;a href=&#34;https://twitter.com/algorithm_club&#34;&gt;Algorithm Club&lt;/a&gt;, a Twitter book club, for more.&lt;/p&gt;
&lt;p&gt;Continuing the theme of data and algorithms, Sarah Gold and Ian Hutchinson from Projects By If&amp;rsquo;s session &lt;a href=&#34;https://web.archive.org/web/20220429091917/https://internetfreedomfestival.org/wiki/index.php/You_and_your_data&#34;&gt;You and Your Data&lt;/a&gt; turned out to be the boldest empathy exercise I encountered at IFF, encouraging empathy for advertisers and people who make their money from advertising revenue. This participatory discussion imagined the &lt;a href=&#34;https://medium.com/@projectsbyif/if-at-iff-advertising-after-adblockers-da11c71df292#.pwmf7qas5&#34;&gt;internet after adblockers&lt;/a&gt;. I&amp;rsquo;m interested to see their &lt;a href=&#34;https://catalogue.projectsbyif.com/&#34;&gt;examples of data permissions&lt;/a&gt; work as a case study of how policy, user experience, and data agency intersect.&lt;/p&gt;
&lt;h2 id=&#34;building-better-ux&#34;&gt;Building Better UX&lt;/h2&gt;
&lt;p&gt;Huge thanks everyone who participated in the &lt;a href=&#34;https://web.archive.org/web/20220429093702/https://internetfreedomfestival.org/wiki/index.php/UI_and_Usability_Jam_Sessions&#34;&gt;UI and Usability Jam&lt;/a&gt;, a workshop connecting the a community of people working to improve the design and usability of internet freedom tools. If you haven&amp;rsquo;t seen these &lt;a href=&#34;https://superbloom.design/learning/blog/self-starter&#34;&gt;Resources for UX Self-Education&lt;/a&gt;, take a look. My biggest inspiration came from appreciating how the well-known user onboarding challenge of empty states – or the initial state of the interface before there&amp;rsquo;s activity to display – is an opportunity for techno-activists to attract people to their movement. Triggered by Stingray Mapping and &lt;a href=&#34;https://whereat.io/&#34;&gt;Whereat.io&lt;/a&gt;’s use of location information in compelling ways, I got excited about how &amp;ldquo;demo mode,&amp;rdquo; or using an app solely for the purpose to showing features, is an opportunity to reinforce the values that lead people to download the app in the first place. Special thanks to Bridget Sheerin for pushing my thinking about radars and other dynamic interfaces for communicating location tracking.&lt;/p&gt;
&lt;p&gt;I was also glad to see more sessions about the craft of UX. Thanks to our Fellow &lt;a href=&#34;https://medium.com/@gusandrews&#34;&gt;Gus Andrews&lt;/a&gt; for a great session focused on &lt;a href=&#34;https://web.archive.org/web/20220429093702/https://internetfreedomfestival.org/wiki/index.php/Feedback_on_secure_tools:_Giving_it_and_getting_it_more_easily,_with_graphics&#34;&gt;tools and feedback&lt;/a&gt;, and to Sajolida for the &lt;a href=&#34;https://web.archive.org/web/20220429093621/https://internetfreedomfestival.org/wiki/index.php/User_experience_of_configuring_Tor_in_Tails_(and_Tor_Browser_and_Whonix)&#34;&gt;Tor configuration in Tails&lt;/a&gt; feedback session.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Thanks &lt;a href=&#34;https://twitter.com/gusandrews&#34;&gt;@gusandrews&lt;/a&gt; for graphic tools for feedback &lt;a href=&#34;https://twitter.com/hashtag/InternetFF?src=hash&#34;&gt;#InternetFF&lt;/a&gt;. &lt;a href=&#34;https://twitter.com/hashtag/ux?src=hash&#34;&gt;#ux&lt;/a&gt; design FTW. &lt;a href=&#34;https://twitter.com/anxiaostudio&#34;&gt;@anxiaostudio&lt;/a&gt; &lt;a href=&#34;https://twitter.com/xurxosanz&#34;&gt;@xurxosanz&lt;/a&gt; &lt;a href=&#34;https://t.co/rFhVljA12Q&#34;&gt;pic.twitter.com/rFhVljA12Q&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Finally, inspired by An Xiao Mina&amp;rsquo;s &lt;a href=&#34;https://web.archive.org/web/20220429093702/https://internetfreedomfestival.org/wiki/index.php/Multilingual_Design:_Bringing_Language_Access_to_the_Full_Stack&#34;&gt;Multilingual Design&lt;/a&gt; session, I&amp;rsquo;ve been thinking more about majority and minority languages, and what a more linguistically inclusive internet would be like. As a first step, I&amp;rsquo;m working to follow more people on Twitter who Tweet in languages other than English.&lt;/p&gt;
&lt;p&gt;I came away from the Festival energized by the vibrant and passionate community and fired up to make the internet a better place.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Learning Lessons Where We Find Them: Analyzing Facebook&#39;s Privacy Checkup, Part 1</title>
      <link>https://superbloom.design/learning/blog/facebook-p1/</link>
      <pubDate>Fri, 11 Mar 2016 19:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/facebook-p1/</guid>
      <description>&lt;p&gt;&lt;em&gt;This is the first in a short series of posts looking at Facebook&amp;rsquo;s &amp;ldquo;Privacy Checkup&amp;rdquo; feature. This installment examines why even privacy advocates who avoid social-media sites should take time to understand it and related user experiences. The next installment will go into depth critiquing the feature itself, taking lessons from the user experience that are useful to any designer of privacy or security-related software.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;As a reader of the Simply Secure blog, chances are good that you spend a fair amount of time thinking about privacy and data security. If you use programs like &lt;a href=&#34;https://www.torproject.org/projects/torbrowser.html.en&#34;&gt;Tor Browser&lt;/a&gt;, &lt;a href=&#34;https://www.eff.org/privacybadger&#34;&gt;Privacy Badger&lt;/a&gt;, or &lt;a href=&#34;https://whispersystems.org/&#34;&gt;Signal&lt;/a&gt;, you might express your personal data-privacy goals with statements like &amp;ldquo;I don&amp;rsquo;t want anyone to be able to follow what I do online,&amp;rdquo; &amp;ldquo;I want to be able to control my online data and metadata as much as possible,&amp;rdquo; or &amp;ldquo;I don&amp;rsquo;t want any companies or governments spying on me.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;While people who don&amp;rsquo;t use these types of programs may have spent fewer hours searching out vetted open-source software, that doesn&amp;rsquo;t mean that they don&amp;rsquo;t care about their data privacy. The Pew Research Center has &lt;a href=&#34;http://www.pewresearch.org/key-data-points/privacy/&#34;&gt;found&lt;/a&gt; that &amp;ldquo;91% of American adults say that consumers have lost control over how personal information is collected and used by companies,&amp;rdquo; and that &amp;ldquo;the public has little confidence in the security of their everyday communications.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;One thing that Ame heard during her &lt;a href=&#34;https://superbloom.design/learning/blog/straight-talk&#34;&gt;recent study&lt;/a&gt; in New York City is that participants were concerned that they were being surveilled by the police through Facebook. Although we need no external validation or justification of their concerns to find meaning in their lived experience, there is tremendous evidence that their fears are justified – as reported by &lt;a href=&#34;http://www.theverge.com/2014/12/10/7341077/nypd-harlem-crews-social-media-rikers-prison&#34;&gt;The Verge&lt;/a&gt;, &lt;a href=&#34;http://www.theguardian.com/us-news/2015/apr/23/online-surveillance-black-teenagers-new-stop-and-frisk&#34;&gt;The Guardian&lt;/a&gt;, and other outlets.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The mix of social media and conspiracy statutes creates a dragnet that can bring almost anybody in.
– Andrew Laufer, as quoted by &lt;a href=&#34;http://www.theverge.com/2014/12/10/7341077/nypd-harlem-crews-social-media-rikers-prison&#34;&gt;The Verge&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Of course, some privacy advocates would tell people with these concerns that privacy is anathema to sites like Facebook because their revenue model is largely based on gathering data about users and selling targeted ads. And, depending on your threat model and the security practices of the social-media site in question, it&amp;rsquo;s true that sharing your data with such sites can put your security at risk – both online and in the physical world – especially if you are an activist under threat from state actors.&lt;/p&gt;
&lt;p&gt;But there is no single definition of what is &amp;ldquo;private enough.&amp;rdquo; Everyone has different threat models. And as a user advocate with a human-centered-design ethos, I argue that it is not reasonable to simply tell &lt;a href=&#34;http://newsroom.fb.com/company-info/&#34;&gt;a billion&lt;/a&gt; or more people that they should abandon the platforms they use to communicate every day with friends and relatives – that they use to buy used clothing for their children, get inspiration for their creative endeavors, and hunt for job opportunities. The value that users get from these sites is too high; a message to leave it based on amorphous privacy threats would fall on closed ears.&lt;/p&gt;
&lt;p&gt;We should instead make sure that users have the tools they need to manage who can see their data, and work to understand the ways that sites share data outside of the user-visible platform. It sounds like the New York City police are not able to obtain warrants that provide them access to large swaths of the local population&amp;rsquo;s accounts (although I welcome correction on this point). This means that helping users control who sees their data shared through the platform – and an increased focus on helping individuals detect phony friend requests – could go a long way toward protecting the participants Ame talked to who were concerned about unwarranted police surveillance.&lt;/p&gt;
&lt;p&gt;This is why features like Facebook&amp;rsquo;s &amp;ldquo;Privacy Checkup&amp;rdquo; hold great potential. The best way to understand how well it works for users in practice would be to look at Facebook&amp;rsquo;s usage statistics (How many users complete the checkup? What changes do they implement as part of the process? Do they engage more with their privacy settings than users who don&amp;rsquo;t interact with the feature? Do their sharing behaviors change after completing the checkup?) or perform a user study (Do users understand what is going on? Are they happy with the results of the checkup when they&amp;rsquo;re complete? What about six months later? Do they feel that their data is safer? Do they work with friends or family to help them protect their data?). But, we&amp;rsquo;re going to be scrappy and do an armchair expert review – the kind of analysis that is easy to perform on any piece of software after using it for a short amount of time. This kind of review is most useful for identifying low-hanging fruit – i.e., obvious things that may confuse or frustrate users.&lt;/p&gt;
&lt;p&gt;Stay tuned for the next post in this series, where we&amp;rsquo;ll start taking the feature apart and identifying lessons that are useful to any designer of privacy or security-related software.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/fb-privacy-settings_hu_59fea85589647695.png&#34; alt=&#34;Screenshot of Scout&amp;rsquo;s Facebook account, taken today.&#34; width=&#34;740&#34; height=&#34;702&#34;&gt;

&lt;em&gt;Screenshot of Scout&amp;rsquo;s Facebook account, taken today.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Be a self-starter: UX educational resources</title>
      <link>https://superbloom.design/learning/blog/self-starter/</link>
      <pubDate>Tue, 01 Mar 2016 13:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/self-starter/</guid>
      <description>&lt;h2 id=&#34;user-experience-self-education-resources&#34;&gt;User Experience Self-Education Resources&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;An annotated list by &lt;a href=&#34;http://about.me/susanfarrell&#34;&gt;Susan Farrell&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Last updated&lt;/strong&gt;: 1 March 2016
&lt;strong&gt;Status&lt;/strong&gt;: Beta / draft
&lt;strong&gt;Suggestions, etc.&lt;/strong&gt;: &lt;a href=&#34;mailto:susanf@acm.org&#34;&gt;susanf@acm.org&lt;/a&gt;
&lt;strong&gt;Usage Intent&lt;/strong&gt;: Please ask, until it&amp;rsquo;s under version control at GitHub. This is just a draft.
&lt;strong&gt;Intended Audience&lt;/strong&gt;: Anyone who wants to learn how to make things easier to use, through better design and research.&lt;/p&gt;
&lt;h3 id=&#34;what-is-user-experience-ux&#34;&gt;What is User Experience? (UX)&lt;/h3&gt;
&lt;p&gt;There are a lot of &lt;a href=&#34;https://en.wikipedia.org/wiki/User_experience&#34;&gt;official and unofficial definitions worth reading&lt;/a&gt;. An applied version:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;User experience is concerned with what happens when someone uses something (tools, designs, systems, toys, amusement parks, etc.) and their experience of that.&lt;/li&gt;
&lt;li&gt;People experience interacting with businesses and organizations in various ways for various reasons (find information, shop, research, call, buy, receive, set up, repair, return, email, branding, stores, etc.).&lt;/li&gt;
&lt;li&gt;A person&amp;rsquo;s user experience with something can be good, bad, ugly, brilliant, fun, embarrassing, and so on.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://en.wikipedia.org/wiki/Usability&#34;&gt;Usability&lt;/a&gt; can, and should, be &lt;a href=&#34;https://en.wikipedia.org/wiki/Comparison_of_usability_evaluation_methods&#34;&gt;evaluated&lt;/a&gt;. Occasionally it should be measured, but quick, qualitative testing with users helps you improve outcomes faster, especially while designing.&lt;/li&gt;
&lt;li&gt;The profession of UX is a big set of people with many and various combinations of UX skills.&lt;/li&gt;
&lt;li&gt;They are all trying to improve people&amp;rsquo;s lives by making software, information, products, services, and other designed experiences, better, easier to use, and more delightful.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/UXUnicorn_hu_e01443dc5f39ab.png&#34; alt=&#34;Image of a unicorn composed of different elements of the user-experience process&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The skills and responsibilities of an effective team. It’s ideal to have more than one UX person to ensure important sub-specialties are covered. Originally published in &lt;a href=&#34;http://blog.invisionapp.com/building-an-enterprise-ux-team&#34;&gt;Building an enterprise UX team&lt;/a&gt; by &lt;a href=&#34;https://twitter.com/RainbowliciousD&#34;&gt;Rachel Daniel&lt;/a&gt; (also on &lt;a href=&#34;https://www.linkedin.com/in/racheldaniel&#34;&gt;LinkedIn&lt;/a&gt;), UX Director at MaxPoint. Used by permission.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;What&amp;rsquo;s a good user experience? Well, that depends on things like:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Who the users are&lt;/li&gt;
&lt;li&gt;What the purpose of the system is&lt;/li&gt;
&lt;li&gt;What people expect&lt;/li&gt;
&lt;li&gt;How well it meets their needs&lt;/li&gt;
&lt;li&gt;How they feel about it&lt;/li&gt;
&lt;li&gt;And how it&amp;rsquo;s experienced, sustained, and maintained over time&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;why-improving-human-computer-interaction-matters&#34;&gt;Why improving human-computer interaction matters&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;In many parts of the world, every business is suddenly in the software business&lt;/li&gt;
&lt;li&gt;Everyone is a potential computer user&lt;/li&gt;
&lt;li&gt;UX methods solve important problems for people and organizations&lt;/li&gt;
&lt;li&gt;UX research finds and meets real, human needs&lt;/li&gt;
&lt;li&gt;People want to be delighted. Functionality is usually not enough.&lt;/li&gt;
&lt;li&gt;You can decide with data (stop arguing)&lt;/li&gt;
&lt;li&gt;You can create more-appropriate products and services by collaborating with users&lt;/li&gt;
&lt;li&gt;You can find and mitigate risks by testing designs early and often&lt;/li&gt;
&lt;li&gt;You can measure how much more usable your products and services are over time&lt;/li&gt;
&lt;li&gt;You can compare your offerings with competitors’&lt;/li&gt;
&lt;li&gt;You can streamline: saving time, effort, and money&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;how-to-get-up-to-speed&#34;&gt;How to Get Up to Speed&lt;/h3&gt;
&lt;p&gt;&lt;a href=&#34;http://nngroup.com/reports/user-experience-careers/&#34;&gt;User Experience Careers (free report and article)&lt;/a&gt; Read this to see if it sounds right for you.&lt;/p&gt;
&lt;p&gt;Start doing these things one at a time until you&amp;rsquo;re doing all of them:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Carry a notebook&lt;/li&gt;
&lt;li&gt;Collect screenshots and photos of designs that work well and poorly&lt;/li&gt;
&lt;li&gt;Pay attention to the details of every interface you use&lt;/li&gt;
&lt;li&gt;Aggressively teach yourself by reading books&lt;/li&gt;
&lt;li&gt;Find a mentor and a community&lt;/li&gt;
&lt;li&gt;Get (and later provide) an internship or apprentice position&lt;/li&gt;
&lt;li&gt;Take some courses online and also hands-on workshops&lt;/li&gt;
&lt;li&gt;Learn to describe interfaces and interactions as precisely as possible&lt;/li&gt;
&lt;li&gt;Embrace usability testing so you can learn what works and check designs as you build&lt;/li&gt;
&lt;li&gt;&amp;mdash;&amp;ndash;Start designing&amp;mdash;&amp;ndash;&lt;/li&gt;
&lt;li&gt;(Don&amp;rsquo;t get distracted by tools, use what you can get that works)&lt;/li&gt;
&lt;li&gt;Paper prototyping&lt;/li&gt;
&lt;li&gt;Interactive prototyping&lt;/li&gt;
&lt;li&gt;Practice&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;where-to-start-reading&#34;&gt;Where to Start: Reading&lt;/h3&gt;
&lt;p&gt;Principles of visual design
HCI university textbook(s) that cover both design and ergonomics / human factors
Interaction design
Accessibility
Research methods (overview)
Information architecture
How to analyze data&lt;/p&gt;
&lt;p&gt;You are what you read. Get serious by hitting the books. There&amp;rsquo;s no faster or better way to educate yourself. Snack a little with blogs, talks, and workshops, sure; but the books are where the foundational learning happens. Everyone in UX has read these, will read these, or has them on hand for reference. See also other books these people write. Find more in their bibliographies. Go to CHI, UXPA, and other conferences where new design research papers are presented. (See UX Professional Organizations, below.)&lt;/p&gt;
&lt;h4 id=&#34;books&#34;&gt;Books&lt;/h4&gt;
&lt;p&gt;Great books on interface design are infrequent. The old textbooks have a lot of good in them still. Humans hardly ever change, and usability problems seem perennial.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/Dont-Make-Think-Revisited-Usability/dp/0321965515/&#34;&gt;Don&amp;rsquo;t Make Me Think&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/Design-Everyday-Things-Revised-Expanded/dp/0465050654/&#34;&gt;The Design of Everyday Things&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.oreilly.com/ideas/ux-for-beginners-key-ideas&#34;&gt;UX For Beginners: Key Ideas&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/Rocket-Surgery-Made-Easy-Do-It-Yourself/dp/0321657292/&#34;&gt;Rocket Surgery Made Easy - Do It Yourself&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/The-User-Experience-Team-One/dp/1933820187/&#34;&gt;The User Experience Team of One&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.usability.gov/sites/default/files/documents/guidelines_book.pdf&#34;&gt;Research-Based Web Design and Usability Guidelines (PDF - free)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/AWeb-Everyone-Designing-Accessible-Experiences-ebook/dp/B00HCREJZ6/&#34;&gt;A Web for Everyone - Designing Accessible Experiences&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/Observing-User-Experience-Practitioners-Research/dp/1558609237/&#34;&gt;Observing the User Experience&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/Designing-Interfaces-Jenifer-Tidwell/dp/1449379702/&#34;&gt;Designing Interfaces&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/About-Face-Essentials-Interaction-Design/dp/1118766571/&#34;&gt;About Face - Essentials of Interaction Design&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.jjg.net/elements/&#34;&gt;The Elements of User Experience: User-Centered Design for the Web&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/Information-Architecture-Beyond-Louis-Rosenfeld/dp/1491911689/&#34;&gt;Information Architecture: For the Web and Beyond&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/Search-Analytics-Your-Louis-Rosenfeld-ebook/dp/B005EI86HC/&#34;&gt;Search Analytics for Your Site&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/dp/B004VFUOWY/&#34;&gt;Remote Research&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/dp/1933820217/&#34;&gt;Prototyping: A Practitioner&amp;rsquo;s Guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/dp/0124157815/&#34;&gt;Measuring the User Experience&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.amazon.com/dp/1937557286/&#34;&gt;Designing for Touch&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.nngroup.com/articles/recommended-user-interface-books/&#34;&gt;NN/g recommended UI Books&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;other&#34;&gt;Other&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;http://usabilitygeek.com/top-20-user-experience-blogs-resources-2015/&#34;&gt;Top [35] blogs and resource website list by usabilitygeek.com&lt;/a&gt; (Don&amp;rsquo;t miss their Honorable Mentions at the bottom)&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://uipatterns.io/&#34;&gt;UI Patterns&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There are many pattern libraries, including the above; seek them out.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Look at a lot of patterns to understand interaction.&lt;/li&gt;
&lt;li&gt;Beware copy-pasting. Almost nothing is universally appropriate, and interfaces evolve (and devolve) all the time. If your platform has an official style and pattern library, start with that.&lt;/li&gt;
&lt;li&gt;Some popular patterns are awful. Figure out why.&lt;/li&gt;
&lt;li&gt;When someone mentions a great app or website, find out what makes it so great.&lt;/li&gt;
&lt;li&gt;Optimize and improve design patterns that people already love. Don&amp;rsquo;t reinvent the wheel. Invent new controls and interactions, but test them.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;websites-for-ux-reference-and-best-practices&#34;&gt;Websites for UX Reference and Best Practices&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.nngroup.com&#34;&gt;https://www.nngroup.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://usabilitynet.org&#34;&gt;http://usabilitynet.org&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://hcibib.org&#34;&gt;http://hcibib.org&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://usability.gov&#34;&gt;http://usability.gov&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.nngroup.com/reports/how-to-recruit-participants-usability-studies/&#34;&gt;How to Recruit Participants for Usability Studies&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.cs.umd.edu/users/ben/goldenrules.html&#34;&gt;The Eight Golden Rules of Interface Design&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://www.universalusability.com/resources.html&#34;&gt;Universal Usability Resources&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;ux-professional-organizations&#34;&gt;UX Professional Organizations&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;http://uxpa.org/&#34;&gt;uxpa.org&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://sigchi.org/&#34;&gt;sigchi.org&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://ixda.org/&#34;&gt;ixda.org&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;interesting-talks-and-resources&#34;&gt;Interesting Talks and Resources&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://www.youtube.com/results?search_query=bret+victor&#34;&gt;Brett Victor&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://offlinefirst.org/&#34;&gt;Offline First&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Reaching For The Masses: Protecting Privacy Through Better Software</title>
      <link>https://superbloom.design/learning/blog/cfr-brief/</link>
      <pubDate>Fri, 26 Feb 2016 18:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/cfr-brief/</guid>
      <description>&lt;p&gt;Many regular readers of our blog have already &lt;a href=&#34;https://en.wikipedia.org/wiki/Drinking_the_Kool-Aid&#34;&gt;drunk the metaphorical Kool-Aid&lt;/a&gt;. You know that a good user experience is critical to an app&amp;rsquo;s success; moreover, you know that when a piece of software seeks to preserve its users&amp;rsquo; privacy, a poor UX can have disastrous results.&lt;/p&gt;
&lt;p&gt;But working in a community of passionate individuals – whether it&amp;rsquo;s as a designer, a cryptographer, or an internet-freedom activist – can make it easy to forget that the majority of the human race isn&amp;rsquo;t aware of your favorite issues. It&amp;rsquo;s easy to lose sight of the fact that most people don&amp;rsquo;t spend their days thinking about their relationship to software, or how their software handles their data. The recent news about &lt;a href=&#34;https://en.wikipedia.org/wiki/FBI_v._Apple&#34;&gt;Apple and the FBI&lt;/a&gt; have brought many of these issues to the forefront, but it&amp;rsquo;s hard for people on the outside to sort through the hype to understand what&amp;rsquo;s really going on.&lt;/p&gt;
&lt;p&gt;Although our main focus at Simply Secure is on helping UX professionals and software developers learn, connect, and grow in their efforts to make great experiences for their users, we also try to help other communities understand the space we work in. To that end, I recently penned &amp;ldquo;Protecting Data Privacy With User-Friendly Software&amp;rdquo; for the &lt;a href=&#34;http://www.cfr.org/&#34;&gt;Council on Foreign Relations&lt;/a&gt; series of &amp;ldquo;&lt;a href=&#34;http://www.cfr.org/thinktank/dcp/cyberbrief.html&#34;&gt;Cyber Briefs&lt;/a&gt;&amp;rdquo;. The CFR &lt;a href=&#34;http://www.cfr.org/about/mission.html&#34;&gt;positions itself&lt;/a&gt; as &amp;ldquo;a resource for its members, government officials, business executives, journalists, educators and students, civic and religious leaders, and other interested citizens&amp;rdquo; – many of whom aren&amp;rsquo;t familiar with the difference between symmetric and asymmetric crypto, or between UI and UX.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Policymakers in the United States and other countries should recognize that anything less than intact cryptography puts all users at risk. Developers cannot build software that allows law enforcement to access encrypted communications but prevents malicious actors from exploiting that access. Cryptography cannot distinguish good people from bad, so a backdoor for one is a backdoor for all.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;The focus of too many projects has long been on users who resemble the developers themselves. It is time to professionalize the practice of open-source development, recruit designers and usability researchers to the cause, and take a human-centered approach to software design. In particular, project leaders should make the development process more accessible to new participants by including explicit instructions to user-experience experts in their documentation.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;You can read the full brief &lt;a href=&#34;https://www.cfr.org/report/protecting-data-privacy-user-friendly-software&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Features – Like Backdoors – Are Forever</title>
      <link>https://superbloom.design/learning/blog/backdoors-are-forever/</link>
      <pubDate>Fri, 19 Feb 2016 18:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/backdoors-are-forever/</guid>
      <description>&lt;p&gt;We are pleased to announce a new collaboration with the &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt; as part of their &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Usability Lab&lt;/a&gt; project. This exciting initiative will allow open-source software projects to &lt;a href=&#34;https://docs.google.com/a/simplysecure.org/forms/d/1uOPAhJLspvP9RydoGDCci2gKkOjzgF6qExBFHbuL-3Q/viewform&#34;&gt;apply&lt;/a&gt; for free assistance with user-experience (UX) design as well as usability research. To our knowledge, this is the first program to offer support of this kind.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/otf-simsec_hu_987626dd4e7f2c4d.png&#34; alt=&#34;Open Technology Fund &amp;#43; Simply Secure&#34; width=&#34;740&#34; height=&#34;267&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;who-should-apply&#34;&gt;Who should apply?&lt;/h2&gt;
&lt;p&gt;The Usability Lab is focused on projects within OTF’s &lt;a href=&#34;https://www.opentech.fund/about/program&#34;&gt;remit&lt;/a&gt; – i.e., software tools and initiatives that support free expression and information exchange online. If you’re working on a tool that provides encrypted communication, secure file exchange, censorship circumvention, or related features, you should definitely apply. If you&amp;rsquo;re not sure whether your project fits within this framework, please apply, and we will work with you to see if it can be supported under the program.&lt;/p&gt;
&lt;h2 id=&#34;what-kind-of-support-can-projects-receive&#34;&gt;What kind of support can projects receive?&lt;/h2&gt;
&lt;p&gt;Eligible software projects will receive free support from design and/or research professionals to evaluate and improve the quality of their project’s UX. Simply Secure will work with your project to identify the type of support will be most useful and scope a well-defined set of activities that can be accomplished over the period of a few weeks.&lt;/p&gt;
&lt;p&gt;Potential activities include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Expert reviews to identify opportunities for improving the UX&lt;/li&gt;
&lt;li&gt;Usability studies to evaluate a newly-proposed feature&lt;/li&gt;
&lt;li&gt;Design sprints to harmonize the visual look-and-feel between an app and its website&lt;/li&gt;
&lt;li&gt;Program evaluations to examine a team’s process for getting feedback from its users&lt;/li&gt;
&lt;li&gt;Strategy research to help a team identify and understand its user population&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In addition to matching software teams with skilled designers and researchers, Simply Secure will collaborate with engineers and UX professionals to ensure good communication over the course of the project. Simply Secure will also work with the software team after the design or research phase is complete, to make sure they are successful in incorporating the findings into their next development cycle. Finally, Simply Secure will work with software teams to transparently share the results of the collaboration, bringing open-source values to UX work.&lt;/p&gt;
&lt;h2 id=&#34;can-ux-professionals-get-involved&#34;&gt;Can UX professionals get involved?&lt;/h2&gt;
&lt;p&gt;Absolutely! If you are a UX or visual designer or a usability researcher interested in doing applied work on software in this space, please contact us at &lt;a href=&#34;mailto:ux@superbloom.design&#34;&gt;ux@superbloom.design&lt;/a&gt; with a link to your portfolio and/or curriculum vitae. This is a pilot program that we hope will help us connect an extensive network of designers and researchers working on privacy and internet-freedom tools, so we want to hear from you!&lt;/p&gt;
&lt;h2 id=&#34;how-do-i-learn-more&#34;&gt;How do I learn more?&lt;/h2&gt;
&lt;p&gt;Please apply for support &lt;a href=&#34;https://docs.google.com/a/simplysecure.org/forms/d/1uOPAhJLspvP9RydoGDCci2gKkOjzgF6qExBFHbuL-3Q/viewform&#34;&gt;here&lt;/a&gt; (or email us if you are uncomfortable using Google forms) as part of OTF’s &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Usability Lab&lt;/a&gt;, and contact &lt;a href=&#34;mailto:scout@superbloom.design&#34;&gt;scout@superbloom.design&lt;/a&gt; or &lt;a href=&#34;mailto:lindsay@opentechfund.org&#34;&gt;lindsay@opentechfund.org&lt;/a&gt; with questions!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Awkward! QR Scanning &#43; LinkedIn Spam</title>
      <link>https://superbloom.design/learning/blog/qr-linkedin/</link>
      <pubDate>Fri, 12 Feb 2016 15:30:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/qr-linkedin/</guid>
      <description>&lt;p&gt;Messaging with friends and colleagues is rewarding – but sharing contact information is awkward. Many people want to preserve their privacy by carefully controlling who gets their contact information, and choose not to broadcast their email address or phone number via a public Facebook or Twitter profile. Instead, they choose to strategically share their contact info.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s awkward to navigate the social and UX challenges in this sharing. Looking at how WeChat and LinkedIn handle this problem exposes two different kinds of awkwardness: mechanics of sharing and social agreement about what permissions you get as a result.&lt;/p&gt;
&lt;h2 id=&#34;wechat-reciprocity-and-leaving-people-hanging&#34;&gt;WeChat: Reciprocity and Leaving People Hanging&lt;/h2&gt;
&lt;p&gt;Chinese messaging app &lt;a href=&#34;https://web.wechat.com/&#34;&gt;WeChat&lt;/a&gt; has grown to 650 million monthly users. Although posts &lt;a href=&#34;https://citizenlab.org/2015/07/tracking-censorship-on-wechat-public-accounts-platform/&#34;&gt;may be censored&lt;/a&gt;, it&amp;rsquo;s a fixture of the Chinese mobile landscape. During 2016&amp;rsquo;s Lunar New Year, WeChat handled &lt;a href=&#34;http://qz.com/613384/over-8-billion-red-envelopes-were-sent-over-wechat-during-chinese-new-year/&#34;&gt;8 billion&lt;/a&gt; &amp;ldquo;red envelopes&amp;rdquo; of New Year&amp;rsquo;s money through its payment platform. Christina Xu&amp;rsquo;s &lt;a href=&#34;http://www.88-bar.com/2016/01/are-you-scanning-me-or-am-i-scanning-you/&#34;&gt;Am I Scanning You, or Are You Scanning Me&lt;/a&gt; shares the social nuances of scanning a QR code off someone else&amp;rsquo;s phone to exchange contact information. Her writing provides cultural context; for example, URLs are &lt;a href=&#34;https://medium.com/chrysaora-weekly/pictures-of-chinese-people-scanning-qr-codes-a564047ec58f#.x6mx3a1iv&#34;&gt;only &lt;em&gt;slightly&lt;/em&gt; more human-readable than a QR code&lt;/a&gt; for most Chinese people. Her discussion of Chinese norms of courtesy and reciprocity include descriptions of the discomfort that an inexperienced QR-code scanner causes, requiring their scanning partner to &amp;ldquo;hold their phone out steadily for awkward, uncertain seconds, as if waiting slightly too long for a high five.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/WeChatQRScan_hu_e84c5e86b01702f.jpg&#34; alt=&#34;Image of users scanning QR codes.&#34; width=&#34;740&#34; height=&#34;740&#34;&gt;
&lt;br&gt;
&lt;em&gt;Scanning a QR Code to share contact info in WeChat. Photo by &lt;a href=&#34;https://www.instagram.com/p/BAalOnLHyTZ/&#34;&gt;An Xiao Mina&lt;/a&gt;, used by permission.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;With WeChat, the physical mechanics of contact sharing may be awkward or difficult, but it&amp;rsquo;s clear what you have permission to do. After being scanned, you still have a graceful way to not complete the friend request if you choose. However, once the request is accepted, you can exchange messages with them on the platform, and optionally share &lt;a href=&#34;http://blog.wechat.com/tag/moments/&#34;&gt;Moments&lt;/a&gt; with them.&lt;/p&gt;
&lt;h2 id=&#34;linkedin-spam-and-dark-patterns&#34;&gt;LinkedIn: Spam and Dark Patterns&lt;/h2&gt;
&lt;p&gt;Last fall, designer &lt;a href=&#34;http://www.frankchimero.com/writing/&#34;&gt;Frank Chimero&lt;/a&gt; proposed that any New Yorker cartoon could be captioned with &amp;ldquo;Hi, I&amp;rsquo;d like to add you to my professional network on LinkedIn.&amp;rdquo;  These bland and unthreatening words, which the professional networking site has made familiar to many people around the world, have achieved internet memedom.&lt;/p&gt;
&lt;blockquote class=&#34;twitter-tweet&#34; data-lang=&#34;en&#34;&gt;&lt;p lang=&#34;und&#34; dir=&#34;ltr&#34;&gt;&lt;a href=&#34;http://t.co/L2KQhUd8vf&#34;&gt;pic.twitter.com/L2KQhUd8vf&lt;/a&gt;&lt;/p&gt;&amp;mdash; Frank Chimero (@frank_chimero) &lt;a href=&#34;https://twitter.com/frank_chimero/status/646390063283208192&#34;&gt;September 22, 2015&lt;/a&gt;&lt;/blockquote&gt;
&lt;script async src=&#34;//platform.twitter.com/widgets.js&#34; charset=&#34;utf-8&#34;&gt;&lt;/script&gt;
&lt;p&gt;However, these messages are not always desirable, and a specific set of UX decisions has caused LinkedIn to become synonymous with spam. Dan Schlosser describes &lt;a href=&#34;https://medium.com/@danrschlosser/linkedin-dark-patterns-3ae726fe1462#.spk95qyup&#34;&gt;LinkedIn&amp;rsquo;s Dark Patterns&lt;/a&gt; and how they trick people into inviting their contacts to connect on the social network.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/LinkedInScreen_hu_3ee94b3d769ee88f.png&#34; alt=&#34;LinkedIn iPhone app screenshot&#34; width=&#34;740&#34; height=&#34;1314&#34;&gt;
&lt;br&gt;
&lt;em&gt;LinkedIn interrupts users&amp;rsquo; workflow to request access to your contacts.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In contrast to the up-front awkwardness of scanning a QR code, sharing contact information via LinkedIn is downright seamless. The LinkedIn iPhone app screenshot shown above makes &amp;ldquo;continue,&amp;rdquo; which gives ongoing access to your contacts, prominent – and the &amp;ldquo;x&amp;rdquo; to dismiss the request without granting access subtle. Because the app frequently requests access to your contacts, invitations to connect can be unknowingly sent to everyone in your address book, including those you don&amp;rsquo;t consider professional contacts, such as someone you texted with to buy a used sofa.&lt;/p&gt;
&lt;p&gt;With LinkedIn, the social awkwardness around contact sharing comes after the request has been sent. The fact that LinkedIn&amp;rsquo;s aggressive requests reached meme status indicates that these requests are often unintentional. Furthermore, there&amp;rsquo;s no social agreement on how to interact once the LinkedIn connection is made. Message only within the app? Send emails? Endorse for skills? It&amp;rsquo;s not clear what accepting the request means, because it&amp;rsquo;s not clear what the invitation-sender intended.&lt;/p&gt;
&lt;h2 id=&#34;designing-to-share-contacts-and-preserve-privacy&#34;&gt;Designing to Share Contacts and Preserve Privacy&lt;/h2&gt;
&lt;p&gt;Deliberately increasing the awkwardness of sharing contacts would decrease usability and distract users from their primary communication goals. However, &amp;ldquo;friction-free&amp;rdquo; isn&amp;rsquo;t always good; designers should safeguard the intentionality of sharing contacts by making it explicit and noticeable. Instead of happening seamlessly behind the scenes, contact sharing should be something people intentionally and explicitly opt into. I look forward to more experiences like WeChat, where the on-screen UX and social agreements work together – even if they require a little QR awkwardness.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Video Roundup</title>
      <link>https://superbloom.design/learning/blog/video-roundup/</link>
      <pubDate>Fri, 05 Feb 2016 16:40:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/video-roundup/</guid>
      <description>&lt;p&gt;It’s always great to attend security and privacy conferences in person. But in cases where you have to miss an event, online videos of the talks can be a great way to stay current with the ongoing conversation.&lt;/p&gt;
&lt;h3 id=&#34;art-design-and-the-future-of-privacy&#34;&gt;Art, Design, and The Future of Privacy&lt;/h3&gt;
&lt;p&gt;As I promised &lt;a href=&#34;https://superbloom.design/learning/blog/privacy-discussions/&#34;&gt;back in September&lt;/a&gt;, the videos of the event we co-hosted with &lt;a href=&#34;http://dismagazine.com/&#34;&gt;DIS Magazine&lt;/a&gt; at &lt;a href=&#34;http://pioneerworks.org/&#34;&gt;Pioneer Works&lt;/a&gt; are available online. The &lt;a href=&#34;#&#34;&gt;DIS blog&lt;/a&gt; had a great writeup with summaries of the different panels, and you can find transcripts over at &lt;a href=&#34;http://opentranscripts.org/sources/art-design-future-privacy/&#34;&gt;Open Transcripts&lt;/a&gt;. I had a great time participating and came away with some great perspectives.&lt;/p&gt;
&lt;p&gt;Two of my favorite sessions were Sarah Ball talking about unique perspective from her work as a prison librarian and our advisor Cory Doctorow’s barn-burning sendoff at the end.&lt;/p&gt;
&lt;p&gt;
      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/140995268?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;a href=&#34;https://vimeo.com/140995268&#34;&gt;Art, Design, and The Future of Privacy - Ask a Prison Librarian about privacy, technology, and state control&lt;/a&gt; from &lt;a href=&#34;https://vimeo.com/mjoseff&#34;&gt;Matthew Joseff&lt;/a&gt; on &lt;a href=&#34;https://vimeo.com&#34;&gt;Vimeo&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;
      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/141260965?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;a href=&#34;https://vimeo.com/141260965&#34;&gt;Art, Design, and The Future of Privacy - Where to from here?&lt;/a&gt; from &lt;a href=&#34;https://vimeo.com/mjoseff&#34;&gt;Matthew Joseff&lt;/a&gt; on &lt;a href=&#34;https://vimeo&#34;&gt;Vimeo&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Video links:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://vimeo.com/140246342&#34;&gt;Preface&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#&#34;&gt;Welcome – Meredith Whittaker and Marvin Jordan&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://vimeo.com/140995266&#34;&gt;Human rights meets design challenges – Scout Sinclair Brody&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://vimeo.com/140995269&#34;&gt;Digital Privacy IRL: Architecture, public space, and its role in preserving online rights – Noah Biklen and Sarah Gold, moderated by Ame Elliott&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://vimeo.com/140995264&#34;&gt;If you build it they won’t care: Designing privacy-preserving technologies for people with other interests – Tyler Reinhard, Ame Elliott, and Harlo Holmes, moderated by Scout Sinclair Brody&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://vimeo.com/140995268&#34;&gt;Ask a Prison Librarian about privacy, technology, and state control – Cory Doctorow interviewing Sarah Ball&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://vimeo.com/143852704&#34;&gt;No, thank you: Agency, imagination, and possibilities for rejecting world-changing technological innovation – Kate Crawford, Lauren McCarthy and Allison Burtch, moderated by Meredith Whittaker&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://vimeo.com/141260965&#34;&gt;Where to from here? – Cory Doctorow&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;shmoocon-2016&#34;&gt;Shmoocon 2016&lt;/h3&gt;
&lt;p&gt;In an &lt;a href=&#34;https://superbloom.design/learning/blog/shmoocon-talk/&#34;&gt;earlier post&lt;/a&gt;, I described the talk that &lt;a href=&#34;https://superbloom.design/learning/blog/hello-gus/&#34;&gt;Gus&lt;/a&gt; and I gave last month at Shmoocon, and linked to the &lt;a href=&#34;https://superbloom.design/resources/Shmoocon2016-user-are-people-too.pdf&#34;&gt;slides&lt;/a&gt;. Videos for the whole conference are &lt;a href=&#34;https://archive.org/details/shmoocon-2016&#34;&gt;now online&lt;/a&gt;, including one of &lt;a href=&#34;https://archive.org/details/Users_Are_People_Too&#34;&gt;our talk&lt;/a&gt;, which highlights some practical, low-cost things that any software team can do to improve the user-experience design of their project.&lt;/p&gt;
&lt;iframe src=&#34;https://archive.org/embed/Users_Are_People_Too&#34; width=&#34;640&#34; height=&#34;480&#34; frameborder=&#34;0&#34; webkitallowfullscreen=&#34;true&#34; mozallowfullscreen=&#34;true&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;h3 id=&#34;enigma&#34;&gt;Enigma&lt;/h3&gt;
&lt;p&gt;Last week’s USENIX &lt;a href=&#34;https://www.usenix.org/conference/enigma2016&#34;&gt;Enigma Conference&lt;/a&gt; had a great slate of speakers and we’ve heard some positive feedback about it on our Slack channel. Watching via &lt;a href=&#34;https://www.youtube.com/channel/UCIdV7bE97mSPTH1mOi_yUrw&#34;&gt;YouTube&lt;/a&gt;, I particularly enjoyed hearing &lt;a href=&#34;https://www.youtube.com/watch?v=XfFjde0UPbY&#34;&gt;Adrienne Porter Felt&lt;/a&gt; talk about some of her team’s efforts to make security more accessible and useful for their users.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Notes on the O&#39;Reilly Design Conference</title>
      <link>https://superbloom.design/learning/blog/notes-on-oreilly/</link>
      <pubDate>Fri, 29 Jan 2016 16:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/notes-on-oreilly/</guid>
      <description>&lt;p&gt;Last week I went to the O&amp;rsquo;Reilly Design Conference and enjoyed learning about emerging UX trends.  The conference was full of high-quality presentations on UX practice. Here are three of my favorite talks.&lt;/p&gt;
&lt;h2 id=&#34;the-many-minds-of-the-maker&#34;&gt;&lt;a href=&#34;http://conferences.oreilly.com/design/ux-interaction-iot-us/public/schedule/detail/45749&#34;&gt;The Many Minds of the Maker&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Knight-Mozilla Fellow &lt;a href=&#34;https://twitter.com/livlab&#34;&gt;Livia Labate&lt;/a&gt; shared examples of how designers can overcome barriers to learning code. Her experiences from the pragmatic (no you don&amp;rsquo;t need to learn Rails) to the philosophical (to be good at something, be bad at it first) are relevant to people beyond designers. Her willingness to find common ground and avoid stereotypical conflicts between designers and developers is important.&lt;/p&gt;
&lt;h2 id=&#34;measuring-hard-to-measure-things&#34;&gt;&lt;a href=&#34;http://conferences.oreilly.com/design/ux-interaction-iot-us/public/schedule/detail/45525&#34;&gt;Measuring Hard to Measure Things&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;GitHub&amp;rsquo;s &lt;a href=&#34;https://twitter.com/tenaciouscb&#34;&gt;Chrissie Brodigan&lt;/a&gt; shared user research that helped make GitHub more useful to new users. She included interesting examples of empathetic listening to understand what people wanted. I especially appreciated her insights on survey design and A/B testing offers of free, private code repositories at attract people. Pro tip: consider phrases other than &amp;ldquo;free private&amp;rdquo; (e.g., “You’re eligible for a free private repository!”) in an email subject line to avoid spam filters. There were some nice lessons on transparency too, as people took to Twitter to complain about newbies being offered free stuff at the expense of long-time users during a limited-rollout experiment.&lt;/p&gt;
&lt;h2 id=&#34;designing-for-evil&#34;&gt;&lt;a href=&#34;http://conferences.oreilly.com/design/ux-interaction-iot-us/public/schedule/detail/45326&#34;&gt;Designing for Evil&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;https://twitter.com/jorm&#34;&gt;Brandon Harris&lt;/a&gt; described the benefits of a troll persona (or, more generally, an attacker persona) for understanding how users could subvert your software to harm others. This seems particularly relevant as a way for designers without a technical security background to consider how their interfaces are vulnerable to attackers. For example, Scout wrote about &lt;a href=&#34;https://superbloom.design/learning/blog/catching-issues-evolving-interfaces/&#34;&gt;Ashley Madison&amp;rsquo;s leaky interface&lt;/a&gt; and password recovery flow. With no technical knowledge, a designer could imagine someone testing both their partner&amp;rsquo;s and their own email addresses to see what kind of messages are returned.&lt;/p&gt;
&lt;h3 id=&#34;privacy-as-a-social-good&#34;&gt;Privacy as a Social Good&lt;/h3&gt;
&lt;p&gt;The conference had a robust slate of 11 presentations over two days in the Design for Social Good track. Privacy played a role in several presentations, including my own talk on &lt;a href=&#34;http://conferences.oreilly.com/design/ux-interaction-iot-us/public/schedule/detail/45742&#34;&gt;UX for Security&lt;/a&gt;. Two areas that felt particularly rich in other talks were helping people feel mastery over IoT environments and questioning algorithmic decision-making. It was nice to see designers talking seriously about the benefits of privacy, but more work is still needed to expand the conversation. Birds of a Feather groups and hallway conversations on social good felt more anchored to &amp;ldquo;social&amp;rdquo; as in social media rather than societal good.&lt;/p&gt;
&lt;h2 id=&#34;favorite-quotes&#34;&gt;Favorite Quotes&lt;/h2&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/MargaretGouldStewart_hu_b17866f73741b08c.JPG&#34; alt=&#34;Image of a slide from the conference, which says: This is hands down the most time-consuming process and the least efficient thing that I do in my life. [&amp;hellip;] People have wasted years of their lives doing this.&#34; width=&#34;740&#34; height=&#34;740&#34;&gt;

&lt;em&gt;Facebook’s &lt;a href=&#34;https://twitter.com/mags&#34;&gt;Margaret Gould Stewart&lt;/a&gt;, pictured here, encouraged designers to improve enterprise software by offering this quote from a usability study participant. There are many painstaking experiences that waste people’s time, and they have no say in which system they have to use for their jobs.&lt;/em&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Luxurious design has a place in people&amp;rsquo;s lives regardless of who they are.&amp;rdquo; - &lt;a href=&#34;https://twitter.com/danamo&#34;&gt;Dana McKay&lt;/a&gt; &lt;a href=&#34;https://twitter.com/hashtag/oreillydesign&#34;&gt;#oreillydesign&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;I started out as a designer and developer. Now I&amp;rsquo;m just an expectation setter.&amp;rdquo; &lt;a href=&#34;https://twitter.com/mikekuniavsky&#34;&gt;Mike Kuniavsky&lt;/a&gt; &lt;a href=&#34;https://twitter.com/hashtag/oreillydesign&#34;&gt;#oreillydesign&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&#34;for-the-reading-list&#34;&gt;For the Reading List&lt;/h2&gt;
&lt;p&gt;Two of my next UX reads will be &lt;a href=&#34;http://www.oreilly.com/design/free/designing-for-respect.csp&#34;&gt;Designing for Respect: UX Ethics for the Digital Age&lt;/a&gt; by David Hindman an Designing for Dasein by Thomas Wendt.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Users are people too: our talk at Shmoocon</title>
      <link>https://superbloom.design/learning/blog/shmoocon-talk/</link>
      <pubDate>Fri, 22 Jan 2016 19:40:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/shmoocon-talk/</guid>
      <description>&lt;p&gt;Last week &lt;a href=&#34;https://superbloom.design/learning/blog/hello-gus/&#34;&gt;Gus&lt;/a&gt; and I gave a talk at &lt;a href=&#34;http://shmoocon.org/&#34;&gt;Shmoocon&lt;/a&gt; in DC. The focus was on helping technologists who don&amp;rsquo;t have experience in human-centered design processes conduct basic research to improve their existing open-source tools.&lt;/p&gt;
&lt;p&gt;We covered four basic steps that we believe even small or volunteer teams can take:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Agree on your target users&lt;/li&gt;
&lt;li&gt;Do an expert review of your UX to identify (&amp;amp; fix) low-hanging fruit&lt;/li&gt;
&lt;li&gt;Interview real users&lt;/li&gt;
&lt;li&gt;Build a model of your users and their needs&lt;/li&gt;
&lt;li&gt;Smooth the path for user feedback&lt;/li&gt;
&lt;li&gt;Iterate until you get it right&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Overall the talk was well received, with a few choice quotes making their way onto Twitter.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Usability is what allows you to get the job done. Design is what brings you joy.&amp;rdquo; - &lt;a href=&#34;https://twitter.com/scouttle&#34;&gt;@scouttle&lt;/a&gt; on making security tools not suck &lt;a href=&#34;https://twitter.com/hashtag/shmoocon&#34;&gt;#shmoocon&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;Great line by &lt;a href=&#34;https://twitter.com/scouttle&#34;&gt;@scouttle&lt;/a&gt;: &amp;ldquo;&lt;em&gt;Actually&lt;/em&gt; listen to your users! Duct tape your mouth if you have to!&amp;rdquo; (With &lt;a href=&#34;https://twitter.com/gusandrews&#34;&gt;@gusandrews&lt;/a&gt; at &lt;a href=&#34;https://twitter.com/shmoocon&#34;&gt;@shmoocon&lt;/a&gt; Belay It)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;We&amp;rsquo;ve gotten a few queries from folks interested in our slides. If you&amp;rsquo;d like to take a look, you can find a PDF of the deck (including speaker notes) &lt;a href=&#34;https://superbloom.design/resources/Shmoocon2016-user-are-people-too.pdf&#34;&gt;here&lt;/a&gt;! We will also put them in our small-but-growing &lt;a href=&#34;https://github.com/simplysecure/resources&#34;&gt;GitHub repository&lt;/a&gt; of resources.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Signing on to protect the internet</title>
      <link>https://superbloom.design/learning/blog/signing-on-to-protect/</link>
      <pubDate>Fri, 15 Jan 2016 16:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/signing-on-to-protect/</guid>
      <description>&lt;p&gt;This week we joined nearly 200 other organizations, companies, and individuals in signing &lt;a href=&#34;https://securetheinternet.org/&#34;&gt;an open letter&lt;/a&gt; to the world&amp;rsquo;s governments calling for them to protect the integrity of online security, and to not undermine it by weakening, limiting, or backdooring encryption.&lt;/p&gt;
&lt;p&gt;Simply Secure has written before about the importance of this issue before, both &lt;a href=&#34;https://superbloom.design/learning/blog/encryption-not-for-terrorists/&#34;&gt;on our blog&lt;/a&gt; and &lt;a href=&#34;https://www.huffpost.com/entry/wanting-it-bad-enough-won_b_8762322&#34;&gt;elsewhere&lt;/a&gt;. We believe that all people should have access to strong privacy-preserving technologies, and that efforts to compromise encryption in the name of fighting terrorism will only backfire.&lt;/p&gt;
&lt;p&gt;If you agree with us, we encourage you to &lt;a href=&#34;https://securetheinternet.org/#form&#34;&gt;sign the letter&lt;/a&gt; as well.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Calling UX Designers &amp; Usability Researchers</title>
      <link>https://superbloom.design/community/opportunities/suds/</link>
      <pubDate>Fri, 08 Jan 2016 17:00:00 -0500</pubDate>
      <guid>https://superbloom.design/community/opportunities/suds/</guid>
      <description>&lt;p&gt;We are pleased to share that the call for applications to the 2016 Supporting Usability and Design for Security (SUDS) Fellowship &lt;a href=&#34;https://www.opentech.fund/fellowships/suds&#34;&gt;is now live&lt;/a&gt;. The fellowship, which is sponsored by the &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt; and co-administered by Simply Secure, is the next generation of the Secure Usability Fellowship Program (SUFP).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note: the deadline for applications has been extended to March 21st.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;SUDS is designed to pair fellows with host organizations that will offer mentorship and oversight, and Simply Secure is once again acting as one of the host organizations. Read on for more information about the fellowship, as well as for details on what types of projects we specifically are interested in hosting.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/interface-sketching_hu_4af8d4d7c87b4cfc.jpg&#34; alt=&#34;Come design and research with us!&#34; width=&#34;740&#34; height=&#34;493&#34;&gt;

&lt;em&gt;Come design and research with us!&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;fellowship-basics&#34;&gt;Fellowship basics&lt;/h2&gt;
&lt;h3 id=&#34;how-long-is-the-fellowship&#34;&gt;How long is the fellowship?&lt;/h3&gt;
&lt;p&gt;The fellowship term can be 3-6 months (for seasonal fellows) or 12 months (for senior fellows).&lt;/p&gt;
&lt;h3 id=&#34;what-is-included&#34;&gt;What is included?&lt;/h3&gt;
&lt;p&gt;A modest stipend, plus a modest travel stipend for 12-month (senior fellows). See the &lt;a href=&#34;https://www.opentech.fund/fellowships/suds&#34;&gt;SUDS application site&lt;/a&gt; for more details.&lt;/p&gt;
&lt;h3 id=&#34;who-should-apply&#34;&gt;Who should apply?&lt;/h3&gt;
&lt;p&gt;The fellowship is targeted at UX professionals. This means primarily UX designers and usability researchers, although other types of human-centered experts are welcome to apply.&lt;/p&gt;
&lt;h3 id=&#34;what-types-of-projects-does-it-support&#34;&gt;What types of projects does it support?&lt;/h3&gt;
&lt;p&gt;It is designed to fund human-centered design and research work on security and privacy problems that fall under OTF&amp;rsquo;s Internet-freedom &lt;a href=&#34;https://www.opentech.fund/about&#34;&gt;remit&lt;/a&gt;. This might include, for example, research into challenges users of privacy-preserving software currently have, or design explorations to help make such tools more useful and delightful.&lt;/p&gt;
&lt;h3 id=&#34;what-types-of-projects-does-it-not-support&#34;&gt;What types of projects does it not support&lt;/h3&gt;
&lt;p&gt;SUDS does not support software development directly: i.e., it generally won&amp;rsquo;t fund people to write software code. It doesn&amp;rsquo;t support policy research, training, or long-horizon (5+ year) speculative research activities. Finally, it is not general-purpose lab funding; it is designed to support an individual UX professional working full-time for the specified fellowship term.&lt;/p&gt;
&lt;h2 id=&#34;what-simply-secure-is-looking-for&#34;&gt;What Simply Secure is looking for&lt;/h2&gt;
&lt;p&gt;The &lt;a href=&#34;https://www.opentech.fund/fellowships/suds&#34;&gt;SUDS application site&lt;/a&gt; has the list of current hosts and encourages you to suggest additional ones. Different hosts are interested in working on different types of projects. Simply Secure is open to applicants from a variety of UX-oriented backgrounds, and with different levels of experience working with security and/or privacy.&lt;/p&gt;
&lt;p&gt;Our organization is especially focused on supporting high-quality UX design and usability research for secure-communications software (e.g., encrypted chat), and on normalizing UX processes into the open-source development process. But, we&amp;rsquo;re open to other types of projects, too.&lt;/p&gt;
&lt;p&gt;So if you&amp;rsquo;re an experienced UX designer or researcher and are passionate about security and privacy, we want to hear from you. If your idea falls outside of our core focus area or you don&amp;rsquo;t even know exactly what you want to work on, that&amp;rsquo;s ok – we can chat about your interests and work with you to see if there&amp;rsquo;s a project that might fit your background! Just drop us a line at &lt;a href=&#34;mailto:contact@simplysecure.org&#34;&gt;contact@simplysecure.org&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>How to Sketch Storyboards in 10 Minutes: No Drawing Skills Needed</title>
      <link>https://superbloom.design/learning/blog/sketching-storyboards/</link>
      <pubDate>Fri, 01 Jan 2016 14:30:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/sketching-storyboards/</guid>
      <description>&lt;p&gt;Sketching &lt;a href=&#34;https://uxmag.com/articles/storyboarding-in-the-software-design-process&#34;&gt;storyboards&lt;/a&gt; – cartoon-like drawings showing how people use technology – is a way to get more, high-quality ideas for product design. Sketches are useful for taking notes during a discussion and for getting a team on the same page. Fine art drawing is difficult for many, but anyone can master the basics of sketching storyboards – even without drawing skills. You don&amp;rsquo;t need to be artistic, just follow these simple steps.&lt;/p&gt;
&lt;p&gt;This is a quick primer to get started. Thank you to &lt;a href=&#34;http://eleganthack.com/&#34;&gt;Christina Wodtke&lt;/a&gt; and &lt;a href=&#34;http://www.usersknow.com/&#34;&gt;Laura Klein&lt;/a&gt; for inspiring this with their workshop at Lean Startup 2015. All you&amp;rsquo;ll need is a pen, a few sheets of paper, and 10 minutes. If you&amp;rsquo;re unaccustomed to drawing, thicker pens like Sharpie markers can be more expressive than fine-tipped pens like ballpoints.&lt;/p&gt;
&lt;h2 id=&#34;sketching-emotions&#34;&gt;Sketching Emotions&lt;/h2&gt;
&lt;p&gt;One key element that storyboard often convey is emotion. To learn how to quickly sketch a variety of sentiments, start by folding a piece of paper into thirds horizontally, as though folding a letter. Then unfold the paper and fold it in thirds vertically. You should end up with 9 boxes folded into the paper.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/Fold-Paper_hu_fcd009781bff8c04.png&#34; alt=&#34;Images of folded paper.&#34; width=&#34;740&#34; height=&#34;313&#34;&gt;
&lt;br&gt;
&lt;em&gt;Fold a piece of paper into thirds vertically (left). Then unfold and fold into thirds horizontally (right).&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Draw a circle in each of the nine squares, then add two dots to the middle of each circle. These dots are the eyes. Eyes go in the middle of the face, lower than you might think.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/FacesAndEyes_hu_eb36e5c10f985bd5.png&#34; alt=&#34;Images of circles and circles with eyes.&#34; width=&#34;740&#34; height=&#34;315&#34;&gt;
&lt;br&gt;
&lt;em&gt;Draw a circle in each box (left). Two dots for eyes go in the middle of each circle (right).&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Now it&amp;rsquo;s time to add mouths and eyebrows for expression. Draw a smile on each face in the top row, a straight line on each face in the middle row, and a frown on each face in the bottom row. Draw eyebrows tilted up on every face in the left column, no eyebrows in the middle column, and eyebrows pointed down on every face in the right column.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/SimpleFaces_hu_b2917447d7d9f57d.png&#34; alt=&#34;Images of simple expressive faces.&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;br&gt;
&lt;em&gt;Simple mouths and eyebrows capture emotions.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Congratulations, you&amp;rsquo;ve done it! You have 9 different facial expression capturing a range of emotions.&lt;/p&gt;
&lt;h2 id=&#34;from-stick-figures-to-star-people-and-box-people&#34;&gt;From Stick Figures to Star People and Box People&lt;/h2&gt;
&lt;p&gt;Some of us learn to draw stick figures in grade school, and don&amp;rsquo;t practice beyond the game of Hangman. But with a few minutes of practice with these new forms, you&amp;rsquo;ll be up and running with more expressive figures.&lt;/p&gt;
&lt;p&gt;Star people are simple figures whose head, arms, and legs make a star shape. Take a new sheet of paper and draw a star for reference. Underneath it, practice drawing the &amp;ldquo;body&amp;rdquo; of the star, which will be the arms and legs of the figure. To do this, imagine tracing around the perimeter of a star. Don&amp;rsquo;t worry about the fifth point/head of the star yet. After you&amp;rsquo;ve practiced a few times, draw 10 star people with heads. If you like, experiment with drawing different groups of figures, such as figures of different sizes together.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/StarPeople_hu_3122f968bcf939c1.png&#34; alt=&#34;Left column: practice drawing the perimeter of a star as the body of a figure. Right column: 10 star people figures and some groupings of figures.&#34; width=&#34;740&#34; height=&#34;567&#34;&gt;
&lt;br&gt;
&lt;em&gt;Left column: practice drawing the perimeter of a star as the body of a figure. Right column: 10 star people figures and some groupings of figures.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Box people are an alternative to star people. I personally find star people easier, but box people&amp;rsquo;s arms and legs are easier to position. Practice drawing a page of box people. At the end, you&amp;rsquo;ll probably have a sense of which are easier for you to draw.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/BoxPeople_hu_eef71c827826471f.jpg&#34; alt=&#34;Image of sketched box people.&#34; width=&#34;740&#34; height=&#34;555&#34;&gt;
&lt;br&gt;
&lt;em&gt;Practicing sketching box people.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Don&amp;rsquo;t worry if the sketches are messy and the lines aren&amp;rsquo;t square. Just keep practicing.&lt;/p&gt;
&lt;h2 id=&#34;putting-it-all-together&#34;&gt;Putting It All Together&lt;/h2&gt;
&lt;p&gt;Sketching a storyboard is a way to be specific about the problem you&amp;rsquo;re trying to solve. Here are some examples of star people with faces that tell two simple stories about the emotions people feel when using technology.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/Storyboards_hu_155766ef8610254b.png&#34; alt=&#34;Image of example sketches.&#34; width=&#34;740&#34; height=&#34;392&#34;&gt;
&lt;br&gt;
&lt;em&gt;Example sketches of star people feeling emotions while using technology.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;You can see how these brief sketches convey the emotional experience of using technology. Storyboards like these are useful at the beginning of the product development cycle because they help get a team on the same page about what problem they are solving and how they deliver positive feelings. Storyboarding is also a good way to get unstuck if you&amp;rsquo;re not sure where to begin or how to prioritize possible changes. Taking a few minutes to sketch a handful of storyboard panels can uncover new insights into how people use technology.&lt;/p&gt;
&lt;h2 id=&#34;additional-resources&#34;&gt;Additional Resources&lt;/h2&gt;
&lt;p&gt;Christina Wodtke&amp;rsquo;s &lt;a href=&#34;http://eleganthack.com/a-library-of-visual-thinking/&#34;&gt;Library of Visual Thinking&lt;/a&gt; includes lots of resources for digging deeper into working visually. If you&amp;rsquo;re unsure what to illustrate with these figures, read Laura Klein on &lt;a href=&#34;http://www.usersknow.com/blog/2015/11/28/predictive-personas&#34;&gt;Predictive Personas&lt;/a&gt;. Simple sketches like these are a nice way to illustrate predictive personas, far better and more expressive than generic stock photography. Happy sketching.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Some Of Our 2015 Favorites</title>
      <link>https://superbloom.design/learning/blog/2105-favorite-resources/</link>
      <pubDate>Thu, 24 Dec 2015 19:30:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/2105-favorite-resources/</guid>
      <description>&lt;p&gt;2015 was our first full year in operation, and we’ve come a long way! Looking back at the past twelve months, here are some resources that we’ve found to be particularly useful (or entertaining). Let us know your favorites on &lt;a href=&#34;https://twitter.com/simplysecureorg&#34;&gt;Twitter&lt;/a&gt;!&lt;/p&gt;
&lt;h2 id=&#34;ames-picks&#34;&gt;Ame’s picks&lt;/h2&gt;
&lt;p&gt;Thinking back on 2015, I’m really glad to be part of Simply Secure and for the opportunity to be an evangelist for design. I’m thankful for resources that make design easier.&lt;/p&gt;
&lt;h3 id=&#34;the-noun-project&#34;&gt;The Noun Project&lt;/h3&gt;
&lt;p&gt;&lt;a href=&#34;https://thenounproject.com/&#34;&gt;The Noun Project&lt;/a&gt; is a great resource for icons. They’re useful for more than interfaces – I’ve included them in presentations and posters too. With low pricing for individual icons or subscriptions, as well as options for &lt;a href=&#34;https://help.thenounproject.com/hc/en-us/sections/200137528-Icon-Credit-Requirements&#34;&gt;free attributed use&lt;/a&gt;, they’re my number one resource for 2015. Easy to search, easy to download, or drag-and-drop directly from the desktop app into Keynote.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/snowflake_hu_a3e8446b58d86b06.png&#34; alt=&#34;Screenshot of the Noun Project&amp;rsquo;s image download interface.&#34; width=&#34;740&#34; height=&#34;532&#34;&gt;
&lt;/p&gt;
&lt;p&gt;With subscription or purchase, the images are free to modify. Here are some of my favorite modifications from this year:&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/NounProjectIcons_hu_70772948bf6d93b7.png&#34; alt=&#34;Noun project sample icons&#34; width=&#34;740&#34; height=&#34;368&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;flickr&#34;&gt;Flickr&lt;/h3&gt;
&lt;p&gt;Flickr has a nice way &lt;a href=&#34;https://www.flickr.com/creativecommons/&#34;&gt;to search images licensed&lt;/a&gt; under &lt;a href=&#34;http://creativecommons.org/&#34;&gt;Creative Commons&lt;/a&gt;, which I use to &lt;a href=&#34;https://superbloom.design/learning/resources/lessons-from-architecture-school-2/&#34;&gt;illustrate presentations and blog posts&lt;/a&gt;, like the Lessons from Architecture School series. (Scout is also a fan of Google’s advanced image search options; after doing a search, choose “Search Tools &amp;gt; Usage Rights&amp;quot;.)&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/Flickr_hu_5a65c6c3863bd8b0.png&#34; alt=&#34;Screenshot of Flickr interface.&#34; width=&#34;740&#34; height=&#34;488&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;invision-blog&#34;&gt;InVision Blog&lt;/h3&gt;
&lt;p&gt;InVision makes collaboration software great for teams working remotely on UX projects. The &lt;a href=&#34;http://blog.invisionapp.com/&#34;&gt;InVision Blog&lt;/a&gt; is a consistent source of high-quality, accessible design writing. Here are three recent posts I’ve found helpful:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;http://blog.invisionapp.com/designing-for-android/&#34;&gt;Designing for Android&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://blog.invisionapp.com/top-3-tips-from-our-webinar-the-7-most-common-usability-issues/&#34;&gt;Top 3 Tips from our Webinar “The 7 Most Common Usability Issues&amp;quot;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.invisionapp.com/inside-design/dlf-book-podcast-recommendations/&#34;&gt;A Comprehensive Reading List By and For Designers&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;scouts-picks&#34;&gt;Scout’s picks&lt;/h2&gt;
&lt;p&gt;This year was one of tremendous growth for us as an organization; we went from being a group of one to having other staff members and receiving official nonprofit status from the IRS. Here are some of the online resources I’ve found useful and entertaining, either in my own work or as a support to others.&lt;/p&gt;
&lt;h3 id=&#34;nngroup&#34;&gt;NNGroup&lt;/h3&gt;
&lt;p&gt;&lt;a href=&#34;https://www.nngroup.com/&#34;&gt;The Nielsen Norman Group&lt;/a&gt; has been a mainstay in the user-experience research space for almost twenty years. They have a great collection of free &lt;a href=&#34;https://www.nngroup.com/articles/&#34;&gt;articles&lt;/a&gt; on all sorts of relevant topics, from &lt;a href=&#34;https://www.nngroup.com/articles/which-ux-research-methods/&#34;&gt;foundational user-research pieces&lt;/a&gt; to gems like &lt;a href=&#34;https://www.nngroup.com/articles/ux-learn-in-restaurants&#34;&gt;this recent comparison&lt;/a&gt; of UX design and working in restaurants. They are one of the first places I encourage new researchers to check out while exploring the field.&lt;/p&gt;
&lt;h3 id=&#34;swift-on-security&#34;&gt;Swift on Security&lt;/h3&gt;
&lt;p&gt;Lest any of us in security take ourselves too seriously, it’s always good to have someone like &lt;a href=&#34;https://twitter.com/SwiftOnSecurity&#34;&gt;Swift on Security&lt;/a&gt; in our Twitter feeds.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/swift-twitter_hu_f16473f35d8c7ac1.png&#34; alt=&#34;Screenshot of @SwiftOnSecurity&amp;rsquo;s Twitter page.&#34; width=&#34;740&#34; height=&#34;983&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;nonprofit-pointers&#34;&gt;Nonprofit pointers&lt;/h3&gt;
&lt;p&gt;Setting up a new tech nonprofit in the US isn’t always easy, especially given the IRS’s &lt;a href=&#34;https://www.techdirt.com/articles/20140701/11470827745/irs-rejects-non-profit-status-open-source-organization-because-private-companies-might-use-software.shtml&#34;&gt;recent take on open-source&lt;/a&gt;. My #1 bit of advice is to get good lawyers helping you, if your organization can afford it (shout out to the &lt;a href=&#34;http://www.neolawgroup.com/&#34;&gt;NEO Law Group&lt;/a&gt; in San Francisco), or a good law clinic if you can’t (for example, check out OTF’s new &lt;a href=&#34;https://www.opentech.fund/lab/legal-lab&#34;&gt;Legal Lab&lt;/a&gt;). But I also have found resources like &lt;a href=&#34;http://www.guidestar.org/&#34;&gt;Guidestar&lt;/a&gt; and &lt;a href=&#34;http://www.nolo.com/legal-encyclopedia/nonprofit-basics-29948.html&#34;&gt;Nolo&lt;/a&gt; to be tremendously helpful in understanding the landscape and requirements of organizations like ours.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Straight Talk: New Yorkers on Privacy</title>
      <link>https://superbloom.design/learning/blog/straight-talk/</link>
      <pubDate>Fri, 18 Dec 2015 18:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/straight-talk/</guid>
      <description>&lt;p&gt;We spent last week in New York doing field work on mobile messaging. Thank you to the &lt;a href=&#34;https://www.labs.robinhood.org/dig&#34;&gt;Design Insights Group&lt;/a&gt; at Blue Ridge Labs for connecting us to such great participants. Many thanks also to the research participants themselves, who gave us permission to share their stories and images.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/NYC-EnvironmentSidebySide_hu_bf24dab02c577328.png&#34; alt=&#34;NYC background images&#34; width=&#34;740&#34; height=&#34;274&#34;&gt;

&lt;em&gt;Apartment building in Brownsville (left); jewelry store + phone center in Harlem (right).&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;real-new-yorkers-with-real-stories&#34;&gt;Real New Yorkers with Real Stories&lt;/h2&gt;
&lt;p&gt;We talked with twelve New Yorkers from across the city, meeting with people in libraries, offices, restaurants, and homes. We spent an hour listening to each participant talk about how they currently message, their privacy concerns and security practices, and their opinions on secure messaging. These conversations provided insights into how to design secure communication tools for a mass audience.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/NYC-PeopleSideBySide_hu_9e6bbc5ff090b934.png&#34; alt=&#34;NYC interview images&#34; width=&#34;740&#34; height=&#34;332&#34;&gt;

&lt;em&gt;Learning how real New Yorkers use mobile phones by interviewing them.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Most participants were Android users, with one iPhone user and one person declining to say. All of them used multiple messaging apps on the same phone, with the native messaging app, &lt;a href=&#34;https://www.whatsapp.com/&#34;&gt;WhatsApp&lt;/a&gt;, &lt;a href=&#34;http://www.kik.com/&#34;&gt;Kik&lt;/a&gt;, and &lt;a href=&#34;https://www.messenger.com/&#34;&gt;Facebook Messenger&lt;/a&gt; the most commonly used, along with direct messages in &lt;a href=&#34;https://support.twitter.com/articles/14606&#34;&gt;Twitter&lt;/a&gt; or &lt;a href=&#34;https://help.instagram.com/400205900081854/&#34;&gt;Instagram&lt;/a&gt;. Many people have developed a hierarchy based on how well they know someone to determine how they message them: letting someone know your Instagram handle is less intimate than giving them your phone number.&lt;/p&gt;
&lt;h2 id=&#34;emoji-for-fun-and-security&#34;&gt;Emoji for Fun and Security&lt;/h2&gt;
&lt;p&gt;Going out into the field is always surprising. One unexpected insight during this research was participants’ use of emoji as a privacy-preserving strategy. Emoji were an important part of messaging for many people, with apps like &lt;a href=&#34;https://bitmoji.com/&#34;&gt;Bitmoji&lt;/a&gt; and Expresser used to add graphics across multiple platforms. One teenaged participant even used emoji in place of names in her contact list; the people with emoji were the most intimate or frequently messaged.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/NYC-PhonesSidebySide_hu_8ad039a166119a63.png&#34; alt=&#34;NYC phone images&#34; width=&#34;740&#34; height=&#34;425&#34;&gt;

&lt;em&gt;Left to right: Bitmoji, Expresser, and a participant’s contacts list.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Using emoji to hide the names of contacts can be an effective strategy if, like these participants, your main privacy concerns are related to other people getting physical access to your device. Shoulder surfing, people rifling through your phone, and screenshotting were some of participants’ top worries. Concealing the name through emoji makes it more difficult to identify the contact at a glance.&lt;/p&gt;
&lt;p&gt;Stay tuned for more research findings and design directions from this work.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Maximizing Meaning in Empty States</title>
      <link>https://superbloom.design/learning/blog/maximizing-empty-states/</link>
      <pubDate>Fri, 11 Dec 2015 18:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/maximizing-empty-states/</guid>
      <description>&lt;p&gt;It can be hard to communicate about security-related features with users who aren&#39;t already security experts. From word choice to the level of detail included, it&#39;s easy to overwhelm people with information, leave them scared, or bore them to indifference. &lt;/p&gt;
&lt;p&gt;For many applications, one major challenge is finding the right place to communicate. Empty states – screens in your app where there is no actual content to display – are a great opportunity for this communication, in part because they frequently occur when the user is first starting out. Here&#39;s a &lt;a href=&#34;http://emptystat.es/&#34;&gt; sampling&lt;/a&gt; of empty states from a variety of platforms, and a &lt;a href=&#34;http://blog.invisionapp.com/why-empty-states-deserve-more-design-time/&#34;&gt;piece&lt;/a&gt; on designing great empty states in general.&lt;/p&gt;
&lt;h2&gt;Incognito Mode vs. Private Browsing: Scannability Wins&lt;/h2&gt;
&lt;p&gt;As a mini case study of how empty states can be used to communicate about security, consider the initial pages for Incognito Mode in Chrome and Private Browsing in Firefox.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/chrome-incognito_hu_47ef3d7fc574f84b.png&#34; alt=&#34;Incognito mode empty state, Chrome version 47.0.2526.80&#34; width=&#34;740&#34; height=&#34;271&#34;&gt;

&lt;em&gt;Incognito mode empty state, Chrome version 47.0.2526.80&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Both take advantage of the empty state associated with a new browser window to communicate both the benefits and limitations of the feature. They both share that their respective features prevent some data (like cookies and search history) from being recorded by the browser, but preserve other types of data (like downloaded files and bookmarks). Both screens also communicate that the features don&#39;t protect the user from surveillance by ISPs or employers providing internet service.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/firefox-private-browsing_hu_fce3e4f8465d4784.png&#34; alt=&#34;Private Browsing empty state, Firefox 42.0&#34; width=&#34;740&#34; height=&#34;323&#34;&gt;

&lt;em&gt;Private Browsing empty state, Firefox 42.0&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In comparing the two, though, the text in Firefox&#39;s empty state stands out as being more scannable: it&#39;s easier to extract essential information from it without having to read it carefully. Specifically, the use of lists, bold subheadings, and icon bullets helps the reader 1) learn that Private Browsing doesn&#39;t keep everything private, and 2) extract details on what is and isn&#39;t retained while using Private Browsing.&lt;/p&gt;
&lt;p&gt;When you&#39;re setting out to communicate complicated concepts to your users, working to make your textual content more scannable is one quick and easy step you can take. Reflecting the meaning of the text in its structure – e.g., dividing benefits and limitations into two bulleted lists – reduces the burden on the user in trying to understand your material. And, this structure helps you resist the temptation to make your writing complex in an attempt to be precise. It&#39;s better to be simple in the main interface and provide a link to more information for users who want to learn more.&lt;/p&gt;
&lt;p&gt;For other ideas on how to make your interface text more scannable, check out The Nielsen Norman Group&#39;s &lt;a href=&#34;http://www.nngroup.com/articles/how-users-read-on-the-web/&#34;&gt;handy list of tips&lt;/a&gt; and illustrative examples.&lt;/p&gt;
&lt;h2&gt;There&#39;s Always Room for Improvement&lt;/h2&gt;
&lt;p&gt;Although the Firefox Private Browsing empty state wins out over Chrome&#39;s Incognito Mode as being more scannable, its design could still be refined to help new users understand the feature better.&lt;/p&gt;
&lt;p&gt;For example, the green checkmarks under &#34;Not Saved&#34; convey confidence, but the caution symbols (which are affectionately referred to as &#34;party hats&#34; on the Simply Secure Slack channel) can be ambiguous. If the point is to help users understand that saved downloads and bookmarks can be problematic, wouldn&#39;t something along the lines of a red X be more clear?&lt;/p&gt;
&lt;p&gt;This brings up an interesting conflict between the positive and negative words and their corresponding icons: the negative heading (&#34;Not Saved&#34;) has positive icons (green checks) and vice versa. Perhaps alternative symbols would help, like smiling and frowning faces? Perhaps a term other than &#34;saved&#34; would be helpful: &#34;discarded&#34;, or &#34;forgotten&#34; and &#34;remembered&#34;? Alternative terminology could also prevent &#34;saved&#34; as being understood to mean &#34;kept safe or protected&#34;, an interpretation that non-native English speakers might make.&lt;/p&gt;
&lt;p&gt;Similarly, the &#34;Tracking Protection&#34; box in Firefox poses potential challenges to unfamiliar users. The rectangle labeled &#34;ON&#34; looks like a button or toggle from a mobile interface, but is in fact not actionable. The tutorial helps the user understand what the feature does (it block &#34;parts of the page that may track your browsing activity&#34;) and goes out of its way to explain how to turn the feature off, but doesn&#39;t offer users insight into how parts of a page might track them, what kinds of content might be blocked, or the implicit tradeoffs they might be making when choosing whether to use the feature (i.e., they might not be tracked, but parts of webpages might stop working).&lt;/p&gt;
&lt;h2&gt;Opinions are Opinions; Data is Data&lt;/h2&gt;
&lt;p&gt;All this illustrates that there&#39;s always room for improvement in any user experience. And, it also shows that there can be a lot of hard decisions to make when trying to communicate with users: two people could probably argue endlessly about whether &#34;saved&#34; and &#34;not saved&#34; is better or worse than &#34;remembered&#34; and &#34;forgotten&#34;.&lt;/p&gt;
&lt;p&gt;That&#39;s why it&#39;s important for a software team to not just rely on their own intuition and inclinations in making decisions about user experiences. Whenever possible, products benefit when teams gather data from real users – whether it&#39;s a broad quantitative sampling or a small focus group in all its qualitative glory. Quick, scrappy, and informal studies can offer just as might food for thought as large, well-organized ones – and are easier for small teams to perform on the fly.&lt;/p&gt;
&lt;p&gt;If you&#39;re interested in improving how your project communicates with users about its security features, or want help structuring a study to get insight from real users, &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;get in touch&lt;/a&gt;. And, please spread the word to your favorite open-source projects and encourage them to apply for &lt;a href=&#34;https://superbloom.design/learning/blog/apply-for-help&#34;&gt;free help!&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Donate to Simply Secure</title>
      <link>https://superbloom.design/learning/blog/donate15/</link>
      <pubDate>Fri, 04 Dec 2015 16:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/donate15/</guid>
      <description>&lt;p&gt;Simply Secure is a non-profit organization, and we rely on donations to be
successful in our work of getting privacy-preserving software in the hands of
more people.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/donation-gifts_hu_a3f38b465af36692.png&#34; alt=&#34;Image of wrapped gifts&#34; width=&#34;740&#34; height=&#34;652&#34;&gt;
&lt;/p&gt;
&lt;p&gt;To celebrate our official recognition by the IRS as a 501(c)3 organization –
which means donations are tax-deductible in the US – we have added a &lt;a href=&#34;https://superbloom.design/donate/&#34;&gt;donations page&lt;/a&gt; to our website. As
you are contemplating your charitable giving at the end of the year, please keep
us in mind. Even small amounts will help us demonstrate that there is broad
support for improving the user experience of secure software, so we welcome your
contribution, whether it is $1, $10, or $1,000.&lt;/p&gt;
&lt;p&gt;And, don&amp;rsquo;t forget to drop us a line at &lt;a href=&#34;mailto:contact@simplysecure.org&#34;&gt;contact@simplysecure.org&lt;/a&gt; and let us
know what open-source software projects you would like to see get support
polishing their user experience. We will reach out to the teams you suggest and
see if we can lend them free help, either through our &lt;a href=&#34;https://superbloom.design/learning/blog/apply-for-help/&#34;&gt;recently-announced&lt;/a&gt;
collaboration with the Open Technology Fund or as part of another initiative.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Apply now for design and usability help</title>
      <link>https://superbloom.design/learning/blog/apply-for-help/</link>
      <pubDate>Fri, 27 Nov 2015 18:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/apply-for-help/</guid>
      <description>&lt;p&gt;We are pleased to announce a new collaboration with the &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Technology Fund&lt;/a&gt; as part of their &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Usability Lab&lt;/a&gt; project. This exciting initiative will allow open-source software projects to &lt;a href=&#34;https://docs.google.com/a/simplysecure.org/forms/d/1uOPAhJLspvP9RydoGDCci2gKkOjzgF6qExBFHbuL-3Q/viewform&#34;&gt;apply&lt;/a&gt; for free assistance with user-experience (UX) design as well as usability research. To our knowledge, this is the first program to offer support of this kind.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/otf-simsec_hu_987626dd4e7f2c4d.png&#34; alt=&#34;Open Technology Fund &amp;#43; Simply Secure&#34; width=&#34;740&#34; height=&#34;267&#34;&gt;
&lt;/p&gt;
&lt;h2 id=&#34;who-should-apply&#34;&gt;Who should apply?&lt;/h2&gt;
&lt;p&gt;The Usability Lab is focused on projects within OTF’s &lt;a href=&#34;https://www.opentech.fund/about/program&#34;&gt;remit&lt;/a&gt; – i.e., software tools and initiatives that support free expression and information exchange online. If you’re working on a tool that provides encrypted communication, secure file exchange, censorship circumvention, or related features, you should definitely apply. If you&amp;rsquo;re not sure whether your project fits within this framework, please apply, and we will work with you to see if it can be supported under the program.&lt;/p&gt;
&lt;h2 id=&#34;what-kind-of-support-can-projects-receive&#34;&gt;What kind of support can projects receive?&lt;/h2&gt;
&lt;p&gt;Eligible software projects will receive free support from design and/or research professionals to evaluate and improve the quality of their project’s UX. Simply Secure will work with your project to identify the type of support will be most useful and scope a well-defined set of activities that can be accomplished over the period of a few weeks.&lt;/p&gt;
&lt;p&gt;Potential activities include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Expert reviews to identify opportunities for improving the UX&lt;/li&gt;
&lt;li&gt;Usability studies to evaluate a newly-proposed feature&lt;/li&gt;
&lt;li&gt;Design sprints to harmonize the visual look-and-feel between an app and its website&lt;/li&gt;
&lt;li&gt;Program evaluations to examine a team’s process for getting feedback from its users&lt;/li&gt;
&lt;li&gt;Strategy research to help a team identify and understand its user population&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In addition to matching software teams with skilled designers and researchers, Simply Secure will collaborate with engineers and UX professionals to ensure good communication over the course of the project. Simply Secure will also work with the software team after the design or research phase is complete, to make sure they are successful in incorporating the findings into their next development cycle. Finally, Simply Secure will work with software teams to transparently share the results of the collaboration, bringing open-source values to UX work.&lt;/p&gt;
&lt;h2 id=&#34;can-ux-professionals-get-involved&#34;&gt;Can UX professionals get involved?&lt;/h2&gt;
&lt;p&gt;Absolutely! If you are a UX or visual designer or a usability researcher interested in doing applied work on software in this space, please contact us at &lt;a href=&#34;mailto:ux@superbloom.design&#34;&gt;ux@superbloom.design&lt;/a&gt; with a link to your portfolio and/or curriculum vitae. This is a pilot program that we hope will help us connect an extensive network of designers and researchers working on privacy and internet-freedom tools, so we want to hear from you!&lt;/p&gt;
&lt;h2 id=&#34;how-do-i-learn-more&#34;&gt;How do I learn more?&lt;/h2&gt;
&lt;p&gt;Please apply for support &lt;a href=&#34;https://docs.google.com/a/simplysecure.org/forms/d/1uOPAhJLspvP9RydoGDCci2gKkOjzgF6qExBFHbuL-3Q/viewform&#34;&gt;here&lt;/a&gt; (or email us if you are uncomfortable using Google forms) as part of OTF’s &lt;a href=&#34;https://www.opentech.fund/labs/sua-lab/&#34;&gt;Usability Lab&lt;/a&gt;, and contact &lt;a href=&#34;mailto:scout@superbloom.design&#34;&gt;scout@superbloom.design&lt;/a&gt; or &lt;a href=&#34;mailto:lindsay@opentechfund.org&#34;&gt;lindsay@opentechfund.org&lt;/a&gt; with questions!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Encryption is not for terrorists</title>
      <link>https://superbloom.design/learning/blog/encryption-not-for-terrorists/</link>
      <pubDate>Fri, 20 Nov 2015 15:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/encryption-not-for-terrorists/</guid>
      <description>&lt;p&gt;Recent attacks by&lt;a href=&#34;https://www.vox.com/2015/11/14/9734894/daesh-isis-isil&#34;&gt;Daesh&lt;/a&gt; in Turkey, Egypt, Lebanon, and Paris have fanned the flames of an ongoing debate about software that is resistant to surveillance. It seems that some participants in that debate are trying to use these attacks as an excuse to drum up fear around end-to-end encryption. They argue that these events tell us that the general citizenry shouldn’t have access to strong privacy-preserving tools.&lt;/p&gt;
&lt;p&gt;A lot of people are saying a lot of &lt;a href=&#34;http://www.theguardian.com/commentisfree/2015/nov/17/intelligence-agencies-pounce-paris-attacks-pursue-spy-agenda&#34;&gt;smart things&lt;/a&gt; on the subject, but I want to briefly outline a couple ways in which this call for limiting encryption is problematic.&lt;/p&gt;
&lt;h2 id=&#34;this-instance&#34;&gt;This instance&lt;/h2&gt;
&lt;p&gt;There appears to be no actual evidence that encryption software was used to plan recent attacks, much less that such software thwarted intelligence agents who would otherwise have been able to prevent the tragedies. Indeed, &lt;em&gt;Le Monde&lt;/em&gt; &lt;a href=&#34;http://www.lemonde.fr/attaques-a-paris/article/2015/11/18/le-telephone-portable-d-un-membre-du-commando-trouve-pres-du-bataclan-a-permis-de-remonter-a-alfortville_4812515_4809495.html&#34;&gt;reports&lt;/a&gt; that the cell phone found in a trash can near the Bataclan in Paris contained “a detailed map of the concert hall in addition to an SMS message saying, according to information gathered by &lt;em&gt;Le Monde&lt;/em&gt;, ‘Let’s go and get this started.’” [^1] Not an encrypted chat program, or an encrypted email – an old-fashioned, easily-intercepted text message.&lt;/p&gt;
&lt;p&gt;This lack of evidence did not prevent “European officials” from asserting that encryption tools had a role in the Parisian attacks – assertions that were &lt;a href=&#34;http://techcrunch.com/2015/11/17/the-blame-game/&#34;&gt;published and silently removed&lt;/a&gt; in an article by the New York Times.&lt;/p&gt;
&lt;p&gt;We all have an interest in seeing terrorists’ attacks prevented, and we can all appreciate that finding and monitoring the activities of malicious actors is hard work. It’s also understandable if officials are trying to keep details of the investigation (like what communication tools the terrorists used) quiet. But fear-mongering about encryption – whether it’s truly disingenuous or simply unsupported – doesn’t make the public feel better when attacks occur, nor does it mollify people’s concerns about the massive surveillance systems that have been put in place to thwart such plots.&lt;/p&gt;
&lt;p&gt;Indeed, false claims of encryption hampering intelligence efforts only highlight the ineffectiveness of mass surveillance. The cynics among us must wonder, “Why are they complaining about encryption, when they can’t even thwart attacks that are planned in the clear?”&lt;/p&gt;
&lt;h2 id=&#34;the-bigger-picture&#34;&gt;The bigger picture&lt;/h2&gt;
&lt;p&gt;Even if there is evidence that the terrorists who planned these attacks were using high-quality encryption tools (and not just ones that are likely insecure &lt;a href=&#34;http://motherboard.vice.com/read/encryption-app-telegram-probably-isnt-as-secure-for-terrorists-as-isis-thinks&#34;&gt;in practice&lt;/a&gt;), that doesn’t mean that law-abiding citizens should be prevented from doing so. There are many imperfect analogies we can use to argue this point: terrorists use fast cars, paper shredders, cell phones, and (for countries with minimal gun-control laws) terrorists use firearms. When push comes to shove, the fact that a technology with substantial lawful use is sometimes used by malicious people – and even when this use of technology makes it more difficult for law enforcement to stop the “bad guys” – does not justify efforts to ban it.&lt;/p&gt;
&lt;p&gt;This is especially true when it comes to things like encryption. We live in a world where the internet is integrated in every intimate corner of our lives – from our love letters to our financial and health records – and numerous criminal factions stand to profit from gathering our personal data. The average person’s integrity and even safety depends on keeping their private information private. Some policy-makers would have us believe that it’s possible to build a “backdoor” into encryption so law enforcement can peek into our private lives when they have probable cause, but the technological reality doesn’t line up. Backdoors can’t reliably be marked “good guys only”; when one is introduced, it will inevitably be used by malicious actors as well. Encryption tools that only work some of the time aren’t proper encryption tools at all. All sorts of organizations and people – from Google and Facebook to the EFF and The Tor Project, from the CISO of Yahoo to the co-inventor of the RSA algorithm – &lt;a href=&#34;https://static.newamerica.org/attachments/3138--113/Encryption_Letter_to_Obama_final_051915.pdf&#34;&gt;agree&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;the-future-of-this-debate&#34;&gt;The future of this debate&lt;/h2&gt;
&lt;p&gt;Simply Secure believes that all people deserve access to privacy-preserving communication tools, including end-to-end encryption. We are working to support software developers in their efforts to make these tools more user-friendly, and to help tool-makers express the value of their software to non-experts.&lt;/p&gt;
&lt;p&gt;The debate on who should have access to these tools will only intensify as they become more popular. If the pundits arguing in favor of backdoors – or, more absurdly, in favor of outright bans on certain encryption algorithms – have their way, dedicated terrorists won’t be thwarted. They’ll still find ways to communicate out of the eyes of law enforcement. But law-abiding citizens will have lost the ability to protect their data in the process.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;[^1] My own translation; &lt;a href=&#34;http://www.lemonde.fr/attaques-a-paris/article/2015/11/18/le-telephone-portable-d-un-membre-du-commando-trouve-pres-du-bataclan-a-permis-de-remonter-a-alfortville_4812515_4809495.html&#34;&gt;original text&lt;/a&gt;: &amp;ldquo;un plan détaillé de la salle de concert ainsi qu’un message SMS disant, selon des informations du Monde, « On est parti on commence ».&amp;rdquo;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Why Open-Source Projects Need Style Guides</title>
      <link>https://superbloom.design/learning/blog/style-guide/</link>
      <pubDate>Fri, 13 Nov 2015 15:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/style-guide/</guid>
      <description>&lt;p&gt;&lt;em&gt;Style guides&lt;/em&gt; specify the look and feel of how a company or team communicates with the outside word. &lt;a href=&#34;http://styleguides.io/examples.html&#34;&gt;Styleguides.io&lt;/a&gt; collects examples of website visual standards that maintain a consistent online presence. Brand guidelines typically focus on how logos are treated, while style guides are more extensive – including not only look and feel, but also interactive behavior, such as the &lt;a href=&#34;https://playbook.cio.gov/designstandards/alerts/&#34;&gt;alerts and form templates&lt;/a&gt; in the U.S. Web Design Standards.&lt;/p&gt;
&lt;p&gt;Style guides empower groups, such as teams developing open-source software, to communicate with their users with one consistent voice. Visual design elements, such as fonts and colors, help the world understand who you are. For example, Starbucks Coffee has a particular green, which they use for a variety of purposes:&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/starbucks-green_hu_361fbe6bcbe2c789.jpeg&#34; alt=&#34;Image of the Starbucks Green&#34; width=&#34;740&#34; height=&#34;1316&#34;&gt;

&lt;em&gt;Starbucks Green: Pantone 3425 C / Hex #00704A / RGB[0,112,74] / CMYK[100,0,78,42].&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Because they are so consistent in using that green – and only that color green – people in many countries can make sense of this ad.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/starbucks-ad-cropped_hu_bb8507b3d2a3f732.jpg&#34; alt=&#34;Image: Photo of a Starbucks advertisement&#34; width=&#34;740&#34; height=&#34;472&#34;&gt;

&lt;em&gt;Photo of a Starbuck&amp;rsquo;s advertisement seen in San Francisco, October 2015.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;building-users-confidence&#34;&gt;Building Users&amp;rsquo; Confidence&lt;/h2&gt;
&lt;p&gt;As my recent blog post on &lt;a href=&#34;https://superbloom.design/learning/resources/nostalgia-trust-and-brand&#34;&gt;Nostalgia, Trust, and Brand Guidelines&lt;/a&gt; argues, end users can&amp;rsquo;t assess the quality of underlying cryptography, and will instead evaluate how robust or trustworthy software is based on its look and feel. Style guides can help a distributed team of volunteers come together to make polished software that inspires confidence by end-users and drives adoption of secure communication technologies.&lt;/p&gt;
&lt;h2 id=&#34;beyond-darth-hoodie&#34;&gt;Beyond &amp;ldquo;Darth Hoodie&amp;rdquo;&lt;/h2&gt;
&lt;p&gt;When Simply Secure worked with &lt;a href=&#34;&#34;&gt;Martin Wright&lt;/a&gt; of &lt;a href=&#34;https://www.mysociety.org/&#34;&gt;mySociety&lt;/a&gt; to create our style guide, we discussed using bright, punchy colors to convey a friendly, approachable tone. The Simply Secure colors and rounded fonts communicate a welcoming feeling, very different than the traditional shield, lock, and key icons that try to say &amp;ldquo;Secure!&amp;rdquo; but end up saying &amp;ldquo;Keep Out&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/resources/style-guide-v1.pdf&#34;&gt;Simply Secure&amp;rsquo;s style guide.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;These choices were intended to make security accessible and desirable to a mass audience, rather than the &lt;a href=&#34;http://www.istockphoto.com/photos/computer+hacker?facets=%7B%22text%22:%5B%22computer%20security%22%5D,%22pageNumber%22:1,%22perPage%22:100,%22abstractType%22:%5B%22photos%22%5D,%22order%22:%22bestMatch%22,%22f%22:true%7D&#34;&gt;dark, menacing images&lt;/a&gt; familiar to people who read articles about security in the popular press. Stock photography of hackers tends to be comical, with balaclavas and hoodies as standard attire, as in &lt;a href=&#34;https://www.pinterest.com/jkulenski/horrible-infosec-stock-art/&#34;&gt;Horrible Infosec Stock Art&lt;/a&gt; (thanks to @bascule in our Slack channel for the pointer).&lt;/p&gt;
&lt;h2 id=&#34;inviting-designers-to-participate&#34;&gt;Inviting Designers to Participate&lt;/h2&gt;
&lt;p&gt;Just as a cliché stock image tells InfoSec professionals that they aren&amp;rsquo;t the audience for an article, designers judge whether a team is a good fit for them based on appearances. UX professionals will look at a piece of software and evaluate how much its creators value their users, based on how professional and consistent the software&amp;rsquo;s interface, website, and supporting materials look. Style guides are a tangible asset that all teams should create to help designers understand a team&amp;rsquo;s values and commitment to UX, and to creating software for average people.&lt;/p&gt;
&lt;h2 id=&#34;imaging-different-use-cases&#34;&gt;Imaging Different Use Cases&lt;/h2&gt;
&lt;p&gt;Putting together a style guide is a good exercise on its own, because it helps clarify the audience and describe the situations where end users&amp;rsquo; will encounter the materials.  For instance, at Simply Secure we knew we wanted community events, so we made sure to have event signage that included the same colorful Fibonacci sequence that&amp;rsquo;s on our website and business cards.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/2016/EventSignageLandscape_hu_4124dd6915dfbb54.jpg&#34; alt=&#34;Image: Simply Secure event sign template.&#34; width=&#34;740&#34; height=&#34;572&#34;&gt;

&lt;em&gt;Simply Secure&amp;rsquo;s template for event signs.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Style guides should be living documents, updated over time, so starting with something quick and scrappy  – but open and accessible – is a great choice for an open-source project. We&amp;rsquo;re releasing ours under a &lt;a href=&#34;http://creativecommons.org/licenses/by/4.0/&#34;&gt;CC-BY 4.0 license&lt;/a&gt; on &lt;a href=&#34;https://superbloom.design/resources/style-guide-v1.pdf&#34;&gt;our website&lt;/a&gt; and our &lt;a href=&#34;https://github.com/simplysecure/resources&#34;&gt;Github repo&lt;/a&gt;, so you check it out. And, if you want help developing a style guide for your open-source secure-communications project, &lt;a href=&#34;https://superbloom.design/contact&#34;&gt;let us know&lt;/a&gt;!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Don&#39;t let security dogma steer you wrong</title>
      <link>https://superbloom.design/learning/blog/security-dogma/</link>
      <pubDate>Fri, 06 Nov 2015 16:00:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/security-dogma/</guid>
      <description>&lt;p&gt;My &lt;a href=&#34;https://superbloom.design/learning/blog/when-closed-source-wins/&#34;&gt;recent post&lt;/a&gt; describing some of the reasons we choose Slack over IRC for our public forum is part of a larger conversation people are having around the promise and concerns of group-communication tools. A quick search for &amp;ldquo;Slack vs. IRC&amp;rdquo; yields a wealth of opinions on the subject; our post generated some interesting discussion (and a couple angry rants on Twitter).&lt;/p&gt;
&lt;p&gt;I focused my discussion on the usability advantages of Slack – advantages that I believe encourage designers to join our public forum in a way that they would not if it were hosted on IRC. Simply Secure is about bridging the gap between the technical and design/research communities to get more human-centered thinkers working on open-source privacy-preserving tools. We can&amp;rsquo;t do that if we continue to tell designers that they have to communicate using tools they hate, and the OSS community&amp;rsquo;s expectation that they do so is one reason open-source tools are still so painful to use.&lt;/p&gt;
&lt;p&gt;Buried at the end of the post was another point that deserves more attention: &amp;ldquo;But for the meantime, this abstract threat does not outweigh the benefits Slack offers, especially when one ponders how often both Slack and its open-source alternatives realistically undergo regular security reviews by skilled engineers.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/xdogma_hu_9357afea147823cc.png&#34; alt=&#34;Text image: security reality, not security dogma&#34; width=&#34;740&#34; height=&#34;232&#34;&gt;
&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s critical to observe that we can&amp;rsquo;t assume that open-source tools are always – &lt;em&gt;by virtue of them being open source alone&lt;/em&gt; – the most secure in practice.&lt;/p&gt;
&lt;h2 id=&#34;open-source-alone-is-not-enough&#34;&gt;Open source alone is not enough&lt;/h2&gt;
&lt;p&gt;&amp;ldquo;What?!&amp;rdquo;, you might be yelling at your screen. After all, we all know that opening source code to the light of day allows the public to hold developers accountable, and prevent both unintentional bugs and all-too-intentional back doors.&lt;/p&gt;
&lt;p&gt;But, you have to ask yourself: how many security audits have you personally performed of the open-source tools you use? (What were the results? Did you do a follow-up a year later?) How many IRC clients have &lt;a href=&#34;https://hackerone.com/slack&#34;&gt;bug bounties&lt;/a&gt;? How many of the open-source tools we depend on have &lt;em&gt;anyone&lt;/em&gt; with security expertise reviewing their code – much less neutral third parties who aren&amp;rsquo;t part of the team that wrote it?&lt;/p&gt;
&lt;p&gt;The answers, of course, are not pretty. Even projects &lt;a href=&#34;http://arstechnica.com/security/2013/07/bad-kitty-rooky-mistake-in-cryptocat-chat-app-makes-cracking-a-snap/&#34;&gt;new&lt;/a&gt; and &lt;a href=&#34;http://heartbleed.com/&#34;&gt;old&lt;/a&gt; with an explicit security focus suffer serious bugs that would arguably have been caught by a thorough security review. We&amp;rsquo;re still exploring the world of Slack alternatives, but a &lt;a href=&#34;https://blog.okturtles.com/2015/11/five-open-source-slack-alternatives/&#34;&gt;recent review&lt;/a&gt; listed &amp;ldquo;empty test suite&amp;rdquo; as a problem with three of the five products it considered. If a team doesn&amp;rsquo;t have the resources to build automated tests into their development cycle, what confidence can we have that they are doing their due diligence with respect to security?&lt;/p&gt;
&lt;h2 id=&#34;dealing-with-resourcing-realities&#34;&gt;Dealing with resourcing realities&lt;/h2&gt;
&lt;p&gt;Big closed-source organizations like Slack clearly have the leg up in this domain; a quick search on &lt;a href=&#34;https://www.linkedin.com/vsearch/p?keywords=security&amp;amp;company=slack&#34;&gt;LinkedIn&lt;/a&gt; reveals at least a handful of Slack engineers whose primary focus is security. This is slowly changing in the open-source world; efforts like the &lt;a href=&#34;https://www.coreinfrastructure.org/&#34;&gt;Core Infrastructure Initiative&lt;/a&gt; and OTF&amp;rsquo;s &lt;a href=&#34;https://www.opentech.fund/lab/red-team-lab&#34;&gt;Red Team Lab&lt;/a&gt; (currently accepting &lt;a href=&#34;https://docs.google.com/a/simplysecure.org/forms/d/1nrbxhucjKeloQu3eSUkO1rMQ6QwdWNVOQqm-uUZVwjQ/viewform&#34;&gt;applications&lt;/a&gt;; contact &lt;a href=&#34;mailto:info@opentech.fund&#34;&gt;info@opentech.fund&lt;/a&gt; with questions) provide support to open-source projects seeking to evaluate and improve their security posture.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s not enough to shake our collective, outraged fist and say that open-source projects would fulfill their maximally-secure destiny if only they had more resources. And I agree, of course, that there are considerations beyond code-level vulnerabilities that should give any user pause when considering a tool like Slack. &lt;a href=&#34;https://superbloom.design/learning/resources/not-binary-properties/&#34;&gt;Security is not a binary property&lt;/a&gt;, and a cloud-based solution hosted by a third party is too risky in the context of many organizations&amp;rsquo; threat models.&lt;/p&gt;
&lt;h2 id=&#34;open-source-is-good-avoiding-dogma-is-better&#34;&gt;Open-source is good; avoiding dogma is better&lt;/h2&gt;
&lt;p&gt;So if you&amp;rsquo;re an organization that has the technical resources to host your own solution, and you find one that is truly accessible to your users (or your users have the time and patience to work with the developers to improve it), that&amp;rsquo;s great! If you do use an open-source tool, please contribute back to the project so its developers can continue in their good work. This is the ideal outcome, and the one that will lead us to the best privacy and security posture over time.&lt;/p&gt;
&lt;p&gt;But, in the meantime – and no matter your threat model – please take an honest look at the pros and cons of any solution you consider, and think critically about whether a development team practices the values that they preach. Open-source solutions are great, but only if they will really meet your needs, or can be adapted to in a reasonable amount of time to do so. Just because something is open-source doesn&amp;rsquo;t mean that is it necessarily has fewer security vulnerabilities than a closed-source solution. Espousing otherwise – especially to organizations with limited technical capacity – is irresponsible.&lt;/p&gt;
&lt;p&gt;Don&amp;rsquo;t let security dogma get in the way of your assessment of security reality.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Thanks to &lt;a href=&#34;https://twitter.com/Isa&#34;&gt;@isa&lt;/a&gt; for a recent conversation on the topic that inspired this post, although please don&amp;rsquo;t blame her for my conclusions.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Mind The Gap Between Mobile Apps</title>
      <link>https://superbloom.design/learning/blog/mind-the-gap-mobile/</link>
      <pubDate>Fri, 30 Oct 2015 18:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/mind-the-gap-mobile/</guid>
      <description>&lt;p&gt;Users of the Facebook iPhone app were recently surprised by a new feature offering to “Add the last link you copied?” into a status update. Many people did not expect to see a complete URL that they had put onto the clipboard from another app, without explicitly involving Facebook. Christian Frichot &lt;a href=&#34;https://un-excogitate.org/facebook-ios-clipboard&#34;&gt;discusses iOS security concerns&lt;/a&gt; with this feature, but I also consider this to be a UX design failure.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/Facebook-URL2_hu_89acd01f5e5287e1.jpg&#34; alt=&#34;Screenshots of new Facebook URL feature&#34; width=&#34;740&#34; height=&#34;593&#34;&gt;
&lt;br&gt;
&lt;em&gt;Copying a link in Safari (left) makes it appear in Facebook (right).&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Consider the following example scenario: you get a reminder to share the name of a counseling service with a friend who is having a difficult time. Several minutes after copying Integral Counseling’s website URL from Safari into an email and sending it to your friend, you open Facebook and see the offer to include the link in a status update. Clicking the X in the dialog box presumably prevents Facebook from including the link in your status update, but there’s no way to keep the link from the screen or – more broadly – to limit Facebook’s access to your clipboard in the first place.&lt;/p&gt;
&lt;p&gt;Facebook seems to be reading everything on the clipboard to see if there happens to be a link to a website. People copying &lt;em&gt;any&lt;/em&gt; information – even passwords or personal notes to themselves, even when using encrypted chat or email – feel like they have had their privacy compromised.&lt;/p&gt;
&lt;h2 id=&#34;good-ux-isnt-creepy&#34;&gt;Good UX Isn&amp;rsquo;t Creepy&lt;/h2&gt;
&lt;p&gt;Individual iOS apps haven’t always done a good job of exposing to the user how they access OS-level features like the clipboard and address book. Seamless access to Contacts creates all sorts of awkward situations, such as Tinder dates showing up in LinkedIn’s “People you might know”.&lt;/p&gt;
&lt;p&gt;The Privacy menu of the device’s Settings lets users specify which apps have access to Contacts, Photos, and other OS features. This control panel, traditional copy-pasting, and the interface for explicit in-app sharing are the ways users understand how content gets into Facebook, a broadcast medium. Automatically pulling in links from the clipboard breaks that mental model.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/iOS-Privacy-Menu2_hu_5e85e2d3121af8f1.jpg&#34; alt=&#34;Screenshots of the iOS Privacy Settings&#34; width=&#34;740&#34; height=&#34;438&#34;&gt;
&lt;br&gt;
&lt;em&gt;Left: the Privacy menu of Settings controls which apps access OS-level functionality like Photos and Contacts. Center: within Safari and other apps that use the iPhone’s native sharing menu, Facebook shows up as a destination. Right: the iOS Facebook app automatically pulls in links from the clipboard.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;There is no setting for granting access to the clipboard; it seems that iOS provides unlimited access to all apps. There are cases where this functionality makes sense and truly helps the user: for example, reading-list manager Pocket also inspects the clipboard for content and asks to add a copied URL to your personal list. Perhaps similar functionality makes Facebook feel creepy because Pocket is about keeping your data for you, while Facebook is about sharing your data with the world.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/Pocket-Flow_hu_dc8542eecddac480.png&#34; alt=&#34;Screenshots from using Pocket&#34; width=&#34;740&#34; height=&#34;424&#34;&gt;
&lt;br&gt;
&lt;em&gt;Left: Pocket asks to add a URL to a reading list. Center: when reading a website within Pocket, there’s an option to share that link. Right: Pocket has options to share with different audiences, including via Facebook, but the default is a personal reading list.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;These apps’ differing value propositions are apparent from the language on their respective home pages. &lt;a href=&#34;https://www.facebook.com/&#34;&gt;Facebook&lt;/a&gt; invites you to “Connect with friends and the world around you.” In contrast, &lt;a href=&#34;https://getpocket.com/&#34;&gt;Pocket&lt;/a&gt; is about keeping thing to yourself, telling users “When you find something you want to view later, put it in Pocket.” The private nature of the app is reinforced by a mental model that Pocket is a place on your phone where you can read articles and watch videos even without a network connection.&lt;/p&gt;
&lt;p&gt;UX designers have worked hard to create seamless user experiences where things seem to happen as if by magic. But as people’s behavior online and off is increasingly tracked, seamlessness can now easily evolve from being unexpectedly delightful to downright creepy. Facebook has a business imperative to get more content into the platform, and this probably resulted in a drive to create a shortcut around the iOS sharing menu. I encourage individual designers facing similar imperatives to push back and protect their users by advocating for good UX – in other words, UX that isn’t creepy.&lt;/p&gt;
&lt;h2 id=&#34;alternative-elegant-seams&#34;&gt;Alternative: Elegant Seams&lt;/h2&gt;
&lt;p&gt;As more people become privacy aware, there’s a professional challenge for UX designers to understand the technical on-ramps and off-ramps of how data flows into and out of their apps. Elegant transitions between apps can help UX designers move from a siloed view of their product to a transitional view, designing for users to move throughout an ecosystem of apps and operating systems.&lt;/p&gt;
&lt;p&gt;Consider how the &lt;a href=&#34;http://www.theverge.com/2011/12/13/2612736/ios-history-iphone-ipad&#34;&gt;iPhone UX&lt;/a&gt; evolved; it launched without a clipboard or the ability to multi-task between apps. The UX for switching between apps is still clunky, relying on a double-click to see what apps are open. And even though people now often move between apps or close apps they don’t want running in the background, the interface for multi-tasking hasn’t kept pace. Double-clicking to scroll through apps is one kind of seam, but not an elegant one.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/Double-Click-Apps-Small_hu_15a116f869165e01.png&#34; alt=&#34;Screenshot of iOS app switching&#34; width=&#34;740&#34; height=&#34;1313&#34;&gt;
&lt;br&gt;
&lt;em&gt;Double-clicking the iPhone’s button shows open apps.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Surfacing the seams between apps – such as permission management and data sharing (both implicit and explicit) – is important for empowering users to protect their privacy. Rather than falling into a paternalistic trap of “making everything just work” and not “forcing the user to think” – which robs users of their agency – designers must create elegant interfaces that liberate users to manage how their data flows between apps.&lt;/p&gt;
&lt;p&gt;One opportunity for managing seams and meeting people’s privacy goals is to use best practices from &lt;a href=&#34;https://www.service-design-network.org/about-service-design&#34;&gt;service design&lt;/a&gt; for helping people move between multiple experiences and platforms.&lt;/p&gt;
&lt;p&gt;In an increasingly-privacy conscious world, “seamless” doesn’t always work. Sometimes we need elegantly visible seams.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Underexposed: Building a Movement for Secure UX</title>
      <link>https://superbloom.design/learning/blog/underexposed-building-movement/</link>
      <pubDate>Fri, 23 Oct 2015 15:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/underexposed-building-movement/</guid>
      <description>&lt;p&gt;Last week Simply Secure hosted a pilot workshop called Underexposed. A small group came together in San Francisco to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Share successes and challenges in secure user experiences.&lt;/li&gt;
&lt;li&gt;Describe processes and wishes for successful collaboration between designers, developers, and security professionals.&lt;/li&gt;
&lt;li&gt;Prioritize the most important topics and audiences for outreach.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We also held participant-proposed breakout sessions on topics ranging from “Making a Living” to “Privacy-Preserving User Research Metrics.”&lt;/p&gt;
&lt;p&gt;You can &lt;a href=&#34;https://superbloom.design/resources/events/Underexposed2015RawNotes.pdf&#34;&gt;download a pdf&lt;/a&gt; of photos capturing the post it notes from the sessions.&lt;/p&gt;
&lt;h2 id=&#34;top-3-surprises&#34;&gt;Top 3 Surprises&lt;/h2&gt;
&lt;p&gt;We&amp;rsquo;re hard at work synthesizing the discussion, but Underexposed is a community effort. Please reach out if you&amp;rsquo;re interested in being a reviewer of the output. Stay tuned for more outcomes, but here are three of the things from the notes that stood out to me.&lt;/p&gt;
&lt;h3 id=&#34;timing-is-everything&#34;&gt;Timing is Everything&lt;/h3&gt;
&lt;p&gt;One of our goals was to find specific ways to facilitate collaboration between designers and other teammates. Part of that effort involved identifying communication gaps and misconceptions about design. Timing came up as a common misconception. Budgeting sufficient time for design into a project plan is one way to insure success. We also heard a clear request to involve design earlier in the process, rather than tacking it onto the end after the technical challenges are met.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/designmisconceptions-small_hu_9c3e7b539b8e52f0.jpg&#34; alt=&#34;Image: Design takes time. Design is not window dressing at the end.&#34; width=&#34;740&#34; height=&#34;361&#34;&gt;
&lt;/p&gt;
&lt;p&gt;We heard an unmet need for project and product management expertise, and Simply Secure is working to build those skills in the secure communications community.&lt;/p&gt;
&lt;h3 id=&#34;lights-camera-action&#34;&gt;Lights, Camera, Action!&lt;/h3&gt;
&lt;p&gt;The group identified some surprising potential audiences for Simply Secure&amp;rsquo;s work normalizing Human-Centered Design for security. Journalists were consistently mentioned as a priority, but groups like celebrities and parents/grandparents unexpectedly surfaced as well.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/audiences-small_hu_b67869d2b4225917.jpg&#34; alt=&#34;Image: Audience journalists; Audience: celebrities; Audience: Parents and Grandparents&#34; width=&#34;740&#34; height=&#34;250&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Telling human stories about the lives of relatable people is an important part of communicating the value of secure communications.&lt;/p&gt;
&lt;h3 id=&#34;blackout-day&#34;&gt;Blackout Day&lt;/h3&gt;
&lt;p&gt;The community is looking for ways to build awareness of global security challenges. There&amp;rsquo;s a need for visual design that works across cultures, in addition to localizing the text in interfaces. Building empathy for the digital threats that people face in other geographies is challenging. Perhaps inspired by the 2012 &lt;a href=&#34;https://en.wikipedia.org/wiki/Protests_against_SOPA_and_PIPA&#34;&gt;protest against proposed internet legislation&lt;/a&gt; in the U.S., one creative way to help more people appreciate an open internet is to have a &amp;ldquo;Blackout Day,&amp;rdquo; simulating the conditions of internet restrictions.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/blackout-day-small_hu_b58672a049329089.jpg&#34; alt=&#34;Black Out Day. Empathy for the experience of other countries.&#34; width=&#34;740&#34; height=&#34;733&#34;&gt;
&lt;/p&gt;
&lt;p&gt;Thanks to our participants&amp;rsquo; lively discussion, Underexposed was a success. We&amp;rsquo;re working on ways to involve more people in the future.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>When Closed-Source Software Wins The Day</title>
      <link>https://superbloom.design/learning/blog/when-closed-source-wins/</link>
      <pubDate>Fri, 16 Oct 2015 16:10:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/when-closed-source-wins/</guid>
      <description>&lt;p&gt;We prefer to use open-source software as a matter of principle. We believe that putting software code in the open is the best way for the public to build trust in it.&lt;/p&gt;
&lt;p&gt;You might find it curious, then, that we choose to foster communication and community through a tool like &lt;a href=&#34;https://slack.com/&#34;&gt;Slack&lt;/a&gt;, which is closed-source. (Note: you can request to join our Slack channel by sending a request to &lt;a href=&#34;mailto:slack@superbloom.design&#34;&gt;slack@superbloom.design&lt;/a&gt;.) Many software teams that build privacy-preserving tools host similar spaces dedicated to communication with volunteers and users. Their spaces are usually built on &lt;a href=&#34;https://en.wikipedia.org/wiki/Internet_Relay_Chat&#34;&gt;IRC&lt;/a&gt;, though, which has multiple open-source options for both the client and the server. Why didn’t we go a similar route?&lt;/p&gt;
&lt;p&gt;Our decision to go with Slack over IRC mirrors the decisions that people the world over make every day. If we take a minute to examine our reasoning, we can find some valuable lessons for open-source developers.&lt;/p&gt;
&lt;h2 id=&#34;instant-access&#34;&gt;Instant access&lt;/h2&gt;
&lt;p&gt;One of the biggest advantages we found Slack has over IRC is how quickly it works in a variety of environments. You can get up and running on the web in less than a minute, and expand your experience to include a native client on your desktop or mobile device with a quick download. You don’t have to enter a channel name or configure the software to point at a particular server: you click on an invitation in your email, and you can get started after just one or two steps.&lt;/p&gt;
&lt;p&gt;Slack has been pretty close to instantly accessible from an administrative point of view, too. We haven’t had to set up a server, do extensive configuration, or offer any kind of how-to information to our users other than “send us an email and we’ll invite you”. Given the diverse community of people we are trying to reach – including designers, researchers, and program managers – we expect we would either have to offer a lot of support to get the more adventuresome among them to try IRC.&lt;/p&gt;
&lt;h2 id=&#34;stateful-active-participation&#34;&gt;Stateful, active participation&lt;/h2&gt;
&lt;p&gt;IRC grew up in the age of desktops, where you only participated in a real-time online conversation when you were seated at the keyboard. Some IRC clients may have evolved beyond this model, but vestiges of it remain. Today’s smartphone-weilding users operate in a different world, where they might be on their phone at one moment, a computer the next, and a tablet in a few hours. Slack tries to make this experience seamless. It remembers where in the conversation stream you left off, and helps you find your place across different devices. It also lets you get notifications when somone mentions you, so you can tune in even when you’re “offline”.&lt;/p&gt;
&lt;h2 id=&#34;friendliness&#34;&gt;Friendliness&lt;/h2&gt;
&lt;p&gt;Beyond ease of first use and aspects of the software’s functionality, Slack is just so gosh darn &lt;em&gt;friendly&lt;/em&gt; looking. For many people, staring at a screen full of monospace text is tortuous. Tasteful in-line image integration, textual hierarchies interspersed with whitespace, and tastefully-colorful menus all make Slack easier on the eyes. There’s a welcoming bot that helps you set up your profile, and pithy loading messages help you adopt a lighthearted mood when you join each day. Finally, Slack offers much of its functionality up front through graphical interfaces, rather than requiring the user to learn special textual incantations to access them. Although Slack is intended to help people communicate through text, its attention to other details is what makes the experience more enjoyable than current IRC clients for most people.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/irc-client_hu_436f13bd627dfe0.png&#34; alt=&#34;Image: Screenshot of an IRC client.&#34; width=&#34;740&#34; height=&#34;417&#34;&gt;
 

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/slack-screenshot_hu_b7a56a2bc993fd52.png&#34; alt=&#34;Image: Screenshot of our Slack channel.&#34; width=&#34;740&#34; height=&#34;391&#34;&gt;

&lt;em&gt;The IRC and Slack experiences are very different&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;the-tradeoffs&#34;&gt;The tradeoffs&lt;/h2&gt;
&lt;p&gt;Now that I’ve gushed about what Slack offers, I want to call out some of its downsides. Because it’s owned and operated by a third party, we don’t have ultimate control over our Slack community. We believe that the company has reasonable policies in place that prevent their employees from going in and mucking about, but there’s always a chance that a bad apple could get in and do damage of some kind.&lt;/p&gt;
&lt;p&gt;This lack of control also manifests in the fact that Slack limits the number of archived messages that are available on unpaid accounts. In other words: if we want to access all of our archives, we need to pay them money – and given their rates for a community our size, we can’t afford to. The silver lining here is that they offer &lt;a href=&#34;https://slack.com/help/articles/204368833-Apply-for-the-Slack-for-Nonprofits-discount&#34;&gt;free upgrades to documented nonprofit organizations&lt;/a&gt;, so when our application for 501(c)3 status is approved, we should be able to gain access to those archives again. (We have also been trying to download the archives on a semi-regular basis for our archive, and are glad that Slack provides the facility to perform such downloads to administrators.)&lt;/p&gt;
&lt;p&gt;Finally, being closed-source means that Slack may have all sorts of crazy vulnerabilities that could allow an attacker to compromise our community in some way, and only Slack employees would know. For some communities this alone is enough to make Slack an impossible option, which we understand and support. So if an open-source solution comes along that offers more of Slack’s benefits than current IRC options, we will definitely reconsider our choice (feel free to &lt;a href=&#34;https://www.simplysecure.org/contact&#34;&gt;contact us&lt;/a&gt; if you know of one). But for the meantime, this abstract threat does not outweigh the benefits Slack offers, especially when one ponders how often both Slack and its open-source alternatives &lt;em&gt;realistically&lt;/em&gt; undergo regular security reviews by skilled engineers.&lt;/p&gt;
&lt;p&gt;This is one case where open-source options are currently losing the battle, at least right now.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;sup&gt;Screenshot of the WeeChat IRC client, &lt;a href=&#34;https://commons.wikimedia.org/wiki/File:WeeChat_0.3.5_-_es.wikipedia_at_irc.wikimedia.org.png&#34;&gt;Fundación Wikimedia, Inc.&lt;/a&gt;, published under a CC BY-SA 3.0 license.&lt;/sup&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Catching Issues in Evolving Interfaces</title>
      <link>https://superbloom.design/learning/blog/catching-issues-evolving-interfaces/</link>
      <pubDate>Thu, 08 Oct 2015 16:10:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/catching-issues-evolving-interfaces/</guid>
      <description>&lt;p&gt;You may remember this summer’s media frenzy surrounding adultery-matchmaking site Ashley Madison. In brief, the company had its password database hacked, stolen, and posted online with great fanfare. Amidst the stories focusing on noteworthy individuals and the demographics of the membership as a whole, some people have been investigating other aspects of the site’s operations, from their “Affair Guarantee” package to their practice of &lt;a href=&#34;http://arstechnica.com/business/2015/07/cheaters-hook-up-site-ashley-madison-makes-account-deletion-confusing/&#34;&gt;charging to delete&lt;/a&gt; a user’s account from their servers.&lt;/p&gt;
&lt;h2 id=&#34;leaky-interfaces&#34;&gt;&amp;ldquo;Leaky&amp;rdquo; Interfaces&lt;/h2&gt;
&lt;p&gt;One researcher uncovered a quirk of the site’s password-recovery form that actually allows someone to check whether an email address is associated with an account. In security, we often refer to such a flaw as “leaking” sensitive information.&lt;/p&gt;
&lt;p&gt;Usually leaks that occur with sign-in or password-recovery forms involve the text of the interface – e.g., a sign-in form that responds “The password entered does not match the one on file for this email address” as opposed to the more broad “The email address and/or password entered do not match our records.”&lt;/p&gt;
&lt;p&gt;The Ashley Madison password-recovery form actually uses the same text whether or not the email address entered is in their database. However, in one case the text-input field and the button stay present in the screen, and in the other case they disappear.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/am-screenshots_hu_bea5ac6d50bb7ef3.png&#34; alt=&#34;Image: Screenshots from Ashley Madison&amp;rsquo;s password-recovery form.&#34; width=&#34;740&#34; height=&#34;258&#34;&gt;
&lt;br&gt;
&lt;em&gt;Screenshots of Ashley Madison’s password-recovery form when the email address is not (left) and is (right) part of their database.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;supporting-graceful-product-evolution&#34;&gt;Supporting graceful product evolution&lt;/h2&gt;
&lt;p&gt;Given the site’s focus on discretion – and the carefully-worded textual content of the form – it’s unlikely that someone sat down and intentionally designed it to behave this way. It’s more likely that this interaction snuck in as parts of the site’s architecture were reworked over time. Since the folks working on the site likely don’t reset their passwords on a regular basis (much less compare the result when the email address is and is not in the database), it&amp;rsquo;s easy to see how the team missed the addition once it was added.&lt;/p&gt;
&lt;p&gt;This is an example of why it&amp;rsquo;s important to think of designing not just the &lt;em&gt;product&lt;/em&gt;, but also &lt;em&gt;processes&lt;/em&gt; to support the product&amp;rsquo;s graceful evolution over time.&lt;/p&gt;
&lt;p&gt;Here are some ideas to help catch interface problems that sneak in:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Create UX reviewers.&lt;/strong&gt; Just as teams conduct code reviews before a set of code changes are committed, it can be useful to have UX reviews as well. These can be performed by a designer – advisable when an interface is being implemented against a set of mockups that the designer created – or by another engineer when the change is small. The goal is to make sure that at least one other person takes a solid, critical look at the user-facing implications of the changes, just as the code implications are examined.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Create an adversary persona.&lt;/strong&gt; Many teams craft &lt;a href=&#34;https://en.wikipedia.org/wiki/Persona_(user_experience)&#34;&gt;user personas&lt;/a&gt; to help them design interaction patterns that will meet the needs of their diverse user population. Why not also create one or more personas representing attackers? (Thanks to &lt;a href=&#34;https://twitter.com/gretared&#34;&gt;@gretared&lt;/a&gt; for her take on &lt;a href=&#34;https://twitter.com/jorm&#34;&gt;@jorm&lt;/a&gt;&amp;rsquo;s idea of creating a troll persona – &amp;ldquo;because you can&amp;rsquo;t design for good without understanding the evil&amp;rdquo;). This adversary persona can help UX reviewers identify ways that the interface might inadvertently leak information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Regularly audit against known best practices.&lt;/strong&gt; Armed with your attacker persona and other approaches for threat modeling, try to identify a set of principles or clear protection goals that you can then use to evaluate the user experience on a regular basis. For example, many websites require users to reauthenticate before accessing sensitive parts of their account; this is a best practice that protects against both accidental and some intentional forms of data compromise. Keep the list of best practices as short as you can, to make it feasible to schedule a regular review that assures your interface hasn&amp;rsquo;t evolved too far from its original privacy-driven design.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;p&gt;&lt;em&gt;Screenshots of Ashley Madison password-recovery forms captured by Troy Hunt and &lt;a href=&#34;http://www.troyhunt.com/2015/07/your-affairs-were-never-discrete-ashley.html&#34;&gt;used on his blog&lt;/a&gt;, which is published under a CC BY-SA 3.0 license.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Ninjas &#43; Hemingway: Writing for User Interfaces</title>
      <link>https://superbloom.design/learning/blog/writing-for-uis/</link>
      <pubDate>Fri, 02 Oct 2015 16:10:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/writing-for-uis/</guid>
      <description>&lt;h2 id=&#34;writing-for-interface-how-to-explain-things-and-reduce-support-needs&#34;&gt;Writing for Interface: How to Explain Things and Reduce Support Needs&lt;/h2&gt;
&lt;p&gt;The writing in your user interface is an opportunity to encourage people to use your product. Writing in interfaces includes everything from the words in an in-app setup tutorial to a website&amp;rsquo;s navigation menu. Because there is both technical complexity and high stakes for user failure, careful language is key to getting mass audiences to adopt secure communication tools.&lt;/p&gt;
&lt;p&gt;Good writing for an interface, also called user-experience (UX) copywriting, does two things:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;It explains &lt;strong&gt;how things work&lt;/strong&gt;, and&lt;/li&gt;
&lt;li&gt;It creates an &lt;strong&gt;emotional reaction&lt;/strong&gt; with the user.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;explanations-in-language-people-understand&#34;&gt;Explanations in language people understand&lt;/h3&gt;
&lt;p&gt;Explaining how things work isn&amp;rsquo;t straightforward. Many secure communication apps struggle with conveying too much technical information to an overwhelmed user who, for example, doesn&amp;rsquo;t care about the difference between DSA and RSA keys. Careful UX copywriting avoids this pitfall.&lt;/p&gt;
&lt;p&gt;Even a simple explanation can create a negative emotional reaction when it sounds like jargon to a general audience. Jargon is off-putting, whether it&amp;rsquo;s Silicon Valley buzzwords or bureaucratic &lt;a href=&#34;https://en.wiktionary.org/wiki/governmentese&#34;&gt;governmentese&lt;/a&gt;, because it conveys that the service is untrustworthy. To stamp out jargon, Mail Chimp&amp;rsquo;s Content Style Guide on GitHub includes this &lt;a href=&#34;https://github.com/mailchimp/content-style-guide/blob/master/16-word-list.html.md#words-to-avoid&#34;&gt;list of words to avoid using&lt;/a&gt;. They&amp;rsquo;ve flagged a bunch of corporate-speak words as inappropriate. Mail Chimp is a sales tool for sending customized email and newsletters, so &amp;ldquo;Incentivizing your ninjas to crush it!&amp;rdquo; could be a reasonable explanation of their value to their customers who are marketing professionals, but their writing is careful to use vocabulary that is accessible to a broader audience.&lt;/p&gt;
&lt;p&gt;&amp;ldquo;Hash&amp;rdquo;? &amp;ldquo;Fingerprint&amp;rdquo;? Tweet us @simplysecureorg with your nominations of technical security terms to avoid.&lt;/p&gt;
&lt;h3 id=&#34;reducing-the-need-for-support&#34;&gt;Reducing the need for support&lt;/h3&gt;
&lt;p&gt;With good UX copywriting directly in the interface, the need for training and other kinds of support decreases. Consider this excerpt from 18F&amp;rsquo;s writing guide for U.S. Government websites:&lt;/p&gt;
&lt;p&gt;&amp;ldquo;FAQs are bad. We don&amp;rsquo;t like them. &lt;strong&gt;If you write content by starting with user needs, you won&amp;rsquo;t need to use FAQs.&lt;/strong&gt; … If you&amp;rsquo;re thinking about adding FAQs, consider reviewing the content on your website that is generating questions and think about how you can change the content or design to answer the question — or provide an answer in context to prevent people from visiting an additional webpage to find the answer.&amp;rdquo; – &lt;a href=&#34;https://pages.18f.gov/content-guide/faqs/&#34;&gt;18F Content Guide&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Similarly, the &lt;a href=&#34;https://www.gov.uk/guidance/content-design/writing-for-gov-uk&#34;&gt;Gov.UK writing guide&lt;/a&gt; does a good job of explaining how to make complex information accessible to a broad audience. Just as a piece of consumer software must be understandable to many types of users to be successful, UK government publications must reach and be useful to a broad spectrum of readers, from English-language learners, to populations with low levels of literacy, and citizens with a range of accessibility challenges.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;With good UX copywriting directly in the interface, the need for training and other kinds of support decreases.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&#34;resources-for-ux-copywriting&#34;&gt;Resources for UX copywriting&lt;/h3&gt;
&lt;p&gt;In addition to complete style guides, here are some practical tips:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;InVision&amp;rsquo;s &lt;a href=&#34;http://blog.invisionapp.com/10-ux-copywriting-tips-designers/&#34;&gt;Ten UX Copywriting Tips for Designers&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;User Testing&amp;rsquo;s &lt;a href=&#34;https://www.usertesting.com/blog/2015/02/10/copywriting/&#34;&gt;Six Ways to Keep Bad Copywriting from Killing Your Product&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;My favorite suggestion (which makes both lists) is to make your writing shorter. To trim excess words, try the &lt;a href=&#34;http://www.hemingwayapp.com/&#34;&gt;Hemingway App&lt;/a&gt;. It was named after the writer whose work was famous for its short, clear sentences.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/hemingway_hu_a9725b0536a95cf1.png&#34; alt=&#34;Image: Screenshot from Hemingway App, showing dynamic highlighting as you type.&#34; width=&#34;740&#34; height=&#34;442&#34;&gt;
&lt;br&gt;
&lt;em&gt;Image: Screenshot from &lt;a href=&#34;http://www.hemingwayapp.com/&#34;&gt;Hemingway App&lt;/a&gt;, showing dynamic highlighting as you type.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Victims of Success: Dealing With Divergent Feature Requests</title>
      <link>https://superbloom.design/learning/resources/handling-feature-requests/</link>
      <pubDate>Fri, 25 Sep 2015 17:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/handling-feature-requests/</guid>
      <description>&lt;p&gt;Last fall I attended a workshop with a group of open-source developers working on security tools. In talking about the challenges they faced in making their tools more usable, I blithely said something along the lines of &amp;ldquo;It&amp;rsquo;s important to always listen to your users, and take your cues from them.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;&amp;ldquo;But how,&amp;rdquo; replied one developer, &amp;ldquo;do you know what feature requests are the right ones?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;My first response was confusion. I was talking about user research, so a question about feature requests seemed like a bit of a non-sequitur – especially since lay users are generally more comfortable sharing problems than they are sharing suggestions for improvement (e.g., “configuring the app is hard!” rather than “please reduce the number of steps in the sign-up flow&amp;quot;). The developer then shared that, although his team didn&amp;rsquo;t have a lot of opportunities to interact directly with their users, they &lt;em&gt;did&lt;/em&gt; have a form for submitting feature requests. Moreover, their more tech-savvy users were using the form a lot, to the point of inundating the team. He wanted to know how to prioritize among this deluge.&lt;/p&gt;
&lt;h2 id=&#34;listen-for-the-intent-underneath-the-request&#34;&gt;Listen for the intent underneath the request&lt;/h2&gt;
&lt;p&gt;While it is important to listen to your users and learn from their message, it&amp;rsquo;s absolutely critical to hear the intent behind what they say. To use a contrived example, imagine that a user says &amp;ldquo;You should put a purple pony on your main page. Ponies are really friendly, and I like them, and they would make me smile every time I opened the app!&amp;rdquo;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;While it is important to listen to your users and learn from their message, it&amp;rsquo;s absolutely critical to hear the intent behind what they say.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;While it&amp;rsquo;s undoubtedly true that this one user would find your app much improved by the addition of a little &lt;a href=&#34;https://en.wikipedia.org/wiki/List_of_My_Little_Pony:_Friendship_Is_Magic_characters#Twilight_Sparkle&#34;&gt;Twilight Sparkle&lt;/a&gt;, that doesn&amp;rsquo;t mean that actually adding an image of a My Little Pony is going to improve the experience for most of your users. Even if you got the same message from hundreds of people, you should still ask yourself: &lt;em&gt;What underlying need is driving these requests?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In this example, the suggestion itself gives some clues:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The user says that ponies are friendly. Does the user find the app unfriendly? Is there something about the color scheme, the typography, or the wording used in the app that could be changed to make it more inviting?&lt;/li&gt;
&lt;li&gt;Ponies are lighthearted and energizing. Does the user feel that interacting with the app is burdensome or painful? Are there unvoiced friction points that could be smoothed over to make the app more enjoyable to use?&lt;/li&gt;
&lt;li&gt;The user says they want to smile when they open the app. Although a pony may not be an appealing symbol for all people, is there another non-invasive way to greet the user when the app is launched?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;find-deeper-answers-through-research-and-analysis&#34;&gt;Find deeper answers through research and analysis&lt;/h2&gt;
&lt;p&gt;Rather than view feature requests as a set of highly-divergent signals, it can help to try and group requests based on the underlying need that they speak to. If you see a lot of heat around your error conditions, consider reviewing the messages displayed in those situations to make sure they make sense to people not on the development team. If you have a lot of requests around your sign-up flow, perhaps it&amp;rsquo;s time to do some &lt;a href=&#34;https://en.wikipedia.org/wiki/Cognitive_walkthrough&#34;&gt;cognitive walkthroughs&lt;/a&gt; with real users to identify friction points. If possible, make sure that your feature-request channel offers users the possibility to enter their contact information, as it is often helpful to follow up with them afterward for more context about why they are making the request.&lt;/p&gt;
&lt;h2 id=&#34;keep-the-channels-open&#34;&gt;Keep the channels open&lt;/h2&gt;
&lt;p&gt;More generally, make sure that your team gets opportunities to interact with users that aren&amp;rsquo;t just through feature requests. Whether it&amp;rsquo;s a help forum, a user study, a questionnaire on the download page, or some other channel, the more insight you can gain into what and how users think about your product, the better equipped you will be to prioritize user-facing improvements.&lt;/p&gt;
&lt;p&gt;If you want to talk through how your open-source security project learns about its users or prioritizes its feature requests, please &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;get in touch&lt;/a&gt;!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Fostering Discussions Around Privacy</title>
      <link>https://superbloom.design/learning/blog/privacy-discussions/</link>
      <pubDate>Fri, 18 Sep 2015 17:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/privacy-discussions/</guid>
      <description>&lt;p&gt;This week we&amp;rsquo;ve been busy in New York City meeting with our &lt;a href=&#34;about/people/#board-of-directors&#34;&gt;advisors&lt;/a&gt; and co-hosting &lt;a href=&#34;https://superbloom.design/learning/blog/nyc-event/&#34;&gt;Art, Design, and the Future of Privacy&lt;/a&gt;. It was gratifying to see so many people turn out to discuss creative ways of approaching an issue that is dear to our hearts, and I know that I&amp;rsquo;m not the only one who was inspired by the work our speakers are doing. From Lauren McCarthy&amp;rsquo;s &lt;a href=&#34;http://socialturkers.com/&#34;&gt;crowdsourced relationships&lt;/a&gt;, to Sarah Ball&amp;rsquo;s perspective from working as a &lt;a href=&#34;http://www.nypl.org/help/community-outreach/correctional-services&#34;&gt;prison librarian&lt;/a&gt;, and straight through to &lt;a href=&#34;http://craphound.com/&#34;&gt;Cory&lt;/a&gt;&amp;rsquo;s rousing call for hope and action in the era of peak indifference, the evening showed that the conversation about privacy is for more than just technologists and policy makers.&lt;/p&gt;
&lt;p&gt;The event was recorded, and we&amp;rsquo;ll share that recording here and via &lt;a href=&#34;https://twitter.com/simplysecureorg&#34;&gt;Twitter&lt;/a&gt; as soon as we can. In the meantime, we want to hear about the conversations you&amp;rsquo;re having in your town about privacy. Are you a designer or an artist working on projects that deal with the subject? Are you a software developer who has been inspired to build privacy-preserving tools, or a person who is curious and interested in learning more about what tools are already available? We want to hear about your experiences, so &lt;a href=&#34;https://superbloom.design/contact&#34;&gt;get in touch&lt;/a&gt;!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Nostalgia, Trust, and Brand Guidelines</title>
      <link>https://superbloom.design/learning/resources/nostalgia-trust-and-brand/</link>
      <pubDate>Fri, 11 Sep 2015 15:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/nostalgia-trust-and-brand/</guid>
      <description>&lt;p&gt;Last week &lt;a href=&#34;https://design.google/library/evolving-google-identity&#34;&gt;Google unveiled a new logo&lt;/a&gt; as part of an updated brand identity. Professional typographic designers were swift to react. &lt;a href=&#34;http://www.theverge.com/2015/9/2/9248309/google-new-logo-graphic-design&#34;&gt;Tobias Frere-Jones&lt;/a&gt;, designer of &lt;a href=&#34;https://en.wikipedia.org/wiki/Interstate_(typeface)&#34;&gt;Interstate&lt;/a&gt; and other widely-used fonts, said &amp;ldquo;I really hope this &amp;rsquo;e&amp;rsquo; does not become a thing.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Beyond professional designers, the New Yorker&amp;rsquo;s &lt;a href=&#34;https://www.newyorker.com/culture/sarah-larson/why-you-hate-googles-new-logo&#34;&gt;Sarah Larson&lt;/a&gt; complained Google &amp;ldquo;took something we trusted and filed off its dignity.&amp;rdquo;  The Google logo reaches the level of cultural commentary in a general interest magazine because its use is so widespread.&lt;/p&gt;
&lt;h2 id=&#34;logos-in-the-landscape&#34;&gt;Logos in the Landscape&lt;/h2&gt;
&lt;p&gt;As a point of historical comparison, in 1970 designer Saul Bass created a new bell logo for telecommunications company AT&amp;amp;T. When AT&amp;amp;T updated to Bass&amp;rsquo; bell logo they changed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;135,000 Bell System vehicles&lt;/li&gt;
&lt;li&gt;22,000 buildings&lt;/li&gt;
&lt;li&gt;1,250,000 phone booths&lt;/li&gt;
&lt;li&gt;170,000,000 telephone directories&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Those numbers, taken from the description of the imaginative &lt;a href=&#34;https://www.youtube.com/watch?v=xKu2de0yCJI&amp;amp;list=PLNEqylJnMBqTlxSpVfV0CJiMX4oF2cRsh&#34;&gt;1969 pitch video&lt;/a&gt;, capture what was the largest corporate re-branding effort of the time. Although a meandering twenty-six minutes full of dated cinematography, the video makes some still-relevant points about why companies change logos. Starting at 6:09 the narrator describes how logo changes signal to external audiences (customers) and internal audiences (employees) that the organization is a different kind of company with different values.&lt;/p&gt;
&lt;p&gt;Interpretations of what the new Google logo means range from enthusiasts seeing evidence of  a company maturing and becoming more interested in design, to critics observing that the friendly, approachable letters could be a counter-measure against the company&amp;rsquo;s  Orwellian growth.&lt;/p&gt;
&lt;h2 id=&#34;logos-and-nostalgia&#34;&gt;Logos and Nostalgia&lt;/h2&gt;
&lt;p&gt;A negative reaction to the new Google logo is understandable, because any change reminds users that those browser tabs and mobile app icons can be modified at will. When Larson demands Google &amp;ldquo;give us back our serifs,&amp;rdquo; we&amp;rsquo;re reminded that those serifs weren&amp;rsquo;t ours to begin with, but were simply part of the landscape we passed through. Similarly, the Southern Bell pay phones emblazoned with Bass&amp;rsquo; logo were part of the landscape of my childhood, but they weren&amp;rsquo;t mine to control.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/Southernbell_hu_b3a3ecb36dacdc42.png&#34; alt=&#34;Southern Bell logo, https://en.wikipedia.org/wiki/Southern_Bell#/media/File:Southernbell.png, used under fair use guidelines.&#34; width=&#34;740&#34; height=&#34;190&#34;&gt;
&lt;br&gt;
&lt;em&gt;Southern Bell logo (1970-1983) designed by Saul Bass.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Strong emotional bonds fuel nostalgia for lost logos. Given the place that NASA (the United States&amp;rsquo; National Aeronautics and Space Administration) holds in the hearts of many Americans, it&amp;rsquo;s not surprising that the organization&amp;rsquo;s retired logo – which was part of a set of graphics standards created by design firm Danne &amp;amp; Blackburn – is still revered. A recent &lt;a href=&#34;https://www.kickstarter.com/projects/thestandardsmanual/reissue-of-the-1975-nasa-graphics-standards-manual&#34;&gt;crowd-funded campaign&lt;/a&gt; to republish the 1975 NASA Graphics Standards Manual as a hardcover book ballooned past its goal the day it launched, even though those standards are &lt;a href=&#34;https://www.nasa.gov/sites/default/files/atoms/files/nasa_graphics_manual_nhb_1430-2_jan_1976.pdf&#34;&gt;available free as a PDF&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/NASA_hu_e90cdf6c70832e7a.jpg&#34; alt=&#34;NASA Graphics Standards Manual by Display Graphic Design Collection, https://www.flickr.com/photos/thisisdisplay/, used under CC-BY-NC-ND 2.0&#34; width=&#34;740&#34; height=&#34;494&#34;&gt;
&lt;br&gt;
&lt;em&gt;Page from the 1975 &lt;a href=&#34;https://www.flickr.com/photos/thisisdisplay/6112626281/&#34;&gt;NASA Graphics Standards Manual&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Danne &amp;amp; Blackburn&amp;rsquo;s logo is more than the beneficiary of nostalgia. It&amp;rsquo;s a powerful, simple design classic of extraordinary flexibility. Their logo is successful in sizes ranging from icon on a business card to the exterior of the Hubble Telescope, where it continues to orbit the Earth today.&lt;/p&gt;
&lt;h2 id=&#34;brand-guidelines-for-correct-and-incorrect-use-of-logos&#34;&gt;Brand Guidelines for Correct and Incorrect Use of Logos&lt;/h2&gt;
&lt;p&gt;The &lt;a href=&#34;https://www.nasa.gov/image-article/nasa-graphics-standards-manual/&#34;&gt;NASA Graphics Standards Manual&lt;/a&gt; is one example of brand guidelines. Unlike logos, where everyone is entitled to an opinion on whether they like or dislike the styling, brand guidelines go beyond style preferences to create an independent system by which design choices can be judged to be right (&amp;ldquo;on brand&amp;rdquo;) or wrong (&amp;ldquo;off brand&amp;rdquo;).&amp;quot; You may think that a particular logo is badly done or not to your taste, but still be able to conclude that it is used correctly if it follows the brand guidelines.&lt;/p&gt;
&lt;p&gt;Mozilla&amp;rsquo;s &lt;a href=&#34;https://www.mozilla.org/en-US/styleguide/identity/mozilla/branding/&#34;&gt;brand guidelines&lt;/a&gt; are unusual because they allow use of any solid color. New York University&amp;rsquo;s &lt;a href=&#34;http://www.nyu.edu/content/dam/nyu/advertisePublications/documents/standards/CentralAdmin_Visual_Identity.pdf&#34;&gt;visual identity (PDF)&lt;/a&gt; is more typical in describing exact colors, sizes, positions, and how to use the logo correctly. The American Red Cross&amp;rsquo; &lt;a href=&#34;http://www.redcross.org/about-us/media-resources/logo/brand-standards&#34;&gt;brand standards&lt;/a&gt; include downloadable logos, which are important for reassuring participants of a high-quality experience when a community center hosts an official blood drive.&lt;/p&gt;
&lt;h2 id=&#34;why-secure-communication-needs-brand-guidelines&#34;&gt;Why Secure Communication Needs Brand Guidelines&lt;/h2&gt;
&lt;p&gt;Brand guidelines ensure consistency when many different people are working on a product. This is an important component for building trust with end-users. It&amp;rsquo;s crucial for secure communication projects in particular because lay users can&amp;rsquo;t assess the underlying cryptography. Instead, they assess how trustworthy something is by the user experience, and consistent brand expression is a key part of that. As a counterexample, consider how a sloppily-implemented logo in an email can alert people to a phishing scam by signaling untrustworthiness.&lt;/p&gt;
&lt;p&gt;Logos and brand guidelines communicate trust, and giving mass users confidence that open-source secure communications tools are trustworthy is an important step to driving adoption.&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;&lt;sup&gt;Image of &lt;a href=&#34;https://en.wikipedia.org/wiki/Southern_Bell#/media/File:Southernbell.png&#34;&gt;Southern Bell logo&lt;/a&gt;, used
under fair use guidelines&lt;/sup&gt;&lt;/p&gt;
&lt;p&gt;&lt;sup&gt;Image of &lt;a href=&#34;https://www.flickr.com/photos/thisisdisplay/6112626281/&#34;&gt;NASA Graphics Standards Manual&lt;/a&gt; by &lt;a href=&#34;https://www.flickr.com/photos/thisisdisplay/&#34;&gt;Display Graphic Design Collection&lt;/a&gt;, used
under &lt;a href=&#34;https://creativecommons.org/licenses/by-nc-nd/2.0/&#34;&gt;CC-BY-NC-ND 2.0&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Art, Design, and the Future of Privacy</title>
      <link>https://superbloom.design/learning/blog/nyc-event/</link>
      <pubDate>Wed, 09 Sep 2015 16:09:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/nyc-event/</guid>
      <description>&lt;p&gt;&lt;em&gt;We&amp;rsquo;re headed to NYC next week for our annual Advisors&amp;rsquo; Meeting. While we&amp;rsquo;re there we&amp;rsquo;re thrilled to be partnering with Dis Magazine to host Art, Design, and the Future of Privacy. If you&amp;rsquo;re in the area, please join us; the event is free and open to the public.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;730pm-thursday-sept-17&#34;&gt;7:30pm, Thursday Sept 17&lt;/h2&gt;
&lt;h3 id=&#34;pioneer-works-brooklyn&#34;&gt;Pioneer Works, Brooklyn&lt;/h3&gt;
&lt;p&gt;Join cryptographers, critical theorists, architects, designers, sociologists, user experience researchers and other bright luminaries for a casual evening discussing privacy, the culture of technology, and possibilities for creative intervention in the age of ubiquitous digital tracking. The conversation will be rich, fun, and move from the stage to the audience to end the night with a party feeling and plenty of shared discussion.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/adfp-flyers_hu_7198aa29205cc710.png&#34; alt=&#34;Event flyer&#34; width=&#34;740&#34; height=&#34;957&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Human rights meets design challenges&lt;/strong&gt;
&lt;em&gt;Scout Sinclair Brody&lt;/em&gt;
Scout discusses our collective obsession and fatigue with technology, and the rights and responsibilities of artists, designers, and clear-thinking technologists within this context. How can we all work to make technology better for us as individuals and as a society?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Digital Privacy IRL: Architecture, public space, and its role in preserving online rights&lt;/strong&gt;
&lt;em&gt;Moderated by Ame Elliott&lt;/em&gt;
Noah Biklen and Sarah Gold examine the role of built space, public space, and spatial metaphors in the preservation of privacy and digital rights.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;If you build it they won’t care: Designing privacy-preserving technologies for people with other interests&lt;/strong&gt;
&lt;em&gt;Moderated by Scout Sinclair Brody&lt;/em&gt;
Tyler Reinhard, Ame Elliott, and Harlo Holmes discuss the deployment of “privacy-preserving technologies,” the role of design and critical engagement in this process, and the needed creative interventions that help these efforts resonate with the rest of us.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Ask a Prison Librarian about privacy, technology, and state control&lt;/strong&gt;
&lt;em&gt;Cory Doctorow interviewing Sarah Ball&lt;/em&gt;
Cory talks with Sarah about the lives of people in prison, the fraught conception of “the private individual”, and the intersection between human rights, state control, and privacy.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;No, thank you: Agency, imagination, and possibilities for rejecting world-changing technological innovation&lt;/strong&gt;
&lt;em&gt;Moderated by Meredith Whittaker&lt;/em&gt;
Kate Crawford, Lauren McCarthy, and Allison Burtch examine the role of human-centered approaches and critical discourse in the conception “technology for social justice,” and speculate on the moves necessary to enable local communities (et. al) to reject globally celebrated “disruptions.”&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Where to from here?&lt;/strong&gt;
&lt;em&gt;Cory Doctorow&lt;/em&gt;
Cory closes the evening with hopeful practicalities. Where can we direct our attention if we value privacy, have views on technology, and want to build more creative and relevant interventions?&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Briar: Notes From An Expert Review</title>
      <link>https://superbloom.design/learning/blog/briar-expert-review/</link>
      <pubDate>Fri, 04 Sep 2015 15:20:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/briar-expert-review/</guid>
      <description>&lt;p&gt;Researchers who want to evaluate software interfaces have a number of tools at their disposal. One option for identifying obvious and significant problems is an expert review, which is often used to catch low-hanging fruit before performing any kind of user testing. Expert reviews employ &lt;a href=&#34;http://www.nngroup.com/articles/ten-usability-heuristics/&#34;&gt;usability heuristics&lt;/a&gt;, which systematically explore potential problems with a piece of software by applying patterns for good design.&lt;/p&gt;
&lt;p&gt;With some guidance from UX-research veteran &lt;a href=&#34;https://about.me/susanfarrell&#34;&gt;Susan Farrell&lt;/a&gt;, we recently performed expert reviews of a few open source tools for encrypting communications. Each expert review included evaluation by myself and at least one additional researcher; many thanks to &lt;a href=&#34;https://twitter.com/hcisec&#34;&gt;Arne Renkema-Padmos&lt;/a&gt;, &lt;a href=&#34;http://www.robertstribley.com/&#34;&gt;Robert Stribley&lt;/a&gt;, and &lt;a href=&#34;https://github.com/ei8fdb&#34;&gt;Bernard Tyers&lt;/a&gt; for their work on this project. During the review we described issues and took screenshots to illustrate them. After prioritizing the issues by severity and picking our top 15, we compared our findings with one another and synthesized them into a single report.&lt;/p&gt;
&lt;p&gt;One of the tools we reviewed was &lt;a href=&#34;https://briarproject.org/&#34;&gt;Briar&lt;/a&gt;, an open source peer-to-peer communications application for Android. Briar uses a range of communications methods — Bluetooth, Wi-Fi, or Tor — to provide users end-to-end encryption for messaging.&lt;/p&gt;
&lt;p&gt;We picked Briar to review because the development team expressed readiness (and eagerness!) to get and incorporate feedback. You can access our full report &lt;a href=&#34;https://medium.com/@gusandrews/expert-review-briar-a-p2p-messaging-app-33413034005f&#34;&gt;here&lt;/a&gt;. Below are a few insights regarding visibility, an important element of successful user interfaces.&lt;/p&gt;
&lt;h2 id=&#34;visibility&#34;&gt;Visibility&lt;/h2&gt;
&lt;p&gt;An overarching issue that Briar has, which it shares with a number of applications in the FLOSS secure tools space, is a lack of visibility into system and messaging status. Researchers found it unclear how Briar was connecting to the network at a particular moment in time – was it via Bluetooth, Wi-Fi, or Tor? – making it hard to troubleshoot when a connection was not working. Status icons do not make it clear when Briar is running versus when Briar is actually connected.&lt;/p&gt;
&lt;p&gt;Additionally, Briar does not yet do a thorough job of indicating when a message has been delivered. Because Briar can only deliver messages when a user is online, it can be hard to tell whether a message has made it through to the recipient. Briar also does not display an icon on its main screen to indicate when new messages have arrived.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/briar-screenshot_hu_cfcbc325ef26062b.png&#34; alt=&#34;Screenshot of Briar mobile interface&#34; width=&#34;740&#34; height=&#34;519&#34;&gt;

&lt;em&gt;Briar&amp;rsquo;s main screen currently does not provide a flag to make visible when new messages have arrived, requiring the user to dig into &amp;lsquo;Contacts&amp;rsquo; or &amp;lsquo;Forums&amp;rsquo; to discover them.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Visibility is a crucial principle of usable design. Users need indications that they are correctly understanding the status of the system, that it has changed, or that they need to take action. While we were successful at using Briar to get a message to friends in the same room (the case which we tested), a clearer picture of where messages were in transit would have helped us better understand when and why we were having trouble.&lt;/p&gt;
&lt;p&gt;See the full report on our review of Briar &lt;a href=&#34;https://medium.com/@gusandrews/expert-review-briar-a-p2p-messaging-app-33413034005f&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Usability and Security: Not Binary Properties</title>
      <link>https://superbloom.design/learning/resources/not-binary-properties/</link>
      <pubDate>Fri, 28 Aug 2015 15:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/not-binary-properties/</guid>
      <description>&lt;p&gt;People who think about computer security for a living sometimes cringe when they read about the subject in the popular press. Security is a complex and nuanced topic, and it’s easy to make assertions that don’t hold up to careful scrutiny.&lt;/p&gt;
&lt;p&gt;One basic-but-unintuitive principle is that security is not a binary property: in the absence of other context, it’s hard to definitively say that a particular system or piece of software is “secure” or “insecure”. We can only say that a system is secure against a particular threat, or – more usefully – against a collection of threats, known as a “threat model”.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/justice-statue-small_hu_d7b6771109a57a39.jpg&#34; alt=&#34;Justitia, Tehran Courthouse. Image CC BY-SA 3.0, Abolhassan Khan Sadighi,&#34; width=&#34;740&#34; height=&#34;1023&#34;&gt;
&lt;br&gt;
&lt;em&gt;Justitia, Tehran Courthouse.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;For example, some people might say that using a VPN while browsing the web from a coffee shop is “secure”, because it prevents the jerk across the street with a &lt;a href=&#34;https://en.wikipedia.org/wiki/Cantenna&#34;&gt;cantenna&lt;/a&gt; from listening in and seeing what websites you go to. But if your threat model includes listeners with devices housed with internet service providers (or a government that &lt;a href=&#34;http://www.dailydot.com/politics/iran-censorship-circumvention-tech/&#34;&gt;operates VPNs&lt;/a&gt;), you might instead refer only to an option like &lt;a href=&#34;https://www.torproject.org/&#34;&gt;Tor&lt;/a&gt; as “secure”.&lt;/p&gt;
&lt;p&gt;As someone who has spent a lot of time thinking about security, it’s tempting to dismiss things as “insecure” when they don’t protect against the threats that I’m personally concerned about. Go too far down that path, though, and we find ourselves in a world where only the products that protect against the most extreme threats are considered acceptable. As with transportation safety and public health, we have to recognize that getting people to adopt a “good enough” solution – at least as a first step – is usually better than having them not change their behavior at all. In other words: it’s important to not let the perfect be the enemy of the good!&lt;/p&gt;
&lt;p&gt;Just as security is not a binary property, it’s also important to not think of usability as an all-or-nothing game. Design thinking encourages us to ask not just whether humans in general find a piece of software usable, but to explore 1) the circumstances in which different groups of users might be motivated to use the software and 1) the needs that a piece of software must meet in order to sustain that motivation.&lt;/p&gt;
&lt;p&gt;I think that this distinction is particularly important for software developers to bear in mind. It’s easy to get discouraged when someone tells you that the code you’ve slaved over “isn’t usable”. (Or get defensive – after all, there are plenty of people who seem to find it useable enough, or there wouldn’t be anyone to file all those feature requests.) I challenge you instead to dig deeper, and try to understand exactly what things the user found frustrating about their experience, and what expectations they had using the software that may be mismatched against the assumptions you have made in designing it.&lt;/p&gt;
&lt;p&gt;Just as we can only say that software is “secure” against certain threats, so too must we define “usability” as a function of particular users with particular needs, backgrounds, and expectations. Working to understand those users will ultimately help our community build better software.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Design Thinking</title>
      <link>https://superbloom.design/learning/blog/design-thinking/</link>
      <pubDate>Fri, 21 Aug 2015 17:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/design-thinking/</guid>
      <description>&lt;p&gt;The latest Harvard Business Review (paywall, but with limited free content) has two articles about design thinking that are relevant for teams working on security and privacy: &lt;a href=&#34;https://hbr.org/2015/09/design-for-action&#34;&gt;Design for Action&lt;/a&gt; by Tim Brown and Roger Martin and &lt;a href=&#34;https://hbr.org/2015/09/design-thinking-comes-of-age&#34;&gt;Design Thinking Comes of Age&lt;/a&gt; by Jon Kolko. These articles describe how design thinking has moved beyond creating tangible products and on to supporting collaborative design of complex systems. They give an overview of design thinking’s evolution, from its roots in Herbert Simon’s &lt;em&gt;The Sciences of the Artificial&lt;/em&gt;, through Richard Buchanan’s &lt;a href=&#34;https://web.mit.edu/jrankin/www/engin_as_lib_art/Design_thinking.pdf&#34;&gt;Wicked Problems in Design Thinking&lt;/a&gt;, and into addressing challenges for domains far outside areas historically considered “design.”&lt;/p&gt;
&lt;p&gt;Each article presents an easy-to-understand list: one that presents problems, another that offers solutions.&lt;/p&gt;
&lt;h2 id=&#34;getting-past-common-criticisms&#34;&gt;Getting Past Common Criticisms&lt;/h2&gt;
&lt;p&gt;Brown and Martin highlight how design thinking can facilitate organizational change – including stakeholder buy-in – that helps teams get past common criticisms of work in progress.&lt;/p&gt;
&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;This doesn’t address the problems I think are critical.&lt;/li&gt;
&lt;li&gt;These aren’t the possibilities I would have considered.&lt;/li&gt;
&lt;li&gt;These aren’t the things I would have studied.&lt;/li&gt;
&lt;li&gt;This isn’t an answer that’s compelling to me.
&amp;ndash; Common negative reactions from &lt;a href=&#34;https://hbr.org/2015/09/design-for-action&#34;&gt;Design for Action&lt;/a&gt;, by Tim Brown and Roger Martin&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;These criticisms occur in many contexts, including secure communications, and although the example in the article is of a CEO critiquing a consultant, the criticisms will probably be familiar to open-source developers too.&lt;/p&gt;
&lt;h2 id=&#34;principles-for-a-design-centric-culture&#34;&gt;Principles for a Design-Centric Culture&lt;/h2&gt;
&lt;p&gt;Kolko’s article describes principles of a design-centric culture that help teams get past traditional criticism and get unstuck.&lt;/p&gt;
&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;Focus on users’ emotional experiences&lt;/li&gt;
&lt;li&gt;Create models to examine complex problems&lt;/li&gt;
&lt;li&gt;Use prototypes to explore potential solutions&lt;/li&gt;
&lt;li&gt;Tolerate failure&lt;/li&gt;
&lt;li&gt;Exhibit thoughtful restraint.
&amp;ndash; From &lt;a href=&#34;https://hbr.org/2015/09/design-thinking-comes-of-age&#34;&gt;Design Thinking Comes of Age&lt;/a&gt; by Jon Kolko&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;Thoughtful restraint is particularly tough for open-source efforts because the collaborative nature of decision-making can lead to compromises resulting in an ever-longer feature list rather than necessary editing. For an example of thoughtful restraint in action, check out Open Whisper Systems’ &lt;a href=&#34;https://github.com/signalapp/Signal-Android/blob/main/CONTRIBUTING.md#development-ideology&#34;&gt;Development Ideology&lt;/a&gt;: “The answer is not more options. If you feel compelled to add a preference that&amp;rsquo;s exposed to the user, it&amp;rsquo;s very possible you&amp;rsquo;ve made a wrong turn somewhere.”&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Empathy In The Real World</title>
      <link>https://superbloom.design/learning/blog/empathy-in-the-real-world/</link>
      <pubDate>Fri, 14 Aug 2015 16:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/empathy-in-the-real-world/</guid>
      <description>&lt;p&gt;As a practitioner of Human-Centered Design, empathy is a core skill in the work I do. In &lt;a href=&#34;https://medium.com/@duretti/no-flex-zone-empathy-driven-development-aebf4d8cf7cf&#34;&gt;No Flex Zone: Empathy Driven Development&lt;/a&gt;, Duretti Hirpa writes about how empathy can be a competitive advantage.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“We build software for all kinds of people, and empathy helps us to connect to these disparate audiences. We have to choose empathy, but I’d argue, it’s undeniably the ‘one weird trick’ to future-proofing the software engineering.”
– Duretti Hirpa&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Simply Secure chooses empathy, and we believe that understanding the lives of end-users is an essential element in building empathy for them. Here are some security-focused resources for building empathy. These are useful not only because they explain use scenarios for different technologies but also because they paint vivid pictures of users’ priorities and motivations.&lt;/p&gt;
&lt;p&gt;Swift on Security writes &lt;a href=&#34;https://korvys.tumblr.com/post/128982454345/a-story-about-jessica/amp&#34;&gt;A Story About Jessica&lt;/a&gt;, a fictionalized 17-year-old interested in biology and her boyfriend. She is currently worried about getting a scholarship for college and getting evicted from the apartment she shares with her mother. To make matters worse, Jessica unwittingly infects her hand-me-down laptop with spyware and doesn’t even know it, since she trusts the accuracy of the reassuring “protected” message she sees from her anti-virus software. This story is consistent with the finding shared by Iulia Ion, Rob Reeder, and Sunny Consalvo that &lt;a href=&#34;http://googleonlinesecurity.blogspot.com/2015/07/new-research-comparing-how-security.html&#34;&gt;non-experts rely on anti-virus software&lt;/a&gt; for all their security needs.&lt;/p&gt;
&lt;p&gt;Eleanor Saitta gives detailed &lt;a href=&#34;http://dymaxion.org/essays/usecases.html&#34;&gt;Real World Use Cases for High-Risk Users&lt;/a&gt;, explaining how applications like Facebook are essential emotional supports for vulnerable people, and that Facebook over Tor can help keep them safe. Details like a controlling husband making his wife get rid of her phone after a cross-country move can help tool developers build empathy for people who would benefit from their services. It can also help technologists make “compromises,” such as interoperating with services like Facebook that may be problematic from a security point of view, more desirable.&lt;/p&gt;
&lt;p&gt;Simply Secure fellow Gus Andrews’ &lt;a href=&#34;https://medium.com/@gusandrews/user-personas-for-security-and-privacy-a8b35ae5a63b&#34;&gt;User Personas for Security and Privacy&lt;/a&gt; build on work from Saitta and others to share personas from around the globe, important for helping developers make technologies that are accessible to people in contexts different than their own. The example of a human-rights activist from the Democratic Republic of Congo contains some helpful nuance – for example, that she needs “to take a break from the stress of worrying for her safety and meeting with victims of violence.” Social technologies are one way that people escape and relax, so this activist may get important emotional benefits from using “insecure” applications.&lt;/p&gt;
&lt;p&gt;Working on secure communications is important because we have the chance to improve people’s lives by making critical tools meet their needs more closely. As Saitta writes about a woman living in a shelter’s Facebook use, “That account has been her one lifeline to contacting people, and not only is it crucial for her to be able to access it, it&amp;rsquo;s been an emotional lifeline for her for years. Losing access to it radically lowers her long-term chances of not only getting to safety but also of living a happy life later on.”&lt;/p&gt;
&lt;p&gt;Doing user research is a powerful and efficient way to build empathy, and I encourage everyone to spend time in the field, talking with people about their lives and how technology fits (or doesn’t fit) into it. One starting point when having such conversations is the USDS &lt;a href=&#34;https://methods.18f.gov/&#34;&gt;18F Method Cards&lt;/a&gt;, which are an open-source resource for structuring user research. The cards on &lt;a href=&#34;https://methods.18f.gov/archive/bodystorming/&#34;&gt;bodystorming&lt;/a&gt; and &lt;a href=&#34;https://methods.18f.gov/stakeholder-and-user-interviews/&#34;&gt;user interviews&lt;/a&gt; from the Discover section are particularly relevant for gaining insight that helps establish an empathetic connection with users.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Missing Trouble: In Memoriam</title>
      <link>https://superbloom.design/learning/blog/missing-trouble-in-memoriam/</link>
      <pubDate>Fri, 07 Aug 2015 16:12:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/missing-trouble-in-memoriam/</guid>
      <description>&lt;p&gt;This week we are marking the sudden passing of our Operations Manager, Nóirín “Trouble” Plunkett, who introduced
themselves &lt;a href=&#34;https://superbloom.design/learning/blog/hello-trouble/&#34;&gt;here&lt;/a&gt; just a few short months ago. We are
heartbroken, and it has been hard to come to terms with this unexpected loss. Ame and I attended a memorial service
in their honor this week in Boston, and we have been reading the multitude of memorials that have been posted online
(including &lt;a href=&#34;https://medium.com/@quince/n%C3%B3ir%C3%ADn-go-lonra%C3%AD-solas-suthain-orthu-231c0eb42453&#34;&gt;this&lt;/a&gt; one by Kaia Dekker, which deeply resonated with us).&lt;/p&gt;
&lt;p&gt;While we did not know Trouble for very long – our organization is new, and they started with us in March – their
impact was immeasurable. They were a force of organization (of financials and file systems) and a source of productive
rhythm (for newsletters, blog posts, and social media). They proofread our writing, cheered us on in our outreach, and
lightened our work with wit and good humor. They wrangled our HTML, managed our Git repo, and had a talent for finding
beautiful open-licensed images (Ame often joked that Trouble seemed to be using a better internet than she was).&lt;/p&gt;
&lt;p&gt;Trouble was also a vocal advocate of openness, and one of its greatest champions as we work to integrate the open-source
ethos into our collaborative design efforts. In their short time with our new organization, they helped us create a
foundation of honesty, precision, and compassion for the work we do. We will honor their memory by building on their
contributions, maintaining a rigorous commitment to openness, and methodically trying to make the world a better place,
one project at a time.&lt;/p&gt;
&lt;p&gt;There are no words that can adequately express our sadness or our appreciation for the short time we shared with Trouble.
They were an irreplaceable treasure, and we miss them sorely.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Kids’ Online Privacy: SOUPS Conference Keynote</title>
      <link>https://superbloom.design/learning/blog/soups-keynote/</link>
      <pubDate>Fri, 31 Jul 2015 16:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/soups-keynote/</guid>
      <description>&lt;p&gt;Last week I went to the &lt;a href=&#34;https://cups.cs.cmu.edu/soups/2015/program.php&#34;&gt;SOUPS&lt;/a&gt; conference in Ottawa. As a first-time attendee, it was a good opportunity to connect with some members of the academic usable-security community. One of the highlights was keynote speaker &lt;a href=&#34;https://socialsciences.uottawa.ca/crm/professor-profile?id=36&amp;amp;pageID=1&#34;&gt;Valerie Steeves&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Steeves, sharing findings from her &lt;a href=&#34;https://mediasmarts.ca/research-and-evaluation/young-canadians-wireless-world/ycww-phase-iii/young-canadians-wired-world-phase-iii-life-online&#34;&gt;Young Canadians in a Wired World&lt;/a&gt; research, reported results of an in-depth study of 5,436 Canadians in Grades 4-11. Based on a survey and in-person discussions, she shared sobering findings that kids’ expectations of online privacy are not being met. Alarmingly, 68% of respondents agreed with the incorrect statement that “If a website has a privacy policy, that means it will not share my personal information with others.”&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://mediasmarts.ca/sites/default/files/images/publication-report/infographic-YCWWIII-Life-Online.pdf&#34; alt=&#34;2013 Summary of Young Canadians’ Online Behaviors&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;2013 Summary of Young Canadians’ Online Behaviors, from &lt;a href=&#34;https://mediasmarts.ca/research-and-evaluation/young-canadians-wireless-world&#34;&gt;Young Canadians in a Wireless World&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Steeves also explained specific ways that the corporate, for-profit internet is harmful to children. She particularly called out commercial surveillance – for example, Club Penguin’s rules for policing other community members – as harmful for reinforcing gendered stereotypes and setting kids up for conflict with each other.&lt;/p&gt;
&lt;p&gt;Using quotes, she captured the frustration young people felt at being forced to agree to consent to privacy behaviors they don’t want in order to participate with their friends.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“If we had a choice to say no, I would chose no. We can’t, or else we can’t go on the thing…” – Young Canadians in a Wired World study participant on agreeing to undesirable website terms.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Being able to spend time online with friends is tremendously important, so the participants were repeatedly willing to make privacy compromises to be able to participate.&lt;/p&gt;
&lt;p&gt;The qualitative research shared in this presentation is a powerful motivator for giving people more control over their privacy and has an important role in informing design directions.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Behind-the-Scenes: Emerging Conversations from Slack</title>
      <link>https://superbloom.design/learning/blog/conversations-from-slack/</link>
      <pubDate>Tue, 21 Jul 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/conversations-from-slack/</guid>
      <description>&lt;p&gt;Thank you to everyone contributing to the Simply Secure Slack channel. If you’re interested in joining, email &lt;a href=&#34;mailto:slack@superbloom.design&#34;&gt;slack@superbloom.design&lt;/a&gt; for an invitation. I’m especially eager to get more UX people in privacy and security involved, so spread the word. Here are some highlights from our recent Slack conversations.&lt;/p&gt;
&lt;h2 id=&#34;sharing-the-rationale-for-ux-decisions&#34;&gt;Sharing the Rationale for UX Decisions&lt;/h2&gt;
&lt;p&gt;Check out Gabriel Tomescu’s &lt;a href=&#34;https://medium.com/user-experience-design-1/the-anatomy-of-a-credit-card-payment-form-32ec0e5708bb&#34;&gt;The Anatomy of a Credit Card Form&lt;/a&gt; sharing the &lt;a href=&#34;https://www.waveapps.com/&#34;&gt;Wave&lt;/a&gt; design team’s process for arriving at an elegant, easy-to-use form. It includes a quote that spoke to me, “Given the existing mental model of paying with credit cards online, we felt the presence of one lock icon was sufficient.” Indeed.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/creditcardentry_hu_39bf325c2e2af89e.png&#34; alt=&#34;Subtle improvements to Wave’s credit card form&#34; width=&#34;740&#34; height=&#34;497&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Subtle improvements to &lt;a href=&#34;https://www.waveapps.com/&#34;&gt;Wave’s&lt;/a&gt; credit card form&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;communicating-technical-benefits-vs-user-benefits&#34;&gt;Communicating Technical Benefits vs. User Benefits&lt;/h2&gt;
&lt;p&gt;Stewart Butterfield wrote &lt;a href=&#34;https://medium.com/accel-insights/we-dont-sell-saddles-here-4c59524d650d&#34;&gt;We Don’t Sell Saddles Here&lt;/a&gt;, which speaks eloquently to selling benefits of &lt;em&gt;horseback-riding&lt;/em&gt;, not saddles. A technically savvy crypto audience will happily geek out about the details of different saddles. Meanwhile everyday computer users are still puzzling, “This helps me ride a horse? But why? And how does this help?”.&lt;/p&gt;
&lt;h2 id=&#34;security-cuddly-and-fierce&#34;&gt;Security: Cuddly and Fierce&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;https://www.tunnelbear.com/&#34;&gt;Tunnel Bear’s&lt;/a&gt; brand is more about horseback-riding than saddles. Their website doesn’t lead with “VPN” to describe what it is. Instead of shields, locks, or keys they use bears. Bears!&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/tunnelbearhiding_hu_2797d197a969583c.png&#34; alt=&#34;Tunnel Bears are approachably cuddly, but also fierce&#34; width=&#34;740&#34; height=&#34;605&#34;&gt;
&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/tunnelbearpricing_hu_f20fcfa78abd87b1.png&#34; alt=&#34;Tunnel Bears are approachably cuddly, but also fierce&#34; width=&#34;740&#34; height=&#34;400&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Tunnel Bears are approachably cuddly, but also fierce&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Look for me at &lt;a href=&#34;https://cups.cs.cmu.edu/soups/2015/program.php&#34;&gt;SOUPS&lt;/a&gt; in Ottawa this week. I’ll be presenting a lightning talk on ”Security is Not Enough: Design for Security Engagement” on Thursday afternoon. I’d love to chat if you’re there.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Closing the Participation Gap: HotPETS Presentation Summary</title>
      <link>https://superbloom.design/learning/blog/hotpets-presentation-summary/</link>
      <pubDate>Fri, 17 Jul 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/hotpets-presentation-summary/</guid>
      <description>&lt;p&gt;I really enjoyed being part of the emerging-work track, &lt;a href=&#34;https://petsymposium.org/2015/hotpets.php&#34;&gt;HotPETS&lt;/a&gt;, at the Privacy Enhancing Technologies Symposium earlier this month. From meeting lots of great people to getting face-time with the Simply Secure team, Philadelphia was fun.&lt;/p&gt;
&lt;p&gt;Scout and I presented “&lt;a href=&#34;https://petsymposium.org/2015/papers/elliot-simsec-hotpets2015.pdf&#34;&gt;Human-Centered Design for Secure Communication: Opportunities to Close the Participation Gap&lt;/a&gt;” as part of a session on Privacy and Human Behavior. The session also included some nice qualitative work from &lt;a href=&#34;https://petsymposium.org/2015/papers/ganesh-activists-hotpets2015.pdf&#34;&gt;Tactical Technologies&lt;/a&gt; covering the collaborative and social nature of privacy and ethical implications for researchers working with vulnerable populations.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&#34;https://superbloom.design/resources/PETS-Final-2015.pdf&#34;&gt;HotPETS presentation&lt;/a&gt; shared emerging findings from my Listening Tour — a series of semi-structured interviews reporting on perceptions and opportunities for security and privacy.&lt;/p&gt;
&lt;p&gt;The Listening Tour is a series of conversations — 27 so far — with designers, cryptographers, researchers, entrepreneurs, activists, and other potential members of Simply Secure’s community. This activity is part of a Human-Centered Design process to understand the needs and priorities of the stakeholders we serve.&lt;/p&gt;
&lt;p&gt;The biggest surprise from the tour so far has been how poorly the phrase “secure communication” is understood outside the security community. The entrepreneurs and designers I spoke with at professional events — people with no particular interest or awareness of security concerns — guessed “secure communication” to be something related to anti-&lt;a href=&#34;https://en.wikipedia.org/wiki/Doxing&#34;&gt;doxxing&lt;/a&gt; efforts, &lt;a href=&#34;https://en.wikipedia.org/wiki/Bitcoin&#34;&gt;bitcoin&lt;/a&gt;, or specialized tools for doctors and lawyers. There’s definitely work to do in bridging this gap.&lt;/p&gt;
&lt;p&gt;Stay tuned for more as the Listening Tour progresses, but emerging opportunities we have identified so far for closing the participation gap are 1) motivating lay-user adoption and 2) creating a shared vocabulary. The need for a shared vocabulary between designers and cryptographers resonated particularly well in the post-presentation discussion at HotPETS. We’ll be thinking more about how language can smooth collaboration and improve the accessibility of secure communication.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Lessons from Architecture School: Part 3</title>
      <link>https://superbloom.design/learning/resources/lessons-from-architecture-school-3/</link>
      <pubDate>Wed, 08 Jul 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/lessons-from-architecture-school-3/</guid>
      <description>&lt;p&gt;This is the third and final installment in the series on Lessons from Architecture School: Lessons for IoT Security. You can also read the &lt;a href=&#34;https://superbloom.design/learning/resources/lessons-from-architecture-school-1&#34;&gt;first&lt;/a&gt; and &lt;a href=&#34;https://superbloom.design/learning/resources/lessons-from-architecture-school-2&#34;&gt;second&lt;/a&gt; installments, or download &lt;a href=&#34;https://superbloom.design/resources/OReillyUXIoTElliott.pdf&#34;&gt;the presentation&lt;/a&gt;. Thank you to the audience at Solid Conference for good questions and lively discussion.&lt;/p&gt;
&lt;h2 id=&#34;homes-are-more-than-houses&#34;&gt;Homes Are More Than Houses&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Shop houses&lt;/em&gt; are a type of vernacular architecture built throughout Southeast Asia. &lt;a href=&#34;https://en.wikipedia.org/wiki/Vernacular_architecture&#34;&gt;Vernacular architecture&lt;/a&gt; is built using folk knowledge and local customs, typically without the use of an architect.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/shophouses_hu_fd8c73a521c3aded.jpg&#34; alt=&#34;Shop Houses, Singapore. Image CC-BY-NC-ND, Peter Morgan&#34; width=&#34;740&#34; height=&#34;323&#34;&gt;

&lt;em&gt;Shop houses, Singapore.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Shop houses are traditionally two levels with commercial space on the ground floor and a residence above. A typical feature is an awning protecting the street from sun and rain. Local custom, which became law in Singapore in the 1800s, is that the owner maintains the awning over a public passage or sidewalk, creating an interesting interplay between personal responsibility and the common good.&lt;/p&gt;
&lt;p&gt;Despite widespread familiarity with the building type, there are better and worse examples of vernacular architecture because, despite having access to good precedents, not everyone does a good job with implementation. For example, an awning may be both legally required and obviously a good idea, and still be leaky or badly constructed.&lt;/p&gt;
&lt;p&gt;Different types of knowledge — and different types of professional expertise — are necessary to make a successful building, just as they are for making successful security.&lt;/p&gt;
&lt;h2 id=&#34;security-thought-starter&#34;&gt;Security Thought-Starter&lt;/h2&gt;
&lt;p&gt;Don’t roll your own crypto. It’s easy to create a code that you yourself can’t crack that is trivially easy to a pro. Recent &lt;a href=&#34;https://threatpost.com/weak-homegrown-crypto-dooms-open-smart-grid-protocol/112680&#34;&gt;threats to Open Smart Grid&lt;/a&gt; show that creating a home-grown cryptographic solution leaves big vulnerabilities. Working with standard cryptographic libraries is one way to make sure your applications are using best-in-class security. Using open-source libraries also means that you (or experts) can validate the crypto. One venue for learning more is the &lt;a href=&#34;http://www.realworldcrypto.com/rwc2016&#34;&gt;Real World Crypto Conference&lt;/a&gt;, next held in Stanford, CA in January 2016.&lt;/p&gt;
&lt;h2 id=&#34;ux-consideration&#34;&gt;UX Consideration&lt;/h2&gt;
&lt;p&gt;Exposing underlying systems can teach behavior. When electric cars first reached a mass audience, new dashboard interfaces educated drivers on the basics of how these unfamiliar systems work. Many Prius drivers didn’t know how internal combustion engines worked, which meant an explanation only in terms of difference would not be meaningful. Instead, UX design taught a bunch of people how to think about their car’s power source.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/prius_hu_7078a6b9638e0a3.png&#34; alt=&#34;Toyota Prius dashboard. Image CC-BY, It&amp;rsquo;s Our City&#34; width=&#34;740&#34; height=&#34;483&#34;&gt;

&lt;em&gt;Toyota Prius dashboard&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The design decisions in electric car dashboards have changed drivers’ behavior by helping them understand how the system works. Similarly, there is a huge opportunity for designers to create new interfaces to help people communicate securely. For example, simple visualizations of how the internet works could change users’ messaging behavior to become more security aware. The challenge is to show only appropriate complexity and not overwhelm the user with extraneous detail, just as the UX designers for the Prius selected only a few pieces of information that directly respond to changes in driving conditions.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;em&gt;Image of &lt;a href=&#34;https://www.flickr.com/photos/pmorgan/9611965697/&#34;&gt;Shop houses, Singapore&lt;/a&gt; by &lt;a href=&#34;https://www.flickr.com/photos/pmorgan/&#34;&gt;Peter Morgan&lt;/a&gt;, used under &lt;a href=&#34;https://creativecommons.org/licenses/by-nc-nd/2.0/&#34;&gt;CC-BY-NC-ND&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Image of &lt;a href=&#34;https://www.flickr.com/photos/its_our_city/2838668732/&#34;&gt;Toyota Prius dashboard&lt;/a&gt; by &lt;a href=&#34;https://www.flickr.com/photos/its_our_city/&#34;&gt;It&amp;rsquo;s Our City&lt;/a&gt;, used under &lt;a href=&#34;https://creativecommons.org/licenses/by/2.0/&#34;&gt;CC-BY 2.0&lt;/a&gt; (cropped)&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Niaje! Introducing Maina</title>
      <link>https://superbloom.design/learning/blog/hello-maina/</link>
      <pubDate>Wed, 01 Jul 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/hello-maina/</guid>
      <description>&lt;p&gt;I’m Maina, and I&amp;rsquo;m excited to start out as a Senior Fellow at Simply Secure. Prior to this fellowship, I conducted research at the Center for Advanced Security Research Darmstadt, and the &lt;a href=&#34;http://www.tu-darmstadt.de&#34;&gt;Technische Universität Darmstadt&lt;/a&gt;. Using both quantitative and qualitative research methods, I focused on the usability of verification in &lt;a href=&#34;http://www.heliosvoting.org&#34;&gt;Helios&lt;/a&gt;, an end-to-end verifiable, open-source, remote electronic voting system. Previously, I taught several undergraduate courses, including human-computer interaction and computer security. My undergraduate degree is in computer science, and for my master’s degree, I investigated secure protocols for mobile phone voting.&lt;/p&gt;
&lt;p&gt;My previous research had two goals: first, to investigate the usability of verification in Helios, and second, to investigate whether voters are motivated to take up opportunities to verify their vote. With respect to the first research goal, my colleagues and I conducted a cognitive walkthrough and identified &lt;a href=&#34;https://www.usenix.org/conference/evtwote-11/usability-analysis-helios-%E2%80%94-open-source-verifiable-remote-electronic-voting&#34;&gt;obstacles to voter verification in Helios&lt;/a&gt;. We proposed improvements which were integrated and tested in a lab user study. The findings showed that &lt;a href=&#34;http://ieeexplore.ieee.org/xpl/articleDetails.jsp?reload=true&amp;amp;arnumber=6059254&#34;&gt;voters were able to perform verification with the improved Helios&lt;/a&gt;. We also found, using surveys, that despite the usability improvements, &lt;a href=&#34;http://link.springer.com/chapter/10.1007%2F978-3-319-10178-1_20&#34;&gt;voters lacked the motivation to take up verification opportunities&lt;/a&gt;. Furthermore, and with respect to the second research goal, we identified that voters trust the people and processes involved in (paper-based) elections, suggesting that they are &lt;a href=&#34;http://link.springer.com/chapter/10.1007%2F978-3-642-39185-9_9&#34;&gt;insufficiently motivated to take up verification opportunities&lt;/a&gt;. Consequently, we designed &lt;a href=&#34;https://www.ndss-symposium.org/ndss2014/workshop-usable-security-usec-2014-programme/voter-what-message-will-motivate-you-verify-your-vote/&#34;&gt;motivating messages to increase voter verification intention&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;At Simply Secure, I want to continue to focus on user motivation and apply it in the context of secure communication. I want to understand user motivation and how it can better guide secure behavior, focusing specifically on email. My research will concentrate on these three questions: (i) To what extent does a lack of user motivation contribute to the low adoption and use of secure email behaviors?, (ii) How can we motivate users to adopt such behaviors?, and (iii) How can security motivation be integrated effectively into the design of email interfaces? I will focus on the link between user motivation and adoption, and test the impact of motivational interventions. The output of my research should recommend how to increase the uptake of secure email behaviors for the general population.&lt;/p&gt;
&lt;p&gt;Niaje, pronounced &amp;rsquo;ni-a-dʒei&amp;rsquo;, means &amp;ldquo;what&amp;rsquo;s up&amp;rdquo; in Swahili.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Hello Joseph and Kat</title>
      <link>https://superbloom.design/learning/blog/hello-joseph-and-kat/</link>
      <pubDate>Tue, 23 Jun 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/hello-joseph-and-kat/</guid>
      <description>&lt;p&gt;You’ve already met &lt;a href=&#34;https://superbloom.design/learning/blog/hello-gus/&#34;&gt;Gus&lt;/a&gt;, and we’re looking forward to introducing you to Maina, the other Fellow that Simply Secure is hosting under the auspices of Open Tech Fund’s Secure Usability Fellowship Program.&lt;/p&gt;
&lt;p&gt;Ours are not the only SUFP fellows, however – the EFF has been hosting &lt;a href=&#34;http://jbonneau.com/&#34;&gt;Joseph Bonneau&lt;/a&gt; since the start of this year, and Kat Krol started recently as a SUFP Fellow at University College London. We hope to share more about their research later in the year, but in the meantime, here are their introductions, in their own words! (And remember, if you’d like to catch up with any of the Fellows, share your work with them, or ask about what they’re up to, you can find them all on our Slack channel. &lt;a href=&#34;mailto:slack@superbloom.design&#34;&gt;Email us&lt;/a&gt; for an invite!)&lt;/p&gt;
&lt;h3 id=&#34;joseph-bonneau-sufp-fellow-at-eff&#34;&gt;Joseph Bonneau, SUFP Fellow at EFF&lt;/h3&gt;
&lt;p&gt;I&amp;rsquo;m Joseph Bonneau and I&amp;rsquo;m a Secure Usability Fellow working at both the Electronic Frontier Foundation and Stanford. I started in February 2015. My main goals are to improve the state of the art of secure messaging with user-centered cryptographic architectures. In particular, on the EFF side I&amp;rsquo;m working on improving the EFF&amp;rsquo;s Secure Messaging Scorecard and starting next steps of the Campaign for Secure and Usable Crypto. At Stanford I&amp;rsquo;m doing technical work on the CONIKS project to build user-verifiable public key directories for secure messaging tools.&lt;/p&gt;
&lt;p&gt;My background is in cryptography and computer security. I earned my PhD from the University of Cambridge as well as BS and MS degrees in Computer Science from Stanford. I&amp;rsquo;ve worked at Google, Yahoo, and Cryptography Research, Inc. and last year I was a fellow at Princeton University&amp;rsquo;s Center for Information Technology Policy. My research has spanned many topics including passwords and user authentication, cryptocurrencies, HTTPS and web security, privacy in social networks and side-channel cryptanalysis. I also taught the first courses on cryptocurrencies in the past year (both in-person at Princeton and an online MOOC). In my spare time I enjoy the outdoors, triathlons and pub trivia.&lt;/p&gt;
&lt;h3 id=&#34;kat-krol-sufp-fellow-at-ucl&#34;&gt;Kat Krol, SUFP Fellow at UCL&lt;/h3&gt;
&lt;p&gt;My name is Kat Krol. I&amp;rsquo;m a final year PhD student at University College London, UK. In my PhD research, I look at the role of effort in users&amp;rsquo; security and privacy decisions online. I&amp;rsquo;m passionate about conducting user studies of various kinds, always aiming to combine quantitative data with qualitative feedback from participants.&lt;/p&gt;
&lt;p&gt;Today, design and computing are all about fulfilling users&amp;rsquo; every need and want, providing interactions that are pleasurable and seamlessly integrate with their lives. Security is absolutely at odds with this – it disrupts users&amp;rsquo; natural workflow, asks them to heed every warning, check URLs and create complex passwords. The aim of my research is to contribute towards usable security and privacy that are contextually sensitive to human capabilities, needs and preferences.&lt;/p&gt;
&lt;p&gt;During my fellowship, I will be focusing on tools for secure instant messaging looking at their usability and adoption. There is so much technically excellent encryption software out there, that has not been widely adopted due to poor usability and/or a mismatch between what the technology offers and what the users need. I&amp;rsquo;m excited about the first steps, in which I will be conducting focus groups with users of selected messaging apps to learn about their perspective.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>All Your Base Are Belong To Gus</title>
      <link>https://superbloom.design/learning/blog/hello-gus/</link>
      <pubDate>Fri, 19 Jun 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/hello-gus/</guid>
      <description>&lt;p&gt;Hi, everyone! I’m Gus. I am pleased to be joining Simply Secure for a one-year fellowship.&lt;/p&gt;
&lt;p&gt;For the past year and change I worked for the Open Internet Tools Project, where I pioneered their work on security usability. OpenITP being an open source organization, I had the great joy of doing all my work in public, which means everything we did is &lt;a href=&#34;https://medium.com/@gusandrews&#34;&gt;still online&lt;/a&gt; and publicly available. Among the things I did:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;worked to help the community share best practices in usability;&lt;/li&gt;
&lt;li&gt;ran usability-focused hackathons;&lt;/li&gt;
&lt;li&gt;held a monthly meeting of security trainers (which is still ongoing!);&lt;/li&gt;
&lt;li&gt;held workshops to develop security-focused user personas and visual assets;&lt;/li&gt;
&lt;li&gt;ran user tests on a number of tools;&lt;/li&gt;
&lt;li&gt;analyzed tool-building projects’ data on their downloads;&lt;/li&gt;
&lt;li&gt;and wrote analyses of the field.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;My fellowship at Simply Secure will have two parts:&lt;/p&gt;
&lt;p&gt;One part of my job this year will be continuing to do usability work for various secure-tools projects, in a more focused way. I will work with particular projects to identify what their usability needs are and develop solutions specific to their stage of development. These might include design workshops, metrics analysis, expert review, or more user testing.&lt;/p&gt;
&lt;p&gt;The other part of my job will be a more overarching research project that might be useful to a number of tool developers, as well as to the broader community of security trainers, usable-security researchers, and digital literacy educators. Building on the methodology already developed by Arne Renkema-Padmos, I will work with a handful of researchers to assess users’ mental models of how the Internet works. Users will draw out diagrams of what they understand, with “scaffolding” provided by images of Internet elements with which they may be familiar (browsers, routers, etc.). We will then analyze these diagrams to identify patterns in misconceptions, as well as what users already understand.&lt;/p&gt;
&lt;p&gt;Outside of work, I produce &lt;a href=&#34;https://www.youtube.com/user/themediashow&#34;&gt;The Media Show&lt;/a&gt;, a YouTube series about media literacy and digital literacy which I began while writing &lt;a href=&#34;http://www.studyplace.org/wiki/User:Gusandrews/SearchProject/1208chapters&#34;&gt;my dissertation&lt;/a&gt; at Teachers College. Our latest series of episodes answer questions about media and technology drawn from Google Autocomplete — meaning many people have asked them. We’ve got episodes in the works on how ads know your location, how the Internet crosses the ocean, and how hackers find out your passwords. Previously, we’ve done episodes on &lt;a href=&#34;https://www.youtube.com/watch?v=HupyaXuSqMA&#34;&gt;how spam ends up in your email&lt;/a&gt; and &lt;a href=&#34;https://www.youtube.com/watch?v=IBjQ28CqsS4&#34;&gt;how search engines work&lt;/a&gt;. Follow our progress on &lt;a href=&#34;https://youtube.com/themediashow&#34;&gt;YouTube&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I look forward to continuing to work with folks in this space!&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/themediashow_hu_623e5cf6e76d3835.png&#34; alt=&#34;The Media Show&amp;rsquo;s puppets explain how search engines work&#34; width=&#34;740&#34; height=&#34;398&#34;&gt;

&lt;em&gt;The Media Show&amp;rsquo;s puppets explain how search engines work&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Lessons from Architecture School: Part 2</title>
      <link>https://superbloom.design/learning/resources/lessons-from-architecture-school-2/</link>
      <pubDate>Thu, 11 Jun 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/lessons-from-architecture-school-2/</guid>
      <description>&lt;p&gt;This continues &lt;a href=&#34;https://superbloom.design/learning/resources/lessons-from-architecture-school-1&#34;&gt;Part 1 of a series&lt;/a&gt; of posts drawn from a talk I gave at O’Reilly’s online conference &lt;a href=&#34;http://conferences.oreilly.com/experience-design-iot&#34;&gt;Experience Design for Internet of Things (IoT)&lt;/a&gt; on “Lessons from Architecture School for IoT Security.”  You can find the slides for the original talk &lt;a href=&#34;https://superbloom.design/resources/OReillyUXIoTElliott.pdf&#34;&gt;here&lt;/a&gt;. The talk encourages designers to think about security and outlines some ways UX design can support privacy in IoT applications.&lt;/p&gt;
&lt;p&gt;When designing IoT applications for the home, we can take advantage of how much time we spend there by looking critically at the unspoken assumptions homes reveal. Living in a house is something we all unconsciously understand how to do, having learned from watching those around us before we could talk. The home is a rich environment from a cultural anthropology perspective, in part because it encodes tacit knowledge about the people who live there.&lt;/p&gt;
&lt;h2 id=&#34;understanding-unspoken-needs&#34;&gt;Understanding Unspoken Needs&lt;/h2&gt;
&lt;p&gt;Looking at Finland’s &lt;a href=&#34;https://www.kansallismuseo.fi/en/hvittraesk&#34;&gt;Hvitträsk&lt;/a&gt;, a home and architectural studio built in 1903 by Herman Gesellius, Armas Lindgren, and Eliel Saarinen, reveals extensive use of &lt;em&gt;Jugendstil&lt;/em&gt;, or &lt;a href=&#34;http://en.wikipedia.org/wiki/Art_Nouveau&#34;&gt;Art Nouveau&lt;/a&gt;, decor mimicking forms found in nature. Hvitträsk teaches the cultural context of its construction, when Finnish Nationalism was rising as Finland sought to establish a distinct identity from neighboring Sweden and from Russia, who was administering Finland at the time. Nationalism and Romanticism are values that can be decoded by looking carefully at the environment. The combination rug/blanket references coverings used for sleigh rides, and the stained glass figures reference the Kalevala, the Finnish national epic poem. These design choices reflect an emerging national identity.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/hvittraesk_hu_b20d23ca3dbc276e.png&#34; alt=&#34;Hvitträsk, built 1903, boyhood home of architect Eero Saarinen. Image CC-BY-NC, David Castell, https://www.flickr.com/photos/8712554@N02/2797981340/&#34; width=&#34;740&#34; height=&#34;770&#34;&gt;

&lt;em&gt;Hvitträsk, built 1903, boyhood home of architect Eero Saarinen.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Hvitträsk was the boyhood home of Eero Saarinen, well-known as the architect of what was then called the &lt;a href=&#34;http://en.wikipedia.org/wiki/TWA_Flight_Center&#34;&gt;Trans World Airlines Flight Center&lt;/a&gt;, and is still in use by JetBlue passengers as T-5 of John F. Kennedy airport in New York City.  Just 59 years separate the construction of Hvitträsk and the airport, but they included sweeping technical advances, from horse-drawn sleigh to commercial airplanes. One of the unspoken needs of buildings is to endure, and buildings – unlike many forms of IoT hardware – are upgradeable. Buildings are expected to last much longer than the 18-month lifespan of a device designed to become obsolete.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/jfk-t5_hu_e1d0a5dbaff1806d.jpg&#34; alt=&#34;JFK Airport T-5, built 1962 by architect Eero Saarinen. Image CC-BY-NC, Sean Marshall, https://www.flickr.com/photos/7119320@N05/7452651372/&#34; width=&#34;740&#34; height=&#34;479&#34;&gt;

&lt;em&gt;JFK Airport T-5, built 1962 by architect Eero Saarinen.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;security-thought-starter&#34;&gt;Security Thought-Starter&lt;/h2&gt;
&lt;p&gt;Buildings’ long lifespans challenge IoT security paradigms. There’s an inherent tension in the enduring quality of building hardware and the difficulties of keeping connected devices secure over time. Sources including the &lt;a href=&#34;http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=PM&amp;amp;subtype=XB&amp;amp;htmlfid=GBE03620USEN#loaded&#34;&gt;IBM Institute for Business Value&lt;/a&gt; caution that committing to connected building infrastructure, such as smart doorknobs with 20+ year lifespans, carries risks because a smart doorknob needs to be maintained and kept up to date against security threats unknown at the time it was built. Designers need to think critically about the path for upgrading firmware in order to reduce the risk of IoT devices becoming out of date and vulnerable to new security threats. Supervisory Control and Data Acquisition (&lt;a href=&#34;https://en.wikipedia.org/wiki/SCADA&#34;&gt;SCADA&lt;/a&gt;) systems in industrial contexts have long been criticized as insecure, so designers have a chance to learn from that experience and encourage thinking about security as those systems are adapted to home use.&lt;/p&gt;
&lt;p&gt;Routers are one example of a piece of infrastructure with long lifespans, still keeping the internet of ten years ago alive, often with numerous security vulnerabilities.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/firmware-upgrade_hu_432bb83f642188fe.png&#34; alt=&#34;Detail of a router firmware update dialog box. Image CC-BY, Fabian Rodriguez, https://www.flickr.com/photos/magicfab/3893245793/&#34; width=&#34;740&#34; height=&#34;332&#34;&gt;

&lt;em&gt;Detail of a router firmware update dialog box.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;ux-consideration&#34;&gt;UX Consideration&lt;/h2&gt;
&lt;p&gt;One of the simplest ways to protect a computerized system is to install software updates that include security patches, but users often view updating software as unpleasant and disruptive. I call on designers to re-imagine software updates as a moment for positive user engagement and behavior change. Successes in chronic disease management, financial planning, and other difficult topics show that design can change behavior. Let’s translate those successes into information security.&lt;/p&gt;
&lt;p&gt;There are formidable challenges to re-inventing something banal – people unthinkingly rush to dismiss dialog boxes unread – but new interfaces for explaining underlying security systems have the opportunity to create positive change.&lt;/p&gt;
&lt;p&gt;This series continues with Part 3: &lt;a href=&#34;https://superbloom.design/learning/resources/lessons-from-architecture-school-3/&#34;&gt;Homes Are More than Houses&lt;/a&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;&lt;sup&gt;Image of &lt;a href=&#34;https://www.flickr.com/photos/8712554@N02/2797981340/&#34;&gt;Hvitträsk&lt;/a&gt;, by &lt;a href=&#34;https://www.flickr.com/photos/8712554@N02/&#34;&gt;David Casteel&lt;/a&gt; used under &lt;a href=&#34;https://creativecommons.org/licenses/by-nc-nd/2.0/&#34;&gt;CC-BY-NC-ND 2.0&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
&lt;p&gt;&lt;sup&gt;Image of &lt;a href=&#34;https://www.flickr.com/photos/7119320@N05/7452651372/&#34;&gt;T-5, JFK Airport&lt;/a&gt;, by &lt;a href=&#34;https://www.flickr.com/photos/7119320@N05/&#34;&gt;Sean Marshall&lt;/a&gt;, used under &lt;a href=&#34;https://creativecommons.org/licenses/by-nc/2.0/&#34;&gt;CC-BY-NC 2.0&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
&lt;p&gt;&lt;sup&gt;Image of &lt;a href=&#34;https://www.flickr.com/photos/magicfab/3893245793/&#34;&gt;OpenWRT router firmware update&lt;/a&gt; by &lt;a href=&#34;https://www.flickr.com/photos/magicfab/&#34;&gt;Fabian Rodriguez&lt;/a&gt;, used under &lt;a href=&#34;https://creativecommons.org/licenses/by/2.0/&#34;&gt;CC-BY 2.0&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Lessons from Architecture School: Part 1</title>
      <link>https://superbloom.design/learning/resources/lessons-from-architecture-school-1/</link>
      <pubDate>Fri, 05 Jun 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/resources/lessons-from-architecture-school-1/</guid>
      <description>&lt;p&gt;This is the first in a series of posts pulled from a talk I gave at O’Reilly’s online conference &lt;a href=&#34;http://conferences.oreilly.com/experience-design-iot&#34;&gt;Experience Design for Internet of Things (IoT)&lt;/a&gt; on “Lessons from Architecture School for IoT Security.” The talk is a call to action for designers and non-technical people to get involved — with us at Simply Secure or elsewhere — in the worthy problems of experience design for IoT security. I want to encourage more people to think about security and to outline some ways UX design can support privacy in IoT applications. You can find the slides for the original talk &lt;a href=&#34;https://superbloom.design/resources/OReillyUXIoTElliott.pdf&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Many thanks for all the positive comments from the online audience for the talk. I’m glad to see that a few of the participants joined our Slack channel. You should join too — by emailing &lt;a href=&#34;mailto:slack@superbloom.design&#34;&gt;slack@superbloom.design&lt;/a&gt; — if you’re interested in being part of an emerging conversation about security, privacy, design, and more.&lt;/p&gt;
&lt;h2 id=&#34;architecture-school&#34;&gt;Architecture School&lt;/h2&gt;
&lt;p&gt;I studied architecture. Not systems architecture, but actual building architecture. The time I spent in the Colleges of Environmental Design in Boulder, Colorado and Berkeley, California shaped how I think and how I approach problems. No, I can’t tell you if your deck will fall down, and although I may have an opinion on your kitchen remodel, that’s not part of my professional education.&lt;/p&gt;
&lt;p&gt;My background is much closer to what we today call “&lt;a href=&#34;http://en.wikipedia.org/wiki/Design_thinking&#34;&gt;design thinking&lt;/a&gt;” or even “Lean Startup” methods. Architecture school teaches &lt;em&gt;problem finding&lt;/em&gt;, rather than &lt;em&gt;problem solving&lt;/em&gt;, and it’s great preparation for work on many kinds of complex systems. There are many elements of a studio-based architectural education that make it useful for thinking about security, including rapid prototyping and getting feedback during critiques. However, the most relevant quality is how architecture school teaches new ways of seeing how buildings work and how people inhabit them. I’d like to share some of the lessons from architecture school that are applicable to security.&lt;/p&gt;
&lt;h2 id=&#34;calling-designers-iot-security-needs-you&#34;&gt;Calling Designers, IoT Security Needs You&lt;/h2&gt;
&lt;p&gt;Anyone working on a connected-home application is also in the data-collection business, as connecting and collecting go hand-in-hand. &lt;a href=&#34;http://www.theguardian.com/technology/2015/may/17/sold-our-souls-and-more-to-internet-giants-privacy-surveillance-bruce-schneier&#34;&gt;Bruce Schneier’s recent Guardian article&lt;/a&gt; includes examples that speak to designers’ priorities on crafting user experience: Samsung TVs listening in on near-by conversations and Mattel re-selling children’s questions to Hello Barbie dolls. As a designer, I understand the motivation for some of the choices that eventually led to privacy problems, and that some designers haven’t had exposure to the privacy implications of their designs. The desire to create convenient, positive interactions for users can have unintended consequences, and designers have a role to play in safeguarding end-user needs. Beyond that, designers have the power to make conversations about privacy richer than the tension between what’s technically possible and what’s legal. What’s desirable? What’s delightful? Security for IoT needs design.&lt;/p&gt;
&lt;p&gt;Here’s one lesson from architecture school for designing IoT applications with privacy in mind.&lt;/p&gt;
&lt;h2 id=&#34;start-with-people-in-context&#34;&gt;Start with People, In Context&lt;/h2&gt;
&lt;p&gt;Architecture is concerned with creating spaces for people to experience. As a Human-Centered designer, I encourage everyone to get out into the field as much as possible to understand the context. People working on domestic IoT applications should go and meet with people in their homes to get a deeper understanding of how their products fit into the rhythms of home life. But even without doing in-context interviews, looking at examples of how people inhabit space can inform the design of appropriate technology. Most of us spend quite a bit of time in buildings, and critically examining how people inhabit buildings can lead to the design of more Human-Centered IoT products.&lt;/p&gt;
&lt;p&gt;To be deliberately provocative, I’ve selected images for this series that feel historical and far-removed from the current hype around IoT. This one is from the Dutch Golden Age.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/deHooch1670_hu_d8bc8c4625d5a6f8.jpg&#34; alt=&#34;Pieter de Hooch, “Man Handing a Letter to a Woman in the Entrance Hall of a House.” from the Rijksmuseum.&#34; width=&#34;740&#34; height=&#34;858&#34;&gt;

&lt;em&gt;Pieter de Hooch, 1670. “Man Handing a Letter to a Woman in the Entrance Hall of a House.” from the Rijksmuseum.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Looking at this painting with the eyes of an architect, this domestic scene tells us about the values of Dutch society in the 1600s. There are no window coverings, highlighting a social convention around transparency. There are also multiple people visible, each of whom has different privileges in the home. The man delivering the letter could be a guest, who would only have access to the entrance hall or certain semi-public areas of the home. There’s also a dog and a child. Children are an interesting case in the modern context because they are not able to consent to the collection of their data in many situations.&lt;/p&gt;
&lt;p&gt;One method for doing design research is to seek inspiration from observation of &lt;a href=&#34;https://www.designkit.org/methods/extremes-and-mainstreams.html&#34;&gt;extreme users&lt;/a&gt;, or people outside the mainstream who are likely to invest time in creating work-arounds to make technology fit their needs. Extreme users can be helpful participants with well-articulated worldviews, whose experiences can create designs that work well across the entire spectrum of users. Designing to accommodate the needs of a child in a European country — who is protected from unwanted data collection by local regulations — can result in a user experience that works well for all kinds of people, including those eagerly opting in. We can expect additional regulatory constraints around children’s data in the future, so giving attention to these issues now can also help designers future-proof their product.&lt;/p&gt;
&lt;h2 id=&#34;ux-consideration&#34;&gt;UX Consideration&lt;/h2&gt;
&lt;p&gt;Profile managers are examples of interfaces that can contribute to future-proofing by allowing people to opt in or out of data collection.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/netflix-profiles_hu_722e925080c28cd8.png&#34; alt=&#34;Netflix profile manager&#34; width=&#34;740&#34; height=&#34;862&#34;&gt;

&lt;em&gt;Video-streaming service Netflix has an explicit interface for asking viewers to sign in with a profile to interact with their system, but what about other people who may also be watching? There are examples of using mobile phones to passively interact with video viewing systems, such as logging everyone in a group who may be watching at once, but without an explicit login moment, users have no ability to safeguard their privacy by opting out.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Watching videos is a screen-based interaction, but the issues become more complex with ambient systems. We don’t yet have best practices around signing in to ambient systems where an explicit login at a console may not be appropriate. How can we as designers create appropriate interfaces to give users control of ambient IoT systems?&lt;/p&gt;
&lt;h2 id=&#34;security-thought-starter&#34;&gt;Security Thought-Starter&lt;/h2&gt;
&lt;p&gt;There is no single place to turn for guidance on this issue, but the European &lt;a href=&#34;http://ec.europa.eu/justice/data-protection/article-29/index_en.htm&#34;&gt;Article 29 Working Party&lt;/a&gt; is one starting point for understanding privacy protection and data collection mechanisms. If you’re a developer or entrepreneur thinking about collecting data in the home, keep in mind that there need to be ways for people to opt out, whether they’re guests or residents, adults or children.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Plan for change, and don&amp;rsquo;t take on privacy debt in a quickly-changing landscape.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Planning for the ability to opt out of collection by ambient devices can help future-proof emerging design work.&lt;/p&gt;
&lt;p&gt;To learn more about emerging challenges in IoT interfaces, check out the recently released &lt;a href=&#34;http://shop.oreilly.com/product/0636920031109.do&#34;&gt;Designing Connected Products&lt;/a&gt; by Claire Rowland, Elizabeth Goodman, Martin Charlier, Ann Light, and Alfred Lui.&lt;/p&gt;
&lt;p&gt;This series continues with Part 2: &lt;a href=&#34;https://superbloom.design/learning/resources/lessons-from-architecture-school-2&#34;&gt;Understand Unspoken Needs&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>What We Look For in a Software Partner</title>
      <link>https://superbloom.design/learning/blog/what-we-look-for/</link>
      <pubDate>Fri, 29 May 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/what-we-look-for/</guid>
      <description>&lt;p&gt;As we gear up to start collaborating with open-source software projects, there are a bunch of things we have been pondering. There are a lot of compelling projects out there that we’d love to work with, but we need some criteria to choose which ones to focus on first.&lt;/p&gt;
&lt;p&gt;So, we’ve drafted a &lt;a href=&#34;https://superbloom.design/resources/CollaborationQuestions.pdf&#34;&gt;set of questions&lt;/a&gt; to ask about a software project and the team that develops it. As the document notes, these questions are not a quiz to judge the worthiness of projects or the people who work on them. Many questions have no “right” answer, and are included to ultimately help us foster a diverse portfolio of projects aligned with our core goals.&lt;/p&gt;
&lt;p&gt;The questions boil down to the following high-level issues:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What does the software do?&lt;/li&gt;
&lt;li&gt;How is it built, and how is it licensed?&lt;/li&gt;
&lt;li&gt;At whom is it targeted, and who actually uses it?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Again, there are no right or wrong answers to these questions, but we do have some ideas about what types of tools and teams we want to work with first. To start, we are particularly focused on tools that enable &lt;em&gt;secure communication&lt;/em&gt; — multi-way data exchange among end users – although we’re also interested in knowing about tools that perform related functions. Furthermore, we are most interested in working with development teams that are &lt;em&gt;committed to improving the user experience&lt;/em&gt; of their software, and to integrating good design into their ongoing development practices. Finally, as part of our ongoing commitment to publicly-auditable software, we are committed to working on &lt;em&gt;open-source tools&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;We expect this document of criteria to evolve and change over time, so we want to hear your feedback on it. &lt;a href=&#34;https://superbloom.design/contact&#34;&gt;Get in touch&lt;/a&gt; if you have suggestions on how to improve it!&lt;/p&gt;
&lt;p&gt;In a future post, I will describe the models of collaboration we’re currently envisioning. In the meantime, if you are working on a secure-communications software project and you are interested in collaborating with us to evaluate and improve its user experience (or if you’re a software user and want to suggest a team for us to reach out to), please tell us about the project &lt;a href=&#34;https://docs.google.com/a/simplysecure.org/forms/d/1yWK2kIGdC_y0Vz5S-j_jno9P0qelBHeYsHrFuusoysg/viewform&#34;&gt;here&lt;/a&gt;. (Note: this form is hosted by Google. If you’re more comfortable communicating by email, you can also send a message to &lt;a href=&#34;mailto:collab@superbloom.design&#34;&gt;collab@superbloom.design&lt;/a&gt; with answers to &lt;a href=&#34;https://superbloom.design/resources/IntakeQuestions.pdf&#34;&gt;these questions&lt;/a&gt;.)&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Making the Abstract Experiential</title>
      <link>https://superbloom.design/learning/blog/making-the-abstract-experiential/</link>
      <pubDate>Thu, 21 May 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/making-the-abstract-experiential/</guid>
      <description>&lt;p&gt;It’s difficult for many lay users who are unfamiliar with the mechanics of how the internet works to make assessments of risk or to secure their communications. One way that design can help is by making abstract concepts understandable. There’s exciting work in understanding existing models of security and ways to leverage them in design, such as Rick Wash’s &lt;a href=&#34;http://www.rickwash.com/papers/rwash-homesec-soups10-final.pdf&#34;&gt;&amp;ldquo;Folk Models of Home Computer Security&amp;rdquo;&lt;/a&gt;, but there’s still so much to be done.&lt;/p&gt;
&lt;p&gt;As an inspirational example of how design can contribute to making abstract concepts accessible to a lay audience, here’s a 1977 video from designers Charles and Ray Eames. It makes the abstract topic of exponential growth &lt;em&gt;experiential&lt;/em&gt; by relating it to the scale of the human body. Having admired the Eames’ work since my days in architecture school, I think starting with the scale of the human body is a great way to approach problems. The whole 9 minutes is worth a watch to get a sense of the pacing, since timed transitions between views illustrate scale.&lt;/p&gt;
&lt;div style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
      &lt;iframe allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen&#34; loading=&#34;eager&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; src=&#34;https://www.youtube.com/embed/0fKBhvDjuy0?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0&#34; style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; title=&#34;YouTube video&#34;&gt;&lt;/iframe&gt;
    &lt;/div&gt;

&lt;p&gt;Video: Powers of Ten by Charles and Ray Eames&lt;/p&gt;
&lt;p&gt;The strong narrative structure of the video connects abstract mathematical concepts to personal experience. Viewers learn by relating powers of ten to concrete things they can see or imagine, but the video feels more inspirational than educational. The inspirational tone is more powerful than a neutral explanation for increasing engagement, and I’m eager to see more inspiration in discussion of privacy.&lt;/p&gt;
&lt;p&gt;Sarah Gold’s &lt;a href=&#34;https://www.sarah.gold/alternet/&#34;&gt;&lt;em&gt;Alternet&lt;/em&gt;&lt;/a&gt; video is one example of an experiential narrative that makes risks to privacy accessible to a mass audience. Similarly, the &lt;a href=&#34;https://donottrack-doc.com/en/episodes/&#34;&gt;&lt;em&gt;Do Not Track&lt;/em&gt;&lt;/a&gt; episodes are personalized videos that let people experience what various groups know about their online behavior. They are engaging and pleasurable to watch, even if the information in the video upsets people learning it for the first time. Like &lt;em&gt;Powers of Ten&lt;/em&gt;, Episode 1 of &lt;em&gt;Do Not Track&lt;/em&gt; also uses time to help viewers experience the scale of large numbers, with &lt;em&gt;Do Not Track&lt;/em&gt; showing how much revenue technology companies and the US internet advertising market make every second.&lt;/p&gt;
&lt;p&gt;When designers approach privacy, we look beyond education and into action. Making abstract privacy topics experiential can motivate a broader group of end users to get involved in making better tools to protect privacy and security. It’s already pleasurable to relax at a picnic gazing at the sky, but Powers of Ten makes knowledge of exponents so compelling that gazing at the sky gets even better. I believe that understanding the mechanics of the internet can let people enjoy it more.&lt;/p&gt;
&lt;p&gt;Charles and Ray Eames are legends of modern American design, famous for making products people welcome into their lives. As a community, let’s work to help end users embrace privacy and security by making challenging ideas accessible and easy to integrate into their daily lives.&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/blog/EamesStamps_hu_2b1ea57338aa4559.png&#34; alt=&#34;US Postage Stamps Commemorating Charles and Ray Eames. Photo by Ame Elliott&#34; width=&#34;740&#34; height=&#34;749&#34;&gt;
&lt;/p&gt;
&lt;p&gt;US Postage Stamps Commemorating Charles and Ray Eames.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>What We Do</title>
      <link>https://superbloom.design/learning/blog/what-we-do/</link>
      <pubDate>Wed, 13 May 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/what-we-do/</guid>
      <description>&lt;p&gt;You learned at our &lt;a href=&#34;https://superbloom.design/learning/blog/why-hello-world/&#34;&gt;launch&lt;/a&gt; that we’re setting out to improve the experience users have with secure-communication tools. We told you that we want to work with the open source community, and that we’re committed to documenting our activities transparently. But what does this mean in practice – how will &lt;a href=&#34;https://superbloom.design/learning/blog/hello-ame/&#34;&gt;Ame&lt;/a&gt;, &lt;a href=&#34;https://superbloom.design/learning/blog/hello-trouble/&#34;&gt;Trouble&lt;/a&gt;, and I be spending our days?&lt;/p&gt;
&lt;p&gt;It’s much easier to show than to tell, so I expect you’ll get a better feel for our work as we describe it here over time. For the moment, though, you can expect it to fall into three major buckets:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Direct collaboration&lt;/strong&gt;: We partner with open-source software-development teams to support them in researching and improving the usability of their tools. We’re focusing at first on secure-communication tools that have an established user base, but also collaborate with teams building related or emerging tools. I’ll tell you more in future posts about what we look for in a partner, and also introduce the projects we’ve already started working with. If you have a tool that you’d like a hand with, &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;get in touch&lt;/a&gt;!&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Information sharing&lt;/strong&gt;: We take our collaborative research and use it to build public resources that help everyone – developers, designers, researchers, users, and the community at large – better understand great user experiences and how to achieve them. We also work to raise the profile of high-quality usable-security designs and projects, both those that we participate in directly and those conducted by other organizations. We share this information freely here, and through our newsletter, &lt;a href=&#34;https://twitter.com/simplysecureorg&#34;&gt;Twitter stream&lt;/a&gt;, and conference talks. Stay tuned in the near term for a reading list that will help you get started thinking about usable security – and &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;let us know&lt;/a&gt; about your favorite books and papers that you want to see included.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mentorship and capacity building&lt;/strong&gt;: We work to support usable-security practitioners of all stripes, including developers, designers, and researchers. We encourage promising junior practitioners and students in their efforts to learn, and to participate in designing trustworthy experiences. As part of this, we are &lt;a href=&#34;https://superbloom.design/learning/blog/fellowship/&#34;&gt;partnering&lt;/a&gt; with the Open Technology Fund on the Secure Usability Fellowship program.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In addition to these formal activities, we also aspire to act as a hub for usable-security practitioners, and among the development, design, research, and user communities. Although we don’t provide funding for projects, we make it a point to know about different practitioners and activities in the space, and offer referrals when asked. So, although we’re still catching up on our backlog of email inquiries, we’re always interested in hearing from you if you’re doing work in this space. And, as always, we hope you’ll &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;stay tuned&lt;/a&gt; to keep up with our activities!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Dia dhaoibh, mise Nóirín!</title>
      <link>https://superbloom.design/learning/blog/hello-trouble/</link>
      <pubDate>Mon, 11 May 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/hello-trouble/</guid>
      <description>&lt;p&gt;Hi, I&#39;m N&amp;#243;ir&amp;#237;n (sounds like
[n&amp;#810;&amp;#736;&amp;#245;&amp;#720;&amp;#638;&amp;#690;i&amp;#720;&amp;#626;]). In Ireland, I have a
pretty common name: I share it with professors, politicians, and even our
police commissioner! Elsewhere, however, it&#39;s less simple. I&#39;ve had conference
badges in the names of &#34;N&amp;#8730;&amp;#8805;ir&amp;#8730;&amp;#8800;n&#34; and
&#34;N&amp;#219;ir&amp;#204;n&#34;, online services often call me &#34;N&amp;amp;#xF3;ir&amp;amp;#xED;n&#34; or
&#34;N&amp;#56128;&amp;#56352;ir&amp;#56128;&amp;#56352;n&#34;, and I&#39;ve even gotten mail for
&#34;N&amp;#x251C;&amp;#xE2;&amp;#xE3;&amp;#xC6;&amp;#x251C;&amp;#xE9;&amp;#x252C;&amp;#x2502;ir&amp;#x251C;&amp;#xE2;&amp;#xE3;&amp;#xC6;&amp;#x251C;&amp;#xE9;&amp;#x252C;&amp;#xA1;n&#34;!&lt;/p&gt;
&lt;p&gt;So at Simply Secure, I go by a name I picked up on the Appalachian Trail,
that&#39;s found in most spell-checkers, and is a bit simpler to pronounce:
Trouble.&lt;/p&gt;
&lt;p&gt;According to the IRS, my job title is Operations Manager. Much like my name
though, the reality is more nuanced, and always evolving. I think of myself as
Simply Secure’s &lt;a
href=&#34;http://en.wikipedia.org/wiki/The_Steerswoman&#34;&gt;Steersman&lt;/a&gt;&lt;sup&gt;&lt;a href=&#34;#fn1&#34; id=&#34;ref1&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;. I travel
alongside our collaborators, through their varied communities, always
collecting knowledge, connecting ideas, and helping to preserve and share what
we see. I come from the Open Source world, and, with Scout and Ame, will be
working hard to make sure that the things we learn, create, and do, are done as
transparently as possible.&lt;/p&gt;
&lt;p&gt;Our shared vision at Simply Secure is that people shouldn’t have to choose
between tools they like and tools that are secure. We know where we want to be:
in a world where secure and private communication tools are available to
everyone. We know the direction we need to go to get there: human-centered
design is our guide star, open-source tools are the paths we walk along,
verifiable and auditable cryptography is the shelter we depend on. But in the
words of the Irish proverb, “it’d be a long road that didn’t have turns in
it”&lt;sup&gt;&lt;a href=&#34;#fn2&#34; id=&#34;ref2&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;.  So, bringing together the finest
traditions both ancient and modern, I’m here to record what we’re doing, map
out where we’ve been, and glean what I can about where we’re going.&lt;/p&gt;
&lt;p&gt;I hope you&#39;ll join me along the way!&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;&lt;sup id=&#34;fn1&#34;&gt;1. I prefer gender-neutral titles and pronouns where
possible. &lt;a href=&#34;#ref1&#34; title=&#34;Return to text&#34;&gt;&amp;#8617;&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
&lt;p&gt;&lt;sup id=&#34;fn2&#34;&gt;2. Is fada an b&amp;oacute;thar nach mb&amp;iacute;onn casadh ann.&lt;a
href=&#34;#ref2&#34; title=&#34;Return to text&#34;&gt;&amp;#8617;&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Hello, I’m Ame, Design Director for Simply Secure</title>
      <link>https://superbloom.design/learning/blog/hello-ame/</link>
      <pubDate>Wed, 06 May 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/hello-ame/</guid>
      <description>&lt;p&gt;I’m Ame (sounds like “Amy”). Last month I joined Simply Secure after
spending the past eight years at IDEO, a global design and innovation
consultancy. While there, I designed consumer technology for entertainment, &lt;a
href=&#34;http://www.ideo.com/work/innovators-accelerator-digital-platform-by-lightspeed&#34;&gt;education&lt;/a&gt;,
banking, &lt;a href=&#34;http://www.ideo.com/work/the-bold-italic&#34;&gt;media&lt;/a&gt;, business
software, mobile/wearables, and home automation. Uniting all my work is
Human-Centered Design, a set of practices and research methods that starts with
people, studies their needs and preferences, and creates things they want and
enjoy.&lt;/p&gt;
&lt;p&gt;I was fortunate to work with fantastic teams on projects I was proud of, but
over time I began to feel a vague sense of unease about how little power people
had to protect their privacy. A catalyst for my thinking more explicitly about
about user experience + privacy was watching Mike Monteiro’s Webstock talk on
&lt;a href=&#34;https://vimeo.com/68470326&#34;&gt;How Designers Destroyed the World&lt;/a&gt;,
which takes designers to task for the drastic real world consequences of bad
design [the privacy settings example starts at 4:40].&lt;/p&gt;

      &lt;div
          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;
        &lt;iframe
          src=&#34;https://player.vimeo.com/video/68470326?dnt=0&#34;
            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;
        &lt;/iframe&gt;
      &lt;/div&gt;

&lt;p&gt;Mike Monteiro at &lt;a
href=&#34;https://vimeo.com/webstock&#34;&gt;Webstock &#39;13&lt;/a&gt;: &lt;a
href=&#34;https://vimeo.com/68470326&#34;&gt;How Designers Destroyed the World&lt;/a&gt;, on &lt;a
href=&#34;https://vimeo.com&#34;&gt;Vimeo&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In exploring the social and technical barriers to privacy for mass
audiences, a common thread has been the need for design. And by design I don’t
mean decoration – I mean research and implementation that makes things work for
people. By the time I saw the announcement for Simply Secure on &lt;a
href=&#34;http://boingboing.net/2014/09/18/privacy-for-normal-people.html&#34;&gt;Boing
Boing&lt;/a&gt;, I knew that I wanted to work on design for privacy and security.
Simply Secure is founded on the idea that people shouldn’t have to choose
between communication tools they like and tools that are secure, and that
design and user research can play a role in eliminating the need to choose.
That founding principle is what I practice, and why I’m here.&lt;/p&gt;
&lt;p&gt;At Simply Secure, I’ll be building a culture of design to address the
challenges of privacy and security. That means working directly on the user
experience (UX) of tools providing secure communication, as well as connecting
to the community of people working on privacy and security around design.
Everyone should be able to communicate privately and securely, and it will take
collaboration by people of different backgrounds to make that a reality. So if
design is unfamiliar, stay tuned. I’ll be sharing my passion and showing how
design can make secure communication accessible.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Simply Secure&#39;s Growing Team</title>
      <link>https://superbloom.design/learning/blog/hello-again/</link>
      <pubDate>Mon, 04 May 2015 12:00:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/hello-again/</guid>
      <description>&lt;p&gt;Happy Spring! Like so much in the northern hemisphere, our blog and Twitter
stream have been largely dormant for a while – but we’ve been behind the scenes
getting ready for a season of tremendous growth. Since we announced Simply
Secure in the fall, we’ve become formally established as a legal entity,
interviewed and hired an exceptional staff, and fleshed out our plans for
partnering with open-source organizations to make secure-communication tools
more usable. We’ll tell you more about what we’re working on in future blog
posts, but today I’d like to introduce you to our two awesome new staff
members: Ame Elliott, our Design Director, and Nóirín Plunkett,
our Operations Manager.&lt;/p&gt;
&lt;p&gt;Ame Elliott comes from global design consultancy IDEO, where she led Design
Research for Fortune 500 clients. She holds a Ph.D. in Design Theory and
Methods, and has spent her career creating and developing Human-Centered Design
techniques, which ensure that the resultant design responds to the needs of the
people who will engage with it, and not the other way around. This approach –
improving technology by focusing on users – is at the core of Simply Secure’s
mission, and we are ecstatic to have someone of Ame’s caliber applying these
principles to the secure-communications space.&lt;/p&gt;
&lt;p&gt;Nóirín “Trouble” Plunkett is Simply Secure’s Archivist,
Historian, and Operations Manager. Trouble brings impeccable organization and
writing skills to this unusual role, along with deep experience in the open
source world by way of the Apache Software Foundation, Google, and the Ada
Initiative. As Operations Manager, they work to generally keep the ship that is
Simply Secure sailing smoothly. As Archivist and Historian, they will be
working to catalog (and make freely available to the public) resources to help
make usability and design an integral part of software development.&lt;/p&gt;
&lt;p&gt;What is this excellent team up to? In a word, lots. In coming weeks we will
share more about some work Ame is doing (a “listening tour”) to learn about
where the design, software, and user communities stand in relation to current
secure-communication technology. This series of qualitative-research interviews
will provide a broad and deep review of the work being done, and help pinpoint
clear opportunities for us to make a serious impact. We’ll also tell you about
the ways in which we are hoping to collaborate with software partners to
improve their tools, and how to get involved. And, of course, we can’t wait to
introduce our inaugural group of Secure Usability Fellows!&lt;/p&gt;
&lt;p&gt;Thank you for your interest and support while we’ve been getting up and
running. If you want to stay in touch as we start sharing out our work, please
sign up for our newsletter, follow us on Twitter, or drop us an email – more
info &lt;a href=&#34;https://superbloom.design/contact/&#34;&gt;here&lt;/a&gt;!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>A Fellowship of Usability</title>
      <link>https://superbloom.design/learning/blog/fellowship/</link>
      <pubDate>Mon, 01 Dec 2014 20:22:00 -0500</pubDate>
      <guid>https://superbloom.design/learning/blog/fellowship/</guid>
      <description>&lt;h2 id=&#34;announcing-a-new-program-for-usable-security-researchers&#34;&gt;Announcing a new program for usable-security researchers&lt;/h2&gt;
&lt;p&gt;We are pleased to announce one of our first initiatives – the &lt;a href=&#34;https://www.opentechfund.org/fellowships/sufp&#34;&gt;Secure Usability Fellowship Program&lt;/a&gt; (SUFP) – in partnership with the &lt;a href=&#34;https://www.opentechfund.org/&#34;&gt;Open Technology Fund&lt;/a&gt;. This new program aims to cultivate applied research and creative collaboration at different levels and across institutions on the topic of usable security, especially the usability of open-source secure-communication tools to promote human rights and open societies.&lt;/p&gt;
&lt;p&gt;SUFP’s approach to this work is straightforward; the program supports qualified individuals to work within &lt;a href=&#34;https://www.opentechfund.org/fellowships/sufp/partners&#34;&gt;accomplished host organizations&lt;/a&gt; on clearly-defined and high-impact usable-security projects. Simply Secure will offer mentorship and community to the fellows, act as a host organization for some of them, and help OTF guide and administer the program overall.&lt;/p&gt;
&lt;p&gt;Two tiers of competitively-paid fellowships are available:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Senior Fellows&lt;/strong&gt; - Offered as a one year term and typically taken up by postdoctoral or doctoral students, and/or researchers/practitioners with demonstrated expertise and experience.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Seasonal Fellows&lt;/strong&gt; - Offered as a three- or six-month term and typically taken up by students and/or less-experienced practitioners.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We encourage people from a varied and unlikely backgrounds – from students to established practitioners – to apply. We welcome applications from people in a diversity of disciplines; likely candidates have experience as usability researchers, interaction or visual designers, computer scientists, user-facing software developers, data visualization designers, or other types of social scientists.&lt;/p&gt;
&lt;p&gt;To apply to be a fellow, please complete &lt;a href=&#34;https://www.opentechfund.org/fellowships/sufp&#34;&gt;this online form&lt;/a&gt;. The deadline for applications to the inaugural group of fellows is &lt;strong&gt;January 2nd, 2015&lt;/strong&gt;. If you’re interested in hosting a fellow, please contact &lt;a href=&#34;mailto:sufp@opentechfund.org&#34;&gt;sufp@opentechfund.org&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>We&#39;re hiring!</title>
      <link>https://superbloom.design/learning/blog/hiring/</link>
      <pubDate>Wed, 08 Oct 2014 17:35:00 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/hiring/</guid>
      <description>&lt;h2 id=&#34;join-our-team-and-lets-make-this-happen&#34;&gt;Join Our Team and Let&amp;rsquo;s Make This Happen&lt;/h2&gt;
&lt;p&gt;We have ambitious goals, and the first step to meeting them is growing our team. We’re officially hiring two new positions – an Operations Manager and a Research Director (or Associate Director).&lt;/p&gt;
&lt;p&gt;If you’re interested in helping us quickly make an impact on the usability of secure communication tools, please apply. If you know someone who fits this description, please spread the word. In any case, check out the &lt;a href=&#34;https://superbloom.design/community/opportunities/&#34;&gt;job descriptions&lt;/a&gt; and let’s get to work!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Why Hello, World!</title>
      <link>https://superbloom.design/learning/blog/why-hello-world/</link>
      <pubDate>Thu, 18 Sep 2014 14:56:18 -0400</pubDate>
      <guid>https://superbloom.design/learning/blog/why-hello-world/</guid>
      <description>&lt;h2 id=&#34;were-here-to-make-security-easy-and-fun&#34;&gt;We&amp;rsquo;re here to make security easy and fun.&lt;/h2&gt;
&lt;p&gt;Internet software links us to our friends, allows us to transact across oceans, and forms a digital space for culture and society. Because these technologies provide forums for sensitive discourse and expression, we are all concerned about their security and privacy – but don’t always know what to do about it.&lt;/p&gt;
&lt;p&gt;In fact, when security-enhancing functionality exists, it often seems to add an extra layer of complexity. Under these circumstances, how can an average person tell how a given feature works – or validate that security claims are true at all?&lt;/p&gt;
&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/audience-funders@2_hu_cb750db0aefd18a5.png&#34; alt=&#34;Celebratory balloons&#34; width=&#34;740&#34; height=&#34;631&#34;&gt;
&lt;/p&gt;
&lt;p&gt;That’s why we’ve created Simply Secure: to help develop security and privacy tools that make this choice clear, easy, and available to everyone.&lt;/p&gt;
&lt;h4 id=&#34;our-founding-principles&#34;&gt;Our founding principles&lt;/h4&gt;
&lt;ol&gt;
&lt;li&gt;The future of a positive, accessible, and people-centered Internet requires trustworthy privacy and security.&lt;/li&gt;
&lt;li&gt;If privacy and security aren’t easy and intuitive, they don’t work. Usability is key.&lt;/li&gt;
&lt;li&gt;Technology should respect the user’s desire for privacy and security.&lt;/li&gt;
&lt;li&gt;Users shouldn’t have to choose between services they like and services that are secure; they should be able to easily adopt privacy and security solutions for existing services.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;There are already many credible and exciting software-development efforts that aim to make privacy and security ubiquitous. Rather than create redundant initiatives, we will focus on supporting existing open source work by providing usability and development expertise, direct ties to user communities, connections to funding sources, and other resources.&lt;/p&gt;
&lt;p&gt;To build trust and ensure quality outcomes, one core component of our work will be public audits of interfaces and code. This will help validate the security and usability claims of the efforts we support.&lt;/p&gt;
&lt;p&gt;More generally, we aim to take a page from the open-source community and make as much of our work transparent and widely accessible as possible. This means that as we get into the nitty-gritty of learning how to build collaborations around usably secure software, we will share our developing methodologies and expertise publicly. Over time, this will build a body of community resources that will allow all projects in this space to become more usable and more secure.&lt;/p&gt;
&lt;p&gt;We hope that this effort will result in more pleasing and robust tools that meet users’ privacy and security needs where they are – from layering additional security on top of popular name-brand cloud platforms, to augmenting small, stand-alone mobile apps.&lt;/p&gt;
&lt;p&gt;We’re excited to be launching, and hope you will &lt;a href=&#34;https://superbloom.design/contact&#34;&gt;contact us&lt;/a&gt; or &lt;a href=&#34;https://twitter.com/simplysecureorg&#34;&gt;follow us on Twitter&lt;/a&gt; if you’re interested in learning more and getting involved.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title></title>
      <link>https://superbloom.design/work/readme/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/work/readme/</guid>
      <description>&lt;h2 id=&#34;impact-to-date-section&#34;&gt;Impact to date section&lt;/h2&gt;
&lt;h3 id=&#34;eileen-additions-nov-23&#34;&gt;Eileen additions Nov 23&lt;/h3&gt;
&lt;p&gt;C. Tails summit workshops + Radical Networks + open source design summit -&amp;gt; 50&lt;/p&gt;
&lt;p&gt;D. 65 -&amp;gt; 67&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Localisation Lab&lt;/li&gt;
&lt;li&gt;Tails&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;ame-edits-on-12-octo&#34;&gt;Ame edits on 12 Octo&lt;/h3&gt;
&lt;p&gt;Numbers higher than 5,600:&lt;/p&gt;
&lt;p&gt;A. Audience increases from 5,600 to 5,700&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Rights Con 15&lt;/li&gt;
&lt;li&gt;Foss Backstage 40&lt;/li&gt;
&lt;li&gt;HERE 15&lt;/li&gt;
&lt;li&gt;Invoice to Go 15&lt;/li&gt;
&lt;li&gt;Adobe Design Summit SF 250&lt;/li&gt;
&lt;li&gt;Adobe MAX 625 est per RSVPs&lt;/li&gt;
&lt;li&gt;Berlin Design Lab 30&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;B. Increase to 50+&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Adobe SF, Adobe LA, Adobe LA, Foss, HERE, Invoice to Go, Design Lab Berlin Acual number is 52&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;C.Workshops increases from 31 to 47&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;HERE&lt;/li&gt;
&lt;/ul&gt;
&lt;!-- * Open Archive --&gt;
&lt;p&gt;// Eileen comment: aren&amp;rsquo;t we counting PF twice? I&amp;rsquo;d put them under projects/coachings, and have workshops be separate! We do enough workshops for those to be impressive!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Prototype Fund round 3 = 13
&lt;ul&gt;
&lt;li&gt;Briar&lt;/li&gt;
&lt;li&gt;Conflict Base:&lt;/li&gt;
&lt;li&gt;Dein eigenes Webarchiv:&lt;/li&gt;
&lt;li&gt;Das lokal finanzierte Europa:&lt;/li&gt;
&lt;li&gt;DEMOCRACY:&lt;/li&gt;
&lt;li&gt;Diversity Ticket:&lt;/li&gt;
&lt;li&gt;Ernte Teilen:&lt;/li&gt;
&lt;li&gt;Global Agriculture Information Platform:&lt;/li&gt;
&lt;li&gt;Menstruation Cycle Tracker&lt;/li&gt;
&lt;li&gt;Nordlicht/Timelens&lt;/li&gt;
&lt;li&gt;Solar Energy Mesh System&lt;/li&gt;
&lt;li&gt;Voice Gym&lt;/li&gt;
&lt;li&gt;Hoax Files&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;D. Increase from 59 to 65 (number is 64 but some pro bono must have happened)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;13 prototype fund&lt;/li&gt;
&lt;li&gt;RightsCon KeePassXc and FOTP&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;E. Partners goes up from 10 to 14&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Adobe&lt;/li&gt;
&lt;li&gt;HERE&lt;/li&gt;
&lt;li&gt;Invoice2Go&lt;/li&gt;
&lt;li&gt;Omidyar&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;F. Countries up by 1 to 13&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;One Prototype Fund project in Hungary&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&#34;updates-on-17-may&#34;&gt;Updates on 17 May&lt;/h4&gt;
&lt;p&gt;A. Audience increases by 1,760 to 5,600&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;May 2018 UX London 600&lt;/li&gt;
&lt;li&gt;May 2018 re-publica. 500&lt;/li&gt;
&lt;li&gt;May 2018 Biz to Buttons 600&lt;/li&gt;
&lt;li&gt;May 2018 Biz to Buttons workshop 10&lt;/li&gt;
&lt;li&gt;April 2018 Underexposed Caroline, Adam, Maya 50&lt;/li&gt;
&lt;li&gt;March 2018 IFF SapientRazorfish talk, 40&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;B. Add 5 presentations to 45+&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Listed above in A.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;C. Add 15 workshops to be 31&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Biz to Buttons&lt;/li&gt;
&lt;li&gt;Prototype Fund: Briar, Conflict Base, Eigenes Web Archiv, Democracy, Diversity Ticket, Ernte Teilen, Global Agriculture Information, Menstrual Cycle Tracker, Voice Gym, Nordlich, Hoax Files, GREMIEN&lt;/li&gt;
&lt;li&gt;IFF documentation workshop&lt;/li&gt;
&lt;li&gt;IFF privacy workshop with Least Authority&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;D. Teams goes up by Prototype Fund entries in C. above to 59&lt;/p&gt;
&lt;p&gt;E. Partners goes up by 1 to be 10&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;From Biz to Buttons paid for workshop&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;F. No change to countries&lt;/p&gt;
&lt;h3 id=&#34;already-live-on-site-formerly-ame-is-editing-this-text-file-with-numbers&#34;&gt;ALREADY LIVE ON SITE. FORMERLY AME IS EDITING THIS TEXT FILE WITH NUMBERS.&lt;/h3&gt;
&lt;p&gt;I&amp;rsquo;m using these numbers for the Adobe pitch deck. I&amp;rsquo;m showing my work, but do not plan to push them to the website. Somebody else can.&lt;/p&gt;
&lt;p&gt;Increases to add to website:
A. Audience numbers to increase by 500 to 3,800 (this is an estimate, 2 events haven&amp;rsquo;t happened)
Add in number of participants from the Prototype fund coachings, which we are calling workshops&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Mar. 2018.    Introduction to UX, Prototype Fund, Berlin. (Guess 35 event this week)&lt;/li&gt;
&lt;li&gt;Feb. 2018.   Overview of UX Findings from Prototype Fund Round 2 (Guess 100)&lt;/li&gt;
&lt;li&gt;Feb. 2018.   Panelist, &amp;ldquo;Trust Labels for IoT,&amp;rdquo; Bosch Connected World, Berlin, Germany. 150&lt;/li&gt;
&lt;li&gt;Feb. 2018.    Intro to User Experience Design, Demokratie.io Kickoff, Better Place Lab, Berlin, Germany. 15&lt;/li&gt;
&lt;li&gt;Jan. 2018.    Exploring the &amp;lsquo;Design&amp;rsquo; in Privacy By Design, Computers, Privacy, and Data Protection, Brussels, Belgium. 75)&lt;/li&gt;
&lt;li&gt;Jan. 2018.    UX, Usability, and Privacy: Building Trustable Products, Privacy for Everyone, Berlin, Germany. 50&lt;/li&gt;
&lt;li&gt;Dec. 2017.     IoT Security: User Experience and Privacy, ThingsCon Amsterdam, the Netherlands. 25&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;B. 9 presentations added since Droid Con. Do we make it 40+ assuming that the current 30+ is at least 32? I say yes. We didn&amp;rsquo;t track this carefully in the beginning, so I think rounding up by 1 right now is fine.&lt;/p&gt;
&lt;p&gt;C.  Workshops increase to 16
Note: we are calling 1:1 team coachings workshops. Is this weird? It sounds grander that it is. But some of them are realy hard.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Prototype Fund Round 2 total is 15 since  10/30 and +1 pro Bono with Zifra. Zifra isn&amp;rsquo;t a new team, but it is a new workshop.&lt;/li&gt;
&lt;li&gt;Round 2 New since 10/30: Pluragraph, Videoactive X2, Sea Watch X2, Stadtgestalten X2,tale:net, Meine Stadt Transparent, VISOR, Atomschatzkarte, Pretix, UwaziML, Datenland, Cobudget&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;D. Projects updated to 46
Note, was 38 and need to add 8. Many projects already counted only 8 new projects. Rest are repeats.&lt;/p&gt;
&lt;p&gt;E. Partner Organizations to 9 with Better Place/Demokratie as new. Question did we get any donations for Underexposed from somebody new? That could make that number go higher.&lt;/p&gt;
&lt;p&gt;F. Counties should be 12 because one of the Prototype Fund CoBudget is in New Zealand.&lt;/p&gt;
&lt;h3 id=&#34;1030-update-countries&#34;&gt;10/30 update countries:&lt;/h3&gt;
&lt;p&gt;Adding: Lebanon, France, Cuba, Venezuela, increasing country total to 11.&lt;/p&gt;
&lt;p&gt;Original 7 countries: US, Canada, Germany, Sweden, UK, Syria, Italy&lt;/p&gt;
&lt;h3 id=&#34;1030-update-projects&#34;&gt;10/30 update* projects:&lt;/h3&gt;
&lt;p&gt;New coachings&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;(6) Prototype Fund Round 2:CoBudget, Uwazi, AtomMuell,Crabgrass, Pretix, Fix My Berlin&lt;/li&gt;
&lt;li&gt;(5) OTF Summit 2016: Apretaste, OTI Measurement Lab, OONI, Venezuela Sin Filtro, Tails&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Increases total to&lt;/em&gt; 37&lt;/p&gt;
&lt;p&gt;Old total was 25, but should have been 26. Note that Peerio participated in 3 events, but gets counted once.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;(1) Usable: Least Authority and [Peerio]&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;(6) Prototype Fund 1: Speakerinnen, Frab, MietLimbo, Fireside, Syrian Archive, Schleuder&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;(2) IFF 2016: Mailvelope, Zifra, [Peerio]&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;(5) IFF 2015 Whereat.io, Stingwatch, Mailvelope, Peerio, Amnesty&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;(6) OTF DC Summit 2015: Signal, GlobaLeaks, Tor Project, smex.org, MLab Browser Extension, Qubes OS&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;(6) Misc: Geti2p, Storymaker 2, Shamir Secret, Mynigma, F-Droid, Scout&amp;rsquo;s random open-source developer seeking help on needfinding circa early 2016, Ranking Digital Rights&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;925-update-next-conference-1k-participants&#34;&gt;9/25 update* NEXT Conference: +1k participants&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;New participant total:&lt;/em&gt; 3,340&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Published participant total:&lt;/em&gt; 3,300+&lt;/p&gt;
&lt;h3 id=&#34;95-update&#34;&gt;9/5 update&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Product manager meetup: +1 presentation, est. +35 attendees&lt;/li&gt;
&lt;li&gt;DroidCon: +1 presentation, +700 attendees&lt;/li&gt;
&lt;li&gt;Add other presentations by Scout (+1 presentation for each):
&lt;ul&gt;
&lt;li&gt;Dartmouth Talk (40 people)&lt;/li&gt;
&lt;li&gt;RightsCon panel (30 people)&lt;/li&gt;
&lt;li&gt;O&amp;rsquo;Reilly Security (40 people)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Participant increase:&lt;/em&gt; +840 for a total of 2,340&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Presentation increase:&lt;/em&gt;  +5 presentations for a total of 32&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Published participant total:&lt;/em&gt; 2,300+&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Published presentation total:&lt;/em&gt; 30+&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;2 more projects supported under Prototype Fund (that concludes first round of PF folks)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Project toal:&lt;/em&gt; 25&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Published projects total:&lt;/em&gt; 25 projects&lt;/p&gt;
&lt;h3 id=&#34;initial-deployment&#34;&gt;Initial deployment&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Included Ame&amp;rsquo;s talks to date&lt;/li&gt;
&lt;li&gt;Included Scout&amp;rsquo;s SchmooCon and and NetGain panel&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Estimated participants total:&lt;/em&gt; 1,500&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>2019 UX Residency in Berlin</title>
      <link>https://superbloom.design/residency/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/residency/</guid>
      <description>&lt;p&gt;

    &lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/images/img/wocintech-lady-on-laptop_hu_2ff8bdaf11a517c2.jpg&#34; width=&#34;740&#34; height=&#34;494&#34;&gt;
&lt;/p&gt;
&lt;h1 id=&#34;bringing-ux-forward&#34;&gt;Bringing UX Forward&lt;/h1&gt;
&lt;p&gt;We depend on human-centered thinkers to challenge assumptions, draw lines in the sand, and chart new paths that protect and empower the people whose lives our software touches.&lt;/p&gt;
&lt;p&gt;We need designers and UX researchers to have a seat at the table as we tackle emerging challenges in fields such as IoT, artificial intelligence, and secure communication.&lt;/p&gt;
&lt;p&gt;We must make space for cutting-edge dialogue that focuses not just on the technical, but the human and the ethical.&lt;/p&gt;
&lt;h1 id=&#34;2019-an-immersive-residency-experience&#34;&gt;2019: An Immersive Residency Experience&lt;/h1&gt;
&lt;p&gt;Join a small but global cohort of UX designers and researchers building a better future. In 2018 we will focus on how UX can make new technologies (including the Internet of Things and artificial intelligence) understandable and trustworthy from a privacy-preserving perspective.&lt;/p&gt;
&lt;p&gt;This week-long program will include workshops with guest lecturers, individual or small-group work sessions, critiques, and public cultural events.&lt;/p&gt;
&lt;p&gt;There are opportunities for travel and lodging support.&lt;/p&gt;
&lt;h1 id=&#34;learn-more&#34;&gt;Learn More&lt;/h1&gt;
&lt;p&gt;To be notified when more details become available, please contact us at &lt;a href=&#34;mailto:residency@superbloom.design&#34;&gt;residency@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In the meantime, consider joining our Slack channels by asking for an invitation in the same email, or by sending us a note at &lt;a href=&#34;mailto:slack@superbloom.design&#34;&gt;slack@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;em&gt;Header image CC-BY &lt;a href=&#34;https://www.flickr.com/photos/wocintechchat/&#34;&gt;#WOCinTech&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>3 x 3</title>
      <link>https://superbloom.design/about/people/3x3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/3x3/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Aaron Brunmeier</title>
      <link>https://superbloom.design/about/people/aaron/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/aaron/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Abhishek Sharma</title>
      <link>https://superbloom.design/about/people/abhishek/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/abhishek/</guid>
      <description>&lt;p&gt;Abhishek is a multi-disciplinary product designer skilled in UI/UX, with experience in branding, product management and team building. He has designed for various softwares such as chatbots, process automation, data dashboards; in domains like education, healthcare; for non-profit and for-profit space in an agency model. Being a part of small teams and startup, he has built capability in performing various roles rolled into one while his time leading product at Glific and leading design at ColoredCow. He is adept at working with less resources and is driven towards getting things done.&lt;/p&gt;
&lt;p&gt;He works best in a close collaboration with users, developers and product people. He has a keen interest in informing his work with metrics and measurements that allow tracking and improvements over time.&lt;/p&gt;
&lt;p&gt;Abhishek is largely self-taught as a practicing design thinking professional having graduated with a degree in Mechanical Engineering. He is a generalist and takes a keen interest in organisation development. He is driven to make a large-scale impact through design.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>accessibility</title>
      <link>https://superbloom.design/tags/accessibility/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/accessibility/</guid>
      <description></description>
    </item>
    
    <item>
      <title>adoption</title>
      <link>https://superbloom.design/tags/adoption/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/adoption/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Adriana Valdez Young</title>
      <link>https://superbloom.design/about/people/adriana-valdez-young/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/adriana-valdez-young/</guid>
      <description>&lt;p&gt;Adriana is a design researcher and strategist focused on democratizing access to new technologies and creating more inclusive, accessible, and joyful experiences for all. &lt;/p&gt;
&lt;p&gt;Over the past 15 years, she has led design research at littleBits, Openbox, Stae, and 3x3. Currently, she is Associate Chair of &lt;a href=&#34;https://interactiondesign.sva.edu/&#34;&gt;MFA Interaction Design at School of Visual Arts&lt;/a&gt;, and Senior Advisor at SOUR, an urban innovation and design studio co-located in Brooklyn and Istanbul. &lt;/p&gt;
&lt;p&gt;Her work has been presented in the Amsterdam Biennale, Archizines, Design Institute Australia, Eyebeam, Journal of Urban Technology, UX Magazine and the World Bank. Her work and life story are featured in Jesse Eisenberg’s new documentary, &lt;em&gt;&lt;a href=&#34;https://www.indiewire.com/news/trailers/secret-mall-apartment-trailer-jesse-eisenberg-documentary-1235096495/&#34;&gt;Secret Mall Apartment.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;She holds a BA in History from Brown University and an MSc in City Design from the London School of Economics.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Alexander Morley</title>
      <link>https://superbloom.design/about/people/alexander-morley/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/alexander-morley/</guid>
      <description>&lt;p&gt;Alex is a med-student turned neuroscientist turning into a developer. He is currently a Mozilla fellow working on building tools and communities to facilitate the sharing of research.&lt;/p&gt;
&lt;h2 id=&#34;project-name&#34;&gt;Project name:&lt;/h2&gt;
&lt;p&gt;feed.me&lt;/p&gt;
&lt;h3 id=&#34;project-description&#34;&gt;Project description:&lt;/h3&gt;
&lt;p&gt;Increasingly, the applications we use in our day-to-day lives are driven by algorithms that are hard to understand and are optimised for the end-goals of the developers (e.g. advertising money, time-on-site) and not for the users (e.g. keeping in touch with family, finding a new job). Feed.me is an experiment to see what happens when we give users more control over the algorithms that control their feeds. Can we allow a grandparent to look at photos of their kids without being shown political news, or allow a trauma victim to filter for things that are specifically triggering for them, or allow an electrician who was recently made redundant to use their feed to find leads on new jobs rather than waste more time that they could be using to continue pursuing their online degree? Technically all these things are well within reach, but they don’t line up well with the goals of the organisations that provide our social media services. Feed.me hopes to leverage the power of the browser to put the user in control with easy to understand “plug and play” algorithms that will work on all their social media. Guided by some user-research completed during the residency the first concrete goal is to implement a browser-extension that will allow the re-ordering of posts viewed through the browser without directly interacting with the APIs of the social media services.&lt;/p&gt;
&lt;p&gt;video: &lt;a href=&#34;https://vimeo.com/325016831&#34;&gt;https://vimeo.com/325016831&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Alexandra Creighton</title>
      <link>https://superbloom.design/about/people/alex-creighton/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/alex-creighton/</guid>
      <description>&lt;p&gt;Alex enjoys laying the tracks before the train, and is focused on crafting efficient, scalable systems and infrastructure, empowering Simply Secure to realize its strategic goals. Alex and her team manage all aspects of the day-to-day operations work that makes Simply Secure go. She is the founder of &lt;a href=&#34;http://sanssoucigroup.com/&#34;&gt;Sans Souci&lt;/a&gt;, and has provided operational consulting and back-office support services to small businesses and freelance professionals for over ten years.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>algorithms</title>
      <link>https://superbloom.design/tags/algorithms/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/algorithms/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Alicja Peszkowska</title>
      <link>https://superbloom.design/about/people/alicja-peszkowska/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/alicja-peszkowska/</guid>
      <description>&lt;p&gt;Alicja Peszkowska (she/her) is a Copenhagen-based anthropologist, researcher, and participation strategist. She has collaborated with public institutions, such as the National Gallery of Denmark, and international players, including the European Commission, as well as grassroots nonprofit organizations across Western and Eastern Europe and beyond. Her experience spans community building &amp;amp; engagement, communication, narrative shaping, PR, and organizational strategy. She has designed for participation for clients such as LEGO, IKEA, Milestone Systems, Creative Commons, and the Wikimedia Foundation, and curated campaigns and events both online and offline &amp;ndash; most recently at the community-run Vi lever på polsk gallery in Copenhagen &amp;ndash; and her writing on digital culture and everyday democracy has appeared in The Fix, Last Week in Denmark, and elsewhere. &lt;br&gt;
&lt;br&gt;
As a coach, Alicja brings a human-centered approach to strategy and storytelling. She helps people clarify their mission, strengthen their communities, and design participation that feels both inspiring and realistic. Known for asking sharp questions and challenging assumptions, she focuses on solutions grounded in values, resources, and reality, so that ideas can grow into structures that last and work in practice.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Allen Gunn</title>
      <link>https://superbloom.design/about/people/allen-gunn/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/allen-gunn/</guid>
      <description>&lt;p&gt;Allen Gunn, “Gunner”. is Executive Director of Aspiration (&lt;a href=&#34;https://www.aspirationtech.org&#34;&gt;www.aspirationtech.org&lt;/a&gt;) in San Francisco, USA, and works to help NGOs, activists, foundations and technologists make more effective and sustainable digital strategies in support of social change.&lt;/p&gt;
&lt;p&gt;Gunner has worked in numerous technology environments from NGO to Silicon Valley start-up to college faculty to large corporation, serving in senior management, engineering, teaching and volunteer roles. He is an experienced strategist, mentor and facilitator with a passion for designing collaborative open learning processes, and he believes in melding hard work with serious fun.&lt;/p&gt;
&lt;p&gt;In his role at Aspiration, he connects nonprofit organizations, free and open source projects, philanthropic funders and activists with strategic frameworks, technology solutions, digital practices and data skills that help them more fully realize their missions.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Ame Elliott</title>
      <link>https://superbloom.design/about/people/ame/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/ame/</guid>
      <description>&lt;p&gt;Ame (sounds like &amp;ldquo;Amy&amp;rdquo;) Elliott is a designer, researcher, and strategist working at the intersection of people x data x environments. Prof. Dr. Elliott teaches interaction design and design ethics at Hochschule Macromedia in Berlin and has been a coach for the Prototype Fund since 2017. She enjoys helping teams prioritize and move items onto a “To Don’t” List and focus their limited resources in high-impact ways. After many years of working in Silicon Valley, she believes that some elements of Big Tech (e.g. UX patterns) can be directly applied to public-interest tech projects. Some aspects (e.g. surveillance capitalism) are so toxic they must be rejected. And there is a middle area of practices that need to be adapted and re-imagined to fit the needs of values-driven projects. Ame is interested in system change and capacity building for transformation. Her particular passions are fighting climate change, urban design/cities, and imagining the future of work. Ame’s research explores how to include stakeholders with different backgrounds in discussion of responsible AI and data governance and making technical concepts accessible to a broad audience.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>An Xiao Mina</title>
      <link>https://superbloom.design/about/people/an-xiao-mina/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/an-xiao-mina/</guid>
      <description>&lt;p&gt;An Xiao Mina is a futures thinker, creative consultant, and coach, with a decade in nonprofit executive and board experience. Her mission is building a more just, compassionate, and sustainable world through better futures in work, technology, and society, and she’s coached and trained hundreds of global media and nonprofit leaders in the fields of product, program, strategy and operations. Co-founder of Five and Nine Futures Lab and producer for their podcast on magic, work and economic justice, Mina has written for publications like Hyperallergic, Fast Company, The Atlantic, and Nieman Lab. Her creative practice has been exhibited in spaces like the Victoria &amp;amp; Albert Museum, the Museum of the Moving Image, and the Brooklyn Museum, and she is a Senior Civic Media Fellow at the USC Annenberg Innovation Lab and 2024 Fellow at the Sundance Trans Possibilities Intensive. She serves on the boards of the Processing Foundation and the News Product Alliance. Her newest book, the Hanmoji Handbook, is co-authored for MITeen Press about emoji and the Chinese language. She is a certified foresight strategist and trauma-informed yin yoga teacher.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Andrea Goulet</title>
      <link>https://superbloom.design/about/people/andrea-goulet/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/andrea-goulet/</guid>
      <description>&lt;p&gt;Andrea Goulet is a globally recognized expert in empathy-driven communication and organizational change. As the founder of Lovelace Communications and the nonprofit Empathy in Tech, as well as the former CEO of Corgibytes, a software company specializing in modernizing mission-critical legacy systems, Andrea has spent her career helping teams align and collaborate more effectively.&lt;/p&gt;
&lt;p&gt;She is the cohost of the Empathy in Tech podcast and a LinkedIn Learning instructor, where over 75,000 learners have taken her courses on effective communication. A sought-after keynote speaker, Andrea brings a unique blend of deep technical knowledge and human-centered leadership to the stage, helping organizations improve collaboration, reduce friction, and scale with clarity.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Angela Sasse</title>
      <link>https://superbloom.design/about/people/angela/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/angela/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Anh Le</title>
      <link>https://superbloom.design/about/people/anh/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/anh/</guid>
      <description>&lt;p&gt;Anh Lê is designer and researcher whose work focuses on labor, migration, and digital justice. They recently completed their Masters in International Affairs at The New School, where they worked as a Research Assistant for the Mellon Initiative for Inclusive Faculty Excellence. Prior to graduate school, Anh worked on strategic communications and digital organizing campaigns with organizations including Community Tech NY, Mekong NYC, and the Southeast Asian Freedom Network. In a past life, they worked as a 3D designer and implementation specialist in the apparel industry.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Ann Marie Carrothers</title>
      <link>https://superbloom.design/about/people/ann-marie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/ann-marie/</guid>
      <description>&lt;p&gt;Ann Marie is a jill of all trades who has worked in fields ranging from television production and the performing arts to UX/web design and education. An opera singer turned computer programmer, she cares deeply about the integration of the arts and technology, speaking around the world to artists, activists, and educators on how to integrate digital education into the arts. She specializes in helping educators, non profits, and small businesses increase awareness and audience engagement through low cost technology and content strategy implementation.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>announcements</title>
      <link>https://superbloom.design/tags/announcements/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/announcements/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Apply for Design Researcher, Fall 2026</title>
      <link>https://superbloom.design/design-researcher-fall2026/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/design-researcher-fall2026/</guid>
      <description>
&lt;div class=&#34;indicates-required&#34;&gt;&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt; indicates required&lt;/div&gt;
&lt;form name=&#34;design-researcher-fall2026&#34; class=&#34;fullpage-form&#34; netlify&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;name&#34;&gt;Name &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;input type=&#34;text&#34; id=&#34;name&#34; name=&#34;name&#34; required /&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;email&#34;&gt;Email &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;input type=&#34;email&#34; id=&#34;email&#34; name=&#34;email&#34; required /&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;about&#34;&gt;Where can we learn more about you on the internet (
      e.g. Portfolio, Blog, LinkedIn, Website, Current Work Bio page, Social)?&lt;/label&gt;
    &lt;p class=&#34;help-text&#34;&gt;If we can’t learn about you on the internet, please share anything that can help us learn more
      about you. &lt;/p&gt;
    &lt;textarea id=&#34;about&#34; name=&#34;about&#34; rows=&#34;3&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;resume&#34;&gt;Resume &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;p class=&#34;help-text&#34;&gt;Accepted file formats: PDF. 2 pages max. Within the resume, please ensure that your experience in both Spanish and English are highlighted. &lt;/p&gt;
    &lt;input type=&#34;file&#34; id=&#34;resume&#34; name=&#34;resume&#34; required /&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;work-sample&#34;&gt;Work samples &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;p class=&#34;help-text&#34;&gt;Submit a single PDF that includes up to 3 past work samples. These work samples should be relevant to the role you are applying to.&lt;/p&gt;
    &lt;input type=&#34;file&#34; id=&#34;work-sample&#34; name=&#34;work-sample&#34; rows=&#34;1&#34; required/&gt;
  &lt;/div&gt;

  &lt;p class=&#34;help-text&#34; id=&#34;upload-limit-note&#34;&gt;Your resume and work samples are uploaded together and must come to
    &lt;strong&gt;7.5&amp;nbsp;MB or less in total&lt;/strong&gt;. If they are larger, please compress the PDFs or email them to
    &lt;a href=&#34;mailto:jobs@superbloom.design&#34;&gt;jobs@superbloom.design&lt;/a&gt;.&lt;/p&gt;
  &lt;div class=&#34;message error&#34; id=&#34;upload-size-error&#34; role=&#34;alert&#34; style=&#34;display:none&#34;&gt;&lt;/div&gt;
  
  &lt;h3&gt;Video submissions&lt;/h3&gt;
  &lt;p&gt;In lieu of cover letters, we request that each applicant submit a video recording to answer each of the following prompts. 
    &lt;br&gt;
    We’d like to get a sense of who you are, how you communicate, and how you think through problems. We’re not looking for polish or highly produced content. We just want to get to know you better.  
    &lt;br&gt;
    Each video should be around 2 to 5 minutes in length. You are welcome to record the video in whatever format or manner is most comfortable for you. Please share a link to an unlisted video uploaded to YouTube or a similar video platform, or provide a link to a cloud storage service (such as Google Drive or Dropbox). Please make sure the link is accessible to anyone with the link.
    &lt;br&gt;
    If you would like to request an accommodation, please don’t hesitate to reach out to &lt;a href=&#34;mailto:jobs@superbloom.design&#34;&gt;jobs@superbloom.design&lt;/a&gt;. &lt;/p&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;video1&#34;&gt;Video 1: What is your experience with community-centered design principles and methodologies? What approaches would you take in this role to ensure that the voices of community members are heard and represented in design and decision-making processes?
    &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;p class=&#34;help-text&#34;&gt;Video length: 5 minutes max.&lt;/p&gt;
    &lt;textarea id=&#34;video1&#34; name=&#34;video1&#34; rows=&#34;1&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;video2&#34;&gt;Video 2: Walk us through one of your work samples.&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;p class=&#34;help-text&#34;&gt;Video length: 5 minutes max. Questions you need to respond to:
    &lt;ul&gt;
        &lt;li&gt;What was the problem you were trying to solve?&lt;/li&gt;
        &lt;li&gt;Who was your target audience/community/user? How did you garner trust with this group? &lt;/li&gt;
        &lt;li&gt;What methods did you use and why?&lt;/li&gt;
        &lt;li&gt;What were the outcomes? &lt;/li&gt;
        &lt;li&gt;What did you learn from the process and how has it affected your current approach to design and research?&lt;/li&gt;
    &lt;/ul&gt;
    &lt;/p&gt;
    &lt;textarea id=&#34;video2&#34; name=&#34;video2&#34; rows=&#34;1&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;

&lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;language-exp&#34;&gt;Language Experience&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;p class=&#34;help-text&#34;&gt;Please briefly describe your professional experience leveraging both Spanish and English.&lt;/p&gt;
    &lt;textarea id=&#34;language-exp&#34; name=&#34;language-exp&#34; rows=&#34;3&#34; required&gt;&lt;/textarea&gt;
&lt;/div&gt;

&lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;start-date&#34;&gt;Availability&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;p class=&#34;help-text&#34;&gt;Please share the date you would be available to start, and/or how much time you would need from the offer to start date.&lt;/p&gt;
    &lt;textarea id=&#34;start-date&#34; name=&#34;start-date&#34; rows=&#34;3&#34; required&gt;&lt;/textarea&gt;
&lt;/div&gt;

&lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;ai-disclosure&#34;&gt;AI Disclosure&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;p class=&#34;help-text&#34;&gt;If you used AI on any part of this application, please disclosure what materials you used AI on and how you used it. Otherwise respond N/A.&lt;/p&gt;
    &lt;textarea id=&#34;ai-disclosure&#34; name=&#34;ai-disclosure&#34; rows=&#34;3&#34; required&gt;&lt;/textarea&gt;
&lt;/div&gt;

&lt;h3&gt;References&lt;/h3&gt;
&lt;p&gt;List the names, email addresses, and phone numbers for 2 references. Please ensure that 1 of the 2 references can speak to your professional experience in both English and Spanish. We will inform you before reaching out to your references.&lt;/p&gt;

&lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;reference1&#34;&gt;First Reference&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;textarea id=&#34;reference1&#34; name=&#34;reference1&#34; rows=&#34;3&#34; required&gt;&lt;/textarea&gt;
&lt;/div&gt;

&lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;reference2&#34;&gt;Second Reference&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;textarea id=&#34;reference2&#34; name=&#34;reference2&#34; rows=&#34;3&#34; required&gt;&lt;/textarea&gt;
&lt;/div&gt;

  &lt;input type=&#34;submit&#34; value=&#34;Apply&#34; class=&#34;button&#34; /&gt;
&lt;/form&gt;

&lt;script&gt;
  (function () {
    // Netlify rejects any form POST over 8 MB. Observed live on 2026-09-28 with an
    // 11 MB upload: the browser tab just spins. No error page, no message, nothing.
    // (Netlify&#39;s forum describes a bare HTTP 400, which at least yields a browser
    // error page. The real behaviour was worse - a spinner invites the applicant to
    // wait, or to retry the same doomed upload.)
    //
    // The submission is discarded outright. Verified after that test: no record in
    // Netlify, not even in the spam bucket; no webhook; no automation run; no task
    // and no notification. Netlify performs no client-side check of its own, so an
    // applicant with a large work-sample PDF never learns their application vanished
    // and we never learn they tried.
    //
    // The 8 MB cap applies to the WHOLE request, not to each file, so the text
    // fields and multipart overhead share the budget with the uploads. The ceiling
    // here is deliberately lower to leave room for the rest of the form.
    //
    // BUDGET and the figure quoted to applicants must stay in step. Quoting
    // Netlify&#39;s 8 MB while blocking at 7.5 MB tells someone with a 7.6 MB file
    // that they are under a limit they have just been refused for. If you change
    // one, change the other: the error message above and #upload-limit-note.
    //
    // This is a courtesy check only. Netlify still enforces the limit server-side,
    // and with JavaScript disabled the form behaves exactly as it did before.
    var BUDGET = 7.5 * 1024 * 1024;

    var form = document.querySelector(&#39;form[name=&#34;design-researcher-fall2026&#34;]&#39;);
    if (!form) return;

    var inputs = [form.querySelector(&#39;#resume&#39;), form.querySelector(&#39;#work-sample&#39;)]
      .filter(function (el) { return el; });
    var box = document.getElementById(&#39;upload-size-error&#39;);
    if (!inputs.length || !box) return;

    // Round UP. Plain toFixed(1) renders 7.5 MB + 1 byte as &#34;7.5 MB&#34;, so the
    // message would read &#34;7.5 MB, which is over the 7.5 MB limit&#34;.
    function mb(bytes) {
      return (Math.ceil(bytes / 1024 / 1024 * 10) / 10).toFixed(1) + &#39; MB&#39;;
    }

    function totalBytes() {
      return inputs.reduce(function (sum, input) {
        var file = input.files &amp;&amp; input.files[0];
        return sum + (file ? file.size : 0);
      }, 0);
    }

    function withinBudget() {
      var bytes = totalBytes();
      if (bytes &lt;= BUDGET) {
        box.style.display = &#39;none&#39;;
        box.textContent = &#39;&#39;;
        return true;
      }
      box.textContent = &#39;Your resume and work samples come to &#39; + mb(bytes) +
        &#39; together, which is over the 7.5 MB limit for attachments on this form.&#39; +
        &#39; Please compress the PDFs, or email them to jobs@superbloom.design.&#39;;
      box.style.display = &#39;&#39;;
      return false;
    }

    inputs.forEach(function (input) {
      input.addEventListener(&#39;change&#39;, withinBudget);
    });

    form.addEventListener(&#39;submit&#39;, function (event) {
      if (!withinBudget()) {
        event.preventDefault();
        box.scrollIntoView({ block: &#39;center&#39; });
      }
    });
  })();
&lt;/script&gt;
</description>
    </item>
    
    <item>
      <title>Apply for Superbloom Board of Directors</title>
      <link>https://superbloom.design/2024-directors-application/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/2024-directors-application/</guid>
      <description>
&lt;div class=&#34;indicates-required&#34;&gt;&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt; indicates required&lt;/div&gt;
&lt;form name=&#34;directors&#34; class=&#34;fullpage-form&#34; netlify&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;name&#34;&gt;Name &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;input type=&#34;text&#34; id=&#34;name&#34; name=&#34;name&#34; required /&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;email&#34;&gt;Email &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;input type=&#34;email&#34; id=&#34;email&#34; name=&#34;email&#34; required /&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;about&#34;&gt;Where can we learn more about you on the internet (
      e.g. LinkedIn, Website, Current Work Bio page, Social)? &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;p class=&#34;help-text&#34;&gt;If we can’t learn about you on the internet, please share anything that can help us learn more
      about you. &lt;/p&gt;
    &lt;textarea id=&#34;about&#34; name=&#34;about&#34; rows=&#34;5&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;reference&#34;&gt;Who is someone who can be a reference for your background in public
      interest work or communities relevant to Superbloom’s mission? &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;p class=&#34;help-text&#34;&gt;If you don’t have permission to share that person’s contact information now, we can follow up
      for that later.&lt;/p&gt;
    &lt;input type=&#34;reference&#34; id=&#34;reference&#34; name=&#34;reference&#34; required /&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;why-interested&#34;&gt;Share with us why you are interested in getting involved with Superbloom,
      and why you would be a good fit for our Board of Directors. &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;textarea id=&#34;why-interested&#34; name=&#34;why-interested&#34; rows=&#34;5&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;prior-experience&#34;&gt;Do you have any prior experience related
      to non-profits (board, advisory groups, work experience, or other)? &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;textarea id=&#34;prior-experience&#34; name=&#34;prior-experience&#34; rows=&#34;5&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;fieldset class=&#34;checkbox-group&#34;&gt;
      &lt;legend&gt;What would you be most interested in helping with? &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/legend&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;checkbox&#34; id=&#34;option1&#34; name=&#34;Nonprofit Administration &amp; Management&#34; /&gt;
        &lt;label for=&#34;option1&#34;&gt;Nonprofit Administration &amp; Management&lt;/label&gt;
      &lt;/div&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;checkbox&#34; id=&#34;option2&#34; name=&#34;Finance&#34; /&gt;
        &lt;label for=&#34;option2&#34;&gt;Finance&lt;/label&gt;
      &lt;/div&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;checkbox&#34; id=&#34;option3&#34; name=&#34;Fundraising&#34; /&gt;
        &lt;label for=&#34;option3&#34;&gt;Fundraising&lt;/label&gt;
      &lt;/div&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;checkbox&#34; id=&#34;option4&#34; name=&#34;Program Design &amp; Strategy&#34; /&gt;
        &lt;label for=&#34;option4&#34;&gt;Program Design &amp; Strategy&lt;/label&gt;
      &lt;/div&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;checkbox&#34; id=&#34;option5&#34; name=&#34;Legal Support&#34; /&gt;
        &lt;label for=&#34;option5&#34;&gt;Legal Support&lt;/label&gt;
      &lt;/div&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;checkbox&#34; id=&#34;option6&#34; name=&#34;Compliance&#34; /&gt;
        &lt;label for=&#34;option6&#34;&gt;Compliance&lt;/label&gt;
      &lt;/div&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;checkbox&#34; id=&#34;option7&#34; name=&#34;Programmatic Advising&#34; /&gt;
        &lt;label for=&#34;option7&#34;&gt;Programmatic Advising&lt;/label&gt;
      &lt;/div&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;checkbox&#34; id=&#34;option8&#34; name=&#34;Business Models &amp; Sustainability&#34; /&gt;
        &lt;label for=&#34;option8&#34;&gt;Business Models &amp; Sustainability&lt;/label&gt;
      &lt;/div&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;checkbox&#34; id=&#34;option9&#34; name=&#34;Policy / Advocacy &amp; Mobilization&#34; /&gt;
        &lt;label for=&#34;option9&#34;&gt;Policy / Advocacy &amp; Mobilization&lt;/label&gt;
      &lt;/div&gt;

      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;checkbox&#34; id=&#34;option10&#34; name=&#34;Communications &amp; Storytelling&#34; /&gt;
        &lt;label for=&#34;option10&#34;&gt;Communications &amp; Storytelling&lt;/label&gt;
      &lt;/div&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;checkbox&#34; id=&#34;option11&#34; name=&#34;Organizational Culture &amp; Health&#34; /&gt;
        &lt;label for=&#34;option11&#34;&gt;Organizational Culture &amp; Health&lt;/label&gt;
      &lt;/div&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;checkbox&#34; id=&#34;option12&#34; name=&#34;Scaling Organizations &amp; Systems&#34; /&gt;
        &lt;label for=&#34;option12&#34;&gt;Scaling Organizations &amp; Systems&lt;/label&gt;
      &lt;/div&gt;
    &lt;/fieldset&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;interest-more&#34;&gt;Please share more of your thinking in relation to the boxes you have checked &lt;span
        class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;textarea id=&#34;interest-more&#34; name=&#34;interest-more&#34; rows=&#34;5&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;input type=&#34;submit&#34; value=&#34;Apply&#34; class=&#34;button&#34; /&gt;
&lt;/form&gt;</description>
    </item>
    
    <item>
      <title>Artificial Intelligence</title>
      <link>https://superbloom.design/topics/artificial-intelligence/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/artificial-intelligence/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Asher Lipman</title>
      <link>https://superbloom.design/about/people/asher/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/asher/</guid>
      <description>&lt;p&gt;Asher Lipman is a designer and developer whose work operates at the intersection of civic technology, privacy, and ludic design. Asher has full stack developer skills with experience in open source software management, design research, and iterative prototyping. Asher comes to Superbloom from Helpful Places, where he helped maintain and promote an open-source solution for digital transparency in smart cities. Prior to that, he served as a Research Assistant at Cornell University’s Interplay Research Lab, where his work focused on non-utilitarian design schemes for robots and AI agents. Asher holds a Bachelors in Information Science, though in his free time he likes to focus more on his minors in Game Design and Creative Writing. Outside of work you will probably find him reading, most likely something by Claire North or Nick Harkaway, or concocting increasingly elaborate sandwiches like that yellow alien from Lilo &amp;amp; Stitch.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Ben Laurie</title>
      <link>https://superbloom.design/about/people/ben-laurie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/ben-laurie/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Ben Scott</title>
      <link>https://superbloom.design/about/people/ben-scott/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/ben-scott/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Bernard Tyers</title>
      <link>https://superbloom.design/about/people/bernard/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/bernard/</guid>
      <description>&lt;p&gt;Bernard works on open source software and digital public services where privacy, security, identity, accessibility, inclusion are vital. He’s led international user research, and designed services for vulnerable user groups. He’s contributed to the Python package manager, Yunohost, SecureDrop and Briar. Bernard is a founder of Open Source Design collective, an organisation that advocates for UX design in open source software, and is member of the Open Technology Fund advisory council. He holds an MSc in Human Centred Design dissertation on user mental models of the Off-The-Record encryption protocol for instant messaging. Before he came to the “Light Side” of technology, he was an engineer and systems administrator for 15+ years.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>branding</title>
      <link>https://superbloom.design/tags/branding/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/branding/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Brooke Hunter</title>
      <link>https://superbloom.design/about/people/brooke/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/brooke/</guid>
      <description></description>
    </item>
    
    <item>
      <title>browser extension</title>
      <link>https://superbloom.design/tags/browser-extension/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/browser-extension/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Cade Diehm</title>
      <link>https://superbloom.design/about/people/cade/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/cade/</guid>
      <description>&lt;p&gt;With a multi-disciplinary background in information security, interface politics and digital systems, Cade and his team at New Design Congress work tirelessly to tease out and weave threads that can be pulled together to build a truly hopeful future.&lt;/p&gt;
&lt;p&gt;In 2018, his influential essay On Weaponised Design, introduced the titular concept, a term that describes designed systems that harm users while behaving within normal parameters. His critiques on design ethics, decentralisation and open source bring nuance to the complexity of digital infrastructure. His work on the Para-Real, a term that describes the collision-point between digital platforms and the real world, is the focus of a research series about subcultures and solidarity networks building livelihoods in spite of platform exploitation, austerity and crisis.&lt;/p&gt;
&lt;p&gt;Cade&amp;rsquo;s work is equally advisory, applied and research-based. He has collaborated with PEN America, the University College London, the London College of Communication, Signal, Google, 
Mozilla, Bauhaus Earth, Webrecorder, Eyebeam, C/O Berlin, Open Archive, Superbloom, WYNG Foundation, the Pontifical Academy of Sciences, Furtherfield, Ink &amp;amp; Switch, the European Centre for Constitutional and Human Rights, the International Institute for the Environment and Development, the European Commission, Protocol Labs, the Deutschland Bundestag Prototype Fund, the Center for Digital Resilience, Consumer Reports, the Algorithmic Transparency Institute and many others.&lt;/p&gt;
&lt;p&gt;Prior to founding the New Design Congress, Cade spent six years leading design-focused digital security projects in Australia, the United States, Korea, Germany, Singapore and the United Kingdom. He was an information security researcher and head of production at the Berlin-based non-profit Tactical Tech, providing security consultation and bringing the NGO’s activism to audiences worldwide. He contributed to early prototypes of the secure messaging app Signal and was Chief Design Officer at SpiderOak, then a Snowden approved no-knowledge cloud storage company.&lt;/p&gt;
&lt;p&gt;From 1999 to 2006, Cade represented Australia in international disability swimming, and holds Australian and world records.&lt;/p&gt;
&lt;p&gt;Cade resides in Berlin with his partner and two Shiba Inus, Ripley and Kodak.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Carissa Yao</title>
      <link>https://superbloom.design/about/people/carissa/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/carissa/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Caroline Sinders</title>
      <link>https://superbloom.design/about/people/caroline/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/caroline/</guid>
      <description>&lt;p&gt;Caroline Sinders is an award winning critical designer, researcher, and artist. They’re the founder of human rights and design lab, Convocation Research + Design. For the past few years, they have been examining the intersections of artificial intelligence, intersectional justice, systems design, harm, and politics in digital conversational spaces and technology platforms. They have worked with the United Nations, Amnesty International, IBM Watson, the Wikimedia Foundation, and others. Sinders has held fellowships with the Harvard Kennedy School, Google’s PAIR (People and Artificial Intelligence Research group), Ars Electronica’s AI Lab, the Weizenbaum Institute, the Mozilla Foundation, Pioneer Works, Eyebeam, Ars Electronica, the Yerba Buena Center for the Arts, the Sci Art Resonances program with the European Commission, and the International Center of Photography. Their work has been featured in the Tate Exchange in Tate Modern, the Contemporary Art Center of New Orleans, Telematic Media Arts, Victoria and Albert Museum, MoMA PS1, LABoral, Wired, Slate, Hyperallergic, Clot Magazine, Quartz, the Channels Festival, and others. Sinders holds a Masters from New York University’s Interactive Telecommunications Program.&lt;/p&gt;
&lt;p&gt;They’ve been named by Forbes as an AI Designer to Watch in 2017, won the bronze award for Webby’s Anthem Award’s responsible technology category for a toolkit they created for technologists and community organizers for how to hold safe and caring events during COVID19, shortlisted for a Fast Company’s Innovation by Design Award in the Social Good Category for a product they lead design on, and they have provided insights, critique and feedback to internationally regulatory bodies such as the ICO and FTC on technology, design, digital harm, and policy.  Their artwork on disinformation has been described “work [that] helps us better understand how easily visual culture contributes to their credibility” by Hyperallergic.&lt;/p&gt;
&lt;p&gt;Caroline is currently based between London, UK and New Orleans, USA.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Carrie Winfrey</title>
      <link>https://superbloom.design/about/people/carrie-winfrey/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/carrie-winfrey/</guid>
      <description></description>
    </item>
    
    <item>
      <title>case studies</title>
      <link>https://superbloom.design/tags/case-studies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/case-studies/</guid>
      <description></description>
    </item>
    
    <item>
      <title>case study</title>
      <link>https://superbloom.design/formats/case-study/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/formats/case-study/</guid>
      <description></description>
    </item>
    
    <item>
      <title>censorship</title>
      <link>https://superbloom.design/tags/censorship/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/censorship/</guid>
      <description></description>
    </item>
    
    <item>
      <title>censorship circumvention</title>
      <link>https://superbloom.design/tags/censorship-circumvention/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/censorship-circumvention/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Chelsea McCullough</title>
      <link>https://superbloom.design/about/people/chelsea/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/chelsea/</guid>
      <description>&lt;p&gt;Dr. Chelsea McCullough brings decades of experience working at the intersection of government, technology, and community-led innovation. She focuses on translating between and across the public, private, social, and academic sectors to build shared language and common understanding so that diverse groups may address complex social and civic challenges.&lt;/p&gt;
&lt;p&gt;Chelsea directs initiatives that prioritize the ethical design and application of emerging technologies (including AI) based on principles of collaboration, inclusion, equity, and transparency. She integrates this work across several domains. In her roles as the Founder of Digi.City and a Strategic Advisor to Smart Cities Connect, she convenes government and industry leaders to build cohesive ecosystems. As a researcher, she focuses on resident-centered community engagement with city government. She has also led initiatives to co-design AI-enabled smart hand tools with skilled trade workers with the City of Austin, the Texas AFL-CIO, and Good Systems, a UT Grand Challenge. Chelsea is also an Instructor at Texas State University in Department of Political Science.&lt;/p&gt;
&lt;p&gt;Chelsea completed her PhD in Information Science from the School of Information and MA and BS degrees in Communication from The University of Texas at Austin. She is an NSF NRT Fellow in Ethical AI, a ZEIT-Stiftung Research Fellow with the City Science Lab in Hamburg, GE, a Simon Industrial &amp;amp; Professional Fellow at the University of Manchester (UK), a Marshall Memorial Fellow, and an Eisenhower Fellow.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>code of conduct</title>
      <link>https://superbloom.design/coc/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/coc/</guid>
      <description>&lt;h3 id=&#34;we-are-committed-to-providing-a-harassment-free-event-experience-for-everyone&#34;&gt;We are committed to providing a harassment-free event experience for everyone.&lt;/h3&gt;
&lt;p&gt;Harassment includes, but is not limited, to offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.&lt;/p&gt;
&lt;p&gt;Participants asked to stop any harassing behavior are expected to comply immediately. If a participant engages in harassing behavior, the organizers may take any action they deem appropriate, in consultation with the person reporting the harassing behavior. This may include warning the participant, asking them to leave the event or community space, or barring them from this and all future Superbloom events or community spaces.&lt;/p&gt;
&lt;p&gt;If you are being harassed, notice that someone else is being harassed, or have any other concerns, please approach a member of the Superbloom &lt;a href=&#34;https://superbloom.design/about/people&#34;&gt;team&lt;/a&gt;, or write to &lt;a href=&#34;mailto:coc@superbloom.design&#34;&gt;coc@superbloom.design&lt;/a&gt;. At an event, the Superbloom team members will introduce themselves at the start of the event, so that you are able to approach them directly in person. We will work with you to take appropriate action, up to and including contacting venue security or local law enforcement if necessary, though we will never escalate without your permission. We value your attendance and contributions, and we want you to be safe.&lt;/p&gt;
&lt;p&gt;This code of conduct applies to interactions between attendees during the course of their attendance at events, whether or not they occur at the event itself. This code of conduct also applies to community spaces convened or managed by Superbloom, e.g. the Superbloom/Simply Secure community Slack. This includes meetups, gatherings, and other social activities officially or unofficially related to our events are also covered by this Code of Conduct.&lt;/p&gt;
&lt;p&gt;We expect all participants to follow these rules at events, community gatherings, and associated online or offline spaces.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>coding</title>
      <link>https://superbloom.design/tags/coding/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/coding/</guid>
      <description></description>
    </item>
    
    <item>
      <title>community</title>
      <link>https://superbloom.design/tags/community/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/community/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Contact us</title>
      <link>https://superbloom.design/contact/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/contact/</guid>
      <description>&lt;p&gt;To join the conversation about usable security, follow us on Twitter (&lt;a
href=&#34;https://twitter.com/sprblm_&#34;&gt;@sprblm_&lt;/a&gt;) or join us on
Slack (email &lt;a href=&#34;mailto:slack@superbloom.design&#34;&gt;&lt;a href=&#34;mailto:slack@superbloom.design&#34;&gt;slack@superbloom.design&lt;/a&gt;&lt;/a&gt;
for an invitation).&lt;/p&gt;
&lt;p&gt;To express interest in collaborating with Superbloom, email us at &lt;a href=&#34;mailto:contact@superbloom.design&#34;&gt;&lt;a href=&#34;mailto:contact@superbloom.design&#34;&gt;contact@superbloom.design&lt;/a&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;To receive occasional email updates from us, please enter your email address
and subscribe to our newsletter:&lt;/p&gt;
&lt;script type=&#34;text/javascript&#34;&gt;var pleaseEnter = &#34;&#34;; &lt;/script&gt; &lt;script
&lt;p&gt;type=&amp;ldquo;text/javascript&amp;rdquo;
src=&amp;ldquo;&lt;a href=&#34;https://ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js%22%3E&#34;&gt;https://ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js&amp;quot;&amp;gt;&lt;/a&gt;&lt;/script&gt;&lt;/p&gt;
&lt;script type=&#34;text/javascript&#34;
src=&#34;https://s3.amazonaws.com/phplist/phplist-subscribe-0.2.min.js&#34;&gt;&lt;/script&gt;
&lt;div id=&#34;phplistsubscriberesult&#34;&gt;&lt;/div&gt; &lt;form
action=&#34;https://simsec.hosted.phplist.com/lists/?p=subscribe&amp;id=1&#34;
method=&#34;post&#34; id=&#34;phplistsubscribeform&#34;&gt; &lt;input type=&#34;text&#34; name=&#34;email&#34;
value=&#34;&#34; id=&#34;emailaddress&#34; /&gt; &lt;button type=&#34;submit&#34; class=&#34;button&#34;
id=&#34;phplistsubscribe&#34;&gt;Subscribe&lt;/button&gt; &lt;/form&gt;
</description>
    </item>
    
    <item>
      <title>CoRD</title>
      <link>https://superbloom.design/tags/cord/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/cord/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Cory Doctorow</title>
      <link>https://superbloom.design/about/people/cory/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/cory/</guid>
      <description></description>
    </item>
    
    <item>
      <title>COSCUP</title>
      <link>https://superbloom.design/community/events/coscup/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/community/events/coscup/</guid>
      <description>&lt;p&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>CTFG</title>
      <link>https://superbloom.design/tags/ctfg/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/ctfg/</guid>
      <description></description>
    </item>
    
    <item>
      <title>curated</title>
      <link>https://superbloom.design/formats/curated/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/formats/curated/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Dan Hon</title>
      <link>https://superbloom.design/about/people/dan-hon/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/dan-hon/</guid>
      <description>&lt;p&gt;Dan is an award-winning technologist who has worked in the field of online games, interactive advertising and public government digital services over the last 20 years. Over the past few years, his work has focussed on transforming digital services in government at the state and federal government in the United States. &lt;/p&gt;
&lt;p&gt;Dan was lead strategy consultant for &lt;a href=&#34;https://vision2023.cdt.ca.gov/&#34;&gt;Vision 2023&lt;/a&gt;, California’s Statewide Strategic Technology Plan; co-designed and was an instructor for the &lt;a href=&#34;https://mccourt.georgetown.edu/digital-fundamentals-for-public-impact/&#34;&gt;Digital Fundamentals for Public Impact&lt;/a&gt; course at the McCourt School of Public Policy; led the creation of California’s first digital service, the Child Welfare Digital Service; co-chaired the Code for America Summit, and is a keynote speaker and published writer on technology, design, government and ethics in technology. Dan has led award-winning creative work as Creative Director at Wieden + Kennedy for Nike, Coca-Cola, Sony and other clients, and Six to Start, the games startup co-founded with his brother has won Best of Show, Best Experimental and Best Game at SXSW. &lt;/p&gt;
&lt;p&gt;He has been writing online since the late 90s, and most recently has been writing the newsletter &lt;a href=&#34;https://newsletter.danhon.com/&#34;&gt;Things That Caught My Attention&lt;/a&gt; since 2014.&lt;/p&gt;
&lt;p&gt;Dan studied Law at the University of Cambridge, and software engineering at the University of Liverpool. More information about Dan and his previous work is available at &lt;a href=&#34;http://about.danhon.com/&#34;&gt;about.danhon.com&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Daniela Hernandez</title>
      <link>https://superbloom.design/about/people/daniela-hernandez/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/daniela-hernandez/</guid>
      <description>&lt;p&gt;Daniela has been working as a bookkeeper for the last 10 years. She is always eager to learn and grow in her role. In her personal life, she looks forward to time with family and friends and enjoys any opportunity to travel.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>data visualization</title>
      <link>https://superbloom.design/tags/data-visualization/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/data-visualization/</guid>
      <description></description>
    </item>
    
    <item>
      <title>decentralization</title>
      <link>https://superbloom.design/tags/decentralization/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/decentralization/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Decentralization</title>
      <link>https://superbloom.design/topics/decentralization/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/decentralization/</guid>
      <description></description>
    </item>
    
    <item>
      <title>design</title>
      <link>https://superbloom.design/tags/design/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/design/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Design Coaching</title>
      <link>https://superbloom.design/work/ux-guidance/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/work/ux-guidance/</guid>
      <description>&lt;h2 id=&#34;help-when-you-need-it&#34;&gt;Help when you need it&lt;/h2&gt;
&lt;p&gt;We’re here to help you get unstuck on your design challenge, over the barriers to adoption, support in centering the
most vulnerable users by helping you with human-centered design in your software development practice or organizational
processes.&lt;/p&gt;
&lt;p&gt;UX design isn&amp;rsquo;t just a &amp;ldquo;nice to have,&amp;rdquo; even in resource-strapped contexts like human rights advocacy and open-source
software. Making sure that people can actually use the tools you&amp;rsquo;re developing is a crucial part of making an impact. We
can help. Our team of seasoned designers has experience in nonprofit, corporate, and academic contexts, and we can help
you and your team work through the thorniest design issues. We specialize in tools around privacy, security,
decentralization, transparency, data visualization, and civic tech. We envision a world in which tools used by
vulnerable communities have users centered in their design process. Secure tools can&amp;rsquo;t have an impact if no one is using
them, and security and privacy should not be a privilege.&lt;/p&gt;
&lt;p&gt;We are proud to serve as design coaches for &lt;a href=&#34;https://www.opentech.fund/&#34;&gt;Open Tech Fund&lt;/a&gt; and &lt;a href=&#34;https://prototypefund.de/&#34;&gt;Prototype Fund&lt;/a&gt; grantees. We also work with other funders as well as independent teams.&lt;/p&gt;
&lt;p&gt;A multi-lingual team of experts with over 50 years of experience in design, facilitation, and research. We’re here to
help you get unstuck on your design challenge, over the barriers to adoption, support in centering the most vulnerable
users by helping you with human-centered design in your software development practice or organizational processes.&lt;/p&gt;
&lt;h3 id=&#34;what-you-get&#34;&gt;What you get&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Experts in human-centered UX as you need them&lt;/li&gt;
&lt;li&gt;Support with solutions to problems without having to hire more staff&lt;/li&gt;
&lt;li&gt;An approach that centers the most vulnerable needs&lt;/li&gt;
&lt;li&gt;An inclusive, international, and security and privacy focused perspective&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;building-your-knowledge-strengthening-your-team&#34;&gt;Building your knowledge, strengthening your team&lt;/h3&gt;
&lt;p&gt;Our goal isn&amp;rsquo;t just to solve your UX problems – we want to help you and your team gain the skills you need. To that end,
we build, curate, and recommend resources to delve deeper into issues themselves. We&amp;rsquo;ve written articles ourselves, such
as &lt;a href=&#34;https://superbloom.design/learning/resources/color-message&#34;&gt;Don&amp;rsquo;t Let Color Drown Out Your Message&lt;/a&gt; and the &lt;a href=&#34;https://superbloom.design/learning/blog/wireframing-intro&#34;&gt;Illustrated Quick-Start Guide to Wireframing&lt;/a&gt; from our &lt;a href=&#34;&#34;&gt;Knowledge Base&lt;/a&gt;. We&amp;rsquo;ve also put together a
&lt;a href=&#34;&#34;&gt;Starter Pack&lt;/a&gt; of templates specifically geared towards open-source software.&lt;/p&gt;
&lt;p&gt;For teams that want to hire a professional designer, Simply Secure can help scope a creative brief and help structure
projects for success integrating design and research into technical teams. Learn more about &lt;a href=&#34;https://superbloom.design/learning/blog/creative-briefs&#34;&gt;contracting creatives&lt;/a&gt; and how to organize your team for success.&lt;/p&gt;
&lt;p&gt;We also provide peer support and discussion through our &lt;a href=&#34;&#34;&gt;community building&lt;/a&gt;
activities.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;&#34;&gt;Book a Coaching&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/assets/img/PeopleSketching.jpg&#34; alt=&#34;Developers sketching wireframes on paper.&#34; width=&#34;750&#34; height=&#34;563&#34;&gt;

&lt;em&gt;Developers sketching wireframes of analogous websites during a hands-on user experience guidance session.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;more-information&#34;&gt;More Information&lt;/h2&gt;
&lt;h3 id=&#34;what-can-we-help-with&#34;&gt;What can we help with&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Project scoping and planning&lt;/li&gt;
&lt;li&gt;Information architecture, navigation, and overall organization&lt;/li&gt;
&lt;li&gt;Wireframes and screen flow&lt;/li&gt;
&lt;li&gt;Onboarding experience&lt;/li&gt;
&lt;li&gt;Dealing with documentation&lt;/li&gt;
&lt;li&gt;Identifying user needs&lt;/li&gt;
&lt;li&gt;Getting usability feedback&lt;/li&gt;
&lt;li&gt;Visual design, identity, and branding&lt;/li&gt;
&lt;li&gt;Creating a style guide&lt;/li&gt;
&lt;li&gt;Icons, colors, and visual language&lt;/li&gt;
&lt;li&gt;Writing for in-app copy, app store descriptions, and websites&lt;/li&gt;
&lt;li&gt;Service design, including multi-factor authentication&lt;/li&gt;
&lt;li&gt;In addition to general UX guidance, we also offer a specialized &lt;a href=&#34;https://superbloom.design/what-we-do/usable-security-audit&#34;&gt;Usable Security
Review&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Even if you don&amp;rsquo;t quite know what you need, we can help you figure it out!&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;what-to-bring-to-your-coaching&#34;&gt;What to bring to your coaching&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;A physical notebook and pen&lt;/li&gt;
&lt;li&gt;A computer&lt;/li&gt;
&lt;li&gt;As many team members as you wish&lt;/li&gt;
&lt;li&gt;Any demos, mock-ups, or sketches you may have&lt;/li&gt;
&lt;li&gt;A list of challenges or blocks&lt;/li&gt;
&lt;li&gt;A list of questions and goals&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;our-coaches&#34;&gt;Our Coaches&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/georgia/&#34;&gt;Georgia Bullen&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/eileen/&#34;&gt;Eileen Wagner&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/ame/&#34;&gt;Ame Elliott&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/lisa/&#34;&gt;Lisa Steingräber&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/rae/&#34;&gt;Rae McKelvey&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/cade/&#34;&gt;Cade Diehm&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/bernard/&#34;&gt;Bernard Tyers&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/nina/&#34;&gt;Nina Alter&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/ngoc/&#34;&gt;Ngọc Triệu&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/about/people/kelsey/&#34;&gt;Kelsey Smith&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Interested in coaching with us? &lt;a href=&#34;&#34;&gt;Reach out.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;&#34;&gt;Book a Coaching&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>design insights</title>
      <link>https://superbloom.design/formats/design-insights/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/formats/design-insights/</guid>
      <description></description>
    </item>
    
    <item>
      <title>design insights</title>
      <link>https://superbloom.design/formats/workshop/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/formats/workshop/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Design Under Pressure</title>
      <link>https://superbloom.design/topics/design-under-pressure/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/design-under-pressure/</guid>
      <description></description>
    </item>
    
    <item>
      <title>desktop app</title>
      <link>https://superbloom.design/tags/desktop-app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/desktop-app/</guid>
      <description></description>
    </item>
    
    <item>
      <title>diary study</title>
      <link>https://superbloom.design/formats/diary-study/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/formats/diary-study/</guid>
      <description></description>
    </item>
    
    <item>
      <title>digital rights</title>
      <link>https://superbloom.design/tags/digital-rights/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/digital-rights/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Digital Rights</title>
      <link>https://superbloom.design/topics/digital-rights/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/digital-rights/</guid>
      <description></description>
    </item>
    
    <item>
      <title>digital security</title>
      <link>https://superbloom.design/tags/digital-security/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/digital-security/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Dis/Misinformation</title>
      <link>https://superbloom.design/topics/dis-misinformation/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/dis-misinformation/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Django Skorupa</title>
      <link>https://superbloom.design/about/people/django-skorupa/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/django-skorupa/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Dorothy Chou</title>
      <link>https://superbloom.design/about/people/dorothy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/dorothy/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Eileen Wagner</title>
      <link>https://superbloom.design/about/people/eileen/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/eileen/</guid>
      <description>&lt;p&gt;A logician by training, Eileen has a keen eye for structure and detail. Making sense of complex technologies is her bread and butter. As a designer, she focuses on information architecture, content strategy, and interaction design.&lt;/p&gt;
&lt;p&gt;She loves supporting teams and organizations in UX design, and aspires to make her solutions more available to the public. To that end, she founded the project &lt;a href=&#34;http://decentpatterns.xyz/&#34;&gt;Decentralization Off The Shelf&lt;/a&gt;, a pattern library for decentralized technologies. She previously campaigned for public interest technology at the Open Knowledge Foundation Germany. There she helped establish the Prototype Fund, the first public funding program for open source projects in Germany.&lt;/p&gt;
&lt;p&gt;When she’s not buried in sticky notes, Eileen enjoys singing and arranging barbershop music.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>equity</title>
      <link>https://superbloom.design/tags/equity/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/equity/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Erika Owens</title>
      <link>https://superbloom.design/about/people/erika-owens/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/erika-owens/</guid>
      <description>&lt;p&gt;Erika Owens is Co-Director at Open Parliament TV. Previously, Erika was Co-Director at OpenNews, where she supported a thriving network and created inclusive, caring spaces for the journalism-tech community. Erika also serves on the board of the Movement Alliance Project, has trained as a donor organizer with Bread and Roses Community Fund, and recently completed a John S. Knight Journalism Fellowship at Stanford University. She is based in Sheffield, UK and loves nonprofit journalism, people watching, and laughing heartily.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Eriol Fox</title>
      <link>https://superbloom.design/about/people/eriol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/eriol/</guid>
      <description>&lt;p&gt;Eriol is a ‘generalist’ senior designer with 10+ years of experience in design, technology and human rights and has been leading projects and teams for the last 5. Their bachelor&amp;rsquo;s degree was in Time-based media, where they explored the nature of communicating digitally, personal information exchange and vulnerability in the early 2000s. They then pivoted into a design career while doing volunteer community work in Cardiff UK across Environmental, Education, Asylum Seeker and Arts issues and gained their masters in Visual Communication at the University of South Wales. Eriol has worked in insurance, finance, legal, housing and family tech sectors before moving into the open-source and human rights as a designer. They are most happy when working as part of a team of designers, developers and product folks with a focus on collaboration and cross-function conversation and appreciation.&lt;/p&gt;
&lt;p&gt;They are passionate about intersectional inclusion and actively works to make tech and design more inclusive through their talk ‘&lt;a href=&#34;https://www.youtube.com/watch?v=D1RZiIcnEWU&amp;amp;list=PLwz4EueITgvmJzrNWbGkAMeDVLlOWQuch&amp;amp;index=14&amp;amp;t=1s&#34;&gt;Diversity in Design&lt;/a&gt;’ and also ensuring design is &amp;rsquo;trauma informed&amp;rsquo; through their talk &amp;lsquo;&lt;a href=&#34;https://www.youtube.com/watch?v=jx1K8VZ9yeg&amp;amp;list=PLwz4EueITgvmJzrNWbGkAMeDVLlOWQuch&amp;amp;index=5&#34;&gt;UX research and Ethnographic design for humanitarian technology&lt;/a&gt;&amp;rsquo;. Eriol is also part of a number of communities including &lt;a href=&#34;https://opensourcedesign.net/&#34;&gt;Open Source Design&lt;/a&gt;, &lt;a href=&#34;https://sustainoss.org/working-groups/design-and-ux/&#34;&gt;Sustain OSS Design &amp;amp; UX Working group&lt;/a&gt; and their local &lt;a href=&#34;https://bristolpride.co.uk/&#34;&gt;Pride festival committee&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Eriol is currently studying part-time for a PhD in Computer Science at &lt;a href=&#34;https://openlab.ncl.ac.uk/people/eriol-fox/&#34;&gt;Newcastle University’s Open Lab&lt;/a&gt; the research is funded by &lt;a href=&#34;http://www.northernbridge.ac.uk/&#34;&gt;Northern Bridge&lt;/a&gt; and is around &lt;a href=&#34;https://github.com/Erioldoesdesign/Design_HOSS_PhD&#34;&gt;how designers get involved in humanitarian focused open source software projects&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>events</title>
      <link>https://superbloom.design/tags/events/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/events/</guid>
      <description></description>
    </item>
    
    <item>
      <title>external</title>
      <link>https://superbloom.design/formats/external/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/formats/external/</guid>
      <description></description>
    </item>
    
    <item>
      <title>facilitation</title>
      <link>https://superbloom.design/tags/facilitation/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/facilitation/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Feira @ The Global Gathering</title>
      <link>https://superbloom.design/community/events/feira-the-global-gathering/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/community/events/feira-the-global-gathering/</guid>
      <description>&lt;p&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Fiscal Sponsorship Interest</title>
      <link>https://superbloom.design/fiscal-sponsorship-interest/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/fiscal-sponsorship-interest/</guid>
      <description>&lt;div class=&#34;indicates-required&#34;&gt;&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt; indicates required&lt;/div&gt;
&lt;form name=&#34;fsp-interest&#34; class=&#34;fullpage-form&#34; netlify&gt;
  &lt;h3&gt;About You&lt;/h3&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;name&#34;&gt;Name &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;input type=&#34;text&#34; id=&#34;name&#34; name=&#34;name&#34; required /&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;email&#34;&gt;Email &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;input type=&#34;email&#34; id=&#34;email&#34; name=&#34;email&#34; required /&gt;
  &lt;/div&gt;
  &lt;h3&gt;About Your Work&lt;/h3&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;project-name&#34;&gt;Name of Project or Initiative&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;
    &lt;input type=&#34;text&#34; id=&#34;project-name&#34; name=&#34;project-name&#34; required /&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;website&#34;&gt;Website of Project or Initiative&lt;/label&gt;
    &lt;input type=&#34;text&#34; id=&#34;website&#34; name=&#34;website&#34; /&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;overview&#34;&gt;Please give a general overview of the project/initiative, with a focus on the theory of
      change. What change does your project seek to bring about in the world? How, and with whom? Please include detail
      about the type of work/interventions, e.g. research, advocacy, policy.&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;(Max 2000 characters)&lt;/label&gt;
    &lt;textarea id=&#34;overview&#34; name=&#34;overview&#34; rows=&#34;5&#34; maxlength=&#34;2000&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;mission-align&#34;&gt;Superbloom’s mission is to change who technology serves. We believe technology design is
      integral to the open source movement and should be leveraged to affect societal change. How does your project
      align with this mission?&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;(Max 2000 characters)&lt;/label&gt;
    &lt;textarea id=&#34;mission-align&#34; name=&#34;mission-align&#34; rows=&#34;5&#34; maxlength=&#34;2000&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;goals&#34;&gt;What are the 3-5 goals for your program? For example, grow team to #X of staff members to
      facilitate ABC program initiative; build partnerships with XYZ organizations; fundraise $Y to support ABC program
      initiative.&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;(Max 2000 characters)&lt;/label&gt;
    &lt;textarea id=&#34;goals&#34; name=&#34;goals&#34; rows=&#34;5&#34; maxlength=&#34;2000&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;

  &lt;h3&gt;Governance&lt;/h3&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;governance&#34;&gt;Please tell us about your current governance structure – do you have an advisory board? How
      are decisions made? Please share any information you have, including names, responsibilities, and relationship
      with the project.&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;(Max 2000 characters)&lt;/label&gt;
    &lt;textarea id=&#34;governance&#34; name=&#34;governance&#34; rows=&#34;5&#34; maxlength=&#34;2000&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;team&#34;&gt;Please tell us about your team – roles, responsibilities, names, and location. How many are
      volunteers? How many are being paid?&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;(Max 2000 characters)&lt;/label&gt;
    &lt;textarea id=&#34;team&#34; name=&#34;team&#34; rows=&#34;5&#34; maxlength=&#34;2000&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;fieldset class=&#34;checkbox-group&#34;&gt;
      &lt;legend&gt;Do you have a legal entity related to this project?&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/legend&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;radio&#34; id=&#34;option1&#34; name=&#34;legal-entity&#34; value=&#34;yes&#34; required /&gt;
        &lt;label for=&#34;option1&#34;&gt;Yes&lt;/label&gt;
      &lt;/div&gt;
      &lt;div class=&#34;checkbox-group__item&#34;&gt;
        &lt;input type=&#34;radio&#34; id=&#34;option2&#34; name=&#34;legal-entity&#34; value=&#34;no&#34; required /&gt;
        &lt;label for=&#34;option2&#34;&gt;No&lt;/label&gt;
      &lt;/div&gt;
    &lt;/fieldset&gt;
  &lt;/div&gt;

  &lt;h3&gt;About Your Fiscal Sponsorship Search&lt;/h3&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;deadline&#34;&gt;Are you working to a deadline to find a Fiscal Host? If so, what is your deadline? &lt;span
        class=&#34;asterisk&#34;&gt;*&lt;/span&gt;(Max 2000 characters)&lt;/label&gt;
    &lt;textarea id=&#34;deadline&#34; name=&#34;deadline&#34; rows=&#34;5&#34; maxlength=&#34;2000&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;other_hosts&#34;&gt;Are you talking to other possible Fiscal Hosts?&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;(Max 2000 characters)&lt;/label&gt;
    &lt;textarea id=&#34;other_hosts&#34; name=&#34;other_hosts&#34; rows=&#34;5&#34; maxlength=&#34;2000&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;funding&#34;&gt;Do you have existing funding? If yes, please supply details or a link to any
      information as applicable.&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;(Max 2000 characters)&lt;/label&gt;
    &lt;textarea id=&#34;funding&#34; name=&#34;funding&#34; maxlength=&#34;2000&#34; rows=&#34;5&#34; required&gt;&lt;/textarea&gt;
  &lt;/div&gt;
  &lt;div class=&#34;input-item&#34;&gt;
    &lt;label for=&#34;additional-info&#34;&gt;Is there anything else you&#39;d like us to know about your work, your team, or your
      immediate needs? (Max 2000 characters)&lt;/label&gt;
    &lt;textarea id=&#34;additional-info&#34; name=&#34;additional-info&#34; maxlength=&#34;2000&#34; rows=&#34;5&#34;&gt;&lt;/textarea&gt;
  &lt;/div&gt;

  &lt;input type=&#34;submit&#34; value=&#34;Apply&#34; class=&#34;button&#34; /&gt;
&lt;/form&gt;
</description>
    </item>
    
    <item>
      <title>FOSDEM</title>
      <link>https://superbloom.design/community/events/fossdem/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/community/events/fossdem/</guid>
      <description></description>
    </item>
    
    <item>
      <title>fsps</title>
      <link>https://superbloom.design/tags/fsps/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/fsps/</guid>
      <description></description>
    </item>
    
    <item>
      <title>funding</title>
      <link>https://superbloom.design/tags/funding/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/funding/</guid>
      <description></description>
    </item>
    
    <item>
      <title>gdpr</title>
      <link>https://superbloom.design/tags/gdpr/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/gdpr/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Gemma Lane</title>
      <link>https://superbloom.design/about/people/gemma-lane/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/gemma-lane/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Geoffrey MacDougall</title>
      <link>https://superbloom.design/about/people/geoffrey-macdougall/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/geoffrey-macdougall/</guid>
      <description>&lt;p&gt;Geoffrey is an accomplished leader and strategist in innovation change management. With more than 25 years experience in fundraising and advocacy, he has raised more than $75M in public, private, and philanthropic funding for start-ups, nonprofits, and established companies, and engaged millions of people in advocacy campaigns.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>George Danezis</title>
      <link>https://superbloom.design/about/people/george-danezis/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/george-danezis/</guid>
      <description></description>
    </item>
    
    <item>
      <title>George Danezis</title>
      <link>https://superbloom.design/about/people/george/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/george/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Georgia Bullen</title>
      <link>https://superbloom.design/about/people/georgia/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/georgia/</guid>
      <description>&lt;p&gt;Georgia joined Superbloom (previously Simply Secure) in 2018, returning to her first passions — usability and human centered design. She has been working to change who technology serves as an advocate in the internet health movement focusing on issues such as security, privacy, and equitable access to technology. Her work has focused on the intersection of human-centered design, communities, physical space, and technology – e.g. how technology intersects with human rights — access to information and the right to communicate. Georgia brings over 20 years of experience at the intersection of usability and design, technology, data, policy, and nonprofit leadership.&lt;/p&gt;
&lt;p&gt;In addition to her work at Superbloom, Georgia is the chair of the Advisory Committee for Measurement Lab and serves as an advisor to TechCongress. Georgia came to Superbloom from New America’s Open Technology Institute, where she had most recently been a core member of the leadership team. Georgia studied Psychology and Human-Computer Interaction at Carnegie Mellon and Urban Planning at Columbia University’s Graduate School of Architecture, Planning and Preservation. Her previous work and projects are available at &lt;a href=&#34;https://georgiabullen.com&#34;&gt;georgiabullen.com&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Gina Giampaolo</title>
      <link>https://superbloom.design/about/people/gina-giampaolo/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/gina-giampaolo/</guid>
      <description></description>
    </item>
    
    <item>
      <title>guide</title>
      <link>https://superbloom.design/formats/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/formats/guide/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Gus Andrews</title>
      <link>https://superbloom.design/about/people/gus-andrews/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/gus-andrews/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Gus Hosein</title>
      <link>https://superbloom.design/about/people/gus-hosein/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/gus-hosein/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Gus Narea</title>
      <link>https://superbloom.design/about/people/gus-narea/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/gus-narea/</guid>
      <description></description>
    </item>
    
    <item>
      <title>harassment</title>
      <link>https://superbloom.design/tags/harassment/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/harassment/</guid>
      <description></description>
    </item>
    
    <item>
      <title>high-risk</title>
      <link>https://superbloom.design/tags/high-risk/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/high-risk/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Human-Centered Design</title>
      <link>https://superbloom.design/topics/human-centered-design/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/human-centered-design/</guid>
      <description></description>
    </item>
    
    <item>
      <title>identity</title>
      <link>https://superbloom.design/tags/identity/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/identity/</guid>
      <description></description>
    </item>
    
    <item>
      <title>information architecture</title>
      <link>https://superbloom.design/tags/information-architecture/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/information-architecture/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Internet of Things</title>
      <link>https://superbloom.design/topics/internet-of-things/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/internet-of-things/</guid>
      <description></description>
    </item>
    
    <item>
      <title>internet of things (IoT)</title>
      <link>https://superbloom.design/tags/iot/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/iot/</guid>
      <description></description>
    </item>
    
    <item>
      <title>internet shutdowns</title>
      <link>https://superbloom.design/tags/internet-shutdowns/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/internet-shutdowns/</guid>
      <description></description>
    </item>
    
    <item>
      <title>interviews</title>
      <link>https://superbloom.design/tags/interviews/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/interviews/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Iohanna Nicenboim</title>
      <link>https://superbloom.design/about/people/iohanna/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/iohanna/</guid>
      <description>&lt;p&gt;Iohanna Nicenboim is a designer and researcher, focusing on artificial intelligence and IoT in everyday life. Through design fictions she highlights social and ethical issues we might encounter in the future. She recently worked for the Connected Everyday Lab in TU Delft and is a ThingsCon fellow.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Jackie Lu</title>
      <link>https://superbloom.design/about/people/jackie-lu/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/jackie-lu/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Jackie Lu</title>
      <link>https://superbloom.design/about/people/jackie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/jackie/</guid>
      <description></description>
    </item>
    
    <item>
      <title>James Vasile</title>
      <link>https://superbloom.design/about/people/james-vasile/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/james-vasile/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://startpage.com/?query=james%20vasile&#34;&gt;James Vasile&lt;/a&gt; has fifteen years’ experience as a user, developer, advocate and advisor in the free and open source software world. His expertise is in software licensing and community-building, as well as non-profit and small business startup. He focuses on free software and open source production, although his work and interests often take him far beyond the world of software. Much of what James does involves teaching people how to build successful businesses around free software and ensuring licensing alignment in multisource FOSS stacks. James&amp;rsquo;s technical experience also allows him to act as outsource CTO/Architect, due-diligence open source expert, new venture advisor, convening facilitator, and more.&lt;/p&gt;
&lt;p&gt;James currently serves on the governing or advisory boards of &lt;a href=&#34;https://horizonspbc.com/&#34;&gt;Horizons&lt;/a&gt;, &lt;a href=&#34;https://www.bravenewsoftware.org/&#34;&gt;Brave New Software&lt;/a&gt;, and the &lt;a href=&#34;https://opentechstrategies.com/&#34;&gt;Electronic Frontier Foundation&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In addition to his work with OTS, James was the founding Director of the Open Internet Tools Project, which during his tenure originated a variety of excellent community-based projects. These include Techno-Activism Third Mondays (a meetup that gathers people in over 20 cities around the world every month), the Circumvention Tech Festival (which has become the Internet Freedom Festival), and a 1000+ volunteer translation project now know as Localization Lab. He was also a founding board member of Overview Services, which made open source software that powers Pulitzer-winning data journalism.&lt;/p&gt;
&lt;p&gt;Previously, James was a Senior Fellow at the &lt;a href=&#34;http://softwarefreedom.org/&#34;&gt;Software Freedom Law Center&lt;/a&gt;, where he advised and supported a wide range of free software efforts.&lt;/p&gt;
&lt;p&gt;James was a Director of the &lt;a href=&#34;http://freedomboxfoundation.org/&#34;&gt;FreedomBox Foundation&lt;/a&gt;. He helped boot up and served on the board of Open Source Matters, the non-profit behind Joomla. He remains active in several technology development efforts. His FreedomBox work has been recognized by an Innovation Award at Contact Summit 2011 as well as an &lt;a href=&#34;https://www.freedomboxfoundation.org/news/AshokaChangemakers2/&#34;&gt;Ashoka ChangeMaker&amp;rsquo;s award for Citizen&amp;rsquo;s Media&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;James frequently speaks and writes about technology trends and free software. You can learn more about him from his &lt;a href=&#34;https://github.com/jvasile&#34;&gt;GitHub activity&lt;/a&gt; and his &lt;a href=&#34;https://www.linkedin.com/in/jamesvasile/&#34;&gt;LinkedIn profile&lt;/a&gt;, or by connecting with him on &lt;a href=&#34;https://fosstodon.org/@jamesvasile&#34;&gt;Mastodon&lt;/a&gt; or &lt;a href=&#34;https://twitter.com/jamesvasile&#34;&gt;X&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Jamie Tomasello</title>
      <link>https://superbloom.design/about/people/jamie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/jamie/</guid>
      <description>&lt;p&gt;James Tomasello has built global multidisciplinary operations, security, compliance, customer success, and trust and safety teams at internet service providers, security companies, law firms, and nonprofits for over 25 years. She/he is currently a Principal Security Advisor and founding team member of Credible Security, a cybersecurity firm focused on delivering tailored and effective solutions for organizations of all shapes and sizes. She/he finds joy in empowering teams and contributing to a culture where psychological safety is prioritized. Additionally, James is the founder of Keel Prism Travel, a travel management company that provides tailored travel logistics and travel incident response services for nonprofits and early stage startups. James has been a certified Mental Health First Aid Trainer. She/he is a Certified Information Privacy Professional (both CIPP/US and CIPT) and has a Bachelor of Science degree in Interdisciplinary Studies with a concentration in Psychology and double minors in Sociology and Trauma and Resistance from East Tennessee State University.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Jan Dittrich</title>
      <link>https://superbloom.design/about/people/jan/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/jan/</guid>
      <description>&lt;p&gt;Jan is a design researcher and anthropologist. After working for USEEDS° and Wikimedia Germany e.V. they now work on their PhD at the University of Siegen.&lt;/p&gt;
&lt;p&gt;I focus on researching user needs with qualitative methods. How I do this I have written down in a little online book: urbook.fordes.de/.  I also use statistical methods, surveys, usability testing and heuristic analysis.  I would like to expand my skills and knowledge of participatory design in open source projects. I have used PD in some projects at Wikimedia.  I have a solid understanding of UX design and its principles.  I have experience in working with design systems and created a small one myself for Wikimedia Germany’s donation page.  I do some programming myself (JavaScript, Python, some Clojure and R) and I worked with and in Open Source communities, so I have a good understanding of open source software creation.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Jasmine McNealy</title>
      <link>https://superbloom.design/about/people/jasmine/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/jasmine/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Jill Townley</title>
      <link>https://superbloom.design/about/people/jill-townley/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/jill-townley/</guid>
      <description>&lt;p&gt;Jill coordinates research projects and player communication for the Eterna game platform, creating the puzzles that collect RNA sequences designed by Eterna players to be experimentally tested by RNA researchers as part of their larger research goals.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Johanna Barnbeck</title>
      <link>https://superbloom.design/about/people/johanna-barnbeck/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/johanna-barnbeck/</guid>
      <description>&lt;p&gt;Johanna is a creative consultant, science communicator and artistic researcher. As founder of &lt;a href=&#34;https://spreadthenerd.net/&#34;&gt;Spread the Nerd&lt;/a&gt;, a Berlin based agency for science communication and format development, she makes research come alive. She is enthusiastic about strategic communication, creative ways of engaging different audiences, visual communication and artistic approaches to scientific topics.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Join</title>
      <link>https://superbloom.design/community/join/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/community/join/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Join the conversation on Slack</title>
      <link>https://superbloom.design/work/slack/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/work/slack/</guid>
      <description>

&lt;h2&gt;Join the Simply Secure brain trust! &lt;/h2&gt;
  &lt;p&gt;Contribute your voice to our community of practitioners on group discussion tool &lt;a href=&#34;https://www.slack.com&#34;&gt;Slack,&lt;/a&gt; where we share tips, support one another’s work, and collectively make sense of the latest developments in security and UX.&lt;/p&gt;

&lt;a href=&#34;mailto:slack@superbloom.design&#34; class=&#34;button button--primary read-more&#34;&gt;Email to join our public Slack.&lt;/a&gt;

&lt;p&gt;Here&#39;s a summary of &lt;a href=&#34;https://superbloom.design/learning/blog/conversations-from-slack&#34;&gt; some past discussion in the Simply Secure Slack.



</description>
    </item>
    
    <item>
      <title>Jon Rogers</title>
      <link>https://superbloom.design/about/people/jon-rogers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/jon-rogers/</guid>
      <description>&lt;p&gt;Jon Rogers is Professor of Design and Creative Technology at &lt;a href=&#34;https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.northumbria.ac.uk%2F&amp;amp;data=04%7C01%7Cjon.rogers%40northumbria.ac.uk%7C81987d82884d49f6598708d8b3f15dfb%7Ce757cfdd1f354457af8f7c9c6b1437e3%7C0%7C0%7C637457196536618944%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;amp;sdata=D2FdH4DVcr5QCUh%2Fa%2BqfTtR8huO4xQQCbQRRa6pVmp4%3D&amp;amp;reserved=0&#34;&gt;Northumbria University&lt;/a&gt;  with twenty five years&amp;rsquo; experience working at the interface between design and emerging technologies. Following a recent three year  fellowship at Mozilla Berlin, he is now based in Northumbria working on a range of projects exploring how we can start to build trust in the creation and development of the Internet of Things.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Jonathan Romano</title>
      <link>https://superbloom.design/about/people/jonathan-romano/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/jonathan-romano/</guid>
      <description>&lt;p&gt;Jonathan is a software engineer and creative. Following several years as lead developer for the Eterna scientific discovery game, he co-founded and is executive director of Frameshifter, a new nonprofit organization fiscally sponsored by Superbloom Design, engaging the public in scientific research through gamification, collective and hybrid intelligence, and human-centered design. Jonathan operates at the nexus of science, technology, creativity, communities, and public benefit and with interests spanning R&amp;amp;D, software architecture and developer experience, arts and digital media, human computer interaction, information management, collaboration, and education&lt;/p&gt;
&lt;!-- notionvc: e6a37647-e2a5-470a-ad64-d8324cec5599 --&gt;</description>
    </item>
    
    <item>
      <title>Jose René Gutiérrez</title>
      <link>https://superbloom.design/about/people/jose-rene-gutierrez/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/jose-rene-gutierrez/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Júlia Racskó</title>
      <link>https://superbloom.design/about/people/julia-racsko/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/julia-racsko/</guid>
      <description>&lt;p&gt;Julia Racsko is a senior product designer who combines analytical and creative thinking to get to the core of how our digital media environment became so exhausting, and how to design a nourishing one that is based on a holistic understanding of attention as a connection.&lt;/p&gt;
&lt;p&gt;She has lived, studied, and worked in Budapest and Milano as an illustrator before turning towards product design. She then moved to Geneva, where she completed her master’s degree at HEAD exploring the effects of the attention economy and the possible remedies. The results of this research and the exploration of the concept ‘attention as a connection’ are shared in her talk ‘Attentive Design’ (&lt;a href=&#34;https://interaction20.ixda.org/program/attentive-design-a-quest-for-a-sustainable-model-of-attention&#34;&gt;Interaction20&lt;/a&gt;, &lt;a href=&#34;https://beyondtellerrand.com/events/dusseldorf-2021/speakers/julia-racsko&#34;&gt;Beyond Tellerrand&lt;/a&gt;). She also led the design function in an IoT project in collaboration with EPFL and prototyped the device in Shenzhen.&lt;/p&gt;
&lt;p&gt;She is currently an in-house product designer at Steady Media in Berlin helping content creators find independence by owning their audience, so they can create a healthier media environment for all of us. She is also nourishing her illustration practice back to life after the shock of the pandemic.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Justina Leston</title>
      <link>https://superbloom.design/about/people/justina-leston/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/justina-leston/</guid>
      <description>&lt;p&gt;Justina is an Argentine photographer and graphic designer based in Berlin. She has more than ten years’ experience working in different fields of graphic design including branding, editorial, web design and animation. As a freelancer she loves having the freedom to choose the projects she wants to work on and she is very happy to have had the opportunity to work for different prestigious non-governmental organizations including: International Civil Society Center, tbd*, Urgent Action Funds, Digital Freedom Fund, Water Integrity Network, Climate of Change, WWF International.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>K J Hepworth</title>
      <link>https://superbloom.design/about/people/kj-hepworth/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/kj-hepworth/</guid>
      <description>&lt;p&gt;Dr KJ Hepworth is a design researcher with expertise in visualization and information design, and a passion for justice-oriented projects. They are disabled, neurodivergent, and queer, and these identities enrich their mentoring and professional practise.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Kami Joseph</title>
      <link>https://superbloom.design/about/people/kami/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/kami/</guid>
      <description>&lt;p&gt;Kami comes with a background in finance and business operations. After spending some years after college in corporate offices, she was sure that she wanted her work to matter beyond the numbers. In 2016, after navigating an investment banking path, and after a short stretch in the corporate retail space, she entered the nonprofit world and has worked for several organizations with various admirable missions in the Pittsburgh (PA) region. Her compassion for people and ambition to make a difference in the world are her key drivers. Kami holds a Bachelor of Science in Finance and a Master of Business Administration. She currently lives in Atlanta with her husband, Ryan. When she’s not at work, Kami enjoys finding new restaurants, laughing with her loved ones and doesn’t mind finding her way to the gym for a good workout.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Katie Werremeyer</title>
      <link>https://superbloom.design/about/people/katie-werremeyer/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/katie-werremeyer/</guid>
      <description>&lt;p&gt;Katie Werremeyer is a transformational leader with two decades of software company leadership dedicated to fundamentally shifting how technology is built. Her pioneering work establishes empathy and ethics as core drivers of decisions rather than afterthoughts, ensuring technology is both innovative and beneficial to society. &lt;br&gt;
As Co-founder of Empathy in Tech, she&amp;rsquo;s created a global movement through podcasts, workshops, and training tools that make empathy actionable. Previously as COO at Camera Bits and through her consultancy, Katie has demonstrated how human-centered leadership drives sustainable growth even when competing against tech giants. Drawing from her diverse professional experiences across technical and creative fields, she champions inclusive practices that bridge operational excellence with authentic human connection, advocating for responsible innovation that strengthens communities and respects human dignity.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Katie Wilson</title>
      <link>https://superbloom.design/about/people/katie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/katie/</guid>
      <description>&lt;p&gt;Katie is a researcher and writer who likes to zoom in and out from the human scale to the systems-view. She is a practitioner of human-centered design research, incorporating mixed methods from social science, UX design, and participatory action research. Before working in public interest tech, she wrote about and researched housing justice and gentrification policy in the Bay Area. She likes to work on problems concerning the equity and justice of the structures that shape our lives. Katie holds a bachelor&amp;rsquo;s degree in Comparative American Studies from Oberlin College. Outside of work, she volunteers for the Parole Preparation Project and loves to tackle any kind of elaborate cooking or crafting project.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Kelsey Smith</title>
      <link>https://superbloom.design/about/people/kelsey/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/kelsey/</guid>
      <description>&lt;p&gt;Kelsey’s design practice is informed by a background in art, business, and teaching, as well as her time living in Kenya, Korea, Spain, and now Germany. Since starting at Simply Secure in 2020, Kelsey has drawn on these experiences to inform her work &lt;a href=&#34;https://superbloom.design/learning/resources/popping-the-filter-bubble-design-practices-for-data-donation&#34;&gt;exploring institutional trust with data collection&lt;/a&gt;, simplifying digital security practices, and serving diverse communities through participatory user research. Kelsey&amp;rsquo;s toolkit as a UX designer encompasses information architecture, wireframing, workshop facilitation, need-finding research, usability testing, interactive prototyping, and user interface design. Her work has ranged from &lt;a href=&#34;https://superbloom.design/learning/blog/strength-in-numbers&#34;&gt;browser extensions protecting against phishing&lt;/a&gt; to tools that help human rights defenders safeguard their security. In her time with Simply Secure, she has worked with organizations such as Amnesty International and Mozilla. A native of Michigan, she has called Berlin home since 2018.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Kris Wade</title>
      <link>https://superbloom.design/about/people/kris/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/kris/</guid>
      <description>&lt;p&gt;Kris has been supporting Simply Secure’s daily operations for over three years, assisting in project management, policy development, event planning, fundraising support and more. Her background in project management began at Charles Schwab and was fine-tuned at various  startups. Kris’s passion is creating something from the ground up, starting with the initial research, sizing and planning, then completion. When Kris isn’t project managing, she can be found at the movies, a yoga class or at home painting.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Laura Gaetano</title>
      <link>https://superbloom.design/about/people/laura-gaetano/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/laura-gaetano/</guid>
      <description>&lt;p&gt;Laura is a multidisciplinary designer with a background in performance art, ceramics and music journalism. After a career in the music industry where she did everything from artist management to event planning and PR to art direction, she landed in tech almost by accident and became a Ruby developer, then ran the successful open source program “Rails Girls Summer of Code” before moving onto a career in UI/UX and marketing design.&lt;/p&gt;
&lt;p&gt;She’s most passionate to work with mission-oriented folks on things that matter, and has a thing for accessibility, design systems, DEI, open source software and documentation.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Photo credit: Zoe Noble&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Legal</title>
      <link>https://superbloom.design/legal/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/legal/</guid>
      <description>&lt;p&gt;Superbloom is a registered 501(c)3 nonprofit organization based in the United States of America. Our Employer Identification Number (EIN) is available upon request to &lt;a href=&#34;mailto:contact@superbloom.design&#34;&gt;contact@superbloom.design&lt;/a&gt;. Our official address is:&lt;/p&gt;
&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;Mailing: 276 Fifth Ave, Suite 704-33
New York, NY 10001&lt;/li&gt;
&lt;li&gt;Email: &lt;a href=&#34;mailto:contact@superbloom.design&#34;&gt;contact@superbloom.design&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Website: &lt;a href=&#34;https://superbloom.design&#34;&gt;https://superbloom.design&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Phone: +1 (914) 752-2330&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;p&gt;Superbloom adheres to the highest ethical standards in all of our operations and is dedicated to protecting the privacy of everyone who interacts with us. We don’t sell, barter, give away, rent, or permit anyone outside of Superbloom, our Board of Directors, and project-scoped contractors to use or access information about our partners, collaborators, research participants, or website visitors.&lt;/p&gt;
&lt;p&gt;We use third party services to publish work, keep in touch with people, and understand how we can do both of these things better. Here you can find out what these services are and how we handle all sorts of data, from user research to job applications.&lt;/p&gt;
&lt;p&gt;If there is additional information you would like to see in this document about our practices, or if you have other comments or questions, please reach out to &lt;a href=&#34;mailto:data@superbloom.design&#34;&gt;data@superbloom.design&lt;/a&gt;.&lt;/p&gt;

&lt;span&gt;This document was last updated on August 7, 2026.&lt;/span&gt;
&lt;br&gt;
&lt;br&gt;
&lt;h2 id=&#34;our-site--services&#34;&gt;Our site &amp;amp; services&lt;/h2&gt;
&lt;p&gt;We use the following services to run our websites and understand how people are using them.&lt;/p&gt;
&lt;h3 id=&#34;website-analytics&#34;&gt;Website Analytics&lt;/h3&gt;
&lt;p&gt;Our website uses &lt;a href=&#34;https://plausible.io/&#34;&gt;Plausible&lt;/a&gt; for simple and privacy-friendly web analytics. We collects information about how people are using our sites to allow us to improve their experience. Our traffic data is not used for any other purposes. Plausible does not use cookies and is fully compliant with GDPR, CCPA, PECR and other privacy regulations out of the box.&lt;/p&gt;
&lt;h3 id=&#34;newsletter&#34;&gt;Newsletter&lt;/h3&gt;
&lt;p&gt;When we send out newsletters, we use &lt;a href=&#34;https://www.phplist.com/&#34;&gt;phpList&lt;/a&gt; or &lt;a href=&#34;https://tinyletter.com/&#34;&gt;TinyLetter/Mailchimp&lt;/a&gt;, which stores subscribers email addresses. We do not use the platform features for tracking links or opens. We only send our newsletter to people who expressly sign up for it.&lt;/p&gt;
&lt;h3 id=&#34;github&#34;&gt;GitHub&lt;/h3&gt;
&lt;p&gt;We use &lt;a href=&#34;https://pages.github.com/&#34;&gt;GitHub Pages&lt;/a&gt; to host our website. Find out more about how Github uses data in their&lt;a href=&#34;https://help.github.com/articles/github-privacy-statement/&#34;&gt; privacy statement&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;vimeo&#34;&gt;Vimeo&lt;/h3&gt;
&lt;p&gt;We host videos using&lt;a href=&#34;https://vimeo.com&#34;&gt; Vimeo&lt;/a&gt; for its robust and scalable infrastructure. Find out more about how they use data in their&lt;a href=&#34;https://vimeo.com/privacy&#34;&gt; privacy statement&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;google-drive--email&#34;&gt;Google Drive &amp;amp; Email&lt;/h3&gt;
&lt;p&gt;We currently use G Suite for Nonprofits for our email, calendaring, and document storage. Individual members of the team use PGP and are happy to correspond via encrypted email, or honor requests to have files shared with us be not stored in Google Drive. We respect diverse threat models and work to accommodate our partners’ needs and concerns.&lt;/p&gt;
&lt;h3 id=&#34;slack&#34;&gt;Slack&lt;/h3&gt;
&lt;p&gt;We host a &lt;a href=&#34;https://slack.com/&#34;&gt;Slack&lt;/a&gt; organization for internal communication and community organizing. Slack stores your account information and usage data, and our administrators have access to all public channels. Please refer to Slack’s&lt;a href=&#34;https://slack.com/privacy-policy&#34;&gt; privacy policy&lt;/a&gt; before you sign on.&lt;/p&gt;
&lt;h3 id=&#34;underexposed-events&#34;&gt;Underexposed events&lt;/h3&gt;
&lt;p&gt;We use &lt;a href=&#34;https://pretix.eu/about/en/&#34;&gt;Pretix&lt;/a&gt; and &lt;a href=&#34;https://www.meetup.com/&#34;&gt;Meetup&lt;/a&gt; to handle signups and ticketing for our &lt;a href=&#34;https://superbloom.design/underexposed/&#34;&gt;Underexposed&lt;/a&gt; events. They allow us to promote each event to other people interested in similar gatherings.&lt;/p&gt;
&lt;p&gt;When someone signs up to an event through Pretix, we’ll only use that information to get in touch about that specific event. After the event, we delete any information about attendees from Pretix.&lt;/p&gt;
&lt;p&gt;To exercise your data rights on Pretix, go to their&lt;a href=&#34;https://pretix.eu/about/en/privacy&#34;&gt; privacy policy&lt;/a&gt; for more information; also see Meetup’s &lt;a href=&#34;https://help.meetup.com/hc/en-us/articles/360044422391&#34;&gt;privacy policy&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;submissions&#34;&gt;Submissions&lt;/h4&gt;
&lt;p&gt;Our submission platform is run on &lt;a href=&#34;https://airtable.com&#34;&gt;AirTable&lt;/a&gt;. When you submit a session to Underexposed, or apply to the Underexposed Design Residency program, your data will be stored on AirTable. AirTable does not collect or process the information you submit. More in their &lt;a href=&#34;https://airtable.com/privacy&#34;&gt;privacy policy&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;at-the-event&#34;&gt;At the event&lt;/h4&gt;
&lt;p&gt;We ask attendees for consent to being filmed or photographed by members of the Superbloom team on Pretix. If you want to change your decision or you’ve been filmed or photographed against your consent at a Superbloom event, please email &lt;a href=&#34;mailto:data@superbloom.design&#34;&gt;data@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If a speaker consents, we film their talk so we can publish it after the event. We transcribe films to ensure that what the speaker says is accessible to everyone. This transcript will be published verbatim, unless a speaker wants to review and edit it. We won’t publish footage of Q&amp;amp;As if we haven’t received consent from all participants.&lt;/p&gt;
&lt;h2 id=&#34;our-social-media-accounts&#34;&gt;Our social media accounts&lt;/h2&gt;
&lt;p&gt;We use social media accounts to share our work. We occasionally use the analytics tools provided by these platforms to understand how we can use these services better. Our social media accounts are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/@sprblm_&#34;&gt;Superbloom on Twitter&lt;/a&gt; (&lt;a href=&#34;https://twitter.com/en/privacy#update&#34;&gt;Privacy policy&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.linkedin.com/company/superbloomdesign/&#34;&gt;Superbloom on LinkedIn&lt;/a&gt; (&lt;a href=&#34;https://www.linkedin.com/legal/privacy-policy&#34;&gt;Privacy policy&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you’d like content about you removed from any of our social media profiles, please contact &lt;a href=&#34;mailto:data@superbloom.design&#34;&gt;data@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;research-participants&#34;&gt;Research participants&lt;/h2&gt;
&lt;p&gt;Research is an important part of our work: it helps us understand people’s needs and build better products and services.&lt;/p&gt;
&lt;h3 id=&#34;asking-for-consent&#34;&gt;Asking for consent&lt;/h3&gt;
&lt;p&gt;All research participants are given a consent form that outlines what the research involves, what information will be recorded and how it will be used. If the participant is happy to proceed we ask them to sign the form to confirm this. We scan signed consent forms and shred paper copies, then store consent forms on Google Drive and keep these for 3 years.&lt;/p&gt;
&lt;p&gt;At the moment, we do not conduct any research with people under the age of 18.&lt;/p&gt;
&lt;p&gt;You can view an example of&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/research_tools/participant_bill_of_rights.pdf&#34;&gt; our participant Bill of Rights on GitHub&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;using-information-from-research&#34;&gt;Using information from research&lt;/h4&gt;
&lt;p&gt;Research material is separated from any identifiable information, such as consent forms, while we are working with it.&lt;/p&gt;
&lt;p&gt;Any notes we gather during research sessions are stored securely. Any digital files (like audio, photos and videos) are stored on Google Drive and are only accessed by Superbloom team members involved in the research. At the end of the project, all notes and digital files are destroyed or deleted.&lt;/p&gt;
&lt;p&gt;Sometimes we may publish quotes from research sessions. We only do this if we have specific consent from the participant and any personally identifiable information has been removed. We will only publish audio, photos and video from a research session if a participant has given consent and has signed a model release form.&lt;/p&gt;
&lt;h3 id=&#34;survey&#34;&gt;Survey&lt;/h3&gt;
&lt;p&gt;We use LimeSurvey for gathering and processing information from survey participants. See their &lt;a href=&#34;https://www.limesurvey.org/privacy-policy&#34;&gt;privacy policy&lt;/a&gt; for more information.&lt;/p&gt;
&lt;h3 id=&#34;withdrawing-your-consent&#34;&gt;Withdrawing your consent&lt;/h3&gt;
&lt;p&gt;Participants are able to withdraw their information from a project at any time. To do this, contact &lt;a href=&#34;mailto:data@superbloom.design&#34;&gt;data@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;working-at-superbloom&#34;&gt;Working at Superbloom&lt;/h2&gt;
&lt;p&gt;Only team members involved in the recruitment process have access to applications, CVs and emails we receive. We don’t collect any &lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/lawful-basis-for-processing/special-category-data/&#34;&gt;special category data&lt;/a&gt; or ask for any background checks as part of the application process.&lt;/p&gt;
&lt;p&gt;When people join Superbloom, we request information about them needed for tax purposes. We hold information about their role and their professional development at Superbloom. Access to this information is controlled.&lt;/p&gt;
&lt;h3 id=&#34;things-we-dont-do&#34;&gt;Things we don&amp;rsquo;t do&lt;/h3&gt;
&lt;p&gt;Superbloom doesn&amp;rsquo;t participate in the following data processing activities:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Buying or selling marketing lists&lt;/li&gt;
&lt;li&gt;Entering into data sharing agreements with other organisations&lt;/li&gt;
&lt;li&gt;Telephone marketing&lt;/li&gt;
&lt;li&gt;Postal marketing&lt;/li&gt;
&lt;li&gt;CCTV surveillance&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We don&amp;rsquo;t use &amp;ldquo;soft opt-in&amp;rdquo;, meaning you won&amp;rsquo;t receive any marketing communication from us unless you&amp;rsquo;ve specifically agreed to it.&lt;/p&gt;
&lt;h3 id=&#34;keeping-data-secure&#34;&gt;Keeping data secure&lt;/h3&gt;
&lt;p&gt;We carefully choose our services and tools at Superbloom. It’s important that they follow good security practices, like HTTPS, two-factor authentication and the ability to set a strong password. We&amp;rsquo;ve reviewed the privacy policies and security practices of everything we use.&lt;/p&gt;
&lt;p&gt;When a new team member joins Superbloom, we explain best practices for keeping their devices secure, maintaining the security of their online accounts, and working outside our offices.&lt;/p&gt;
&lt;h3 id=&#34;data-breaches&#34;&gt;Data breaches&lt;/h3&gt;
&lt;p&gt;In the event of a data breach, we are required to notify the Information Commissioner’s Office. We will do so following&lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/personal-data-breaches/&#34;&gt; their guidance&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;data-transfer-outside-the-eea&#34;&gt;Data transfer outside the EEA&lt;/h3&gt;
&lt;p&gt;We have reviewed the privacy policies of third party services we use. They provide adequate protections when information is shared outside of the European Economic Area.&lt;/p&gt;
&lt;h3 id=&#34;exemptions&#34;&gt;Exemptions&lt;/h3&gt;
&lt;p&gt;There are exemptions to data protection regulations that may require us to share data about you, including requests by law enforcement. This includes requirements and orders in the United States, where we are based. A full list of EU exemptions are listed&lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/exemptions/&#34;&gt; on the ICO website&lt;/a&gt;. This also applies to data held about you by third party services we use.&lt;/p&gt;
&lt;h3 id=&#34;reviewing-how-we-use-data&#34;&gt;Reviewing how we use data&lt;/h3&gt;
&lt;p&gt;Every quarter, we review our documentation of the data we handle and third party services we use. This helps us continuously improve our processes and hold ourselves to account. We will update this document as necessary.&lt;/p&gt;
&lt;h3 id=&#34;your-rights-and-getting-in-touch&#34;&gt;Your rights and getting in touch&lt;/h3&gt;
&lt;p&gt;The General Data Protection Regulation gives EU citizens the following rights:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/individual-rights/right-to-be-informed/&#34;&gt;Right to be informed&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/individual-rights/right-of-access/&#34;&gt;Right of access&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/individual-rights/right-to-rectification/&#34;&gt;Right to rectification&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/individual-rights/right-to-erasure/&#34;&gt;Right to erasure&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/individual-rights/right-to-restrict-processing/&#34;&gt;Right to restrict processing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/individual-rights/right-to-data-portability/&#34;&gt;Right to data portability&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/individual-rights/right-to-object/&#34;&gt;Right to object&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/individual-rights/rights-related-to-automated-decision-making-including-profiling/&#34;&gt;Rights related to automated decision-making, including profiling&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To exercise any of these rights, please contact us at &lt;a href=&#34;mailto:data@superbloom.design&#34;&gt;data@superbloom.design&lt;/a&gt;. You can find information specific to the services we use or our activities in the relevant sections of this document. If you are located in the EU and aren&amp;rsquo;t satisfied by our response, you can contact the EU &lt;a href=&#34;https://ico.org.uk/concerns/&#34;&gt;Information Commissioner&amp;rsquo;s Office&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;acknowledgements&#34;&gt;Acknowledgements&lt;/h2&gt;
&lt;p&gt;In drafting this policy we used a number of different resources and inspirations. We want to offer particular thanks to Projects By If for their &lt;a href=&#34;https://github.com/projectsbyif/how-if-uses-data&#34;&gt;clear example&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>libraries</title>
      <link>https://superbloom.design/tags/libraries/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/libraries/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Links</title>
      <link>https://superbloom.design/links/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/links/</guid>
      <description>&lt;div class=&#34;flower--list&#34; tabindex=&#34;0&#34; role=&#34;list&#34;&gt;
  &lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design&#34;&gt;superbloom.design&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.redbubble.com/people/Superbloom-Dsgn/shop&#34;&gt;Superbloom Shop&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://github.com/sprblm&#34;&gt;Github&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://mastodon.design/@sprblm&#34;&gt;Mastodon&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.linkedin.com/company/superbloomdesign/&#34;&gt;LinkedIn&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://twitter.com/sprblm_&#34;&gt;Twitter&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>Lisa Baird</title>
      <link>https://superbloom.design/about/people/lisa-baird/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/lisa-baird/</guid>
      <description>&lt;p&gt;Lisa Baird is an independent business and organizational designer, user experience designer, and writer with 15 years of education-to-employment expertise forged in financial administration at The University of Texas System; strategy at the University of California Office of the President; grantmaking at the Bill &amp;amp; Melinda Gates Foundation; human-centered design at IDEO; and direct client work for Arizona State University, Better Future Forward, Calbright College, Edmit, Entangled Solutions, the Foundation for California Community Colleges, Guild Education, IDEO, the U.S. Department of Education, and others.&lt;/p&gt;
&lt;p&gt;Lisa earned her Master of Design from California College of the Arts, her Master of Business Administration from UC Berkeley, and her two bachelors degrees in finance and journalism from The University of Texas at Austin.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Lisa Steingräber</title>
      <link>https://superbloom.design/about/people/lisa/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/lisa/</guid>
      <description>&lt;p&gt;Lisa creates digital and analogue products and services with the greatest passion in the field of the future of life-long learning. After working at a start-up, she moved to a consultancy where she worked on a variety of digitisation projects in the interface between tech, design and education. The user is always at the heart of what she designs.&lt;/p&gt;
&lt;p&gt;Lisa also works as an innovation consultant and advises organisations on how to improve their products and services as well as train agile methodologies. Using her expertise, she guides teams through various phases of a project: developing new ideas, testing them on the market and drawing up implementation strategies. She is most interested in supporting teams to reflect on group dynamics and creating feedback culture.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Lorraine Chuen</title>
      <link>https://superbloom.design/about/people/lorraine/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/lorraine/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Loyalty Study</title>
      <link>https://superbloom.design/work/loyalty-study/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/work/loyalty-study/</guid>
      <description>&lt;h2 id=&#34;surveillance-risks-and-personal-benefits-by-shopping-apps&#34;&gt;Surveillance Risks and Personal Benefits by Shopping Apps&lt;/h2&gt;
&lt;p&gt;In March 2017, we went to San Francisco to speak with people who used store branded loyalty apps or coupon apps.&lt;/p&gt;
&lt;p&gt;Our hypothesis was that people would not understand what data apps gather about them, and once they did might feel that
they were not getting a good deal by exchanging their data for coupons.&lt;/p&gt;
&lt;p&gt;We were wrong.&lt;/p&gt;
&lt;p&gt;Instead of outrage about the data gathered, our participants had positive feelings about how these apps were beneficial
not only to themselves but to their communities. None of the participants were surprised by their settings and the kinds
of data they were sharing.&lt;/p&gt;
&lt;p&gt;Everyone was familiar with their phones&amp;rsquo; privacy settings, and most people had one specific thing they opted out of,
while sharing contacts and location with many apps.&lt;/p&gt;
&lt;h2 id=&#34;outcomes&#34;&gt;Outcomes&lt;/h2&gt;
&lt;p&gt;Read a &lt;a href=&#34;https://superbloom.design/learning/blog/loyalty&#34;&gt;blog post&lt;/a&gt; about the loyalty app study.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Maina Korir</title>
      <link>https://superbloom.design/about/people/maina/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/maina/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Matt Stempeck</title>
      <link>https://superbloom.design/about/people/matt/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/matt/</guid>
      <description>&lt;p&gt;Matt Stempeck (he/him) is a writer, researcher, technologist, and activist. He&amp;rsquo;s been researching and building civic technology since 2005, and looks for creative ways to make the world better through electoral and social campaigns, government, research, and journalism.&lt;/p&gt;
&lt;p&gt;Matt curates the &lt;a href=&#34;https://civictech.guide/&#34;&gt;Civic Tech Field Guide&lt;/a&gt;, the most comprehensive collection of democracy tech projects in the world. And he&amp;rsquo;s Technologist in Residence at Cornell Tech, where he organizes the &lt;a href=&#34;https://www.pi.tech.cornell.edu/&#34;&gt;Siegel PiTech Impact Fellowship&lt;/a&gt;, embedding highly technical PhD students with public interest organizations across sectors.&lt;/p&gt;
&lt;p&gt;In 2016, Matt led the Digital Mobilization team at Hillary for America, which included the campaign’s voter registration, peer organizing, and SMS technologies and programs. Matt also served as Director of Civic Technology at Microsoft in New York City. He&amp;rsquo;s now based in Lisbon, where he work on engagement projects with a creative collective appropriately known as the &lt;a href=&#34;https://biffud.com/&#34;&gt;Bad Idea Factory&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Matt became/earned a Master of Science at the MIT Media Lab’s Center for Civic Media. While at the Media Lab, he quantified global media attention to stories like Trayvon Martin’s, designed a peer-to-peer humanitarian aid marketplace, and built an award-winning email product to fight misinformation online. Matt also holds a Bachelor of Arts with high honors from the University of Maryland College Park, where he wrote his undergraduate thesis on the disruption participatory media brought to political journalism.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Meag Doherty</title>
      <link>https://superbloom.design/about/people/meag-doherty/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/meag-doherty/</guid>
      <description>&lt;p&gt;Meag Doherty is an American design leader and public interest technologist with expertise in science and technology policy, program strategy, and public health. Since 2019, she has worked on user experience strategy at WONDROS for the All of Us Research Program at the National Institutes of Health and, most recently, as the All of Us Deputy Chief User Experience Officer. Meag is also a Fellow at the Software Sustainability Institute and has spent time mentoring open-source community leaders on how to work more openly. &lt;/p&gt;
&lt;p&gt;Previously, Meag was a user experience lead at Agency CHIEF, helping clients like the Centers for Medicare and Medicaid, National Park Foundation, and Rock The Vote to conduct user research and develop user experience strategies. During that time, Meag also frequently wrote and spoke about global open government and data initiatives and their impact on U.S. policies. Before that, Meag led policy, strategy, and research for governments and nonprofits like the Chicago City Council, the U.S. House of Representatives, and the OpenGov Foundation. &lt;/p&gt;
&lt;p&gt;Meag started her career as a research assistant at the Center for Connected Health at MassGeneral Brigham, studying the impact of SMS-based interventions on exercise among patients with Type 2 Diabetes. There, she met technical and clinical mentors who would shape her trajectory toward the intersection of technology, policy, and health.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Melina Garcia</title>
      <link>https://superbloom.design/about/people/melina-garcia/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/melina-garcia/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Melissa Huerta</title>
      <link>https://superbloom.design/about/people/melissa/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/melissa/</guid>
      <description>&lt;p&gt;Melissa works to advance the promise of the internet through strategic philanthropy. Bringing real-world solutions, Melissa weaves operational efficiency and program execution to drive the organization’s mission. Her collaborative, equity-centered approach centers community needs and partnership. With over 17 years of experience in nonprofit technology advocacy, she understands how the evolving social, political, and technological landscape requires organizations to build resilient processes that lead to desired impact.&lt;/p&gt;
&lt;p&gt;Melissa has designed global grantmaking programs and funded over $25 million in initiatives that helped organizations drive impact and build effective strategies. She has a wealth of global experience, having worked across the US, Europe, Latin America, and Asia, and is fluent in Japanese and Spanish. Melissa has her Master&amp;rsquo;s in International Education Policy from Harvard University.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Memo Esparza</title>
      <link>https://superbloom.design/about/people/memo-esparza/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/memo-esparza/</guid>
      <description>&lt;p&gt;Memo is a senior product designer and creative director specializing in UX/UI, branding, and strategic design leadership. He combines deep product expertise with comprehensive brand experience, focusing on design strategy and collaborative processes to drive impactful creative projects forward.&lt;/p&gt;
&lt;p&gt;After co-founding a digital agency where he led brand and visual identity projects across fintech, healthtech, and tech sectors, Memo joined Open Collective as a senior designer and advanced to Head of Design. In this role, he led all design initiatives to scale a financial transparency platform serving 150,000+ users managing over $35M annually.&lt;/p&gt;
&lt;p&gt;He is now serving clients as an independent, spanning complex enterprise interfaces for Google, partnering with SF-based agencies, branding, and cross-functional product leadership in fast-paced startup environments. Memo specializes in translating strategic concepts into intuitive user experiences while maintaining design consistency at scale.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Meredith Whittaker</title>
      <link>https://superbloom.design/about/people/meredith/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/meredith/</guid>
      <description></description>
    </item>
    
    <item>
      <title>method</title>
      <link>https://superbloom.design/formats/method/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/formats/method/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Michael Anton Dila</title>
      <link>https://superbloom.design/about/people/michael-dila/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/michael-dila/</guid>
      <description>&lt;p&gt;Michael has spent his career working at the crux of change: building and equipping teams to do their most ambitious work; working to democratize the knowledge and practice of design; leading innovation work in companies, organizations and institutions; nurturing community and instigating challenging conversations.&lt;/p&gt;
&lt;p&gt;He is currently leading a project called Oslo for AI, which is an effort of technology diplomacy with the intention of creating new possibilities for participation in our most important conversations about AI.&lt;/p&gt;
&lt;p&gt;Michael has a passion for starting things. Whether it&amp;rsquo;s companies or communities, he has spent much of the last 25 years breaking new ground. As a design and innovation leader he was devoted to making both more rigorous and more accessible. He is a founding member of Overlap, a peer network of innovators who share knowledge and practice to advance the state of the art of design. Since spending five years helping to build an elite innovation unit in the U.S. Department of Defense, he has been focused on working with leaders and teams in domains characterized by both high technical and ethical complexity, such as AI, defense innovation and inclusive entrepreneurship.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>mobile app</title>
      <link>https://superbloom.design/tags/mobile-app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/mobile-app/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Molly Clare Wilson</title>
      <link>https://superbloom.design/about/people/molly/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/molly/</guid>
      <description>&lt;p&gt;Molly’s favorite part of being a designer is helping others learn. She makes the language and practice of design into something accessible and meaningful to a wide variety of collaborators. Her background is in human-centered design, strongly influenced by her time creating and leading programs at the Stanford d.school in Palo Alto, CA and later at the Hasso-Plattner-Institut School of Design Thinking in Potsdam, Germany.&lt;/p&gt;
&lt;p&gt;As an interaction designer in industry, she’s worked on complex products in finance, health, and education. Since joining Superbloom in 2018, she has focused on security usability; designing to counteract harm and abuse; framing responsible, respectful design processes and practices; and using co-design to rebalance power dynamics.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Nancy Reyes</title>
      <link>https://superbloom.design/about/people/nancy-reyes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/nancy-reyes/</guid>
      <description></description>
    </item>
    
    <item>
      <title>NDC</title>
      <link>https://superbloom.design/tags/ndc/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/ndc/</guid>
      <description></description>
    </item>
    
    <item>
      <title>networking</title>
      <link>https://superbloom.design/tags/networking/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/networking/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Ngọc Triệu</title>
      <link>https://superbloom.design/about/people/ngoc/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/ngoc/</guid>
      <description>&lt;p&gt;Ngọc practices design as an intervention to address and reform asymmetrical power relations. As a design researcher at Simply Secure, she imagines the future(s) of the world(s) through lenses such as decoloniality and decentralization. Ngọc is passionate about user advocacy, co-creation, and equal access to knowledges(s). Whether she is distilling data into insights that inform design decisions or conceptualizing information architecture, Ngọc works closely with designers, developers, and funders to ensure accessibility and security for vulnerable communities.&lt;/p&gt;
&lt;p&gt;Before joining Simply Secure, Ngọc has lived in Vietnam, Japan, the UK, and Germany where she has worked in international development and humanitarian aid, pedagogical design, documentary photography, and film-making. When Ngọc isn&amp;rsquo;t busy identifying design research gaps and mapping solutions, she enjoys doing Kendo (Japanese sword-fighting) and roaming the forest.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Nicola Pratt</title>
      <link>https://superbloom.design/about/people/nicola/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/nicola/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Nimisha Vijay</title>
      <link>https://superbloom.design/about/people/nimisha/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/nimisha/</guid>
      <description>&lt;p&gt;Nimisha is a UX designer based in Berkeley, USA. With a background in engineering, she ventured into design as a contributor to the open source collaboration platform Nextcloud. She soon transitioned into a full time UX designer and spends her time there working with the open source community to build a better internet. She is a core member of the Open Source Design community, with experience organising events, speaking about ways to contribute, and studying the relationship between open source and design. Nimisha understands designing in low-resource contexts, scrappy user research, and leveraging community as a strength. She has also explored research in privacy and cybersecurity, with a paper published at a top security conference. Nimisha believes in privacy, agency, and control over your life on the internet and is fascinated by how a community can help achieve that.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Nina Alter</title>
      <link>https://superbloom.design/about/people/nina/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/nina/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Nóirín &#34;Trouble&#34; Plunkett</title>
      <link>https://superbloom.design/about/people/trouble/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/trouble/</guid>
      <description></description>
    </item>
    
    <item>
      <title>open source</title>
      <link>https://superbloom.design/tags/open-source/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/open-source/</guid>
      <description></description>
    </item>
    
    <item>
      <title>open source design</title>
      <link>https://superbloom.design/tags/open-source-design/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/open-source-design/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Open Source Design</title>
      <link>https://superbloom.design/topics/open-source-design/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/open-source-design/</guid>
      <description></description>
    </item>
    
    <item>
      <title>open source software</title>
      <link>https://superbloom.design/tags/open-source-software/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/open-source-software/</guid>
      <description></description>
    </item>
    
    <item>
      <title>organizing</title>
      <link>https://superbloom.design/tags/organizing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/organizing/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Participant Bill of Rights</title>
      <link>https://superbloom.design/bill-of-rights/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/bill-of-rights/</guid>
      <description>&lt;h3 id=&#34;participant-bill-of-rights&#34;&gt;Participant Bill of Rights&lt;/h3&gt;
&lt;p&gt;We respect you and appreciate your time. Everyone participating in an interview with Simply Secure has the following rights:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;I can ask questions about the interview, the organization, or the interviewer at any time.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;I do not have to answer any question that I do not want to.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;I can refuse to be video or audio recorded and I will still be compensated.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;I can leave at any time and I will still be compensated.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;I can provide confidential feedback on my interview experience to the interviewer’s manager.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;I must approve the use of any photos, audio, videos or anonymized quotes that are used publicly, whether on a website, on a blog, or in the press.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Once a photo, video or quote has been published, I have the right to request it be taken down at any point in the future.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;br&gt;
&lt;p&gt;You can reach Simply Secure any time by emailing
&lt;a href=&#34;mailto:contact@superbloom.design&#34;&gt;contact@superbloom.design&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>people</title>
      <link>https://superbloom.design/tags/people/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/people/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Philliph Drummond</title>
      <link>https://superbloom.design/about/people/philliph/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/philliph/</guid>
      <description>&lt;p&gt;Philliph is a creative technologist residing in the Bay Area, with their partner Annelisa, child Xinasa, and two cats, Mam and Pate. Recently, Philliph has been working with mostly not-for-profit startups across a range of challenges from IT streamlining, UX/Product coaching, and business process improvement.&lt;/p&gt;
&lt;p&gt;In the past, they designed and managed internal systems for mid-sized NPOs in the social justice sector, approaching organizational infrastructure as permaculture, delivering IT trainings and technical support to organizers in the field.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>policy</title>
      <link>https://superbloom.design/tags/policy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/policy/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Pooja Channaveerappa</title>
      <link>https://superbloom.design/about/people/pooja/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/pooja/</guid>
      <description>&lt;p&gt;Pooja is an aerospace and hardware design engineer dedicated to pushing the boundaries of sustainable innovation in both technology and entrepreneurship. She is one of the founding team members of Pocket Reform, a novel open hardware, modular, and customizable pocket computer. This project achieved a successful crowdfunding campaign in early 2023. She applied her expertise in user-centric design, rapid prototyping, and circular design in the early stages of developing this sustainable electronic device.&lt;/p&gt;
&lt;p&gt;In addition to her contributions to Pocket Reform, Pooja has been involved in the development of other sustainable consumer products, all designed to empower users by offering repairability and enhanced autonomy. She herself was a recipient of the Prototype Fund in 2017 while developing an open-source platform for sex education. Beyond product innovation, her expertise extends to hydraulic technologies for aerospace applications. Pooja is also an experienced facilitator and coach for product innovation and team development in both established corporations and young startups. She is committed to supporting user sovereignty in design and sustainable innovation with all her capacities.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>privacy</title>
      <link>https://superbloom.design/tags/privacy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/privacy/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Raashi Saxena</title>
      <link>https://superbloom.design/about/people/raashi-saxena/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/raashi-saxena/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Rae McKelvey</title>
      <link>https://superbloom.design/about/people/rae/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/rae/</guid>
      <description>&lt;p&gt;Rae is an expert in open source software development, security, and Internet architecture. She researches technical architecture design and its impact on usability, safety, and resilience. Her contributions are depended upon by at-risk users including human &amp;amp; environmental rights defenders, journalists, and civil society activists. Her background is in political sociology and data science, and she loves making weird musical art that touches funny bones. She is a maintainer of &lt;a href=&#34;http://decentpatterns.xyz/&#34;&gt;Decentralization Off the Shelf&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>remote</title>
      <link>https://superbloom.design/tags/remote/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/remote/</guid>
      <description></description>
    </item>
    
    <item>
      <title>report</title>
      <link>https://superbloom.design/formats/report/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/formats/report/</guid>
      <description></description>
    </item>
    
    <item>
      <title>reports</title>
      <link>https://superbloom.design/tags/reports/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/reports/</guid>
      <description></description>
    </item>
    
    <item>
      <title>research</title>
      <link>https://superbloom.design/tags/research/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/research/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Research &amp; Design</title>
      <link>https://superbloom.design/work/user-research/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/work/user-research/</guid>
      <description>&lt;h2 id=&#34;user-research&#34;&gt;User Research&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;What do people need? What do they want? What can they use?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Any project – whether it&amp;rsquo;s still a broad concept or whether it&amp;rsquo;s already a robust product with a large user base – needs
to know the answer to these questions in order to have an impact.&lt;/p&gt;
&lt;p&gt;We can help you uncover priorities, make sense of contradictory feedback, and articulate a clear design direction for
your project. At the end of each phase of our work together, we deliver a design synthesis report, with quotations,
examples, and concrete recommendations.&lt;/p&gt;
&lt;p&gt;Our deep expertise in multiple methods for fieldwork helps us craft a custom research program to address your team&amp;rsquo;s
priorities. We use a variety of methods, both in-person and remote, including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Cognitive walkthroughs/think aloud protocols&lt;/li&gt;
&lt;li&gt;Semi-structured individual or group interviews&lt;/li&gt;
&lt;li&gt;Surveys, questionnaires, card-sorting, and prioritization exercises&lt;/li&gt;
&lt;li&gt;Feedback on low-fidelity prototypes, including paper&lt;/li&gt;
&lt;li&gt;Diaries and prompted in situ studies&lt;/li&gt;
&lt;li&gt;Workshops, games, and activities for capturing structured feedback&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We keep the rights of all research participants front and center, using &lt;a href=&#34;https://superbloom.design/learning/blog/sensitive-interviews&#34;&gt;threat modeling techniques&lt;/a&gt; to ensure everyone is treated respectfully and ethically throughout the
process. All our research uses a &lt;a href=&#34;https://superbloom.design/learning/blog/participant-rights&#34;&gt;Participant Bill of Rights&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;For examples of our past work in this area, see our &lt;a href=&#34;&#34;&gt;Mobile Messaging in NYC study&lt;/a&gt; and &lt;a href=&#34;http://ontrustandtransparency.report&#34;&gt;On Trust and Transparency&lt;/a&gt;, our research collaboration with &lt;a href=&#34;https://luminategroup.com&#34;&gt;Luminate&lt;/a&gt; around the nonprofit funding experience.&lt;/p&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/assets/img/gridsync.jpg&#34; alt=&#34;Paper prototype of GridSync.&#34; width=&#34;750&#34; height=&#34;563&#34;&gt;

&lt;em&gt;Participant thinking aloud while going through screenshots of the onboarding process for encrypted storage solution
GridSync.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;interaction-design&#34;&gt;Interaction Design&lt;/h2&gt;
&lt;p&gt;Once we&amp;rsquo;ve identified and prioritized what your technology needs to do, we work together on the design. Our process is
highly collaborative and iterative; we begin with rough sketches and move on to higher-fidelity digital tools, working
closely with you and conducting quick usability tests as we go. Getting feedback from your community is a priority for
us, and we gladly share our design work as we go.&lt;/p&gt;
&lt;p&gt;Though we dream big, we have a pragmatic approach to design. Many groups we work with work under resource constraints,
and often the best design is the one that can actually be implemented. We make design choices that make sense not just
for your end users, but also for your team and your development capacity.&lt;/p&gt;
&lt;p&gt;We can provide the deliverables that are most helpful to you. That might include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Information architecture diagrams&lt;/li&gt;
&lt;li&gt;Wireframes&lt;/li&gt;
&lt;li&gt;Annotated screenshots&lt;/li&gt;
&lt;li&gt;Click-through prototypes&lt;/li&gt;
&lt;li&gt;Style guides&lt;/li&gt;
&lt;li&gt;Visual assets (logos, typography, color palettes, branding)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For examples of our recent work in this area, see our work on &lt;a href=&#34;https://superbloom.design/learning/blog/noscript-case-study&#34;&gt;NoScript&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We are an educational nonprofit, and it&amp;rsquo;s important to our work that we share what we learn openly with the community.
Even when the content of the project needs to remain private, we like to create open process resources, like the
interview guide in our &lt;a href=&#34;https://github.com/simplysecure/resources/tree/master/Research&#34;&gt;resource library&lt;/a&gt;. We respect
that all teams and projects have different needs around confidentiality, and we will work with you to figure out what
parts of our work together make the most sense to make public.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Reshama Shaikh</title>
      <link>https://superbloom.design/about/people/reshama-shaikh/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/reshama-shaikh/</guid>
      <description>&lt;p&gt;Reshama Shaikh is a statistician, data scientist and open source advocate. She has more than 14 years experience as a biostatistician and over 10 years experience as a community manager. She holds a Masters in Statistics from Rutgers University and an MBA with a focus on business analytics, strategy and marketing from New York University Stern School of Business.&lt;/p&gt;
&lt;p&gt;She began her statistical career at Educational Testing Service. She then worked for over 10 years as a biostatistician in the pharmaceutical industry at various companies including PPD, Merck, Thomas Jefferson University and Pfizer, covering Phase I through Phase 4 clinical trials. She also taught math, statistics and Rstats, and has given more than a dozen workshops on Using Git for Open Source for the community.&lt;/p&gt;
&lt;p&gt;She founded Data Umbrella in 2019, a community to expand the participation of open source users and contributors in the data science space. Prior to that, she served in a key leadership role with Women in Machine Learning and Data Science for 5 years, expanding the community globally from 3 chapters to 100 and was the lead organizer for the New York City chapter of PyLadies, which is the third largest chapter worldwide.&lt;/p&gt;
&lt;p&gt;She is an &lt;a href=&#34;https://github.com/reshamas&#34;&gt;open source contributor&lt;/a&gt; to a number of projects and on the teams for scikit-learn (the most popular python machine learning library) and PyMC (a probabilistic python programming language). &lt;/p&gt;
&lt;p&gt;Reshama has written &lt;a href=&#34;https://reshamas.github.io/&#34;&gt;numerous community blogs&lt;/a&gt;, given &lt;a href=&#34;https://www.youtube.com/watch?v=kmS2MRLicKc&amp;amp;list=PLBKcU7Ik-ir84cthbsQ_zU72sG-zUnEQn&#34;&gt;presentations and tutorials&lt;/a&gt; on data science, community and open source and mentored others in the community. &lt;/p&gt;
&lt;p&gt;Her community manager certifications include: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;CSCCE Scientific Community Engagement Fundamentals (CEF)&lt;/li&gt;
&lt;li&gt;GitHub DPG Open Source &lt;a href=&#34;https://github.blog/open-source/social-impact/just-launched-second-cohort-of-the-dpg-open-source-community-manager-program/&#34;&gt;Community Manager Program&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;She has a wide range of skills and expertise including: statistics, data science, coding in Python and R, teaching, open source, strategy and community. Reshama is an experienced community manager, with expertise in open source, diverse and inclusive practices and working with global teams.&lt;/p&gt;
&lt;p&gt;She was awarded the &lt;a href=&#34;https://reshamas.github.io/on-receiving-2019-community-leadership-award-from-numfocus/&#34;&gt;Community Leadership Award from NumFOCUS in 2019&lt;/a&gt;, and became a &lt;a href=&#34;https://pyfound.blogspot.com/2022/07/announcing-python-software-foundation.html&#34;&gt;Python Software Foundation Fellow&lt;/a&gt; in 2022.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>responsibility</title>
      <link>https://superbloom.design/tags/responsibility/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/responsibility/</guid>
      <description></description>
    </item>
    
    <item>
      <title>RightsCon</title>
      <link>https://superbloom.design/community/events/rightscon/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/community/events/rightscon/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Rocío Armillas Tiseyra</title>
      <link>https://superbloom.design/about/people/rocio-armillas-tiseyra/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/rocio-armillas-tiseyra/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://www.linkedin.com/in/armillas-tiseyra/?ref=newdesigncongress.org&#34;&gt;Rocío Armillas Tiseyra&lt;/a&gt; (she/they) is a Strategy and Fundraising Expert, who keenly navigates bureaucratic mazes and jargon–especially in conservative policy environments. Her experience includes technical assistance in urbanism and gender equality at the United Nations, funding climate innovation at EIT Climate-KIC, and at Bauhaus Earth, working in thought leadership and fundraising strategy. She co-edited &lt;a href=&#34;https://birkhauser.com/books/9783035627015&#34;&gt;Reconstructing the Future: Cities as Carbon Sinks&lt;/a&gt; while working there. She holds an MSc in Development Economics and a BSc in Social Anthropology, both from the London School of Economics and Political Science (LSE).&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Romain Robert</title>
      <link>https://superbloom.design/about/people/romain/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/romain/</guid>
      <description>&lt;p&gt;Romain is qualified lawyer in Belgium and specialises in technology law. He worked in academia and national and EU institutions where he focused on data protection (GDPR). He was program director of noyb, an NGO focusing on the enforcement of data protection.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Sam Smith</title>
      <link>https://superbloom.design/about/people/sam-smith/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/sam-smith/</guid>
      <description>&lt;p&gt;Sam has been practicing as an open source intelligence (OSINT) investigator to aid in human rights and social justice organizations for almost 10 years. Previously he has worked as Research Director at Equality Labs and Black Core Security. He focuses on combating violent extremism, dis/misinformation campaigns, and cultural manipulation. Sam uses his broad breadth of knowledge about global extremism, as well as his skills in OSINT, and deep understanding of digital security to better serve marginalized and vulnerable communities, movement partners, thought leaders, and collaborators. When he is not conducting research, he is sharpening his digital security skills, expanding digital privacy, analyzing state/non-state/private surveillance capabilities, as well as leading training sessions on general digital security, opposition research, OSINT, and more. Sam’s work has been directly used by outlets like ProPublica, Political Research Associates, Right Wing Watch, and many other mainstream media sources.&lt;/p&gt;
&lt;p&gt;Sam is currently Co-Founder and Research Director of Convocation Research and Design (CoRDs), a research, design, and art agency that combines human rights, technology, activism, advocacy, policy and design together to make complex technology more human readable.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Saptak S</title>
      <link>https://superbloom.design/about/people/saptak/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/saptak/</guid>
      <description>&lt;p&gt;Saptak S. is a human rights centered web developer, focusing on usability, security, privacy and accessibility topics in web development. He works as a web development contractor. He is a contributor and maintainer of various different open source projects like &lt;a href=&#34;https://www.a11yproject.com/&#34;&gt;The A11Y Project&lt;/a&gt;, &lt;a href=&#34;https://onionshare.org/&#34;&gt;OnionShare&lt;/a&gt; and &lt;a href=&#34;https://wagtail.org/&#34;&gt;Wagtail&lt;/a&gt;. He is part of the Open Source Design core team. He is also the author of the &lt;a href=&#34;https://almanac.httparchive.org/en/2022/security&#34;&gt;Security&lt;/a&gt; and &lt;a href=&#34;https://almanac.httparchive.org/en/2022/accessibility&#34;&gt;Accessibility&lt;/a&gt; chapter of &lt;a href=&#34;https://almanac.httparchive.org/en/2022/&#34;&gt;Web Almanac 2022&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Sara “Scout” Sinclair Brody</title>
      <link>https://superbloom.design/about/people/scout/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/scout/</guid>
      <description>&lt;p&gt;Scout has long been passionate about improving the usability of security tools. Her Computer Science doctoral dissertation, Access Control In and For The Real World, focused on the mis-integration of classic security mechanisms with modern human organizations.&lt;/p&gt;
&lt;p&gt;As a Product Manager at Google, she worked on projects such as 2-step verification, the Android operating system, and uProxy. When not working directly on software, she enjoys dabbling in graphic design, fiber artistry, and woodworking.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Sarah Fox</title>
      <link>https://superbloom.design/about/people/sarah-fox/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/sarah-fox/</guid>
      <description>&lt;p&gt;Sarah Fox is a Postdoctoral Scholar at the University of California, San Diego in the Department of Communication and The Design Lab. Her research focuses on how technological artifacts challenge or propagate social exclusions, by examining existing systems and building alternatives.&lt;/p&gt;
&lt;h2 id=&#34;project-name-care--iot&#34;&gt;Project name: Care &amp;amp; IoT&lt;/h2&gt;
&lt;h3 id=&#34;project-description&#34;&gt;Project description:&lt;/h3&gt;
&lt;p&gt;Sarah extended her research program on infrastructures of care by examining
how Internet of Things (IoT) technologies — or, ubiquitous networked
objects imbued with computational capacity — are newly shaping intimate
bodily experiences. Computing technologies for tracking the body are on the
verge of being introduced broadly across public and private spheres and are
poised to have unique and lasting effects on the privacy and autonomy of
those being sensed, as well as the responsibility of workers entrusted with
handling such data. For example, hygiene product manufacturers boast the
ability for new models of soap dispensers to track the number of times one
washes one’s hands during the day, correlating this information with
employee break records. By investigating such technologies as they are
being newly deployed, Sarah seeks to engage what computing researchers Paul
Dourish and Genevieve Bell (2011) call the “mess” of ubiquitous computing
as it unfolds — focusing on how these systems shape experiences on the
ground.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Schirin Lucie Richter</title>
      <link>https://superbloom.design/about/people/schirin-lucie-richter/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/schirin-lucie-richter/</guid>
      <description>&lt;p&gt;Schirin Lucie Richter (MA London) formerly with IDEO is a trained anthropologist turned design strategist/service designer. As Senior Partner at healthcare design and development firm Future Medical Systems (&lt;a href=&#34;http://futuremedicalsystems.com/&#34;&gt;futuremedicalsystems.com&lt;/a&gt;) she leads complex-innovation programmes bringing systems-oriented designs to healthcare. She mentors a wide range of design and insights teams as well as leadership teams at all sizes of organizations across industries.&lt;/p&gt;
&lt;p&gt;The common theme in her work is bringing clarity to complexity and delighting the often neglected B2B users or disempowered groups in general such as patients, caregivers, administrators or field service engineers. Under her leadership and guidance, teams go through a creative problem-solving process to envision future scenarios involving products, services and brands where thoughtfully designed touchpoints offer meaningful experiences for varying stakeholders while achieving business success and being mindful about societal and planetary impact. &lt;/p&gt;
&lt;p&gt;She holds multiple patents and contributed to work that received design awards. &lt;/p&gt;
&lt;p&gt;She teaches Design Research and Strategy at various universities, such as Stanford School of Medicine, Stanford d.school, California College of the Arts in San Francisco, UC Berkeley, TU Munich and University of Applied Sciences Flensburg. She&amp;rsquo;s National Guest Lecturer at Stanford Clinical Research Excellence Center and in 2018 she co-authored Discovery Design: Design Thinking for Healthcare Improvement, a handbook for everyone who considers themselves a changemaker in healthcare. After 12 years in the San Francisco Bay Area with a stint in Shanghai beforehand, Schirin is back in Germany where she grew up and plans to shake things up in complex industries such as healthcare and beyond!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Search</title>
      <link>https://superbloom.design/search/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/search/</guid>
      <description>&lt;p class=&#34;error message js-hidden&#34;&gt;You must have Javascript enabled to use this function.&lt;/p&gt;
&lt;p class=&#34;search-loading status message hidden&#34;&gt;Loading search index…&lt;/p&gt;

&lt;div class=&#34;search-input hidden&#34;&gt;
  

  &lt;form id=&#34;search-form&#34; class=&#34;search-form&#34; action=&#34;#&#34; method=&#34;post&#34; accept-charset=&#34;UTF-8&#34; role=&#34;search&#34;&gt;
    &lt;label for=&#34;query&#34; class=&#34;visually-hidden&#34;&gt;Search&lt;/label&gt;
    &lt;input type=&#34;search&#34; id=&#34;query&#34; name=&#34;query&#34; class=&#34;search-text&#34; placeholder=&#34;search our resource library&#34; maxlength=&#34;128&#34;&gt;
  &lt;/form&gt;
&lt;/div&gt;


&lt;div class=&#34;popular&#34;&gt;


  &lt;span class=&#34;popular-header&#34; tabindex=&#34;0&#34;&gt;frequently searched&lt;/span&gt;
  &lt;ul class=&#34;popular-keywords search-form tags&#34; aria-label=&#34;Popular searches&#34; role=&#34;list&#34;&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;ux-research&#34;&gt;UX Research&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;foundations-of-design&#34;&gt;Foundations of Design&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;how-to-security-privacy-and-transparency&#34;&gt;How to Security Privacy and Transparency&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;open-source&#34;&gt;Open Source&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;gdpr&#34;&gt;GDPR&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;community&#34;&gt;community&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;identity&#34;&gt;Identity&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;ai&#34;&gt;AI&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;how-to-research-for-human-rights&#34;&gt;How to Research for Human Rights&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;security-privacy-and-transparency&#34;&gt;Security, Privacy, and Transparency&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;professional-knowledge-user-research&#34;&gt;Professional Knowledge: User Research&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;human-centered-design&#34;&gt;Human-centered Design&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;design-spots&#34;&gt;Design Spots&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;internet-of-things&#34;&gt;Internet of Things&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;information-architecture&#34;&gt;Information Architecture&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;digital-infrastructure&#34;&gt;Digital Infrastructure&lt;/a&gt;&lt;/li&gt;
    
    &lt;li id=&#34;popular-term&#34; role=&#34;listitem&#34;  tabindex=&#34;0&#34; &gt;&lt;a id=&#34;terms&#34; class=&#34;search-popular search-terms&#34;  data-query=&#34;big-tech&#34;&gt;Big Tech&lt;/a&gt;&lt;/li&gt;
    
  &lt;/ul&gt;
  
&lt;/div&gt;


&lt;section class=&#34;search-results&#34; role=&#34;list&#34;&gt;

&lt;template&gt;
  &lt;article class=&#34;list-view card card--blog&#34; role=&#34;listitem&#34;&gt;
    &lt;div class=&#34;card__content&#34;&gt;
      &lt;header&gt;
        &lt;div class=&#34;submitted&#34;&gt;&lt;time class=&#34;created-date&#34;&gt;Date here&lt;/time&gt;&lt;/div&gt;
        &lt;h2 class=&#34;title&#34;&gt;&lt;a href=&#34;#&#34;&gt;Title here&lt;/a&gt;&lt;/h2&gt;
        &lt;img src=&#34;&#34; alt=&#34;&#34;&gt;
      &lt;/header&gt;
      &lt;p class=&#34;content description&#34; aria-role=&#34;Summary&#34;&gt;Summary here
        &lt;p /&gt;
    &lt;/div&gt;
  &lt;/article&gt;
&lt;/template&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>Secure Communications</title>
      <link>https://superbloom.design/learning/collections/secure-communications/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/learning/collections/secure-communications/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Secure Communications</title>
      <link>https://superbloom.design/topics/secure-communications/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/secure-communications/</guid>
      <description></description>
    </item>
    
    <item>
      <title>secure UX</title>
      <link>https://superbloom.design/tags/secure-ux/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/secure-ux/</guid>
      <description></description>
    </item>
    
    <item>
      <title>security</title>
      <link>https://superbloom.design/tags/security/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/security/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Security and Privacy</title>
      <link>https://superbloom.design/topics/security-and-privacy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/security-and-privacy/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Sign up</title>
      <link>https://superbloom.design/sign-up/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/sign-up/</guid>
      <description>
&lt;div class=&#34;page&#34;&gt;
    &lt;div class=&#34;container&#34;&gt;
        &lt;h1&gt;Enter your email address to sign up for our newsletter&lt;/h1&gt;

&lt;script type=&#34;text/javascript&#34;&gt;var pleaseEnter = &#34;&#34;; &lt;/script&gt;
    &lt;script type=&#34;text/javascript&#34;
src=&#34;https://ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js&#34;&gt;&lt;/script&gt;
&lt;script type=&#34;text/javascript&#34;
src=&#34;https://s3.amazonaws.com/phplist/phplist-subscribe-0.2.min.js&#34;&gt;&lt;/script&gt;
&lt;div id=&#34;phplistsubscriberesult&#34;&gt;&lt;/div&gt; &lt;form
action=&#34;https://simsec.hosted.phplist.com/lists/?p=subscribe&amp;id=1&#34;
method=&#34;post&#34; id=&#34;phplistsubscribeform&#34;&gt; &lt;input type=&#34;text&#34; name=&#34;email&#34;
value=&#34;&#34; id=&#34;emailaddress&#34; /&gt; &lt;button type=&#34;submit&#34;
id=&#34;phplistsubscribe&#34;&gt;Subscribe&lt;/button&gt; &lt;/form&gt;

    &lt;/div&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>Soraya Okuda</title>
      <link>https://superbloom.design/about/people/soraya/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/soraya/</guid>
      <description>&lt;p&gt;Soraya Okuda is a designer passionate about educational access. Soraya is excited to support efforts in conveying technical concepts to beginners, creating accessible materials for at-risk and under-resourced groups, and building free security and privacy tools.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Stephanie Morillo</title>
      <link>https://superbloom.design/about/people/stephanie-morillo/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/stephanie-morillo/</guid>
      <description>&lt;p&gt;Stephanie Morillo is a product manager and content strategist. She specializes in content strategy, developer marketing, and technical writing. She has written and delivered talks around the importance of content in the user experience, developer relations, the role of content strategy in open source, and marketing for software developers. Her work has appeared in various publications, and she has also served as an editor for titles published by O&amp;rsquo;Reilly Media and CRC Press.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Straight Talk: Surveillance and Mobile Messaging in NYC</title>
      <link>https://superbloom.design/work/nyc-study/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/work/nyc-study/</guid>
      <description>&lt;h2 id=&#34;lived-surveillance-in-new-york&#34;&gt;Lived Surveillance in New York&lt;/h2&gt;
&lt;p&gt;In December 2015, we talked with twelve New Yorkers from Harlem and Brownsville, meeting with people in libraries, offices, restaurants, and homes. We spent an hour listening to each participant talk about how they currently message, their privacy concerns and security practices, and their opinions on secure messaging. These conversations provided insights into how to design secure communication tools for a mass audience.&lt;/p&gt;
&lt;p&gt;Our findings indicate a significant gap between the priorities of the low-income African-Americans in our study and much of the security and privacy community, both academic and industrial. This report shares how social, economic, and technical systems shape priorities for secure communication among our participants. Against a backdrop of inevitable surveillance, participants shared their concerns about physical device security, particularly shoulder surfing, negative consequences of family-plan group billing arrangements giving unwanted access, and renter’s mindset that the handset is controlled by an adversarial carrier.&lt;/p&gt;
&lt;h2 id=&#34;outcomes&#34;&gt;Outcomes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/learning/blog/straight-talk&#34;&gt;Blog post&lt;/a&gt; with emerging findings.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Research/2015_NYC_Mobile_Messaging/NYCMobMsgTechReport.pdf&#34;&gt;Tech Report&lt;/a&gt;: Straight Talk: New Yorkers on Mobile Messaging and Implications for Privacy.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Talks-and-Slides/2016/IFF-%20Lived%20Surveillance.pdf&#34;&gt;Internet Freedom Festival 2016 presentation&lt;/a&gt;: Lived Surveillance in NYC: Design Implications for Mobile Messaging.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://superbloom.design/resources/Elliott-EverydaySurveillance-Shortened.pdf&#34;&gt;Everyday Surveillance Workshop at CHI 2016&lt;/a&gt;: Design Implications of Lived Surveillance in New York.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Talks-and-Slides/2016/HotPETS-2016-paper.pdf&#34;&gt;HotPETS 2016 paper&lt;/a&gt;: Respecting Participants in Privacy-Related User Studies: A Case Study of Mobile Messaging by Low-Income New Yorkers.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Talks-and-Slides/2016/AmeElliott-NYCStudy.pdf&#34;&gt;Usenix Security 2016 invited presentation&lt;/a&gt;: Privacy and Threat in Practice: Mobile Messaging by Low-Income New Yorkers.&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>Stuart Schecter</title>
      <link>https://superbloom.design/about/people/stuart/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/stuart/</guid>
      <description>&lt;p&gt;Stuart Schechter has researched computer security, human behavior, and occasionally gotten lost in such distant topics as computer architecture and research ethics. He is currently leading a small start-up, under the assumption that it’s hard to cause much harm to a venture that is already statistically expected to fail.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Sumana Harihareswara</title>
      <link>https://superbloom.design/about/people/sumana/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/sumana/</guid>
      <description>&lt;p&gt;Sumana Harihareswara is a project manager, programmer, and standup
comedian who leads a consultancy to help open source projects level up.
She led the rollout of the new PyPI.org, and has worked on Zulip, HTTPS
Everywhere, Mailman, MediaWiki, and several other open source projects.
Recently she has managed improvements to pip&amp;rsquo;s dependency resolver and
user experience, coached and trained maintainers in management skills,
and expedited the release of new versions of pipenv and autoconf. She&amp;rsquo;s
working on a book to teach what she&amp;rsquo;s learned about rejuvenating legacy
open source projects. She earned an Open Source Citizen Award in 2011
and a Google Open Source Peer Bonus in 2018, and participated in Recurse Center in 2013 and 2014. She lives in New York City and founded
Changeset Consulting in 2015.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Support us</title>
      <link>https://superbloom.design/support-us/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/support-us/</guid>
      <description></description>
    </item>
    
    <item>
      <title>surveillance</title>
      <link>https://superbloom.design/tags/surveillance/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/surveillance/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Susan Kennedy</title>
      <link>https://superbloom.design/about/people/susan/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/susan/</guid>
      <description>&lt;p&gt;Susan Kennedy is a librarian-by-training who wrangles projects big and small. Using participatory design and facilitation, she researches how we can make tech better, with recent projects in open source sustainability, funder advocacy, digital equity and inclusion, mobile surveillance, and platform transparency. She has also co-authored multiple articles and reports on subjects such as library broadband measurement and digital equity ecosystems. Susan has an MS in Library and Information Science from Simmons University where she focused on ethical technology and social informatics.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>sustainability</title>
      <link>https://superbloom.design/tags/sustainability/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/sustainability/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Tanya O&#39;Carroll</title>
      <link>https://superbloom.design/about/people/tanya-ocarroll/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/tanya-ocarroll/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Tara Kelly</title>
      <link>https://superbloom.design/about/people/tara-kelly/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/tara-kelly/</guid>
      <description>&lt;p&gt;Tara Kelly is a journalist, media consultant and e-learning producer. She has over 10 years of experience working on Internet Freedom and digital rights issues for not-for-profits. Most recently, Tara led and produced courses for the Advocacy Assembly Shutdown Academy, an e-learning experience designed to train journalists, advocates, and human rights defenders on Internet Shutdowns. She also served as the data editor for the European Journalism Centre, where she hosted two podcasts on data journalism and media innovation. Previously, she worked as a journalist for The Huffington Post, TIME Magazine and CNN International. Her articles have also appeared in the Financial Times Magazine, Poynter.org and France24.com. She has experience in strategic communications, podcasting, digital media and data storytelling.Tara holds a BA in Political Science from Duquesne University and an MA in International Conflict Analysis from the University of Kent at Canterbury, Brussels School of International Studies. Most recently, she earned a postgraduate degree in Data Journalism from University College Dublin. She is currently enrolled at City St George&amp;rsquo;s, University of London, completing her Graduate Diploma in Law.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Tara Tarakiyee</title>
      <link>https://superbloom.design/about/people/tara-tarakiyee/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/tara-tarakiyee/</guid>
      <description>&lt;p&gt;Tara is a public interest technologist, and a free and open source software advocate, and a longtime believer in the transformational potential of information technology as an enabler of human rights and to liberate societies from systemic oppressions. At the Jordan Open Source Association and the Association for Progressive Communications, they&amp;rsquo;ve worked to help support individuals, groups and communities working on human rights online and free and open source software build their capacity to work safely online. At the Open Technology Fund, they&amp;rsquo;ve helped essential and cutting edge open source internet freedom projects gain access to much needed resources and funding to do what they do best. They currently work as a technologist at &lt;a href=&#34;http://techcultivation.org/&#34;&gt;techcultivation.org&lt;/a&gt;, and enjoy investigating how far they can push the limits of home-cooked comfort food.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>technical infrastructure</title>
      <link>https://superbloom.design/tags/technical-infrastructure/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/technical-infrastructure/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Templates and Resources</title>
      <link>https://superbloom.design/work/templates/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/work/templates/</guid>
      <description>&lt;h2 id=&#34;workshop-materials&#34;&gt;Workshop Materials&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Research/2015_NYC_Mobile_Messaging/NYCMobMsgScreener.pdf&#34;&gt;Trustworthy IoT Toolkit&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/research%20tools/app_feedback_gathering.pdf&#34;&gt;User Feedback Activities&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;fieldwork-materials&#34;&gt;Fieldwork Materials&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Research/2015_NYC_Mobile_Messaging/NYCMobMsgScreener.pdf&#34;&gt;Example Screener&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Research/2015_NYC_Mobile_Messaging/NYCMobMsgModelRelease.pdf&#34;&gt;Model Release&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Research/2015_NYC_Mobile_Messaging/NYCMobMsgParticipantBillofRights.pdf&#34;&gt;Participant Bill of Rights&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/simplysecure/resources/blob/master/Research/2015_NYC_Mobile_Messaging/NYCMobMsgConsentForm.pdf&#34;&gt;Research Consent Form&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;style-guides&#34;&gt;Style Guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/resources/style-guide-v1.pdf&#34;&gt;Simply Secure Style Guide&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/resources/tor-style-guide-v1.3.pdf&#34;&gt;Tor Project Style Guide&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>testing</title>
      <link>https://superbloom.design/tags/testing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/testing/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Thomas Oberndörfer</title>
      <link>https://superbloom.design/about/people/thomas-oberndorfer/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/thomas-oberndorfer/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Tiffany Ou</title>
      <link>https://superbloom.design/about/people/tiffany/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/tiffany/</guid>
      <description>&lt;p&gt;Tiffany is a freelance designer, currently residing in Los Angeles, California and specializing in information architecture, brand identities, and multi-platform design and production. Aside from a couple corporate clients, her current work mostly revolves around the blockchain and distributed technology space. She’s a huge proponent of open source technology and design and is passionate about supporting projects that promote internet freedom, security and education.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Tin Geber</title>
      <link>https://superbloom.design/about/people/tin-geber/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/tin-geber/</guid>
      <description>&lt;p&gt;Creative strategist, practitioner and technologist. Experienced in human-centered program/service design, development, implementation, and learning.  Focused on supporting social change organizations to make the most of data and technology. Tin is founder of &lt;a href=&#34;https://draftlab.org/&#34;&gt;Draftlab&lt;/a&gt;, a creative design/development consultancy for social good champions. Previously, he was managing director of &lt;a href=&#34;https://greenhost.net/&#34;&gt;Greenhost&lt;/a&gt;; social innovation specialist for &lt;a href=&#34;https://hivos.org/&#34;&gt;Hivos&lt;/a&gt;; and design and tech lead for &lt;a href=&#34;https://www.theengineroom.org/&#34;&gt;The Engine Room&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Tin’s passion is improving people’s relationship with technology through better tools, activism, art, and education. His mixed bag of skills gives him an eye for patterns and systems. He made role-playing games for activists, microtasking platforms for human rights, sonic art installations on online abuse, needy Twitter artist bots, and scarves with LEDs.&lt;/p&gt;
&lt;p&gt;Tin has a BA in Media Sciences, and an &lt;a href=&#34;http://www.gold.ac.uk/pg/ma-computational-arts/&#34;&gt;MA in Computational Arts&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>toolkit</title>
      <link>https://superbloom.design/formats/toolkit/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/formats/toolkit/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Tori Boeck</title>
      <link>https://superbloom.design/about/people/tori-boeck/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/tori-boeck/</guid>
      <description>&lt;p&gt;Victoria (Tori) Boeck is an expert on open data, data sharing and government data (specifically in Germany). Currently she is a technical consultant at IBM iX working with public sector clients. Previously she was a Transformation Manager at CityLAB Berlin, a public innovation lab funded by the Berlin Senate Chancellery and run by the Technologiestiftung Berlin. There she worked with the Berlin city government on topics including open data, open source, and digital innovation. She holds a Masters of Public Policy from the Hertie School.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>transparency</title>
      <link>https://superbloom.design/tags/transparency/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/transparency/</guid>
      <description></description>
    </item>
    
    <item>
      <title>trust</title>
      <link>https://superbloom.design/tags/trust/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/trust/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Trust and Transparency</title>
      <link>https://superbloom.design/topics/trust-and-transparency/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/trust-and-transparency/</guid>
      <description></description>
    </item>
    
    <item>
      <title>ui</title>
      <link>https://superbloom.design/tags/ui/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/ui/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Underexposed</title>
      <link>https://superbloom.design/underexposed/2017-workshop/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/underexposed/2017-workshop/</guid>
      <description>&lt;p&gt; &lt;img src=&#34;https://superbloom.design/underexposed/assets/2017-header-web.png&#34;
alt=&#34;Underexposed Workshop Header Image&#34;/&gt;&lt;/p&gt;
&lt;h2&gt; About the workshop&lt;/h2&gt;
&lt;p&gt;As the technology industry strives to build intelligence through data, what does it mean for a &#34;smart&#34; system to be not just technically reliable or theoretically accurate, but trustworthy in practice?&lt;/p&gt;
&lt;p&gt;Furthermore, at a time where being first-to-market seems to outweigh ethical considerations, how can designers, researchers, and technologists incorporate goals such as privacy, security, and transparency into their work? What barriers do they face in designing such massively complex systems, what successful strategies are they employing today, and what work do we need for the future? &lt;/p&gt;
&lt;p&gt;Underexposed brings together design and technology practitioners to have hard conversations at the intersection of human-centered thinking, ethics, and computing. This year the event will also feature an open evening session for members of the public to join in the conversation.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://superbloom.design/underexposed/2017-salon/&#34;&gt;Learn more about the public salon&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The workshop portion of the event is by invitation only and is at capacity. If you are a designer, a technologist, or a researcher working on issues of human-centered privacy and security and are seeking an invitation, please reach out to underexposed@superbloom.design.
&lt;p&gt;
10am-5pm
&lt;br&gt;Thursday, November 9th 2017
&lt;br&gt;We Are All In Coworking
&lt;br&gt;Torstr. 177
&lt;br&gt;10115 Berlin, Germany
&lt;/p&gt;
&lt;p&gt;&lt;hr&gt;&lt;/p&gt;
&lt;h3&gt;Partners, supporters, and friends&lt;/h3&gt;
&lt;div class=&#34;container&#34;&gt;
    &lt;div class=&#34;flex-grid-row&#34;&gt;
      &lt;div class=&#34;flex-grid-col partner-box&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/underexposed/assets/logo-ford.png&#34;
        alt=&#34;&#34; height=&#34;150&#34; width=&#34;150&#34;&gt;
        &lt;p&gt;Ford Foundation&lt;/p&gt;
      &lt;/div&gt;
      &lt;div class=&#34;flex-grid-col partner-box&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/underexposed/assets/logo-mozilla.png&#34;
        alt=&#34;&#34; height=&#34;150&#34; width=&#34;150&#34;&gt;
        &lt;p&gt;Mozilla Foundation&lt;/p&gt;
      &lt;/div&gt;
      &lt;div class=&#34;flex-grid-col partner-box&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/underexposed/assets/logo-if.png&#34;
        alt=&#34;&#34; height=&#34;150&#34; width=&#34;150&#34;&gt;
        &lt;p&gt;Projects By If&lt;/p&gt;
      &lt;/div&gt;
      &lt;div class=&#34;flex-grid-col partner-box&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/underexposed/assets/logo-prototype-fund.png&#34;
        alt=&#34;&#34; height=&#34;150&#34; width=&#34;150&#34;&gt;
        &lt;p&gt;Prototype Fund&lt;/p&gt;
      &lt;/div&gt;
      &lt;div class=&#34;flex-grid-col partner-box&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/underexposed/assets/logo-things-con.png&#34;
        alt=&#34;&#34; height=&#34;150&#34; width=&#34;150&#34;&gt;
        &lt;p&gt;Things Con&lt;/p&gt;
      &lt;/div&gt;
      &lt;div class=&#34;flex-grid-col partner-box&#34;&gt;
        &lt;img src=&#34;https://superbloom.design/underexposed/assets/logo-least-authority.png&#34;
        alt=&#34;&#34; height=&#34;150&#34; width=&#34;150&#34;&gt;
        &lt;p&gt;Least Authority&lt;/p&gt;
      &lt;/div&gt;
    &lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;&lt;hr&gt;&lt;/p&gt;
&lt;h3 id=&#34;conduct&#34;&gt;Code of Conduct&lt;/h3&gt;
&lt;p&gt;We are committed to providing a harassment-free event experience for everyone.&lt;/p&gt;
&lt;p&gt;Harassment includes but is not limited to offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.&lt;/p&gt;
&lt;p&gt;Participants asked to stop any harassing behavior are expected to comply immediately. If a participant engages in harassing behavior, the workshop organizers may take any action they deem appropriate, including warning or expelling the offender.&lt;/p&gt;
&lt;p&gt;If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact Scout or Ame, who will introduce themselves at the start of the workshop. We will work with you to take appropriate action, up to and including contacting venue security or local law enforcement if necessary. We value your attendance and want you to feel safe.&lt;/p&gt;
&lt;p&gt;We expect participants to follow these rules at the workshop and associated events.&lt;/p&gt;
&lt;p&gt;&lt;hr&gt;&lt;/p&gt;
&lt;h3 id=&#34;contact&#34;&gt;Contact&lt;/h3&gt;
&lt;p&gt;Questions? Concerns? Contact us at underexposed@superbloom.design.&lt;/p&gt;
&lt;p&gt;Learn more about last year&#39;s &lt;a href=&#34;https://superbloom.design/underexposed/underexposed-2016&#34;&gt;Underexposed 2016&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Underexposed 2015</title>
      <link>https://superbloom.design/underexposed/underexposed-2015/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/underexposed/underexposed-2015/</guid>
      <description>&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/underexposed/assets/header_large_date.png&#34; alt=&#34;Underexposed Workshop Header Image&#34; width=&#34;750&#34; height=&#34;170&#34;&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Please note: this iteration of Underexposed has passed. Please see the main &lt;a href=&#34;https://superbloom.design/underexposed&#34;&gt;Underexposed page&lt;/a&gt; to learn about the most recent iteration.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;#logistics&#34;&gt;Basic Logistics&lt;/a&gt; | &lt;a href=&#34;#agenda&#34;&gt;Agenda&lt;/a&gt; | &lt;a href=&#34;#travel&#34;&gt;Lodging &amp;amp; Travel&lt;/a&gt; | &lt;a href=&#34;#conduct&#34;&gt;Code of Conduct&lt;/a&gt; | &lt;a href=&#34;#contact&#34;&gt;Contact&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Underexposed is an invitation-only workshop that celebrates the role of design in meeting the privacy needs of a broad audience. Building on a foundation of technical and operational realities, this workshop will explore emerging best practices for creating a new generation of useful, usable, and delightful user interfaces. Through invited talks and round-table discussion, we will chart a vision of the grand challenges and opportunities in user experience (UX) for secure communication.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;basic-logistics&#34;&gt;Basic Logistics&lt;/h3&gt;
&lt;h4 id=&#34;date-and-time&#34;&gt;Date and Time&lt;/h4&gt;
&lt;p&gt;9am-5pm on Thursday, October 15th&lt;br&gt;
Followed by a happy hour&lt;/p&gt;
&lt;h4 id=&#34;location&#34;&gt;Location&lt;/h4&gt;
&lt;p&gt;185 Berry Street&lt;br&gt;
Lobby 3, 5th Floor&lt;br&gt;
San Francisco, CA 94107&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Thanks to Dropbox for donating space for the event!&lt;/em&gt;&lt;/p&gt;
&lt;iframe src=&#34;https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d3153.5856845551803!2d-122.39161670000001!3d37.77631190000002!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x808580889bc8761f%3A0x36b753cc3d2f0afb!2sDropbox+Inc.!5e0!3m2!1sen!2sus!4v1443624731677&#34; width=&#34;400&#34; height=&#34;300&#34; frameborder=&#34;0&#34; style=&#34;border:0&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;hr&gt;
&lt;h3 id=&#34;agenda&#34;&gt;Agenda&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;This is a rough outline of the day; more details to follow.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;9:00 – Underexposed begins&lt;/p&gt;
&lt;p&gt;We start get started over a light breakfast. Our morning sessions are designed to set a shared vocabulary and frame of reference as we share stories as a global community working at the intersection of UX and security.&lt;/p&gt;
&lt;p&gt;12:15-1:15 – Lunch served on site&lt;/p&gt;
&lt;p&gt;Our afternoon sessions prioritize specific obstacles to effective collaboration between UX designers, researchers, security experts, and developers.&lt;/p&gt;
&lt;p&gt;5:00 – Official program ends and happy hour begins&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;lodging--travel&#34;&gt;Lodging &amp;amp; Travel&lt;/h3&gt;
&lt;h4 id=&#34;hotel&#34;&gt;Hotel&lt;/h4&gt;
&lt;p&gt;We have reserved a block of rooms at the Courtyard San Francisco Downtown. If you are joining us from out of town, we encourage you to book a room there.&lt;/p&gt;
&lt;p&gt;Courtyard San Francisco Downtown&lt;br&gt;
299 2nd Street&lt;br&gt;
San Francisco, CA 94105&lt;br&gt;
Phone: 1-415-947-0700&lt;br&gt;
Room block name: CTM/Underexposed&lt;/p&gt;
&lt;h4 id=&#34;to-and-from-the-workshop&#34;&gt;To and from the workshop&lt;/h4&gt;
&lt;p&gt;185 Berry Street is an 18-minute walk or a 10-minute bus ride (#10 to 3rd &amp;amp; Townsend, $2.25 exact change) from the hotel. The Caltrain 4th and King St. Station (which is the northern terminus of the Caltrain line) is a block away from 185 Berry, as are MUNI T and N stops.&lt;/p&gt;
&lt;p&gt;Generally speaking, San Francisco has a variety of public-transport options, so we encourage you to check &lt;a href=&#34;http://maps.google.com&#34;&gt;Google Maps&lt;/a&gt;, &lt;a href=&#34;https://511.org/transit&#34;&gt;511.org&lt;/a&gt; or a similar service to figure out your best options.&lt;/p&gt;
&lt;p&gt;Finally, walking along The Embarcadero toward the Ferry Building has beautiful views of the Bay, so if the weather is dry (which it should be), consider taking a stroll.&lt;/p&gt;
&lt;h4 id=&#34;airport&#34;&gt;Airport&lt;/h4&gt;
&lt;p&gt;San Francisco International Airport (SFO) is your best bet if you&amp;rsquo;re coming in from out of town. There are a variety of public-transport options for getting to and from the airport, including BART and ride-sharing apps. Don&amp;rsquo;t hesitate to reach out if you want to talk them through.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;code-of-conduct&#34;&gt;Code of Conduct&lt;/h3&gt;
&lt;p&gt;We are committed to providing a harassment-free workshop experience for everyone.&lt;/p&gt;
&lt;p&gt;Harassment includes but is not limited to offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.&lt;/p&gt;
&lt;p&gt;Participants asked to stop any harassing behavior are expected to comply immediately. If a participant engages in harassing behavior, the workshop organizers may take any action they deem appropriate, including warning or expelling the offender.&lt;/p&gt;
&lt;p&gt;If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact Scout or Ame, who will introduce themselves at the start of the workshop. We will work with you to take appropriate action, up to and including contacting venue security or local law enforcement if necessary. We value your attendance and want you to feel safe.&lt;/p&gt;
&lt;p&gt;We expect participants to follow these rules at the workshop and associated social events.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;contact&#34;&gt;Contact&lt;/h3&gt;
&lt;p&gt;Questions? Concerns? Contact us at &lt;a href=&#34;mailto:underexposed@superbloom.design&#34;&gt;underexposed@superbloom.design&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Underexposed 2016</title>
      <link>https://superbloom.design/underexposed/underexposed-2016/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/underexposed/underexposed-2016/</guid>
      <description>&lt;p&gt; &lt;img src=&#34;https://superbloom.design/underexposed/assets/2016-header-subtitle-web.png&#34;
alt=&#34;Underexposed Workshop Header Image&#34;/&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Please note: this iteration of Underexposed has passed. Please see the main &lt;a href=&#34;https://superbloom.design/underexposed/&#34;&gt;Underexposed page&lt;/a&gt; to learn about the most recent iteration.&lt;/em&gt;
&lt;p&gt; &lt;a href=&#34;#logistics&#34;&gt;Basic Logistics&lt;/a&gt; | &lt;a href=&#34;#agenda&#34;&gt;Agenda&lt;/a&gt; | &lt;a
href=&#34;#travel&#34;&gt;Lodging &amp; Travel&lt;/a&gt; | &lt;a href=&#34;#conduct&#34;&gt;Code of Conduct&lt;/a&gt; |
&lt;a href=&#34;#contact&#34;&gt;Contact&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Do algorithms rule our lives?&lt;/p&gt;
&lt;p&gt;Technologists must strive to understand the needs, wants, and perceptions of
real users as part of the process of building useful, usable products. As
technology becomes ever-more intertwined with our daily lives, many users are
surprised to find that their chat programs, online shoe stores, and even their
“smart” lightbulbs are aggregating data on their actions and behavior.&lt;/p&gt;
&lt;p&gt;Much of this data-gathering is well-intentioned. Many technology companies use data to perform user research, learn about people’s needs, and improve their products accordingly. But as instrumented systems become the norm and the value of data grows, we must also ask: how does this information-gathering impact our sense of privacy, security, and well-being? In an era of increasing data complexity, where information seems to sift across boundaries in unexpected ways – both through intentional action and unintentional breaches – what does it mean for a technology to respect its users? &lt;/p&gt;
&lt;p&gt;Underexposed is a workshop that brings together designers, user-experience researchers, and technologists to have hard conversations at the intersection of human-centered design, ethics, and computing. This year the event will focus on the data and algorithms that are coming to permeate all aspects of our daily lives, such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Chatbots and learning chat clients
&lt;li&gt;Predictive recommendations for music, bars, and blind dates
&lt;li&gt;Location-based ad targeting
&lt;li&gt;Financial scoring systems for employment and credit
&lt;li&gt;Stream filters and filter bubbles
&lt;li&gt;Genetic matching and medical diagnosis
&lt;li&gt;Predictive policing and algorithmic sentencing
&lt;/ul&gt;
&lt;p&gt;Well-intentioned innovations in these and other domains may have scary consequences. Designers and user researchers must play a critical role in empowering users to both understand and participate in the data-driven decisions that surround them.&lt;/p&gt;
&lt;p&gt;At this workshop we will explore new trends, critique example solutions, and identify hard unsolved problems. We welcome designers, user-experience researchers, technologists, and program/product managers to share their experiences, designs, solutions, and challenges.&lt;/p&gt;
&lt;p&gt;The workshop is open in that all are welcome to propose talks or apply to attend, but limited in that we can only accept a small number of participants. Stay tuned for more details on the proposal process, or email underexposed@superbloom.design to be notified when the call for proposals is open.&lt;/p&gt;
&lt;p&gt;&lt;hr&gt;&lt;/p&gt;
&lt;h3 id=&#34;logistics&#34;&gt;Basic Logistics&lt;/h3&gt;
&lt;h4&gt;Date and Time&lt;/h4&gt;
&lt;p&gt;
9am-5pm
&lt;br&gt;November 11, 2016
&lt;br&gt;Followed by a happy hour
&lt;/p&gt;
&lt;h4&gt;Location&lt;/h4&gt;
&lt;p&gt;
IXDS
&lt;br&gt;Paul-Lincke-Ufer 39-40
&lt;br&gt;10999 Berlin, Germany
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Thanks to IXDS for donating space for the event!&lt;/em&gt;&lt;/p&gt;
&lt;iframe src=&#34;https://www.google.com/maps/embed?pb=!1m14!1m8!1m3!1d9716.098970409856!2d13.4225691!3d52.4967917!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x0%3A0x20828871b13e9cad!2sIXDS!5e0!3m2!1sen!2sus!4v1473785861651&#34; width=&#34;400&#34; height=&#34;400&#34; frameborder=&#34;0&#34; style=&#34;border:0&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;p&gt;&lt;hr&gt;&lt;/p&gt;
&lt;h3 id=&#34;agenda&#34;&gt;Agenda&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;This is a rough outline of the day; more details to follow.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;9:00 – Underexposed begins&lt;/p&gt;
&lt;p&gt;We start get started over a light breakfast. Our morning sessions are designed to set a shared vocabulary and frame of reference as we share stories as a global community working on thorny issues such as security, privacy, and transparency in the era of algorithms.&lt;/p&gt;
&lt;p&gt;12:15-1:15 – Lunch served on site&lt;/p&gt;
&lt;p&gt;Our afternoon sessions continue the work from the morning, and explore new themes brought forth by presenters.&lt;/p&gt;
&lt;p&gt;5:00 – Official program ends and happy hour begins&lt;/p&gt;
&lt;p&gt;&lt;hr&gt;&lt;/p&gt;
&lt;h3 id=&#34;travel&#34;&gt;Lodging &amp; Travel&lt;/h3&gt;
&lt;p&gt;More details to come.&lt;/p&gt;
&lt;p&gt;&lt;hr&gt;&lt;/p&gt;
&lt;h3 id=&#34;conduct&#34;&gt;Code of Conduct&lt;/h3&gt;
&lt;p&gt;We are committed to providing a harassment-free workshop experience for everyone.&lt;/p&gt;
&lt;p&gt;Harassment includes but is not limited to offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.&lt;/p&gt;
&lt;p&gt;Participants asked to stop any harassing behavior are expected to comply immediately. If a participant engages in harassing behavior, the workshop organizers may take any action they deem appropriate, including warning or expelling the offender.&lt;/p&gt;
&lt;p&gt;If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact Scout or Ame, who will introduce themselves at the start of the workshop. We will work with you to take appropriate action, up to and including contacting venue security or local law enforcement if necessary. We value your attendance and want you to feel safe.&lt;/p&gt;
&lt;p&gt;We expect participants to follow these rules at the workshop and associated social events.&lt;/p&gt;
&lt;p&gt;&lt;hr&gt;&lt;/p&gt;
&lt;h3 id=&#34;contact&#34;&gt;Contact&lt;/h3&gt;
&lt;p&gt;Questions? Concerns? Contact us at underexposed@superbloom.design.&lt;/p&gt;
&lt;p&gt;Learn more about &lt;a href=&#34;https://superbloom.design/underexposed/underexposed-2015/&#34;&gt;Underexposed 2015&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Underexposed 2017</title>
      <link>https://superbloom.design/underexposed/2017-salon/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/underexposed/2017-salon/</guid>
      <description>&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/underexposed/assets/underexposed-header-gray.png&#34; alt=&#34;Underexposed Header Image&#34;&gt;
&lt;/p&gt;
&lt;p&gt;When you use a smart gadget or give your data to the cloud, how do you know it&amp;rsquo;s trustworthy? In an era where our home appliances have joined the Internet of Things and our every action is being analyzed by an artificial intelligence, what role does design play in making sure these devices behave ethically?&lt;/p&gt;
&lt;p&gt;Join designers, hackers, makers, and thinkers in considering this and other issues at the intersection of design and trust. This year Underexposed features an evening salon, which is open to the public, in addition to a day-long invitational workshop.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/underexposed/assets/2017-salon-header.png&#34; alt=&#34;Underexposed Salon: Trust &amp;amp; Design&#34;&gt;
&lt;/p&gt;
&lt;h3 id=&#34;about-the-salon&#34;&gt;About the Salon&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;November 8th, 2017, 7-9pm, doors open at 6:30pm&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Mozilla Offices on the Banks of the Spree&lt;br&gt;
Schlesische Straße 27&lt;br&gt;
Gebäude 3, 3. Obergeschoss&lt;br&gt;
10997 Berlin Germany&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://pretix.eu/simplysecure/underexposed/&#34;&gt;Register here&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Co-hosted by &lt;a href=&#34;https://projectsbyif.com/&#34;&gt;IF&lt;/a&gt; as part of their Trust &amp;amp; Design &lt;a href=&#34;https://trustanddesign.projectsbyif.com/&#34;&gt;meetup series&lt;/a&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;salon-panelists-include&#34;&gt;Salon panelists include&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href=&#34;https://sarah.gold/&#34;&gt;Sarah Gold&lt;/a&gt;: Trust and Design&lt;/strong&gt;&lt;br&gt;
Sarah is a designer interested in privacy, security, and networks in the public domain. She founded IF in 2015 to work on ambitious projects involving accountability, machine learning, and digital rights. A NESTA New Radical and Forbes 30 under 30 awardee, Sarah sits on the practitioner panel for the Research Institute in the Science of Cyber Security. Sarah will be talking about their work building tools to help teams make better decisions about consent.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href=&#34;https://www.cennydd.com/&#34;&gt;Cennydd Bowles&lt;/a&gt;: The Shadows of Data&lt;/strong&gt;&lt;br&gt;
Cennydd is a London-based designer and writer focusing on the ethics of future technologies. He has worked with companies including Twitter, Samsung, and the BBC, and is a popular speaker at technology and design events worldwide. His second book &amp;lsquo;Future Ethics&amp;rsquo; will be released in 2018. The Shadows of Data: The data-driven economy is here to stay. Datafication is in the ideological ascendancy, and the promises of an artificially intelligent world will require us to share our intimate secrets. Algorithmic decisions will increasingly be tied to our data shadows. In a landscape of black-box obfuscation, diminished user agency, and diluted moral responsibility, can designers be sure they are empowering rather than disenfranchising?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href=&#34;https://www.socialcooling.com&#34;&gt;Tijmen Schep&lt;/a&gt;: Social Cooling – Communicating the Why of Privacy Design&lt;/strong&gt;&lt;br&gt;
Tijmen is a technology critic and privacy designer. As a critic, he works on the question of how to increase audience demand for privacy-enhancing technologies, which has become focused on the concept of &amp;ldquo;social cooling,&amp;rdquo; the data version of global warming. As a privacy designer, he explores cloudless alternatives to popular smart products. His book &lt;em&gt;Design My Privacy&lt;/em&gt; is used by design schools across the Netherlands. He also helped found the critical &amp;ldquo;ubicomp design&amp;rdquo; course at the Amsterdam University of Applied Sciences, and through the SETUP medialab was a driving force behind several humorous design fictions that explore the darker side of the Internet of Things.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;invitation-only-workshop&#34;&gt;Invitation-Only Workshop&lt;/h3&gt;
&lt;p&gt;Space at the workshop is limited, and we are at capacity. If you are interested in attending but don&amp;rsquo;t already have an invitation, please contact us. &lt;a href=&#34;https://superbloom.design/underexposed/2017-workshop&#34;&gt;Learn more&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;partners-supporters-and-friends&#34;&gt;Partners, supporters, and friends&lt;/h3&gt;
&lt;p&gt;
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/underexposed/assets/logo-ford.png&#34; alt=&#34;Ford Foundation&#34;&gt;
 Ford Foundation&lt;br&gt;

&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/underexposed/assets/logo-mozilla.png&#34; alt=&#34;Mozilla Foundation&#34;&gt;
 Mozilla Foundation&lt;br&gt;

&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/underexposed/assets/logo-if.png&#34; alt=&#34;Projects By IF&#34;&gt;
 Projects By IF&lt;br&gt;

&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/underexposed/assets/logo-prototype-fund.png&#34; alt=&#34;Prototype Fund&#34;&gt;
 Prototype Fund&lt;br&gt;

&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/underexposed/assets/logo-things-con.png&#34; alt=&#34;Things Con&#34;&gt;
 Things Con&lt;br&gt;

&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/underexposed/assets/logo-least-authority.png&#34; alt=&#34;Least Authority&#34;&gt;
 Least Authority&lt;br&gt;
&lt;a href=&#34;https://www.meetup.com/Behavior-Emotion-Design/&#34;&gt;
&lt;img class=&#34;image&#34; src=&#34;https://superbloom.design/underexposed/assets/logo-bed.png&#34; alt=&#34;BED Meetup&#34;&gt;
&lt;/a&gt; BED Meetup&lt;/p&gt;
&lt;p&gt;Simply Secure is a not-for-profit organization and relies on support from the public to hold events like Underexposed. If you would like to support this event and our other work, please consider making a donation via PayPal or by contacting us at &lt;a href=&#34;mailto:donations@superbloom.design&#34;&gt;donations@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&amp;amp;hosted_button_id=Z7NMFLAKDRGRA&#34;&gt;Donate via PayPal&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;code-of-conduct&#34;&gt;Code of Conduct&lt;/h3&gt;
&lt;p&gt;We are committed to providing a harassment-free event experience for everyone.&lt;/p&gt;
&lt;p&gt;Harassment includes but is not limited to offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.&lt;/p&gt;
&lt;p&gt;Participants asked to stop any harassing behavior are expected to comply immediately. If a participant engages in harassing behavior, the workshop organizers may take any action they deem appropriate, including warning or expelling the offender.&lt;/p&gt;
&lt;p&gt;If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact Scout or Ame, who will introduce themselves at the start of the workshop. We will work with you to take appropriate action, up to and including contacting venue security or local law enforcement if necessary. We value your attendance and want you to feel safe.&lt;/p&gt;
&lt;p&gt;We expect participants to follow these rules at the workshop and associated events.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;contact&#34;&gt;Contact&lt;/h3&gt;
&lt;p&gt;Questions? Concerns? Contact us at &lt;a href=&#34;mailto:underexposed@superbloom.design&#34;&gt;underexposed@superbloom.design&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Rope bridge image &lt;a href=&#34;https://creativecommons.org/licenses/by/2.0/deed.en&#34;&gt;CC&lt;/a&gt;-licensed by &lt;a href=&#34;https://www.flickr.com/people/62787780@N06&#34;&gt;John5199&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Underexposed Machine Ethics</title>
      <link>https://superbloom.design/underexposed/2018-meetup/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/underexposed/2018-meetup/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://superbloom.design/underexposed/assets/underexposed-machine.jpg&#34;
alt=&#34;Underexposed Header Image&#34;/&gt;&lt;/p&gt;
&lt;p&gt;Algorithms affect almost every aspect of daily life, from self-driving cars to predictive policing to banking to even something as benign as movie recommendations. But, how do we question these systems, how do we think about ethical intervention and ethical standards for algorithms in our daily lives? This talk, with invited speakers Maya Indira Ganesh, Adam Harvey and Caroline Sinders, focuses critically on how to create ethical standards for machine learning, from artistic work examples to analysis of current systems to better ways to work with data.&lt;/p&gt;
&lt;p&gt;Speakers include &lt;strong&gt;&lt;a href=&#34;https://carolinesinders.com/&#34;&gt;Caroline Sinders&lt;/a&gt;, &lt;a href=&#34;https://bodyofwork.in/&#34;&gt;Maya Indira Ganesh&lt;/a&gt;, &lt;a href=&#34;https://ahprojects.com/&#34;&gt;Adam Harvey&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.meetup.com/Underexposed-Trust-and-Design/events/249193295/&#34; class=&#34;button button--secondary read-more&#34;&gt;Signup here&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Co-hosted by &lt;a href=&#34;http://www.thoughtworks.com/&#34;&gt;ThoughtWorks Berlin&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;hr&gt;&lt;/p&gt;
&lt;p&gt;Simply Secure is a not-for-profit organization and relies on support from the public to hold events like Underexposed. If you would like to support this event and our other work, please consider making a donation via PayPal or by contacting us at donations@superbloom.design.&lt;/p&gt;
&lt;br&gt;
&lt;form action=&#34;https://www.paypal.com/cgi-bin/webscr&#34; method=&#34;post&#34; target=&#34;_top&#34;&gt;
&lt;input type=&#34;hidden&#34; name=&#34;cmd&#34; value=&#34;_s-xclick&#34;&gt;
&lt;input type=&#34;hidden&#34; name=&#34;hosted_button_id&#34; value=&#34;Z7NMFLAKDRGRA&#34;&gt;
&lt;input type=&#34;image&#34; src=&#34;https://www.paypalobjects.com/en_US/i/btn/btn_donateCC_LG.gif&#34; border=&#34;0&#34; name=&#34;submit&#34; alt=&#34;Donate via PayPal&#34;&gt;
&lt;img alt=&#34;&#34; border=&#34;0&#34; src=&#34;https://www.paypalobjects.com/en_US/i/scr/pixel.gif&#34; width=&#34;1&#34; height=&#34;1&#34;&gt;
&lt;/form&gt;
&lt;p&gt;&lt;hr&gt;&lt;/p&gt;
&lt;h3 id=&#34;conduct&#34;&gt;Code of Conduct&lt;/h3&gt;
&lt;p&gt;We are committed to providing a harassment-free event experience for everyone.&lt;/p&gt;
&lt;p&gt;Harassment includes but is not limited to offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.&lt;/p&gt;
&lt;p&gt;Participants asked to stop any harassing behavior are expected to comply immediately. If a participant engages in harassing behavior, the workshop organizers may take any action they deem appropriate, including warning or expelling the offender.&lt;/p&gt;
&lt;p&gt;If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact Scout or Ame, who will introduce themselves at the start of the workshop. We will work with you to take appropriate action, up to and including contacting venue security or local law enforcement if necessary. We value your attendance and want you to feel safe.&lt;/p&gt;
&lt;p&gt;We expect participants to follow these rules at the workshop and associated events.&lt;/p&gt;
&lt;p&gt;&lt;hr&gt;&lt;/p&gt;
&lt;h3 id=&#34;contact&#34;&gt;Contact&lt;/h3&gt;
&lt;p&gt;Questions? Concerns? Contact us at underexposed@superbloom.design.&lt;/p&gt;
&lt;p&gt;Photo &lt;a href=&#34;https://creativecommons.org/licenses/by/2.0/deed.en&#34;&gt;CC&lt;/a&gt;-licensed by Igor Ovsyannykov.
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
</description>
    </item>
    
    <item>
      <title>Unlock the Future of Civic Tech 🚀</title>
      <link>https://superbloom.design/civictech/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/civictech/</guid>
      <description>&lt;p&gt;Discover the innovations shaping our cities, governments, and communities. Civic tech is more than just a buzzword—it&amp;rsquo;s the key to a brighter, smarter, and more connected future.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Stay Ahead with Our Exclusive Updates&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Don&amp;rsquo;t miss out on the latest breakthroughs, trends, and product launches. By signing up for our newsletter, you’ll be at the forefront of the field.&lt;/p&gt;
&lt;h3 id=&#34;-why-join-our-community&#34;&gt;✨ Why Join Our Community?&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Exclusive Access  🎉:&lt;/strong&gt; Be the first to hear about the latest product launches and civic tech solutions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Insightful Analysis 💡 :&lt;/strong&gt; Dive deep into the trends and technologies making waves in the industry.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Global Perspective 🌐 :&lt;/strong&gt; Understand the impact of civic tech around the world.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;join-the-movement-shape-the-future&#34;&gt;Join the Movement. Shape the Future.&lt;/h3&gt;
&lt;p&gt;Be part of the community that’s paving the way for a more inclusive, transparent, and technologically advanced society.&lt;/p&gt;
&lt;p&gt;👉 &lt;strong&gt;Sign Up Now&lt;/strong&gt; and let the world of civic tech unfold in your inbox! 💌&lt;/p&gt;
&lt;div id=&#34;mc_embed_shell&#34;&gt;

  &lt;div id=&#34;mc_embed_signup&#34;&gt;
    &lt;form
      action=&#34;https://guide.us19.list-manage.com/subscribe/post?u=cdb853c4847acff0d0a09460d&amp;amp;id=ca5a70438b&amp;amp;f_id=00ae91e4f0&#34;
      method=&#34;post&#34; id=&#34;mc-embedded-subscribe-form&#34; name=&#34;mc-embedded-subscribe-form&#34; class=&#34;validate&#34; target=&#34;_blank&#34;&gt;
      &lt;div id=&#34;mc_embed_signup_scroll&#34;&gt;
        &lt;h4&gt;Get updates&lt;/h4&gt;
        &lt;div class=&#34;indicates-required&#34;&gt;&lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt; indicates required&lt;/div&gt;
        &lt;div class=&#34;mc-field-group&#34;&gt;&lt;label for=&#34;mce-EMAIL&#34;&gt;Email Address &lt;span class=&#34;asterisk&#34;&gt;*&lt;/span&gt;&lt;/label&gt;&lt;input
            type=&#34;email&#34; name=&#34;EMAIL&#34; class=&#34;required email&#34; id=&#34;mce-EMAIL&#34; required=&#34;&#34; value=&#34;&#34;&gt;&lt;span
            id=&#34;mce-EMAIL-HELPERTEXT&#34; class=&#34;helper_text&#34;&gt;Unsubscribe at any time&lt;/span&gt;&lt;/div&gt;
        &lt;div id=&#34;transition: all 0.23s ease-in-out 0s;&#34; class=&#34;clear&#34;&gt;
          &lt;div class=&#34;response&#34; id=&#34;mce-error-response&#34; style=&#34;display: none;&#34;&gt;&lt;/div&gt;
          &lt;div class=&#34;response&#34; id=&#34;mce-success-response&#34; style=&#34;display: none;&#34;&gt;&lt;/div&gt;
        &lt;/div&gt;
        &lt;div aria-hidden=&#34;true&#34; style=&#34;position: absolute; left: -5000px;&#34;&gt;&lt;input type=&#34;text&#34;
            name=&#34;b_cdb853c4847acff0d0a09460d_ca5a70438b&#34; tabindex=&#34;-1&#34; value=&#34;&#34;&gt;&lt;/div&gt;
        &lt;div class=&#34;clear&#34;&gt;&lt;input type=&#34;submit&#34; name=&#34;subscribe&#34; id=&#34;mc-embedded-subscribe&#34; class=&#34;button&#34;
            value=&#34;Subscribe&#34;&gt;&lt;/div&gt;
      &lt;/div&gt;
    &lt;/form&gt;
  &lt;/div&gt;
  &lt;script type=&#34;text/javascript&#34; src=&#34;//s3.amazonaws.com/downloads.mailchimp.com/js/mc-validate.js&#34;&gt;&lt;/script&gt;
  &lt;script
    type=&#34;text/javascript&#34;&gt;(function ($) { window.fnames = new Array(); window.ftypes = new Array(); fnames[0] = &#39;EMAIL&#39;; ftypes[0] = &#39;email&#39;; }(jQuery)); var $mcj = jQuery.noConflict(true);&lt;/script&gt;
&lt;/div&gt;
&lt;h5 id=&#34;explore-the-civic-tech-field-guide&#34;&gt;&lt;a href=&#34;https://civictech.guide/&#34;&gt;Explore the Civic Tech Field Guide&lt;/a&gt;&lt;/h5&gt;
</description>
    </item>
    
    <item>
      <title>usability</title>
      <link>https://superbloom.design/tags/usability/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/usability/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Usable Security Review</title>
      <link>https://superbloom.design/work/usable-security-audit/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/work/usable-security-audit/</guid>
      <description>&lt;p&gt;A Usable Security Review is a report to help a software team make its tool more usable and useful for its target users,
while at a minimum helping preserve – and ideally enhancing – privacy and security.&lt;/p&gt;
&lt;p&gt;We work closely with technical teams to craft an individual research plan that answers their questions and meets their
needs. However, this isn&amp;rsquo;t a security audit of your code - we evaluate privacy and security through the lens of user
experience and usability. We analyze what users see and do, so that we can make targeted recommendations for
improvements. A Usable Security Review is a complement to, not a replacement for, a comprehensive security audit of your
code.&lt;/p&gt;
&lt;h2 id=&#34;what-a-usable-security-review-includes&#34;&gt;What a Usable Security Review Includes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Understanding who are the tool’s desired, likely, and/or actual users (or “target” users)&lt;/li&gt;
&lt;li&gt;Understanding relevant threats (threats users are likely to face, threats that the tool seeks to mitigate, and threats
that the tool cannot mitigate against, but that users might expect it to)&lt;/li&gt;
&lt;li&gt;Analyzing the tool’s user experience heuristically (through an expert review)&lt;/li&gt;
&lt;li&gt;Analyzing the tool’s user experience empirically (through user studies)&lt;/li&gt;
&lt;li&gt;Making actionable recommendations to the software team to help them improve the tool’s design in response to review
and study results&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;phases-and-outputs&#34;&gt;Phases and Outputs&lt;/h2&gt;
&lt;h3 id=&#34;phase-1-understanding-the-background&#34;&gt;Phase 1: Understanding the Background&lt;/h3&gt;
&lt;p&gt;The first phase is to understand your tool&amp;rsquo;s background goals. This includes identifying the tool’s target users and its
threat model. It also includes understanding the tool’s position in its competitive landscape and the development team’s
priorities for UX improvement. Our steps are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Identifying target users&lt;/li&gt;
&lt;li&gt;Scoping threats&lt;/li&gt;
&lt;li&gt;Benchmarking and competitive analysis&lt;/li&gt;
&lt;li&gt;Evaluation priorities&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;phase-2-heuristic-evaluation-expert-review&#34;&gt;Phase 2: Heuristic Evaluation (expert review)&lt;/h3&gt;
&lt;p&gt;As well as experience in UX best practices, our evaluators understand the relevant security/privacy design patterns and
their common pitfalls. This expertise, and the ability to review the app in the context of background information about
the team&amp;rsquo;s and target users’ threat models, is what distinguishes a usable security review from a traditional UX review.&lt;/p&gt;
&lt;h3 id=&#34;phase-3-empirical-evaluation&#34;&gt;Phase 3: Empirical Evaluation&lt;/h3&gt;
&lt;p&gt;A key step in evaluating and improving a user experience is to put it in front of real users. Based on the questions the
software development team wants to answer, Simply Secure selects appropriate usability testing techniques. In a Usable
Security Review, our goal is to determine whether users accurately understand the threat model, and whether they can
perform key security-related tasks with comprehension. For example, it’s not enough for a user to be able to
successfully generate a key if she does not understand what that key is for or how she should manage it in the future.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Usability methods may include:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Cognitive walkthroughs&lt;/li&gt;
&lt;li&gt;Semi-structured or group interviews&lt;/li&gt;
&lt;li&gt;Task analysis&lt;/li&gt;
&lt;li&gt;Diary / prompted in situ studies&lt;/li&gt;
&lt;li&gt;Surveys or questionnaires&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Learn more in a report about our &lt;a href=&#34;https://superbloom.design/resources/techreports/InitialUsableSecurityAuditMethodology.pdf&#34;&gt;Usable Security Audit
Methodology&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>user research</title>
      <link>https://superbloom.design/tags/user-research/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/user-research/</guid>
      <description></description>
    </item>
    
    <item>
      <title>User Research</title>
      <link>https://superbloom.design/topics/user-research/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/user-research/</guid>
      <description></description>
    </item>
    
    <item>
      <title>user testing</title>
      <link>https://superbloom.design/tags/user-testing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/user-testing/</guid>
      <description></description>
    </item>
    
    <item>
      <title>ux</title>
      <link>https://superbloom.design/tags/ux/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/ux/</guid>
      <description></description>
    </item>
    
    <item>
      <title>UX Design</title>
      <link>https://superbloom.design/topics/ux-design/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/topics/ux-design/</guid>
      <description></description>
    </item>
    
    <item>
      <title>UX Patterns</title>
      <link>https://superbloom.design/learning/collections/ux-patterns/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/learning/collections/ux-patterns/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Valentina Pavel</title>
      <link>https://superbloom.design/about/people/valentina/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/valentina/</guid>
      <description>&lt;p&gt;Valentina Pavel is a legal adviser and a digital rights advocate focusing on privacy, freedom of speech and open culture. Currently she is a Mozilla Fellow, working with Privacy International as host organization, exploring concentration of corporate power or “digital feudalism” and the implications for privacy and data protection. Most recent work focuses on third party tracking.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Vanessa Rhinesmith</title>
      <link>https://superbloom.design/about/people/vanessa/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/vanessa/</guid>
      <description>&lt;p&gt;Vanessa Wrenn Rhinesmith (she/her/hers) is the Executive Director of the &lt;a href=&#34;https://www.c2i2.ucla.edu/&#34;&gt;UCLA Center for Critical Initiative (C2i2)&lt;/a&gt; where she also oversees the Minderoo Initiative on Technology and Power. Vanessa brings over 15 years of project, program, and strategy experience working with non profits, higher education institutions, and social entrepreneurs. She takes an approach to work that is rooted in critical inquiry, collaboration, and trust.&lt;/p&gt;
&lt;p&gt;Vanessa started her journey as a social worker in Chicago, Illinois before transitioning to work centered in purpose, community, and care in relation to intersectional feminism, harm reduction, and technology and society. Vanessa received her Masters in Business Administration (MBA) from Simmons School of Management (Massachusetts) with a focus on women* and org behavior.&lt;/p&gt;
&lt;p&gt;Vanessa continues to explore feminist approaches to cyber security and international relations; the role of history, narrative, and power in the creation of sex trafficking policies. She is currently cultivating a care network with and for women-identifying and gender nonconforming folx experiencing online and other forms of harassment in STEM. Vanessa has spoken at the University of Illinois at Urbana-Champaign, Simmons University, Harvard Kennedy School, South by Southwest (SXSW), the Nonprofit Technology Conference (NTEN), and more. Vanessa speaks, and facilitates conversations, on a variety of topics that include intersectional feminist approaches to data and digital technology; activism, advocacy, and stewardship; and community engagement.&lt;/p&gt;
&lt;p&gt;Vanessa is also the Event Producer of the Community Informatics Research Network (CIRN), annual research conference, and Review Editor for the Journal of Community Informatics (JoCI). She lives with her husband, child (they/them), and two cats. In her (little) free time, you’ll find her running, reading graphic novels, or scuba diving (post-pandemic).&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Veszna Wessenauer</title>
      <link>https://superbloom.design/about/people/veszna/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/veszna/</guid>
      <description>&lt;p&gt;Veszna is a human rights researcher by training, and has special interest in building a just digital future. She earned her MA in Human Rights from Central European University in Hungary and has worked with various NGOs and think tanks across the globe, including Democracy Reporting International, Political Capital, Global Voices, EU-Russia Civil Society Forum.&lt;/p&gt;
&lt;p&gt;Before joining Superbloom, Veszna worked for almost four years at Ranking Digital Rights as a program manager. She was responsible for the production of RDR Rankings and she also supported the process of developing new indicators addressing algorithmic systems and targeted advertising.&lt;/p&gt;
&lt;p&gt;In her downtime, she is with her son, helps build the Hungarian solidarity economy movement, and creates mixtapes for friends under her not-so-serious DJ alias, Venuscontroller. She is also a festival coordinator at UH Fest, a small music festival focusing on adventurous music.&lt;/p&gt;
&lt;p&gt;She is based in Budapest, Hungary.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Victory Brown</title>
      <link>https://superbloom.design/about/people/victory/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/victory/</guid>
      <description>&lt;p&gt;As a UX designer, Brown has worked on a variety of projects to improve user experience and usability in health tech, fintech, and even blockchain. She is passionate about content design advocacy, user-centered design, and open source. She is the community manager for the open source design Africa chapter and the founder of Dezignhers - a network of women inspired by design in her hometown in Nigeria.&lt;/p&gt;
&lt;p&gt;When she is not designing or advocating for open source, she writes content for web3 products and helps projects draft content that converts users. She is also a lover of communities, and is creative with community engagement strategies and social media engagement.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>video</title>
      <link>https://superbloom.design/formats/video/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/formats/video/</guid>
      <description></description>
    </item>
    
    <item>
      <title>visual</title>
      <link>https://superbloom.design/tags/visual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/visual/</guid>
      <description></description>
    </item>
    
    <item>
      <title>visual design</title>
      <link>https://superbloom.design/tags/visual-design/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/visual-design/</guid>
      <description></description>
    </item>
    
    <item>
      <title>website</title>
      <link>https://superbloom.design/tags/website/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/website/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Wendy Seltzer</title>
      <link>https://superbloom.design/about/people/wendy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/wendy/</guid>
      <description></description>
    </item>
    
    <item>
      <title>workshop</title>
      <link>https://superbloom.design/tags/workshop/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/tags/workshop/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Wrangelfilm</title>
      <link>https://superbloom.design/about/people/wrangelfilm/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/wrangelfilm/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Yasmina López Lluch</title>
      <link>https://superbloom.design/about/people/yasmina/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/about/people/yasmina/</guid>
      <description></description>
    </item>
    
    <item>
      <title>zine</title>
      <link>https://superbloom.design/formats/zine/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://superbloom.design/formats/zine/</guid>
      <description></description>
    </item>
    
  </channel>
</rss>
