New Adoption Model (Viral) vs. The Traditional One (Hierarchical)

| Comment | Tags: , , , , ,

Introducing Kaito, the RFP response automation platform. Try Kaito now!
Image copyright Flickr user Kristin Wall (

There are two main ways to facilitate the adoption of collaborative software: one is on hierarchical scale, also called the traditional model. The alternative way to draw users absorption works exactly in reverse from the first one and that is gradually, from small to big, rather than an instant overall employment. It is highly preferred by bigger business organizations that are autonomous by departments, but it also fits perfectly to the needs of small companies.

The first category that is more inclined to go for the new adoption model is a specific department from a big company. Quandora product is anyway organized in knowledge bases, so that each department can share private information that only concerns a limited number of employees. But the purchase of a collaboration tool can be an independent decision since each section of the corporation administrates its own budget. Sharing knowledge habits may draw attention to particular managers as being an asset for their type of activity, without burdening themselves with marketing the benefits to the rest of the company. It’s a genuine test for the product, which if it will prove useful for a limited group of people, will have a viral effect, spreading naturally across your organization. This will eliminate employees inflexibility towards a new tool and the responsibility of coordinating its implementation and adoption will feel like less of an overload.

Now let’s take a look at the second category: the small business industry is notably growing and so is their investments outlook. The many funding programs allow startups and other SMEs to budget acquisitions meant to assist their progress so that makes the whole expenses agenda less stressful and worry-free. Using a collaboration solution for organizations with reduced number of employees is an ideal setting for businesses with growing plans. Starting to gather and share knowledge content right from the start will ease the adoption process for present users, as they are already homogeneous as a group, thus more open to internal communication. Likewise, the employees to come will see it as a ready confirmed routine and they will only need a training session in order to start using it. Another result is that it will also help with the team coagulation. It’s customary for small businesses to work with distributed teams and this practice may submit the team to different tryouts.

— to be continued —

Happy Knowledge Sharing!

Looking for a great way to ask questions and build knowledge with your co-workers? Quandora enables simple, efficient knowledge sharing with your team, way more fun than a mailing list or a forum. Try Quandora

Comments are closed.