Product Product manager
Your product manager.
A teammate who stays close to the product context. Give them ownership of keeping the plan useful, turning discussion into clear requirements, and bringing the right questions back to the team.
See how a hire worksThe questions.
A place on your team
Define their role.
Make it your own.
Your product goals, project pages, feedback, team conventions, and the issues you want the hire to look after.
Help the team keep this product area moving. Maintain the requirements and open questions, follow the relevant issues, prepare status updates, and bring trade-offs or changes in scope back to us for a decision.
A standing product role with the check-ins and areas of ownership you define.
Ongoing responsibilities
A few things they can look after.
Make the requirements useful
Bring shared notes and feedback into a clearer brief. Ask them to develop acceptance criteria, identify unanswered questions, or revise requirements after a team discussion.
Keep the project context current
Read issue activity and project notes, follow the questions you assign, and prepare updates with links to the underlying work. Give them a recurring check-in responsibility.
Prepare the next decision
Ask for a summary of options, dependencies, or a proposed next step. Review the evidence together and update the plan as the team makes decisions.
A clearer picture of what comes next.
Your product manager brings feedback into the plan, keeps the questions visible, and prepares the decisions for your team.
“Finding the right item takes too many steps.”Customer conversation
“Could the filter stay with the view?”Support note
Make the next
search easier.
Bring repeated feedback into a focused proposal, with the questions still attached.
The tools for their role
A connection.
A clear boundary.
Connect and authorize your own accounts, then choose what this hire may read or change. Provider setup and account permissions determine the available access.
Explore tools and permissions- Linear
- Limit the hire to the relevant teams. Read access supports issue and comment checks; creating, commenting on, or changing issues requires write access.
- Notion
- Share the product pages and set root-page limits. Grant write access when the hire should maintain pages or add comments.
- Google Drive
- Read supporting research and planning documents from permitted folders. Drive access is read-only.
The handoff
Useful work.
A person in the loop.
Requirements, decision briefs, project updates, organized feedback, and a maintained set of open questions.
Your team sets product direction and decides priorities, scope, and commitments. Use the hire to prepare and maintain the context for those decisions, with explicit access to the records they may change.
Who would you
hire first?
Sign in to RosterMake a little room on your team.
Good work
has a name.
Start with the role your team needs.
See what a little more team can do.