New features go unused
A release adds a better way to do the job. People keep the old way, because nobody showed them the new one.
The cost: The work behind the feature does not pay back.
Release readiness
Your product ships every week. Your team keeps up.
Every release moves a button, adds a field or changes a flow. GuidedRole versions your training with your product, lets you give the new lessons to each role a change affects, and shows you who has passed them.
Courses updated by FasterApps · Practice on your test site · Works in Chrome
Course releasesCustomer portal
- v0.5.0DraftMade available by FasterApps · 16 OctValidated on the test site · no warnings · Not assigned until published
- v0.4.0PublishedPublished by Hannah Ortiz · 30 SepValidated on the test site · no warnings · Used by 24 learners
- v0.3.1RetiredPublished 12 Sep · retired 30 Sep by Hannah OrtizValidated on the test site · Results are kept
Content healthv0.4.0
- 3.1 Create an invoiceHealthy
- 3.2 Send a payment reminderNeeds review
send-reminderNot found 5 / 9 - 3.3 Refund an orderHealthy
FoundFound by a fallbackAmbiguous or not found
The Send button moved into the Actions menu in the last app release. Lesson 3.2 needs review.
When training falls behind
What fast releases do to an untrained team.
Every release changes what people need to know. When the training does not change with it, the cost turns up all over the company.
Support questions spike after a release
Customers ask about the change before the people answering them have seen it. Agents guess, escalate or promise to come back.
The cost: Longer queues and uneven answers while everyone catches up.
Sales and marketing describe the old product
Demos, decks and launch posts show last month’s screens, or leave out what is new.
The cost: Prospects notice the gap between the pitch and the product.
Written guides fall behind
Help articles and internal wikis are updated last, if at all, and nobody can tell which page is current.
The cost: People stop trusting the documentation and ask a colleague instead.
Old training points at screens that moved
Videos and walkthroughs show a button where it used to be. Learners follow them and get stuck.
The cost: The training teaches the wrong thing, and someone has to undo it.
The course changes with the product.
With GuidedRole, your course gets releases of its own: updated from your code by FasterApps, assigned to the roles that need them and checked with an assessment.
See the release cycleThe release cycle
From code change to trained team.
Here is what happens between a product release and a team that can use it, and who does each part. Select a stage to read how it works.
Your app changes
Done by Your developersA release moves a button, adds a field or changes a flow.
Step 1: Lessons updated
Done by FasterAppsAn AI coding agent reads the change and rewrites the lessons it affects.
Step 2: Release published
Done by Your adminIt arrives as a draft. Publishing it retires the previous release.
Step 3: Lessons assigned
Done by Your admin and GuidedRoleA path with the new lessons reaches each training role, with a due date.
Then your product ships its next release, and the cycle starts again.
How it works
How GuidedRole keeps every role current.
Five steps, repeated with every release, from the change in your code to an assessment that shows people can use it.
Step 1: Lessons are updated from the code change.
FasterApps builds and updates your course. An AI coding agent reads your application’s source code, read-only, to find what a release changed. It rewrites the affected steps, hints and assessment criteria in the words your screens use.
- Validated automatically before anything is imported.
- Tried on your test site with the extension.
- Delivered as a draft release, never straight to learners.
- Nothing for your team to record or rewrite.
Lesson updatev0.4.0 → v0.5.0
3.2Send a payment reminder
Found in the source codeThe Send button moved into the Actions menu.
Steps rewritten
- 4Removed: Select Send.
- 4Added: Open the Actions menu.
- 5Added: Choose Send.
- Automatic checks passed, no warnings
- Tried on the test site: every step completed
- Imported into your workspace as draft v0.5.0
Step 2: Your admin publishes the new course release.
Courses are versioned like software, with semantic versions such as 0.5.0. A workspace admin reviews the draft in Curriculum and publishes it, and the previous release is retired at the same moment.
New practice sessions and assessments use the new release. Attempts in progress keep the release they started on, and earlier results stay as they were graded.
Publish v0.5.0?
New practice sessions and attempts in Customer portal use v0.5.0. The published release v0.4.0 is retired.
Attempts in progress keep the release they started on, and earlier results stay as they were graded.
Support essentials is assigned to members with the training role support who have never held it.
Step 3: Give what changed to the roles it affects.
Paths hold the required and optional lessons for each training role, such as support or sales, with a due date. Give a release’s new lessons a path of their own, such as Launch: Payment links. Saving it assigns it to everyone with the training role, with a due date.
When a release is published, paths with a training-role rule also reach members with that role who have not held them before. Admins can also assign a path to any member, with a due date of its own.
Path · SupportSupport essentials
17required lessons2 optional
- Auto-assigned to training role support
- Due 21 days after assignment
- Learners
- 14
- Completed
- 5
- Overdue
- 1
Assigned pathDue 31 Oct
Support essentialsOn track
9 / 17 lessons passed- 2.3 Publish and update a pricePassed 91.6
- 2.4 Answer a customer requestIn progress
Step 4: Check that people can use the change.
Every lesson has an assessment with an outcome-only brief: no hints, no highlights and no Guided Mode. GuidedRole checks the result on the page, and can reopen the saved page in a background tab to confirm the work was saved or made public.
With the default scoring, a pass needs 80 points and every critical outcome. Results show each attempt with its accuracy, time and actions, and the overview shows who is on track, overdue or needs attention.
Assessment resultPassed
3.4Approve a refund
87.3/ 100 · pass line 80 · every critical outcome met
- Accuracy
- 59.5
- Time
- 18.6
- Actions
- 9.2
- 40 / 40C1 Refund approved for order SO-1187 (Met)CriticalVerified by reopening
- 25 / 25C2 Partial refund of $120.00 for the damaged item (Met)CriticalObserved on page 01:52
- 20 / 20C3 Reason recorded as Damaged in transit (Met)Observed on page 02:10
- 0 / 15C4 Order note added for the warehouse (Missed)Not observed on page at submission (3:05).
Step 5: Catch drift early.
GuidedRole records how it finds each target on the page, release by release. When a target keeps needing a fallback, matches more than once or goes missing, its lesson is flagged for review, beside its pass rate and median time against the reference, so it is fixed before more learners get stuck.
A fallback match is still exact, so scores stay valid while FasterApps updates the lesson. If a target stops resolving during an assessment, the attempt is interrupted as a content problem and is not counted against the learner.
Content healthNeeds review
3.2Send a payment reminder
1 target needs review on v0.4.0Send button
Of 9 lookups: found by a fallback strategy 2 times, not found 5 times.send-reminderNot found 5 / 9FoundFound by a fallbackAmbiguous or not found
- 30-day pass rate
- 3 / 8
- 30-day median time
- 4:05reference 2:45
Re-validate lesson 3.2 against the test site.A target needs review when, over at least three lookups, it matched more than once or was not found in 10% of them, or needed a fallback in 30%.
The same steps in the admin space
Results you can trust
Fair to learners while the product changes.
When the site fails or a target can no longer be found, the attempt is not counted against the learner. Every result keeps the release it was taken on.
Assessment 2.2Incomplete – technical
The site showed “Something went wrong” while saving. This attempt is not counted against you.
Technical issue opened for the admin
Site failures are not counted.
When the test site shows an error page or another technical signal, the attempt ends as “Incomplete – technical”. It is not counted against the learner, a retake is always available, and a technical issue opens for your admins.
Attempt historyMaya Fernandes
3.3Refund an order
- A38 Oct · v0.4.0Passed88.4Passed
- A26 Oct · v0.4.0Not countedIncomplete – technical
- A122 Sep · v0.3.1Below the pass mark74.0Not passed
Attempts stopped by a technical problem are never counted against you.
Attempts keep their release.
Each attempt is pinned to the release it was taken on, so results from an earlier release stay exactly as they were graded.
BenchmarkThis workspace
3.2Send a payment reminder
- Reference time
- from
2:30to 2:45 - Reference actions
- from
21to 22
Saved for this workspace, without a new release.
Benchmarks follow the product.
If a change makes a task take longer, admins adjust its time and action benchmarks for the workspace, without waiting for a new release.
Questions
Keeping training current: common questions.
Who updates the course when our product changes?
FasterApps builds and updates courses for its customers. An AI coding agent works from your application’s source code, read-only. Every update is validated automatically and tried on your test site before it reaches your workspace as a draft. There is no point-and-click course editor or recorder in this version.
Do we have to change our application?
No. Nothing is installed in your application. Learners use the GuidedRole extension in Chrome 142 or later on your test site, which an admin sets up under Applications.
What happens to results from an earlier release?
They stay as they were graded. Every attempt keeps the release it was taken on, and an attempt in progress when a new release is published finishes on its own release.
Does a new release use more of our plan?
Only if it adds modules. Plans count modules across the published releases of applications that are not archived: 10 on the trial and Startup, 20 on Business and 50 on Enterprise. Publishing a release replaces the previous release in that count. See Pricing for every limit.
Can people ask about a new feature while they practise?
On the Enterprise plan, Guided Mode answers questions during practice from the course’s knowledge articles and the current lesson and step, and points at the control it means on the page. It is never available during assessments, and admins can turn it off.
Can team leads follow progress without admin rights?
Yes. Give them the trainer role: trainers see learners, results and technical issues, and can close technical issues. They do not open step-by-step timelines or change paths, releases or settings. Owners and admins can open a recent attempt’s timeline when they coach someone; each opening is recorded in the audit log.
Make every release one each role is ready for.
Start a 14-day trial, or talk to FasterApps about building and updating a course for your application.
14-day free trial · No payment details · Works in Chrome