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
NowUpdated November 2026
LeadingAssistant principal at John P. Stevens High School
BuildingMain Office Works. Looking for its first schools.
WritingThe latest piece

Noticed

Each of these began with something I saw at school. Pick one. See what I led or built, then what I wrote.

    1 · I noticed

    Built

    Each one began with a job I knew from school. I learn the job first. Then I design the product and build it.

    School operations platform

    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.

    iPhone, Apple Watch and widgets

    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.

    Graduation names

    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.

    Small tools, code kept private

    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.

    In progress

    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.

    All four, with the decisions behind them

    Written

    What a school teaches me about software. What software teaches me about a school. Thirteen pieces so far.

    Built

    Each one began with a job I knew from school. Open any of them for the problem, a decision I made, and where it stands today.

    Main Office Works

    School operations platform · Founder

    Six connected apps for the work that passes through a school office.

    A decision I made
    Connect the handoff, not just the record.
    Where it stands
    Built and ready to demo. Looking for its first outside clients.
    Open Main Office Works

    ClassBell Alarm

    iPhone and Apple Watch · Design and development

    A personal bell schedule that stays with an educator through the day.

    A decision I made
    Make the next bell visible at a glance.
    Where it stands
    Live on the App Store. One-time purchase.
    Open ClassBell Alarm

    myGradVoice

    Graduation names · Product development

    Pronunciation review and ceremony preparation, designed around the person whose name will be called.

    A decision I made
    Keep a sent recording separate from an approved name.
    Where it stands
    Built. Public deployment is paused.
    Open myGradVoice

    Tools for my own school

    Private builds · Google web apps

    Small tools for the everyday tasks around teaching. I share the lesson and keep the code private.

    A decision I made
    Build it in software my colleagues already know.
    Where it stands
    Built for colleagues at John P. Stevens.
    Open the everyday tools

    What I’m building next

    On the bench

    More products are in progress. Each one starts the way the four above did: I learn a job I know from school, then design the product and build it.

    How each one starts
    With the people who do the job, before any screen.
    Where it stands
    In progress. I add each one here when a school can use it.
    Ask me what I’m building

    A school day is connected.Its tools should be, too.

    I live the work I’m designing for. Main Office Works grew from the forms, spreadsheets, emails and handoffs that fill a school office.

    Six apps, one set of school information. Pick an app to follow its handoff. This page explains the product decisions and keeps the implementation private.
    My role
    Founder. Product design and development.
    Built for
    Teachers, office staff, counselors and administrators
    Where it stands
    Built and ready to demo. Looking for its first outside clients.

    The work crosses roles. The context gets lost.

    A teacher submits a referral. A secretary enters a class-cut slip. An administrator reviews a case. The work moves between people, but the information often sits in separate places.

    I built Main Office Works around those handoffs. Shared school information connects the applications, while access reflects each person’s role and school.

    Every button has a person behind it.

    A teacher needs to know that a referral arrived and that it was addressed. A secretary needs to find the right person. A counselor needs the context for a follow-up. An administrator needs to see what still requires a decision.

    Those needs determine what belongs on a page. The design starts with the next action someone can responsibly take.

    Read “A button is a promise”

    From the room to the system.

    School operations also involve time, staffing and budget. A useful platform has to account for the people entering information, the people acting on it, and the people responsible for the result.

    The public walkthroughs show how that thinking becomes a workflow. They demonstrate what the product can do. Schools outside my own using it is the next chapter.

    Read “Building the system our school needed”

    Stay with the class.Keep the time in view.

    A personal bell schedule for educators. The current period, the time remaining and what comes next, wherever a quick glance fits into the day.

    The watch face is counting down as you read this. The phone screens are from the app: the Today view, and widgets on the Home Screen.
    My role
    Product design and development, for iOS and watchOS
    Built for
    Teachers, specialists and librarians
    Where it stands
    Live on the App Store for iPhone and Apple Watch. One-time purchase.

    The timetable changes. Teaching continues.

    Regular days, assemblies, half days and different assignments all change the schedule an educator needs. ClassBell Alarm keeps saved timetables and date-specific changes together.

    The central interaction is a glance: which period is running, how much time remains, and when the next bell arrives.

    Protect the regular week.

    Date-specific schedules handle assemblies and half days without overwriting the usual timetable.

    Meet the moment.

    Widgets, Apple Watch and Lock Screen Live Activities make the schedule available beyond the full app.

    Make behavior clear.

    The notification test checks scheduling. Sound still depends on device, Focus and notification settings.

    Small details. Fewer surprises.

    Educators can follow real clock time or start from the first period now. Halfway reminders, five-minute warnings and end bells support different teaching routines.

    Backup and restore are explicit actions. Analytics are off until a person opts in. The product explains what its indicators mean, so a timer is never mistaken for a recording.

    Read the privacy policy

    A name deservesto be heard correctly.

    myGradVoice connects the preparation behind a graduation announcement: pronunciation, student review, staff approval, and audio ready for the ceremony.

    A sketch of the review loop, with sample data. Ask for a correction and watch the staff side. These are not the product’s real screens.
    My role
    Product development
    Designed for
    Graduates and the staff preparing their ceremony
    Where it stands
    Built. Public deployment is paused.

    Who gets to say whether it sounds right?

    The student can listen to the pronunciation, approve it, or give guidance on a correction. The person whose name will be announced has a say before the ceremony.

    That makes a complete review loop. If a recording changes, the student has to be able to hear the new version and respond to it.

    1. 01

      Hear it.

      The student reviews the pronunciation.

    2. 02

      Confirm it.

      Corrections and approval guide the preparation.

    3. 03

      Have it ready.

      Checked audio travels into the ceremony package.

    Sent does not mean approved.

    Sending an updated recording and approving a pronunciation are different events. Staff need to see both without losing the review history.

    During development I noticed that a follow-up was not visible in the main roster. The design now keeps the review status and the follow-up indicator apart, so staff can tell what happened without opening each record.

    The microphone is live. The Wi-Fi shouldn’t matter.

    The offline ceremony package holds the audio and the tools to play it. Readiness checks flag missing approved audio before export, so the preparation is finished before anyone reaches the podium.

    This describes the workflow as built. It is not a claim about verified ceremony results. The image is concept artwork.

    A small tool can givesomeone their time back.

    Some of my work lives in the everyday tasks around teaching. I share the problems and the choices here, and keep the applications and their code private.

    A sketch of the idea with sample data: one row of teacher feedback becomes one message home. The real sheet stays private.
    My role
    Workflow design and build
    Built with
    Google Sheets and AutoCrat, tools my colleagues already use
    Where it stands
    Built for staff at John P. Stevens and shared at an EdCamp session.

    Teacher feedback, turned into a message home.

    I built a Google Sheets and AutoCrat workflow for staff at John P. Stevens and prepared to share it at EdCamp. It turns teacher feedback into personalized communication for students and families.

    The starting point was staff capacity. Teachers care about keeping families informed, but the work competes with planning, grading and everything else in the day.

    Understand the task. Respect the constraint.

    A useful solution has to fit the time, tools and support available to the people using it. Sometimes that means a focused workflow in software colleagues already know.

    The same attention belongs in a larger product: understand the work, choose what matters, and make the next step easier to take.

    Read “From classrooms to code”

    Written

    Essays, articles and short posts on leading a school, building software for one, and what each job teaches the other.

    Everything I’ve written

    Knowing the person behind the student

    Knowing students beyond their grades, staying connected with families, and recognizing individual progress.

    A student’s interests, experiences and challenges belong in the relationship an educator builds with them. In this article I look at how personal attention, steady contact with families, and recognition of progress can shape a more supportive school experience.

    It is the human side of the operational work. Systems should help educators see and support people, and never reduce them to records.

    Taught

    Before I was an administrator or a builder, I was a teacher. Everything else on this site comes from that.

    Ojas Ray
    Education is where I practice. Understanding people is what I bring.

    A teacher first. A builder because of it.

    To the teacher whose time is already spoken for. To the office trying to keep up. To the student whose name is about to be called.

    Now
    Assistant principal, John P. Stevens High School, New Jersey
    In schools
    Seven years teaching, eight in administration
    Studied
    Ed.D., educational technology leadership
    01

    Where it began

    The classroom taught me to look beyond the plan.

    I came to product development through education. Before school administration, I was a teacher.

    A lesson has a purpose, but its success depends on the people in the room. You need to understand what they already know, where they are getting stuck, and what the next step asks of them. You watch, adjust, and try again.

    I carried that way of thinking into school leadership and, eventually, into software. My doctorate in educational technology leadership gave me another way to study the relationship between learning, leadership and the tools we introduce. The questions stayed practical: who is this for, and what will it help them do?

    02

    A wider responsibility

    A school runs on relationships and follow-through.

    As a high school assistant principal in New Jersey, I work where people’s needs meet the constraints of a school day.

    A teacher needs support. A student needs to be understood. Office staff need information they can act on. A decision that seems simple from one desk can create work for someone else.

    My writing returns to trust and school culture because the systems only work through people. I have written about staying steady when a building is tired, knowing students beyond their grades, and giving teachers the conditions to learn before judging their readiness for a new tool.

    Those responsibilities also shape my product judgment. I want to know what a change asks of someone: more time, another login, a new habit, a different kind of trust. That question belongs near the beginning of the work.

    A standard I hold my work to
    “Every page, every button on that page is intentional.”

    That means being able to explain the person, the need, and the next action behind a design choice.

    03

    Understanding into delivery

    I started building the things I kept wishing existed.

    Main Office Works grew from the disconnected forms, spreadsheets, emails and handoffs I knew from school operations.

    Its six applications bring together work such as coverage, conduct, devices and attendance. My interest is in what happens between people: whether a teacher knows a referral was addressed, whether office staff have the right context, and whether the next person can act.

    When reviewing Teacher Coverage, I questioned duplicate information and controls whose purpose was unclear. Before continuing a redesign, I asked for the application’s actual functionality to be understood. A cleaner screen is only useful if it still serves the work.

    Read the product decisions in full
    A different scale. The same attention. A whole workflow. For one name. myGradVoice takes that thinking into graduation: student review, clear follow-up, and audio prepared for a ceremony. Open myGradVoice
    04

    Beyond one product

    Useful can be small.

    ClassBell Alarm puts a school schedule where an educator can glance at it. A Google Sheets and AutoCrat workflow helps turn teacher feedback into family communication.

    Different scopes, different tools, and the same starting point: understand the task well enough to make it easier to carry out.

    That curiosity travels with me. In Mumbai, everyday experiences with payments, connectivity and delivery became material for writing about useful technology. Education is where I developed this habit of noticing. It is not the only place I want to apply it.

    The context to ask.
    The judgment to choose.
    The persistence to build.

    I’m interested in school leadership and in product or innovation leadership. I bring experience working with people, an understanding of how systems affect their day, and the willingness to carry an idea through the decisions that make it usable.

    Now

    A short record of where my attention is going. Updated November 2026.

    Leading

    John P. Stevens High School

    Assistant principal at a public high school of more than 2,800 students in New Jersey. The daily work is people: teachers who need support, students who need to be understood, and an office that needs information it can act on.

    More about me
    Building

    Main Office Works

    Developing the connected school-operations platform and looking for its first outside clients. The work is also a way to make my product decisions visible: the people, the constraints, and the reason behind each action.

    Open the project
    Making

    A more personal home for my work

    Rebuilding this site around school leadership, the products I make, and writing that comes from actual experience.

    See the work
    Writing

    Starting with a conversation

    Making space to examine a real situation, challenge my first answer, and turn that conversation into a useful article. The archive gathers what I have published while this practice grows.

    Browse the notes

    Hello

    What are you working through? Tell me about your school, your team, or the problem that keeps coming back.

    Let’s start there.

    I’m interested in opportunities to lead people, understand a difficult problem, and carry useful work forward. I bring experience in educational leadership and the ability to take a product from an everyday need through delivery.

    Message me on LinkedIn

    linkedin.com/in/ojasray

    • School leadershipPeople, trust, culture, and the systems that support the work.
    • Product and innovation leadershipUnderstanding users, choosing a direction, designing workflows, and carrying them through.
    • About one of the productsFor demos and support, go to Main Office Works or ClassBell Alarm.

    Hello

    I’m open to two kinds of roles: school leadership, and product or innovation leadership. I bring fifteen years inside schools and three products I have built so far. Tell me what your team is working through.

    Ojas Ray

    A teacher first.

    I came to product development through education. A lesson only works if you understand the people in the room: what they already know, where they get stuck, and what the next step asks of them. You watch, adjust and try again.

    I carried that habit into school leadership and then into software. The school shows me what to build. Building makes me say exactly how the school works.

    Read my story
    Now
    Assistant principal, John P. Stevens High School
    The school
    Public, 2,800+ students, New Jersey
    In schools
    Seven years teaching, eight in administration
    Studied
    Ed.D., educational technology leadership
    Open to
    School leadership, and product or innovation leadership

    Tell me what your team is working through.