About
Built for the month nobody budgets for.
Teachers privately work on one practice through brief check-ins, 3 times a week by default; leaders see anonymous implementation patterns and a Day-30 report.
The workshop is the beginning, not the product
Schools don't lack ideas; they lack the month of small, private, supported attempts that turns an idea into a habit. That month deserves the same design attention the workshop day gets. It almost never receives any.
Privacy is the mechanism, not a feature
A teacher who believes she's being watched writes for the watcher. Honest reflection requires a boundary leaders cannot cross — so the boundary is enforced in the database, chosen before launch, disclosed to every teacher, and frozen for the cycle.
Evidence says what it is
Self-report is labeled self-report. Activity is labeled activity. Nothing claims to prove practice changed or students improved, because this data cannot support that claim — and a report that overstates its evidence poisons the trust everything else depends on.
Self-serve is a promise about respect
The price is public. The builder works before an account exists. Nothing renews by itself, and no sales call stands between a leader and the decision. Software that respects a school's time earns the right to ask for its attention.
Who’s accountable
PD That Works is built by Yechiel in Boca Raton, Florida — the workshops, the coach, the reports, and every page on this site. Small on purpose: the same person who wrote the privacy promise maintains the database rules that keep it. Questions, corrections, and disagreements all land at hello@pdthatworks.com and get read by a person.
The product runs itself — building a cycle, launching it, and reading the report never depends on anyone’s inbox, including ours. The commitments that bind it are public: teacher privacy, evidence rules, security.
The fastest way to understand it is to use it: Preview a cycle from my PD