2. Formulate a plan and gather your crew
The first question you should ask yourself is, is change really necessary? It’s unlikely that senior staff will commit to change if things are ticking along nicely as they are. They may not doubt that there are benefits to your idea, but have you considered the costs and organisational changes that will be required? Do they weigh up against the perceived benefits?

To answer the question honestly, begin by laying out both the problem and your proposed solution as clearly as possible. The importance of the issue to others will depend heavily on how you frame it. A new development in your IT software for example, may seem trivial until you’ve clearly outlined how this will support a strategic goal, such as increasing responsiveness for customers. Then it begins to matter. Once you’ve framed it in the context of the bigger picture, senior staff will take an interest.
Once your plan is clear, don’t try to go it alone. Involve colleagues at your level and tap up members of your own network. With a coalition of staff, not only will you build a pool of advocates for your idea, but you will gain expertise in various areas of the business and add credibility to your proposal.
3. Expose your idea to criticism
Once your proposal is in place, it’s time to put your ego aside and invite criticism. Firstly, meet with your immediate team and present your ideas to request their input. It’s perfectly possible that they may raise issues that you hadn’t even thought of and it’s far better to have these weaknesses exposed sooner rather than later. You may also meet objection in the form of “but the system we have is good enough” giving you the chance to practice your response.

It’s important that you show genuine interest and genuine willingness to listen to the input you receive from others. A barrage of critiques is actually preferable to a lacklustre, non-committal response. Indifference means that people don’t care and if this is the case, you’ll be hard-pressed to get their support further down the line.
Go into any discussion armed with questions to draw your crew around you. “What am I missing?” “How can I make this better?” Genuine curiosity is invaluable and will show the team that you’re looking to make changes that will benefit them all. Acknowledge criticism and make sure everyone is on the same page, be sure to ask for clarification if someone’s points are not clear. The ultimate goal is to achieve mutual understanding.
4. Tell your story and be and prepared to compromise
The meeting is scheduled, you’ve developed a concise pitch and you have an idea that people are starting to get on board with, don’t fall at the final hurdle by not thinking through your communication methods.
Centre your pitch around a solid value proposition and provide your target audience with the information they need to make a decision. Furthermore, utilise your skills as a storyteller. Human beings are hardwired to understand stories, so refrain from throwing dreary stats at your audience. A simple way to this is to begin at the problem and walk them right the way through to your solution. It doesn’t have to be complex, but it should hook your audience.

And finally, don’t become so tied to your idea that you’re unwilling to listen to the concerns and criticisms of others. Approach any meeting with a clear and defined proposal but one that’s open to change. By working this way, you could end up with a workable solution that isn’t your original idea but does accomplish your desired outcome.
5. Maintain communication
Once a course has been set, it’s your role to preserve communication throughout. Outlining your plans and then following up with radio silence will win you no favours. Throughout execution, be sure to reaffirm goals and update stakeholders. This contact is invaluable in ensuring senior figures are engaged throughout the entire process. It is easy to assume that once a project is being executed, stakeholders understand their role and will remain focussed on the deliverables, but this assumption can easily become the downfall of the project. Throughout the process, remind associates of the project goals and how the role they play to reduce the risk of decreased buy-in.
If you encounter difficulties at any point, don’t be afraid to elicit advice. After all, people who ask for advice are seen as more trustworthy not less. “What would you do if you were me?” will elicit candid and valuable guidance to help you along the path.