diff --git a/Docs/Personas/Cedric.md b/Docs/Personas/Cedric.md deleted file mode 100644 index 08f81c031..000000000 --- a/Docs/Personas/Cedric.md +++ /dev/null @@ -1,19 +0,0 @@ -# Persona: Milena (mobile user to mobile contributor) - -## Background - -Name: Milena -Age: 31 -Occupation: Cycle reparation, comic artist -Computer skills: Good - - -## Interests & Influences - -## Motivations - -## Goals - -## Needs and expectations - -## Pain points & frustrations diff --git a/Docs/Personas/Elise.md b/Docs/Personas/Elise.md index 178ac7b4e..ba22da19a 100644 --- a/Docs/Personas/Elise.md +++ b/Docs/Personas/Elise.md @@ -1,4 +1,4 @@ -# Persona: NAME (scenario summary) +# Persona: Elise (communicating about POI) ## Background @@ -34,8 +34,11 @@ And except for pumps, there are also a few poles where yools (such a screwdriver At last, these pumps and tools are broken sometimes, so how to communicate this to the public? -## Needs and expectations +## User scenario +Elise want to have a read-only view with only pumps embedded on her website. +As such, she creates an embed-link on the 'share'-screen where she disables some options to log in (and thus disables making edits), disables all layers she doesn't need and sets a home location. + +Furthermore, she makes a second version which only shows bicycle repair shops and embeds this on a different page. -## Pain points & frustrations diff --git a/Docs/Personas/Jos.md b/Docs/Personas/Jos.md new file mode 100644 index 000000000..32b35f4bb --- /dev/null +++ b/Docs/Personas/Jos.md @@ -0,0 +1,16 @@ +# Persona: Jos (Crowdsourcing campaign + import) + +## Background + +Jos works for a national, tourist agency which promotes tourism in the country. +They currently focus on cycle tourism, including ebikes. For this, they'd like to make a map showing all the charging stations for electrical bikes, except that no one knows where these are. + +Additionally, other POI (such as toilets, benches and picnic tables) are important as well. For those, various data sets are lying around, all covering different geographical areas and having different formats. He'd love to see those data sets unified and maintained together. + +## User scenario + +As such, he'd like to facilitate crowdsourcing this data and importing them into OpenStreetMap. + +For the POI that are missing - namely the charging stations for electrical bikes - he sets up a custom map with the custom theme generator and starts a media campaign by inviting all partners of the touristical agency to add information about charging stations that they know of. Additionally, a promo video is made to be circulated on social media. + +Additionally, a (guided) import is setup for the diverse datasets that are available so that the new points can be integrated as well. diff --git a/Docs/Personas/Maarten.md b/Docs/Personas/Maarten.md index dca30c5cb..5bbd9e4b9 100644 --- a/Docs/Personas/Maarten.md +++ b/Docs/Personas/Maarten.md @@ -24,4 +24,26 @@ Making an inventory of all AED's - See which items he's already checked and which he still has to visit - Add a picture and metadata about every AED +## Scenario + +### Preparation + +Before starting the survey, the already existing data of the municipality is loaded into a guided import helper - a special theme to support the (re)survey is set up, e.g. with the MapRoulette integration or the 'Notes'-import-flow integration. + +Maarten receives a small training on how to use the tools, a few AED's are mapped together. + +### Surveying + +Maarten cycles around the city, visiting all AEDs that aren't visited yet. +When an AED is mapped, this is done with the import tool and by adding some information. + +If a location is visited but the AED doesn't exist anymore, this is marked as such in the import tool + +This can take several weeks to complete + +### After surveying + +After surveying, all the data can be exported using the 'download'-button (which is enabled on the custom theme) for data analysis or to add it to the municipality website. + +Alternatively, MapComplete can be embedded in the municipality website directly. diff --git a/Docs/Personas/Mateo.md b/Docs/Personas/Mateo.md new file mode 100644 index 000000000..4b3a63dcb --- /dev/null +++ b/Docs/Personas/Mateo.md @@ -0,0 +1,17 @@ +# Persona: Mateo (casual user) + +## Background + +- Name: Mateo + + +## User scenario + +Mateo goes rock climbing every now and then. To discover climbing routes, he uses the climbing map to search for locations. + +Before planning a trip, he browses around on the map to see possible climbing crags. He searches climbing crags in the area of interest and zooms then in to see how much climbing routes and of which difficulty they are. + +He finds the information he needs, even though he doesn't have an OpenStreetMap account. + + +After a while, he spots a missing item and signs up to correct this item. diff --git a/Docs/Personas/Pieter.md b/Docs/Personas/Pieter.md new file mode 100644 index 000000000..4cc76883f --- /dev/null +++ b/Docs/Personas/Pieter.md @@ -0,0 +1,17 @@ +# Persona: Pieter (casual OSM contributions) + +## Background + +- Name: Pieter +- Age: 20-30 +- Computer skills: Excellent + + +Pieter regularly contributes to OpenStreetMap and wants to keep the map up to date. + +When a new element appears in the city where he lives - such as a bench or artwork, he'll open up MapComplete to check if that item is already mapped in OpenStreetMap. +If the item is not on OSM, he'll quickly add the item there and fill out the form with all relevant information and adds a picture. + +Similarly, when he visits a shop or restaurant, he'll open up MapComplete during the waiting time and check that all the metadata is still correct. + +At last, if a feature has been removed in real life or has slightly moved, he'll use MapComplete to udpate this as well. diff --git a/Docs/Personas/README.md b/Docs/Personas/README.md new file mode 100644 index 000000000..5f8671332 --- /dev/null +++ b/Docs/Personas/README.md @@ -0,0 +1,19 @@ +# Personas / user scenarios + +In this directory, you'll find some possible user profiles and how they interact with MapComplete. + +They serve as a baseline, to indicate what type of use cases are important to support for MapComplete. +In other words, these persona's are a part of the vision on what MapComplete should (not) be. +As such, they mostly focus on a specific use case, not necessarily on fluffy background of the persona - unless that background is relevant. + +Note that the UserTests might also give a good idea on where usability might go wrong in small, individual steps. + +## The most important user scenarios are + +- [Someone who needs a map with some type of POI (and which in turns becomes a contributor)](./Mateo.md) +- [A casual OSM-contributor](./Pieter.md) +- [Someone who needs to survey a lot of points in the field in a mapping campaign](./Xavier.md) +- [Someone who needs to _re_survey a lot of points](./Maarten.md) +- [Someone who needs to manage data on an ongoing basis (and validate changes)](./Tom.md) +- [Someone who needs to _communicate_ about POI (e.g. on their website)](./Elise.md) +- [Someone who has a dataset and wants it imported into OSM/wants to run a crowdsourced mapping campaign](./Jos.md) diff --git a/Docs/Personas/Tom.md b/Docs/Personas/Tom.md index a3dcfb64d..31c2d0e3c 100644 --- a/Docs/Personas/Tom.md +++ b/Docs/Personas/Tom.md @@ -18,11 +18,6 @@ Tom works for the city council and is responsible for maintaining a lot of data and physical devices. His days are swamped with big and little tasks to keep everyone in the municipality safe. -## Goals - -One of his tasks is to keep an up-to-date list of all the AEDs and to effectively communicate this to his citizens. -Today, a citizen sent an email that they have installed an AED in their shop. - ## Needs and expectations A map showing all nearby AED's, with their availability and if they are publicly accessible. @@ -37,3 +32,16 @@ Ideally, all the AED's would show up in Google Maps as most people are familiar It is hard to maintain a list of all AEDs and to keep this up to date. The map on the website is oudated and people don't know it exists. The list on the website is an excel-sheet; in case of an emergency it is nearly impossible to spot which AED is the closest. + +## User scenario + +All the AEDs have already been surveyed by [Maarten](./Maarten.md), so the data should be up to date. + +When a shop owner sends him an email that they installed an AED in their shop, he has some options: + +- he asks the shop owner to add the AED directly into MapComplete +- he adds the AED himself - either remotely by the emailed information or by surveying locally + +Additionally, he gets an automatic message when someone made a change to an AED within the boundaries of the city, so that he can review it. + +Every while, he'll also download the data to make a report, e.g. on the total number of AEDs in the city or a heatmap of the distribution. diff --git a/Docs/Personas/Xavier.md b/Docs/Personas/Xavier.md index 47a835866..88eb2c1b0 100644 --- a/Docs/Personas/Xavier.md +++ b/Docs/Personas/Xavier.md @@ -15,17 +15,11 @@ Together, they want that more people take the bicycle and that cycling becomes s ## Motivations -In order to create a safer cycling environment, Xavier wants to urge the local municipality to remove bollards from the cycleways if those bollards don't add a lot of value. -But then, they first need to know _where_ all those bollards are. +In order to create a safer cycling environment, Xavier wants to urge the local municipality to remove bollards from the cycleways if those bollards don't add value. +But then, they first need to know _where_ all those bollards are - data that the municipality doesn't have as well. -## Goals +## Scenario -Create a map of all bollards +Xavier starts with adding all the bollards in his neighbourhood. He opens up the cycle-infra theme and adds all bollards that he sees while surveying all streets during an afternoon he is out on the streets. -## Needs and expectations - -Easily add bollards to a map, easily show an overview map of where all the bollards are - -## Pain points & frustrations - -It is hard to create such a map and get an overview of this... +He'll use the data afterwards to inform the municipality where bollards are. diff --git a/Docs/Personas/_README.md b/Docs/Personas/_README.md deleted file mode 100644 index bddf4fad0..000000000 --- a/Docs/Personas/_README.md +++ /dev/null @@ -1,20 +0,0 @@ -# Personas - -In this directory, you'll find some possible user profiles and how they interact with MapComplete. - -They serve as a baseline, to indicate what type of use cases are important to support for MapComplete. -In other words, these persona's are a part of the vision on what MapComplete should (not) be. -As such, they mostly focus on a specific use case, not necessarily on fluffy background of the persona - unless that background is relevant. - -Note that the UserTests might also give a good idea on where usability might go wrong in small, individual steps. - -## The most important usecases are - -- Someone who needs a map with some type of POI (and which in turns becomes a contributor) -- A casual OSM-contributor -- Someone who needs to survey a lot of points in the field in a mapping campaign --> Xavier, paaltjestocht -- Someone who needs to _re_survey a lot of points --> Maarten O (for AED) -- Someone who needs to manage data on an ongoing basis (and validate changes) --> Security prevention -- Someone who needs to _communicate_ about POI (e.g. on their website) --> Fietsambassade -- Someone who has a dataset and wants it imported into OSM --> Jos -- Someone who needs to analyse the OSM-data --> Jos, city municipality, OnWheels diff --git a/Docs/Personas/_TEMPLATE.md b/Docs/Personas/_TEMPLATE.md deleted file mode 100644 index 6bf7a001e..000000000 --- a/Docs/Personas/_TEMPLATE.md +++ /dev/null @@ -1,20 +0,0 @@ -# Persona: NAME (scenario summary) - -## Background - -- Name: -- Age: -- Occupation: -- Computer skills: -- Demography: - - -## Interests & Influences - -## Motivations - -## Goals - -## Needs and expectations - -## Pain points & frustrations