Better requires technology that respects the person using it
Software fails in this field for a specific reason: it is designed for the report, not for the clinician at 6:40pm finishing notes.
By Corey Mack · Columnist, What Better Requires
Published July 3, 2026
7 min read

Key takeaways
- Sample column content demonstrating the essay template.
DEMO CONTENT — This entry is sample material created to demonstrate layout and structure. It does not describe real laws, payer requirements, or official guidance.
We talk constantly about making things better. But what does better actually require? In practice, it usually requires something specific and uncomfortable: a decision someone has been avoiding, a system nobody owns, or a standard that was never written down.
This essay looks at technology — not as a slogan, but as a set of obligations. Better requires clarity about who decides. It requires measurement that survives contact with the people being measured. And it requires leaders willing to say what they will stop doing.
Most organizations do not fail at ambition. They fail at sequencing. The work that would actually move the outcome sits behind three other things that felt more urgent, and the urgent work never ends.
The practical test is simple: name the constraint, name the owner, name the date. If any of the three is missing, the improvement is still an intention.
Who this affects
- Technology buyers
- Clinicians
- Product teams
How we sourced this entry
Every report is built from primary documents wherever they exist. Below are the citations behind this entry, their publication dates, and when we last checked them.
Citations
- This entry is analysis and cites no single primary document. It draws on the standing references listed here.
- ReferencePrimary — federal rulemakingFederal Register
U.S. Government Publishing Office · Official daily publication for federal rules, proposed rules, and notices.
- ReferencePrimary — certification bodyBehavior Analyst Certification Board
BACB · Certification requirements, ethics codes, and supervision standards for BCBAs and RBTs.
Publication dates
- Published
Method
- Opinion and analysis. Claims of fact are checked against the references above before publication.
- Dates are recorded as issued by the publishing authority; we re-check status on a rolling basis and log any change in the correction history.
- Corrections are published on the entry itself rather than silently edited.
DEMO CONTENT — This entry is sample material created to demonstrate layout and structure. It does not describe real laws, payer requirements, or official guidance. Citation links point to real public source homepages for demonstration, not to a specific document behind this entry.
Correction history
No corrections have been issued for this entry.
Submit a correction for this entryThis article is general educational information about the Applied Behavior Analysis industry. It is not legal, compliance, billing, or clinical advice, and ABA Command Center is not a law firm. Always consult the primary source and qualified professionals before acting.
Related coverage
Governing AI-assisted documentation without pretending it is neutral
A sample technology analysis on the review structures an organization needs before automated drafting touches a clinical record.
Interoperability is an operations problem before it is a data problem
A sample technology feature on why system integrations fail at the handoff rather than the API.
