Once I’ve determined what problems to tackle in the near term, I find it useful to create a “one-pager” to synthesize my thoughts around a problem/project. This is after the point where discovery research has been done, and I’ve talked with the team (including tech leads, designers, and another product manager) about the idea.
I’ve listed the sections I found most useful to include, both for myself to confirm it’s a project worth tackling, as well as for the designer to read before they start designing. (Keep in mind, I’m only a few months into being a product manager! But this is what I’ve done so far)
For me, these are to help guide the team as they begin thinking through details; it’s not meant as a functional requirements document, nor should it be overly prescriptive.
Several resources are included at the end of this article; I highly encourage you to check out John Cutler’s article and/or video for some great insights and frameworks around this idea.