When the next role is unavailable, another year of good work may still leave your title unchanged. A useful response is to prepare a small set of examples showing the responsibility you can handle, then ask which examples matter for a realistic next step.
The video’s portfolio method can be used without assuming that career ladders have disappeared everywhere. This article offers a practical way to prepare for a development conversation. It is a proposed workflow, not a study showing that portfolios cause promotions or a promise that more documentation will overcome a closed position.
Define the decision you want to support
Start with a specific question: do you want broader responsibility in your current team, a move into another team or consideration for an advertised role? Those decisions can require different evidence. A collection assembled for every possible future can become too large to explain.
For example, imagine a fictional support coordinator who wants to own the team’s onboarding process. A record of excellent customer replies is relevant to current performance. To discuss process ownership, the coordinator also needs an example of diagnosing a recurring problem, working with others and maintaining a change after its introduction.
Write down the intended responsibility before collecting material. That gives you a reason to include one project and leave another out. It also gives your manager something concrete to correct if your understanding of the next role is wrong. Our guide to comparing a title with the work it lets you own develops that scope question.
Build a case card for one completed project
CareerOneStop’s portfolio guidance recommends work samples accompanied by context about the project, your contribution and its results. Its work-experience guidance similarly emphasizes relevant accomplishments and specific context rather than a bare task list.
Use that principle to make a one-page case card with five short fields:
- Problem: which recurring onboarding question needed attention?
- Action: what did you create or change?
- Contribution: what did you do, and who else was involved?
- Observed result: what happened when the work was used?
- Limitation: what remains unmeasured or unresolved?
For the fictional coordinator, a sanitized checklist could accompany the card if sharing it is permitted.
Under contribution, separate authorship from collaboration. Perhaps you drafted the checklist, a colleague checked technical accuracy and a manager approved it. Naming those roles makes the account more precise than claiming sole ownership of a team result.
Distinguish an output from an observed outcome
“Created a checklist” describes an output. “New starters used the checklist to complete setup” describes an observed use. “The checklist reduced all onboarding time” is a broader claim that would require stronger evidence.
If you have no reliable before-and-after measure, say what you do know. In the fictional example, the coordinator might record that two new starters used the checklist and that their feedback identified one missing step. Those are illustrative details, not results from an actual company.
A limitation can improve the usefulness of the conversation. “We have not measured time saved” tells a manager what remains uncertain. It also suggests a next task: agree on a proportionate way to evaluate the process. Inventing a percentage would hide that opportunity.
Select a second example that adds something
A second card should help answer a different part of the intended responsibility. If the first shows documentation, the next might show how you handled a disagreement about which onboarding tasks were essential.
Describe the competing needs, the choice made and what you personally did. Avoid turning the account into a story in which everyone else was confused and you supplied the answer. The reader needs to understand your judgment and cooperation, not just the final document.
For this proposed portfolio, two complementary cards may be enough to begin a conversation. That is a manageable starting size, not an evidence-based optimum. Add material only when it answers a real question about your next step.
Ask for the standard before expanding the work
Bring the cards to a development meeting and ask: “Do these examples address the responsibility we discussed? What is still missing?” A useful answer names a capability, a suitable assignment or a condition such as an available role or budget.
If the answer is simply “show more leadership,” ask for an example of a decision you would be expected to handle. Then agree whether a proposed project offers a fair opportunity to demonstrate it. This turns a broad phrase into something you and the manager can revisit.
Also ask who makes the eventual decision and when. A portfolio cannot create an opening or authorize a promotion. Knowing that constraint helps you decide whether further work supports an attainable move or whether you should explore another route.
Maintain an internal and an external version
Keep confidential details inside the appropriate workplace systems. Before reusing any artifact externally, check permission and whether it exposes customer information, internal figures or another person’s work. Removing a logo does not necessarily remove the underlying sensitivity.
For an external conversation, a carefully described case may be more suitable than the original file. If you create a fictional replacement, label it as a demonstration. Do not present invented outcomes as achievements from your employment.
A practical maintenance habit is to update a card when a project ends, then review the set before a relevant conversation. The purpose is a usable record, not an additional reporting job with no audience.
End the meeting with an agreed next action: revise one example, take on one bounded assignment or revisit the decision at a stated point. If the organization cannot offer a route, the same honest examples can support a different conversation elsewhere. Keep the agreed action and review point with the cards, so the next meeting can address what changed.
