Skip to content
Matthew Sazma
Menu

For organizations

Define the decision before you build the solution.

I work with teams when an idea matters, the evidence is incomplete, and forward motion requires more than another brainstorm.

Discuss the decision

Engagements

A defined question. A bounded piece of work.

Final scope follows a first conversation. These are useful starting shapes, not rigid packages.

01

Engagement

Problem and Product Discovery Sprint

A team with a promising idea that is not yet sure it solves the right problem.

The question underneath

Whose problem is this, what do they actually do today, and what is the smallest test that would tell us whether we are right?

Possible outputs

  • Stakeholder and user interviews
  • Workflow and burden mapping
  • An assumption and risk inventory
  • A review of competing approaches
  • Definition of the smallest useful test
  • A short product and research decision brief
02

Engagement

AI Evaluation and Human-Oversight Design

A team with an AI workflow that needs evidence, failure boundaries, and meaningful human control.

The question underneath

What is this system claiming, how would we know if it were wrong, and where does a person need to stay in the loop?

Possible outputs

  • A claims and evidence audit
  • A high-severity failure taxonomy
  • Benchmark and test-set design
  • Abstention, uncertainty, correction, and confirmation rules
  • A human-in-the-loop workflow review
  • Pilot-readiness recommendations
03

Engagement

Research-to-Pilot Strategy

A researcher, nonprofit, or early product team moving from an interesting concept to responsible field testing.

The question underneath

What outcome are we changing, how would we measure it honestly, and what result would make us stop?

Possible outputs

  • A theory of change with measurable outcomes
  • A formative user-research plan
  • Pilot design with go/no-go criteria
  • Grant or competition narrative development
  • An evidence and decision ledger
  • Findings communicated for technical and nontechnical audiences

How the work moves

01

Frame

Name the decision, the people affected, and the assumptions already doing hidden work.

02

Investigate

Gather the smallest amount of behavioral and technical evidence that can change the direction.

03

Design

Turn what we learned into a workflow, test, or pilot with explicit failure boundaries.

04

Decide

Leave with a recommendation, an evidence trail, and clear conditions for moving or stopping.

Evidence, not adjectives

Inspect the work before you hire it.

All selected work
01

2025

Proposal and methodology

TwinSight

Winning entry in a NIST-funded national challenge on turning smart-city digital twin data into decisions people can act on.

02

2025–present

Working prototype

Assistant to the Caregiver

An early-stage Android application testing whether low-friction capture and caregiver-reviewed AI can reduce the bookkeeping burden between medical appointments.

Behind the work: a PhD cognitive psychologist who led the team that won a NIST-funded national challenge.More about Matthew.

A clear boundary

What this work is not.

This is not legal, clinical, regulatory, cybersecurity, or compliance work. I can help design the evidence and human-oversight rules around a system; establishing that it is compliant or secure requires a practitioner in that discipline.

Start with the knot, not a polished brief.

Tell me what you are trying to learn, build, or decide. I will tell you plainly whether I am useful, what I would need to know, and what a sensible first piece of work looks like.

Start a conversation

Here as a student?Research coaching for students.