When an employee is missing a behavioral or performance mark, it’s not uncommon for orgs to assume that an e-learning course is a surefire way to address the problem. And if you’re not in a posi...
Published 7 years ago
Version 1.0
Blog Post
Hi all:
I cannot share links externally, because these are core documents for my organization, but I have built the following two items using RISE.
1. STANDARD OPERATING PROCEDURES DOCUMENT:
Rise's speed, ability to embed media (labeled graphics screenshot), accordions- I am able to keep documentation on a complex systems integration spanning 3 systems maintained quickly.
A huge bonus is publishing to Review. When a team member (like our Product Support reps) have a question, they can post a comment that draws my attention immediately to the section in question. Let's say in a case where there was an adaptation to the system and the documentation no longer represents what is needed to support our clients. I can quickly get focused on the area of need, update and improve the experience for everyone.
2. USER TESTING SCRIPTS
Testing is hard. Although scripts are common (same fields to access or buttons to push), there are actions taken on each step which can vary per test case. Rise allowed me to create a basic starting test case, and quickly generate variants where needed.
By linking to specific test cases that are common (i.e. login), I could reuse assets common to all testers, but then branch to unique steps where necessary with ease instead of creating multiple copies of test scripts for redundant tasks.
I cannot share links externally, because these are core documents for my organization, but I have built the following two items using RISE.
1. STANDARD OPERATING PROCEDURES DOCUMENT:
Rise's speed, ability to embed media (labeled graphics screenshot), accordions- I am able to keep documentation on a complex systems integration spanning 3 systems maintained quickly.
A huge bonus is publishing to Review. When a team member (like our Product Support reps) have a question, they can post a comment that draws my attention immediately to the section in question. Let's say in a case where there was an adaptation to the system and the documentation no longer represents what is needed to support our clients. I can quickly get focused on the area of need, update and improve the experience for everyone.
2. USER TESTING SCRIPTS
Testing is hard. Although scripts are common (same fields to access or buttons to push), there are actions taken on each step which can vary per test case. Rise allowed me to create a basic starting test case, and quickly generate variants where needed.
By linking to specific test cases that are common (i.e. login), I could reuse assets common to all testers, but then branch to unique steps where necessary with ease instead of creating multiple copies of test scripts for redundant tasks.
Hi David - I'd LOVE to use Rise, but I work on content that cannot leave my organization's firewall. Sounds like you might have the same scenario yet you've found a way to use Rise. I'd love to learn more! Can you share how you've set up Rise to keep your content safe and internal? Thanks!
- Would love to know this as well
