What's the purpose/goal of your KB?

To provide our teammates an organized, efficient, and complete environment from which to learn and learn quickly.

What solutions did you approach before you decided to go with Helpjuice?

Confluence was where ARK 1.0 was housed and there were discussions about restarting in Confluence, SharePoint, or other sites -- eventually Helpjuice won out.

Why did you decide to use Helpjuice?

We originally had "ARK" (the name of our site) on Confluence. To make a long story short, we realized we needed to start from the ground up because ARK 1.0 on Confluence was messy and unorganized. It had been created without structure or management and the consequences was that it was inefficient. After some shopping of different sites, we found Helpjuice had the most features of stuff we were looking for, so we began a pilot. 

Many of the other solutions were missing certain features that we really wanted. I don't remember the sites specifically (other than Confluence and Sharepoint b/c we were already using them) but it was difficult to find sites that could do ALL of the following: 

 - Track page views and user searches

 - Be highly organized

 - Tag documents with keywords

 - Flag documents that were coming up to be expired

 - Provide different levels of access to users

 - Be visually appealing

 - Be able to link/house various document types (i.e. PPT, Excel, etc.)

What's your favorite Helpjuice feature?

Clean layout and ability to organize. I've also been wildly impressed with the customer service thus far. What I find Helpjuice allows us to do is start with a base User Interface that is sleek AND separates out documents in the way we need. Navigating the UI is easy and from there, the site still remains clean and easy to run, allowing people to find what they need. If they choose to use search instead, this too is A) very easy and B) very accurate because of the tagging feature. In short, HelpJuice has enabled our teammates to get to the document they're looking for in 3 clicks or less.

What problem are/were you looking to solve with Helpjuice?

The main problem we were looking to solve with HelpJuice was 2 fold: 

1) Onboarding - our team has no formal training to speak of and we needed a highly-organized and intuitive site that could house/tag onboarding materials. Part of this is our own content creation, yes, but another aspect of it is moving it to a platform that is easy to use and navigate

2) Learning Quickly - again, part of this is our own content creation, but we wanted to house highly-organized libraries of content so that when teammates get placed on a new project, they can become "Dangerous" quickly. We're a consulting-esque team so being able to understand business processes efficiently and quickly (at least at a base level) is imperitive, no matter the teammates tenure.

What kind of an impact has Helpjuice had?

Relating back to the top 2 problems we were trying to solve:

1) Onboarding. We anticipate this will reduce onboarding time by about 50% (probably 6 month-ish) while also allowing teammates to come out the other side of Onboarding knowing/retaining 70% more information since they'll understand the whole business and lanes (plus other stuff) vs. just what they need for their project.

2) Learning Quickly. We anticipate this will reduce the amount of time needed to "learn quickly" to ~ 1 week and teammates can largely do it on their own. Previously, they would have needed 2-3 weeks per project with probably alignment with stakeholders or lane experts along the way (taking up more people's time). Now, they'll still meet with those people, but have a base foundation of understanding already so they can contribute to the conversation and solution quicker.