“It should get better soon” can be reassuring when a role has become frustrating. A new manager may be settling in, a vacancy may be due to fill, or a broader remit may have been discussed. Some changes do take time. Yet a general expectation of improvement can keep a professional in the same situation long after they have stopped learning from it.
Deciding whether to stay need not begin with an ultimatum or a resignation date. A more useful starting point is to define what would make staying worthwhile, what evidence would show that the change is happening, and when you will look again. That turns waiting into a deliberate test. It also leaves room for the realities that constrain a career choice: income, location, personal commitments and the availability of another suitable role.
Identify what actually needs to change
“The role needs to improve” can refer to very different problems. You might have too little room to use your judgement, too little access to work that develops you, a workload that prevents careful work, or a relationship that makes reasonable decisions unnecessarily difficult. The remedy depends on which of these is at issue. A new title will have limited value if the work and authority remain the same; a more interesting project may not offset an unsustainable workload.
Start with the experience that has made you reconsider the role. Describe it in terms of work and consequence. For example, a Quality specialist may have developed the capability to lead an improvement project but continue to receive only routine checking tasks. The relevant concern is not merely that they feel underused. It is that the current allocation of work gives little opportunity to exercise and demonstrate the broader capability they want to develop.
Some problems are local to a job. A different project, clearer authority or a revised division of responsibilities may address them. Others reflect a wider organisational constraint, such as limited capacity for progression or a persistent mismatch between what the organisation needs and the work you want to do. The distinction matters because it changes what improvement is plausible. A supportive manager may be able to allocate a project but may not be able to create a senior role or change a decision structure alone.
Try to separate a temporary difficult period from the continuing shape of the job. A demanding launch or absence cover may be tolerable for a defined period, especially if it offers learning and has an end point. If every exception becomes the normal workload, the original explanation loses force. Look at the work over time rather than relying on either one bad week or a vague belief that patience will eventually pay off.
Define a change you could recognise
A useful stay condition is specific enough that you would know whether it had occurred. “More opportunities” is an understandable wish, but it leaves the decision open to reassuring language. “Take responsibility for a defined improvement project, with agreed time and a manager who can review the result” identifies a change in actual work. The condition can concern scope, support, decision authority or development. It should reflect what would make the role valuable to you, not what looks impressive on paper.
Specificity does not mean demanding a guaranteed outcome. A manager may be able to discuss a possible assignment without controlling when it becomes available. You can distinguish a firm commitment from an aspiration and decide how much weight to give each. A date to review a plan is useful, but it is different from a date by which a promotion will occur. Treating the two as equivalent invites disappointment and obscures what was really agreed.
The change also needs to be meaningful. A single invitation to a meeting may signal interest, yet it may not alter the work you do or the capability you can build. Conversely, a trial assignment may be genuinely valuable even before a formal title changes, provided you have enough time, support and authority to do it well. Consider what the change would let you learn, contribute or demonstrate. If it would not address the reason you are considering leaving, it is a poor stay condition however welcome it feels in the moment.
You can make your part explicit. Perhaps you need to say that you want broader responsibility, show readiness for a project or propose a manageable way to take one on. The organisation may need to make the assignment available, release time or authorise the work. Separating those responsibilities prevents the decision from becoming a private test of whether you can somehow make the whole organisation change.
Give the role a fair period to show movement
A review point should allow enough time for a real change to be attempted without turning an indefinite hope into a permanent plan. The sensible period depends on the work, the decision process and your circumstances. A project that requires a scheduled planning cycle cannot be judged the next week. A repeated promise with no named owner, practical step or visible movement may not deserve another long wait.
Imagine the Quality specialist has discussed a broader improvement remit with their manager. They agree that the specialist will prepare a proposal for a cross-functional issue and, if the work is approved, be given time to coordinate a limited trial. The manager will confirm who can approve the trial and review the specialist's contribution after it. The professional can now look for real signals: whether the proposal was considered, whether the trial was authorised, whether time was made available and whether the promised review happened. None of these alone guarantees a future role, but together they show whether the present role is changing in the direction that matters.
The example also shows why a review point is more than a calendar reminder. It connects the desired development with actions and decisions. If the trial cannot proceed because a genuine operational priority intervenes, the specialist can assess whether an alternative route is offered and whether the delay is explained. If there is no progress and no credible next step, that is relevant evidence too. The professional need not prove bad faith to decide that the role is unlikely to provide the development they seek.
Keep the review honest. It is easy to extend a deadline whenever something promising is mentioned. An extension may be reasonable when a concrete step has occurred and its consequence needs time to become clear. Repeatedly substituting a new possibility for an earlier unmet condition changes the test. Ask whether the underlying work, support or authority has actually moved, and whether the revised timetable still serves your own needs.
Decide with the information you have, not the answer you hoped for
At the review point, several outcomes are possible. The change may have happened and the role may now offer enough value to justify staying. It may be underway but incomplete, with a credible next step that makes a further bounded period sensible. The employer may be unable to offer the change even while valuing your work. Or the conversations may continue without meaningful movement. Each outcome supports a different decision; none requires you to pretend that the original expectation has already been fulfilled.
Staying after an unsuccessful test can still be a rational choice. Financial stability, caring responsibilities, geography or a limited range of suitable alternatives may make an immediate move impractical. The difference is that you know why you are staying. You can stop counting on an uncertain improvement as your only development plan and seek work, learning or relationships that remain available within the current constraints.
An internal move may preserve useful relationships and organisational knowledge while changing the work. It is worth considering when the problem belongs to the present role rather than the whole organisation. If the gap is broader, preparing an external move may be more appropriate. Preparation can include understanding your transferable contribution and assessing opportunities as they arise; it need not require a dramatic announcement at work. The decision should be grounded in the actual options you have, not an imagined perfect alternative.
There may also be value in one more clear conversation. If the original condition was too vague, explain the work you want, why it matters and what support would make it possible. Invite a realistic answer. A manager's inability to promise the result is useful information when stated plainly. Repeating the same conversation without a new action or decision, however, is unlikely to make the choice clearer.
The stay test is ultimately yours. Others can explain organisational possibilities, but only you can weigh them against your aims and constraints. You are entitled to revise those aims as you learn more about the work. A decision that made sense six months ago does not bind you after the evidence changes.
Stay for a reason you can still defend
A role does not have to meet every ambition immediately to be worth keeping. It should offer something that matters to you now, whether that is development, useful contribution, stability or a realistic path toward a different scope. Name the change you are waiting for, identify what would demonstrate it, and choose a fair point to review the evidence.
That approach cannot remove uncertainty from a career decision. It can prevent a hopeful prediction from silently becoming the reason to stay forever. When the review arrives, you can choose to remain, renegotiate or prepare a move with a clearer account of what the role has actually become.
