Public-interest technology, data, and research
rhizae is an independent practice combining software development, data systems, research-informed analysis, and communication for organizations working on public-interest problems.
Its current experience is strongest in technology and implementation. That foundation is extending into applied research, policy analysis, measurement, and decision systems through independent work and pilot partnerships.
The condition
Organizations often have research, data, institutional knowledge, and lived experience. The difficulty is connecting those inputs to the decisions people need to make.
The problem is often not a lack of information, but a lack of usable systems for connecting evidence to decisions, communication, implementation, and learning.
Capabilities
rhizae's strongest current experience is in software development, technical systems, product implementation, and applied technical problem-solving. That foundation is extending into public-interest research, data strategy, measurement, policy analysis, and evidence communication.
Delivered in prior roles and independent projects, with work available to review.
Being tested and documented through independent projects and pilot partnerships.
Each engagement is scoped to the question, available evidence, organizational context, and level of specialist expertise required. Limits are made explicit, and specialist collaboration may be recommended.
The difference
rhizae brings principles from software development, technical systems, and applied problem-solving into public-interest work. The questions that make a technical system reliable also shape the developing research practice: who uses the result, what it assumes, and who maintains it.
Projects and applied work
rhizae is early in building its public-interest research portfolio. The work here includes independent research, demonstration projects, and technical work completed before or outside rhizae. Each item states whether it is client work, independent work, or a demonstration.
Technical research
A technical investigation comparing three recommendation approaches on the same dataset, which found that the evaluation metric could not separate them.
Completed and reviewed. Recommends fixing the evaluation before selecting a model.
Technical research and experimentation
Demonstration prototype
A prototype examining how inconsistent definitions, spreadsheets, and recurring reporting tasks could be reorganized into a maintainable workflow.
Shows a proposed structure and deliverables; not yet implemented with a client.
Reporting and decision systems
Independent research
An exploratory project examining how program measures can be connected to recurring staff decisions rather than selected mainly for compliance reporting.
Available for further testing and adaptation with a pilot partner.
Program measurement and learning
Portfolio sample
A demonstration brief that synthesizes evidence, identifies affected groups, distinguishes findings from assumptions, and documents uncertainty.
Demonstrates a developing approach to research synthesis and evidence communication.
Policy research and analysis
Approach
The work starts by defining what must be understood, who will use the result, and what decision it supports. Methods, tools, and deliverables follow from that context rather than setting the direction from the start.
Define the question, decision, audience, constraints, responsibilities, and existing knowledge.
Select research, technical, analytical, evaluation, or discovery methods that fit the question.
Connect findings to context, tradeoffs, uncertainty, and possible implementation.
Develop the report, system, tool, prototype, or workflow needed to put the work to use.
Document the work, clarify ownership, and support the people who will maintain it.
Who we are
rhizae began from experience in software development, technical systems, product work, and applied problem-solving. That foundation is applied to public-interest questions where research, data, technology, and communication need to work together. The research practice is still developing, so established experience is kept distinct from emerging capability, and collaborators are brought in when a project needs expertise beyond that scope.
Pilot partnerships
rhizae is accepting a limited number of pilot partnerships with organizations that have a defined technology, data, reporting, measurement, research, or evidence-communication problem.
Pilot projects are intentionally narrow. They apply established technical experience while testing and documenting newer approaches to research and decision support.
Each engagement begins with a defined question, scope, and responsibility structure. Methods, assumptions, limitations, and ownership are documented as part of the work.
A pilot may produce a prototype, technical assessment, research memo, reporting workflow, data model, visualization, or decision tool.
If your organization is working through a research, data, reporting, or technical question, rhizae can determine whether it fits current capabilities or would require additional expertise.
