<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>Writing by Dr. Ojas Ray</title>
<link>https://www.ojasray.com/writing</link>
<atom:link href="https://www.ojasray.com/feed.xml" rel="self" type="application/rss+xml"/>
<description>Essays, articles and short posts on leading a school, building software for one, and what each job teaches the other.</description>
<language>en</language>
<lastBuildDate>Mon, 16 Nov 2026 12:00:00 GMT</lastBuildDate>
<item>
<title><![CDATA[Count the people who show up]]></title>
<link>https://www.ojasray.com/writing/count-the-people-who-show-up</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/count-the-people-who-show-up</guid>
<pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
<category><![CDATA[Leadership]]></category>
<description><![CDATA[Two years of tracking late arrivals taught me to read the rest of the spreadsheet.]]></description>
<content:encoded><![CDATA[<p>For two years, part of my job was tracking staff attendance. When someone came in late, I was the one who sent the email.</p>
<p>Nobody asks for that job.</p>
<p>The system started with staff. Teachers told us that some of their colleagues were late often, not once in a while, and that the people who arrived on time were picking up the slack. We listened, and we built a plan.</p>
<h2 id="fair-and-human">Fair, and human</h2>
<p>People are late for real reasons: a car accident, a tree across the road, a sick child, a medical appointment. Anyone who has sat in traffic watching the clock knows lateness isn’t always a choice.</p>
<p>So the plan had to hold two things at once: accountability for a pattern, and patience for a bad morning.</p>
<p>Every late got a short email from me, from the first through the fifth. Each one was a heads-up and a record, never a gotcha. Only a fifth late went further, and only when the lates came close together. Four lates before November and a fifth in May was life, not a pattern. A few people needed follow-up meetings, and we had them.</p>
<p>None of it was formal discipline, and none of it was comfortable. Telling a colleague they were late feels awkward every time, even in an email. I did it because the staff who raised the concern deserved to know someone had listened.</p>
<h2 id="the-rest-of-the-sheet">The rest of the sheet</h2>
<p>Tracking lateness means spending months looking at the exceptions, the same few names in red. After a while, you start to believe that’s the whole picture.</p>
<p>Then one morning I looked at the entire sheet. The overwhelming majority of our staff were in the building before 7:15, day after day. Nobody had ever thanked them for it, because nobody had been looking.</p>
<p>I had been keeping a list of who was late. The same data held a much longer list: the people who showed up.</p>
<h2 id="saying-thank-you">Saying thank you</h2>
<p>I started small. Anyone who was on time for 25 or more days in a month got a thank-you, and each month I recognized the top ten early birds in a small contest.</p>
<p>It can sound unnecessary. These are adults, and nobody needs a gold star for coming to work. But I think almost everyone wants to be seen, adults included.</p>
<p>It changed the work for me, too. I still sent the late emails and still sat in the hard meetings. But every month I was also thanking dozens of colleagues, and the thank-yous far outnumbered the reminders.</p>
<h2 id="read-your-data-both-ways">Read your data both ways</h2>
<p>Any system built to catch problems is also recording what’s going right. Discipline logs, missed deadlines, failing grades: we set them up to surface the red, because red needs action. The green is usually the bigger share, and we rarely look at it.</p>
<p>If you lead people, whether it’s a school, a company or a team of four, take the data you already collect and read it the other way. Who never appears on it? Who is always on time, always the one who covers? They hold the place up, and they’re the easiest people to forget, because they never give you a reason to think about them.</p>
<h2 id="small-wins-add-up">Small wins add up</h2>
<p>I used to save celebration for big moments, like test scores or the last day of school. Now I think the ordinary wins matter more. Walking in at 7:10 on a rainy Tuesday in February isn’t remarkable. A year of those mornings, from dozens of people, is what keeps a school running.</p>
<p>Accountability matters, and those emails were worth sending. But accountability alone tells people what you’re watching. Acknowledgment tells them what you value. Most of us practice the first and forget the second.</p>
<p>This week, look at something you track for problems and find one person it shows doing the right thing. Tell them you noticed. It costs nothing, and it may be the first time anyone has.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[A button is a promise to the person using it]]></title>
<link>https://www.ojasray.com/writing/a-button-is-a-promise</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/a-button-is-a-promise</guid>
<pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
<category><![CDATA[Product thinking]]></category>
<description><![CDATA[What a Teacher Coverage redesign taught me about asking better questions before making a screen look better.]]></description>
<content:encoded><![CDATA[<h2 id="start-with-the-office-not-the-screen">Start with the office, not the screen</h2>
<p>Teacher coverage looks straightforward from a distance. Someone is absent. Someone else covers the class. In a school office, that decision sits among phone calls, visitors, changing schedules, and the rest of a morning that has already started.</p>
<p>When I reviewed a redesign of Teacher Coverage in Main Office Works, I kept returning to the same questions: What happens when someone clicks this? Where does the information appear? What does this control actually do?</p>
<p>Those questions came before approval of the design. A screen can look organized while leaving its user unsure of the next step. I wanted the person working in the main office to understand what they could do without having to interpret the interface.</p>
<h2 id="a-second-date-does-not-create-more-clarity">A second date does not create more clarity</h2>
<p>One of my comments was about a repeated date. The date was already visible on the left. I asked for a calendar and date picker there instead of showing the same information again.</p>
<p>It is a small example, but it captures how I review a product. Repetition takes up attention. If a control occupies space on a busy screen, it should earn that space by helping someone understand something or take an action.</p>
<p>The same scrutiny applies to buttons. A label that sounds useful is not enough. I need to know where it takes the person, what information they will find, and whether another control already does the same job.</p>
<h2 id="understand-the-product-before-redesigning-it">Understand the product before redesigning it</h2>
<p>As the designs improved, I asked for a read-only discovery of the actual application. I wanted its purpose, functionality, and workflows understood before more pages were redesigned.</p>
<p>That matters in school operations because a detail that looks inconvenient to a designer may represent a real constraint. Availability, assigned periods, special schedules, and coverage requirements affect the decision the office can make. Removing that context can make a screen cleaner and the work harder.</p>
<p>My role is to bring the school day into the product conversation. I know the work from inside a school, and I still need to inspect the specific workflow rather than assume that familiarity answers every question.</p>
<h2 id="the-standard-i-bring-to-a-team">The standard I bring to a team</h2>
<p>I want designers, developers, and the people doing the work to be able to explain the same interaction in plain language. What problem does it solve? What does the person need to know? What happens after they act?</p>
<p>That is how I try to make intentionality concrete. It is visible in the question asked during a review, the duplicate removed, and the decision to learn more before shipping a polished misunderstanding.</p>
<p>The redesign discussion is evidence of how I make product decisions. It is not a claim that a new layout has already saved a measured number of hours. That answer comes from watching people use it.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Getting a name right takes more than a recording]]></title>
<link>https://www.ojasray.com/writing/getting-a-name-right</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/getting-a-name-right</guid>
<pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
<category><![CDATA[Building]]></category>
<description><![CDATA[The decisions behind myGradVoice: a student’s chance to correct a pronunciation, a staff member’s next action, and a ceremony that should not depend on Wi-Fi.]]></description>
<content:encoded><![CDATA[<h2 id="before-the-name-is-called">Before the name is called</h2>
<p>A graduation name is a small piece of audio with a lot attached to it. The student will hear it. Their family will hear it. The staff member running the ceremony needs to know that the right recording is ready when it is needed.</p>
<p>I built myGradVoice around that whole sequence. There is work before the ceremony: collecting information, preparing a pronunciation, giving the student a chance to listen, reviewing corrections, and getting the approved audio ready for playback.</p>
<p>Generating a recording is one step. The product also has to make room for the person whose name it is.</p>
<h2 id="let-the-student-hear-the-result">Let the student hear the result</h2>
<p>The review flow gives a student an opportunity to listen and approve the pronunciation or provide correction guidance. That keeps a decision about their name connected to them.</p>
<p>A correction creates another responsibility. When an updated recording is sent, the student needs a way back into review. A confirmation screen from their earlier response should not prevent them from hearing and responding to the newer version.</p>
<p>This is the kind of detail that becomes obvious when you follow the person through the process. An email can be sent successfully while the experience that follows it is still incomplete.</p>
<h2 id="the-staff-view-has-to-tell-the-truth">The staff view has to tell the truth</h2>
<p>During development, I noticed that sending an updated recording did not make the follow-up clear in the main roster. The record still showed its review status. I could not tell from that view that a new recording had been sent.</p>
<p>The distinction mattered. The progress of the review and the fact that a follow-up message was sent describe different things. One should not erase the other.</p>
<p>The design discussion led to a separate follow-up indicator alongside the existing status. Staff should be able to see that information where they are already working, without opening every record to reconstruct what happened. It is a small piece of interface with a specific job: help someone know what still needs attention.</p>
<h2 id="prepare-for-the-room-where-it-will-be-used">Prepare for the room where it will be used</h2>
<p>The ceremony workflow includes an offline package containing the audio and the tools needed to play it. The preparation happens before the event, so the plan does not rely on the venue having a usable internet connection at the podium.</p>
<p>Readiness also needs a clear meaning. An approval without playable audio is not enough. The workflow checks for approved audio and identifies missing pieces before export.</p>
<p>These decisions are part of the product, even when they are less visible than a generation button. They connect the student’s review, the staff’s preparation, and the person responsible for playback.</p>
<h2 id="what-this-work-asks-of-me">What this work asks of me</h2>
<p>My school experience makes me attentive to the handoffs. My product work asks me to turn that attention into an interface, a rule, and a way to check that the rule holds.</p>
<p>I want to carry both perspectives into a team: understand what a moment means to a person, then work through the details that make the moment possible.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[A tool for the Tuesday-night workload]]></title>
<link>https://www.ojasray.com/writing/a-tool-for-the-tuesday-night-workload</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/a-tool-for-the-tuesday-night-workload</guid>
<pubDate>Sat, 02 May 2026 12:00:00 GMT</pubDate>
<category><![CDATA[Building]]></category>
<description><![CDATA[A Google Sheets and AutoCrat workflow turns teacher feedback into personalized family communication, built to share with colleagues at EdCamp.]]></description>
<content:encoded><![CDATA[<p>Family communication matters, and the time to do it is often missing. I built a workflow in Google Sheets and AutoCrat for staff at my school, and prepared to hand teachers a ready-to-use version at an EdCamp session.</p>
<p>It is a small example of designing around staff capacity: start with an everyday task, use tools people already have, and make the result something a colleague can take back to their own work.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[The ordinary work of holding a school together]]></title>
<link>https://www.ojasray.com/writing/holding-a-school-together</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/holding-a-school-together</guid>
<pubDate>Mon, 23 Mar 2026 12:00:00 GMT</pubDate>
<category><![CDATA[Leadership]]></category>
<description><![CDATA[Steadiness, tone, and the small decisions that still matter when everyone in the building is running low on energy.]]></description>
<content:encoded><![CDATA[<p>The week before a school break shows a quieter side of leadership. Coverage, attendance, behavior and surprises keep coming even when people are exhausted. This post is about staying present and calm through those ordinary demands.</p>
<p>Culture shows up in daily behavior: how a leader responds when the work is repetitive and the room is tired.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[AI integration, from the assistant principal’s chair]]></title>
<link>https://www.ojasray.com/writing/ai-integration-from-the-principals-chair</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/ai-integration-from-the-principals-chair</guid>
<pubDate>Wed, 18 Mar 2026 12:00:00 GMT</pubDate>
<category><![CDATA[Leadership]]></category>
<description><![CDATA[The useful conversations about AI happen close to the classroom, where a teacher has a specific problem and a leader has time to listen.]]></description>
<content:encoded><![CDATA[<p>School leaders shape the conditions in which teachers try something new. In this article I draw on everyday coaching conversations to look at four of those conditions: shared beliefs about learning, support that arrives when it is needed, leaders who practice in the open, and tools that fit the pace of a school day.</p>
<p>It is also a product argument. A tool’s value depends on the working conditions around it, so adoption starts with understanding those conditions.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Before measuring readiness, build the conditions]]></title>
<link>https://www.ojasray.com/writing/conditions-for-teacher-ai-readiness</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/conditions-for-teacher-ai-readiness</guid>
<pubDate>Wed, 18 Mar 2026 12:00:00 GMT</pubDate>
<category><![CDATA[AI & education]]></category>
<description><![CDATA[Protected time, clear expectations, and visible leadership practice are part of teacher readiness, too.]]></description>
<content:encoded><![CDATA[<p>A readiness score can put the responsibility on one teacher and miss the conditions around their work. In this post I ask leaders to check three things first: whether teachers have time to learn, whether there is a shared picture of good practice, and whether the adults leading the building are practicing too.</p>
<p>Make adoption possible in daily work before judging whether teachers are prepared.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[The distance between the product and the classroom]]></title>
<link>https://www.ojasray.com/writing/product-and-classroom-reality</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/product-and-classroom-reality</guid>
<pubDate>Thu, 29 Jan 2026 12:00:00 GMT</pubDate>
<category><![CDATA[Product thinking]]></category>
<description><![CDATA[Seven years teaching and eight in administration shape a practical view of what school software needs to understand.]]></description>
<content:encoded><![CDATA[<p>A product decision looks different when the person making it has stood in a crowded passing period, lived on a teacher’s short break, or watched a system fail just as the day begins. In this post I make the case for putting people with school experience on the teams that design educational products.</p>
<p>The skill that transfers is judgment about context: knowing an environment well enough to build something useful inside its limits.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Building the system our school needed]]></title>
<link>https://www.ojasray.com/writing/building-the-system-our-school-needed</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/building-the-system-our-school-needed</guid>
<pubDate>Wed, 16 Jul 2025 12:00:00 GMT</pubDate>
<category><![CDATA[Product thinking]]></category>
<description><![CDATA[Paper referrals and scattered emails became the starting point for a student-conduct system built from inside the school.]]></description>
<content:encoded><![CDATA[<p>This is the account of a school operations problem turning into a product. I built a central conduct system for my own school, a building of more than 2,800 students. It brings incident reporting, a view for each role, case histories and follow-up into one place.</p>
<p>Closing the loop with staff is part of the design, because a referral is also someone’s time and effort. The article describes my own school. It is not a claim that other schools have adopted Main Office Works, which is still looking for its first outside clients.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Noticing useful technology in everyday life]]></title>
<link>https://www.ojasray.com/writing/noticing-useful-technology-in-everyday-life</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/noticing-useful-technology-in-everyday-life</guid>
<pubDate>Sun, 10 Nov 2024 12:00:00 GMT</pubDate>
<category><![CDATA[Beyond school]]></category>
<description><![CDATA[A visit to Mumbai prompted observations about connectivity, digital payments, delivery, and the design of daily convenience.]]></description>
<content:encoded><![CDATA[<p>My curiosity about useful systems goes beyond schools. During time in Mumbai, ordinary experiences with mobile connectivity, payments and delivery became a way to think about access and friction.</p>
<p>It is the habit behind my product work: notice how technology fits into ordinary life, and ask what made it easier.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[From classrooms to code]]></title>
<link>https://www.ojasray.com/writing/from-classrooms-to-code</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/from-classrooms-to-code</guid>
<pubDate>Mon, 28 Oct 2024 12:00:00 GMT</pubDate>
<category><![CDATA[Product thinking]]></category>
<description><![CDATA[What curriculum planning, learner feedback, and classroom assessment can contribute to building better products.]]></description>
<content:encoded><![CDATA[<p>Teaching offers useful ways to think about product work. In this article I connect clear learning objectives with product direction, stakeholder participation with user research, and continuous classroom assessment with iterative testing.</p>
<p>It is about how experience in one field can sharpen judgment in another, while the people using the result stay at the center.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Leadership before the title]]></title>
<link>https://www.ojasray.com/writing/leadership-before-the-title</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/leadership-before-the-title</guid>
<pubDate>Tue, 24 Sep 2024 12:00:00 GMT</pubDate>
<category><![CDATA[Leadership]]></category>
<description><![CDATA[Initiative, follow-through, trust, and helping colleagues grow are leadership behaviors available at any level.]]></description>
<content:encoded><![CDATA[<p>Leadership can start before formal authority. This piece describes the choices that earn influence: taking responsibility, contributing useful work, listening, keeping commitments and supporting colleagues.</p>
<p>The weight is on consistent behavior and the quality of working relationships, more than on a position in an organization chart.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Knowing the person behind the student]]></title>
<link>https://www.ojasray.com/writing/knowing-the-person-behind-the-student</link>
<guid isPermaLink="true">https://www.ojasray.com/writing/knowing-the-person-behind-the-student</guid>
<pubDate>Thu, 05 Sep 2024 12:00:00 GMT</pubDate>
<category><![CDATA[School culture]]></category>
<description><![CDATA[Knowing students beyond their grades, staying connected with families, and recognizing individual progress.]]></description>
<content:encoded><![CDATA[<p>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.</p>
<p>It is the human side of the operational work. Systems should help educators see and support people, and never reduce them to records.</p>]]></content:encoded>
</item>
</channel>
</rss>
