Reflection

What designing an AI learning-plan generator taught me

A first-person look at the instructional-design decisions behind the platform — why personalization at scale is the problem worth solving, and why the right answer keeps the AI in the role of assistant and the educator in the role of author.

Why personalization at scale is the central problem

I have watched too many teachers know exactly what a student needs and have no way to act on it for everyone at once. Individualized learning is not a mystery of pedagogy; it is a problem of time and arithmetic. A genuinely personal plan takes hours, and no one has hours times a hundred and fifty. So I started here deliberately: the central instructional-design problem of our moment is not whether we can personalize — it is whether we can personalize for every learner at a scale a human can sustain. Everything else in this build is downstream of that question.

Designing AI as a planning assistant, not a decision-maker

The most important design decision was a refusal. I would not build a system that decides for students. The AI here does the exhausting first-draft work — synthesizing evidence into a complete plan with goals, strategies, supports, and enrichment — and then it stops and hands the pen back. The educator reviews, edits, and approves. I kept asking myself one test: if this recommendation is wrong, who catches it? As long as the answer is "a professional who knows the child, before anything reaches the student," the design is sound. The moment the AI could quietly act on a learner, it would stop being an assistant and start being a risk.

Explainability and educator approval

A draft an educator cannot interrogate is a draft they should not trust, so I made rationale a first-class citizen rather than a footnote. Every recommendation carries why it surfaced and which evidence informed it. That serves two purposes: it lets a teacher weigh the suggestion against what they know firsthand, and it makes approval a real act of judgment instead of a rubber stamp. I came to see explainability and approval as a single mechanism — transparency is what makes human oversight more than a formality.

UX for warmth and student voice

It would have been easy to render a child as a dashboard of scores. I worked hard not to. Every plan opens with the whole learner and the student's own strengths, interests, and preferences, and the visual system is intentionally warm — encouraging, calm, framing learners by possibility rather than deficit. I wanted a teacher to feel, opening a plan, that they were meeting a person. Student voice is not decoration here; it is an input the plan is built around, because a plan a student recognizes as theirs is a plan they will actually own.

Integrating MTSS and UDL into software

Personalization without proven structure is just improvisation, so I built the platform on practice educators already trust. MTSS gives the plan its tiers — universal, targeted, intensive — with ownership and timelines, and UDL shapes the recommendations themselves toward multiple means of engagement, representation, and expression. Translating those frameworks into software taught me to treat them not as compliance checkboxes but as the grammar of a good plan: the same engine that scaffolds a struggle should stretch a strength, and barriers should be designed out from the start rather than retrofitted.

What it demonstrates

This build is evidence of a particular point of view: that responsible AI in education means drafting and explaining, never deciding; that personalization at scale is achievable when software does the heavy first-draft work and humans keep authorship; and that a scalable individual-learning-plan system can be warm, transparent, equitable, and grounded in MTSS and UDL all at once. It is a demonstration of instructional design and enterprise edtech thinking applied to the hardest version of the personalization problem.

What this demonstrates about responsible, scalable ILP systems

Stepping back, the platform argues that the tension people assume — between scale and care, between AI and professional judgment — is largely false when the roles are drawn correctly. AI can carry the volume; educators can keep the meaning. Done this way, a learning-plan system gets more personal as it gets bigger, because the constraint it removes is the one that forced teachers to teach to the average. That, to me, is what responsible, scalable individual-learning-plan systems should demonstrate: more personalization, less burnout, and not one decision about a child taken out of human hands.

What I'd build next

If I carried this forward, I would make the assistant more present without making it more powerful: voice coaching so planning and check-ins can happen hands-free, and adaptive recommendations that propose the next best step as fresh progress data arrives. I would connect plans to the tools classrooms already use through LMS integration and link goals to AI tutoring so a plan flows into practice. And I would extend the long view — career forecasting that ties today's strengths to tomorrow's pathways, and a mobile app that puts plans, goals, and family updates in a pocket. Every one of those, though, would keep the same rule: the AI proposes, and a human approves.