How to Think One Level Above Your Current Role
Do you do everything your role asks of you and still watch someone else get picked when the next big opportunity comes along? You hit your targets, deliver on time and rarely drop the ball, yet somehow you’re still seen as someone who executes well, not someone who’s ready to lead.
You may wonder what you need to do to prove you’re ready for more.
The answer is rarely more effort in your current role. It’s developing a different attitude of thinking. Most people operate at the level their job title asks of them—they solve problems handed to them, make decisions their role permits and wait for direction on anything bigger. This keeps them reliable. It doesn’t make them promotable.
The people who move up aren’t necessarily the ones doing the most work. They’re the ones already thinking, deciding and acting one level above where they currently sit.
In order to get the results we desire, we must do two things. We must first create the space to reason in our thoughts, feelings, and actions; and second, we must deliberately use that space to think clearly. Once you have mastered this skill, you will find you have an unstoppable advantage.
― Shane Parrish, Clear Thinking
Use these practices to think one level above your current role.
Solve problems before they’re handed to you
Most people wait for a problem to be assigned to them before they act on it. Waiting to be told what to fix keeps you at your current level. Staying in your lane, not overstepping and letting the person whose job it is to handle the situation take control may feel like the right thing to do. But this instinct is exactly what signals you’re not ready for more responsibility.
You notice a process that keeps causing delays for your team, but since it’s officially not your problem to solve, you mention it in passing and move on.
A customer complaint pattern is forming that nobody’s tracking yet. You see it three months before your manager does, but you wait for someone to ask you about it.
People who think a level above don’t wait for a problem to become official before addressing it. They notice it early, often before it has a name, and start working on it quietly while everyone else is still waiting for direction.
Use these practices to solve problems before they’re handed to you:
- Notice what keeps almost becoming a problem, not just what already is one. Recurring near misses are usually early warnings nobody has named yet.
- Bring a proposed fix, not just the observation. Flagging an issue is useful. Flagging it with a plan is what gets noticed.
- Act on small problems within your control instead of waiting for permission to touch them.
The most effective problem-finders become adept at searching for and identifying patterns…refine your ability to “connect the dots” among seemingly disparate pieces of information. Threats do not come to us in neat little packages.
― Michael A. Roberto, Know What You Don’t Know
The person who waits for a problem to be assigned to them is doing their current job well. The person who solves it before anyone even asks is already doing the next one.
Make the decisions your role doesn’t require you to make
Most people escalate anything that isn’t clearly within their authority. Deferring every ambiguous call keeps you exactly where you are. It feels safe—if it goes wrong, it isn’t your fault. But constantly pushing decisions upward signals that you need direction, not that you’re ready to give it.
A client issue comes up that technically isn’t your decision to make, so you forward it to your manager and wait, even though you already know what the right call is.
Two competing priorities land on your desk and instead of deciding which one matters more, you ask your manager to choose for you.
The idea is not to overstep into decisions that genuinely aren’t yours. It’s making calls that are ambiguous instead of routing every one of them upward—the ones nobody explicitly assigned but that need a decision anyway.
Use these practices to make the decisions your role doesn’t require you to make:
- Look for the decisions sitting in the gray zone, the ones nobody owns but someone needs to make. Take those on first.
- Make the call, then inform, instead of asking permission for every ambiguous decision.
- Get comfortable being wrong sometimes. Waiting for certainty before deciding is its own kind of decision and usually the worse one.
Decision making brings together many of the finest traits of contrarian leadership–thinking gray, thinking free, artful listening, delegating authority while retaining ultimate responsibility,artful procrastination, ignoring sunk costs, taking luck into account, and listening to one’s inner voice. Weaving these traits together is an art itself. When it is done well, the result is a thing of beauty and a powerful tool for effective leadership.
― Steven B. Sample, The Contrarian’s Guide to Leadership
Escalating every hard call keeps you safe. Making the ones nobody assigned you is what makes you look ready for the next role.
Second Order Thinking Templates
Become a more effective decision maker by considering both the short-term and long-term implications of your choices.
Create opportunities instead of waiting for your role to offer them
Most people assume their job will naturally expose them to the experience they need for promotion. It rarely does. Your current role was not designed to make you ready for the next one. A job description reflects what the role requires today, not what you need to prove you’re capable of more.
You want to lead a cross-functional initiative, but nothing in your current scope naturally leads there. So you wait for someone to offer it to you.
You’d like exposure to senior stakeholders, but your role doesn’t put you in those meetings. So you assume that exposure just isn’t available to you yet.
Opportunities that stretch you rarely show up on their own. They get built, usually by volunteering for the cross-functional project nobody else wanted, offering to represent your team in a meeting above your level or proposing the initiative that doesn’t yet have an owner.
Use these practices to create opportunities instead of waiting for them:
- Volunteer for the work that sits just outside your job description, especially the kind that touches multiple teams.
- Ask to be included in conversations you’re not automatically invited to and give a clear reason why your input would help.
- Propose the project nobody has claimed yet, instead of waiting for it to be assigned.
If you don’t create new opportunities within the confines of your day job, they may never come your way.
― Herminia Ibarra, Act Like a Leader, Think Like a Leader
A role rarely hands you the experience you need for the next one. You have to build it for yourself, inside the same job everyone else is doing.
Talk in outcomes, not just tasks
Most people talk about their work in terms of what they did—tickets closed, meetings run, deliverables shipped, bugs fixed. How you describe your work shapes how ready you appear for more of it. Describing work as tasks completed is accurate, but it’s the language of execution, not leadership.
You spent the quarter fixing a recurring bug. You describe it as “I fixed 40 tickets” instead of “I reduced support volume by 30 percent,” even though the second version is the one that actually matters to leadership.
You led a project end to end, but when asked about it, you list the steps you took instead of the business result those steps produced.
The shift here isn’t about exaggerating your work. It’s about noticing that the same work can be described at two different altitudes and choosing the one that reflects the level you want to operate at, not the one you currently hold.
Use these practices to talk in outcomes instead of just tasks:
- Translate your activity into its business impact before you describe it to anyone. What changed because of the work, not just what the work involved.
- Practice this in low-stakes conversations first (like status updates) before it matters in a performance conversation.
- Notice when you default to listing tasks and ask yourself what result those tasks were actually in service of.
Results, not effort, is the name of the game. You are rewarded in life by the results you produce, not the effort and time you put in.
― Dan Sullivan, Who Not How
Tasks describe what you did. Outcomes describe what changed. Leaders are evaluated on the second one, so start talking in terms of impact.
Widen what you pay attention to
Most people’s attention is shaped entirely by their job description. Your current role trains you to notice a narrow slice of what’s happening. You track what your role measures, you notice what affects your immediate deliverables and everything outside that scope quietly becomes someone else’s problem to notice.
A shift in a neighboring team’s priorities will affect your project in two months, but since it’s not your team, you don’t hear about it until it’s already a problem.
Company-wide numbers shift in a way that will eventually reach your part of the business, but you only pay attention to your own metrics, so you’re caught off guard when it does.
Thinking a level above means paying attention to more than your role technically requires, not because you’re expected to, but because the person operating at the next level already has to think that way.
Use these practices to widen what you pay attention to:
- Follow what’s happening with other teams, not just your own. Most disruptions arrive from somewhere adjacent before they arrive at your desk.
- Ask what the wider goal is behind your specific task and check periodically whether your work still serves it.
- Read or listen to updates meant for a level above yours, even when nobody requires you to.
We have to think more broadly. Effective risk management requires a holistic approach that transcends a siloed focus on isolated threats. In today’s interconnected business landscape, risks are rarely confined to a single department or function. Instead, they often ripple across the organization, impacting multiple areas simultaneously.
― Hendrith Vanlon Smith Jr., Board Room Blitz
The narrower your attention, the narrower your role stays. Widening it is often the first sign, to yourself and to others, that you’re already operating one level up.
Summary
- Waiting for a problem to be officially assigned keeps you at your current level. Noticing issues early and bringing a proposed fix, instead of just flagging what’s wrong, is what separates execution from leadership.
- Escalating every ambiguous decision feels safe, but it signals you need direction rather than being ready to give it. Making the calls nobody explicitly owns is what builds the track record for bigger ones.
- Your current role was never designed to prepare you for the next one. Opportunities that stretch you have to be built deliberately, usually by volunteering for work that sits just outside your job description.
- Describing your work only in terms of tasks completed is the language of execution. Translating the same work into its business outcome is the language of the level above you.
- Your role trains you to notice a narrow slice of what’s happening around you. Paying attention to what’s happening beyond your immediate scope is often the first real sign that you’re already thinking at the next level.
Recommended Reading
