Bloomfire provides knowledge engagement, aiming to deliver an experience that connects teams and individuals with the information they need to excel at their jobs. Their cloud-based knowledge engagement platform aims to give people one centralized, searchable place to engage with shared knowledge and grow their organization's collective intelligence.
PTS: needed to bring a new senior marketing team member up to speed on how we got to our current TV campaign
Solution: Series featuring consumer insights, why specific spokesperson, agency brief, the entire creative process - scrips, animatics, rough cuts, feedback, and testing at each step. Including the actual creative from each step.
Total time to build: 1 hour
Concept testing:
PTS: things get lost, findable but version control
Solution: everything in one placeConcepts, testing, IHUTs, verbatims, videos with transcripts. Reduces the possibility of missing something, helps with any builds (reuse), but gives us a the chance to dig deeper. Example: search on terms like "indulgent", or "crispy" or "share" much faster
BookStack is fantastic for having business users and not-so-technically-savvy IT users. It enables them to create a documentation they like in a visual way while still forcing them to adhere to logical structure of a document. It works fine even for more technical matters such as integration guidelines, especially when these concern some of the more obscure technologies. The exported docs are presentable but lack any interactivity. Where it lacks is generating heavily technical documentations. Heavier REST or GraphQL integrations should for example be documented through other means. As for developer documentations, there are definitely more suitable alternatives, also.
Quickly reach out to whatever employee segment you want to reach by posting a topic and it will send a notification to everyone in that group with a link to the posting.
Bloomfire saves all of the previous posts so in your free time you can go to the site, and explore the various range of topics others have posted. The information on there will only be as good as the person posting it, but it will be people within your company and industry posting it. So it will always be helpful.
Bloomfire is a place to be noticed by your peers. Have a great topic you want to express, my company allows all to post there as long as we keep it professional. So you can share your ideas or experiences in a safe and productive manner. But we do have some fun on there too!
I would recommend adding a feature to combine different posts/series by job title (so in addition to the Revenue Ops category, there could be a structured walkthrough for Revenue Manager).
Live Q+A sessions for group onboarding initiatives.
Most likely we will renew, our team needs a refresher on possible opportunities to advance our usage and learning of opportunities to move this answer to a 10, can't live without it.
Bloomfire is an easy-to-use platform for posting information and asking questions of my peers. It also has a user-friendly search capability. Yet like any other CMS, the secret to success rests in such items as the ability to use metadata to tag content or posts, and Bloomfire provides a wide range of options to make posting content and subsequently searching for it.
I have not needed to pose questions to the support team yet, as it is a very simple piece of software to use, however, its help documents and the bot ready to answer questions let me know I am in good hands. The help center could load a little quicker, but that's my only complaint.
I like Bloomfire because it is more concise with the work I do whereas Google search engine would provide broader information. It has just been so user-friendly, and easier to use [than] I could have imagined. I would use this program over any other that I have tried in the past.
Confluence, having only a slight advantage in terms of features compared to BookStack, really only makes sense to procure as a part of the Jira bundle. It requires much more maintenance from my experience and does not really deliver any extra value aside from the very strict certifications like HIPAA. DokuWiki and MediaWiki both provided way too much in terms of customizability, not really focusing on the business need. Of course, MediaWiki was conceived for a whole different purpose but is very often seen being used for both internal and public documentation delivery. DokuWiki did not provide the authors with the user-friendly environment that BookStack has and integrated most poorly with LDAP. As for OneNote, which was used for support docs prior to BookStack, it provided the authors with too much of a user-friendly environment, rendering the product of their work very inconsistent. Also, the sharing model was either peer-to-peer or within Teams, neither of which made it easy to audit and supervise.
Spillover within Business IT staff up, nearly double substitutability. This is through the ability of a support technician servicing a different product to find a guide describing how to solve the more frequent issues the way a product lead would do it.
Time to draft and publish a documentation down some 20% compared to previous solution.
OpenSource that integrates fine with enterprise-grade software and somehow even passes security audit. 20 times cheaper to implement compared to Confluence, almost free to maintain.
