Duration

4 months

Platforms

Desktop application

Role

UX designer

ADOBE CAPTIVATE

Adobe Captivate is an authoring tool that is used for creating eLearning content such as software demonstrations, software simulations, branched scenarios, and randomised quizzes in Small Web Formats and HTML5 formats.

It can also convert Adobe Captivate-generated file formats (.swf) to digital MP4 (.mp4) formats which can be played with media players or uploaded to video hosting websites. For software simulations, Captivate can use left or right mouse clicks, key presses and rollover images.

Adobe Captivate is an authoring tool that is used for creating eLearning content such as software demonstrations, software simulations, branched scenarios, and randomised quizzes in Small Web Formats and HTML5 formats.

It can also convert Adobe Captivate-generated file formats (.swf) to digital MP4 (.mp4) formats which can be played with media players or uploaded to video hosting websites. For software simulations, Captivate can use left or right mouse clicks, key presses and rollover images.

Dismantle Captivate

Captivate 9 was dismantled and mapped down to the smallest feature to create the existing workflows in the software. It helped us get a clearer picture of the product and all the features that are hidden in the small corners of the product.

Captivate 9 was dismantled and mapped down to the smallest feature to create the existing workflows in the software. It helped us get a clearer picture of the product and all the features that are hidden in the small corners of the product.

USER CONTEXT

We then started creating a bird’s eye view of the workflow that is being used majorly in the product.

We then started creating a bird’s eye view of the workflow that is being used majorly in the product.

RESEARCH

Our primary research was conducted with our extensive users and evangelists over a video call. They having the knowledge of how the product is used and how it is been seen by other people and gave us a more open view on the product, the needs and changes that would make it faster and intuitive to use.

Our secondary research was done online where we looked over different blogs, forums and review threads. We collected all the reviews and tried to evaluate that with the software.

Our primary research was conducted with our extensive users and evangelists over a video call. They having the knowledge of how the product is used and how it is been seen by other people and gave us a more open view on the product, the needs and changes that would make it faster and intuitive to use.

Our secondary research was done online where we looked over different blogs, forums and review threads. We collected all the reviews and tried to evaluate that with the software.

INSIGHTS

INSIGHTS

Their profession and how the product is being used in their profession

  • A need to have cloud library to create seamless communication between the client and the user for sharing content, preview and view of the course.

  • A planning section for the course where they use other tools now to plan a course, but integration in captivate will help them work faster.

  • Simplify the product and make it more intuitive for the user to move around the software confidently

  • Providing a mobile experience for the end users.

Their profession and how the product is being used in their profession

  • A need to have cloud library to create seamless communication between the client and the user for sharing content, preview and view of the course.

  • A planning section for the course where they use other tools now to plan a course, but integration in captivate will help them work faster.

  • Simplify the product and make it more intuitive for the user to move around the software confidently

  • Providing a mobile experience for the end users.

USER & SCENARIOS

We detailed out the user persons and different scenarios they would be in. The personas was a cumulation of the problems the users had and a peek at the solutions that could be.

We detailed out the user persons and different scenarios they would be in. The personas was a cumulation of the problems the users had and a peek at the solutions that could be.

PILLARS OF THE PRODUCT

A white board discussion was a phase done to club down the features, improvise them for the new version, and add new features creating the main pillars for the product.

These pillars were a representation of the process of creating a course, the tools and the needs in the software. They were divided into four pillars consisting of all the features that can be added or modified in the tool.

A white board discussion was a phase done to club down the features, improvise them for the new version, and add new features creating the main pillars for the product.

These pillars were a representation of the process of creating a course, the tools and the needs in the software. They were divided into four pillars consisting of all the features that can be added or modified in the tool.

COURSE PLANNING

Structure : Templates, Subject specific, Top help authors pedagogy
Storyboarding : Script, content sync, Layout, Drawing, Prototype, Mind map, Keyword-centric

CAPTIVATE CLOUD

Libraries : Templates, Assets, Content, Toolkits, APIs
Collaboration : Client, co-author, Other Adobe products, other products(ever note, etc).

COURSE CREATION

Tools: Knowledge, Assess, Content creation, Sync code
Approach : Workspace levels, Consistent workflow patterns, Assisting authors to save time, Optimise content, Template+custom

COURSE CONSUMPTION

Learning : Method, format, Navigation, Keyboard search, Recap, Proficiency.
Community : Leaderboard, Progress, peer-to-peer and teacher interaction, Note-keeping

CONCEPT CREATION

The features were assessed for similarity and patterns of use. They were highlighted as the features used horizontally across all the workflow in authoring tool.

We broke down a generic authoring workflow from receiving content from client to the course being consumed by a learner. This breakdown involved the process of course creation for third party or for themselves. We started creating the concepts for the features and highlighting the parts that were covered in the workflow for the concept.

CONCEPT CREATION

The features were assessed for similarity and patterns of use. They were highlighted as the features used horizontally across all the workflow in authoring tool.

We broke down a generic authoring workflow from receiving content from client to the course being consumed by a learner. This breakdown involved the process of course creation for third party or for themselves. We started creating the concepts for the features and highlighting the parts that were covered in the workflow for the concept.

The features were assessed for similarity and patterns of use. They were highlighted as the features used horizontally across all the workflow in authoring tool.

We broke down a generic authoring workflow from receiving content from client to the course being consumed by a learner. This breakdown involved the process of course creation for third party or for themselves. We started creating the concepts for the features and highlighting the parts that were covered in the workflow for the concept.