4.1.1 - Designing an Output Packet

The design process has an elusive quality.  Awareness toward process is a key tool in engaging with design.  At its most fundamental, design places conscious awareness around 'the how' and 'the what' we do: Observation, Goals Articulation, Analysis, Asssessment, Implementation, Evaluation are all commonly used in the cyclic nature of design.  It is crucial to recognize that design is not static; it is a dynamic process that most often is refined in its iterative nature: constant reassessment. 

Anywhere there is repetition in life is an opportunity to design for greater efficiency by creating templates or automation.  Designing structure around any iterative process or designing small routines into our life can be an effective use of making systems more efficient: templates, automation.     Design is an opportunity to create a structure; however, I would argue that those of us that feel free to improvise within our designs truly grasp the utility of design. Design, thus, creates a structure in which we are free to improvise in a container toward our goals.  Full circle evaluation of any automation is recognizing the iterative reassessment and refinement.   When the scale of a project is vast,  design holds this structure by enabling delegation (to a worker or our future self).

Why?
Creating an outline or a structure to present our material, experiences and findings is a valuable part of research and living.  Design can help bring structure, organization, clarity and efficiency to this OP and ideally to future OP's.  

How?
Observation/brainstorming prior to the design, flexibility during the process and reflection/evaluation with each successive draft/prototype.  Feedback can come through our own reflection or from peers and advisors returning us to the stages of analyzing and assessing the paths toward our goals.  
Spontaneity is a powerful force and often a great tool within a design.  I encourage creating a structure and then doing a lot of free writes (Get it done), then as we evaluate we can edit and refine. 

The xMind Map entitled  OP Structure Guidelines has been an evolving living mind map throughout this process that I both have used to guide this project and hope to have as a template for future OP's. This outline has helped me articulate the various components of an OP and recognize where some of those parts need my input and where some can be run on automation. 

I find that regardless of whether you are designing abstract concepts or concrete buildings, using models, frameworks or templates can function as a guiding light.  I have catered for many years and have often designed events.  The unique realization I came to in this OP is what are the patterns I am able to take away as a template to ease future work. Playing with multiple models of design allowed perspective.  The most empowering tool during this OP cycle was creating my own design methodology that shows me the key elements I use when designing a system/OP.  This illustrates a key feature of Gaia U: action learning theory which highly values doing over reading or watching.  I felt more empowered when I refined my own design methodology than reading the many others I have come upon.  Just Do It.  When we read something we may learn 20% but when we do it, we can learn 80%.   In light of theory on multiple models each shedding different light onto the project, I chose to brainstorm this design through several design processes that I have been introduced to.  I used OBREDIMET, GaSADIE and Simha's reflections on design, then I created my own system: ORGBADIE 

Observe the Opportunity
Research Information and Resources
Goal Articulation
Brainstorm
Assess and Analyze
Design
Implement
Evaluate

The primary outcome of working with multiple models in design methodologies is recognizing the power that different words have for eliciting ideas from me.  In some ways, the word Brainstorm has become a key aspect to my design methodology (thanks Simha) for its powerful connotations of Just doing IT without fear/judegement of right or wrong -- generating content for the sake of content.  Brainstorming increases the value and work of the Assess & Analyze stage.

Goals Articulation ideally is broken down into Actionable items that we recognize that we can do.  In Getting Things Done, Allen remarks that we need to make our "To Do" list specific concrete action.  This explicit clarity is fundamental often to the what and the how we are designing.  The drawing to the left represents the interplay in design between goals and actionable items.  As the design sharpens into focus, so, too, do the actionable items.  As I get clearer on what I am actually doing, it preposterously points to what I am aiming to do; and contrariwise, if, i know what it is I want, then mere deduction can often eludicate my path to success. 

    1.    improve as a designer
    2.    Bring ease to future OP's .
    3.    Communicate with reviewer/reader/ clear navigation and instructions
    4.    Use google docs
    5.    Use several design methodologies, create my own design methodology
    6.    Document my path as action learner
    7.    Show levels of change as the project progressed to document my action learning / emergent style
    8.    Play with fonts/colors
    9.    Clear outline/template of what each page of an OP looks like with clear requests to be filled in my language
    10.    Explore why we design
    11.    Catalog goals for catering events (addressed in Core Report)