Limitations of the Rise Scenario Block for Building Branching Scenarios

When Articulate released the Scenario block, we were very excited to start using it.

As the features and functions of this block type were largely unknown to us, we decided to create a rapid prototype. We needed a proof of concept to validate that Rise could deliver what we needed without putting a lot of initial development resources into it.

The scenario we created for the prototype was very small but representative of what we hoped to achieve functionally.

We built the scenario and documented any functional deficiencies we found as we went along. We evaluated the result as a team, and as the scenario was far from what we required, we reworked the design to match the way Rise scenarios worked. Then we built two more variations and evaluated them.

No matter what we did, we could not fully implement our design despite making some uncomfortable compromises. The Rise scenario block lacked some very fundamental functionality and imposed limitations, many of which you have described.

Within the space of two days it became very clear that the Rise Scenario block did not meet our requirements. As we were unable to demonstrate a successful proof of concept to management, we decided not to use the Rise Scenario block at all.

Fortunately we were able to come to this determination at negligible cost to our organization. 

Many Rise users have created successful scenarios, but it's not the right tool for us.