Forum Discussion
Week 1 Discussion
- Which editing tools (rewrite, shorten, change tone, etc.) did you find most valuable, and why?
One of the most valuable tools for me was the “shorten” editing feature. I often receive very text-heavy content from SMEs who genuinely believe the learner needs to know everything. While their intent is good, it can easily overwhelm the learner. Being able to quickly condense and streamline that content without losing the core message has been a game-changer. It helps me maintain instructional integrity while improving the learner experience.
I also found the image generation from text incredibly helpful. That said, I did run into a small challenge. When I used the word “cookie” in my prompt, the AI kept generating images of actual cookies instead of the concept I was aiming for (website tracking). I had to “massage” the wording several times, eventually replacing “cookie” with phrases like “browsing data,” “trackers,” or “website analytics” to get a more accurate visual.
Is there a more effective way to prompt AI when a word has both a literal and technical meaning?
- What challenges did you face when trying to get AI to produce the results you wanted?
When generating images within the course content itself, the AI performed beautifully. The images were appropriately sized and visually balanced. However, when I used AI to generate a cover image for my Rise microlearning course, the image appeared too large, and I couldn’t find a way to resize it within the platform.
I practiced this in a microlearning course I’m currently developing, and while the image quality was great, the sizing limitation made it less desirable for a cover. I’d love to know the best practice for resizing or adjusting AI-generated cover images in Rise.
Hi EmeraldBrown you raised a great point here about AI-generated cover images.
The most effective cover images are very wide, with a 1:3 aspect ratio. I also avoid using images with people, since the cropping can change significantly based on the learner’s browser size.
For cover images, I usually stick with the stock photos available in the content library!