Keen is Joining the Scaleworks family

Today we’re excited to share that we’re starting a new chapter and joining the Scaleworks family.

Keen set out to empower developers with a custom analytics platform and the most seamless SaaS tool out there for data-handling. We created a periscope into user activity that we’re really proud of. We’ve helped companies easily build and embed all sorts of analytics for teams and customers, and we often power the dashboards in your favorite SaaS tools. It has been fulfilling knowing end-users rely on us for insights and that we help our customers make better decisions and build better products.

The Scaleworks team lives and breathes growing SaaS and has a great track record with businesses at our stage. They bring a ton of collective experience, and a focus on strategic direction, identifying and scaling efficiencies, specific innovation around market/customer demand, and business fundamentals. Given where we are and the path ahead, the combination just makes sense. There might be some things you’re wondering about. Yes, we’re going to continue to invest in product development, platform performance, and service levels. Our ethic around customer success remains as strong as ever, and is a core principle of Scaleworks’ also. Please let us know if you have any questions.

We’re thankful to the founding team that set the vision and got us here, and to our customers, and we now have our eyes on the future to take Keen to the next level. With an appreciation for what got Keen to where we are, we’re excited to fulfill Keen’s potential going forward.

Announcing: .NET Summer Hackfest

Keen IO is excited to be the first featured project in the first ever .NET Summer Hackfest! It’s coming up next Monday, July 24 and wraps up Friday, August 4th.

.NET Summer Hackfest is a six week community run open source hackfest. Teams are get together to contribute to open source projects for a two week session. It’s an opportunity to get involved in open source.

The main project is to work together to port our .NET SDK to .NET Standard 2.0. But we will also list various SDK improvements and example code projects if porting to .NET Standard 2.0 doesn’t sound like your cup of tea. We have projects and issues outlined in our GitHub repo along with contribution guidelines and information on how to get started. There’s also a slack channel, #dotnetsummer, in our Community Slack Chat ( and we’ll be there to hang out and talk shop the whole two weeks.

Check out the .NET Foundation’s announcement about our project!

There will be a kickoff post on the July 24th, and we’ll update this post with that info.

FYI* Contributors don’t need to commit to working the whole two weeks. We are designing this to be collaborative and hope that it’s educational and useful to anyone who gets involved. Please feel free to reach out on slack or twitter (@keen_io) with questions or suggestions.

Here’s a video walking through getting started setting up your .NET dev environment and contributing to the project:

Happy Hacking.

Keen IO .NET SDK on GitHub


Happy Data Hour with Readme and Keen IO

Free on July 20th? Keen IO and will be having a casual drinkup at from 5:30–7:30 PM, and we’d love you to join us!

Chat data, startups, and community, tell us what you really think about our services, or just swing by and hang a bit.

Please RSVP here if you’re coming. Let us know how many people to plan for. See you there!


Join us for Happy Data Hour!

Below is some nerdy JSON which probably looks terrible on your mobile device :)

   “event”: {
   “name”: “Happy Data Hour”,
   “type”: “meetup”,
   “pretty_timestamp”: “July 20th, 5:00pm-7:00pm (PST)”,
   “location”: {
      “street_address”: “”,
      “city”:”San Francisco”,
      “zip_code”: “94103”,
      “special instructions”: “ Featuring data and community members from Keen IO and ReadMe!”
   “beverages”: true,
   “host”: “Keen IO &”

Creative Code and APIs at Twilio's SIGNAL

Last week I attended SIGNAL, the developer conference by Twilio, with the Keen IO team. I’m happy to say that Twilio has figured out the art of conferences.

Developer conferences are a weird thing. They are a mystical form of art consisting of education, social interaction, and celebration. Some are amazing, others are just good, and some gain whispers across sponsors for how bad they are yet somehow still manage to happen every year.

I was impressed by how Twilio created a conference for everyone, and as a developer I felt right at home.

Why was SIGNAL awesome?

I could talk about a lot of different things: the live coding, great conversations, hackable badges, generally awesome talks around communication and code that were relevant to anyone, and much more. But I want to focus on two ideas that I saw a lot of at the conference:

  • Code is creative
  • How does this relate to APIs’ role in this rapidly changing world?

These were ideas that Jeff Lawson, CEO and co-founder, brought up very early on:

As Lawson said, the Hollywood narrative of a “hacker” is broken. It ignores that there is more than just math to coding. Coding is an art. It wasn’t just all talk too. I continually saw it in talks at the conference.

Code is creative

It was really hard to pick just a few talks that I thought highlighted how code is creative, but here’s a few of them:

Rachel Simone Weil’s talk “Hertzian Tales: Adventures in “Useless” Hacking”

Rachel really digs into a question that many of us have when we hack and build projects that will never be a “business.” While some of the hacking could be considered “useless,” she touches on the real benefits of creative projects from a critical design lens.

Jenn Schiffer’s talk “What If Twilio Could…” A Tale of Glitch, Twilio, and the Power of Friendship”

If you haven’t gotten to listen to a talk from Jenn, you should! In this talk, Jenn and a friend worked on coming up with a bunch of creative and random ideas based the prompt “What if Twilio Could…” They were able to be more creative by relying on APIs and not worrying about if it was technically possible. Jenn digs into some critical questions, such as, how do we keep the “a-ha moment” going when we have these creative ideas? And how do we work with people while building and learning new things?

Lauren Leto’s talk “At-Home Batphone: The Future of Phone Numbers and Noble MVNOs”

Can you imagine a world where you never need to check your phone and the messages that need to get to you do? Lauren is building for that future with APIs, like Twilio. I love this one quote from the talk:

“When anyone can do it, there’s more chance for creativity.
Andrew Reitano’s talk “NESpectre: The Massively Multi-Haunted NES” and Dan Gorelick’s talk “Crowdsourcing Music via WebSockets: Using Scalable Technologies to Enable Musical Expression”

These last two talks really highlighted interdisciplinary creativity. While I strongly believe all code is interdisciplinary, these two took it to another extreme. Also, I played games and music with 60+ other people in the room while watching these talks, which was freaking awesome!

One other thing about these two talks is that they had nothing to do with Twilio, which I thought was great. Twilio put developers first by choosing to educate attendees on creative and interesting uses of technology over their own API.

How do APIs come into play with this creativity?

As some of the speakers touched on, APIs open up opportunities. When you get to focus on being creative instead of on whether something is technically challenging or possible, what you make with the code is more creative.

Lawson asked questions in the keynote like, how many business problems are there that we could be solving if we had the right APIs first to solve them? And why isn’t that an API?


When dealing with inflexible legacy systems, we don’t always get to solve the most creative problems. APIs allow us to apply our creative energy on a whole new set of problems waiting to be solved.

Lawson also asked, “How big can this economy get?” This really turns into a question for developers. When we are creative, what are the limits with building with APIs? At Keen IO, we are still pushing those limits today while we explore the possibilities that are part of an Unstoppable API Era.

It is common to say that software is eating the world, but in many ways APIs are eating the world.

Our own API stories

Many of us have our own API stories. Suz Hinton mentioned in her talk about immersive experiences with Chat Bots +IRL Bots that many of us, including herself, have a “Twilio Story.” This idea came up constantly at the conference.

For example, my own “Twilio Story” is that the Twilio API Docs helped me get interested in web development. Previously, I had been writing Java and C++ programs that were completely disconnected from the Internet. The Twilio API Docs helped me setup my first web server, a Python Flask server, in order to send a text message for a project I was working on. This was a life changing experience for me.

Paul Fenwick’s first Hello World experience with Twilio turned into building the National Rick Astley Hotline and then he gave an awesome talk about it at Signal! Basically, he knew nothing about the technology, but because the APIs and technology existed, he was able to focus on the creative use case first.

A conference for everyone

Lastly, the last part of conference is usually the “celebration.” Twilio calls their conference after party, $bash. (Feel free to insert your own bash jokes here.) I’d say that Twilio sprinkled celebration into a lot of parts of the conference, but this is where it was at its greatest.

Photo booths + Face paint artists = 💖

I was definitely unsure about this celebration though. When someone tells you that there are going to be “coding challenges” and “puzzles” in a dark environment with lasers, loud music, and alcohol in a warehouse on a pier in San Francisco, you can’t blame me for being slightly pessimistic about how “fun” it will be.

I quickly realized that there was really something for anyone at $bash. If “coding challenges” weren’t your thing, there was half a dozen other things you could do instead. That’s why $bash was special to me. As an introvert, who really likes conferences yet is exhausted at the end of them, after parties aren’t always my idea of “fun.” It even got two of our co-founders to stick around and try out the coding challenges.

As Kyle Wild, our CEO, said:

“Signal was like a case study in how to make a conference for introverts. I ❤❤❤❤ it and want to go back every year.”

Congrats on finding the right mixture of mystical conference art, Twilio! See you next year.

P.S. At SIGNAL, we also announced our partnership with Twilio to provide Contact Center Analytics. Check out our blog post about analytics with the TaskRouter API:

Twilio’s Al Cook using multiple APIs including TaskRouter API and Keen IO to build Contact Center Analytics, see the talk here.

P.P.S. I highly recommend going to check out some of the talks I shared. If you loved those, here are a few more favorites:

From left to right: The Democratization of State: How exposing real-time state can improve your business, Lucky: Examining the Barriers to Contributing to Open Source
From left to right: Coding for a Cause: SMS for Voter Registration, and Build Twilio Apps That Scale to the Moon

If you think “Code is Creative” or the talks that were included are awesome, consider clicking the ❤ below!

Join Us at Twilio for Happy API Hour


Twilio’s Signal Conference 2017 is just around the corner! We’re excited to meet thousands of fellow developers in San Francisco for 2 days of talks, panels, events, knowledge sharing, and fun. Come visit us at booth number i2 to say hi, get some sweet swag, give us a hi-five, ask questions about APIs, or get a sneak peak of our latest product collaboration with Twilio.📊

On the evening of Wednesday, May 24th Keen IO is co-hosting a Happy API Hour with our friends at Auth0 and Algolia. Join us for an evening of networking and hanging out with plenty of food, beer, wine, and refreshments. Space is limited so help us out by making sure to register early with the link below:



Happy Hour Event Details

Where: Rogue Ales Public House, 673 Union Street, San Francisco, CA 94133

When: May 24, 2017 at 7:30pm — 9:30pm

What: Happy Hour/afterparty, space is limited!

How: RSVP on Eventbrite to reserve your spot


About our Co-Sponsors

Algolia helps developers connect their users with what matters most. Their hosted search API powers billions of queries for thousands of websites & mobile applications every month, delivering relevant results in an as-you-type search experience in under 100ms anywhere in the world. Algolia’s full-stack solution takes the pain out of building search; we maintain the infrastructure & the engine, and we provide extensive documentations to our dozens of up-to-date API clients and SDKs with all the latest search features, so you can focus on delighting your users.

Auth0 provides frictionless authentication and authorization for developers. The company makes it easy for developers to implement the most complex identity solution for their web, mobile and internal applications. Ultimately Auth0 allows developers to control how a person’s identity is used with the goal of making the internet safer.

About ourselves — Over 60,000 developers use Keen IO APIs to capture, analyze, and embed event data into their tools and products. Thousands of customers rely on Keen’s event data platform to white label data applications in media, e-commerce, adTech, gaming, IoT and retail. Keen’s customers query trillions of data points daily. Keen IO also values and promotes empathy, introspection, distributed innovation, continuous learning, playing to your strengths, and patching your weaknesses with diverse collaborators.


shhh… we may or may not have VIP wristbands for the happy hour event at our booth i2!

See you there at the afterparty + Twilio Signal!

The Future of History

Photo of Anna Fisher by John Bryson, Life Magazine, May 1985

Brahe & Kepler

When people ask me why we wanted to start Keen, I tell them this story of two scientists.

Tycho Brahe by Eduard Ender (1822–1883)

Tycho Brahe was a Danish astronomer in the 16th century. You probably haven’t heard of him. He wasn’t a great physicist or mathematician, but he had a really important insight, which was that the astronomers of the day were spending a lot of time working with really bad data. The data was longitudinally large (hundreds of years of star charts, handed down through the ages), but crappy. Brahe realized that he couldn’t draw useful conclusions from poor data, so his first step was to re-instrument the universe with the right data model. In each of his nightly “data snapshots,” Brahe wanted to document the position, motion, and brightness of every single celestial object in the sky.

To accomplish this, Brahe built several versions of his own observatory from scratch. He built all his own instruments, and he kept such extensive records that he even built his own paper mill just to keep up — data storage wasn’t quite as cheap back then as it is today. And after sacrificing much of his fortune (plus over 30 years of nightlife), he suddenly died.

Tycho Brahe’s Uraniborg from Brahe’s book Astronomiae instauratae mechanica (1598)

Luckily he had an assistant named Johannes Kepler. You probably have heard of him. Kepler spent over 20 years running calculations on Brahe’s data. In the end, he devised the laws of planetary motion, which inspired the work of Newton and Einstein and the foundation of modern physics.

According to NASA, Kepler’s work “launched the scientific revolution.”

Historical data not only helps us study the past, but it allows us to figure out the laws of our universe, which provide our only glimpses into the future. Powerful stuff, that historical data!

Left: Brahe’s star data. Right: NASA’s modern view of space.

The Digital Observatory

Brahe was always the person in this story that stood out to me. He wasn’t a scientific genius and isn’t remembered by very many people, but in my book he was every bit as impactful as the famous Kepler (moreso, even — many Kepler-level thinkers had probably come and gone, but it wasn’t til one worked with Brahe that things fundamentally changed).

Brahe, armed with a custom-built observatory, was just a really practical, methodical, large-scale record-keeper — with high standards for precision and a very broad data model.

That’s pretty much what Keen is, too.

Keen is the modern observatory for the digital universe. The trillions of data points our customers are collecting will be the foundation for their future discoveries.

Cerro Tololo Inter-American Observatory in Chile. Credit: Abbott and NOAO/AURA/NSF

Observatory Design Considerations

The most important factors in building a good observatory are:

  1. the field of view
  2. the precision of the instrumentation
  3. the breadth of the data model

Beyond that, the most important factors for making those future discoveries more likely are the portability and the accessibility of the data.

Humanity was lucky that Kepler happened to work onsite with Brahe, because physical reams of paper aren’t all that portable.

Fortunately, thanks to the Internet, a modern observatory could transcend such physical barriers. Imagine a cloud API that modern Brahe-like people can use to measure their worlds. And every one of those Brahe-like people would be able to expose their data to far more than one Kepler-like person.

Logical map of ARPANET, which eventually became the The Internet


These concepts of portability and accessibility are the reason we took an API-first approach to designing Keen.

In data systems generally:

Portability is high if I can get all or some of the data into other systems easily, and higher still if the form of those other systems can be arbitrary. The highest level of portability in a data system would be an API for extracting full-resolution chunks of the data, combined with an API for streaming the data out wholesale.

Accessibility of the data is higher through a Twilio-inspired REST API like Keen Compute versus, say, a giant and arcane data lake stored in SAP or Oracle or HBase or Teradata. In the latter, the data is guarded by a department full of data adepts, who require lots of meetings before maybe choosing to spend months of magician-time to give you an answer. In those sorts of systems, the API to get to that data is meetings + corporate politics + waiting around. The API into Keen data is, errr, an actual API.

This is nice for humans who want answers, but it’s even nicer for applications that want answers, since applications can’t have meetings or play politics. All they can really do is use APIs.

To put it another way, a well-abstracted REST API provides extremely high data accessibility to anything connected to the internet. When developers use those APIs to build data into software, we can achieve an even higher level of information accessibility. The beauty of making data-powered applications is that developers can put data into the hands of ordinary people. They don’t have to be Keplers.

Software Developers

As Marc Andreessen famously wrote, software is eating the world. What he really meant is that software is taking over the economy. Yes, leave it to a VC to accidentally conflate the economy with the whole world — but still, his point has merit.

Building of the Golden Gate Bridge in San Francisco. Source.

If he’s right, then that means software developers will have an enormous responsibility in architecting the future economy. Developers will be its carpenters, its plumbers, its masons, its general contractors, its architects. They will build its bridges, its cities, its transportation systems, and its parks. Developers will build an increasing percentage of everything, and build into everything.

And increasingly, developers will choose which tools & technologies they build it with.

The things (products, apps, businesses) they build will be increasingly intelligent, in a variety of ways. One of those ways is that these things will have a sense of history. You might call them “history-aware products” or “history-aware applications” or “history-aware businesses.”

A Sense of History

Imagine you’re a software application.

You’re a bunch of bits of code and logic, creating and consuming an intricate symphony of information.

Got it? Good.

Now, what would it mean for you to have a sense of history? To be history-aware?

In my view, it doesn’t merely mean that you have a good memory, although that’s important. A good memory means you’re aware of — and can recall — what’s happened in the past. A perfect memory would allow you to instantly recall arbitrary facts in perfect detail.

Imagine you (the application) are running on a Fitbit in the year 2020. Every Fitbit in the world is running one of your brothers or sisters. Perfect memory would mean you know the answer to questions like these: What was the 90th percentile heart-rate of audience members during that one perfect scene in that one amazing horror movie? Was it different depending on time of day? On which theater they were watching in? On how much alcohol they had consumed beforehand?

Perfect memory alone is clearly powerful. And being able to access your entire tribe’s perfect memory just by issuing an API call is a superpower. As an application, calling an API is as trivial for you as it would be for a human to speak a word of English.

But to be history-aware isn’t just about knowing what happened in the past. More broadly, it means you’re aware that history exists as a concept.

The 10,000 year clock. Source: The Long Now Foundation

What would it mean for you, the software application, to be history-aware in this way?

Not only would you remember all the events that happened previously and be able to run calculations across them, but that you would record your own observations in detail (like Brahe), so that in the future, other history-aware applications (including yourself in a future timeline!) can possess that same kind of perfect memory. For its members to have perfect memory, the entire tribe has to diligently record events as they pass.

Being a smart citizen means being aware of the history that’s already occurred. Being a good citizen means being history-aware in this broader context.

If you were a software application, this is a superpower you would probably find compelling.

Looking Forward

Much of the future economy will be built by developers. With great data tools and a sense of history, developers will not only make us contextually smarter, they will lay a foundation for ongoing discovery.

At Keen, our mission is to provide a ready-made digital observatory so that they don’t have to spend years building one like Brahe did.

The future is a place where anyone can study their universe or, like NASA did when they took Keen for a one-day spin, discover a pattern that has been eluding them for over a decade.

(And I think Kepler would find that pretty rad.)

Thanks to Michelle Wetzler, Micah Wolfe, Patrick Woods, Seth Bindernagel, Ursula Ayrout, inconshreveable, Sunil Dhaliwal, Ryan Spraetz, and Elias Bizannes for editing help.

Interview with Michael Greer (CTO, TAPP TV, The Onion)

We recently interviewed Michael Greer, former CTO of The Onion and now Co-Founder and CTO of TAPP TV. We wanted to hear how he navigated the decision to build or buy analytics infrastructure.

In our CTO’s Guide to Getting Data Strategy Right white paper, we discuss the limitations of off-the-shelf analytics solutions, as well as the risks of building custom solutions with expensive internal resources. As we continue to navigate these discussions with our clients at Keen, we wanted to share some of their stories. TAPP decided to build their analytics capabilities in-house using Keen’s APIs, and they have been a Keen customer for several years.

According to Mike, his team of engineers has tested a variety of approaches including combinations of Segment, KissMetrics, and Google AdWords. “The reason we ended up increasingly relying on Keen was our ability to influence the metrics we were tracking with Keen — it turned out to be more engineer-friendly than anything else on the market,” says Greer.

TAPP uses a video content management system and a subscription system to allow their team to manage different video sites. These systems are also used for various internal dashboards and reporting on key business metrics. For example, reports embedded within the CMS help employees identify the most popular content, compare subscription rates across time or make revenue projections. “We run correlations, track whether users are more or less likely to subscribe when they look at a particular content piece, and much more,” explains Mike.

When asked how Mike would explain Keen’s API platform he says,

“Keen is the perfect 80% solution. It’s not turnkey and doesn’t give developers anything out of the box, but rather offers 80 percent of what’s needed and allows a company to build what they need, quickly.”

TAPP’s team also found Keen’s engineers and customer success team to be extremely helpful.

“I simply contact Keen’s customer service via chat. Engineers send us back example code which is extremely high quality. I’ve also reached out directly to the engineers who maintain the JavaScript library, so we could really see what was happening.”

Mike Greer found Keen’s pricing and platform to be easy to scale with the company’s needs.” TAPP currently has over 30 people across the company consuming data in a variety of custom dashboards and reports specific to their workflows, all of which is maintained part-time by a small team of three.

Another consideration for the executive team was the investment risk inherent in choosing a technology for such a foundational, business-critical need (and in particular one that touches many parts of the business). Two factors influenced their decision here: Keen’s high data-portability reduced their lock-in risk, and the flexibility of the platform meant they weren’t married to a single prescriptive way of doing analytics.

“Keen is a platform that’s been created by builders for builders.”

Mike cited a few additional factors that made the choice to build his analytics infrastructure on Keen the most viable for TAPP:

  • Keen has great JavaScript SDKs so it works well with their stack
  • Emergent questions from company stakeholders are very easy to answer: “Keen is sufficiently flexible for us to always be able to offer additional capabilities”;
  • A much lighter burden for the engineering team: TAPP runs their entire analytics stack with no full-time headcount dedicated to analytics infrastructure and scalability.
  • New dashboars can be added on demand. This makes it easy to add and remove key metrics as needed.

Download our latest white paper to learn more about the “Build vs. Buy” debate. Keen IO helps companies accelerate deployment of intelligent data applications and embed intelligence throughout their business.

Announcing our new podcast: Data Science Storytime!


We’re excited to announce the debut of Data Science Storytime, a podcast all about data, science, stories, and time.

In Episode 1, Kyle Wild (Keen IO Co-founder and CEO) and I brainstorm the concept of the show, debate the difference between data science and non-data science, and recount the story of the action-hero data scientist who skipped a meeting with Kyle to rescue a little girl trapped on a mountain (or so he assumes).

Tune in for all this and plenty more as we consider the many ways data shapes our lives and activates our imagination, today and in the future.

If you like what you hear, make sure to subscribe to get a new episode every two weeks. And follow us on Twitter @dsstorytime. Thanks, and enjoy the show!

An Open Source Conversation with OpenAQ


Last month, I sat down with Christa Hasenkopf and Joe Flasher from OpenAQ, one of the first open, real-time, air quality data platforms to talk about open environmental data, community building, analytics, and open source. I hope you enjoy the interview!

Taylor: Could you both tell me a little bit about yourselves, and how y’all got interested in environmental data?

Christa: I’m an atmospheric scientist, and my background for my doctoral work was on ‘air quality’ on a moon of Saturn, Titan. As I progressed through my career, I got more interested in air pollution here on Earth, and realized I could apply the same skills I’d gained in my graduate training to do something more Earth-centric.

That took Joe, my husband, and I to Mongolia, where I was doing research in one of the most polluted places in the world: Ulaanbaatar, Mongolia. As a side project, Joe and I worked together with colleagues at the National University of Mongolia to launch a little open air quality data project that measured air quality and then sent out the data automatically to Twitter and Facebook. It was such a simple thing, but the impact of that work felt way more significant to me than my research. It also seemed more impactful to the community we were in, and that experience led us down this path of being interested in open-air quality across the world. As we later realized, there are about 5–8 million air quality data points produced each day around the world by official or government-level entities in disparate and sometimes temporary forms but that aren’t easily accessible in aggregate.

Joe: I was a trained as an astrophysicist but then I quickly moved into software development and so when Christa and I were living in Mongolia, I think we just sort of looked around and saw things that didn’t exist that we could make, we went ahead and did that. Open data was always something that seemed like the right thing to do. Especially when it’s data that affects everyone, like air quality data. I think we have the tools together: I had the software development skills and Christa with atmospheric science to put things in place that could really help people.

Taylor: That’s awesome. Could you tell me more about the OpenAQ Project?

Christa: Basically what we do is we aggregate air quality data from across the world and put it one format in one place, so that anyone can access that data. And the reason we do that is because there is still a huge access gap between all of the real-time air quality data publicly produced across the world and the many sectors for the public good that could use these data. Sectors like: public health research or policy applications, or an app developer who wants to make an app of global air quality data. Or say even a low cost-sensor group that wants to measure indoor air quality and also know what the outdoor air quality is like so you know when to open your windows if you live in a place like Dhaka, Bangladesh or Beijing, China. And so by putting the data in this universal format, many people can do all kinds of things with them.

Joe: Yeah, I think we’re just focused on two things. One is getting all the underlying air quality data collected in one place and making it accessible, and the main way to do that is with an API that people can build upon. And then we also have some of these other tools that Christa mentioned to help groups examine the data and look at the data, but meshing that with tools built by people in the community. Because I think the chances of building the best thing right away is very small. What we’re trying to do is make the data openly available to as many people as possible. Because a lot of these solutions are based in local context in a community.

Taylor: That’s really cool. I have heard from other organizations that when you open up the data, you democratize the data because it’s available for the people.

I read the Community Impact document for the project and you had mentioned that some researchers from NASA and NSF and UNICEF are using the data from OpenAQ. I was wondering, what are some other cool applications of the data that you are seeing?

Christa: I think when we first started the project it was all about the data. It was all about collecting the data, getting as much data as we could. And as we went on, we realized, pretty quickly, it’s actually about the community we are building around it and the stuff that people are building. And so there are a few different pieces.

One thing we have seen is a journalist taking OpenAQ-aggregated data to analyze air quality data in their local communities. There is a journalist in Ulaanbaatar, Mongolia, who has published a few data-driven articles about air quality in Ulaanbaatar relative to Beijing. There are some developers who have built packages that make the data more accessible to people using different programming languages.

There is a statistician in Barcelona, Spain, who has built a package in R that makes the data very accessible in R and makes cool visualizations. This person made a visualization where she analyzed fireworks across the US on the Fourth of July. She did a time series, and you could see a map of the US, and as 9pm rolled around in the various time zones you can see air quality change across the US as the fireworks went off.

There is a developer in New Delhi, India, who has made a global air quality app and Facebook bot that compares air quality in New Delhi to other places or will send you alerts. We feel these usages point to the power of democratizing data. No one person or one entity can come up with all the possible use-cases themselves, but when it’s put out there in a global basis, you’re not sure where it’s going to go.

Joe: We have also been used by some commercial entities to do weather modeling, pollution forecasting. Christa, there was an education use case right… Was it Purdue?

Christa: Yeah, a professor there is using it for his classroom to bring in outdoor air quality data to indoor air quality models. Students pick a place around the world. They use outdoor quality data from there to model what indoor air quality would look like, so they are not just modelling air quality data in Seattle, which is pretty good air quality. But they are also pulling in places like Jakarta or Dhaka, to see what air quality would be like indoors, based on the outdoor parameters.

Low cost sensor groups have contacted us because they are interested in getting their air quality data shared on our platform. These groups would like their data to be accessible in universal ways so that more people can do cool stuff with it too. Right now, for our platform, we have government-level data, some research-grade data, and a future direction we are hoping to move is low-cost sensors, too.

Taylor: As you have touched on, I read that OpenAQ has community members over four continents and aggregated 16 million data points from 24 countries. I am curious, how were you able to grow the project to have all that data coming in?

Christa: We have a couple ways of getting the word out about OpenAQ and getting people interested in their local community and to engage with the OpenAQ global community. One way is we do in-person. We visit places that are facing what our community calls “air-inequality” — extremely poor air quality in a given location — and we have a workshop that will convene various people, not just scientists, not just software developers, but also artists, policy makers, people working in air quality monitoring within a given government, and educators. We focus on getting them all in the same room, working on ways they can use open data to advance fighting air inequality in their area.

So far, we’ve held a workshop in Ulaanbaatar, and we have had meetups in San Francisco and DC, since that’s where we’re based. We have also done presentations in the UK, Spain, and Italy. We are about to have our next work shop in Delhi in November. We’re getting the word out through the workshops, the meetups, on Twitter, we have a slack channel. Participation in the OpenAQ Community has been growing organically in terms of participation. Whether it’s in terms of the development end, pulling in more data, or in the application of the data. We tend to get more people interested in using the data once they are aggregated rather than in those helping to build ways to add in more data, which makes sense. We are always in need of more people helping on helping build and improve the platform.

Joe: In the beginning it was very interesting how we decided to add in new sources — there are so many possible ones to add from different places. You could look at a map and see where we had been, because whenever we would go somewhere to give a presentation we would want to make sure we had local air quality data. So before we would give a presentation in the UK, we would make sure we had some UK data. Data has been added like that and according to interest for particular locations in the community.

An interesting thing that we are able to do now with the Keen analytics, is that we can look at what data people are requesting most, and even if we don’t have the data, they might still be requesting it. So we can see from the analytics where we should potentially focus on bringing in new data. So it has been a very helpful way for us to be more data-driven when looking at what data to bring in.

Taylor: When you have a project that is an open source or an open data platform, your time becomes very valuable. You want to put your resources where they are needed most.

Joe: We want to be as data-driven as possible. And it’s hard for us to talk directly to all of the people who are using the data. I think we have a similar problem to anyone who opens up data completely. We don’t require anyone to sign up for anything. We have a lot more people using the data than we know about. We can see just from how many times the data is getting grabbed that it is popular. The analytics really help us, sort of tell something about those use cases, even if we don’t know of them specifically.

Taylor: Could you explain your use of Keen for everyone so they can understand how you are figuring that out?

Joe: The API is powered by a Node.js application that includes the Keen library. Every request that comes in goes to Keen and so we have a way to sift through it.

We don’t track any use, any sign ups, any API keys or anything at the moment. We don’t see addresses that come in from the requests, they are anonymous. But we do get tons of data that we can look through. And that was super-helpful. It gave me two lines of code that go into my API and then all my requests come into Keen and I can handle all the queries there.

We do all the normal things that you would do: total counts of requests that are coming in, we look at our end points usage statistics. This is also very interesting, we were looking at this the other day, not all our endpoints are equal and our system has some that are much heavier computationally and have taken a lot more work to create. It’s interesting to look at how much they are getting hit versus how much effort we put into making them. We can see the most popular endpoints that we have, and then we can also see ones that aren’t used as much. This helps me figure out what and how to prioritize efforts. We have a very database request heavy system. Knowing specifically the sort of queries that are coming in really helps us optimize the database to get the most out of it and make it most cost efficient.

Taylor: That’s interesting that you were able to gauge how much effort you put into some of those endpoints and then look their usage. When you don’t have that data, you are just guessing. It can also help you see that maybe there should be more education on some endpoints.

Why was it important to y’all for this platform to be open source?

Christa: So one of the major reasons we built this platform and made it open source is that we noticed a few of the groups who were gathering this sort of data and the data themselves weren’t open, nor was it clear how they were gathered. There was a few efforts, some commercial, some unclear if they were commercial or public, there were some researchers who do this. And everyone was doing it in a different way or wasn’t entirely clear how it was being done. We saw a lot of efforts having to duplicate what another effort was doing because their work wasn’t open. So we thought if someone just makes the data open and also the platform itself open source and transparent, so it’s clear how we’re grabbing the data — that’s a huge reason to do it. The other reason we chose, was that when we first started this, there was just two of us in our little basement apartment. It’s a big project, and we knew we would need help. So making it open source was an obvious route to find folks interested in helping us around the world.

Joe: I think the other piece here is that open source and free aren’t the same thing. But they are often times lumped together. Beyond just open source, I think what we wanted to be was freely available, because air pollution disproportionately affects people in developing countries. They are the ones that would generally have to pay for this data or don’t have access to them at all. And so we wanted to break down that barrier and let everyone have access to the data, making tools, and not have that be a roadblock.

Taylor: To end things, what is the most exciting thing about the project to each of y’all?

Christa: I think for me it’s definitely interacting with people in specific communities and sharing the data in the open. I love that, it’s the best.

Joe: For me it is definitely having people build something on top of it. As a developer, that’s the best feeling. In fact the first workshop we did in Mongolia, there was a developer who, just over the weekend, built an interface, like a much better exploration interface for the data than what I had initially made. Which was great, right? So I think we used that, and pointed people to that over and over and over again, because I think it took us probably, I don’t know, six months until we finally rolled out sort of a different exploration interface for the data. And that was just made by one community member and that was awesome.

I wanted to thank Christa and Joe for taking the time to talk to me about OpenAQ. I don’t know about you, but I learned a lot! It is a wonderful project that you should definitely check out.


Keen IO has an open source software discount that is available to any open source or open data project. We’d love to hear more about your project of any size and share more details about the discount. We’d especially like to hear about how you are using Keen IO or any analytics within your project. Please feel free to reach out to for more info.

Six Steps to Building Successful Customer Relationships


Analytics is a complex beast. When you think about everything you want to build and track, it’s easy to get carried away. That’s why at Keen, we created a API-based platform with tools that make creating something from nothing much easier. Instead of doing it alone, let’s build together!

Last year we expanded from a self-service tool to an enterprise product serving large organizations with increasingly complex needs. In addition to advanced features, we also added hands-on help and organizational planning with the Customer Success Team.

As we’ve worked with bigger and bigger organizations, we’ve found the following framework to be really valuable.

1. Evaluate your customer’s needs

This may seem obvious but asking the most basic questions is really important. Before you take a step forward, take the time to ask meaningful questions about your customer’s business.

At root, what are you trying to accomplish? And how can you work together to meet these goals?

It’s easy to get carried away with all the things that are possible, but getting mired in details that are not mission critical takes attention away from the primary goals. Remember to stay focused on why your product is needed.

This shift in the conversation from the “nice-to-haves” to primary business goals helps identify which tasks might not be effective/good uses of effort. By using this focus, you can drive home and highlight the core value proposition of your service. In our case at Keen IO: analytics.

By making sure our customers understand what we’re good at — delivering a stable platform for data ingestion, analysis, and visualization — we can continue to showcase the progress they’ve accomplished in a short amount of time, the good work they’re continuing to accomplish, and then coincidentally how good of a job we are doing as their platform provider.

2. Stay Organized

When we work on customer integrations, staying organized is crucial. A Gantt Chart or Project Plan is my preferred method of staying on top of my delivery timeline and critical deadlines. This shared view helps the customer stay abreast of expected timelines, and avoid any misunderstandings in communication.


Sample Project Overview

Don’t skip this important step: Communicate timelines for when you are going to do something.

Nothing is more frustrating that making a request to a team and getting no response. Respond quickly if even just to say “I’m looking into it.” Some answers may take longer than others to reply to, and some customer requests may not be completed overnight. Providing a timeline is providing a reasonable expectation, and communicating this information in a structured way is key.

3. Maintain regular communication

When your product evolves to include new features that may be helpful, remember to let your customers know.

I tend to write frank and friendly emails to describe new feature sets and partnerships, and at times I also send along blog articles written by our team. It always feels good to find out about a change to something you’re used to or something completely new. Feature announcements have been a way for our customers to share excitement for what is upcoming for Keen.

Don’t be shy about advocating your own product’s features and regularly. By recommending use of unused or newer features, you can help your customer figure out how they can be using your technology better. There may be a more efficient or effective way to do what they’re doing.

Plus, by keeping in touch and knowing what our customers are trying to do, we can share lessons from customers doing similar things. It gives us the opportunity to reassure customers, remind them that they’re not alone in thinking about a problem in a particular way, and that they’ve chosen the right approach and technical solution for their project.

I make it a point to share helpful solutions with customers even when they don’t directly involve our product. A conversation like this has the added benefit of letting your customer know you’re available to bounce ideas off of.

Even when there’s bad news, we’ve found that customers are very appreciative when they receive a message directly from us. They appreciate the personal message and helps to receive a heads-up from you before finding out about a patch or planned downtime from anywhere else.

An added bonus of staying in touch and updating customers on your product’s best practices is that you can protect your operational teams from suboptimal customer usage patterns that can become stressful or expensive in the long term.

4. Periodically recheck goals

To keep abreast of your customers’ day-to-day operational needs and stay relevant to their business, it helps to establish periodic check-ins. At Keen we do these on a quarterly basis.

Each quarter we run an in-depth integration analysis and spend time doing a business review with our customers. Sometimes, this turns out to be a big investment of time. So why do we do this?

For one thing, it feels good to help customers succeed. But also, our customers’ success is our success. In the long run, we’ve found that the customers we’ve helped attain their own success tend to recommend Keen IO to others.

When we help customers achieve their current business goals, we build trust with them. It makes the organizations and companies we work with more likely to continue the relationship and build more integrations on top of Keen.

5. Include the customer in the product feedback loop

We share our product roadmap with our customers and actively ask what our platform’s current limitations are. Including our customers in the Product Roadmap, and allowing their input to drive the future of Keen’s product is core to our methodology for success!

As members of the Customer Success team, we become experts on the best ways to use Keen. In the process of collecting genuine customer input and bringing our customers up to speed on what’s next, we’ve gained valuable data on how to help future customers undergoing integrations too!

At times, building a requested piece of technology to help one specific customer’s goal in our platform has led to creating new product that has allowed all of our customers realize benefits.

In these Product Roadmap Sessions with our Chief of Product, our customers have even shared with us amazing tools they’re proud of and have spent time building on top of our open source toolsets. These have become fantastic opportunities to cross-promote and build a partnership, and deeply meaningful moments to learn from the people and their use cases we originally built the platform for.

6. Be yourself.

You can’t forget or unlearn how to be yourself, so bring your full self and best traits of yourself to work. If you’re fun, quirky, funny, or clumsy (I may or may not be some of these things 😜 ), show that side of who you are. Because if you are being your true self, it shows. Your genuine feelings and empathy, the moments you’re happy or sorry that you let your customer down conveys your message in the most clear and honest way possible.

Thinking about ways to do right by your customers? Do you have some of your own tips or style of working with users to share? Please leave a comment or start a conversation over DM, you’ll find me on Twitter as @jandwiches. 🍞

Rocking Customer Success from a Segway in Portland


There are many reasons why Customer Success is important to a healthy business — from growth to retention to referrals to product development — but I do it not for those reasons at all…

I do it because I love it!

I was in the middle of a Segway tour in Portland this past weekend and we stopped for drinks (yeah, apparently it’s legal to drink and ride a Segway there), and as soon as I found out that one of the other Segwayers was interested in adding analytics into his company, I started quizzing him about how he was looking to grow his business and talking about what he could do with Keen. I just couldn’t help myself. It’s like a puzzle he and I could work together to solve and then hop back on our Segways feeling refreshed!

The big difference between Customer Success and Customer Support

Before the Customer Success team existed, we had a team dedicated to helping customers, but it was reactive. If a customer wanted help modeling data or had a question on how to create a dashboard, we would help them. And sometimes we got to learn about what they were doing. We prided ourselves on being customer oriented, but it wasn’t really customer success. It was customer support.

Customer success is about preemptively helping a customer before they have even really asked for it. I am a people pleaser by nature, and if I can help a customer before they even know the need it, then I feel great!

I went to a talk the other day about Consciousness Hacking and they talked about how there are studies to measure whether people can tell what image they are going to see before they actually see it. I am still processing the talk, but I love that idea. If I could apply that to knowing what the customer is going to have questions about, and helping them before they even ask, that would be amazing.

Fortunately for me, it’s a little easier to predict customers’ behaviors than determine whether we can really predict which future image we will see. (By the way, Robert Krulwich from Radiolab has an interesting commentary on that subject)


Did Alice know what was behind that curtain?

Understanding customers’ needs before they feel the pain

The customer may not always know the best way to achieve their goals. By getting an overarching understanding of how they want to grow their business, we can figure out how they can get the most value out of Keen.

These conversations help us avoid the potential pain points a customer might have with our product today and also help us understand how our product needs to grow to support them in the future. We can now align our product roadmap based directly from an understanding of how our customers would like to expand. I love this! I get to help the customer by being their advocate at Keen and I get to help Keen by making sure customers are taking advantage of new features and capabilities we add.

And, I get to hear about really cool projects that people are working on!

One customer,, used the metadata of where they placed different news articles and advertisements on their webpage to provide information to their editorial staff which could then optimize how many articles a user was likely to read.

Another customer, Net-a-Porter, was able to use Keen to monitor web performance, which they displayed in their common room to alert them when the network went down.

Another customer,, built their own desktop analytics right on top of Keen] and used that to provide information to their clients about user engagement with their own application.

And I even learned about a customer, Whitesmith, that used us to measure happiness in their workplace. How cool is that?


Customer Success is a win for everyone

I feel like Keen has really stepped up the growth phase ever since we started the Customer Success team. We have become proactive instead of only reactive. We have gotten a much better understanding of our customers’ growth plans and how to provide direct value as they scale. Most importantly, we turned on the faucet to enable a constant stream of communication between the customer and our product team. Now we are aligning our growth to the growth of our customers.

And I get to be in the middle of all that, helping customers even before they are our customers, just riding around on a Segway.

If you’d like to talk more about Customer Success or building analytics with Keen or Segway safety tips, I’d love to chat! Feel free to drop me a line at

Focus on Allies - Learning Ally Skills at Keen IO


At Keen IO, we value introspection, continuous learning, honesty and empathy. In the spirit of those values, we are eager to learn how we can leverage our individual and collective privilege to work towards a more tolerant and inclusive world. As such, we teamed up with Trello to host a leading expert in diversity and inclusion, Valerie Aurora, to share how we can all become better allies.

Most diversity and inclusion initiatives focus on changing the behavior of targets of oppression, rather than allies. This talk helped to explain why we should focus on changing the behavior of allies instead. It described about a dozen specific ally skills and talk about effective ways to develop your own ally skills, including attending the Ally Skills Workshop.

At a glance, here are the 13 skills Valerie explored in her talk:

  1. An ally self-educates
  2. An ally listens
  3. An ally gives credit
  4. An ally asks for consent from the target, if they’re doing something that might possibly harm them.
  5. An ally keeps the focus on helping targets.
  6. An ally speaks up and draws fire.
  7. An ally uses their energy wisely.
  8. An ally spends money.
  9. An ally uses their social capital.
  10. An ally acts even when it’s uncomfortable.
  11. Sometimes an ally sacrifices personal gain.
  12. An ally follows leaders from marginalized groups.
  13. An ally makes mistakes and apologizes.

We’re happy to share the recording and transcript with you.

We’re hopeful the skills Valerie covered will help to inspire our community members to use their specific constellation of privilege to identify opportunities to support, protect and amplify the voices of targets of oppression. We’ve already had several conversations internally about how we can do that, and have been thrilled to hear event attendees have been having similar conversations at their companies.

Valerie’s slides can be accessed here.



I’m here tonight to talk about Focusing on Allies, which is what I think we should do for diversity and inclusion in technology in 2016. I’ve already got a bit of an introduction, so I’ll just quickly go through the stuff that Sarah-Jane didn’t mention. I am the founder of Frameshift Consulting, which is a consultancy for diversity and inclusion in technology. That will shock you. I actually was also the lead author of that code of conduct that they just read to you. It was fantastic to hear the code of conduct implemented well with the reporting information, thank you. I also, prior to doing this work, I spent a number of years, over ten years, as a volunteer doing work for women in open source in particular. I’ve taught the Ally Skills workshop and given this talk around the world, including a number of places in Europe as well as Mexico, Australia, and our neighbors to the north.

I just have been having a bit of branding confusion so I now have a slide explaining the difference between this talk and the Ally Skills Workshop. This is about a 30 minute long talk with hopefully 20 minutes of Q&A (please!), explaining why we should teach people Ally Skills and going over some Ally Skills. The workshop is actually a three-hour workshop where you spend most of it speaking to each other and discussing real world scenarios. You can find out more about it at this link, and all of these slides and a number of other resources are available on my website as well, the Frameshift website. About the questions again, I love questions, questions are my favorite part; I hate just talking, the thing I’ve already said a million times. Writing them down on index cards gives us much higher quality questions. I’m really looking forward to that. Alright, so let’s go into some terminology.

We’re talking about Ally Skills; what is an Ally? The first thing we need to do is define a few other terms. The term privilege means an unearned advantage that’s given by society to some people but not all, so emphasis on the unearned. Oppression — systemic, pervasive inequality that is present throughout society, that benefits people with more privilege in harms those with fewer privileges. I’ll get into an example in a moment. A target is someone who suffers from oppression, also called a member of a marginalized group. Now we can define Ally. An Ally is a member of a social group that enjoys some privilege, that is taking to actions. They’re working to end oppression and to understand their own privilege. The thing about being an Ally is that that’s not an identity, it’s not a thing that you are, it’s about the actions that you take.

We’ll do an example. Here’s a privilege you may have and not be aware that you have. This is the ability to walk into a convenience store and have the owner assume you are there to buy things and not to steal them. Oppression in this case is the self-reinforcing system of stories, TV, news coverage, and the entire legal system, hooray, that stereotypes black people as criminals, that benefits non-Black people and harms black people. It’s important to remember this is benefiting someone, that’s why it exists. The target in this case is any black person who wants to enter a convenience store. It could be a nontrivial number of people. An Ally in this situation is a non-Black person who does things like donate to legal system reform organisations, actively objects when people tell racist stories or make racist comments in their presence, votes in and anti-racist ways, and reads news articles about this privilege. Those are some of the ways that you could act as an Ally in this situation. I like to hold most questions to the end but if something’s not clear, I’m happy to answer the question during the talk.

I want to talk more about what diversity and inclusion mean. A lot of people will use these words and not be quite short what they mean by them. Diversity is the state of having people in a group who differ along the lines of race, gender, sexuality, age, disability, religion, class, or caregiver status. That includes things like being a mother, or caring for your parents, things like that. Inclusion is when you have a diverse group, run in that group is valued, included and respected without unfair discrimination or bias. That’s why we say both diversity and inclusion. It doesn’t help if you have a diverse group but you’re not treating people equally and fairly within that group. Here’s a couple of common misunderstandings. An individual can’t be diverse, so please don’t say diverse hire. Diversity exists in the context of a group. One of these yellow balls with a smiley face increases the diversity if it’s added to this group of balls, but it’s not having any effect on diversity in this group. Many efforts in this area focus on increasing diversity and don’t follow through on inclusion.

Alright, so here’s some examples of diversity and inclusion efforts: volunteer-run affinity groups for people to support each other within particular groups; travel scholarships from members of marginalized groups; coding boot camps; advice books aimed at targets; volunteer-run mentoring programs; recruiting outreach to places like historically that colleges and universities; conferences for marginalized groups… this is a photo from AdaCamp which is one of the conferences I have drawn for women in open technology and culture. What’s wrong with diversity and inclusion today? I think that the problem is that most work is aimed at changing the behavior of targets of oppression. Less work is aimed at changing the behavior of allies. Let’s talk about some of the reasons why we do this in the first place.

Some of the reasons we focus on changing behavior targets are targets directly benefit from change and tend to be more self-motivated. It’s easy to get someone to take action if it’s going to personally benefit them than if it’s going to take away one of their privileges. Targets are often but not always more aware of oppression. One of the ways you can cope with being a member of a marginalized group is to be unaware of it for whatever reason. That worked for me until about age 21. Usually you get to skip the part where you raise awareness if you’re trying to convince targets to change their behavior. Targets are often lower status and easier to tell what to do. It is much easier to tell your intern that they need to speak up more often in meetings than it is to tell your CEO to stop interrupting the intern. It’s just an easier thing to do.

Targets are often seen as the cause of the problem. You’ll see this when people propose solutions to sexual harassment in the workplace or the military, by saying, why do we remove women from the workplace or the military? This ignores the fact that the majority of sexual harassment is committed by men, but people don’t suggest removing men from the workplace because they’re not seen as the cause of the problem. Finally, really focus on targets and telling targets had to change the behavior, it helps you avoid confronting the feelings of guilt that you might have from any part of your privilege. If the target is at fault because they’re not behaving properly, then there’s nothing that you have to acknowledge about your own advantages that weren’t earned.

Let’s talk about what’s wrong with focusing on targets. In the first place targets tend to be overworked. You may have heard the old phrase, “Ginger Rogers did everything Fred Astaire did, but backwards and in high heels.” I finally found a fair use photo of them. This is maybe not technically true but it’s a very popular thing because it really accurately reflects the feelings of many people who are targets, that they’re working twice as hard to get half as much credit. The truth is is that that’s actually what is happening. One aspect of this is discussed in the book “What Works for Women at Work”? This is the only book of advice will targets that I recommend for two reasons; the first one is that it really presents sexism in the workplace as structural oppression… it says, you’re not going to solve it as a woman by acting in these ways, but you can make life a little bit easier for yourself.

The other thing I like about it is that more than half of the women that they interviewed for this book were women of color, and that they went into details about what the different experiences were and coping strategies for women of different races and ethnicities. In a way that was very detailed and granular. It’s a great book, I highly recommend it, but yeah, it just talks about in particular the prove-it-again bias. This is a pattern that they see, which is where, the way that our brains work is that it’s easier for us to forget things that go against our stereotypes, and it’s easier to remember things that confirm our stereotypes. If you had two co-workers, one of them is stereotyped in your head as the perfect manager and the other one is stereotyped as, you can’t be a manager at all. You’re going to remember all of the good management decisions that the person who fits the stereotype did. It’s going to take you forever to remember all of the examples of the person who doesn’t fit your stereotype. Prove it again, you have to do it over and over again.

Targets are under more stress. Stereotype threat is the fear of confirming negative stereotypes about a group that you are part of. This causes a measurable overhead when you’re working and when you’re thinking that affects your performance. You have to work harder because at the same time you have a voice in your head saying, don’t do it, don’t do it, don’t screw it up. Discrimination is a very miserable experience to be treated unfairly, and to know it. It as a lot to your stress. Harassment, abuse and assault, happen way more often than rethinking the workplace and elsewhere. People often don’t speak about it, because they don’t want to be retaliated against, but this stuff is all happening and it would obviously cause you a lot of stress and overhead. Post-traumatic stress disorder is the result of living through this level of stress for years upon years. Targets are under more stress in general.

Targets have less money. This is very small font. Each of these numbers varies each year. These are mostly 2015 numbers but there’s a few from 2013, so don’t get too worried, but you should get the general idea. Asian women and paid 87% of what white men are paid, and these are all US numbers obviously. Lesbian couples are paid 79% of what men married to women are paid, the individual in that couple. White women are paid 70% of what white men are paid. Black men 73% versus white men. Mothers 73% versus fathers, and fathers often get a small raise after becoming fathers. Trans women, 66% of their pre-transition income. Black women, 65% versus white men again. People with disabilities, 63% versus those without. Latinos, 58% versus white men. There’s more stats obviously but I think you get the message.

You’re also more likely to have unpaid caregiver responsibilities if you’re a member of a marginalized group. Targets are more likely to suffer retaliation. I mentioned this briefly before. There’s actual studies done on this. I’ll just with a quote from the study here. “Ethnic minority of female leaders who engage in diversity-valuing behavior are penalized with worse performance ratings; whereas ethnic majority or male leaders who engage in diversity-valuing behavior are not penalized for doing so.” You can probably think of some experience in your own life where someone who was male or ethnic majority did something related to diversity and got a benefit from, but this really showed that yes, it depends on who’s doing it and whether you’re seen as advocating for a group that you’re part of, or a group that you’re not part of, and the status that you’re part of.

Targets are often but not always in the minority. Here’s two communities I’ve been part of: this one on the left here is for open source software, the only study we have of gender distribution is from 2006. It’s a very small slice men make up 98.5% of the community, women make up 1.5%. I’m an operating systems developer and one of the things we learn is when you’re optimizing a program, you aim for the part that takes up most time. You work on that part first. You do not work on the 1.5% first. It was very clear to me that we couldn’t make any progress if we only tried to change the behavior of women in this community. By the way, I disagree with the categories they used to survey gender in these two studies. If you’d like advice on that I’d be happy to give it offline. Gender of Wikipedia editors came out as 90% men. It’s very clear that you can be more effective if you’re working on the people who are in the majority as well.

Targets have less power and influence. Fewer than 5% of Fortune 500 CEOs are women, fewer than 5% of Fortune 500 CEOs are people of color. Ursula Burns is two of those people, for the purposes of statistics, so when she steps down this is going to drop significantly, I think 20%. The Smurfette Principle was coined by a TV writer named Katha Pollitt. She pointed out that there are a lot of TV shows that had an all-male ensemble cast with the exception of one female character. The message here is that being a woman is strange, and it’s unusual, and it’s rare, when actually it’s one of the two most popular options. Of course, after Smurfette the village of male smurfs with only one female smurf.

This works out in the leadership teams of companies as well. Leadership team is the Board of Directors and the C suite, CFOs, CEO, COO, things like that. Here’s a study that looked at the SMP 1500, and here’s what they found. The probability that a woman occupies a top management team position is 51% lower if another woman holds a position on the same team. The Smurfette Principle lives and tokenism is real. The important thing to remember here is not just that you need to educate your top management team and get them to be making better decisions, but that if you ever see members of the same marginalized group who seem strangely competitive with each other, or even members of different marginalized groups, it’s not because they are terrible people who are competitive. It’s because they are working in a system in which only one of them can win, if they’re both aiming for a promotion higher up.

Finally, targets are seen as whiny, complaining and jealous when they advocate for themselves. I took this one from my personal experience. When I published the example conference code of conduct on the Geek Feminism blog, someone wrote this comment. There’s a little bit of mild profanity and vulgarness, I’m sorry: “Do you actually code anything or contribute to the open source software/hardware community in any tangible way or do you just bitch and moan about having a period and write conference conduct policies?” This was my favorite part. “It is a legitimate inquiry.” My friends had a lot of fun explaining to this person my ten year history of leadership in file systems and development of operating systems. That was enjoyable for them, but it just goes to show that you cannot get to a place where you are successful enough that you are not open to this criticism as a member of a group advocating for your own group.

Those are all the reasons why allies should take action more than targets, and yet when we look at groups and books that are aimed at improving diversity and inclusion in technology, you’ll see they’re still all aimed at targets. I’m not criticizing any of these groups except for the book, I don’t like the book, but these groups are doing great work. Black Girls Code aimed at black girls, Callback Women aimed at women speakers, Natives Who Code, Lesbians Who Tech, TransH4CK, The Pregnant Scholar, Code2040 is for (Black) and Hispanic Latina and Latino coders, and Mother Coders. Those are all explanatory. Lean In of course is the book that says, hey, if women just worked twice as hard, magically sexism will go away. Here’s the complete list of books, nonprofits and organizations for allies in technology that I could find, and yes, it’s blank on purpose.

This is my proposal: that 2016 is the year that we focus on allies and changing the behavior of allies, and whoah, we’re already three quarters of the way through. I wasn’t thinking when I put the year in this. I just want to summarize why we should focus on allies, and then I will talk about ally skills. Allies have more time and energy. Allies have more money. Allies aren’t harmed for diversity valuing behavior. Allies are often in the majority. Allies have more power and influence. They are seen as altruistic, giving and kind when they’re speaking up for members of groups they aren’t part of. What do ally skills look like?

1) An ally self educates. Often people will learn a little bit about a new word or something they don’t understand, and then insist that someone who’s a member of a marginalized group explain it to them, like suddenly they forgot how to Google.

This is a really important, crucial first step to take in your work as an ally, is to really accept the responsibility for teaching yourself, and going out there and making the best effort to learn what you need to learn. If you’ve exhausted the online resources, watched the videos, read the blog posts and you still don’t have an answer to your question, that’s a pretty good question. You can feel free to ask someone that one, but it’s really important to take responsibility for educating yourself in the first place, as the default.

2) An ally listens. I had a hard time deciding whether to put self-education or listening first. They’re parts of the same coin, but yes, a really important thing is as someone who has more privilege, you’re used to talking and other people listening to you. That’s an easy pattern to fall into. Pay attention next time you go to dinner with your friends. There might be a pattern that you see.

An important part of being a good ally is listening to members of marginalized groups and believing what they say, and taking it seriously. Here’s a great example that happened at the 2014 Grace Hopper celebration. They had a panel of all men, about male allies, in front of an audience of about 7,000 women. Multiple people warned them that this might go badly. It went badly and there were multiple press releases and PR disasters, and a cleanup that they needed to do, as well as the people in the audience having a miserable time. One of the people who was on that panel is Alan Eustace, who was at that time a senior vice president at Google. He used his Twitter account to send this one Tweet, “Let’s reverse the male allies panel. You talk, I listen.” Then he gives the room information. He and two of the other panel members spent an hour in this room sitting and listening, while women came to the mic and said what they experienced at work and how the words they had said on stage had hurt them. That was a great example of an ally listening.

3) An ally gives credit. Again, as someone with more privilege, people will assume that you did the thing that you’re talking about. This has only happened to me a few times when somebody thought I wrote a file system I didn’t write, but that was very sweet. It must be wonderful to happen all the time. As an example, there’s a link down here about this. Women get less credit for co-authoring papers. In fact, it has zero effect on their careers according to a study of economics professors, people with PhDs. That’s just one example of how that happens. Here’s another example of how to give credit. In social justice circles there’s a norm that whenever you use the word intersectionality, that you credit the inventor of that term by name, Kimberlé Crenshaw. Briefly, the term intersectionality describes the concept that people can be subject to multiple overlapping forms of oppression that intersect and interact with each other in different ways.

Kimberlé Crenshaw is herself a black woman, so she gets a form of oppression based on being black, she gets a form of oppression based on being a woman, and she gets a whole special form of oppression based on being a black woman together, but it’s really important to give credit frequently and copiously and whenever you’re not sure. The one exception to this is if giving credit will put someone in a position where they might be attacked. If you’re not sure about that, ask whether or not somebody wants credit in that situation.

4) An ally asks for consent from the target, if they’re doing something that might possibly harm them. We all understand that the fight for improving equality and bringing rights to people often involves harmed individual people who are members of that group. Think of anything, really. The important thing is that if you as an ally are taking an action that’s going to put someone in that position, you have to ask them first. An example of this situation is the fight for marriage equality here in the United States. That involved individual same-sex couples going to court and having their personal lives examined with a fine tooth comb and being a symbol and an example and being harassed by people. The important thing is that they volunteered to do that. If you as a straight person walked out there, picked a couple and said, you’re going to be the people that we’re fighting for in this court case, that would not be asking for consent.

5) An ally keeps the focus on helping targets. A common problem is called derailing. If somebody’s trying to talk about the problems facing targets, that other people will try to recenter the discussion on the feelings of people with more privilege. Here’s an example of someone pushing back on that, from Twitter. Jenn Schiffer is an excellent programmer, artist and humorist. You should check out her blog if you have a chance. She says on Twitter, “A shoutout to my girls out there who want to be visible in the tech community but also want a family, but have to choose because Earth is terrible.” Some rando replies and says, “Well, it’s a problem for fathers too. Balancing networking and family isn’t easy for anyone. Then Moishe joins in and says, “As a dad,” so invoking his privilege, he says “I’m going to go ahead and say it’s objectively harder for moms.” He’s getting the discussion right back on track from where it started, so yeah, keeping the focus on helping targets avoiding derailing.

6) An ally speaks up and draws fire. The converse of this is that when being the focus of the discussion is bad, it’s going to get people attacking you, that’s the time to speak up and draw fire as an ally. I got another example of that here, again from Twitter. It’s my friend who goes by @hashoctothorpe. She says, and she’s a straight white cis woman, “In one joke, (elided) and (elited) managed racism, misogyny and transmisogyny. Total (elided) weasel territory,” and also says “The talk from (blank) and (blank) was offensive in every way and violated the code of conduct, please expel them.” There’s a great resolution to this story, the conference did expel these two folks for the remainder of the conference. They both apologized on Twitter and they came back the following year and were not making offensive jokes anymore. This is a great example of when it’s okay to be the center of attention when you’re acting as an ally, because obviously my friend risked being the center of a trollstorm by taking this action.

7) An ally uses their energy wisely. Some of you may have seen this. This is Anita Sarkeesian, who did the tropes about Women in Video Games series for Feminist Frequency. One of her critics said, “My biggest problem with Anita is that if I used her logic, I could see sexism everywhere.” Yes… so close. (laughter) Seriously though, you can’t go to the grocery store without some form of oppression. It’s around you all of the time. It’s systemic, it’s pervasive. What’s important is to be able to see, hey, where do I have the most power and influence? Where can I use my energy in a way that’s going to have the biggest impact? Do I just need to take action, even though it doesn’t make sense, because it’s important to my values? You don’t have to address everything you see, but really you’re starting to pay attention, and say hey, when can I take an action and make a big effect. That’s a great thing to keep in mind.

7a) Charles’ Rules of Argument: This is one of the things I teach in the Ally Skills Workshop, Charles’ Rules of Argument. This is Charles Miller. He had a blog on the internet in 2004. He currently works for Wikia just up the street. He spent a lot of time arguing on the internet, and then decided that was not how he wanted to spend his time, so he made Charles’ Rules of Argument. Rules are, the first one is, don’t go looking for an argument. Somebody’s wrong on your part of the internet that you normally read. Trust me, it’s true. If you do choose to have an argument, state your position once speaking to the audience. This is important because you’re unlikely to change the mind of the rando or the troll or whatever it is that you’re addressing, but the people who are watching haven’t made up their minds, and they want to emulate the person who seems to be the most admirable.

Wait for absurd replies is the next step. On a mailing list this will take two or three days, on Twitter it will take two or three minutes. Once you get a few absurd replies accusing you of saying things you didn’t say, you reply one time to correct any misunderstandings of that first statement. This is the most important part, do not reply again. Spend time doing something you enjoy like going outside or drinking a beer or petting a dog. It’s very important.

8) An ally spends money. An ally has more money. A great thing to do with it is give it to support groups that are fighting to end oppression. If you’re not sure which groups to give it to, this is one time that you’re allowed to ask a member of a marginalized group, “Hey, where should I put my money?” and expect some good suggestions.

As a former executive director of a nonprofit and the fundraising lead, I would like to say please don’t offer to donate your time unless it’s an organization that’s set up specifically to do that, like Black Girls Code has a very efficient system for doing that. If you’re not sure why one or two hours of your time, of your expertise and web design is not helpful, imagine you walked into work tomorrow and somebody said that you have 500 interns, and each have one hour available. Just give people money.

9) An ally uses their social capital. One of the things you can do is give people money, and then tell other people that you gave money. This is not to make you look good, this is to set an example for other people — “I believe in this cause enough and I believe in this group’s effectiveness well enough that I gave them x dollars.” That is a wonderful thing to do, please do it. You can also use your social capital to help people get talks, to make introductions to people who are useful to someone’s career, not just people who are like them in the way that they are marginalized, and to amplify other people’s voices, amplify the voices of targets. One of the things I try to do is I relatively rarely tweet myself, I usually retweet somebody who has a lot of knowledge about a particular subject.

10) An ally acts even when it’s uncomfortable. Poor dog, I always feel sad when I get to this slide. It may be really uncomfortable for you to speak up if your coworkers are using the words “crazy” or “lame” in conversation, because most people don’t know that that’s not okay and it just feels so extreme, but it really helps to remember, hey, if you feel uncomfortable, how does the person who has undisclosed mental illness feel? Or the person who uses a wheelchair, When you’re talking about your product being lame? Being aware that whatever you’re feeling is probably an order of magnitude less will really help you act in a lot of these situations.

11) Sometimes an ally sacrifices personal gain. That’s how privilege works. You don’t have to sign up for it. You don’t have to say, I accept this unearned advantage that you are giving to me. People just hand it to you constantly all of the time, and sometimes you have to turn around and say, no, I don’t accept that. An example of this happening is you may have seen a panel at a tech conference that looks like this before (picture of tech panel with 5 white men). You may be invited to a panel in which you round out a panel that’s all white or all men or something like that. That’s a great time especially if you are already fairly far along in your career, to say,” hey, I no longer serve on panels that are all white, or, I no longer serve on panels that are all men. Here’s my list of suggestions of people to replace me with that are more qualified than I am.” This is obviously better to do once you have more influence and power in the first place, but you can do it at any point.

12) An ally follows leaders from marginalized groups. Again, as someone with privilege you’re used to people following you and doing what you say. The thing is that if you’re trying to support the marginalized group and you’re not part of it, you often don’t know what they need or what would help them. People who are a member of that group do know that and you can instead support them, give them your money, amplify their voices, encourage other people to follow them. There’s a phrase from disability activism; “Nothing about us without us”. There’s a great Wikipedia page on that you’d like to check it out more. That’s a good thing to remember.

13) An ally makes mistakes and apologizes. If you never make a mistake, you’re not doing anything risky or worthwhile. It’s also impossible not to make a mistake. What’s important as an ally is not that you are perfect and you never make a mistake; what’s important is that when you make mistakes, you immediately apologize, correct yourself, make amends if necessary, and then move on. It’s not about you, it’s not about your mistakes, it’s not about feelings about your mistakes. It’s about trying to support this group, this is the best way that you can do it. It’s also a good way to set an example for other people were wondering how to behave, if you can graciously admit your mistake, apologize, correct yourself, move on.

We are almost to the end. That’s just a very high level hand-wavey summary of I think thirteen ally skills, and it’s going to take a little bit more than that to learn them and just to use them. You can learn ally skills but it’s actually sort of difficult right now. Most of the information is spread out, you noticed the number of links to research papers I had in these slides. I’ve collected those over multiple years. There’s not a good set of books right now. There are books that will cover one aspect of being an ally but have maybe a chapter on ally skills, but there’s not a theory of being an ally out there yet.

I’m working on a book about ally skills, you can follow my twitter account @frameshiftllc for more news on that. In the meantime, I and many other people teach an ally skills workshop. It’s interesting that the San Francisco Bay Area has the largest number of people teaching these kind of workshops. We might be the area of the world that needs it least, but that’s how it is. That’s why I’m working on the book.

The ally skills workshop I teach, the materials are all freely usable under the Creative Commons share alike by attribution licence, and there are many ally skills workshops that are derived from the same set of materials you can get from other people as well. There’s a “train-the-trainers” also available. I think I’ve taught about fifty people to do it and there’s a number of people who are self-taught as well. All the materials for that are freely available. Currently this workshop is being taught internally by internal trainers at Google, Square, Slack, and Spotify, and I have some other companies that will hopefully be joining them soon. You can go to my website and find out more about that.

Conclusion, this is what I’d like you to take away from this talk. Most diversity and inclusion efforts focus on targets. Targets have less time, energy, power and influence. Allies have more ability to make change, and ally skills can be learned. Let’s focus on allies for 2016. All right, thank you so much.


I would love to do questions at this point. If you haven’t written your question on an index card, please do and pass it up front. Are there any coming up to the front? Great. I can also answer questions that people ask with voice. I wrote a blog post about how to have better questions — you know, the “this is more of a comment than a question.” If somebody has to write it down on an index card, you can just skip that one!

Wow, this is big picture…

What is your ideal vision of an ally organisation?

Yeah, so the interesting thing about …This is tough, people have always asked me, hey can you start a mailing list or Slack community or something like that for people who want to act as allies? It’s never felt right and I think it’s because there hasn’t been a focus yet on specific ally skills that can be written down. If you’re a member of a group that’s a marginalized group, you have a shared identity. That’s an identity, you have shared experiences. Being an ally is about actions, and there’s not …It’s not the same sort of way that you have this shared experience and this need for the same support group. An ideal vision of an ally organisation I think would be something that’s really focused on supporting people who are doing this kind of work, who are members of marginalized groups. A fantastic form of an ally skills organisation would be a giving club. This is a group of people who get together and share information about what organisations they want to donate to with a focus on diversity and inclusion in technology. That’s an extremely powerful thing to do. You can bring together ten people and perhaps you had a bonus this year for $5000, that’s $50,000 that you can agree on and share your information about how to use. I really think ally organisations would be focused around those specific ally skills in supporting each other, but it would have to have that goal rather than, I’m an ally, you’re an ally, yay, let’s ally together.

Oh wow, good set of questions…

Can you please get Linus (I assume Linus Torvalds) to attend one of your workshops?

No. It doesn’t work that way, I wish it did. That was a hilarious question, thank you whoever wrote it, but that actually is part of a class of questions I often get asked which is, how do I convince people to want to be allies? The answer is you can’t. If you could convince someone to want to be an ally, they could conversely convince you to not want to be an ally. I can tell you how I’ve seen people make this decision, and it is often someone very close to them has a miserable experience. Someone they’re married to gets fired for one of their kids gets attacked or something like that. That can often be an experience that make someone go, “whoa, I just opened my eyes.” A slightly different version of that is if multiple people who are somewhat close to several of your co-workers all tell you about a similar experience they’ve had, and that completely changes your view of the world because you didn’t know that was happening… that’s another way that I see people wanting to be allies. Another way I see it is people who care about studies in science and things like that. There’s just this point where they’re like, “I’ve read the fiftieth study saying the same thing about bias and discrimination. I think it’s true!” It’s often really somebody who has a value, a value of being fair. Most people have a value of being fair and inclusive, and then their eyes are open to the reality that that’s not true. That usually helps people in my experience, become allies. If you don’t have that value in the first place, meh. Linus is pretty clear about what his values are.

Amplifying voices; should we ask for consent?

This is a great question. Sometimes amplifying someone’s voice will help them, sometimes it will harm them. If you’re not sure, if there’s a question in your mind, yes, you should ask for consent. This is a thing I normally do, I’m part of a private discussion group and we have the system of, someone says something really funny that we want to share publicly. It’s, “may I share that and do you want credit for not?” We never assume either of those two things. Once you normalize it, it just becomes part of the usual.

Wow, so many questions, this is great.

How can allies work against unconscious bias?

Yeah, becoming aware of it and setting up structures and checks. Often, one of the great examples I like is that I hear that at Google promotion meetings, where they decide who gets promoted, the beginning of the meeting they read a prepared statement that says, “hey, here’s what unconscious bias is. This is what it looks like. If you think you see it in this meeting, here are the words to say.” That’s a fantastic way of creating a structure to go back against this. Oppression is part of …It’s a systemic structure. It’s got lots of form and ritual around it, so creating new structures is part of how you do that.

Yeah, so this is asking about when do you want separate groups where it’s allies and targets and when you want to be in the same group and giving examples like, white women versus groups of black women and sometimes working across purposes. Oh yes, and that often it seems patronizing, when people are telling people what to do.

Yeah, that’s why I emphasize so much on the ally skills, starting with listening, self educating, and then following and supporting. I believe that this is something that has become clear of the last ten years of doing this sort of work, is that I believe you do need separate groups for members of a marginalized group to support each other, then you need an integrated group of people who are both allies and targets for doing work to change the system. The reason is that it’s just, you need support groups where you can say things without being questioned, when you don’t need to educate people. A group where you can just say, “hey, blah-de-blah happened at work today,” people will just be like, “oh yeah, that really sucks when that happens,” instead of being like, “that doesn’t happen. Could you explain to me why that bad?” All that sort of thing. I really encourage people to have both of those things at work, at school, and in all sorts of things. To be very clear, when you have an event, whether this is a thing for members of the group only, or for members of the group and allies. If you leave it unsaid people will usually assume that the good people, the actual allies, will assume it’s for members of the marginalized group only. The annoying people who want to tell you what to do will assume that they’re welcome and show up. I have this happen a lot with Women in Linux events. (from audience) So an example is the East Bay Meditation Center which has events for specific groups and then they have events for teaching people about inclusivity.

Sometimes a co-worker say something disrespectful and I’m not sure whether to say something to them. What if the result is that they just stop saying those things round me or if I end up blacklisted as a result?

Yes, so first of all if you are in danger for speaking up, you should maybe rethink whether you are an ally in that situation. You may be a target, if speaking up is going to get you in trouble. You may not have the advantage and the privilege and the power and influence that you need in that situation, and it’s fine not to speak up in that case. The concern about people just going underground and just not doing it in front of you…? Sometimes the only thing you can accomplish is to say,”hey, this is not socially acceptable in this situation.” You can’t control what someone’s doing away from you. You can just make clear that it’s not welcome and that it will have consequences if it’s around you. I view that as a win. You’re setting a standard and there’s a lot of other people who are going to see what’s happened and act differently.

Ah, self-education. What’s a good website or Google search to start at?

The way that I like to recommend people with self-education is, you find a starting point and you fan out from there. I’ll give you a specific concrete starting point. I use Twitter a lot. I will follow someone on Twitter, I will pay attention to what they’re saying in their own Tweets, but I’ll also pay attention to who else they are amplifying, who else they are retweeting, and then I will follow them. Often using that you can find your way to extremely knowledgeable people who are sharing for they know for free. You can do the same thing with blogs or Tumblr or mailing lists and things like that. The thing I usually suggest is to start with the Ally Skills Workshop handout on my website, which has a number of different websites and wikis and things like that. Wikis are another good place where you can fan out and begin to learn things, but mainly, find people who are knowledgeable on the subject you’re interested in and who write things in some form that’s distributed on the Internet, and start there.

Let’s see what else. Are consultants the best way for an aspirationally diverse and inclusive company to make concrete progress? If so, can you recommend any?

Yeah, so this is diversity and inclusion, I like for people to think about it like any other aspect of doing business. What would you do if you needed to improve the security of your project? What would you do if you need to improve your HR practices? What would you do if you need it to do more stress testing then you could do with the computers you have in your office? Often you, as you’re growing, you have to outsource these to consultants at various levels and eventually you can bring them in-house once you’re large enough. I don’t think Google is renting botnets to stress test anything at this point, and they are also doing all their internal diversity and inclusion stuff.

A place to start for consultants is, I would say beginning looking at Project Include’s resources to get an idea of what’s the structure, what are you missing, what other things you might do? Personally I often recommend The Ready Set, which is ostensibly a recruiting assistant organisation, but they also do diversity and inclusion training. That’s run by Y-Vonne Hutchinson. Another one I really like is Paradigm IQ, founded by Joelle Emerson and a number of other women, and it’s like they’ve got so many partners now I can’t say all their names. Another good one, shoot …Look to see where Caroline Simard is working right now. I don’t remember the exact name right now.

Those are some good places to start. I do some consulting but I’m fairly specialised. I usually do ally skills workshops or ally skills related things, and I do code of conduct consulting, but I can definitely direct you to other folks. Oh, textio is another good resource. As a company that does large-scale analysis of text corpus to look for bias in language. That can include things like your job descriptions or your performance reports. Again, talk to people who are experts in that area and ask them for advice.

Alright, so this is a tough question but I’ll read it anyway. How do we incorporate cultural competencies in the education of an organisation around diversity and inclusion?

I think what this is saying is how do you use what a company is already good at in terms of its culture and the way works, and use that as a tool to make diversity and inclusion more effective, whatever work you’re doing there. Yeah, I think it’s helpful to have people who have experience in the field that your company is in, be the people that you’re working with as consultants or getting advice. So, really matching up the style of training and information with the cultural biases of your group. One of the things I did with the Ally Skills Workshop is my target audience tended to be introverted, tended to be not interested in standing up in front of other people, tended to be easily bored. It took a while to develop a workshop that worked for that group of people. If I was doing a workshop for a group that was not mostly software engineers like say, people who were sales engineers, that would be a very different format of the workshop, because they would be very excited about speaking in front of other people. That’s what I would look to say in that case.

How do you be an ally to someone who is a target who reports to you? (Given that there’s this other power dynamic which is that you are their manager and they report to you.)

First, kudos for understanding that there is a power dynamic. That’s not a popular thing to talk about or admit in Silicon Valley, that these things exist. Being aware of that power dynamic and being aware that it will cause things like, this person’s less likely to tell you what’s actually going on, they’re less likely to complain to you, they’re less likely to share with you about things, so being aware that you’re limited as a manager in that way. However, then you also have power and influence that’s greater, because you are manager, so if someone does come to you with a problem, you can then go talk to their manager. It’s actually your job to resolve people issues and that sort of thing. I would just say be aware of both the disadvantage and the advantage that that gives you. This is an example of choosing your battles and figuring out where you have the most power and influence.

We have three more minutes, are there any more cards?

Every conversation about diversity and inclusion at work ends up with me trying to educate people. How many *expletive* links do we need to send?

Yes, I know. This is an interesting dynamic. I started to do this, whether or not it’s intentional as an actual strategy to exhaust people who are trying to change the world, who are trying to make the world a better place. It may come unconsciously from this entitlement, this being used to being able to ask for other people to do work for you. Being used to just getting what you want, being used to having people being afraid of you and all that kind of stuff, but I think also people do do it intentionally at some level or another. One of the things I have learned to do is to figure out whether someone is truly open to changing their mind, and is willing to do the work, or if they just want to argue with me, or if they just want to have some excuse to say no and not do a thing. One of the ways I would do that is upfront, I will ask, “hey, why don’t you do this Google search?” If they don’t do that Google search I know that they’re not open to actually learning and I’m wasting my time on them. Setting up a series of small tests to use to figure out whether to spend your time on people. A thing that totally confuses me and just makes me really unhappy is when I see people explaining their block policies on Twitter. You don’t have to justify why you’re blocking someone. I’ve seen people who have come through the other side of that, and have been like, “I don’t explain any more because you know what? None of these people deserve my time. They don’t have any sort of entitlement to it.” I realize that and I realize I don’t have to give them a fair hearing. One of the ways to do this is to compare the amount of time that they spend asking you a question to the amount of time you spend answering the question. A great place to start people, both for feminism and for a number of other things is the intersectional feminism Geek Feminism Wiki. That’s in the slides, or it should be. Oh my gosh, it’s not in the slides, wow. Geek Feminism wiki is a great resource because it has a lot of cross-linked articles about a number of topics. Yeah, really getting that sense of whether someone is open to that level of self-education, and then just not spending your time on those people if they aren’t. I think that’s it. Thank you so much for coming, and does anyone want to say anything before we end? Yes, all right, great.

Hello, Community.

Hi! My name is Tim Falls, and I’m the author of this blog post. I’m writing this to introduce myself to you, the reader of this blog post ;) But, not only do I want to introduce me; I want to introduce we.

We are the community team at Keen IO. We are Justin (aka, JJ, elof), Sarah Jane (aka, SJ), Taylor (aka, ATX’s best), and Tim (aka, a guy who just referred to himself in the third person.)

But enough about us; this is actually about you! “You” are our readers and followers, our customers and partners, our investors and advisors and mentors and inspirations, our family and friends, our people — our community.

Our team exists because our community exists; we’re extremely grateful for that fortunate reality.

Community Roots

Justin was the first to be hired at Keen IO with an explicit focus on community-building, joining as the seventh employee and with the title of Developer Evangelist (or was it dev advocate? oh well, tomayto/tomahto.) When he arrived, community was already baked into Keen’s core.

Our founders and earliest employees depended on support from the people around them each time they collectively cleared a hurdle or broke through the ribbons of the company’s initial milestones. Being the thoughtfully reflective bunch they are, they recognized that the symbiotic relationships they’d forged with the humans around them in fact represented the Keen community in it’s infancy; and they realized that Keen’s success was virtually impossible without the contributions of that community.

Today, each and every employee at Keen — whether they spend most of their time writing code or writing website copy or writing the paychecks — can recognize and appreciate the powerful, positive impact that our community has on the company, and vice versa. That’s because everyone has had the pleasure of engaging with our community members and experiencing first hand the magical good vibes that abound in the presence of you all. And in so doing, each individual has detected, with her very own senses, that our community is not just a bunch of people outside our company that like us and/or use our product; it’s not only the smaller number of people who build/support/sell that product; our community is all of those people (and many more) together as one living, breathing, thriving organism.

And we won’t stop

The four of us on the Keen community team have the humbling responsibility of ensuring that our recognition and appreciation for the value of community never dwindle. We get to focus our daily efforts toward supporting and enabling the community around our people, product, and brand. We dedicate our time and creative bandwidth to crafting the most inclusive, valuable, and uplifting place possible for the humans who choose to join in and help make our community what it is today and what it will be tomorrow.

Obviously, we constantly think about this responsibility and continually ask ourselves:

“What can we do to make our community a happy place?”

Sometimes a “zoom out” is helpful in effectively answering this question. In light of my one year anniversary of employment at Keen (Sept 8), I recently un-zoomed to the max. My findings were strikingly obvious…and equally important:

We can forge stronger relationships, by getting to know our fellow community members even better and by making a concerted effort to help you get acquainted with us — as people and professionals.

The first step toward doing just that is, well, this!

We want you to feel more than welcome in this community, and one of the best ways to feel at home is to be in the presence of friendly faces.

Of course, as I alluded to earlier, you can consider everyone at Keen your go-to person for whatever your needs may be, because we all community. But, it’s good to know who is consciously focusing on you at all times, and that’s this little group of people =)

If you haven’t already given one of us a high-five, then we should fix that ASAP. In fact, an internet high-five is just a few clicks away, so we’ll wait here while you do that… If our relationship has moved beyond high-five-land, cruised through hug-ville, and is already at the serious level of direct messages in Slack, then thanks for being here — we ❤ you, too!

Regardless of our current relationship status, we want to take this opportunity to share more of our “personal” details, in hopes that it will help you better understand us as a group of people, why we fervently strive for your happiness, and what you can expect from us.

Under the hood

At Keen, our organizational and operational structure is defined by a document that has been created through the collective efforts of all employees. We call this document the Keen Operating System, and it exists as a Github repo (it’s private now, but we’re considering opening it up to the world if/when it’d be valuable.) Anyone at Keen can contribute to this document (via pull request) at their discretion, and thus everyone is empowered to have meaningful influence on the operational model in which they work.

Reason for being

One section of the document lists and describes the various teams at Keen. Each team is responsible for creating their own page so that everyone in the company understands their mission, strategy, roles, responsibilities, etc. Community is one of those teams, and we’ve copied our team page into a public repo, so you can see for yourself how we represent ourselves to our fellow Keenies. We hope that, in sharing this, we facilitate your deeper understanding of how other teams at Keen see the Community team and how we think about working with you.

Measuring success

Like all business units, we place an importance on measuring our team’s performance. Indeed, community-building can be a tricky thing to gauge — but, even more certainly, it’s not impossible. A lot of our performance tracking comes in the form of intuition — i.e., “ya just know it’s working.” This is a really human thing, and we’re all humans interacting with each other, and those interactions are filled with signals that only our brains and spirits can interpret. So, thanks for sending the vibes — we’re picking up what you’re putting down!

But, also with all business units, “the feels” only go so far in determining whether or not an investment of resources is returning tangible, meaningful benefits to the company.

So, how do we start to quantify the impact of our efforts?

Well, quite frankly we’re still figuring that out. And guess what — we’d love your help! We’ve started to develop our practices in the open, and we’re inviting anyone/everyone to collaborate with us. If you’re a community member, or if you’re building a community of your own, or if you’re just an interested person with a perspective to share, please join the conversation. Beyond serving as a mechanism for receiving your input, we extend this invitation in hopes that it helps to further familiarize community members with our team’s activities, values, and approach to our work.

See you out there!

I hope this rather long-winded introduction to “we” is helpful for you, or at least it was vaguley entertaining. It’s been fun for me, and I’m sooooo glad to finally get a post onto this here weblog, which I’ve admired since way before I joined the Keen family.

If you fancy the chance to reciprocate the sentiment, please get in touch with us through any number of communication channels (see ALL THE THINGS listed on our community page), or just leave a comment below. We’d love to learn about who you are, what you’re working on, why you do what you do, and how we can help you achieve your loftiest goals.

Ta Ta For Now!

Introducing the Keen IO Community Code of Conduct

A few weeks ago we sent an email to the whole company introducing the Keen Community Code of Conduct. This blog post includes most of that email with a few more things added that we wanted to share with our community.

A few months ago the work began on the Keen IO Community Code of Conduct. We’re very excited to announce v1.0 of the Keen IO Community Code of Conduct is now public. 🎉

This Code of Conduct applies to all Keen IO Community spaces, such as the Community Slack group, open source projects, Keen IO meetups, Happy Data Hours, and more! It will be added over the next few weeks to different projects and other community spaces.

It is the product of many meaningful conversations and advice from many Keenies and other humans from outside of Keen IO. To anyone that contributed to this Code of Conduct, thank you. The process of creating a document like this isn’t easy, and we have so much respect for anyone who has done it before.

The Code of Conduct is a living document. This is only v1.0. It will grow and change with Keen IO and its community. This is why it is on Github. Issues can be created to help with revisions and updates. There is also a feedback form, which can be filled out anonymously. Feedback is always appreciated. It will also help guide training and more internal procedures for the Community Code of Conduct.

Lastly, we’re looking forward to making it even clearer to our community that we are dedicated to providing a safe, inclusive, welcoming, and harassment-free space and experience for all community participants, which will help grow our community in amazing ways. We hope this Code of Conduct clearly states what behavior is expected and not tolerated as well as establishes a path for community members to report possible incidents and seek help.

Please feel free to ask me any questions! I would be more than happy to have a larger conversation about it and its existence. 😀

hack.guides() Tutorial Contest!

Are you obsessed with building Dashboards? We are excited to sponsor a $500 prize for the best guide using Keen IO to power dashboards in their apps.

Over next six weeks, you can submit tutorials and collaborate with hack.guides() developer community on the best practices, hacks, and tricks using keen, RethinkDB, and other partners in production.

Submit your post here and the share your posts with us on Twitter to spread the word.