For PMs who got the title, not the training
Nobody Hands New PMs a Project Charter on Day One. So We Did.
The exact documents and user story format senior PMs use, pre-built, so your first project doesn't feel like a guessing game in front of your team.
Functional Requirement Document
AI Prompts
Risk Register
Work Breakdown Structure
Business Requirements Document
Project Plan
Project Charter
for use
It's not a skills gap. It's a documents gap.
You got the offer letter. The Slack invite. The calendar full of meetings with people who already know what they're doing.
Nobody gave you a project charter template. Nobody sat you down and explained what makes a user story "comprehensive" instead of generic. You're expected to already know the paperwork of the job, and you find out what you got wrong in front of your team, not before.
That's fixable in an afternoon, not a certification course.
Case review · User story
As a user, I want a better dashboard so that things are easier.
Note: who is the user? what is "better"? not testable.
As an operations lead, I want to filter the dashboard by branch and date range so that I can report weekly numbers without exporting to Excel.
Note: role named · outcome clear · acceptance criteria attached.
Two PMs, the same missing document.
Meet Ogechi
Ogechi Okafor · 25 · first PM role, fintech
Three weeks in. She has the access, the title, the calendar invites. What she doesn't have is a starting point.
Her manager said "put together a project charter" and walked off to another meeting. She opened a blank Notion page and sat there for twenty minutes before she typed a single word.
She's too new to ask what a charter is supposed to look like without it sounding like she doesn't belong in the room yet.
Meet Juliana
Juliana Ayodele · a few months in · stories keep bouncing
Comfortable with stakeholders, confident in stand-ups. But every sprint her engineers send her stories back. "This isn't comprehensive enough." "What are we actually building here?"
She knows the format. She's followed it exactly. And it keeps getting rejected anyway.
It isn't her. Nobody ever showed her the difference between a story that sounds right and one that's actually buildable.
The failed attempts
- Googled free templates, built for a US corporate context that doesn't map to how projects actually run on their teams.
- Watched YouTube tutorials, good on theory, but you're still left staring at a blank page afterward.
- Asked a senior colleague, helpful once, awkward the fifth time.
- Considered a PM certification course, weeks of study, real money, and still no ready-to-use document at the end.
None of it gave them something to actually open and fill in.
The New PM Trick isn't a course. It's the actual documents.
Already structured the way a senior PM's are, in Word table format, so you're filling in your project's details instead of guessing at a layout. Copy and paste them wherever you work.
For running the project
A Project Charter, Project Plan, Business Requirements Document, Work Breakdown Structure and Risk Register: the five documents that carry a project from kickoff to close-out. Plus an AI Prompt set to fill each one fast from a one-paragraph project description, and a Functional Requirement Document for when engineering needs the detail spelled out.
For writing tickets developers respect
A user story format built around what actually makes a story estimable, not just "as a user, I want", but the specific, testable version of it. Plus acceptance criteria templates, before and after rewrite examples so you can see exactly what changes, and an AI prompt pack for turning a vague idea into a story that survives refinement.
Why AI alone is not enough
AI can help, but only if you already know what "good" looks like. Without an approved structure to feed it, you get confident-sounding drafts that miss the sections your team actually reviews. These templates give you the structure first, so when you do use AI, you are prompting from a finished example instead of a blank page. Banking on just AI might not be it.
What happened next
- Ogechi · Day 1Duplicates the charter template. Fills in her project specifics in an afternoon instead of staring at a blank page for a week.
- Ogechi · Week 1Presents her first project kickoff document. Her director calls it "the cleanest first charter I've seen from someone this new."
- Juliana · Week 3Her next sprint's stories pass refinement first pass. No more three rounds of back and forth with engineering.
"My fiancé noticed I stopped bringing my laptop to bed rewriting tickets at 11pm."
Pick your case file.
Contents
- 01Project Charter
- 02Project Plan
- 03Business Requirements Document (BRD)
- 04Work Breakdown Structure (WBS)
- 05Risk Register
- 06Bonus: AI prompts library for user research, PRD, FRD and a lot more
- 07Functional Requirement Document (FRD)
For PMs, POs and anyone writing tickets
Writing User Stories That Product Teams and Developers Actually Understand
Contents
- 01User story guide (INVEST-checked)
- 02Downloadable format
The guarantee
7-Day "Actually Useful" Guarantee
Duplicate it. Use it on your next real document. If it doesn't fit how your team works, message us within 7 days and we'll help you customize it, or refund you in full, no argument.
Frequently asked
Word table format. Copy and paste them into wherever you work, Word, Google Docs, Notion or Confluence. The user story guide is also available as a download.
Your next project doesn't have to start with a blank page.
Get the documents senior PMs already use and stop finding out what's wrong in front of your team. Delivered instantly after checkout via Selar.