02. Ideation & Discovery

What Should You Build?

Table of Contents
In: 02. Ideation & Discovery

Why This Stage Matters

The most successful Open Source projects don’t just solve problems, they solve the right problems for the right people.

Ideation & Discovery is about figuring out what to build and why it matters before you write a single line of code.


Step 1: Find a Real-World Need

Start by asking:

  • Who am I trying to help?
  • What problems do they face regularly?
  • Are there tools that exist but don’t fully solve it?

At Software for Progress Foundation, we focus on ideas that advance:

  • Education (learning, teaching, training)
  • Accessibility (tools for people with disabilities or limited access)
  • Security (privacy, safety, and transparency)

Start here and go deep, not broad.


Step 2: Explore What’s Already Out There

Before you build a new tool, see what’s already been made. Some questions to ask:

  • Are there Open Source projects that already do this?
  • Are they still active? Maintained?
  • Can you build something simpler, more ethical, or more accessible?

This is where your value comes in, not just making something new, but making something better or more approachable.


Step 3: Define Your Project's Purpose

Write one sentence that explains what your project is and who it helps.

“I’m building a simple web app that helps teachers quickly create printable worksheets for students with dyslexia.”

This will be your compass through every other stage.


Step 4: Document Everything Early

Even if it’s just a note to yourself, begin your documentation now:

  • What is the idea?
  • Who is it for?
  • Why is it helpful?
  • How is it different from what’s out there?

At Software for Progress, we’ll eventually help you turn this into:

  • A full project brief
  • A public-facing project page
  • A funding-ready proposal (if you apply for support)

Tips for Good Ideas

  • Simple is better than perfect.
  • “Small but useful” wins over “big and vague.”
  • If you wish you had it, others probably do too.

TL;DR

  • Don’t rush to code - start by solving a real problem.
  • Study the landscape so you don’t duplicate effort.
  • Define a clear purpose for your project.
  • Document as you go, it saves time later.
Written by
Cory Chris
Cory Chris leads the Software for Progress Foundation, helping developers build Open Source tools for education, accessibility, and social good through mentorship and community support.
Comments
Great! You’ve successfully signed up.
Welcome back! You've successfully signed in.
You've successfully subscribed to Software for Progress Foundation.
Your link has expired.
Success! Check your email for magic link to sign-in.
Success! Your billing info has been updated.
Your billing was not updated.