Knowing When A Role Has Stopped Teaching You Anything
The signals are quiet, they arrive gradually, and most people notice them a year late.
A role does not usually announce that it is finished. It fades. You notice that you can predict the whole week on Monday morning. You notice that you have stopped asking questions in meetings because you already know the answers, and stopped disagreeing because it does not seem worth it. You notice that the parts of the job you found interesting have been slowly delegated away, or automated, or reorganised into someone else's area, and what remains is maintenance. None of these is dramatic. Collectively they mean the role has stopped changing you, and roles that stop changing you eventually cost more than they pay.
Before concluding anything, test whether the role is finished or whether your version of it is. Many jobs contain unclaimed territory: a problem everyone complains about that nobody owns, an area the team touches badly, a relationship with another part of the organisation that has gone quiet. Taking on one of those can restart the learning without changing anything else, and it is a far cheaper experiment than leaving. It also produces useful information. If you try and the organisation genuinely has no room for it, that answer is worth having, and it is more solid than a vague sense of restlessness.
If the answer is that the role is done, the useful move is to be deliberate rather than abrupt. Finish what you have started, because unfinished work is what colleagues remember. Write down what only you know, so the person after you is not stranded. Leave the relationships intact, since working life is longer and smaller than it looks from inside any one job. And be honest with yourself about what you are moving towards rather than only what you are moving away from, because a decision made entirely out of fatigue tends to produce the same situation somewhere else.