Arise Academy inherited a data collection application from a university project team. When the course ended, so did the support. We took the application over, corrected the defects, and gave the staff back nearly four work weeks a year.
Arise Academy received a data collection application built by a student team at South Dakota State University. It was built as a course project. When the course ended, the team ended with it, and the application arrived too late in the year for staff to pilot it and find the flaws before they needed it.
The defects were not exotic. Codes inside the reporting logic were wrong, so the reports would not run. Once staff started using the tool in earnest, they found more. Every one of them was fixable in an afternoon by someone who could read the code. There was nobody left who could read the code.
So the application sat there, complete and unusable, while staff went back to the manual process it was built to replace. That process took 30 minutes per student, across more than 30 students, every month.
“The SDSU team’s course was complete, and they no longer could or would work on it. They did not get it to us in time to pilot and find the flaws.”Brooke Maday · Special Education Teacher and Educational Leadership Intern · Arise Academy
We did not rebuild it. Most of the original work was sound, and the failure was concentrated in a small number of specific defects plus the absence of anyone to correct them. Rebuilding would have cost more, taken longer, and produced the same orphaned tool on a longer timeline.
Instead we read the code, corrected the report logic, worked through the defects staff found in real use, and stayed available for the next one. Each reported issue is confirmed against what the staff actually wanted before the change ships.
“We have found minor flaws, and within a day, Tyler fixes the code. This was the change we needed for data collection, and we are excited to use it this school year.”Brooke Maday · Special Education Teacher and Educational Leadership Intern · Arise Academy
Substitute a job shop and the shape does not change. A co-op student builds a scheduling tool. A retiring planner leaves behind the workbook that sets safety stock. A VAR writes a custom screen during the ERP rollout and moves on. The work is real and the tool is useful, right up until the person leaves and the tool stops changing while the business keeps moving.
We wrote up the full pattern, including what it costs and the four questions to ask about anything you depend on.
What happens to the systems your operation runs on after the person who built them is gone.
Have a system nobody owns? The diagnostic covers the tools your planning runs on, not just the plan.
Book a Planning Diagnostic →