You're navigating complex IT infrastructure changes. How can you earn trust from non-technical stakeholders?

- Use clear and simple language when discussing IT infrastructure. - Avoid jargon and technical terms that may confuse non-technical stakeholders. - Explain how changes will affect stakeholders in practical terms. - Focus on benefits and outcomes rather than technical details. - Ensure stakeholders understand the relevance and impact of IT changes.

I think this is the big one. Non-technical people really appreciate when technical people stop throwing around acronyms and speak to them in natural language. Also, I usually ask them to show me their business process before I ask them a question about the data coming from that process. They are much more engaged when they actually explain their workflow.

To gain stakeholder buy-in, it's essential to emphasize that the new IT tools are specifically designed to enhance their productivity and streamline their workflows. These tools are meant to work for them, not the other way around.

To earn trust from non-technical stakeholders during complex IT infrastructure changes, transparency and communication are key. Provide regular updates on progress and setbacks, using clear, non-technical language. Create visual aids like charts and diagrams to illustrate how changes will impact their work. By fostering an environment of openness and ensuring stakeholders understand the benefits and challenges, you build credibility and demonstrate your commitment to their needs and concerns.

- Invite stakeholders to meetings to discuss IT changes. - Encourage their input and suggestions. - Tailor IT changes to better serve stakeholders' needs. - Gain valuable insights for the IT team through stakeholder involvement. - Foster a sense of ownership and investment in the project's success.

- Be transparent about potential challenges and the timeline of IT infrastructure changes. - Provide regular updates on progress and any issues or delays. - Demonstrate respect for stakeholders' need for information. - Show commitment to keeping stakeholders informed. - Maintain trust by being honest and proactive in communication.

It circles back to the use of simple and clear language. I usually explain the expected deliverable to the business people using their own workflow. E.g. you will be able to measure the time it took in process A but not the number of products involved in process A. This clarifies exactly what we are building and they just trust you much more when you say things as they are.

Once in a project, a co-worker indicated the most optimistic end date, because the stakeholder told him "that's your time quickly" he had to work even on weekends to finish on time, when he told the stakeholder what he did, he asked him: Why didn't you talk to me when you saw that you were not going to comply? We can have the best expectations, but if something changes it is better to report it

- Offer training sessions and resources to support stakeholders during the transition. - Address concerns proactively and provide assistance as needed. - Demonstrate commitment to a smooth transition to new IT infrastructure. - Reinforce stakeholders' trust in your ability to manage changes effectively.