Some school problems need a conversation. Some need software. I do both
I’m an assistant principal at John P. Stevens High School in New Jersey, a public school of more than 2,800 students. I have designed and built three products: Main Office Works, ClassBell Alarm and myGradVoice. I’m building the next ones now.
- Seven years teaching
- Eight in school administration
- Ed.D., educational technology leadership
Noticed
Each of these began with something I saw at school. Pick one. See what I led or built, then what I wrote.
Built
Each one began with a job I knew from school. I learn the job first. Then I design the product and build it.
Main Office Works. Six connected apps for the school office, built from the forms, spreadsheets and handoffs I worked with every day.
Built and ready to demo. No outside schools yet. I’m looking for the first.
ClassBell Alarm. A personal bell schedule for educators: the current period, the time left and what comes next.
Live on the App Store. One-time purchase.
myGradVoice. Students listen to how their name will be read and approve or correct it. Staff see who still needs follow-up. The audio plays without Wi-Fi.
Built. Public release paused.
Tools for my own school. One turns teacher feedback into a personal message to each family. I shared it with colleagues at an EdCamp session.
Built for staff at John P. Stevens.
What I’m building next. More products are on the bench now. Each one starts the way the four above did, with a job I know from school. I add them here when a school can use them.
Building now.
Written
What a school teaches me about software. What software teaches me about a school. Thirteen pieces so far.

