- Economic and Ecosystem Model Analysis
- Design Kit
The main objective of the design kit is to provide the SP teams with an understanding of who their users are, how those users may interact with what they are building, and how to make their deliverables aligned with the inclusive design principles and best practices. The design kit is comprised of three main components:
Each of these components provide a differnt perspective towards the P4A ecosystem. The use model aims to introduce a concrete representation of the end users of the P4A project to SP teams. While the design specifications are more focused on the P4A infrastructure and the functionalies it should incorporate to offer more inclusive experiences. And after all, the inclusive design guides introduce the principles and practical methods that are required to build inclusive solutions. Together, these three components will help the entire project team to understand the real-world uses of their deliverables, get informed of recommended specifications and functionalities and follow best practices in their design, development and delivery processes.
Kit Components at a Glance
What is it: Provides a deeper knowledge of potential users and their interactions with the P4A ecosystem.
Who can use it: SP2 and SP3 teams can use it when they are building their deliverables to make them more user centeric. SP4 team can use it to evaluate the inclusivity of various parts of the P4A ecosystem, and foresee how users evolve within that ecosystem.
Why it's helpful: The use model is developed based on an extensive user research. Thus, it will help SP teams to have a wide range of people who may use their products in mind, and do not overlook their needs, challenges, desires and aspirations.
What is it: Identifies global specifications and specific functionalities that are required to create inclusive user experiences and interactions within the P4A ecosystem.
Who can use it: The GPII team should consider following the global design specifications when building different parts of the GPII. SP2 and SP3 teams should consider incorporating the functionalities that are specific to their functional package.
Why it's helpful: The next step after understanding the users and their interactions with the ecosystem is to provide solutions that respond to user needs and support the required interactions. Design specifications surface those required functionalities and bridge the user needs with the final solution.
Inclusive Design Guide:
What is it: Creates easier-to-consume, concise and engaging guidelines for inclusive design, and provides tools to put those guidelines into practice.
Who can use it: All internal project partners as well as external collaborators and contributors can use these guides to gain a better understanding of an inclusive design approach and practice its application in their projects or processes.
Why it's helpful: Applying the use model and the design specifications won't lead to inclusive solutions unless all the other processes involved in the design and development of a solution are informed by the inclusive design best practices. Inclusive design guides help teams exercise an inclusive approach towards creation of new solutions.
Return to Inclusive Models