I did not begin with an organization chart. I kept following problems.
Sometimes the problem needed a tool. Sometimes it needed a map, a public record, or a better account of who was responsible. The projects looked different because the questions were different.
Over time, a recurring move became visible: look at how a system is represented, go see what happens, understand the difference, and make something useful from what you learn.
Giving the work a home.
Groundtruth 911 is the public-safety expression of that practice. The Aggregation Point also has a home here as a vendor-neutral practitioner community. Groundtruth can hold technical tools, investigations, and shared learning without requiring every output to become a product or every question to become a business.
Portland TRAP stays a transportation accountability project. The Portland Porch stays a place to explore Portland. Their connections are useful when they help the work; they do not need to become one brand.
The next responsibility.
I want to finish the work I start and be clear about what I can keep maintaining. That means agreeing on what we can take on, paying contributors when the resources are there, and leaving a public record of what changed.
The architecture is catching up with the work. It should make the next question easier to follow, and the useful result easier to leave in other people’s hands.