Skip to main content

🎓 Lesson 21: Collaborate & Review

Real courses are rarely built alone. Subject-matter experts want to weigh in, stakeholders want to sign off, and sometimes the whole thing needs to exist in five languages. This lesson covers the collaboration toolkit: Review 360 for on-slide feedback, shared team folders, translation with XLIFF, and the unglamorous version hygiene that keeps a project from becoming a graveyard of final_FINAL_v2 files.

📚 What You'll Learn

By the end of this lesson, you will be able to:

  • Run a Review 360 feedback loop: publish a link, collect on-slide comments, and resolve them
  • Understand shared team folders and collaboration roles Teams
  • Localize a course by exporting XLIFF or Word, translating, and re-importing
  • Apply sane version management to your .story files and projects

⏱️ Estimated Time: 40 minutes

🎯 Project: Publish a course to Review 360, leave and resolve a comment, and sketch your version-naming scheme.

In This Lesson

💬 Review 360: Feedback on the Slide

Every course author has lived the nightmare: you email a draft, and back comes a spreadsheet that says "on the slide with the blue button, the third bullet is wrong… I think? Maybe slide 8?" Review 360 exists to end that. It's the supporting app you met in Lesson 1, and here's how it works in practice.

From Storyline or Rise, you publish to Review 360. That produces a private shareable link. Anyone with the link — SMEs, your boss, legal — opens the course in their browser (no Articulate account needed to comment) and leaves comments right on the slide or block they're looking at. Every comment is pinned to the exact spot, so there's no more "which slide again?"

As the author, you read the comments in Review 360, reply to ask questions, and resolve each one as you address it — a tidy checklist that melts away as you fix things. Review 360 also keeps version history: publish an updated draft to the same item, and reviewers see the new version while the comment thread continues.

graph LR A["📤 Publish to
Review 360"] --> B["🔗 Shareable link"] B --> C["💬 Reviewers comment
on the slide"] C --> D["✏️ Author revises
& resolves comments"] D --> E["🔁 Republish
new version"] E --> C style A fill:#fed7aa,color:#1e293b style B fill:#bfdbfe,color:#1e293b style C fill:#fde68a,color:#1e293b style D fill:#bbf7d0,color:#1e293b style E fill:#c7d2fe,color:#1e293b

Figure 1 — The Review 360 loop: publish, gather on-slide comments, revise and resolve, republish, repeat.

🧠 Mindset

Feedback can feel personal — someone's poking holes in the thing you built. Reframe it: every comment is a free bug report from someone who wants your course to succeed. The best authors invite critique early and often, because it's far cheaper to fix a wrong fact in Review than after 500 learners have seen it. A resolved comment is a small win, not a wound.

Figure 2 — A Review 360 comment thread (a simplified mock-up, not a real screenshot): comments pinned to a slide, with resolve status.

👥 Team Collaboration & Folders

Review 360 handles feedback, but what about multiple authors building together? That's where the team plan comes in Teams. On team/organization plans, Articulate adds shared spaces so a group isn't juggling files over email.

  • Shared team folders — a central place for the team's Rise courses and Storyline files, so the right people can find and open the current version.
  • Roles & permissions — control who can view, edit, or manage content.
  • Team slides / shared assets — reusable templates and slides the whole team can pull from for consistency.

Now, an honest note on co-editing: Rise courses are cloud-based and lend themselves to collaborative editing, while Storyline works on desktop .story files, so simultaneous "two cursors on one slide" editing isn't how Storyline is designed to work. Exact team capabilities evolve, so check Articulate's current features for your plan rather than assuming — the shape to remember is "Teams unlocks shared folders and roles; Rise is more naturally collaborative than desktop Storyline."

💡 Solo learners, don't worry: Everything in this course works on a solo trial. Team folders and roles are organization-plan conveniences — nice when you're on a team, entirely optional for learning and for building your capstone alone.

🌍 Translation & Localization

Need your course in Spanish, or in twelve languages? You do not rebuild it from scratch. Storyline and Rise both support a translation export/import workflow that keeps your design intact and swaps only the words.

In Storyline, you export the text to either a Word document (easy for a human translator to type into) or an XLIFF file — the standard format professional translation tools and services understand. A translator works on that file, and you re-import it. Storyline drops the translated text back into the exact same objects, layers, and slides. Rise offers its own translation export as well, so localizing a Rise course follows the same "export → translate → import" idea.

✅ Why export/import beats retyping

  • Design survives. Your layout, triggers, and timing stay put — only the text changes.
  • Translators use their own tools. XLIFF plugs into professional translation memory and services.
  • Round-trips are safe. Export, translate, re-import — repeat per language from one source project.
  • Fewer errors. No copy-pasting into hundreds of text boxes by hand.

⚠️ Budget for expansion and review

Translated text often runs longer than English (German and Finnish are notorious), so re-check your layouts after import — buttons and boxes can overflow. And always have a native speaker review the result in-context; a translation that's technically correct can still read awkwardly on a slide.

🗂️ Version Management & File Hygiene

The least glamorous skill in this lesson may save you the most grief. Storyline projects are .story files on your computer, and it's terrifyingly easy to end up with course_final.story, course_final_v2.story, and course_FINAL_actually.story — and no idea which one is real.

  • Name with intent. Use a consistent scheme with a version or date: fire-safety-v3-2026-09-15.story. Increment the version on meaningful changes.
  • Back up your source files. The published output isn't editable — the .story file (or the Rise project) is your only master. Keep copies somewhere safe.
  • Don't rely on the cloud alone. Team folders and Review are great, but keep your own backup of source files; sync services can conflict, and a published/Review copy is not an editable source.
  • Work locally, then save up. For Storyline, editing a .story file straight off a network or sync folder invites corruption — work on a local copy and copy it back.

None of this is exciting, and all of it is the difference between a calm revision and a panicked "I think I lost the good version" afternoon.

🎯 Try It: Run a Review Loop

🏋️ Activity: Publish to Review 360 and close a comment

Objective: Experience the feedback loop from both sides — reviewer and author — and set up your version scheme.

Tool note: Review 360 publishing works from Rise (any browser) or Storyline Windows only on the trial Trial / Paid. Team folders are an organization-plan feature Teams — if you're solo, just read that part and do the rest.

Steps

  1. Open any course and choose Publish → Review 360. Copy the shareable link. (⏱️ 5 min)
  2. Open the link in your browser (pretend you're the SME) and leave a comment on a specific slide — e.g. "This heading should be bolder." (⏱️ 4 min)
  3. Back in Review 360 as the author, read the comment and reply to it. (⏱️ 3 min)
  4. Make the change in your project, republish to the same Review item, and resolve the comment. (⏱️ 6 min)
  5. Write down a version-naming scheme you'll use (project name + version + date) and rename your working file to match. (⏱️ 4 min)
  6. (Optional) Export your course's text to Word or XLIFF to see how the translation workflow looks — no need to actually translate. (⏱️ 5 min)
💡 Hint

If republishing seems to create a new Review item instead of updating the old one, make sure you're publishing to the existing item (Review remembers it) rather than starting fresh — otherwise your comment thread and version history split across two items.

✅ Activity Complete When…

  • You've published a course to Review 360 and have a shareable link
  • You left a comment as a reviewer and replied to it as the author
  • You republished and resolved the comment
  • You have a written version-naming scheme and a renamed source file

🎯 Quick Quiz

Question 1: What is the main benefit of Review 360 over emailing a draft?

Question 2: To localize a Storyline course into another language, you should…

📓 Learning Journal

Keep building your Learning Journal — it's where "I read that" becomes "I can do that." After this lesson, jot down:

  • Key concepts you learned
  • Things that clicked for you
  • Questions or confusion points to revisit
  • Ideas you want to try
  • Your progress and how you feel about learning this

✍️ This lesson's prompt: Who would you want to review your capstone course — a real SME, a colleague, a friend? Write down two people (or roles) and one specific question you'd ask each in Review 360. Then write the exact file-naming scheme you'll commit to for your project.

📝 Lesson Summary

🎓 Key Takeaways

  • Review 360 turns feedback into a tidy loop: publish a shareable link, reviewers comment on the slide, the author replies and resolves, with version history along the way.
  • The team plan adds shared folders, roles, and team slides Teams; Rise is more naturally collaborative than desktop Storyline (check current capabilities).
  • Localize by exporting XLIFF or Word, translating externally, and re-importing — your design survives, only the words change.
  • Version hygiene matters: name with intent, back up source files, don't rely on the cloud alone, and work on local copies of .story files.

🎉 What You've Accomplished

You've moved from "lone author" to "collaborator." You can run a professional feedback loop, understand how teams share work, localize a course without rebuilding it, and manage your files so nothing gets lost. These are the workflow skills that make you trustworthy on a real L&D team.

❓ Common Questions at This Stage

Do reviewers need an Articulate account to comment in Review 360?

Generally no — reviewers open your shareable link and comment in the browser. That low friction is the whole point; you can send the link to an SME or manager who's never touched Articulate.

Can two people edit the same Storyline file at once?

Storyline works on desktop .story files, so it isn't built for simultaneous co-editing the way a cloud doc is. Teams share via folders and hand off files; Rise, being cloud-based, is more naturally collaborative. Exact capabilities change, so check Articulate's current docs for your plan.

Is XLIFF or Word better for translation?

Use XLIFF when a professional translator or translation service is involved — it plugs into their tools and translation memory. Use Word for a quick, human-typed translation when you don't need that machinery. Both re-import the same way.

🔭 Looking Ahead

There's one more modern topic to cover honestly before the capstone: AI. In Lesson 22, we look at Articulate's AI Assistant clear-eyed — what it genuinely does, what it honestly costs, and the responsible workflow that keeps a human (and an SME) in charge.

✅ Before the Next Lesson

  • Run a full Review 360 loop and resolve at least one comment
  • Write this lesson's journal entry — your reviewers and your file-naming scheme
  • Adopt your version-naming scheme on your capstone project files now

📚 Additional Resources

🌟 Encouragement for the Journey

The authors people love to work with aren't the ones who never get feedback — they're the ones who make feedback easy, act on it gracefully, and never lose the file. You just learned to be that person. Your future teammates thank you.