Perspective

Learning Design Is Not a Beauty Contest

A polished learning experience can attract attention. It cannot prove that the designer identified the right problem, chose the right intervention, or helped anyone perform better.

A polished learning experience is easy to admire.

The typography is intentional. The illustrations are cohesive. The animations move smoothly. Every screen looks as if it belongs in a design showcase.

Then someone asks the question that should have guided the project from the beginning:

Can people perform better because of it?

That is when the conversation often becomes less certain.

We can point to completion rates. We can share favorable learner reactions. We can explain how closely the experience follows brand guidelines. We might even show the awards it received.

But none of those things tell us whether the solution helped someone make a better decision, avoid an expensive mistake, respond more confidently, or perform the work under real conditions.

Learning design is not a beauty contest. Yet much of our industry still behaves as if visual polish is the clearest evidence of design quality.

What our portfolios teach us to value

Learning designers are frequently told that their portfolios need to stand out. That advice is not inherently wrong. A portfolio must attract attention long enough for someone to explore the work. Visual design helps establish credibility, communicate professionalism, and make the work easier to understand.

The problem is what happens when attracting attention becomes the primary design objective.

Visual design is immediately visible. Sound analysis is not. A recruiter can recognize an attractive interface in seconds, but understanding the reasoning behind a performance solution requires more time and context.

This creates a powerful incentive for learning designers to optimize for what can be judged quickly. We build sophisticated interactions because they demonstrate technical ability. We create animated scenarios because they look impressive in a portfolio. We add visual complexity because a simple resource may not appear substantial enough to represent weeks of work.

The result is an industry that can become better at presenting learning than designing it.

A beautifully produced course may demonstrate excellent visual judgment and development skill. It does not automatically demonstrate that the designer identified the correct problem, selected the right intervention, created meaningful practice, or established a credible connection to performance.

Those are separate design decisions. When we treat visual polish as a substitute for evidence, we reward the artifact before we understand the thinking behind it.

Beautiful can still be wrong

There is a difficult truth behind many learning requests: sometimes the requested course should never be built.

The performance problem may be caused by an unclear process, an inaccessible tool, conflicting expectations, insufficient feedback, poor incentives, or a work environment that makes the desired behavior unnecessarily difficult.

A beautiful course cannot repair a broken workflow. It can explain the workflow. It can provide examples. It can give people an opportunity to practice. But if the real obstacle remains in the work environment, the course may simply become a polished layer placed over an unresolved problem.

Imagine a team whose employees are repeatedly making errors while processing customer requests. Leadership assumes that employees have forgotten the procedure and asks for refresher training.

The learning team responds with a highly produced digital experience. It includes custom illustrations, branching scenarios, animated transitions, and a final knowledge check. Employees complete it and rate it positively.

The errors continue.

Further investigation reveals that the procedure changed three times in six months, the reference materials contain contradictory instructions, and the internal system presents the required information in an order that does not match the actual workflow.

The course may be beautiful. It may also be irrelevant to the conditions producing the errors.

A simpler intervention might create more value: consolidate the instructions, redesign the job aid around the actual decision sequence, and work with the product team to correct the interface.

The design question

One solution produces a striking portfolio thumbnail. The other may prevent hundreds of mistakes. Which outcome represents better design?

Visual design still matters

Arguing that learning design is not a beauty contest does not mean appearance is unimportant.

Poor visual design creates real barriers. Inconsistent layouts increase cognitive effort. Weak contrast limits accessibility. Decorative elements compete with important information. Dense screens make it difficult to identify what requires attention. Careless typography can make even well-written content exhausting to read.

Good visual design helps people understand where to look, what matters, and what to do next.

The distinction is purpose.

Visual design should reduce friction, establish hierarchy, support comprehension, and make the experience easier to use. It should not exist primarily to prove that the designer knows how to create something impressive.

A learning experience can be visually sophisticated because the problem requires rich simulation, environmental realism, or emotional engagement. It can also be deliberately simple because someone needs immediate access to one clear answer during the work.

Both choices can represent excellent design. The question is not whether the solution looks simple or elaborate. The question is whether every design choice helps someone accomplish something important.

We confuse production value with design value

Production value is visible in the artifact. Design value is visible in the relationship between the problem, the solution, and the result.

Production value asks:

  • Does the experience look professional?
  • Is the interaction technically impressive?
  • Are the visuals consistent?
  • Does the experience feel polished?

Design value asks:

  • What was preventing successful performance?
  • What did people need to perceive, decide, remember, or practice?
  • Why was this intervention selected?
  • How does it fit into the environment where the work happens?
  • What evidence would show that the situation improved?

These categories can overlap, but they are not interchangeable.

An elegant experience built for the wrong problem has high production value and low design value.

A simple decision tool that prevents a recurring operational error may have modest production value and enormous design value. Our profession needs to become more comfortable recognizing that difference.

The five-question beauty contest test

If you are currently designing a course, building a portfolio project, or reviewing an existing learning solution, pause before adding another interaction or polishing another screen.

Use these five questions on one current project:

1. What must someone do differently?

Name the observable action the solution is meant to support.

“Understand the policy” is not enough. What should someone do when applying the policy? What decision must they make? What mistake must they avoid? What action should become more consistent?

If the required performance cannot be described, visual development is premature.

2. What is preventing that performance today?

Do not assume the answer is a lack of knowledge.

The obstacle could be unclear expectations, limited practice, an unreliable process, missing feedback, a confusing tool, contradictory resources, or a consequence that discourages the desired behavior.

A learning intervention can only address the obstacles it was designed to influence.

3. Where will the solution be used?

A resource used during the work has different requirements from a structured practice experience completed before the work.

If someone needs an answer in ten seconds while speaking with a customer, a visually elaborate course may be less useful than a searchable decision guide. If someone needs to develop judgment before handling a high-risk situation, a scenario with meaningful consequences may be appropriate.

The conditions of use should shape the form of the solution.

4. What could be removed without reducing its usefulness?

This question exposes the difference between purposeful design and decorative effort.

If removing an animation, interaction, screen, or block of content does not weaken comprehension, practice, feedback, or performance support, consider removing it.

Simplicity is not evidence that less thought went into the work. Often, simplicity is the result of better decisions.

5. What evidence would demonstrate improvement?

Do not wait until the project is finished to decide what success means.

Would errors decrease? Would decisions become more consistent? Would employees require less assistance? Would managers observe a specific behavior more frequently? Would people complete a task more accurately or confidently?

If success is defined only as completion, satisfaction, or visual approval, the project is still being judged like a beauty contest.

Try it now

Apply these five questions to one current project. If they change what you build, remove, or measure, they have already done more than another round of visual polish.

The most useful solution may not be a course

After more than 23 years in education and workplace learning, I have become increasingly skeptical of the assumption that the most substantial-looking deliverable must be the most valuable one.

Some problems require a course. People may need structured explanations, guided practice, feedback, and repeated opportunities to build a new capability.

Other problems require something much smaller.

A manager may need a conversation guide that helps them coach a new behavior consistently. An employee may need a decision tree when an unfamiliar situation appears. A team may need a checklist that prevents critical steps from being skipped. A new hire may need short practice opportunities distributed across the first month rather than one large onboarding event.

Sometimes the correct intervention is a redesigned process. Sometimes it is clearer feedback. Sometimes it is removing information rather than adding more.

These solutions may not resemble the learning products that receive the most attention online. That does not make them less thoughtful.

In many cases, choosing the smaller intervention requires greater discipline because the designer must understand precisely what is creating the performance gap. There is nowhere for weak reasoning to hide. The solution must be useful enough to justify itself.

It is much easier to begin building than to determine whether building is necessary.

The portfolio case study needs to change

If portfolios are going to represent the full value of learning design, they must show more than attractive screens.

A strong case study should help us understand the conditions surrounding the work. What triggered the request? What did stakeholders initially believe they needed? What evidence was available? What assumptions had to be challenged? What constraints affected the decision? Why was this solution chosen over other possibilities? What was intentionally excluded? How was the solution expected to influence behavior or performance?

The final artifact still matters, but it should be presented as the result of the design process rather than the entire story.

A useful way to test one of your current portfolio projects is to hide its screenshots temporarily. Then read the remaining case study.

Can a reviewer still determine:

  • What problem you were solving?
  • What you discovered before building?
  • Which decisions you made and why?
  • What changed because of your work?
  • What you would measure or improve next?

If the story collapses without the screenshots, the case study is presenting an artifact rather than demonstrating design judgment.

This shift would also make learning design portfolios more credible to business leaders. Organizations rarely hire us because they need someone who can decorate information. They hire us because something important is not working as well as it should.

Our case studies should demonstrate that we know how to investigate that situation and design an appropriate response.

The most compelling sentence in a portfolio should not be, “Here is what I built.” It should be, “Here is why this was the right thing to build.”

Awards can distort the work

Awards, showcases, and public recognition can help advance the profession. They expose designers to new techniques, encourage experimentation, and celebrate work that might otherwise remain invisible.

But awards also influence what gets created.

When a learning experience must be evaluated outside its original environment, judges naturally rely on what they can observe. Visual quality, originality, interaction design, and narrative become easier to assess than long-term performance change.

This can quietly shift the designer’s attention from the people experiencing the problem to the people evaluating the artifact.

Would we still include this interaction if no judge ever saw it?

Would we still produce this animation if it were never shared online?

Would we still build the course if a simple field guide solved the problem faster?

Those questions are not arguments against ambition. They are safeguards against confusing recognition with effectiveness.

A learning solution should be able to succeed without receiving applause.

We need a better definition of excellent work

Excellent learning design begins before visual development.

It begins by refusing to accept the requested deliverable as the complete definition of the problem. It requires understanding the behavior that needs to change, the conditions surrounding that behavior, and the evidence that would indicate improvement.

From there, the designer must decide what people genuinely need.

Perhaps they need information. Perhaps they need practice. Perhaps they need feedback from another person. Perhaps the environment needs to make the correct action easier. Perhaps leadership needs to clarify expectations before anyone creates another piece of content.

Only then should we determine what the solution needs to look like.

This approach does not diminish the craft of visual design. It gives that craft a purpose.

The best visual design directs attention toward what matters. The best interaction design allows someone to rehearse a meaningful decision. The best technology disappears into an experience that helps someone think, act, or perform more effectively.

The goal is not to create something plain. The goal is to create something useful.

The contest we should be trying to win

Learning design should be judged by the quality of the decisions behind the solution and the value it creates for the people who use it.

Did the designer identify the real problem? Did the intervention reflect the conditions of the work? Did people receive meaningful practice or support? Did the solution reduce friction? Did something improve?

A beautiful learning experience can accomplish all of these things. When it does, its appearance is part of a much stronger design story.

But beauty alone is not evidence of learning, behavior change, or improved performance.

Our work does not become valuable when someone admires the screen.

It becomes valuable when someone can do something tomorrow that they could not do today, make a difficult decision with greater confidence, or perform successfully when the situation becomes complicated.

That is the contest learning design should be trying to win.

Inferele

Diagnose the problem before you design the solution.

Inferele helps learning professionals move from a requested deliverable to a clearer understanding of the performance problem, the conditions surrounding it, and the intervention people actually need.

Challenge the request, examine the evidence, and make a stronger design decision before production begins.

Start with the problem
  • Clarify the requested outcome
  • Define observable performance
  • Identify barriers in the system
  • Test whether learning is needed
  • Choose the right intervention