Difference between revisions of "Inclusive Models"

From wiki.gpii
Jump to: navigation, search
(Misconceptions Table)
Line 11: Line 11:
  
 
{|
 
{|
! style="text-align:left;"| Item
+
! style="text-align:left;"| Domain
! Amount
+
! Old way of thinking/doing : Misconceptions & Ruts
! Cost
+
! New way of thinking/doing : Paradigm Shift
 
|-
 
|-
|Orange
+
|Development & Design
|10
+
|* Bulleted list item
|7.00
+
Isolated (stand alone functions) work packages that snap together when completed
 +
|* Bulleted list item
 +
* Require responsive system in quickly changing context with undefined and expanding scope
 +
* Functions are entangled and interdependent
 +
* Need built-in ability to incorporate early trial, error and feedback by users and iteratively respond to this
 +
* Be flexible and porous
 +
* Create conditions for growth, new uses and connections
 +
 
 
|-
 
|-
 
|Bread
 
|Bread

Revision as of 19:11, 11 February 2016

The infrastructure teams are asked to explore their practices and assumptions, note where they are falling into the ruts or misconceptions outlined in the misconceptions table below, and explore the design and economic models from SP1 to adapt their processes to achieve greater inclusion. A key part of the SP1 models is a loop of continuous feedback that leads to refinement of the models to ensure they better address the needs of the infrastructure teams while solving complex problems for unique users.

  • The Design kit including the Use Model, Design Specifications, and Inclusive Design Guides can be found here [1].
  • The economic and ecosystem model analysis can be found here [2].

Misconceptions Table

The ‘Misconceptions’ table contrasts the typical approaches (in various domains) that have failed with new ways of thinking and doing that are driving the paradigm shift needed for making the vision of P4A possible.

Domain Old way of thinking/doing : Misconceptions & Ruts New way of thinking/doing : Paradigm Shift
Development & Design * Bulleted list item

Isolated (stand alone functions) work packages that snap together when completed

* Bulleted list item
  • Require responsive system in quickly changing context with undefined and expanding scope
  • Functions are entangled and interdependent
  • Need built-in ability to incorporate early trial, error and feedback by users and iteratively respond to this
  • Be flexible and porous
  • Create conditions for growth, new uses and connections
Bread 4 3.00
Butter 1 5.00
Total 15.00

Feb 2016 Webinar

The main objective of the Feb 2016 webinar is to provide the infrastructure teams with a brief and clear description of the SP1 design and economic models and their applications. The following image lists the items that will be discussed during the webinar.