When I was recently asked to support programming, it wasn t the kind of programming most people associate with tech it was something completely new to me: building a master schedule for an entire school.

My first reaction? A mix of curiosity, excitement and honesty.

Transparency First

I was upfront: I had never built a master schedule before. It s a complex process that impacts every student, teacher, and department. Starting with honesty helped set the tone for real collaboration.

Learning the System To understand our landscape, I:

• Pulled data and built dashboards to make sense of trends, needs, and course demands
• Met with stakeholders to learn our strengths, challenges, and opportunities
• Asked a lot of questions because good programming starts with understanding, not assuming

Defining Roles & Elevating Expertise

One of the most important things I clarified is that I am not the subject-matter expert in transcript auditing or graduation requirements. Our expert counselors, case manager, ELPT, IB coordinators, CTE leads, and admin play a critical role in ensuring that our schedule is compliant and aligned with student needs.

Programming isn’t just about placing classes in periods. It s about navigating:

• DL and EL service requirements
• IB and CTE pathway needs
• Teacher load and staffing constraints
• Student interest and course demand

That’s why shared ownership is essential.

Building a Transparent, Collaborative System

The work is leading to:
• A clearer workflow for enrollment and schedule changes
• Department input that directly shapes course offerings
• A timeline that keeps everyone aligned on where we are in the master schedule build
• And most importantly, a process where students have more voice and choice in their learning

Leveraging My Skill Set

Even though the task was new, I realized I had strengths that could support the work:

• Systems thinking – seeing how all the moving parts (courses, staffing, pathways, requirements) fit together
• Data analysis & dashboard building – pulling reports, creating tools, and making complex info easy to interpret
• Workflow design – streamlining messy processes into clear, repeatable systems
• Cross-team communication – bringing together admin, counselors, teachers, case managers, and partners
• Project management – creating timelines, coordinating tasks, and keeping everyone aligned
• Tech integration – building tools in Sheets, Apps Script, and dashboards to automate and simplify the work
• Problem solving under constraints – thinking creatively when resources, staffing, or requirements get tight

These skills helped me build a foundation even while I am learning the programming side from scratch.

The Outcome

We re moving toward a system that is transparent, collaborative, and student-centered one where expertise is honored, data guides decisions, and students are empowered to shape their educational path.

Not the programming I expected.

But exactly the kind of programming that builds stronger schools.