<span id=Sharing your roadmap can be scary. Here’s why we are sharing ours." />

We really meant it when we committed to “radical transparency” because we believe in order to improve the way software is built — more efficient, more enjoyable, we have to be a part of sharing what works and doesn’t work for us in the hopes it helps at least one developer or team do their job better. 

And because we want to be more than just talk, we will be sharing a lot of our internal processes, meetings, and even our roadmap.

I know what you might be thinking, “That’s CRAZY.” Ok, maybe not that crazy. There are plenty of other companies like Buffer and most recently, GitHub, already doing this. But for the majority of SaaS companies, I can guess what might be going through their head. 

Sharing your roadmap can be scary. 

I’d bet that traditional SaaS companies would have a panic attack at the mere suggestion of sharing their roadmap outside their own four walls — especially without an NDA in place. We asked ourselves why some may be hesitant to share their roadmap and then, consider if that was a risk we were willing to take in order to advance our broader mission. Here’s what we came up with. 

Things change

The natural rhythm of an engineering team has always come with some unknowns — some code or integration didn’t work as expected, setting our timeline back. Or work just took longer than estimated. Bugs were reported and our teams had to switch from new features to bug fixes. Maybe a high-value customer requested a feature and your focus is pivoted to that unplanned work in order to delight your customer. 

Commonly when setting out the product vision, these things are not factored in. When this happens, there is likely a misalignment between leadership and the people doing the work. If you share your roadmap, sales might sell a product that isn’t ready yet and when deadlines slip, you are bound to have some angry customers. 

Is it worth the risk? 

Yes. Part of the reason for building Pinpoint was to address some of these alignment and blind-spot issues that are common within engineering teams. Our hope is that by bringing together all of the data, from all of the systems used in building software we help cut through the noise of what’s really going on, how long things take, and then use data science to predict some of those previously, unpredictable rhythms in engineering. With this, we can more accurately forecast capacity and tie work back to product vision and business outcomes. The “things change” issue becomes a non-issue when you have this level of visibility and have the tools to course correct in real-time. Because we are customer zero, and are building a product for us — one that we actually we use, we are putting ourselves to the test. We have a strong belief that If it doesn’t work for us, it won’t work for our customers.

Competitive Pressure 

Another common reason companies won’t share their roadmap publicly is the fear of competition and someone else getting to market faster with that great idea of yours. I’ve been a part of companies that would hardly let you put screenshots of their product on the website. And demos? Demos were kept under lock and key. We post our demos on our website and on our YouTube channel, no secret passwords needed.  

Is it worth the risk? 

You bet. We are dedicated to our mission of improving the developer experience and because of that, we believe that a rising tide lifts all boats. We welcome conversations with others in the space in order to collaborate on what a better developer experience could look like. 

Because we are a business, we do still have to worry about remaining ahead and we felt that focusing on our own velocity would have a greater impact than simply making it hard to see what we are up to. We recently restructured our teams into full-stack teams in order to maximize efficiency and continuous innovation. We are also hyper-tapped into and prioritize customer feedback. Because of this, we are now able to ship new features and requested enhancements almost every single day. Since making these changes, we have increased velocity 10x which means we can deliver on our roadmap quickly. 

Our Transparent Roadmap 

Starting today you can visit pinpoint.com/roadmap to view the latest plans for our product. You can check our progress along the way on our changelog that is updated almost every day with what’s been released.  This will help our users see where we are going and provide feedback early and often. 

At the end of the day, we want to be the developer’s best friend. We recognize that we aren’t perfect. We will pack our roadmap with all the confidence in the world and still not complete everything — or do it wrong.  If we miss our targets, we want to openly reflect and share how we could have done better.  But we feel strongly that with these principles that are central to how we work — ship every day, prioritize customer feedback, be fail-friendly, put our own product to the test, etc., that we have a good opportunity to make a real impact not just for developers but everyone involved in building software. 

Check out the roadmap, here.  

Have questions? Want to help shape our product? Join our Slack Community. 

Get the data science behind high-performance teams.