Teacher to Instructional Designer: Build a Portfolio From Classroom Work

Teachers moving into instructional design are often told to hide the classroom and learn an authoring tool. That advice throws away their strongest evidence. Planning for a real audience, diagnosing misunderstanding, sequencing practice, adapting under constraints, and measuring learning are already design activities.

The portfolio still has to translate those activities into the problems an instructional design team hires someone to solve. A lesson plan renamed as a module is not enough. The case study must reveal the analysis and decisions behind it.

Do not erase teaching; change the unit of explanation

School artifacts are usually organized for delivery: slides, worksheets, rubrics, and lesson plans. An instructional design portfolio should be organized for evaluation. It needs to tell a reader who the learners were, what performance or knowledge gap existed, which constraints mattered, why you chose an approach, and how you knew whether it worked.

Oregon State University's guide to transitioning into instructional design highlights needs assessment, objectives, collaboration with subject-matter experts, feedback, and portfolio case studies. Those capabilities matter more than a gallery of tool screenshots.

Choose classroom work with a real design problem

Select two projects where your decisions changed the learning experience. A redesigned unit after poor assessment results is stronger than the prettiest slide deck. A resource built for multilingual families may show audience analysis and accessible communication. A new-teacher onboarding guide may translate directly into workplace learning.

If the original project was tightly tied to children, curriculum standards, or a school context, keep that context. Then explain the transferable design principle instead of pretending the project happened in a company.

Translate the evidence into instructional design language

Use this language only when it describes what happened. Corporate vocabulary pasted over ordinary teaching will feel artificial. The point is to help an employer recognize the design practice that was already present, not to inflate the project.

Show the process around the artifact

For each case, include a short brief, one or two useful artifacts, and a reflection. The artifact might be a storyboard, facilitator guide, job aid, assessment, accessible handout, short video, or small interactive module. Explain what changed because of testing or feedback. A finished screen without that context proves software familiarity, not instructional judgment.

• Write measurable objectives that describe what the learner should be able to do, then connect every major activity and assessment to them.
• Name the constraints, including time, device access, reading level, language, accessibility, class size, or facilitator capacity.
• Describe your own contribution when colleagues, specialists, administrators, or other teachers shaped the project.
• Include one revision with a reason. Iteration is more convincing when the reader can see what evidence caused it.

Protect students and school materials

Remove student names, faces, voices, grades, identifiers, and private communications. Do not assume that access to a school platform gives you publication rights. Recreate examples with invented data, replace copyrighted or licensed assets, and obtain permission when the school or a colleague owns part of the work.

A reconstruction should be labeled as such. You can say that a sample was adapted from a classroom project and rebuilt with fictional learner data for the portfolio. That disclosure strengthens the case because it demonstrates professional handling of private material.

Add one project outside the classroom

Two teaching-based cases can establish genuine experience. A third project designed for adults can close the context gap. Create a five-minute software onboarding, a safety job aid, a volunteer training, or a performance-support resource for a real small organization. Keep the scope narrow enough to research, test, and revise properly.

Avoid building a generic compliance course solely to demonstrate every animation available in an authoring tool. Employers can teach interface shortcuts. The harder signal is whether you can identify the right problem, remove unnecessary content, and design practice that supports performance.

Connect the career story without apologizing for it

Use the resume to establish the depth of your teaching experience and the portfolio to reinterpret selected work. An AI portfolio builder can help organize existing material, but you should write the analysis, boundaries, and outcomes yourself. Those are the parts that prove you can do the new role.

A credible teacher-to-instructional-designer portfolio does not claim that the two jobs are identical. It shows which design capabilities transfer, which business and technical skills you are adding, and how you apply both to a defined learning problem. That is a stronger story than either hiding the classroom or treating it as automatic qualification.