Motivation Is Not a Vibe

I read a paper today that helped me put better words around something I keep seeing while teaching DevOps.

We talk about student motivation as if it is a mood. Some students “are motivated”, some are not. Then we try to fix it with enthusiasm, deadlines, grades, inspirational speeches, or another layer of pressure.

That is mostly useless.

Motivation is not one thing. It is a chain.

The paper maps several major theories of motivation onto a simple action model:

Situation -> self -> goal -> action -> outcome -> consequences.

That framing is much more useful than asking, “How do I motivate students?”

The better question is: where exactly is the chain broken?

Maybe the situation is wrong. The task feels artificial, the environment is noisy, or the student does not see why this matters.

Maybe the self part is weak. They do not yet see themselves as someone who can do this. Confidence is not a sticker you put on top. It is built from evidence.

Maybe the goal is vague. “Learn Kubernetes” is not a goal. “Deploy this service, expose it, break it, observe it, and fix it” is much better.

Maybe the action is too big. The gap between knowing nothing and shipping a working CI/CD pipeline can feel absurd. Split it.

Maybe the outcome is invisible. If feedback arrives too late, students cannot connect action to learning.

Maybe the consequences are poisoned. If grading teaches “do not look stupid”, students optimize for hiding weakness. If feedback teaches “your strategy improved”, they keep moving.

This is why I like practical engineering education. Good labs are not just exercises. They are motivational systems.

A realistic task gives the situation meaning. A small early win builds self-efficacy. A clear target creates a goal. Hands-on work drives action. Fast feedback makes the outcome visible. Thoughtful grading shapes the consequences.

No magic. No motivational posters. Just better system design.

I am increasingly convinced that teaching DevOps in 2026 is not about transferring YAML knowledge. AI can generate YAML all day. The hard part is helping students build judgment, confidence, and taste.

And that does not happen because we tell them to be motivated.

It happens when we design the learning environment so motivation has somewhere to come from.