The Pugpig roadmap, and why you can't see (all of) it
Like most product companies, our roadmap is central to how we think and talk about our work. It's how we decide what gets done, when it gets done and why we're doing it. Naturally, we get asked a lot of questions by our customers about what this roadmap looks like, and when they can expect to see features and changes they're looking forward to.
There are many inputs into our roadmap, such as:
- Customer requests or issues
- Internal feedback, suggestions or innovation
- Industry trends
- Usage data
- Changes in iOS, Android or other relevant platforms
- User research
- Policy and legislation changes
These are collated, interrogated and investigated internally, before being planned into a release or placed into the backlog, usually for further investigation or due to a lack of expected impact.
And then there are two main reasons we don't publish a full and detailed roadmap. These are:
Our planned releases usually stretch many, many months into the future, and yet the final versions of these releases often differ dramatically from earlier expectations. The reasons for this are simple, we're constantly learning, and we aren't afraid to change our minds. Unshackling our product releases from promises we've made means we're free to build what we should, not what we said we would.
Software development can be tricky. Pugpig consists of many interwoven systems (your CMSs, our CMS, the apps or sites themselves, subscription services, external tools like analytics or push etc etc etc) and this means things can turn out harder than we thought, or sometimes these services shift under us while we're working on them. We're also deeply committed to only releasing work we believe in which often means a lot of iterations and a lot of QA. Rushing changes out to meet deadlines we set, often a long time ago, does not ensure success.
With that said, we do want our customers to have a sense of some of the high level ideas we're considering, and to get in touch if they have strong feelings about any of them. You can see these here:
Obviously, some changes need a hard deadline. Policy changes and new versions of iOS and Android regularly impose these on us, and critical bugs or crashes might mean you need greater clarity around when they can be addressed. In these cases we're happy to communicate these to you, and keep you abreast of changes to the stated timeframe.
How can we add our input to what you're planning?
Your Customer Success Manager is your first port of call, either by proactively reaching out or in your scheduled reviews. They're your champions inside Pugpig and are in constant contact with the product team.
As always for anything critical or urgent, we ask you to get in touch with email@example.com.