Sunsetting DistrictZero. Head Held High.

March 17, 2026

Where This Work Began

DistrictZero started with a very simple idea. If we could understand students as whole learners, we could help them show up with more confidence and less stress. Before there was any product, teachers let me into their classrooms and trusted me with their students. Morning by morning, I learned what helped learners feel supported and what helped them build routines that preserved their energy. That is how I discovered social emotional learning (SEL) and it was at a teacher's desk where I first saw the CASEL framework and finally found a lens that made sense of human development inside education.

DistrictZero began with classroom access and teacher trust.
SEL became the framework that made sense of human development in education.

What We Learned Together

In K-12 classrooms across middle and high school, we helped students build design thinking skills alongside self-awareness and self-management, competencies that aligned with SEL but went beyond it. In higher education, we shifted focus to emotional intelligence (EI): professionalism, interpersonal and team-based communication, and social awareness for graduate and professional learners. The most meaningful milestone was the opportunity to support more than seven hundred students, faculty, and administrators at Loyola Stritch, where we demonstrated measurable improvements in human wellbeing and efficiency through a research-validated study. At each step, DistrictZero grew because an educator, researcher, or administrator took a chance and asked for something better than reactive support.

In K-12 we built design thinking, self-awareness, and self-management skills aligned with SEL.
In higher and graduate education we focused on EI: professionalism, interpersonal and team communication, and social awareness.
Supporting over seven hundred people at Loyola Stritch was our most meaningful milestone.

What Broke the Camel's Back

Technology performance. The infrastructure was built in 2020 around a React and Node stack, microservices, and AWS. Over roughly six years of enterprise product-market-fit crawl and experimentation, we kept maintaining and refactoring, maintaining and refactoring. We had real wins: we migrated the frontend to Vercel deployment, which improved speeds; we moved to messaging queue systems that helped performance; we did database indexing that helped performance. But we could not migrate the whole stack. There were simply too many Lambda functions to move over to new infrastructure or a better database. That was the key bottleneck. When we improved the wellness alert system and moved it to version two in 2025, users found real value. But as data grew on the enterprise side, data loading became harder. We could no longer deliver the performance that our highest-usage users needed. They were a small segment, but the most important one. Not edge cases. The performance issues hit exactly the people who relied on the platform most. We did not have the resources to fully transform and rebuild the stack. Margins were negative. We were not hitting profitability. The tough decision was to hand off from our key partner and set them up for success as they continued the advisory program we had designed together. That was the straw that broke the camel's back.

We had wins (Vercel frontend, messaging queues, database indexing) but could not migrate the full stack; too many Lambda functions became the bottleneck.
Wellness alert v2 delivered value, but performance degraded for high-usage users who needed it most.
Without profitability or resources to rebuild, we handed off to our key partner to continue the advisory program we co-designed.

Why The Mission Must Evolve

Technology moves fast, especially agentic workflows and the tools people actually want to use. But enterprise education, especially in highly regulated spaces like higher ed and medical education, operates differently. It requires patience, capital, and the ability to sustain long sales cycles. It needs broader support teams and environments where compliance is non-negotiable. What end users and customers need now is often quite different from what these institutions can realistically adopt. That gap is real, not a failure of anyone involved. Meanwhile, my own curiosity kept pulling me toward the cognitive science behind burnout and the engineering challenges that could measure and predict it. That shift asked for a different path and a different way to contribute.

Technology and end-user needs evolve quickly; enterprise education moves at a different pace.
Higher ed and medical education require patience, capital, long sales cycles, and compliance, legitimately.
My curiosity shifted toward burnout research and predictive engineering.

The Next Chapter

My interest is in human productivity and cognition. Timekeepur Labs is the agentic research and development factory I am building to improve metacognition, the ability for humans to plan and build sustainable systems that drive impact. Not more developer tools or technology that clutters the space. I want to ground decisions in live signal, benchmark ideas against the people and sources shaping a field, and turn research into build-ready plans so the same system that gathers context can help pressure test direction, clarify tradeoffs, and prepare work for the tools teams actually use.

This direction grows out of questions that have followed me for a decade: how routines shape energy, how environments influence behavior, and how burnout can be addressed through better planning, preparation, and understanding oneself. It is not enough to understand our challenges. We need pathways, even clinical pathways, to diagnose, resolve, and grow. That is the lens I am bringing into Labs.

Timekeepur Labs focuses on metacognition and sustainable systems that drive impact, not tools for the sake of tools.
How routines shape energy and how burnout is addressed through planning, preparation, and self-understanding.
Pathways, including clinical pathways, to diagnose, resolve, and grow, not just identify challenges.

Working With Teams At The Edge Of Performance

I want to work as close to the atoms as possible. That means infrastructure teams, hardware teams, or any team where human impact is the measure of success, not downloads, engagements, or vanity metrics. Building software or technology is not the difficult part. What is difficult is finding teams that work on real impact and that enable agency, where cross-functional teams can actually work together at the edge of performance. I am open to selective advisory or consulting work with teams like that, particularly where cognition, automation, and human performance intersect. I am interested in helping teams form ML programs, validate models responsibly, and design systems that support humans under real constraints. These are the environments where my background in product, engineering, and behavioral systems comes together most naturally.

I want to work close to atoms: infrastructure, hardware, or teams where human impact is the KPI.
Not downloads or engagements. Real impact. And teams that enable agency and cross-functional collaboration.
Open to advisory work where cognition, automation, and human performance meet.

With Gratitude

To the team members who contributed in any capacity, thank you. Your commitment and creativity allowed DistrictZero to deliver value long before there was a budget big enough to justify the effort. To our finance and capital partners, thank you for providing belief and support when the world was uncertain. To our pilots that were difficult, I am grateful for the chance to try and I hope our paths cross again with renewed clarity. To Loyola University Chicago Stritch School of Medicine and the Department of Medical Education, thank you for trusting us as a design partner. You helped shape this work into something that mattered for real people in real situations.

DistrictZero taught me what education makes possible when we invest in humans. It taught me that well being must be designed into learning environments, not treated as an afterthought. Most of all, it taught me that building systems of care is a collective effort. Thank you for being part of it.

Thank you to team members, partners, pilots, and Loyola for making DistrictZero possible.
DistrictZero taught me that well being must be designed into learning environments.
Building systems of care is a collective effort.