Request a Project
Have an idea for something we should build? Submit a project request and a manager will review it. Great requests start with clear answers to what, why, and what success looks like.
What makes a great request?
The best project requests paint a clear picture. Reviewers need to understand the problem you're solving, why it matters, and how we'll know it worked. You don't need a full spec — just enough clarity that someone who hasn't thought about this before can get excited about it too.
Think big picture, not tasks
Projects should represent a high-level initiative or outcome — not individual tasks or features. Keep your project description broad and strategic, then use milestones on the project page to break it down into concrete deliverables and dates. This keeps the roadmap readable and gives reviewers the right level of context.
The Four Questions That Matter
What is it?
Describe what you're proposing. What does the end result look like? Keep it concrete — "a dashboard that shows X" is better than "improve data visibility."
Required for approvalWhy build it?
What problem does this solve? Who is struggling today, and how? This is often the most important question — a well-articulated "why" can make a project obvious.
Required for approvalWhat does success look like?
How will we know the project worked? Think outcomes over outputs. "Teachers spend 50% less time on X" is stronger than "we shipped the feature."
Required for approvalWho is it for?
The primary audience. Be specific — "K-5 teachers in US districts with 500+ students" helps reviewers understand the scale and impact.
HelpfulHow the process works
Fill in the basics
Name your project, pick a category, set dates if you have them, and add any links to relevant docs, designs, or research.
Answer the four questions
Tell us what it is, why it matters, what success looks like, and who it's for. This is what reviewers care about most.
Add detail on the project page
After submitting, you'll land on the project page where you can keep editing — add milestones, risks, contributors, and updates while you wait for review.
A manager reviews & approves
Once approved, the project moves onto the roadmap. The approver becomes the owner and normal editing rules apply — contributors and managers can edit.
Tips for a strong request
Be specific. "Improve search" is vague. "Add filters for grade level, subject, and resource type to the search results page" is actionable.
Link your evidence. Customer feedback, support tickets, analytics — anything that backs up the "why" makes your request stronger.
Think about impact. How many users does this affect? How often? Quantifying the problem helps reviewers prioritize.
It's okay to not know everything. Fill in what you can — you can always add more detail after submitting. Progress over perfection.
Ready to submit your idea?
You'll fill in the project basics first, then answer the four key questions. The whole process takes about 5 minutes.