Explore

Straddle 101 - Internal

Project Template

Keith Raphael

Last edited 103 days ago by Keith Raphael.

Project:

⁠

TL;DR

Quick summary of the problem and how we plan to solve

Problem Alignment

Describe the problem we are trying to solve in 1-2 sentences. I should be able to read this alone and communicate the value/risks to someone else.

Why does this matter to our customers and business?

What evidence or insights do you have to support this?

High Level Approach

Describe the rough shape of how we might tackle the problem. I should be able to squint my eyes and see the same shape. For example, if the problem was “discoverability of new features”, then this might be “a notification center for relevant features”.

Goals

Describe high-level goals, ideally in priority order and not too many.

Include measurable (metrics) and immeasurable (feelings) goals

Keep it short and sweet

Non-Goals

List explicit areas we do not plan to address

Explain why they are not goals

These are as important and clarifying as the goals

Solution Alignment

⁠

⁠

Key Features

The Plan

List the features that shape the solution

Ideally in priority order

Think of this like drawing the perimeter of the solution space

Draw the boundaries so the team can focus on how to fill it in

Link out to sub-docs for more detail for particularly large projects

Challenge the size to see if a smaller component can be shipped independently

Milestones

Future considerations

Optionally list features you are saving for later

These might inform how you build now

Key Flows

Show some mocks/embeds of the experience. Link to any other documentation as necessary. In general, it’s helpful to organize these around certain user journeys / use cases. Show enough of a clickthrough where people can walk away with a reasonable understanding of how the product works.

This will naturally change over time — that’s okay. When changes occur, document them in the Changelog and notify all contributors.