User research - Module personen

Goal

As part of the feature passport: Module Personen, we are conducting user research to gain insights into how the users use the current Sharepoint lists used to store data on people and positions as well as their likes, dislikes, and expectations.

Participants

We are organising two sessions:

1. The first session will be attended by the following:

   • LOW (NOT dossierbehandelaars)

   • Screeningsdienst

   • Afdelingshoofd LF

2. The second session will be attended by the following:

   • Dossierbehandelaars LOW

Format

Both sessions will follow the same format:

1. An introduction

   • Quick person-introduction for anyone that doesn't remember us

   • The participants will be told what the format is of the session

   • The participants will be made aware that:

     • everything they tell us is confidential

     • there will be no recordings but, but we will be taking notes

     • they do not need to change their behaviour to please us and they cannot hurt us with their feedback, on the contrary, the more honest they are about something not working for them, the more likely we are to be able to build good features in the future

2. Present the challenges to the user

   • We will be doing this with a presentation: we will explain the context of the questions to the users and ask the following:

   Search screens

   • In what contexts do you usually search for people in your current job? What information are you looking for when searching for a person?

   • When would you use the persons module?

     • When you search for a person, how do you do it? Do you always just type in the name? What refinement filters would you use/do you need?

       • If you use "gemeente" as a filter, is this the gemeente of the organisation of the person, or the gemeente of the contact information of the person? Can they differ?

   Contact information page

   • Practical question: How many positions can a person have on average? This will inform how we display contact information data.

   Positions page

   • When you look at the positions of a person, what are you primarily interested in?

     • Do you often/ever look at past positions?

3. Questions and feedback

   • We will ask whether the attendees have questions for us or other points they might want to raise concerning the Module: Personen.

A future attendee already sent us some feedback on some flows concerning the use of people in an email prior to the session. The feedback is out of scope for this session and the feature passport it concerns, but should still be looked at.

The session

Notes

• Users haven't used OP a lot yet. This will happen in the future but they haven't needed to use it as of yet. (Session 1)

• Users have used OP a lot, but only the Bestuurseenheden module, they do not use the persons module in its current form.

• Search screens

  • In what contexts do you usually search for people in your current job? What information are you looking for when searching for a person? When would you use the persons module?

    • Searching for a specific person within an organisation

      • In the second session the users said they would've done this through the bestuurseenheden module

    • Searching for links between people - identify networks

    • Searching for a person when they know the name but not the organisation

    • Searching for a position in an organisation with then don't know the name/partially know the name

    • Searching for a person's address

    • Searching a person to find out if they work/have ties with more than just one organisation

  • When you search for a person, how do you do it? Do you always just type in the name? What refinement filters would you use/do you need?

    • Name filter (sometimes only parts of the name are known)

    • Organisation

    • Position

    • Filtering out non-active positions is good. The possibility to see then non-active ones too is also good, e.g: when trying to see the links between people who have worked together in the past, or everyone who has every worked for an organisation.

      • This feature was not needed for the users in session 2.

  Contact information page

  • Practical question: How many positions can a person have on average? This will inform how we display contact information data.

    • Usually there will be only 1-2 active positions at a time. It might happen that there are more, but never more than 3-5.

    • 2-3 positions at the same time, sometimes 4 but this is not the norm.

  Positions page

  • When you look at the positions of a person, what are you primarily interested in?

    • Do you often/ever look at past positions?

      • Seeing past positions is OK

  Questions and other feedback

  • Seeing kleine and grote helft is important to for us, as we need to be able to see whether the elections happen properly

  • Positions should be sorted chronologically. The newest on top.

  • The title on every page is unnecessary / the hierarchy might be wrong. When I'm on a page I can already tell what page I'm on when I look in the sidebar. For detail pages, the Positie: is definitely unnecessary repetition. Maybe the name should be thicker than the position.

  • User asked what Betrokken Lokale Besturen meant.

  • User also sent an email with some other problems they found while inputting mandate information

  • the search screen for bestuurseenheden is slow - scared this will be the case for persons module too

  • there was a problem with inputting addresses manually. Would prefer if this would be automatised (needs further investigation)

Conclusions

For the feature passport, we will:

• Add an organisation filter

• Add a position filter

• Add an active-inactive filter

• Keep the card view for contact information as there are not too many positions

• Positions should be sorted chronologically. The newest on top.