Refactor application flow based on user feedback

[kaljarv]

I rethought some parts now to address the issues uncovered by user feedback. I added a new section in Figma that displays different flows in the app depending on these three criteria:

1. Basic info: unfilled/filled
2. Opinions: unfilled/partially filled/completely filled
3. Answering locked

If you go the prototype view, you can also click through the 6 different flow. They're listed in the left-hand menu.

In general, these things are affected by the criteria above:

• The contents of the start page (i.e. 'Hello, Barnabas')
• Where you're routed when you save Basic Info
• Whether the questions intro page /questions or the /questions/summary page is shown
• Button texts
• Warnings
• Whether editable fields are locked
• Whether the logout modal warning is shown

The biggest design changes are:

• The /questions/done page is merged to the start page and has different states
• On /questions/[questionId] pages, we no longer show the Previous and Delete answer buttons, just a big button for saving the answer
  • The button either moves us to the next unanswered question, or back to the /question summary page if we arrived there by clicking an individual question's Edit button. In the latter case, it is also accompanied by a Cancel button
• The /questions intro page ('Enter your opinions') is only shown when the user has answered no opinion questions. If they have answered even one, the summary page is always shown instead
• If the user has unanswered questions, the /question summary page has a prominent button at the start that takes them through all of their unanswered questions
  • The summary page also has clearly marked buttons for editing already answered questions and answering unanswered ones. When clicking on these, only the target question is shown and the user returns to the summary page after saving or cancelling

Here's a breakdown of how the things above depend on the state criteria.

Abbreviations:

• BI = Basic info: unfilled / filled
• OP = Opinions: unfilled / part. filled / filled
• AL = Answering locked: false / true

Item	BI	OP	AL	Behaviour
Start page: title	X	X		Different if BI = filled & OP = filled
Start page: intro text	X	X		Different if BI = filled & OP = filled
Start page: action list	X	X	X	Items are enabled when the previous one is completed. First two texts change if BI/OP = filled from 'Enter/Tell…' to 'Edit…'. They change to 'View…' if AL = true. Badges show missing items.
Start page: main button	X	X	X	Always reflects the last available item in the action list
Basic info page: fields			X	Locked if AL = true
Basic info page: main button		X	X	If OP = unfilled: 'Save and Continue' and go to questions intro; Else if AL = true: 'Return'; Else: 'Save and Return' + 'Cancel' button
Questions intro page		X	X	Only shown if OP = unfilled & AL = false
Questions summary: Fill in missing answers block		X	X	Shown if OP != filled unfilled & AL = false
Questions summary: warnings		X	X	Shown if AL = true, extra warning if OP != filled
Questions summary: button texts		X	X	If AL = true: either 'View answer' on answered questions or a 'You didn't answer this question' text on unanswered
Single question: main button		(X)	X	If AL = true: 'Return'; Else if arriving from questions intro or via the 'Fill Missing Answers' button from questions summary: 'Save and Continue' to next unanswered question or start page if no unanswered are left; Else (i.e. coming via an individual question's button on questions summary): 'Save and Return' + 'Cancel' button

[kaljarv]

Everything seems to be exactly how it's supposed, great!

Just one minor thing you can consider changing is to show a close button instead of or in addition to logout on /candidate/preview route, which would return the user to the start page.