If you want to rise within your company, learn how to make your ideas move.
Having good ideas is not enough.
You can see a problem before everyone else. You can think of a better approach. You can prepare the numbers, build the presentation, and explain your recommendation clearly—and still watch the idea go nowhere.
That can be frustrating, especially when you know the idea has merit.
But there is a capability beyond having good ideas.
You need to learn how to help other people say yes to a useful move.
And once you become good at that, something else begins to happen. People stop seeing you only as someone who does assigned work. They begin trusting you with problems, decisions, and opportunities that require judgment.
That is one way careers grow.
When a good idea goes nowhere
Imagine this.
You have been watching the same problem for months. Customers keep waiting because two departments have to approve something that should be simple. You talk to the people involved. You look at where the delays happen. You even think of a way to remove one approval without increasing risk.
You finally bring the idea to your manager.
You explain everything.
Your manager nods.
“That makes sense. Let’s look at it.”
Three weeks later, nothing has happened.
Maybe you follow up. Maybe you decide your manager is not interested. Maybe you tell yourself this is why employees eventually stop suggesting anything.
Then, two months later, someone more senior proposes something remarkably similar.
Suddenly there is a meeting about it.
That moment can make you bitter.
Or it can make you curious.
What helped the second idea travel when the first one did not?
That is a useful question if you want to rise inside an organization.
The conventional game is to sell the idea
The conventional game begins with the idea.
“I have a suggestion.”
“I think we should change this.”
“I have a proposal.”
“Here is a better way.”
Then comes the explanation. You present the advantages, defend the recommendation, answer objections, and try to convince people that your idea deserves approval.
There is nothing foolish about doing this. Good ideas should be examined carefully.
But notice what is happening on the other side of the table.
You may be thinking:
Is this a good idea?
Your manager may be thinking:
Can we afford it? Who will own it? What gets delayed if we do this? Will another department resist? Has somebody tried this before? What happens if it fails? Is this more important than the five problems already competing for attention?
You are selling an idea.
Your manager is making a choice.
Those are not the same game.
Begin with what matters, not with your idea
Try a different opening.
Instead of:
“I think we should redesign our onboarding process.”
say:
“Our new hires are still depending heavily on supervisors after their first month. If we can help them handle three common tasks independently by Week Two, we can reduce repeated questions and give supervisors some time back. I think there is a small change we can test with the next two hires.”
You may eventually recommend the same onboarding change.
But now the idea has a job.
It serves something that matters.
This is one of the most useful habits you can develop at work: before presenting your idea, find the win behind it.
Ask what the idea is supposed to move.
Will customers wait less?
Will an employee make fewer avoidable mistakes?
Will your team complete something faster?
Will managers spend less time correcting work?
Will fewer decisions travel unnecessarily upward?
Will the company save money?
Will an important project have a greater chance of succeeding?
You are not merely improving something because improvement sounds good. You are connecting your proposal to a result worth moving.
That is also the larger leadership discipline behind Build Leaders Who Move Work: leadership becomes useful when decisions, conversations, direction, ownership, and action help important work move.
You can begin practising that discipline long before you receive a management title.
Learn the game of the person who must say yes
Your idea does not exist by itself.
Everyone whose support you need is carrying something.
Your supervisor may be trying to hit a production target while dealing with two vacancies. Finance may see a cost that your department does not see. Operations may worry about reliability. HR may be protecting a policy because of problems you have never encountered. A senior leader may be looking at five competing initiatives and wondering which one deserves scarce attention.
If you present the idea only from your side of the table, you force everyone else to translate it into theirs.
Do some of that thinking before you enter the room.
Suppose you want the company to buy new software.
You can begin with the software.
“This platform has automation, dashboards, AI features, and better integration.”
Or you can begin with the work.
“Our team spends about six hours every week transferring the same information between systems. I want to see whether we can remove part of that work before we consider replacing anything.”
The second conversation is different.
You have not hidden your agenda. You have made the problem easier to examine.
And there is an interesting side effect.
Sometimes when you understand the other person’s game more deeply, you discover that your original idea is not the best answer.
That is progress too.
Your job is not to make your idea win.
Your job is to help the work win.
Bring a recommendation, not another problem
There is a particular moment that reveals whether an employee is beginning to operate at another level.
Something has gone wrong.
The employee approaches the boss and says:
“We have a problem.”
Then the employee explains the problem.
The boss asks questions. The employee answers what they can. Eventually the boss starts thinking through the options.
Without anyone noticing, ownership of the problem has moved upward.
Now imagine a different conversation.
“We have a problem with the supplier delivery. I checked the order, spoke with purchasing, and looked at the next production schedule. We have three options. I recommend Option B because it protects Friday’s production with the least additional cost. I need your approval because it changes the purchase amount.”
The employee still needs the boss.
But the boss is no longer being asked to do the employee’s thinking.
That distinction is central to Completed Staff Work Training: bring the decision maker a problem that has been thought through, with relevant information, options, and a recommendation—not merely a problem that now needs to be solved upward.
You do not have to wait for formal training to begin practising it.
When you raise a problem, ask yourself:
What have I already done to make the next decision easier?
That question alone can change how people experience working with you.
Shrink the first yes
The bigger your proposal becomes, the harder it becomes for someone to approve.
A new system.
A company-wide process change.
A complete restructuring.
A six-month initiative.
A rollout across every branch.
You may think the size shows ambition.
The person approving it sees something else: money, disruption, people, dependencies, uncertainty, and more ways for the proposal to fail.
So make another move.
Shrink the first yes.
Do not ask the organization to believe everything you believe.
Give people a chance to find out.
Instead of:
“We need to change our weekly meeting system.”
try:
“For the next three Monday meetings, can we begin by naming the three decisions that must be made before the meeting ends? I want to see whether fewer issues remain unresolved.”
That is a much smaller yes.
But do not confuse small with unimportant.
A small test can expose a bad assumption before the company invests heavily. It can also produce early evidence that makes the next conversation easier.
This is part of what it means to Make Execution Daily. Important ideas eventually have to enter real decisions, conversations, handoffs, meetings, assignments, and customer moments. Execution gives you evidence that another presentation cannot.
Instead of arguing endlessly about whether the idea will work, create a responsible way to learn.
Make the idea easy to try
Many ideas do not die in the presentation.
They die after everybody agrees.
“That makes sense.”
“Good idea.”
“We should definitely do that.”
Then the meeting ends.
Nobody knows who moves first. Nobody knows when. Nobody knows what exactly changes. Two weeks later, the idea has become another memory from another meeting.
Agreement is not movement.
If you want your idea to travel, help people cross the distance between yes and now what?
What happens first?
Who owns it?
Where will you test it?
What changes in the actual work?
What permission is needed?
When will you look at what happened?
Do not leave the room with enthusiasm alone.
Leave with a move.
Do not make people buy the entire future
Sometimes we accidentally make our ideas harder to support because we explain everything they could eventually become.
You begin with one useful improvement.
Then you describe Phase Two.
Then the dashboard.
Then the company-wide rollout.
Then the new roles.
Then the automation.
Then you explain what the system could look like next year.
The small useful idea has suddenly acquired a very expensive future.
The decision maker now has to say yes to all of it.
You do not need that.
Ask for enough commitment to produce the next piece of evidence.
If the test works, you can decide what it has earned the right to become.
If it does not work, you have learned cheaply.
Either way, the work teaches you something.
Bring the proof back
This is where a surprising number of employees stop.
They propose something.
They get approval.
They implement it.
Then they move on.
But if you want to build influence, return with what happened.
Did the new handoff reduce errors?
Did customers respond faster?
Did employees need fewer clarifications?
Did the meeting actually produce decisions sooner?
Did your idea create another problem you did not expect?
Bring that evidence back.
And resist the temptation to use proof only to show that you were right.
Suppose you tested a new handoff process for three weeks.
You might return and say:
“The new process reduced missing information, but it also added too much time before the handoff. I recommend keeping the first check and removing the second.”
That is more impressive than pretending the test was a complete success.
You have demonstrated something more valuable than enthusiasm.
Judgment.
You are showing that you are not protecting your idea.
You are protecting the result.
Make your manager look good without disappearing
There is another trap.
Some employees become good at generating ideas but exhausting to work with because every suggestion becomes a battle over ownership.
That was my idea.
I said that first.
They did not give me credit.
Credit matters. You should not make your contribution invisible, and good organizations should recognize useful work fairly.
But there is a difference between making your contribution visible and needing to own every sentence, suggestion, and success.
An idea often improves as it moves.
A colleague sees something you missed. Your manager changes the proposal. Finance removes a feature. Operations finds an easier implementation. What finally works may no longer look exactly like what you first imagined.
Can you still help it succeed?
You want to become known as someone who makes ideas easier to build on—not harder to touch.
Make the idea easier to own together.
Ironically, this can make your own contribution more visible over time.
People begin to notice a pattern.
When this person is involved, conversations become clearer.
Problems arrive with recommendations.
Useful experiments happen.
People collaborate.
Something moves.
That is a reputation worth building.
Do not turn every problem into your personal stage
There is a danger in an article about rising within a company.
You might start treating every problem as an opportunity to impress someone.
People can feel that too.
If every meeting becomes a chance to display intelligence, every idea becomes a campaign, and every colleague becomes someone you need to outperform, you may gain visibility while losing trust.
The goal is not to look promotable.
The goal is to become more capable of carrying important work.
Promotion may follow. Greater responsibility may follow. Invitations into more important conversations may follow. None of these is automatic. Organizations are complicated, and careers are influenced by many factors.
But you can control the contribution you are becoming capable of making.
Start with one useful problem.
Understand it.
Bring a recommendation.
Run a responsible test.
Follow the proof.
Help other people succeed.
Then do it again.
A practical play: Sell the movement
Call this play when you have an idea that requires somebody else’s support.
Before you present the idea, answer four questions.
1. What matters?
What result, problem, customer need, priority, or piece of work makes this idea worth discussing?
Do not begin with what you want to change. Begin with why the change deserves attention.
2. What should move?
If your idea works, what should become visibly different?
Name something people can recognize.
Fewer revisions. Faster decisions. Less waiting. Cleaner handoffs. A clearer customer response. More work completed without avoidable escalation.
3. What is the smallest useful test?
Reduce the size of the first yes.
Do not ask people to approve the entire future when a small experiment can produce useful evidence.
4. What proof will you bring back?
Decide what you will watch before you run the test.
Then return.
Tell people what moved, what did not, what you learned, and what you recommend doing next.
Your proposal can then sound like this:
“I noticed something that may be slowing us down. It affects ____. I think there is a small change we can test. If it works, we should see ____. Can I try it with ____ for the next ____ and bring back what happens?”
Notice what that proposal does.
It connects the idea to something important.
It makes the first move manageable.
It reduces the risk of saying yes.
And it promises evidence.
You are no longer simply asking someone to believe in your idea.
You are offering a responsible way to find out.
The day a bigger problem arrives
One day, a more important problem will land on someone’s desk.
There will be several people who could be asked to handle it.
Your manager probably will not remember every suggestion you made during the past year. They may not remember the slides you prepared or the exact words you used in a meeting.
But they may remember a pattern.
When you see something that matters, you investigate before complaining.
You think before escalating.
You bring recommendations instead of unfinished problems.
You make useful ideas easier to try.
You bring back proof.
And you help other people win with you.
That is when your career begins to change.
Not because you discovered a trick for persuading your boss.
Not because you became louder.
Not because every idea you had was brilliant.
Because people learned that you can be trusted to move important work.
If you want to develop this capability further, explore MVP: Most Valuable Professionals and other employee-development programs. For the larger leadership system, continue to Build Leaders Who Move Work. And if the challenge is turning important intentions into recurring action and proof, explore Make Execution Daily.
