Intro As a Product Manager, I’ve tried a lot of techniques and frameworks to product vision and the team and stakeholders on what needs to be done, why, and when. Some of the techniques gave great results and others were a complete mess. Over the years, going through that trial and error process enabled me to identify techniques with fantastic results and ditch the other ones that were just a waste of time. communicate align That’s how I came up with the HAMMER Product Planning Kit. WTF is HAMMER Product Planning Kit? Well, HAMMER stands for: ypothesis H nalysis A apping M ethodology M ngineering E oadmap R Forgive me, but I had to name it somehow, it IS a tool after all… So, what is it? is a directory of resources to help you understand and execute product planning. It is organized in several abstraction layers. Starting from a high-level business perspective, and then gradually drilling down to technical details. The final result is a shared vision, development plan, roadmap, based on the knowledge from all the documents included. HAMMER Product Planning Kit This kit consists of 5 major documents: Product Vision Board (Hypothesis Analysis) Platform Overview (Mapping) Functional Specification (Methodology) System Design (Engineering) Roadmap Product Vision Board Product Vision Board is a high-level overview of the product (business layer). It provides product vision, description of the users, their needs, and required features to fulfill those needs. This is a strategic document, that should be used as a guide for setting goals and initiatives. It acts as the overarching goal guiding everyone involved in the development effort. This will help you understand why are you building the product, who are you building it for, and what is the expected business outcome. to align on high-level project goals. This will help you prioritize work. What contributes to the goal is important, and other features not contributing to the goal will be postponed and de-prioritized. Also, understanding users and their needs will help you and your team in solving challenges by creating tailored solutions. Why is this document important: Platform Overview This document provides a high-level overview of the product that you are building. It describes the business process behind the app and each step in that process. This is a place where you describe the user journey, workarounds, friction points, and everything that will contribute to the understanding of the user’s steps. But to get there, first, you need to interview your users and test your hypothesis defined in the Product Vision Board. : to understand end-to-end scenarios (users’ journey) for each role, and to understand the information architecture and business flow for each of the features. This will be a starting point for the development team to break down work items into epics. Understanding the process will help the team in making decisions and building better solutions. Why is this document important Functional Specification This document describes the application and all its features (application layer). These features should map exactly to the needs described in the Platform Overview document. Functional Specification contains feature descriptions as well as high-fidelity mockups and UX flows. : Why is this document important To let the developers know what to build. To let the QA engineers know what tests to run. To let stakeholders know what they are getting. System Design This document contains a set of tasks (tactics) to achieve the goals described in previous documents. It contains a list of all technical tasks, user stories, job stories and C-diagrams with an architecture overview. : this gives a clear picture of the architecture, product design, modules, interfaces, and data for a system to satisfy specified requirements. Essentially, this will help you build your product backlog with work items. But with all the work done so far, each work item will clearly contribute to your vision and user needs, since each work item is derrived from there. Why is this document important Roadmap This document contains a high-level delivery plan with proposed delivery milestones - versions. Each version has a “What’s on the box” section which describes what will be delivered to end-users, with emphasis on outcomes rather than outputs. Also, there’s a list of objectives and tasks required to achieve the goal for each version. : The document will be used as a development guide, ensuring the team is always working on high-value - high-priority tasks. Also, this will help us keep track of the progress and measure success. Why is this document important What to do with this? You did an amazing job gathering all the information, understanding your users, aligning with your team and stakeholders. You’ve covered all five layers of abstraction, and five phases for roadmap development. Phase Document Layer Discover Product Vision Board Business Define Platform Overview Information Conceptualise Functional Specification Application System Design System Design Technology Plan Roadmap Timeline Now, share these documents with your team members, stakeholders, managers, and everybody that you find appropriate. Look back at everything that you gathered and acknowledge the huge value captured in these documents. This will help you and your team to build an amazing product since everybody is aligned on what needs to be built, and more importantly why it needs to be built. Having a sense of purpose will give you a huge advantage and motivation. Where can I learn more? Everything mentioned in this article (and more) is part of the Notion template that I created for myself. It’s pretty useful for new projects, where you have the entire structure laid out, ready for you to start rocking. You can find the template . here I use this concept for each new project. It helps me understand what needs to be built and why. Having this in written helps me communicate product plan with team members and stakeholders. As a result, everybody is aligned, motivated and contributing to the shared goal. This Notion template will help you: Create your product hypothesis and understand user needs Let your team know what to build and why are they building it Let your stakeholders (investors)  know what they are getting Good luck!

Flow

"All of my successful projects were the ones where I overcommunicated everything"

4 Templates For Product Owners Looking To Write Great User Stories

Check out my productivity tools

Nominated for 2022 - HackerNoon Contributor of the Year - Agile Software Development

Nominated for 2022 - HackerNoon Contributor of the Year - Freelancing

Nominated for 2022 - HackerNoon Contributor of the Year - Project Management

Nominated for 2022 - HackerNoon Contributor of the Year - Communication

Nominated for 2022 - HackerNoon Contributor of the Year - Product Development

Too Long; Didn't Read

Boost your HackerNoon story @ $159.99! 🚀

How To Use My HAMMER Notion Template To Nail Product Planning

How To Use My HAMMER Notion Template To Nail Product Planning

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Agile35 cards which will improve your backlog refinement process and engage every team member

10 Things Every Beginner Indie Hacker Should Know

10 Features Where Coda Is Better Than Notion

4 Notion + Zapier Integrations You Can Implement Today

5 Reasons Hacker Noon's New Brand Guidelines are Good News for You Too

Agile35 cards which will improve your backlog refinement process and engage every team member

10 Things Every Beginner Indie Hacker Should Know

10 Features Where Coda Is Better Than Notion

4 Notion + Zapier Integrations You Can Implement Today

5 Reasons Hacker Noon's New Brand Guidelines are Good News for You Too

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps