ResiMob: Difference between revisions

From Dreams Knowledge Platform
Jump to: navigation, search
No edit summary
No edit summary
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div style="text-align: center;">
<div class="sump-intro">
==== Mapping the common and diverging perspectives ====
'''ResiMob''' is a survey and visualisation tool that shows a group of stakeholders their shared picture of who does what in a shared mobility system, and where that picture is not shared at all. It was developed in the DREAMS work on governance and business models and has been run with the partners of all six [[Living Lab Overview|living labs]].
</div>


When developing public–private collaborations for shared mobility, different stakeholders often see the system they operate in from different angles. This survey aims to bring those perspectives together and visualize them in a radar chart, comparing how stakeholders perceive their roles and responsibilities in shared mobility systems.  
A session takes a group of partners around a quarter of an hour. Each person rates how involved operators, public authorities, users and civil society organisations ought to be, and the answers come back as one radar chart the group can read and argue over together.


The survey, developed in the Dreams project, will take you around 10-15 min and you will be asked to rate both the current and wished involvement of different stakeholders across nine components than form a resilient, inclusive, and responsible shared mobility ecosystem.
<div class="dreams-btn">[[#The survey|Take the survey →]]</div>
</div>


By wished involvement, we mean the level of stakeholder participation you think is ideal to make shared mobility more accessible in suburban and peripheral areas and achieve 15-minute neighbourhoods.
== What the tool asks ==


The radar chart generated from your responses will help identify areas of alignment and divergence, supporting dialogue for better collaboration.  
Public and private actors working on the same shared mobility service rarely describe it the same way. An operator, a municipal department, a user group and a neighbourhood organisation each see a different part of the system, and each holds a different view of who ought to be taking responsibility for which part of it. Those views usually stay implicit and only surface once a decision has to be made. ResiMob asks for them directly and puts them side by side.


Thank you for contributing to better mobility solutions!
Respondents work through eight components that together make up a resilient, inclusive and responsible shared mobility ecosystem, namely facilitation, finance, feedback systems, regulations, physical infrastructure, digital infrastructure, equity values and environmental values. For each component they rate how involved four actor types should be, private mobility providers, public authorities, shared mobility users, and NGOs and third sector organisations. Involvement runs from one, none, to five, very high, with a separate answer for a respondent who does not know. Each respondent also says which of the four groups best matches their own role, which is what later lets the results be split by who answered.


== Wished and present involvement ==
The survey asks for one rating per actor and component, how involved that actor should be. The surveys run in the living labs used an earlier version that also asked how involved each actor is today, and that second rating is what the pooled results can add.
<div class="sump-bodies-grid">
<div class="sump-body-card">
<div class="sump-body-card__label">Wished involvement</div>
<div class="sump-body-card__desc">How involved each actor should ideally be to make shared mobility accessible in suburban and peripheral areas and to move towards 15-minute neighbourhoods. It is a normative judgement rather than a forecast, and it is what every session on this page collects.</div>
</div>
<div class="sump-body-card">
<div class="sump-body-card__label">Present involvement (living lab surveys)</div>
<div class="sump-body-card__desc">How involved respondents saw each actor in their local shared mobility system at the time. It records the arrangement as it was actually experienced, which is not always the one written into contracts and strategies, and it gives the wished picture something to be measured against.</div>
</div>
</div>
== How to read the results ==
Responses are pooled and drawn as a radar chart with one axis per component, each average rounded to a whole level, so a gap of a single step is already a real difference. The results can be filtered by city or region and by respondent type, which gives two readings for any session and a third where present involvement was recorded.
The first compares the actors with one another. It shows who the group expects to carry which component, and where it expects nobody in particular. In the pooled living lab results, operators and public authorities are expected to lead on almost everything, with public authorities set apart on regulations and physical infrastructure. Users are given a moderate role throughout, while NGOs and third sector organisations are given the smallest, least of all in finance and infrastructure.
The second uses the respondent filter. Where operators and authorities draw the same shape, there is a working consensus to build on. Where they diverge, there is an assumption about responsibility that has not yet been tested in conversation. The filter also shows who is missing. In the living lab surveys only operators and public authorities answered, so the modest role given to users and civil society is a judgement made about them rather than by them, and it is the first thing worth checking with them directly.
The third reading needs present involvement and so draws on the [{{fullurl:Special:Radarchart|file=File:ResimobSurvey.csv}} living lab results]. A wide gap between the present and the wished shape marks a role the group thinks is underfilled today, and a narrow gap marks an arrangement that is broadly accepted as it stands. Pooled across the six labs, the wished shape never falls inside the present one. The partners did not want to take involvement away from anyone, they wanted more of it, most clearly in digital infrastructure. A session of your own can be read against this as a reference point.
<div class="sump-versus">
<div class="sump-versus__pane">
<div class="sump-versus__head">Actors compared, wished involvement</div>
[[File:DREAMS-resimob-compare-actors.png|frameless|400px|alt=Radar chart comparing the wished involvement of operators, public authorities, users and NGOs across eight components]]
</div>
<div class="sump-versus__pane">
<div class="sump-versus__head">Present and wished, living lab surveys</div>
[[File:DREAMS-resimob-present-wished.png|frameless|400px|alt=Radar chart of present and wished involvement across eight components, averaged over all actors and living labs]]
</div>
</div>
<div class="dreams-callout">
<div class="dreams-callout__label">A starting point, not a verdict</div>
ResiMob does not settle who should be responsible for what. It makes the disagreement visible and specific enough to be discussed, which is what a governance conversation needs before roles can be agreed. That is why it is most useful while [[Agree actions and responsibilities|actions and responsibilities]] are still a draft and each allocation can still change.
</div>
<br>
== Taking the survey ==
A session can run in one room or be spread across the partners, and the results end up in the same combined chart either way.
<div class="dreams-tutorial">
<div class="dreams-tutorial__step">
<div class="dreams-tutorial__title">Choose how to collect the answers</div>
<div class="dreams-tutorial__body">In a workshop, sit together at one device and answer the form below person by person. If the partners cannot meet, send them the link to this page so each can answer on their own. Either way, name one person as host to gather and combine the results, and invite at least one user group and one civil society organisation, since the tool is only as balanced as the people who answer it.</div>
</div>
<div class="dreams-tutorial__step">
<div class="dreams-tutorial__title">Fill in the survey</div>
<div class="dreams-tutorial__body">Each respondent picks the stakeholder group that best matches their role, then rates how involved every actor type should be on each of the eight components. Enter the city or region too, even though it is optional, because the city filter in the results relies on it. It takes around ten to fifteen minutes per person. On a shared device, select '''+ Add information of another user''' to hand over to the next respondent.</div>
</div>
<div class="dreams-tutorial__step">
<div class="dreams-tutorial__title">Save the responses</div>
<div class="dreams-tutorial__body">When everyone on the device has answered, select '''Download the response(s) as CSV''' and send the file to the host. One download holds everyone who answered on that device. To pick up an unfinished session later, load the file again with '''Import session CSV'''. For a quick look at the answers so far, '''Submit and show results in the Radarchart''' opens the chart straight away.</div>
</div>
<div class="dreams-tutorial__step">
<div class="dreams-tutorial__title">Merge and present</div>
<div class="dreams-tutorial__body">Under '''Merge many responses''', the host selects all the files received and chooses '''Merge CSV files'''. The merged file is downloaded for safekeeping and the radar chart opens with the combined results. Start with the actor comparison to see who the group expects to carry each component, filter by respondent type to find where it disagrees, and set the result beside the living lab results to see where your partners want more or less than the labs did.</div>
</div>
</div>
<div class="dreams-handoff">
<div class="dreams-handoff__label">ResiMob results</div>
[{{fullurl:Special:Radarchart|file=File:ResimobSurvey.csv}} View the pooled results →] from the surveys run in all six DREAMS living labs, including the present involvement recorded there, and try the chart modes and filters before you run a session of your own.
</div>
<br>
== The survey ==
<resimobform></resimobform>
<resimobform></resimobform>

Latest revision as of 12:23, 21 September 2026

ResiMob is a survey and visualisation tool that shows a group of stakeholders their shared picture of who does what in a shared mobility system, and where that picture is not shared at all. It was developed in the DREAMS work on governance and business models and has been run with the partners of all six living labs.

A session takes a group of partners around a quarter of an hour. Each person rates how involved operators, public authorities, users and civil society organisations ought to be, and the answers come back as one radar chart the group can read and argue over together.

What the tool asks

Public and private actors working on the same shared mobility service rarely describe it the same way. An operator, a municipal department, a user group and a neighbourhood organisation each see a different part of the system, and each holds a different view of who ought to be taking responsibility for which part of it. Those views usually stay implicit and only surface once a decision has to be made. ResiMob asks for them directly and puts them side by side.

Respondents work through eight components that together make up a resilient, inclusive and responsible shared mobility ecosystem, namely facilitation, finance, feedback systems, regulations, physical infrastructure, digital infrastructure, equity values and environmental values. For each component they rate how involved four actor types should be, private mobility providers, public authorities, shared mobility users, and NGOs and third sector organisations. Involvement runs from one, none, to five, very high, with a separate answer for a respondent who does not know. Each respondent also says which of the four groups best matches their own role, which is what later lets the results be split by who answered.

Wished and present involvement

The survey asks for one rating per actor and component, how involved that actor should be. The surveys run in the living labs used an earlier version that also asked how involved each actor is today, and that second rating is what the pooled results can add.

Wished involvement
How involved each actor should ideally be to make shared mobility accessible in suburban and peripheral areas and to move towards 15-minute neighbourhoods. It is a normative judgement rather than a forecast, and it is what every session on this page collects.
Present involvement (living lab surveys)
How involved respondents saw each actor in their local shared mobility system at the time. It records the arrangement as it was actually experienced, which is not always the one written into contracts and strategies, and it gives the wished picture something to be measured against.

How to read the results

Responses are pooled and drawn as a radar chart with one axis per component, each average rounded to a whole level, so a gap of a single step is already a real difference. The results can be filtered by city or region and by respondent type, which gives two readings for any session and a third where present involvement was recorded.

The first compares the actors with one another. It shows who the group expects to carry which component, and where it expects nobody in particular. In the pooled living lab results, operators and public authorities are expected to lead on almost everything, with public authorities set apart on regulations and physical infrastructure. Users are given a moderate role throughout, while NGOs and third sector organisations are given the smallest, least of all in finance and infrastructure.

The second uses the respondent filter. Where operators and authorities draw the same shape, there is a working consensus to build on. Where they diverge, there is an assumption about responsibility that has not yet been tested in conversation. The filter also shows who is missing. In the living lab surveys only operators and public authorities answered, so the modest role given to users and civil society is a judgement made about them rather than by them, and it is the first thing worth checking with them directly.

The third reading needs present involvement and so draws on the living lab results. A wide gap between the present and the wished shape marks a role the group thinks is underfilled today, and a narrow gap marks an arrangement that is broadly accepted as it stands. Pooled across the six labs, the wished shape never falls inside the present one. The partners did not want to take involvement away from anyone, they wanted more of it, most clearly in digital infrastructure. A session of your own can be read against this as a reference point.

Actors compared, wished involvement

Radar chart comparing the wished involvement of operators, public authorities, users and NGOs across eight components

Present and wished, living lab surveys

Radar chart of present and wished involvement across eight components, averaged over all actors and living labs

A starting point, not a verdict

ResiMob does not settle who should be responsible for what. It makes the disagreement visible and specific enough to be discussed, which is what a governance conversation needs before roles can be agreed. That is why it is most useful while actions and responsibilities are still a draft and each allocation can still change.


Taking the survey

A session can run in one room or be spread across the partners, and the results end up in the same combined chart either way.

Choose how to collect the answers
In a workshop, sit together at one device and answer the form below person by person. If the partners cannot meet, send them the link to this page so each can answer on their own. Either way, name one person as host to gather and combine the results, and invite at least one user group and one civil society organisation, since the tool is only as balanced as the people who answer it.
Fill in the survey
Each respondent picks the stakeholder group that best matches their role, then rates how involved every actor type should be on each of the eight components. Enter the city or region too, even though it is optional, because the city filter in the results relies on it. It takes around ten to fifteen minutes per person. On a shared device, select + Add information of another user to hand over to the next respondent.
Save the responses
When everyone on the device has answered, select Download the response(s) as CSV and send the file to the host. One download holds everyone who answered on that device. To pick up an unfinished session later, load the file again with Import session CSV. For a quick look at the answers so far, Submit and show results in the Radarchart opens the chart straight away.
Merge and present
Under Merge many responses, the host selects all the files received and chooses Merge CSV files. The merged file is downloaded for safekeeping and the radar chart opens with the combined results. Start with the actor comparison to see who the group expects to carry each component, filter by respondent type to find where it disagrees, and set the result beside the living lab results to see where your partners want more or less than the labs did.
ResiMob results

View the pooled results → from the surveys run in all six DREAMS living labs, including the present involvement recorded there, and try the chart modes and filters before you run a session of your own.


The survey