Embedded Design: A Guide for Builders

Embedded design is RTP's core methodology for building relational tech. It inverts the typical software development process.

The Inversion

Traditional: Identify problem → Design solution → Build → Ship → Get users Embedded: Be in community → Notice what's needed → Build with neighbors → Iterate together → Tool earns its place

Before You Build Anything

1. Spend time in the place. Walk the neighborhood. Go to events. Be a

neighbor first, a builder second.

1. Listen for recurring themes. What do people wish existed? What's hard?

What's beautiful?

1. Map what already exists. There are always existing assets — people,

spaces, channels, traditions. Build on these, don't replace them.

1. Find co-builders. If you can't find at least one person who wants to

build this with you, you might be solving the wrong problem.

While You Build

1. Build the smallest useful thing. Not an MVP — a "minimum relational

thing." Something that creates one connection that didn't exist before.

1. Test with real neighbors, not personas. The people on your block, at

your café, in your group chat. Real feedback from real relationships.

1. Let the tool earn its place. Don't promote it. Let it spread through

the relationships it serves. If people share it, it's working.

1. Stay accountable. The 1:100 ratio means you know the people using what

you build. You see them at the store. This accountability is a feature.

Design Principles

• Simple over feature-rich
• Accessible over sophisticated
• Local over universal
• Accountable over scalable
• Open over proprietary
• Remix over replicate

Common Mistakes

• Building in isolation, then "launching" to the community
• Optimizing for growth instead of depth
• Adding features instead of deepening relationships
• Assuming digital = better
• Copying what worked elsewhere without local adaptation