This doc outlines basic steps and tips to take an idea to high-level spec for estimation — this is essentially how an idea will make it on the roadmap.

Idea Pitch & Rationale

Articulate why this idea is valuable to the business and Users. Use supporting data to validate and de-risk this idea to prove its value.

Prioritize this idea against others in your product backlog to make sure its worth the team’s time to illustrate and estimate this idea. (development must be likely to fall into the next Q+2).

Note: product ideas can come from anyone but PM is responsible for documenting and prioritizing it.

Illustrate

Gathering with your product Triad (UX, Eng. and PM) complete a fat marker sketch sessions to determine the following aspects of your project.

• Where in the current system does the new thing fit?
• How do you get to it?
• What are the key components and interactions?

<aside> ⏰ Example Sketching Agenda

1.5 hour session MAX

• 10 mins - Establish the problem
• 5 mins - Set guardrails
• 10-15 mins - Individual sketching
• 30 min - Discussion
• 15 min - Merge/choose a winning sketch
• 15 min - Document decisions
• Add Sketches and Decisions to Rationale for estimations </aside>

Deliverables

• Rationale
• Product Sketches
• High-level phases and identified rabbit holes

This will be used to assist in team estimation sessions.

Next Steps