Skip to content
Problem Commons

Bring us a problem.
We'll bring the people.

The world has no shortage of problems — only a shortage of people willing and capable of solving them, across disciplines, borders, and status. Submit a problem — anyone, anywhere.

The loop

01

Submit

Anyone, anywhere, brings a problem to the table.

02

Understand

Is it real? Who is affected? What's been tried, and what's missing?

03

Assemble

Find the disciplines the problem actually needs.

04

Lab

A small team researches, designs, prototypes, and tests in the wild.

05

Validate

Does it work outside a document?

06

Deploy

Can it be implemented where the affected people are?

07

Impact

Who benefited, what changed, what we learned.

08

Share

Open the knowledge — where appropriate.

No problem in, no loop. A loop without deployment is a study group. Deployment without learning is a one-off.

The commons

Anything published here was brought by a real person, reviewed by a human, and marked public with consent. Each one shows where it is, how far it has come, and what has already been tried.

Loading problems…
How problems are handled

Every submission gets a human answer. Nothing marked private is published, quoted, or shared.

Framed

It is real — who lives with it, what has been tried, and what is missing are clear enough to work on. A framed problem joins the loop and is published on this board, with the submitter's consent.

Parked

Real, but not taken up right now. It gets a written reason and stays on the record rather than being left to rot unanswered.

Declined

Not ours to take on — unsafe, out of scope, or already being moved by someone credible. A warm decline with a reason, because an unanswered submission is a broken promise.

Becomes a Lab

Framed problems become Labs: small teams that research, design, prototype, and test in the wild — then deploy where the affected people are. Stage 10, what worked and what failed, is mandatory.

If submissions outpace reviews, we close intake honestly rather than let them rot unanswered. An unanswered submission is a broken promise. A closed door is not.

What we promise

“Submit your problem and Build For Good will solve it.”

“Submit a problem. Build For Good will help determine whether, how, and with whom it can be meaningfully worked on.”

The capacity rule

  • Every submission is framed, parked, or declined with a reason.
  • If submissions outpace reviews, we close intake honestly rather than let them rot unanswered.
  • An unanswered submission is a broken promise. A closed door is not.
How we choose

Voting picks popularity, not importance. A meme with 14,000 votes would bury a rural healthcare problem with four. So we weigh every submission on:

Severity

How bad is it for those living it?

People affected

How many, and how underserved?

Urgency

Does delay make it worse?

Neglectedness

Is anyone credible already on it?

Feasibility

Can small teams actually move it?

Expertise available

Do the needed disciplines exist near us?

Testability

Can we measure whether a solution worked?

Scalability

Could it help far beyond the first site?

Safety & ethics

Could working on this harm anyone?

Framed problems become Labs — small teams that research, design, and build. See how that work runs in our weekly and monthly rhythm.

Lifecycle

  1. Submitted→
  2. Reviewed→
  3. Framed→
  4. Research→
  5. Lab forms→
  6. Prototype→
  7. Pilot→
  8. Deployment→
  9. Impact→
  10. Learn

Paused and archived are honest endings. A closed problem with a written reason beats an abandoned problem with a green badge. Stage 10 — what worked, what failed, what the next team should know — is mandatory.

Want to be one of the people we bring? That is what membership is for.

Submit

Describe it plainly. Who lives with it? What does it cost them?

Make it concrete — "fewer families boiling unsafe water", not "fix the water".

The interdisciplinary angle, a neglected corner, a research gap.

Local knowledge counts as expertise. You may be the most valuable person on the team.

Optional — add one if you'd like a reply.

Who should be able to see this?

Your problem is read by the people reviewing submissions. Public problems may appear in the Problem Commons; “review only” and “private” never do, and nothing private is published or quoted. An unanswered submission is a broken promise — every one gets a human answer within 72 hours.