top of page

Training Isn’t Neutral: Why Your Identity Shapes Learning Outcomes

  • Writer: Carla Guardado
    Carla Guardado
  • Apr 8
  • 4 min read

For a long time, I thought good training meant being neutral.


Clear.

Standardized.

Consistent.

Invisible.


Especially in regulated environments like fintech, where compliance, accuracy, and process matter deeply, it’s easy to believe that the best training is the one that removes the individual behind it.

But over time, I started to notice something.


The trainings that actually worked, the ones that reduced errors, increased confidence, and helped people move faster, weren’t neutral at all.


They had a voice.


The Myth of Neutral Training


We often treat training like a container for information:

  • policies

  • procedures

  • workflows


The goal becomes delivering content as cleanly and consistently as possible.


And while clarity and consistency matter, neutrality can quietly become a limitation.


Because training is not just about what you say.


It’s about how people understand, interpret, and apply it.



Where Identity Shows Up


Whether we realize it or not, our identity is already in our work.


It shows up in:

  • how we simplify complexity

  • the examples we choose

  • the way we structure information

  • the visuals we create

  • the tone we use when explaining something difficult


Some people design training that is highly structured and methodical.Others lean into storytelling, scenarios, or visual cues.


Neither is “more correct.” But both are expressions of identity.



Identity Starts With Understanding Your Audience


Before identity shows up in design, it shows up in how deeply you understand the people you’re designing for.


One of the most important shifts in my work has been intentionally spending time with the subject of the training:

  • observing their workflows

  • understanding their constraints

  • seeing what their day-to-day actually looks like


Because you can’t design effective training from a distance.


You have to get close enough to answer:

  • What does their day feel like?

  • Where do they hesitate?

  • What decisions are they making in real time?


There’s something powerful in truly knowing your audience, not just their role, but their reality.



Design Is Not One-Size-Fits-All


That understanding directly shapes how you design.


For example:

  • Call center environments require:

    • speed

    • clarity at a glance

    • decision-making under pressure

    • resources that support real-time use

    Training here needs to be concise, visual, and immediately actionable.


  • Technical or engineering roles often require:

    • deeper context

    • system-level understanding

    • documentation they can reference


    Training here may lean into flowcharts, diagrams, manuals, or structured guides.


Same goal: understanding and performance.Different design entirely.



Designing for How People Actually Think


This approach is also grounded in how people process information.


Through my work in learning experience design and cognitive science, I’ve come to understand that learning isn’t just about exposure to content, it’s about how the brain manages attention, filters information, and makes decisions under constraint.


Concepts like cognitive load aren’t theoretical; they show up in real time.


In a call center environment, where decisions are made quickly and under pressure, overloaded information doesn’t just slow people dow, it increases errors.

In more technical roles, where systems thinking is required, oversimplification can be just as harmful.


Good training isn’t just clear; it’s calibrated.


It respects the limits of attention, reduces unnecessary friction, and supports the way people actually work.


When you design with cognitive load in mind, you’re no longer just delivering information, you’re shaping how effectively someone can think and act in the moment.



Identity as a Design Advantage


When you combine:

  • a deep understanding of your audience

  • with your own way of thinking and structuring information

something shifts.


You begin to:

  • anticipate confusion more effectively

  • design with empathy instead of assumption

  • create resources that feel intuitive, not just complete

  • make decisions faster because your approach is consistent


Your work becomes recognizable.

Not because of branding; but because of how it thinks.



What This Looks Like in Practice


In my own work, I’ve seen this most clearly when:

  • turning complex system behaviors into visual cheat sheets

  • designing simulations that mirror real decision-making

  • structuring content so that the “next step” is always obvious


These aren’t just format choices.


They reflect how I process information and how I believe people learn best: through clarity, context, and application.



Why It Matters


When training reflects both identity and audience understanding, the impact is tangible:

  • faster onboarding

  • fewer errors

  • increased confidence at the point of action

  • better adoption of tools and processes


Because learners aren’t just receiving information.


They’re interacting with a system that was designed with intention, and built for them.



Final Thought


Training isn’t neutral, and it was never meant to be.


It’s a reflection of how we think, what we prioritize, and how much we consider the experience of the person on the other side.


When you understand your audience deeply and embrace your identity as part of your design, your work stops being generic.


And starts becoming something people can rely on.



If you’d like to explore or learn more:


The ideas in this piece are shaped both by hands-on experience and foundational work in learning science and design.

If you’re interested in going deeper, these are great places to start:


  • Cognitive Load Theory – John Sweller

  • Principles of Multimedia Learning – Richard Mayer

  • First Principles of Instruction – David Merrill

  • Universal Design for Learning – CAST

  • Microsoft Inclusive Design Toolkit – Microsoft Inclusive Design

  • Don’t Make Me ThinkSteve Krug

 
 
bottom of page