top of page

We Default to Transparency

We “flip the bit” and justify opacity.

What this value means:

  • This does not mean everything is transparent. Some things are easy to justify as opaque, such as 1:1 meetings between manager and direct report.

  • What this does mean is that everything starts off as being transparent by default, instead of opaque or private by default. And the conversation we have as about justifying opacity, vs. justifying transparency.

    • You can think of this as whitelisting vs blacklisting -- everything starts on the white list

How to live this value:

Even/Over Statements for this value:

  • Open over Closed

  • @Mentions in Slack Group Chats over Slack Direct Messages

    • This also supports the I of ARCI (informing), efficiently communicating changes to all concerned parties

Putting it into action:

  • If you find yourself having a conversation that sounds like "Should we open up access to this document?", you’re not flipping the bit. The document should start as open, and the conversation should instead be, "Do we have good reasons to close access to this document? What are they? Are there any objections to scoping the access down to a smaller group?"

  • Share data among teams so everyone can make the best decisions

    • Make this data structured and accessible

  • We default to capturing internal meetings (audio and video), and then we decide whether we use them internally or externally

  • If you have a question and you’re not sure what to do, default to asking because others likely have the same question

    • We ask for the good of our Crew even if we feel embarrassed to do so

What this value doesn’t mean:

  • This doesn’t mean that all information is transparent — we just make choices (together) about what requires opacity

bottom of page