đź‘‹ This template is free to use! Go nuts, make it your own, and go conquer the world. Follow me on the Twitter machine, @Zaney_zaners.
TLDR; It pays to start with a quick TLDR for your own or your teams sanity. With this doc, we’re going to pretend we’re making a document for a vacation. We need one, that’s for sure. Anyways, the template below is a solid place to start curating all things you wish to do with your product and tracking progress along the way. Good luck and happy building!
This is where you can add all the glorious information as to why you need a vacation, where you plan on going, how you’ll get there, and the benefit of going. It’s generally a brief explanation, albeit, longer than the TLDR. We can get into the nitty gritty in a bit so for now, just focus on the typical W questions (who, what, when, where, and the notorious why).
What is the problem you are trying to solve for users or businesses? Let’s get into that here. For us, we’re feeling burnt out, we need to detach ourselves from the normal day to day for a bit in order to feel refreshed and ready to get back to work.
With Job to be done applied, it could look like this:
As a Technical Program Manager, I want to take a break from my work for awhile, to feel refreshed and avoid burn out.
You can also think of it like a techie mad-lib: As _____, I want to _____, so that I can ______
What are the must-dos in order to churn out a usable Minimum Viable Product (MVP)? You’ll see P0, P1, and P2 below. That’s just short hand for ordering priorities.
P0 = Critical | P1 = Important | P2 = Nice to have
What are quantitative or, dare I say, qualitative information are we tracking to ensure this endeavor is a success? It doesn’t hurt to list them out, you could even throw in some aspirational values as goals