Articles

Insights and updates for music teachers

Introducing Octavia: The Next Chapter for My Music Studio

My Music Studio is becoming Octavia. This update explains why the name is changing, what it means for the platform, and what remains the same for teachers already using it.

March 10, 2026

A music studio calendar and lesson schedule

Studio Practice

Music Lesson Makeup Policies Explained: Pros, Cons, and Sustainable Choices

Seven common makeup lesson policy models, with the real trade-offs and a few practical ways to keep boundaries without losing goodwill.

February 7, 2026

A computer, metronome, music whiteboard, and dice, with a post-it note saying deploy.

Updates

Introducing the News feature

A News feature in Octavia that helps you publish announcements to families, collect responses, and track who has replied — all in one place.

January 7, 2026

A calm, minimal hero image representing reduced admin friction for music teachers (e.g., an uncluttered desk with a lesson notebook and calendar).

Product Design

Reducing Friction So Things Get Done

Design decisions that reduce admin friction for teachers and parents, so routine studio work actually gets done.

January 5, 2026

A screenshot of a dashboard with lesson times, performance times, and exam times for a teacher to view their schedule in.

Updates

What Is Octavia Designed to Do?

Octavia was built to reduce the admin load of running an instrumental studio by keeping lesson notes, scheduling, attendance, events, communication, and billing connected in one place.

December 26, 2025

A teacher working through lesson notes with integrated tools, showing teaching-first software design.

Product Design

What Makes Octavia Different

Rather than competing on feature lists, Octavia is designed around teaching workflows, long-term trust, and learning-focused decisions that support real studio practice.

December 26, 2025

Product Design

Why the Teacher App Isn’t Optimised for Phones

The teacher app handles dense, high-stakes admin work where context and precision matter. A desktop-first design reduces risk, avoids partial-mobile inconsistency, and supports targeted mobile use only where it’s low-risk and bounded.

December 23, 2025

Product Design

Designing Public Access Without Public Accounts

Families want to watch and share student performances easily — but education software can’t treat access casually. Octavia uses invitation-based, bounded access so viewing stays simple without becoming public or requiring accounts.

December 23, 2025

Abstract illustration representing accountability and privacy balance.

Product Design

Audit Logging: Accountability Without Over-Collection

A clear explanation of how audit logging can support accountability in education software without over-collecting data or creating unnecessary privacy risks.

December 23, 2025

A calm, professional music studio setting (hero image to be added).

Studio Practice

The 10 policies every good music teaching studio should have

A practical menu of policy options across cancellations, billing, payments, practice, communication, materials, etiquette, performances, and teacher absences—so you can choose what fits your studio and apply it consistently.

December 23, 2025

Illustration showing a student login gated by school-scoped consent and activation, with separate checks for identity, consent, and access.

Product Design

Designing Safe Student Access in Music Education Software

A conservative, school-scoped approach to student access that separates identity, consent, and platform eligibility—so access is explicit, auditable, and reversible.

December 22, 2025

Illustration of separate identity models for teachers, parents, and students, with the teacher app remaining untouched.

Product Design

Why We Refactored Identity Without Touching the Teacher App

How we added parent and student support by linking role-specific identities to authentication—without risking the production teacher app’s legacy assumptions and security constraints.

December 22, 2025

Page 1Next