Best Use Cases of Articulate 360 vs dominKnow | ONE

In a previous article, we outlined the biggest differences between the eLearning authoring suites Articulate 360 and dominKnow | ONE.

We wanted to follow up because all those differences have a common root. The products were designed with different customers in mind, and as a result, the ideal use cases are very different. We touched on it before, but it’s worth examining further.

Articulate 360 is an excellent choice for freelancers, as well as organizations and content development contractors whose responsive authoring, collaboration, and content reuse needs are modest in scope.

dominKnow | ONE provide significant advantages in productivity for organizations whose content development teams are large, scattered, or quickly scaling, as well as those that have large quantities of overlapping learning content. It’s also a much stronger tool for authoring responsive learning content.

What Are the Ideal Use Cases for Articulate 360?

Articulate 360 expands the collaborative possibilities from its flagship product and main draw, Storyline. It’s a great solution for freelancers and small organizations, especially with the add-on product Teams.


Freelance eLearning developers are probably the most ideal target audience for the Articulate 360 product. They benefit from Articulate 360’s features without needing the added functionality of Teams.

Freelancers are unlikely to feel any of the comparative downsides to dominKnow | ONE at all. Desktop-only software is a non-issue when you’re the only content author, as are real-time collaboration, content reuse, and strong administrative control.

On the other hand, Storyline-based authoring is still in great demand and considered an essential by many clients. Few freelancers will run into the expectation that they know or use dominKnow | ONE.

With Articulate 360, Storyline users will gain access to an impressive stock library – course templates, characters, photos, videos, and other assets to make their job easier.

Freelancers who’ve had a make-do review process will find Review 360 to be a blessing. With one click, you can share a project to an unlimited number of reviewers and collect all of their feedback in a single place. The reviews are left in-context on the relevant page, clarifications and additions from other users can be threaded on initial comments, and you can mark issues as “resolved” in the app.

Freelancers whose clients expect robust responsive content may need an alternative tool, but there are plenty of jobs that can be tackled with Articulate 360.

Small Teams

By adding a Teams subscription to Articulate 360, you get collaborative mechanisms that are perfect for small teams.

Teams facilitates real-time coauthoring in the responsive tool, Rise, and asset sharing options in both Rise and Storyline. You also gain user administration capabilities.

Articulate 360 with Teams will work best for organizations that fall within certain parameters. It’s perfect for:

      • Organizations that focus their efforts on traditional or light responsive eLearning
      • Teams with a small number of authors who can be trusted to maintain assets and project files
      • Small content libraries with little audience targeting or content overlap

Outside of those parameters, Articulate 360 could still serve your team, but features found in dominKnow | ONE could help things run more smoothly.

eLearning Development Companies

Articulate 360 works for eLearning development firms for the same reasons as freelancers and small teams. After all, these contractors often exist at the intersection of both.

As small groups working on projects with a limited scope and duration, Articulate 360 with Teams can serve eLearning development companies well.

The same limiting factors for collaboration will apply, however so, certain projects or clients may present challenges.

What Are The Ideal Use Cases for dominKnow | ONE?

dominKnow | ONE is designed for teamwork, content reuse, and the management of large content libraries. Its authoring tools are as robust as any, but dominKnow’s roots are those of a learning content management system (LCMS).

That gives it a different kind of power to dominKnow | ONE and serves a few specific needs that Articulate 360 doesn’t.

Large eLearning Departments and Quickly-Growing or Scattered Teams

dominKnow | ONE’s strong administrative capabilities, fully cloud-based nature, stronger collaborative mechanisms, and native review features can all make a big difference for large organizations or those with particular personnel challenges.

dominKnow | ONE’s administrative capabilities are much more extensive than Articulate 360 Teams. Combined with the fact that all assets and project files are in the cloud, this means greater control and security for your intellectual property – especially compared to Articulate 360 where, due to the nature of Storyline, a lot of IP is scattered across users’ hard drives.

In dominKnow | ONE, administrators can directly change users’ project access or permissions. They also have greater oversight over the work. Admins can see updates and progress on all projects under their control. They can generate executive reports. They can even refine the overall development process with features like custom life cycles and publishing checklists.

All of those features – currently lacking in Articulate 360 – become increasingly necessary for large, high turnover, or quickly scaling organizations. You need strong central control and oversight under those conditions.

Large and growing teams will also benefit from the fact that both dominKnow | ONE’s authoring modes provide better support than Articulate 360’s for real-time collaboration and use by authors of varying skill levels. We discussed this in-depth in the previous article, so we won’t dig too deep here.

Finally, large organizations often have a laundry list of stakeholders that need to provide their input on eLearning projects. The review tools for dominKnow | ONE are similar to Articulate’s but with additional features that help manage the chaos of a long or review process, including review scheduling, automated reminders, and a more streamlined experience for the ones doing the editing.

In Articulate 360, reviews occur in a separate app, so completing edits requires switching back and forth between multiple tabs or windows. In dominKnow | ONE, authors can see and interact with reviewer feedback from inside the editing interface for convenience. Additionally, both Articulate 360 and dominKnow | ONE allow in-context resolution of issues, but dominKnow | ONE also lets you see all unresolved comments compiled in a single place. That can be helpful when managing a large volume of feedback.

Even some small teams can benefit from what dominKnow | ONE has to offer. The cloud-based interface, collaborative features, and administrative control can all help address the unique challenges of geographically distributed teams.

Whether you’re a fully remote organization in just a couple time zones, tagteaming contributors on the other side of the globe, or working in an office but with others who are far away, dominKnow | ONE can reduce delays and confusion by keeping everyone on the same page, communicating easily across time and space with continuous access to the right files.

Organizations that Need Robust and Dynamic Content Reuse

Articulate 360 allows some content sharing, but in a way that works best if your content requires little reuse, is rarely updated, or is fairly modest in size.

That’s because content is shared by duplication. You can’t look up where identical content is located or how many times it’s been used. If something changes, you’ll need to find and change every instance by hand to keep materials consistent.

That makes it a nightmare for Articulate 360 users to ever update content in a massive library, but it’s also problematic for small content libraries with lots of reuse or frequent updating.

When you reuse content in dominKnow | ONE, each project file draws from a single instance of the content. That instance can be edited once for instant, universal updates, and this method also makes it easy to see exactly where and how it’s used.

This doesn’t just facilitate quick updates. A dynamic method of content reuse opens up a world of possibilities for more efficient authoring.

It makes it possible to deliver the same content in multiple formats with little effort, so learners can experience it as microlearning, a formal course, a knowledge base article, or a presentation.

It also makes granular audience targeting much more feasible. By leveraging content reuse, it’s low-effort to make and maintain a company-wide training with role-specific examples or location-specific information.

dominKnow | ONE also makes it possible to apply themes and formatting to content dynamically so that giving a project a revamp, rebranding, or changing the delivery mode is as simple as applying a new template to existing content.

Dynamically applied styles are also great for small but universal changes. If a compliance organization suddenly expects all materials in a new font or size, it’s just a few clicks away.

Projects that Require Sophisticated Responsive eLearning

We covered this fairly extensively in the first article, but it’s worth repeating here. If your goal is to create responsive eLearning that’s highly interactive, varied in format, and innovative in design, Articulate 360 can’t help you. dominKnow | ONE can.

Articulate 360’s responsive authoring tool Rise has come a long way. It was extremely limited when it first launched, in everything from supported languages to interactivities. It’s gained a lot of functionality since then.

Rise works perfectly well for responsive projects with a simple layout, a similar look, and well-established types of interactivity. If that’s what you need, then you’re set.

However, responsive authoring in dominKnow | ONE offers advanced interaction and custom design on par with its traditional authoring. Both modes are similar in capability to Storyline, which puts responsive authoring in dominKnow | ONE leagues ahead of Rise.

In addition to a broader potential for creativity and user experience, dominKnow’s responsive authoring tool supports a greater variety of ways to present content. In Rise, all projects look very similar, like a minimalistic webpage. dominKnow’s Flow makes better use of the responsive medium with project themes that vary from a searchable knowledge base to a traditional course or an instructor-led presentation. You get more possibilities than traditional authoring, not less.


For certain organizations, dominKnow | ONE can improve the security of intellectual property, increase supervision for large or scattered teams, make it easier to manage large amounts of input, and facilitate collaboration from near or far.

Its content reuse capabilities can dramatically increase the efficiency of authoring and maintaining projects with overlapping content, making it possible to offer audience targeting or multiple styles of eLearning on the same topic with limited resources.

dominKnow | ONE can also offer responsive authoring that makes full use of the format’s flexibility while providing hefty creative power.

For individuals or organizations that don’t need any of the above, however, any gains would be outweighed by the likely effort of learning a new tool and converting existing content. Especially since Articulate 360 can facilitate teamwork, improve the stakeholder review process, and provide light responsive authoring while you continue enjoying the familiarity and power of Storyline.

A Big-Picture Comparison of Articulate 360 & dominKnow | ONE

If you’re shopping around for an eLearning authoring tool that offers flexibility and collaborative tools, you may have found a few contenders.

Almost certainly, one is Articulate 360. Another is dominKnow | ONE. They both offer similar functionality, including:

      • A traditional (fixed-pixel) eLearning authoring tool
      • A responsive eLearning authoring tool
      • Software simulation or lesson authoring
      • In-context feedback tools with an unlimited number of reviewer
      • Collaboration features
      • Administration features

At first glance, they seem to be equivalent toolboxes. Scratch the surface, though, and you’ll find a number of significant differences. In particular, they’re differences that will matter for large eLearning development operations.

Articulate 360 dominKnow | ONE
Feature Richness X
Capable of Advanced Customization X
Flexible Options & Configurations X
Supports Multiple Skill Levels X X
Good for Beginners
Good for Advanced X
Platform Cloud Cloud Cloud Cloud
Compatible w/Major Operating Systems Windows only
Easily Switch Devices X
Latest File/Version Available to Everyone X
Collaboration NA
Real-Time Co-Authoring
Asynchronous Co-Authoring
Easy to Gather Feedback
Can Address FB From Authoring Tool X
Strong Administrative Control X
Admin Controls Users & Permissions
Admin Manages Shared Assets
Admin Controls User Access to Files only if admin is project owner
Admin Sees All Team Projects only if shared with admin
Admin Can Monitor Progress X
Admin Can Generate Activity Reports X
Built-In Development Cycle Tracking X

Feature Richness in Articulate 360 vs dominKnow | ONE

dominKnow | ONE and Articulate 360 each have two main authoring tools: a traditional slideshow-style tool optimized for desktop learning and a responsive authoring tool that produces content optimized for all screen sizes.

Articulate 360’s traditional tool is Storyline and their responsive tool is Rise. dominKnow | ONE’s traditional tool is called Claro and the responsive tool is called Flow.

Storyline is an authoring powerhouse – there’s a reason it’s an industry favorite. It’s very sophisticated in the right hands, and many eLearning developers have spent years honing their expertise in the tool. This alone makes Articulate 360 the clear choice for some.

Articulate’s responsive authoring tool is much more limited in features and capability. Rise’s functionality continues to expand, but at the moment, there are still serious constraints that restrict both creativity and interactivity. Authors must work within a widget-style UI with no opportunity to step outside their built-in options.

Taking the tools together, project developers using Articulate 360 have to choose between control over the learner experience and responsive design. They can’t have both.

This is a significant problem, given the widespread adoption of mobile use today. To meet learners where they are, organizations should be prioritizing a fully responsive or mobile-first format.

dominKnow | ONE offers fully-featured tools for both traditional and responsive eLearning. Claro and Flow have almost the exact same capabilities, and this allows authors the freedom to choose the right design strategy for a project.

When it comes to responsive authoring, dominKnow’s Flow will feel far more robust and sophisticated than Articulate’s Rise: more project theme choices, more responsive block layouts, more advanced interactions, and broader configuration capabilities.

In the case of traditional authoring, Storyline loyalists acclimating to Claro will probably miss certain bells and whistles they’ve grown used to. However, dominKnow | ONE’s fixed pixel tool provides a significant amount of flexibility for customization and advanced design. The “how” of bringing ideas to life may differ, but the ability to do so is similar in most cases.

Skill Level Requirements for Articulate 360 vs dominKnow | ONE

The differences in Articulate 360’s authoring options also have a serious impact on the skill levels they can support.

Articulate’s fixed-pixel tool is best suited to experienced users. Storyline can have a difficult learning curve for beginners. Rise, in the meantime, is easy to tackle for newbies but disappointingly limited for power users. There’s little flexibility for novel design or interactivity.

To make things more complicated, Storyline and Rise have totally different interfaces – the UIs bear little resemblance even though they’re bundled together.

There are plenty of projects and teams where these quirks won’t matter. For plenty of others, Articulate 360 will still be workable.

However, some organizations could face fewer challenges with dominKnow | ONE. This is especially true for tiered teams and organizations with new but growing authors.

The power and UI of dominKnow | ONE’s two authoring options are the same, so authors of different skill aren’t automatically locked into one or the other. In fact, Claro and Flow are both designed to accommodate multiple skill levels. Highly configurable native widgets even make it possible to author some impressive content with little experience, but the tools are powerful and flexible enough to satisfy the demands of advanced developers.

One of the coolest features in dominKnow | ONE is the adaptive interface feature. You can choose from three options that match a user’s UI and permissions to their skills and needs. You can keep first-time developers out of trouble while giving your stars free reign, and the interface settings can change as an author grows in capability.

Fully Cloud-Based dominKnow | ONE vs Partially Desktop-Based Articulate 360

Stepping outside the authoring interfaces, Articulate 360 and dominKnow | ONE offer avenues for teamwork and collaboration. Many of these features hinge directly on cloud technology.

dominKnow | ONE is entirely cloud-based, meaning it’s accessed exclusively through a browser. The only piece you need to download is a lightweight software simulation tool so you can record within other applications. All content created within that tool is stored right back in the cloud.

Being cloud-based creates unique value for organizations.

      • Users and licenses aren’t tied to any one device
      • Assets and project files are always backed up
      • Everyone is automatically on the same “latest version” of a file
      • Software updates happen in the background
      • All users experience the exact same interface regardless of operating system, browser, or device
      • Certain IT costs are offloaded onto the software provider
      • Organizations gain greater control over content management, file access, and oversight
      • Real-time collaboration is possible from anywhere and asynchronous collaboration is simpler

Articulate 360’s apps are also largely cloud-based, but there’s one big exception: Storyline. It’s still a desktop-only program. The 360 version of Storyline connect to the cloud for stock media access, as well as filing sharing with an additional subscription. Otherwise, it’s a desktop tool.

Since Storyline is the main driver of production in Articulate 360, its desktop functionality means the benefits of the cloud are patchy or missing for the product suite as a whole.

Storyline software isn’t permanently tied to a device, but switching devices requires the installation of bulky authoring software and the transfer of project files.

Speaking of project files, the latest version of an active Storyline project will always be on somebody’s hard drive. Articulate warns users that editing a Storyline file from cloud-based storage puts you at risk of file corruption. Authors can back up or transfer project files through cloud storage, but this requires additional steps by forgetful humans. Only the primary author will have reliable and always up-to-date access to critical project files.

The fact that Storyline is desktop only also has consequences for collaboration in Articulate 360.

Co-Authoring and Collaboration in Articulate 360 vs dominKnow | ONE

Articulate 360 supports shared content and collaboration when you add a Teams subscription.

Teams allows collaborators to share custom assets and content for both authoring modes, in separate pools. Either way, you’re creating a duplicate of the original. Edits will only affect the copy you’re changing.

With Teams, Articulate 360 supports real-time co-authoring for responsive projects. This allows multiple contributors to work on different lessons in the same project at the same time. It’s possible in Rise because the software is cloud-based.

in Storyline, real-time collaboration of this nature is impossible because it’s a desktop tool. Asynchronous co-authoring can be managed by passing files through the Teams library, but for reasons we explained above, the process is cumbersome and error-prone. Without careful communication between co-authors, version mix-ups and redundant work can happen.

dominKnow | ONE supports real-time co-authoring in both Claro and Flow, with various features to help contributors work smoothly together. Content and assets can be reused in multiple projects in either authoring mode, and reused content is “smart.” Edits can be applied to all projects automatically, and it’s easy to see how many times an object is reused and where.

dominKnow | ONE and Articulate 360 each address one more collaboration problem: stakeholder review. Their solutions are very similar. Both allow you to invite an unlimited number of reviewers to view a project in the cloud and leave in-context feedback. Reviewers can interact with others’ comments and authors can get clarification or mark the thread resolved.

There are a few differences stemming from the fact that the review workflow is a native feature of the authoring tools in dominKnow | ONE and a separate application in Articulate 360. The consequence is that dominKnow | ONE’s review workflow provides a more streamlined experience for authors making edits. However, this will really only matter for organizations with a large volume of comments and edits.

Administrative Controls in Articulate 360 vs dominKnow | ONE

Organizations get administrative control over users with both dominKnow | ONE and Articulate 360 with Teams. Admins can add or remove users, reassign seats, manage groups of users, and so on. In both cases, admins can also organize and manage shared content or assets.

Administrative control over project files is where things really diverge.

In dominKnow | ONE, you have a lot of administrative control over projects. Administrators themselves can see and access all projects, regardless of who created the project or whether they’ve been invited. Admins can change users’ access to a project and even do so via mass action.

Many of the issues we’ve already discussed make administration of project files complicated in Articulate 360. There’s no built-in mechanisms at all for administrative control over Storyline projects, since the files are on authors’ hard drives. For Rise projects, access will be controlled by the project’s owner. This could be an admin, but if it’s a non-admin user, access is out of an administrator’s hands. They’ll only gain control when the project owner gets removed from the team.

dominKnow | ONE also provides admins with management tools that don’t have an equivalent in Articulate 360 Teams. For example, admins in dominKnow | ONE can see who’s done what, monitor progress, generate reports on productivity or asset use, and track the development process against custom life cycles.


dominKnow | ONE and Articulate 360 look like very similar product suites based on the types of functionality they offer. The differences between the two end up having a big impact on who will benefit from each.

Articulate 360 offers the powerhouse that is Storyline, a light responsive authoring tool, a solid feedback-gathering application, and collaboration with Teams. It’s a great package for freelancers and small teams who want to use Storyline but need a few ways to make clients’ and teammates’ lives a bit easier.

Bigger teams will feel the pinch of Articulate 360’s limits, and that’s where dominKnow | ONE comes in. It can empower authors on large, tiered teams to smoothly collaborate and make the most of their resources, and it will also provide management with the robust control over files, users, and productivity that organizations need at scale.

6 Key Things to Consider as Universities Plan to Go Online

Universities across the globe are seeing a huge drop in number of students enrolling for campus education. They are also facing a higher drop-out ratio due to student inability to pay fees in wake of COVID- 19. It is being predicted that many universities and higher-ed institutes may have a sustenance challenge in the coming months if they do not act fast. Mid-tier and small universities, which always had a campus curriculum, are suddenly under a pressure to completely go online.

Going online does not only pertain to delivering classes online using zoom or WebEx; but instead, a complete digital transformation of academic operations and delivery. It affects everyone in the university. And such a transformation can take years to be successful. But do universities have that amount of time in hand? The obvious answer is NO. Then how can a university get this done right rapidly?

Here are few short-term solutions that a university can consider while going online:

1) Use Google Meet or Zoom to take online classes.

2) Use default Moodle with minimum customization to host all your online class details. It does not take more than a couple of weeks to get this up and running.

3) Add some engagement in your online sessions through interactive games, quizzes, exercises, and more.

4) Use a simple nudge system like short emails with key points, concepts, and definitions to reinforce learning content

5) Offer a few free online sessions to attract new registrations to your classes

6) Try and create some marketing collateral such as student success testimonials, parent experiences, and more to promote on social media and university website. Marketing it right would help you get more online registrations to classes and eventually sustain the university.

To get this all streamlined and implemented rapidly, perhaps the most appropriate thing would be to interact with a consulting company which has been into the online learning industry for a considerable period of time and has enough experience in the following fields:

– Technology selection

– Systems to go online

– Tools for teachers, students, administrative, and support functions

– Content development expertise to convert Instructor-Led Training (ILT) to online-friendly sessions

– Rapid yet effective innovative solutions to reduce dropout

– Student engagement solutions for pre- and post-class

Once your short-term system is set, then you can start planning the long term. Do ensure you consider all aspects stated above.

What are some interesting solutions you have used in your university which can be shared with other fellow educators? Do share your thoughts in the comments below.

eLearning Conversations – A Passive Way to Learn

A dialog between two characters to present a scenario for learners – Does this sound familiar? All of us who have been associated with eLearning development, mostly have developed such samples showcasing conversations and scenarios.

There was a time when such conversations were considered an engaging way to learn. To make it more effective, voice-overs were added. But, let us step-back for a moment and think if it is an engaging and active mode of learning? Isn’t it a pretty passive way where the learner is simply watching the screen and is only following what is being displayed? The question that arises then is, if such conversations or scenarios are not very effective, then how do we solve this problem? One possible solution that I can think of is to have the learner interact with the system as part of the scenario. And based on how the learner interacts, the system can respond to the learner and take the conversation ahead. With advancement in technology, chatbots could be used as an important element of this.

Chatbots are a great way to engage learners in a conversation and experience the scenario unfold. To explain it better, imagine a conversation between a doctor and a patient on the symptoms to observe for a disease. The doctor needs to recommend the right medication. To train a doctor well on this scenario, we could have the doctor (learner) converse with a bot which acts as a patient. The bot would respond to the doctor’s examination questions. This would help the doctor to know the right set of questions and gather as much information as possible before getting into the actual scenario. This bot could even be voice-enabled which will allow the learner to talk to the bot.

And how do we take this to an eLearning course? Well, in an eLearning course, a bot can be embedded instead of the conversation slides. And when it comes to questions or assessments based on the scenario, the course can continue like usual. Such chatbots can be created using variety of technologies such as Google DialogFlow, Microsoft Q&A Maker, and Amazon Lex.

Chatbot in eLearning

Interested in seeing a demo? Feel free to reach out to us at




Micro-Learning: The Interactive Way

What is the first word that comes to your mind when you hear the word ‘micro-learning’? More than 90% people would respond, “videos”. Over a period, videos have become synonymous with micro-learning. Interesting videos with the right story-line, engaging graphics, and optimal speed, can be a great micro-learning aid. Even though videos come with a lot of benefits, they are really hard to maintain or update in-line with changing content. In that case, is there a different approach we can look at for developing micro-learning?

Personally, I learn really well through Frequently Asked Questions (FAQs). Short questions and precise answers can make learning really effective. Owing to rapid technology advancement, we can now create chatbots to consume nuggets of information in question and answer format. A learner can ask a question and get a quick short answer at the point-of-need. It not only acts as a short learning nugget, but also an interesting way to engage learners. Not only can these bots answer queries, but also log analytics of the questions being asked and questions which remain answered. Bots can also be updated easily for frequently changing content and changes can be displayed to learners immediately. These bots can be created using a variety of technologies such as Microsoft Q&A maker, Google Dialogflow, and Amazon Lex.

Have you tried creating micro-learning using chatbots? How has your experience been?

Interested in seeing a demo of FAQ bots? Reach out to us at