Separate Promotion Readiness from an Available Next-Level Role

How can an employee distinguish an unresolved readiness assessment from an unresolved organizational role condition and choose the next useful promotion conversation?

Substantively revised October 23, 2026. Author interpretation, documented cases and hypothetical examples are distinguished below.

A manager can believe someone is ready for greater responsibility while being unable to identify a role the organization currently needs at that level. Those statements can both be true. Confusing them sends the employee back to collect more achievements when the unanswered question concerns organizational scope. A useful promotion conversation identifies which decision remains open instead of treating every delay as the same personal development problem.

Direct answer

Separate evidence of next-level readiness from evidence that the organization has an applicable role, scope and approval path. Ask the responsible manager which condition is supported, which remains unresolved and what information would change the decision. Keep development actions distinct from organizational decisions and dates for review distinct from promises of promotion. Public company frameworks can illustrate these differences, but only the relevant employer's current process can establish the actual requirements and authority for a particular case.

Key takeaways

Readiness and opportunity answer different questions. Readiness concerns the person's demonstrated work against the relevant expectations. Opportunity concerns the organization and role that would use the proposed responsibility. Evidence for one should not be silently substituted for evidence for the other. A positive performance discussion does not necessarily establish an approved next-level position, and an open position does not establish that a particular person is ready for it.

The reason for a delay determines the useful next action. Missing evidence might require a more relevant assignment or a clearer account of contribution. An unresolved organizational need might require a role decision by someone else. Asking the employee to produce another portfolio of achievements does not logically resolve a role that has not been authorized. Equally, pointing to a desirable role does not repair missing evidence of the required capability.

Do not turn the distinction into an automatic explanation for rejection. A manager's statement about business need may itself require clarification, and the employee's evidence may still have gaps. The method creates separate inspectable questions rather than declaring either party correct. Its useful result is a decision status and next review condition, not a predicted promotion date or a claim of entitlement.

Definitions and relationships

Readiness means the relevant decision makers consider the demonstrated work sufficient for the target expectations under their actual process. It is not simply tenure, enthusiasm or a self-assigned score. Dropbox's published promotion principles emphasize sustained demonstrated next-level results rather than a checkbox guarantee or a hope that the person will handle the role. That is an example of a published company principle, not a universal rule binding every employer. [S1]

Role availability means that the proposed responsibility has an applicable place in the organization under the actual process. GitLab's public promotions page explicitly describes situations in which someone can be ready while the business lacks the need, budget or scope for an additional role. The same page warns that it is under review and directs readers elsewhere for up-to-date information. Use this public example to understand the distinction, not as a verified current internal policy or deadline. [S2]

Role expectations describe the work being evaluated. Monzo's published engineering progression framework emphasizes impact and scope while warning against turning progression into a numerical checkbox exercise. This illustrates why collecting more examples is useful only when they address the relevant responsibility. It does not give an outsider authority to assign a Monzo level or transfer one company's levels directly to another. [S3]

The problem: one vague answer conceals several decisions

Consider an invented employee asking whether they can be promoted this cycle. The manager says more evidence is needed. That can mean the current examples do not demonstrate the target responsibility, the reviewer has not read them, the target role is unclear or an organizational decision has not been made. These possibilities call for different work. Repeating the same request for evidence can leave the actual blocker untouched.

Suppose the employee supplies three documented project examples instead of one. If the unresolved issue was whether those projects demonstrate independent responsibility, the additional examples may matter. If the unresolved issue is whether a second management role exists, the number alone does not create that role. Three is not a promotion threshold here; it is an invented count showing why more material can answer the wrong question.

The opposite mistake occurs when a vacancy is treated as proof of readiness. A role opening can establish an opportunity for assessment without establishing who should fill it. The organization still needs the relevant evaluation under its current process. Keeping the two questions separate prevents both unsupported optimism and an endless development plan whose connection to the decision has never been stated.

Root cause: evaluation and organizational design share one conversation

Employees usually encounter the promotion process through a manager rather than through every person who influences role design, finance or approval. The manager may discuss several constraints at once. Without separate labels, a development statement can sound like a role commitment, or a role constraint can sound like a personal criticism. Clarify the type of decision before debating whether the answer is favorable.

Timing adds another ambiguity. A scheduled review can be a time to discuss evidence, a submission deadline, an approval meeting or an effective date. These events are not interchangeable. A conversation planned for June does not itself promise a June promotion. State which event the date concerns and who has authority over the next step rather than using one familiar month to stand in for the whole process.

The employee's achievements can also outlive a particular organizational opening. A role may disappear while the evidence remains relevant to future development. Conversely, a new business need may arise before the person has shown the relevant capability. Neither change requires rewriting the past. Preserve the evidence and update the separate opportunity status so the conversation remains accurate when circumstances change.

Framework: the Two-Condition Promotion Record

The author's Two-Condition Promotion Record has four fields: Target Responsibility, Readiness Evidence, Role Condition and Next Decision. Target Responsibility states the work being considered. Readiness Evidence records the assessment and its limits. Role Condition records the organizational requirement and current status. Next Decision names the owner, required information and event that would permit review. The record separates conditions without inventing an employer's approval process.

Start with Target Responsibility. Replace a broad aspiration such as become senior with a description of the relevant work and the actual framework or role expectation being used. The purpose is not to write a new job description without authority. It is to ensure that the employee and manager are discussing the same destination before collecting evidence or interpreting a delay.

Readiness Evidence records what the responsible reviewer considers demonstrated, incomplete or not yet assessed. Keep favorable and unfavorable information visible. A manager's preliminary view should not be renamed a final panel decision. If a claim depends on sustained work, ask what period and situations the current evidence covers rather than inventing a universal required number of months from another company's framework.

Role Condition asks whether the required next-level work exists, whether the relevant organizational decision is made and which dependencies remain. Budget, role scope and approved position are possible questions, not assumptions that every employer uses identical gates. Where the manager does not know, record unknown. Do not treat the absence of a refusal as confirmation that the opportunity is approved.

Next Decision connects an unresolved condition to a useful action. If evidence is incomplete, identify the actual missing responsibility and how it can be assessed. If the role condition is unresolved, identify the person or process responsible for that decision. If both are unresolved, keep both actions. A review date tells the parties when to inspect the status again; it does not turn the record into a promise.

Application: distinguish four states without assigning a probability

The simplest logical illustration uses two conditions, each either supported or unresolved for this exercise. Supported readiness and supported role conditions allow the case to proceed under the real approval process. Supported readiness with an unresolved role condition calls for an organizational clarification. Unresolved readiness with a supported role condition calls for assessment or development. Both unresolved means neither part should be assumed complete.

These four combinations are an author's reasoning aid, not an employer policy, scoring model or prediction. Real processes can include additional requirements. The categories also simplify statuses such as disputed or partly evidenced. Their purpose is to prevent one unanswered question from being hidden inside another, not to claim that two ticks automatically authorize promotion.

Use plain language for the actual case. For example: the manager considers the current project evidence relevant, but the target scope and approval owner remain unconfirmed. That sentence preserves positive information while naming the missing decision. It is more useful than either you are definitely ready or you need to do more, because it identifies what the next conversation must establish.

Case study: another project would not answer the role question

Imagine a hypothetical engineer who has led two relevant changes and receives a positive preliminary readiness assessment. They request a management promotion. The organization currently has one team and one manager, and no decision has been made about creating another management role. These numbers describe an invented case, not a staffing rule or an assertion that one team can never support multiple managers.

The employee proposes completing a third technical project to accelerate the promotion. That project may support continued engineering development, but it does not by itself resolve whether the organization needs another management position or whether management is the right target role. The Two-Condition Promotion Record keeps those questions separate instead of treating a larger evidence packet as a universal remedy.

The useful next action is to clarify the intended responsibility and organizational decision, while preserving the preliminary readiness view within its actual scope. A different role or development opportunity can be explored if appropriate, but this guide does not claim it is available. No actual employer, promotion panel or employee record was examined for this case, and no outcome is promised.

Failure example: a review date becomes a promised effective date

A separate hypothetical employee and manager agree to revisit the case after eight weeks. The employee records promotion in eight weeks, while the manager intended a discussion of the evidence then available. At the review, the role remains unresolved. The disagreement began when a date for examining the case was converted into a guaranteed outcome without the relevant authority or confirmation.

The correction is to label the event. An eight-week review means inspect the stated conditions at that time, unless the actual employer process and authorized agreement establish something more. It does not supply a universal trial period or entitlement. Keep submission, decision and effective dates distinct where the real process distinguishes them, rather than making one calendar entry carry all three meanings.

The record should also state what happens if the condition remains unresolved. That can be a further clarification or another legitimate career decision by the employee, not an automatic extension of extra duties. This guide offers no legal interpretation of an assignment or pay agreement. It makes the planning conversation specific enough that the parties can identify what has and has not been decided.

Organizational uncertainty should not erase development evidence

A delayed role decision can be disappointing without making earlier work meaningless. Preserve the examples and the assessment actually made. If the target role later changes, check which evidence still applies rather than describing the employee as having lost capability overnight. A status record can change because the opportunity changed while the person's demonstrated contribution remains the same.

The reverse also matters. A ready label should not become permanent immunity from new expectations. If the actual target responsibility changes, the assessment needs to be matched to that responsibility. Keep the original assessment's scope and date. This avoids using an old positive discussion as proof of readiness for a materially different role or a wider responsibility never considered by the reviewer.

The tradeoff is between clarity and unnecessary bureaucracy. A short record of the target, two conditions and next decision can be enough. A large dossier cannot compensate for an unidentified approval owner. Use detail where it helps resolve a real uncertainty, and avoid collecting confidential material merely to make the packet appear substantial. Follow the actual employer's information-handling requirements.

Counterargument: good performance should already be enough

It is reasonable to expect good work to be recognized. That expectation does not establish that every recognition must take the form of a particular next-level role. The relevant process can distinguish current performance, development and changes in responsibility. Ask what recognition and progression mechanisms actually apply rather than assuming one mechanism must answer every favorable assessment.

This distinction should not become a shield for vague management. A useful response identifies the actual condition, evidence and decision owner. If the explanation remains unclear or inconsistent, record the specific unresolved question. The method does not prove that a business justification is sound; it prevents that justification from being confused with an assessment of the person's work.

Public frameworks can help formulate better questions, but they do not settle a private employment decision. Dropbox's principles, GitLab's public example and Monzo's scope discussion describe their respective documents. Their value here is conceptual specificity. Do not present them as a common global standard, a verified current private procedure or a promise that another employer must use the same criteria.

Common mistakes

Do not count projects, years or favorable comments as an automatic promotion threshold. Ask what the evidence demonstrates against the actual target. Do not use another organization's framework as an entitlement. A documented example can inform a conversation while remaining limited to its own company, version and purpose.

Do not diagnose every delay as a readiness gap or every disagreement as a missing budget. Keep unknown conditions unknown until relevant information supports a status. Do not name someone an approval owner merely because they are the closest manager. The actual process determines who can assess, recommend or authorize each stage.

Do not turn a review date into a promised outcome, or a preliminary readiness view into final approval. Do not ask for indefinite extra work without a stated connection to the unresolved question. A bounded next decision is more useful than another generic instruction to demonstrate leadership when nobody has said which responsibility or condition remains unproven.

Action plan

Write the actual target responsibility and identify the current relevant framework or role information. Ask the responsible manager to distinguish the readiness assessment from the organizational role condition. Record what is supported, what is unresolved and where the information comes from. Preserve preliminary, final and unknown statuses rather than collapsing them into a single yes or no.

Connect each unresolved condition to the appropriate next action and decision owner. Development work should address a stated evidence gap; an organizational decision should be assigned to the relevant process. If a date is agreed, label whether it concerns review, submission, decision or effect. Do not infer a promise from a calendar entry alone.

Revisit the record when the target scope, evidence or organizational position changes. The useful conclusion is not a predicted promotion probability. It is a clear account of the actual case and the next question that can move it forward, allowing the employee to make informed career choices without confusing more effort with a decision outside their control.

FAQ

Can someone be ready when no next-level role is available?

Conceptually yes. GitLab's public page gives that example while warning that the page is under review. Use it to distinguish the questions, then check the actual employer's current process. It does not establish the status of a particular employee or an applicable deadline. [S2]

Does an available role prove that I am ready?

No. Availability concerns the opportunity; readiness concerns the relevant assessment of demonstrated work. The actual process can require evaluation before deciding who fills the role. A vacancy cannot substitute for evidence of the required responsibility.

How many projects guarantee promotion?

No universal number is supplied. A count does not show whether the projects demonstrate the target expectations. Dropbox's published principles reject a checkbox guarantee and emphasize demonstrated sustained next-level results. Apply the actual relevant process rather than inventing a numerical threshold. [S1]

Should every delay lead to another assignment?

Only connect development work to an identified evidence question. Another assignment may not resolve an unapproved role or unclear scope. Ask which condition it would address and how its result would be reviewed instead of assuming additional work is always the appropriate next step.

What should the target responsibility describe?

Describe the actual work and scope being considered, using relevant employer information. A title alone can hide different expectations. The record is a clarification tool, not an authorization to create a job description or assign a level without the appropriate decision makers.

Is a manager's positive view final approval?

Not automatically. Preserve whether the view is preliminary, a recommendation or an authorized final decision under the actual process. A favorable conversation can be useful evidence without proving that every approval stage or organizational condition is complete.

Does a review in eight weeks promise promotion then?

No such inference follows from a review date alone. In the invented example, eight weeks names when the conditions will be examined again. Submission, decision and effective dates may be different events and should be labeled according to the real arrangement.

Can I use a public company framework to establish my level?

Use it as a scoped reference for questions, not a universal verdict. Monzo's published framework emphasizes scope and impact and warns against numerical levelling exercises. Another employer can use different expectations and authority. The relevant current process determines the actual assessment. [S3]

What if the manager does not know the role status?

Record it as unresolved and identify the appropriate information or decision owner. Unknown is not approval or refusal. This preserves the readiness discussion without inventing an organizational commitment that the manager has not established.

Does the method prove a business explanation is justified?

No. It distinguishes that explanation from the readiness assessment. The actual evidence and authority still need examination. A clear record can expose an unanswered or inconsistent question without declaring either party correct in advance.

Should older positive evidence be discarded after a delay?

Not automatically. Preserve the work and the assessment within their original scope. If the target role changes, review relevance to the new responsibility. A changed opportunity does not itself erase demonstrated contribution, and an old assessment does not automatically cover a different role.

Are the employee cases real promotion outcomes?

No. The project counts, staffing example and eight-week review are hypothetical. No real employer panel or employee record was tested. The primary documents support the scoped mechanisms discussed, while the cases illustrate the reasoning without claiming measured outcomes.

Does this guide establish legal rights or pay entitlement?

No. It structures a promotion discussion and makes no legal, contractual or compensation entitlement claim. A separate question about an actual agreement requires the applicable authoritative information rather than an inference from the examples here.

What if both conditions remain unresolved?

Keep separate next actions for the evidence and role questions. Do not assume completing one resolves the other. The four-state illustration is a reasoning aid, not a replacement for additional requirements in the employer's actual approval process.

What belongs in the final conversation note?

State the target responsibility, actual readiness assessment, organizational role condition and next decision with its owner and event. Label uncertainty and dates precisely. The note should explain what could move the case forward without promising an outcome it does not authorize.

Recommended books

Thinking in Systems by Donella H. Meadows helps separate individual development from organizational conditions. Use its attention to boundaries when one favorable assessment is being asked to explain every part of a promotion decision. It does not supply an employer's policy or a probability of advancement.

High Output Management by Andrew S. Grove is useful for examining how managerial decisions connect responsibilities, organizational needs and evaluation. Read it to sharpen the questions about the target work and decision ownership. A management book does not authorize a role or replace the actual promotion process.

The Making of a Manager by Julie Zhuo helps readers consider the responsibilities involved in a management transition. It is particularly relevant when the desired next role is management and an employee is treating it only as recognition for technical work. Match the actual responsibility before assuming that a positive engineering assessment answers the management question.

Further exploration

Construct two hypothetical cases with the same readiness evidence but different organizational role conditions. Then hold the role constant and change the evidence. Identify which next action changes in each case. This tests whether the conversation is responding to the actual unresolved condition rather than prescribing more work regardless of the problem.

The durable decision is to identify the next question that matters. Readiness evidence, organizational opportunity and approval authority can each be necessary without being interchangeable. Keeping them visible turns a vague promotion conversation into a reviewable account of what is known, what remains open and who can act on it.

Primary evidence sources

Related concepts: systems thinking, wealth structure, and the survival loop. Read the editorial policy and citation guide.