The translation step between storyboard and Rise

Hi everyone, I wanted to share an idea and sanity-check something with this community.

 

One friction point I keep running into in Rise isn’t design or content creation, it’s the time it takes to "translate" an approved storyboard into a build that still makes instructional sense.

 

Not rewriting anything.

Not rethinking the learning.

Just deciding how each piece of an already-approved storyboard should actually live in Rise.

 

Which block type fits best?

What order supports the learning objectives?

What needs to be split, grouped, or signposted so the experience still works for learners?

 

That translation step is where I see a lot of hours disappear. It’s also where instructional intent can quietly drift, simply because there are so many small judgment calls to make along the way.

 

Lately I’ve been thinking about how that step could be faster and more consistent, without turning it into a push-button conversion or removing instructional judgment.

I’ve seen a few options popping up, but they don’t really consider the instructional angle, or the pros and cons of different Rise block types from a learning perspective.

I’m curious:

• How much time do you typically spend translating storyboards into Rise?
• Where do you feel the most drag or rework?
• What parts of that step feel most repetitive or manual?

 

I’m pressure-testing a concept around this (while keeping instructional intent intact) and would love to exchange perspectives with anyone who’s felt this friction too.

Thanks.