Method one: The User Manual
This is not a metaphor. You literally write a document.
One page. Two paragraphs. Title: "How to work with me."
What goes in it? A few things:
- What motivates you - specifically. Not "I like to grow." More like: "I'm motivated when I get a task with a lot of freedom in how I approach it, and I can see that my work has a real impact on someone in the company."
- What demotivates you - also specifically. "My energy drains when a project priority changes mid-sprint with no explanation why."
- How to best give me feedback - directly, in writing, with time to reflect first? Everyone's different.
- What I look like when I'm overloaded - because a leader might not notice. Some people withdraw. Others get irritable. Others start working overtime and say nothing.
When you're done - you hand it to your boss. Not at the annual review. In a regular conversation. "I wrote a few things about how to work with me. Might be useful."
We introduced this practice in one company, across the whole team. A month later the leader told me: "For the first two weeks it felt strange, because I'm supposed to already know this. But then I used that information three times in one week and understood what it was about."
It's not about exposing your weaknesses. It's about effectiveness.
Method two: The Proactive Conversation
Don't wait for the annual review.
Simple rule, big shift in thinking. Most of us approach our professional needs reactively - we speak up when something isn't working, or when we get an "opportunity" at a scheduled meeting. But the best conversation about motivation is the one nobody saw coming.
How to have it?
Instead of waiting for the yearly conversation - ask for a short meeting. "I'd like to spend 30 minutes talking about what drives me and what I'm missing. No specific problem - I just want us to have a shared picture."
Bosses rarely receive invitations like that. They usually approach them with curiosity.
It might also happen that your boss doesn't know what to do with the information. That's fine too. Your job isn't to turn your boss into a motivation expert. It's to make the information available. What they do with it - that's on them. But if they didn't have the data, they couldn't use it. Now they do.
One leader I worked with had this kind of conversation with their manager and later said: "I didn't expect it to change anything. But one small thing changed - I got a project that was marginal, but in exactly the area that fascinates me. Nothing else. That was enough for six months."
Motivation doesn't require revolution. Sometimes one well-matched project does it.
Method three: Small Experiments
You don't always know what motivates you. Really.
You think you do. You say: "I like challenges." Or: "I like working with people." But when I look at what clients actually spend their energy on - and when they have more of it - what comes out is often different from what they claim.
Small experiments are the practice of observing yourself at work. Not as philosophy - as a habit.
What does it look like? For two weeks, note which tasks leave you with more energy and which leave you with less. Don't evaluate - just observe. Task was hard and you have more energy? Task was easy and you're drained? Those are data points.
Then expand the experiment. Test what time of day your work produces the best results. Try a week without morning meetings. Compare projects that require conceptual thinking with those that are purely executional. Draw conclusions.
Those conclusions have two uses. First: you can manage your own energy better. Second - and this brings us back to the start: you have concrete data for a conversation with your boss. Instead of "I'd like more interesting projects" you can say: "I've noticed I do my best work on tasks that require analysis and strategic thinking. Is there a chance I could get more of that kind of work this quarter?"
That's a different level of conversation.
What all this gives you
I once wrote a LinkedIn post about how you can teach the people around you how to motivate you. It got several hundred views and a few comments I still remember.
One person wrote: "Sounds like work the boss should be doing." Yes, they should. And often they do. But when both sides do it - the results multiply.
What specifically changes when you use these methods?
Better projects. Not random - matched. Your boss knows what pulls you in, and when a project in that area shows up, they think of you. Not because they like you more. Because they have data.
Promotions and career decisions. It's hard to develop someone's career when you don't know what they want to develop. One of my clients was passed over for promotions for years. The reason was mundane: they never explicitly said they wanted to lead people. Everyone assumed they were "technical" and preferred conceptual work. They wanted both. But nobody asked - and they never said.
Results. You work better when you're doing what drives you. That's not wishful thinking - it's a mechanism. Mihaly Csikszentmihalyi spent decades researching the state of deep focus and engagement he called flow - and described the conditions it requires: the task must sit at the intersection of skill and challenge, have a clear goal, and provide feedback. The User Manual and the proactive conversation with your boss are actions that increase the chances of those tasks showing up more often. Engagement translates to output. Output translates to team results.
Lightness. Hard to measure, but real. Work in which someone knows how to motivate you - and makes the effort to - just feels different. Less energy spent "surviving" the week, more left for the actual work.
In the end, motivation is your responsibility. Not because the leader plays no role - they do. But the leader is not inside your head. You are. And you're the one who knows when you have energy and when something's draining it for no good reason.
The question I leave you with: when did you last tell your boss directly what drives you - and what drains you? If you can't remember - that's a good moment to change that.