Stakeholder Mapping and Case scenarios
The stakeholders are major part of any project. As for PID it is a database whose exiting lies on crowd sourcing information for a huge user group. Now, it is important to know the people who will have a stake at the data contribution and retrieval.
As a designer we consider it our need to understand the use and misuse of the design we create. Every design can be exploited by the users but as a designer mapping the possibilities by which a user could use or misuse the information that our app provides is a matter of design ethics. To understand this, the primary function is to map the user of the system.
Users of this system could either be feeder or retriever of the information.
(stakeholder mapping of PID, created by The Alchemist)
We have classified the major user into category of Resident People, Travellers, Government Organisations/Agencies
What do we mean by these categories and how do they play a role as stakeholder ?
Resident people are the permanent resident of an area who are well aware of the surroundings and the loopholes of public infrastructure of that are. They are also the people who are very susceptible to the minor and major changes in the infrastructure of the surrounding. They could be shopkeeper, children, Adult, Elderly etc.
Travellers are put through the same challenges as the resident but for the traveller these challenges could be short term and they come as surprises to them. Travellers may or may not travel from the same location in their daily commute, thus the infrastructure inability could come as a shock to the travellers. Travellers could be Cyclist,Rickshaw drivers, daily commuters etc.
Government organisations/Agencies These are the members of the society who could be directly or indirectly responsible for providing the citizen with seamless infrastructure service across the area they are charge off, They could be the major data retriever of PID database. This does not imply that they cannot be data feeder into the database. Every information in the database is equally important and can be challenging to see when the data feeder turns to data retriever and vice versa.
Case scenario:
Case Scenario 1: Resident as data provider and Government as data users
Scenario 2: Daily Traveller as data provider and New Traveler as data users