Complex public problems involve many people with only a piece of the answer.

If the tools you already use are working for aligning people across roles or getting at the messy human problem you’re trying to solve, then keep using them. people.to.policy is not a substitute for being present with the complexity others are trying to navigate.

Our value is when time is short, cost is constrained and you need to understand quickly how diverse stakeholders are experiencing an urgent problem that is now an organizational priority: what’s broken from where they sit, how they’re already working around it and what they think would help.

The questions draw on more than ten years of service and systems design in complex organizations. Everyone gets the same questions in the same order regardless of role. Every answer gets read back before the conversation moves on. People say things out loud they won’t write down, especially when the interviewer confirms what they said and moves on without judgment. The knowledge that comes back is operational: workarounds already in use, friction no one filed a ticket about, fixes quietly working in one corner that could work everywhere.

Findings arrive as a short deck & a spreadsheet your team can act on, showing where different roles agree, where they diverge and what people are already doing to make things work. No sorting through raw responses. No extra analysis steps.

There is no substitute for relationships. people.to.policy helps when you can’t afford to wait for them to tell you what’s wrong.

No one is asked for their name, birthday or anything identifying. If someone shares something identifying by accident, we do not capture it. We ask people for their role (frontlines, operations, community partner, client, customer) to give the project team context for the groups of people touching the problem. Callers can choose not to answer any question.

Callers are told immediately they are speaking with an automated system. Audio and transcripts are deleted within 30 days except where required by law. Data stays on US-based servers. We never share it with third parties or use it to train AI models. A people.to.policy team member may review audio alongside its transcript only to verify the system is working correctly, never to identify who is speaking.

We keep anonymized coded responses and the findings spreadsheet: no names, no identifying information, nothing that connects a response to a specific person or organization. We keep these to improve our methodology over time and to identify patterns across engagements. Partners choose upfront whether anonymized aggregate findings or anonymized quotes can be shared publicly in blog posts, conference presentations or case studies. We never identify any organization or individual.

The spreadsheet your team works from is yours to edit and use however you need.

That is a real concern and your organization knows your context best. We can help you think through how to introduce the call and whom to reach out to first. Trust starts with how you invite people to share.

We also encourage your organizational leaders to call in first. They experience exactly what everyone else will and review their own findings among each other. Then they can share their experience with everyone else they ask to participate, but not what they said. What leaders understand about the blockers, causes and workarounds compared to what people across different roles actually experience becomes a helpful benchmark. Those overlaps and gaps are an important part of what people.to.policy surfaces.

We are in our pilot phase. We have tested and refined the interview methodology over more than ten years inside governments. The automated system is new. That is exactly why we are looking for the right pilot partners: to prove it together and document what works.