This week has been really hectic, mostly because we are preparing for an exhibition of our previous project about air quality, Joining the Data, where we partnered with the EPA and Intel. So our MP's have been put to the side and the Exhibition is taking control. I have tried to squeeze in a little bit of my own MP work because there is still a lot of work to be done.
Meanwhile, I've started creating a service blueprint to start figuring out how the mapping would work. This has made me realise that there might be a few different types of users using this service: the front-end users who map out the obstacles, the users who receive this information and use the data to navigate and also stakeholders and government bodies who might also be mapping out obstacles.
I also had an idea of creating a rating system, something like a scale of 1-5, 1 being not important and 5 being something that requires immediate attention. Along with the scale there'll be different categories under which things will get marked, permanent and temporary for example. Things that require immediate attention might somehow get forwarded to local authorities who can then do something to solve the problem. So to summarise, it would be like a constant loop where things are being detected and then marked and depending on certain things, action will be taken to help solve the issues.
At the moment these are things that are going through my head and it would be best to sit down with a clear head and try figure it all out.
I still have a lot of questions like how things are "marked" and how this relates back to the user and whether this is a product or a full service or if there is another way to map.
COMMENTS