We've invested in content very early on, because we recognise that we're bringing new ideas to market. And we sort of took sort of two pronged approach to that. One is - we really focus on customer pain points. And we right from that vantage point, we're very, very targeted about that.
For example, you know, if we have a conversation with, you know, a couple of customers in the last month, and we just realised, oh, they're all struggling with the same pain point, that's something that's like, is probably shared, right. So we have a particular persona, a particular pain point, a particular customer in mind when we write this. And choose it based on what we hear is a high priority and top of mind for folks. For example, you know, folks attended a specific conference and got really excited about a particular talk. Why were they excited about that talk? What about that talk, you know, got them excited? Or, for example, if we talk to them, and we ask them, like, what's your priority for 2021? And, you know, they'll say, you know, they'll describe a very, very particular thing that's on their roadmap that they're working towards, like, that is something that like, you know, gives us food for thought on what these people care about.
And then we add our own perspective and views on that, but in corporate with what we learn from the community, so that's really the first like a very customer specific perspective, for the content.
Then the second tenant of this is we try to write in a very approachable manner, to your point, like, we could make it extremely technical, we could make it very complex, but we actually focus on trying to make it easy to understand, easy to consume. I think, in today's world, people are inundated with information. And we want to make it thoughtful and interesting, but something that can click with people.
And so, you know, we wrote like about data mesh, you know, without going into all the details of that. It's basically a novel architecture that some of our customers are very excited about. And we got excited about that, too. About that vision and where that's going. And we did a lot of research on it and wrote to, like, clarify the idea and explain how data observability actually is connected to the data mesh. The second example is we write a lot about data downtime, right. And again, we could have made it very technical about like, you know, specific sort of schema changes, different anomaly detection methods. But instead, we're focused on the stories and how it impacts people and our methodology. We try to do something that's more approachable and something that you can just start using tomorrow.
In early stages, when you will just building the readership, were you mostly focused on specific technical events and technical audience and you build from there, or you started from, and maybe you remain, in the business domain, and not like data scientists or engineers. What was the original turf, for you to build the community out?
So the very original [community] actually followed kind of the path that we took to develop the company and the product, which is starting with the non-technical, but rather, pain point and impact that it had. That's actually the very first blog posts we wrote was about, I wrote about my personal experiences with data downtime, and how I felt plagued by it. It's called the rise of data downtime, you can look it up on Medium. And that really spoke about sort of a very painful time in my career, when I thought I was gonna get fired, because the data was wrong all the time. When I share that with people, people responded, saying, like, 'I feel heard, you know, and that's what we wanted'. That's sort of the response that we wanted to get, we wanted to get folks to wanted to create empathy and a shared connection around this problem. So that's what we started out with. And moving in sort of the chain and kind of developing a company and building each part, we're actually moving to creating more and more content that's focused on the technical aspects of the product. And stay tuned, there's, there's way more to come.