Persona

<aside> 💁🏽 A user who is just getting acquainted with the system.

</aside>

Task

<aside> ✍🏽 Create a new page for the site.

</aside>

The formal action sequence (Core flow)

No.	Action step	Conclusion
1	Open a necessary site.	Success
2	Click an “Add New Page” button.	Success
3	Select type of the new page.	Success
4	Fill in the form fields.	Failure

Step 1. Open a necessary site

1- copy.png

| Will users try to achieve the right result? | YES | The user observes a list of existing sites. The search field is placed at the top left corner, which fits the F-shaped reading pattern. ⚠ Note. It appears that sites are sorted in reverse alphabetical order (e.g. sites starting with “A” are on the last page instead of being the first ones). ⚠ Note. Each page contains a different number of sites. These two factors impede searching for an appropriate site using pagination (in cases when the user doesn't remember the exact site title). | | --- | --- | --- | | Will users notice that the correct action is available? | YES | The user will see both a search field (top left) and pagination (top right) as well as a list of available sites. | | Will users associate the correct action with the result they’re trying to achieve? | YES | Hovering over the listed sites gives the user a hint with a green scrim and the text “Select site”. A search field supports a smart search and shows results after the first character is entered. | | After the action is performed, will users see that progress is made toward the goal? | YES | The selected site opens after a click. |

Step 2. Click the “Add New Page” button

| Will users try to achieve the right result? | YES | In case the user has just opened a site, the system initially shows the “Pages” menu on the sidebar where the button is placed. In case a user keeps working on a site and uses another sidebar menu, it still meets a mental model that associates creating a new entity (here it’s page) with the corresponding menu. | | --- | --- | --- | | Will users notice that the correct action is available? | YES | The “Add New Page” button is one of two primary CTAs on the page. Also, this button is a sticky element, a user doesn’t need to scroll to reach it. | | Will users associate the correct action with the result they’re trying to achieve? | YES | The button has a clear label. The pointer appears on hover suggesting that the element is interactive. | | After the action is performed, will users see that progress is made toward the goal? | YES | After the user clicked the “Add New Page” button, the system shows page types. |

Step 3. Select type of the new page

3 copy.png

Will users try to achieve the right result?	YES	Page types are placed in a sidebar, where a user took an initial action. In addition, a user is restricted from interacting with a website until she either selects a page type or closes the choice page by clicking the “Close” icon.
Will users notice that the correct action is available?	YES	The list of page types has a clear affordance of interactivity.
Will users associate the correct action with the result they’re trying to achieve?	YES	There are clear labels and brief explanations for each page type.
After the action is performed, will users see that progress is made toward the goal?	YES	The system shows the further form to be filled in.

Step 4. Fill in the form fields

4 copy.png

Clear error message under the “Filter” field

What does the “Persona” field mean?

If the user deletes the Filter field by clicking on a Delete icon next to the field and then tries to proceed, the “Add Page” button is blocked with no error message on display.

Will users try to achieve the right result?	YES	The user will see conventional text fields and dropdowns. If the user fails to fill in the required fields, the system will display an error message.
Will users notice that the correct action is available?	YES	Text fields and dropdowns on hover suggest interactivity.
Will users associate the correct action with the result they’re trying to achieve?	NO	1. For a new user, it can be hard to find out what the “Persona” field means (e.g. in the Category Search Results Page “Persona” refers to “External” and “Internal” values, in other types, it is “Career site” and “Employee experience”.
The error message “Page name already exists for this persona. Please enter a different name.” implies that “Persona” and “Page name” entities are connected, but this relationship seems unclear.

For pages where Filter is a required field (Landing page, Search Results Page): if the user deletes the “Filter” field by clicking on a Delete icon next to the field, and then tries to proceed, the “Add Page” button is blocked with no error message on display. To sort out this issue, the user must add a filter again, but if the flow was either interrupted or the field was deleted by mistake, it can be difficult to recall what exactly caused to blocking the button. | | After the action is performed, will users see that progress is made toward the goal? | YES | The system displays a new page and automatically scrolls down to the new page title in the sidebar. |

The formal action sequence (Additional flow - add page via copy)