Keys to Success in Platform-as-a-Product: Roadmaps
Welcome to the first installment in a series on the key success factors in developing an internal platform-as-a-product. I will be outlining several straightforward strategies to begin this journey, starting with the use of roadmaps.
In defining a platform as a product, our objective is to build solutions for our users or customers, rather than for our internal purposes. This involves identifying and understanding user needs and pain points, then creating a platform that addresses these needs, rather than merely automating our existing tasks.
One crucial aspect of operating a platform as a product is communication, with roadmaps serving as a primary tool in product management.
In the world of tech support teams such as platform teams, there is often a significant backlog of tasks from various sources that constitute the team’s workload. Relying solely on these tasks can result in:
Limited stakeholder engagement
Prioritization based on the loudest voices, potentially misaligned with business objectives
User confusion regarding future platform developments and timelines
Possible duplication of tasks
Moreover, when we solely focus on addressing requests, we limit our ability to make a positive impact on the business. Without understanding the reasons behind these requests, we risk missing broader problems that need resolution.
So, what’s our goal with the platform-as-a-product approach?
We strive to understand customer (user) needs and develop features that cater to those needs.
We aim to boost stakeholder engagement and align with business priorities.
We seek to enhance the company’s overall effectiveness.
By focusing on our users, we can address holistic problems rather than sifting through tickets to find common issues to solve.
A backlog can be a beneficial tool:
Transparent backlogs facilitate dialogue among stakeholders, users, and the team.
Backlogs shift the perception from partners and the team’s mindset from being task providers to feature producers.
Backlogs aid in prioritization across the organization.
A backlog can improve platform efficiency by focusing on the development of what is needed.
Publishing a roadmap is a useful initial step:
Publishing a roadmap for the platform is relatively easy.
It can begin as a series of milestones from your task backlog.
This simple act of communication can initiate many opportunities for meaningful discussions.
By publishing a backlog, one of the most powerful aspects of product management is set in motion: opening dialogue with the customer. It also fosters stakeholder engagement by quickly indicating whether the platform aligns with business goals, or if changes are required.
However, bear in mind the limitations of this approach:
Publishing a roadmap doesn’t automatically shift your orientation towards a product-centric approach.
A cultural change is necessary for this transition.
Once conversations begin, you must strategize on how to take full advantage of them.
Putting a roadmap out there means you must be ready for feedback and possible alterations.
A public roadmap is an excellent tool to kick-start discussions with users and stakeholders. However, it’s important to be ready to alter plans, shift mindsets, and initiate a cultural transformation.
Here are some resources to learn more about product roadmaps:
Atlassian: Product Roadmaps
The Product Manager: How to Create a Product Roadmap
AltexSoft: Product Roadmap Tips
HubSpot: Product Roadmap
In conclusion, roadmaps are a critical tool in product management. The traditional approach to technology platform work involves maintaining a large backlog of task-oriented requests. Publishing a transparent roadmap can boost engagement and initiate a shift in perception and mindset. Although a simple first step towards the platform-as-product approach, it’s just one of many, and limitations must be acknowledged. In future posts, we will delve into topics such as user discovery, self-service, prioritization, and more.
