<aside> ⭐
This roadmap is crafted to inspire teams to think from the perspective of the problem, with a clear focus on understanding the WHY behind each initiative. By establishing this foundation, we aim to visualise what success would look like, setting a purposeful direction for our work. From there, teams can break down these core problems into actionable initiatives and build features—the tangible solutions that end-users will engage with.
</aside>
<aside> ⭐
User stories are also provided, giving teams the flexibility to pursue frameworks such as Jobs to Be Done (JTBD), or other methodologies that suit their needs. Should teams require additional operational tools, there’s an option to add a URL column in the database to link external resources seamlessly.
</aside>
The roadmap is organised into three primary layers, each serving a unique role:
The Teams database is our foundation—consider this as the first layer. It enables comprehensive reporting at any given moment, ensuring a unified, team-centric view across all functions.
The second layer encompasses Problem Statements and Success Metrics. These databases articulate the core WHY of our objectives, grounding our efforts in clear problem definitions and success measures.
By leveraging Notion’s relations and rollups functions, we can pull insightful data from Problem Statements, enhancing visibility into how these outcomes align with our strategic purpose.
The third layer comprises the Initiatives, Features, and User Stories databases. These are the outputs that drive outcomes by influencing user behaviour or meeting business needs.
This roadmap is intended to make teams think from they Problem perspective focusing on the WHY and how success would look like. Later on, we should try break down these problems via initiatives and crafting delivering features that are the tangible things our end-users will use. Also, user stories have been added and left room to decide Ither you want to pursue JobsToBeDone (JTBD) or others. It can also happen that you want to handle so much operational work in another tool, so feel free to add a Url column on that db.
The Main Homepage offers a high-level overview of all information, giving stakeholders a big-picture view. HoIver, this is not intended for day-to-day work. Each team should operate within their respective Team Homepages (e.g., Team 1 ). These pages feature quick-action buttons, enabling teams to easily create:
It is highly encouraged to document user stories directly within the relevant features to maintain clarity and context. With this structure, we’re setting the foundation for teams to build and deliver impactful solutions in a methodical and engaging way.