Nothing is attributed
Individual responses are never tied to a person, a site, or an agency. Direct quotation is used to preserve practitioner voice, with names and identifying operational details deliberately excluded. Candor requires it.
Approach
We let the field tell us what the data means.
Our research is participant-centered and emergent. Rather than arriving with a framework and looking for evidence that fits it, we let themes surface from what people actually describe, then test those themes against the numbers — and against the people who gave them to us.
Emergent and phenomenological research puts weight on the specific setting and the people inside it. It produces contextual, narrowly tailored conclusions rather than reaching for broad generalizability — which is the right trade when the client is a single district, agency, or funder that has to make one real decision.
In practice this means we do not treat open-ended responses as color commentary around the "real" quantitative findings. Scaled items tell us where to look. Interviews and open responses tell us what we are looking at. When the two disagree, that disagreement is usually the most useful thing in the study, and we report it rather than smoothing it over.
Conclusions are written so they read as authentic reflections of the people who offered their insight. If a superintendent, a director, or a teacher reads a finding and says that is not what it is like, the finding is wrong, regardless of how the numbers came out.
Standing commitments
Five things we hold to on every engagement.
Evaluation is not enforcement
We keep a clear line between analysis and compliance. Standards written to punish get gamed; standards written for reflection and peer comparison get used. We say which one we are building, in writing, before collection starts.
Ranges beat single targets
A benchmark that ignores geography, district size, or delivery model tells a rural director nothing useful. We express benchmarks as peer-group ranges paired with guidance on interpreting local context.
Analysis is reproducible
Calculations are performed with standard, auditable tools and documented so that a third party can follow every step from raw response to reported figure. Methods sections are written to be checked, not skipped.
Plain language, always
Technical accuracy and readability are not in tension. Every deliverable is written with the target audience in mind, so a board member, a program officer, and a practitioner can each find what they need without a translator.
Findings must lead somewhere
Each finding should produce something decidable: a guidance update, a funding recommendation, a procurement specification, a contract appendix, a decision matrix, or a revised definition. Observation without a next step is not a deliverable.
-
Workflow development
Scope, timeline, milestones, and decision points agreed in writing. We inventory what data already exists, identify what has to be collected, and name who signs off on what.
-
Collection and baseline analysis
Instruments designed and administered, existing data assembled, and a first analytical pass completed. This is where the reference point gets established.
-
Preliminary draft
A complete first draft — findings, methodology, and proposed recommendations — written to be criticized and used for iteration.
-
Synchronization with the sponsor
Working sessions with the client and any oversight body to check direction, resolve scope questions early, and surface political or fiscal constraints we need to design around.
-
Field validation
The draft goes to practitioners — including people who participated in collection and people who did not. Structured feedback sessions test whether the findings hold up against daily operating reality.
-
Final report and presentation
Revisions incorporated, final document published to professional standard, and findings presented live to the audiences who have to act on them.
A study that is technically sound and unreadable has failed. Our team members have spent careers summarizing highly technical conversations for boards, cabinets, legislative committees, and staff meetings, and we treat that translation as part of the work rather than an afterthought.
Documents are laid out and designed in- house using industry-standard tools, so a final report looks like something an organization is willing to publish under its own name. Live presentation is included: we present findings live, answer hard questions in the room, and give stakeholders a clear path of action rather than a list of observations.
Decisions should flow from data, to findings, to adaptations someone can actually make.
Next step
Bring us the problem, not the scope of work.
Scoping is easier once we understand the decision. Start with a short call and we will help shape what the engagement should actually be.