Frame 1 of 5 · Orient
Orient
Open Workspace settings. You need administrator access for the next steps.
Tutorial Production
Build the teaching sequence before you build the video.
GuideThread turns product knowledge into a reviewable tutorial brief: who the learner is, what they need to complete, which screens matter, what the narration should explain, and how success is confirmed.
Tutorial storyboard
Frame 1 of 5
Frame 2 of 5 · Choose
Choose
Select the invitation policy that matches how your team grants access.
Frame 3 of 5 · Explain
Explain
The policy controls who can invite members; it does not change existing member roles.
Frame 4 of 5 · Confirm
Confirm
Save the policy and check for the confirmation message.
Frame 5 of 5 · Next step
Next step
Share the member guide with workspace owners before the policy takes effect.
Clicks are evidence. The learning objective is the story.
A product walkthrough should help a defined customer complete a real job. Name the starting state, prerequisite access, expected decision points, and the result the learner should recognize.
- Audience
- Who is learning: administrator, contributor, analyst, developer, or another defined role.
- Customer task
- The job the learner needs to complete.
- Starting state
- What must already be configured or available.
- Product version
- The release or interface state shown in the tutorial.
- Completion cue
- The message, status, or changed state that confirms success.
- Owner
- The person accountable for accuracy and future revision.
From source walkthrough to approved learning asset.
Each stage keeps the product evidence, learner decision, and next owner visible.
01 · Source review
Source review
Attach the approved release note, requirement, interface walkthrough, and known exception. Remove steps that are not part of the customer's task.
02 · Storyboard
Storyboard
Choose the screen moments that establish context, show the action, explain the decision, and confirm the result.
03 · Narration
Narration and written steps
Explain why each action matters. Use the same terminology the product uses and keep the written companion aligned with the video sequence.
04 · Review
Subject-matter review
Product confirms behavior. Support checks common exceptions. Customer education checks pacing, prerequisites, and learner clarity.
05 · Version
Approval and versioning
Record the approved product version, content owner, intended destination, and the earlier asset this version replaces.
Every frame has a teaching job.
Orient, choose, explain, confirm, then hand the learner to a clear next step.
Example workflow · neutral software interface
Keep the video and written guide on the same version.
Related assets stay physically attached to the same source record.
Primary asset
Tutorial video
Screen sequence, narration, captions, and completion cue.
Step-by-step guide
Scannable instructions using the same terminology and sequence.
Support excerpt
A short answer for the most common question within the workflow.
Release note link
The approved source that explains why the content changed.
Tutorial Production questions
What should the source package include?
Include the approved change description, product version, a complete walkthrough of the customer task, known exceptions, required access, and the owner who can resolve product questions.
Who should review a tutorial?
The review group depends on the topic. A practical minimum is the product or engineering owner for behavior, a customer-facing owner for exceptions, and a content owner for learner clarity.
Should every tutorial have a video and written guide?
Not every task needs both. The production brief should record the chosen format and why it fits the learner, destination, and maintenance burden.
How are updates handled?
The content owner compares a new release against the tutorial's source version, revises only the affected teaching steps, completes review, and records which earlier asset was superseded.
Start with one release
Give the next tutorial a source, owner, audience, and version before production begins.
Use the release intake template to identify what changed, who needs an explanation, which assets are affected, and what still needs review.