Communicating goals and shared vision
Who is this article for?
Administrators and project leads beginning their journey with Ideagen Healthcare Guardian.
No special access or permissions are required.
Rolling out new software in an organisation is more than just a technical implementation—it’s a people-driven transformation. The success of any rollout depends heavily on how clearly the vision is communicated and how widely it is embraced. That’s why crafting a well-defined, shared vision is not just helpful—it’s essential.
When everyone involved—from project leads to future end users—understands the purpose of the initiative and how success will be measured, it fosters alignment, builds trust, and encourages meaningful engagement. Clear communication of the “why” behind the change helps turn passive users into active participants.
Set clear goals and objectives
A shared vision starts with clarity. Define what success looks like from the outset and, where possible, make sure you:
- Align with business strategy: Ensure goals support broader organisational priorities.
- Be specific: Use SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound).
- Involve stakeholders: Gather input from different departments to ensure relevance and buy-in.
SMART Example: “Reduce manual reporting time by 40% within 3 months of rollout.”
Define success measures
Success isn’t just about going live; it’s about delivering value.
A success measure is a specific way to evaluate whether a project or initiative has achieved its intended goals. It’s a concrete indicator that helps you track progress, demonstrate value, and guide decision-making.
Some measures you might want to consider:
Quantitative (measurable with numbers):
- Percentage of users actively using the software
- Reduction in time spent on manual tasks
- Number of support tickets before and after rollout
- Increase in data accuracy or reporting speed
Qualitative (based on feedback or observation):
- User satisfaction ratings
- Feedback from surveys or interviews
- Observed improvements in collaboration or workflow
In both measures consider measuring rates before and after implementation to demonstrate impact.
Example: Achieve 80% active usage within the first 6 weeks.
Communicate effectively to users
In any software rollout, having a clear vision is essential but it’s not enough on its own. That vision must be understood, believed in, and acted upon by the people who will use the system. That’s where communication comes in.
Why communication matters
Communication is the mechanism that:
-
Translates strategy into action: It turns abstract goals into tangible steps for users.
Builds trust and transparency: When people understand the “why” behind the change, they’re more likely to support it. - Reduces resistance: Clear, consistent messaging helps address fears, correct misconceptions, and reduce uncertainty.
- Drives engagement: People are more likely to adopt new tools when they feel informed and involved.
What effective communication looks like
-
Timely: Start early and keep the conversation going throughout the rollout.
Targeted: Tailor messages to different audiences—what matters to a finance team may differ from what matters to customer service. - Two-way: Create channels for feedback, questions, and dialogue—not just announcements.
- Visual and accessible: Use visuals, demos, FAQs, and simple language to make complex ideas easy to grasp.
Example in practice
Instead of saying:
“We’re launching a new incident reporting system next month.”
Say:
“We’re introducing a new incident and risk management system to help you report, track, and resolve issues more efficiently. It will streamline workflows, improve visibility into risk trends, and support compliance efforts. Training sessions begin next week and here’s how to register...”
Tips:
- Tailor the message: Speak to different user groups in language that resonates with them.
- Use multiple channels: Email, intranet, town halls, videos, and team meetings.
- Be transparent: Share the “why,” not just the “what.” Explain benefits and address concerns.
- Celebrate milestones: Recognise early adopters and share success stories.
- Be visual: Create a simple visual roadmap to show users where they are in the journey.
Save some time! Use our attached templates below for quick and easy communication you can share digitally and physically!
Next: Building user knowledge