eLearning Portfolio Project Ideas That Get You Hired in 2026
By Devlin Peck · Updated
Part of the Instructional Design Portfolios guide
The best eLearning portfolio projects are concept projects that solve a realistic performance problem for a specific audience. They prove the skills hiring managers actually screen for: Storyline development, scenario design, and increasingly, AI. You do not need client work. You need one strong flagship project and a few supporting pieces that show how you think.
Choosing your project ideas is one step in the bigger job of building your instructional design portfolio. This article handles the step most people get stuck on: deciding what to build in the first place.
I have been helping people make this decision for years. My first bootcamp was literally the ID Portfolio Bootcamp, and the whole curriculum worked backwards from one question: what does someone need to build to create a portfolio that lands better opportunities? The answer was an eLearning project that shows off in-demand skills. That answer has not changed. The specific projects worth building have.
What makes a strong eLearning portfolio project?
A strong portfolio project starts from a performance problem: who is failing to do what, and what does it cost? It does not start from a topic. "A course about coffee" or "a module on time management" is a topic, and topics produce the exact kind of portfolio piece employers screen out, because a topic-first project can only demonstrate content dumping.
Flip the framing and everything downstream gets easier. "Baristas at a growing coffee chain are inconsistent on drink builds during rush hour, and remakes are killing throughput" is a performance problem. It gives you an audience, observable actions, a cost of failure, and a reason your design decisions exist. It also gives you something real to say in your project write-up later. Christy Tucker's 30+ Ideas for eLearning Portfolio Samples is a solid list of starting points and makes a compatible warning about fake, condescending sample topics. My push is to take any idea one step further: turn it into a problem before you build anything.
Hiring managers do not hire for interesting topics. They hire people who can solve performance problems.
Two rules before you commit to an idea:
- Never lift work from a current or former employer. Even if you built it yourself, it is almost always confidential. Rebuild the mechanics with brand-new content instead.
- Do not build knock-offs of other people's projects. It might feel like a quick win, but it can cost you. Some companies will read a near-copy as too close to plagiarism, and you will never know which doors it quietly closed.
Concept projects, on the other hand, are fully legitimate. When you use the instructional design process to solve a realistic problem, even an invented one, hiring managers can see your thinking. That goes really far.
Which skills should your portfolio projects prove?
Hiring managers screen for four things: analysis, scenario design, development skill (Storyline above all), and increasingly, AI fluency. Every project you build should visibly prove at least one of them.
The development point deserves the bluntest treatment. I have seen people apply for a year straight without landing interviews when the only things in their portfolio were Rise and PowerPoint projects. It is fine to include a Rise project. It shows you can produce a clean eLearning asset. But it will not land you a job as effectively as showing off Storyline skills, because Storyline is where employers see custom interactions, variables, and real development thinking. If you are building an eLearning developer portfolio specifically, this gap decides interviews.
AI is the newer variable, and the hiring market is genuinely split on it. AI-forward companies want to see you using AI tools. More traditional companies still want to see Storyline. Over the past year I have watched AI work stand out on portfolios and help people get hired more easily, though people are absolutely still getting hired without it. The practical takeaway: you do not have to choose a side. The flagship I recommend below covers both.
What should your flagship project be in 2026?
My recommendation for everyone is the same: a scenario-based Storyline 360 project with an AI-powered practice simulation embedded inside it. It is faster to build than the old approach of hand-branching every conversation path, it is a more engaging experience for the learner, and it proves Storyline and AI skills in one project. The AI-forward companies see you working with AI tools. The traditional companies see real Storyline development. One flagship covers both audiences.
How to find your flagship idea
Pick a specific audience
Choose a role you know something about or can research easily: new retail managers, home health aides, junior sales reps, IT help desk staff. Specificity is what makes a concept project read as real.
Find the problem
What is this audience failing to do, and what does the failure cost? Missed sales, safety incidents, churned customers, escalated tickets. If you cannot name the cost, keep digging.
List the observable actions
What would people do differently if your solution worked? Write down 3 to 5 concrete, observable behaviors. These become the decisions your scenario is built around.
Design the solution around practice
Build the experience so the learner makes those decisions and lives with the consequences. Practice and feedback, not information screens.
I walk through this idea-finding process in more detail in the video below. I recorded it before I started recommending the AI practice layer, so treat the process as current and the tooling advice as the older approach.
What does the AI practice layer look like?
The practice layer is an AI conversation simulation sitting inside your Storyline course: the learner reaches the moment of truth in your scenario, then actually has the conversation instead of clicking a pre-written branch. This is what devlin.ai does, and full disclosure, it is my company. You describe the scenario in plain English and get a working voice or text simulation you can embed in Storyline, Rise, or any LMS.
Describe a scenario your target audience needs to practice and try the simulation it builds:
For a portfolio project, the details are what impress reviewers. The simulation evaluates the learner against criteria you define, and the transcript and scores report back to the course. A Storyline variable bridge lets the sim update variables like score, pass or fail, and even a character's mood, so your Storyline states can react to how the conversation went. That is a rich, demonstrable piece of development work for a write-up. And build it voice-first where you can: voice is what makes the simulation experience feel like real practice rather than a chat window.
Here is what a finished practice conversation looks like. Play the manager's side of a talk with an underperforming employee:
If you want to build your own, the Starter plan exists for exactly this audience (aspiring IDs and solo portfolio-builders) at $9/month, or $6/month paid annually.
eLearning portfolio project ideas by skill: which should you build?
Pick one or two ideas from the skill area you most need to prove, and treat everything else as optional. Every idea below is framed as a performance problem with an audience, a deliverable, and a realistic scope.
| Project idea | Performance problem it solves | Skill it proves | Suggested deliverable | Scope |
|---|---|---|---|---|
| Onboarding needs assessment | New hires at a fictional company take months to reach full productivity | Analysis | Needs assessment report with recommendations | 1 weekend |
| Action map and design brief | Support reps escalate tickets they could resolve themselves | Analysis, design thinking | Action map plus a one-page design brief | 1 weekend |
| De-escalation scenario | Frontline staff lose customers during complaint calls for a made-up product | Scenario design | Branching conversation scenario | 2 weekends |
| Coaching conversation scenario | New managers avoid or fumble tough feedback conversations | Scenario design | Branching scenario with consequence-based feedback | 2 weekends |
| Safety judgment scenario | Warehouse workers skip safety steps under time pressure | Scenario design | Short judgment-call scenario | 2 weekends |
| Custom Storyline interaction | Employees misapply a triage or prioritization process | Storyline development | One polished interaction using states and variables | 2 weekends |
| Software practice simulation | A team wastes hours on one recurring software task | Storyline development | Try-mode walkthrough of a common tool | 2 weekends |
| Animated scenario video | Employees fail to recognize phishing attempts | Visual design, media | Short animated scenario video | 1 to 2 weekends |
| Storyline course with embedded AI sim | New managers freeze in high-stakes conversations | Storyline plus AI | Scenario course with an AI practice simulation inside | Flagship, under a month |
| Evaluation plan and early-data review | Stakeholders cannot tell whether the training worked | Evaluation | Evaluation plan plus analysis of early usage data | 1 weekend |
Analysis and design-thinking ideas
Analysis artifacts prove you think before you build, which is rarer than it should be. Run a needs assessment for a fictional org and publish the report. Or take a real workplace problem you have witnessed and build an action map, Cathy Moore's approach to working backwards from business goals to observable actions, then package it with a short design brief. These are fast, they pair beautifully with a bigger project, and they give hiring managers evidence of consulting-level thinking.
Scenario design and writing ideas
Scenario projects prove you can design decisions, not screens. De-escalating an angry customer (invent the product so you are not borrowing a real brand), coaching an underperformer, or making a safety judgment call under time pressure all work because the learner faces choices with visible consequences. Keep the branching tight: a few meaningful decision points beat a sprawling tree you will never finish.
Storyline development ideas
If your goal is an eLearning developer portfolio, one polished custom interaction beats a 20-minute presentation every time. Build custom navigation, a states-and-variables showcase, or a try-mode software simulation, and wrap it in a realistic problem so the interactivity has a reason to exist. Reviewers open these projects looking for evidence that you can build beyond templates.
On the media side, Vyond is really good for portfolio building because its asset library is so consistent. Everything you produce looks cohesive, which is why you see genuinely flagship-looking projects built with it. It is a pricey tool, so treat it as an option rather than a requirement.
AI-forward ideas
AI projects are what stand out most right now. The strongest version is the one described above: an AI practice simulation embedded in a Storyline course, which doubles as your flagship. A standalone AI character practice conversation also works as a supporting piece, especially voice-based practice for a specific role. A custom GPT built as a performance-support assistant for a defined audience can round things out, and the write-up about your prompt design and guardrails often matters more than the tool itself.
Evaluation and measurement ideas
Evaluation is the thinnest section in most portfolios, which makes it an easy place to stand out. Write an evaluation plan for your own concept project. If your flagship includes a simulation, review the early usage data and transcripts, then document the design decisions you changed based on what you saw. And get other people's eyes on your project even without real learners: share it, collect feedback, improve it, and gather short testimonials from people in the target audience or subject matter experts who would find it useful. A before-and-after iteration write-up is evidence of exactly the judgment employers pay for.
Not sure which of these fits your situation? Answer a few questions and get a ranked shortlist:
Answer five questions and I will rank this article's project ideas against your situation. You get a three idea shortlist with scope guidance for the time you actually have. No email, nothing leaves your browser.
How do you scope a project you can actually finish?
Scope every supporting project to be finishable in about two weekends, and keep any single sample under roughly five minutes of seat time. Over-scoping is the number one reason concept projects die half-built, and a half-built project helps nobody.
The flagship gets more room, but not much more. If you already know how to use Storyline, the full flagship (a scenario-based Storyline course with an embedded AI simulation) is realistic in less than one month, on a single Articulate Storyline free trial. Articulate 360's trial runs 30 days with no credit card required, as of mid-2026. If you are new to Storyline, learn the fundamentals first with free resources, then start the trial when you are ready to build for real.
How many projects do you need, and how should you present them?
Fewer than you think: one flagship plus two or three supporting pieces is plenty. My recommendations here have only gotten more refined over time. Keep the portfolio simple, minimal, and easy to navigate. No filler sections. A hero section followed immediately by your featured project, because that is what hiring managers are looking for.
Each project needs a process write-up, and the write-up is what turns a concept project into evidence of thinking. Cover five things: the problem, the audience, your process, your specific role, and the tools you used. This is also where problem-first idea selection pays off twice. A realistic problem gives you a real write-up. A fake topic leaves you nothing to say.
For hosting the projects themselves, devlin.host gives you free HTML project hosting. For the full walkthrough of getting Storyline output online, see how to publish and share your Storyline projects on the web.
Where can you find inspiration without copying?
Study finished portfolios for standards and structure, then design your own problem. Take inspiration from the quality bar, but don't copy the project. As I said earlier, a knock-off might get you a quick win, but the plagiarism-adjacent cost is not worth it.
Good places to calibrate and generate ideas:
- The eLearning Heroes challenges, Articulate's weekly community design challenges, which are a legitimate source of constraints-based project prompts.
- Go Design Something, Kristin Anthony's free portfolio-idea generator, when you want a randomized starting point to reframe as a performance problem.
- My recorded portfolio reviews, where you can watch me evaluate real portfolios the way a hiring manager would.
- A look back at how my eLearning portfolio has evolved, which shows which standards rose over time and which stayed put.
I also recorded a walkthrough of 20+ strong portfolios and flagship projects:
Frequently asked questions
Have eLearning portfolio expectations changed in 2026?
Not much. When people ask me whether the format, design, or expectations of portfolios have changed, my answer is no, not in my experience. The fundamentals are stable, and we are mostly doing more of what already works. The one real shift is that AI skills on a portfolio now stand out and help people get hired more easily, though people still get hired without them.
Do I need real client work in my eLearning portfolio?
No. Concept projects that solve realistic performance problems carry portfolios into real job offers all the time. What hiring managers evaluate is your process and your craft: whether you identified a problem, designed around observable actions, and built something polished. An invented company with a real problem beats a real company with a topic dump.
Can I use projects from my current or previous job?
Usually not. Work you built for an employer is almost always confidential, even when you were the sole author. The safe move is to rebuild the mechanics you are proud of (the interaction pattern, the scenario structure, the evaluation approach) with entirely new content, audience, and branding.
How long should each portfolio sample be?
Under about five minutes of seat time. Reviewers skim, and they will not sit through a 20-minute course. One tight, polished interaction or scenario demonstrates more skill than a long presentation, and it is far more likely to get experienced end to end.
Next steps
Pick your flagship idea this week using the audience, problem, actions, solution process above, then choose one or two supporting ideas from the skill areas where your portfolio is thinnest. When you are ready to put it all on a site, the full guide to creating an instructional design portfolio covers the build.
And if you want structure and feedback while you do it, Peck Academy is my licensed career school for people transitioning into instructional design. Students build an AI-integrated flagship project in Storyline 360 with extensive feedback, plus the portfolio website to showcase it.