Why we’re moving Corilla to a public roadmap

The first time I mentioned a public road map I felt the room go silent. I was at a Product Manager event and the topic quickly switched from the usual Gantt charts and spreadsheet banter to how crazy I was for giving away our company secrets.

As you might already know, it turns out that this isn’t such a crazy idea anyway. Companies like Buffer and Monzo are already doing it. And are by no coincidence organisations of good humans too.

There’s certainly something to be said for defensible intellectual property and building a strong business. Corilla is in use by teams in over 85 countries now and we take our responsibility to provide long-term support to our customers seriously. But we also take serious our commitment to community driven development. And that just gets easier with the Corilla public roadmap.

Wait… you mean it’s all… public? 😱

As a product person, I can’t help but feel that this isn’t rocket science at the fidelity of a public road map in any case. Is it any surprise that Corilla is building out a knowledge base, deploying extensive import/export APIs and improving commenting in share link mode?

For this kind of thing it’s not about what we are doing. It’s about what order we are doing it. The secret sauce is in the how. And even then we always prefer working side-by-side with our most active users.

I come from open source, I’ve spent my life exploring content science, why would I want to hide away in a little secret bunker? The same goes for the rest of the team. One of our team values is “better together” after all. That includes being on conversation with you (yes you) too.

So if something as simple as a collaborative public roadmap helps increase our conversation with the community, that’s something we’ll explore. And I hope you’ll join us.

Like what you read? Give David Ryan a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.