D-01: remove recurring session edit interstitial#11
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Removed the interstitial screen from the recurring single-day session edit flow.
Recurring session edits now move directly from the session summary to either the affected-bookings warning or the success screen. The success screen copy was simplified so it confirms the update without explaining the underlying split into a one-off session.
Why it changed
Round 1 research showed that the interstitial explaining that a session had been split from the repeating schedule was confusing and did not help users complete the task. Users mainly wanted confirmation that the individual session had been updated.
Traceability
Validation
Remaining uncertainty
This change has not been exercised through a full browser journey yet, so the main remaining uncertainty is whether the new summary to warning or success flow feels clear in use.
What to test next
Test whether users editing one day from a recurring session understand the outcome from the success screen and the availability view without needing an explanatory interstitial.
Closes #5