Skip to content

Impact

We measure what changes, not what happens.

Attendance tells you who showed up. Workshops delivered tells you what we did. Neither tells you whether anyone became more capable. HxDF's framework asks ten questions of every program, from a baseline, with the discipline to publish only what we have earned. Today every one of them is a planned measure. None is a measured outcome.

The framework · Planned measures

Ten questions, asked of every program.

Reach and participation are the least interesting ones. The rest are what a funder, a parent, and a student actually want to know.

  1. 01

    Reach

    Who participated?

    Examples
    Students, families, and organizations served; who they are and where they are.
    How it is measured
    Enrollment and partner records.
  2. 02

    Participation

    Did they complete?

    Examples
    Cohort completion, project completion, mentor engagement, staff training completion.
    How it is measured
    Program records.
  3. 03

    Learning

    What did they understand?

    Examples
    Can explain how a system works; can identify an unreliable claim or a scam.
    How it is measured
    Short pre and post assessments, scenario based.
  4. 04

    Capability

    What can they now do?

    Examples
    Directs an AI tool and verifies the output; maps a workflow; designs controls.
    How it is measured
    Project rubric, demonstrated task performance.
  5. 05

    Creation

    What did they build?

    Examples
    Working workflows, prototypes, documented projects, portfolio entries.
    How it is measured
    Project artifacts reviewed against a standard.
  6. 06

    Application

    Where did they apply it?

    Examples
    A solution in use by a real organization; a charter a family actually follows.
    How it is measured
    Partner confirmation, followup check ins.
  7. 07

    Operational impact

    What changed for an organization?

    Examples
    Staff hours saved, response time improved, followup completion, steps removed, staff confidence.
    How it is measured
    Before and after assessment per project.
  8. 08

    Opportunity

    Did another door open?

    Examples
    Internships, mentors, scholarships, continued study, a next project.
    How it is measured
    Followup survey at 6 and 12 months.
  9. 09

    Resilience

    Did safer practices improve?

    Examples
    Stronger verification habits, documented risk controls, safer sharing and privacy choices.
    How it is measured
    Scenario assessment, pre and post; family and partner observation.
  10. 10

    Longitudinal growth

    What changed over time?

    Examples
    Repeated capability assessments; portfolio growth; retention across program years.
    How it is measured
    Repeated assessment; later, student owned records in the Digital Home, with consent.

Why this framework

Because a certificate is not a capability.

Most youth technology programs can tell you how many students enrolled and how many finished. HxDF's model only works if a student can do something afterward that they could not do before, and if an organization runs differently because of the work. So that is what we measure.

Capability shows up as demonstrated work: a workflow blueprint someone else could follow, a tested solution delivered to a partner with a before and after number, an AI error caught before it did damage, a family charter a household actually follows. Each of those can be observed, rubric scored, and repeated over time.

Longitudinal growth is the category most programs cannot measure because the relationship ends when the program does. The Student Digital Home is designed to change that, with the student’s consent and ownership. How that works.

The proposed pilot

Six commitments, six kinds of proof.

Proposed targets and the proof each one requires. Nothing here is a result.

  1. Audits

    Deliver the first audits to small community organizations, at no cost to them.

    Proof Problem category, priorities recommended, delivery time, and what the organization did in the ninety days after.

  2. Blueprints

    Scope a Blueprint from an audit, build it, transfer it, and follow up.

    Proof Baseline and post measures, implementation effort, staff participation, and whether staff can run it alone afterward.

  3. Tools

    Ship the first free public tools, starting with the Family Digital Charter Builder.

    Proof Real usage, how far people get, and where they stop. Usage is reach, not impact, and is reported as reach.

  4. Published learning

    Publish anonymized field notes, including the work that did not go well.

    Proof Notes that name what failed, not only what worked. A learning organization that only publishes wins is not one.

  5. Economics

    Document actual hours and direct costs per audit, per Blueprint, and per tool.

    Proof Unit costs a funder can test, replacing the round numbers every early organization is tempted to use.

  6. Students

    No cohort in year one. A small apprenticeship only if the safeguarding, mentor, partner, and project readiness gates are met.

    Proof Gates documented as met or not met. Not meeting them and saying so is a valid year one result.

  7. Funding

    One anchor sponsor and targeted foundation conversations.

    Proof A clear cost model, sponsor renewal logic, and funder feedback.

Evidence discipline

Six rules we hold ourselves to.

  1. 01

    Baseline before launch

    Assessment instruments exist before the first session. If we cannot measure it, we do not claim it.

  2. 02

    Dated evidence

    Every published figure carries a date, a cohort, and a method. No rolling totals with no denominator.

  3. 03

    Permission first

    Stories, quotes, photos, and organization names appear only with written permission for the specific use.

  4. 04

    Small and credible

    Year one reports a handful of measures done well, not a dashboard of vanity metrics.

  5. 05

    Cost per outcome

    Cost per participant and per nonprofit intervention are calculated and shared with funders, not hidden.

  6. 06

    Failure counts

    What did not work is reported alongside what did. Reflection is part of the model, including ours.

Every project's evidence package

What each completed project leaves behind.

Assembled without compromising participant privacy, and the raw material for every report HxDF publishes.

  1. 01Before and after problem statement
  2. 02What was delivered
  3. 03Who benefited
  4. 04Measured result
  5. 05Partner quote, where permission exists
  6. 06Photo or video release, where applicable
  7. 07A concise impact story
  8. 08Lessons learned

Measured outcomes

Nothing yet. That is the point.

This is where measured outcomes will live, separately from planned measures. The first pilot report follows the first cohort and the first nonprofit projects. Project stories will appear with permission. Until then, this section stays empty rather than filled with placeholders.

  • First pilot reportAfter the first cohort and nonprofit projects complete
  • Cohort reportsPer cohort, for sponsors and partners
  • Project storiesAs projects complete, with partner and participant permission
  • Cost per outcomeWith the first annual report

No reports exist yet. Each one will be listed here with its date, cohort, and method.

Fund the evidence

A proof of model year is the cheapest credible test of whether this works.