A manager proposes a better way to welcome new members. The idea is sensible: clearer messages, fewer repeated questions, and a more consistent handoff between teams.
The conversation goes well until someone asks who will prepare the messages, test the process, train employees, and handle questions during the change.
Those details determine whether the idea can work.
As your leadership responsibilities grow, more of your recommendations will depend on people outside your immediate team. Learning to understand their commitments is part of developing the range the next role will require.
Start with the problem people can recognize
“We need to improve onboarding” gives colleagues very little to evaluate.
A more useful starting point might be: “Members are calling to ask what happens after they submit an application. I would like to understand where our instructions leave them uncertain.”
That statement gives the team something to investigate before committing to a broad redesign. It also leaves room for evidence to change the recommendation.
For a problem in your own work, identify what you have observed, how often it occurs, and what you still need to learn. Avoid turning one difficult experience into a claim about the whole process.
Ask the people who would do the work
A change that looks small from one desk may involve several teams. A revised message might require review, a system update, testing, and employee preparation.
Ask each affected colleague what the work would involve. Which parts are straightforward? Which depend on a provider or another approval? When would their team realistically have time?
You are gathering the information needed to make a credible recommendation. Give people enough detail to respond, and allow their answers to change your plan.
Make the tradeoff explicit
When several worthwhile ideas compete for the same people, adding another deadline creates a choice whether anyone names it or not.
Make that choice visible. You could recommend narrowing the first step, sequencing the work differently, or requesting additional capacity. Explain the effect of each option on members, employees, and existing commitments.
For the onboarding example, a first step could be reviewing the current instructions and testing revised wording through the appropriate approval process. A larger system change could follow after the team learns where confusion occurs.
That smaller step still needs an owner, time, and a clear purpose. It should produce useful learning rather than simply postpone the harder decision.
Bring a recommendation people can decide on
Try preparing your next recommendation in five sentences:
Here is the problem we have observed.
Here is the next step I recommend and why.
Here is what it would require from the people involved.
Here is what would need to change to make room for it.
Here is the decision we need and when we should review the result.
Be specific about who can make the decision. An employee can propose a different sequence without having authority to change another team’s commitments. A manager may need to bring the choice to an executive who can resolve competing priorities.
Required controls and obligations also need to be accounted for when considering options. If a deadline cannot move, explain what that means for the scope or timing of other work.
Follow through on the choice
After a decision, tell the affected people what was agreed, what changed, and what remains unresolved.
At the agreed review point, compare the result with the original problem. Did members find the instructions clearer? Did repeated questions decline? Did the team discover a different source of confusion?
Leadership range grows through this whole process: understanding the problem, listening across teams, making a recommendation, and learning from the result.
You can begin with one improvement in your current role. Before bringing it forward, ask one colleague: “What would it take for your team to do this well?”
Keep Ascending.