Skip to main content
All CollectionsAdmin Guides
Tips and tricks for the internal rollout
Tips and tricks for the internal rollout

This article points out the most important aspects for the rollout of Zive in your organization

Updated over a week ago

Rolling out a new tool within your organization can be challenging. For most people change and innovation causes a certain degree of uncertainty, often preventing quick adoption. We all know that breaking habits is not always easy, even when we know it would be for the better, and objectively there might be clear arguments for it.

That's why supporting our customers with preparing the internal rollout is an essential part of the onboarding for us. We will make sure that you, as the project lead or project group, have a clear plan at hand and feel confident to execute it. This way we can ensure together that everyone within the organization benefits from Zive as quickly as possible.

At this point, it's important to point out that the exact approach for the internal rollout is very individual and depends on different factors, like size, industry and culture of your organization. That's why the following tips and tricks should be seen as an orientation and ideas based on our experience.

In order to consider the individual situation of each customer, we have a dedicated phase at the end of the onboarding to prepare the rollout together with you.

1. Leverage and empower the right people

Depending on the size of your company and will be difficult to impossible to reach all people at once. Therefore, it can be extremely helpful to identify individuals that can drive the rollout and adoption. This can start with the project group that might have already been involved from the very beginning, but even beyond that it often makes sense to target specific people and involve and engage them first.

  • Senior leaders and executives

  • Managers and team leads

  • Influential or experienced team members

  • ...

You might also have people in mind that you know are often confronted with the challenges Zive is solving and might be excited to get on board early. Maybe there are people who are more open to change and regularly drive innovation in their team or even across teams. Whatever it is, it's definitely worth asking yourself who could be people accelerating the rollout in different ways:

  • Endorse Zive as a new tool in their communication

  • Become a champion or ambassador within a team or department

  • Develop into an expert to support other colleagues with challenges or questions

  • ...

By the way, you can also apply this thought on team level. Maybe you have specific teams or departments that might enjoy a role as early adopters and you know are especially influential within the company.

2. Make it relevant and specific for teams

What would be more interesting for you to try out:

  • A tool that is announced as a new company-wide tool in a generic newsletter or

  • a tool that solves exactly the challenges that you know from your day-to-day work?

Not saying using company newsletters is generally a bad idea, but I hope the point I'm trying to make is clear. If people can relate to the challenges that are solved with a new tool and see concrete examples and use cases relating to their topics and tasks, it's much more likely that this will spark their interest, making it 100% worth investing time in.

Connecting this to the previous tip, having a champion in the different teams often helps to collect use cases and prepare targeted and individualized communication for each team. While first teams are starting to use Zive it can also make a lot of sense to collect early success stories and share them with other teams that have similar challenges.

3. Communicate strongly and steadily

Considering the previous tip and specifying the content of your communication to the team you are targeting is already a great step towards strong communication. Beyond that, there are a few generic tips for communication, based on our experience.

Focus on "why"

I know you hear that a lot in all different kinds of contexts, but it's true for the rollout of a tool as well. Highlight the benefits people and teams can expect from using Zive over the functionalities. Understanding the value for you individually, your team or your peers is usually the best motivation to start using a tool or changing.

Be variable and creative

Do not focus only on one channel, like the company newsletter. Teams and colleagues usually consume information very differently. Maybe even more importantly, think of communication not just as announcements or messages to introduce Zive, but also as formats to support people using it, e.g. sessions, best practices, ...

Stay on it

You will not reach everyone immediately. Changes are always a process and require continuous communication. You can use updates (e.g. our regular product improvements) or new impressions (e.g. success stories from other teams) to avoid being annoying with the same message over and over again. See regular communication as a possibility to update and support your colleagues continuously.

4. Trust us to support you continuously

As mentioned in the beginning, we are aware of the importance of the internal rollout and are happy to support you personally with our Customer Success team and with a lot of helpful features in the product itself to make your rollout enjoyable and successful.

With our experience and under consideration of the individual situation and challenges, we will prepare the rollout together and be at your side along the way, providing resources and coordinating actions like e.g.

  • Product demos

  • Product tours

  • Trainings and webinars

  • Documentation and guides

  • Templates (e.g. for preparing team-specific use cases)

  • ...

Additionally, we remain available even after the completed onboarding, ensure constant feedback loops and improve the experience for your users consistently.

Did this answer your question?