Difference between revisions of "Annual Strategy"

From i3Detroit
Jump to: navigation, search
(Added new page)
 
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
 
=Annual Strategy=
 
=Annual Strategy=
 
This page is for collecting information leading to a year-ahead "what do we want to accomplish for the space" plan.  It also documents what has been decided and accomplished ... so far.
 
This page is for collecting information leading to a year-ahead "what do we want to accomplish for the space" plan.  It also documents what has been decided and accomplished ... so far.
===Calendar Year 2012==
+
 
 +
===Meeting on Jan 17th 2012===
 +
*Matt O. to pursue and foster relationships with other organizations
 +
*Nate B. to champion rebranding into Make * Meet * Hack ?
 +
*John ? to champion remodel of kitchen/craft area
 +
 
 +
===Calendar Year 2012===
 
A small group met on 9 Sept 2011 to talk about what we want to do in 2012 ... or sooner.  The first thing we did was brainstorm the issues that we need to address.  There were three key groups of issues:
 
A small group met on 9 Sept 2011 to talk about what we want to do in 2012 ... or sooner.  The first thing we did was brainstorm the issues that we need to address.  There were three key groups of issues:
  
Line 7: Line 14:
 
====Issues====
 
====Issues====
 
Group A: (12 priority points)
 
Group A: (12 priority points)
Get equipment working
+
*Get equipment working
  
 
Group B: (8 priority points)
 
Group B: (8 priority points)
Retain people during cold months
+
*Retain people during cold months
Drama - not getting along
+
*Drama - not getting along
Getting more artists, minorities, kids, and women.
+
*Getting more artists, minorities, kids, and women.
  
 
Group C: (10 priority points)
 
Group C: (10 priority points)
People working on projects
+
*People working on projects
More group projects and collaboration
+
*More group projects and collaboration
Wheel truing stand
+
*Wheel truing stand
Bike shop revamp
+
*Bike shop revamp
Make bread
+
*Make bread (this was from a metaphor of us being a bakery that doesn't make bread, but just gathers bread making equipment)
  
 
====Root causes====
 
====Root causes====
Line 25: Line 32:
  
 
Group A: Get Equipment Working
 
Group A: Get Equipment Working
Money
+
*Money
Time
+
*Time
Ownership confusion
+
*Ownership confusion
Lack of updates / communication
+
*Lack of updates / communication
Don't want / care about it
+
*Don't want / care about it
  
 
Group B: People
 
Group B: People
Classes
+
*Classes
Better lighting
+
*Better lighting
Cleaning / housekeeping
+
*Cleaning / housekeeping
Lack of activities
+
*Lack of activities
Weather - hard to get here
+
*Weather - hard to get here
Dark location (safety?)
+
*Dark location (safety?)
  
 
Group C: Projects
 
Group C: Projects
Tool chains not complete
+
*Tool chains not complete
Lack of inspiration / communication
+
*Lack of inspiration / communication
Intimidated by inexperience and people
+
*Intimidated by inexperience and people
Lack of clean work areas
+
*Lack of clean work areas
Lack of follow-through on rules
+
*Lack of follow-through on rules
Discouraging surroundings
+
*Discouraging surroundings
  
 
====Proposed Solutions====
 
====Proposed Solutions====
 
We picked four root causes to try to develop some solutions and make assignments.  In the following, it's important to note that this is the raw list of ideas mentioned.  We only agreed on implementing the ones with names attached.
 
We picked four root causes to try to develop some solutions and make assignments.  In the following, it's important to note that this is the raw list of ideas mentioned.  We only agreed on implementing the ones with names attached.
  
1. Tool chains incomplete
+
#Tool chains incomplete
Have zone wardens tell us
+
#*Have zone wardens tell us
Promote use of dream list (Matt)
+
#*Promote use of dream list (Matt) [Potluck scheduled with to-do list]
Develop tools chains and documents missing elements (Roger)
+
#*Develop tools chains and documents missing elements (Roger) [Working on how to document. See PCB wiki page sample.]
Moratorium on new acquisitions until existing stuff is functional or out
+
#*Moratorium on new acquisitions until existing stuff is functional or out
Post to group to look out for new joiner (Dave)
+
#*Post to group to look out for new joiner (Dave S) [Done!]
Make list of non-functional tools or tools we should dispose (Rocco)
+
#*Make list of non-functional tools or tools we should dispose (Rocco) [No update]
 
+
#Lack of inspiration / Discouraging surroundings / Lack of clean working space
2. Lack of inspiration / Discouraging surroundings / Lack of clean working space
+
#*Get an intern to blog for us
Get an intern to blog for us
+
#*Find project managers or coaches to check in on people about their projects
Find project managers or coaches to check in on people about their projects
+
#*Encourage people to blog about their projects (Matt) [Started. Roger to post Wiki class.]
Encourage people to blog about their projects (Matt)
+
#*Merit badges [Done!]
Merit badges
+
#*Awards for best / most projects
Awards for best / most projects
+
#*Limit the number of tools to increase awareness when they are missing
Limit the number of tools to increase awareness when they are missing
+
#*Identify a location for each tool [Nate started this on workbench.]
Identify a location for each tool
+
#*Have more clean-up days / potlucks [Scheduled for 19 Nov]
Have more clean-up days / potlucks
+
#*Make a list of things to be done on the wiki (Matt) [Agreed to drop this one]
Make a list of things to be done on the wiki (Matt)
+
#*Develop a floor plan to make better use of the space (Roger) [No progress]
Develop a floor plan to make better use of the space (Roger)
+
#Intimidated by inexperience and people
 +
#*Tutorial videos (Dustin and Nate W) [Concepts together, need to script and produce]
 +
#*More classes
 +
#*Working group to develop scripts / videos (Dustin, Rocco, and Nate W) [See above]
 +
#*Catalog / link to existing materials (Rocco) [No progress]
 +
#*QR codes on everything (Rocco)  [Added to wiki pages.  Need to make sample to post.]
 +
#*Put lockouts on machines
 +
#*Class signups on each machine (w/ QR codes) (Rocco) [See above]
 +
#Lack of follow-thru on rules and policy
 +
#*Evalutate the rules: Are they self-enforcing? Enforceable? Economics driven?
 +
#*Security deposits for using space (e.g., parking tickets fines) (Dustin)  [Agreed to drop this one.  Google Doc instead.]
 +
#*Perp in the dunk tank for offenders
 +
#*Own up to your violations
  
3. Intimidated by inexperience and people
+
Use these tags around items that have been completed <del>Completed</del>
Tutorial videos (Dustin and Nate W)
+
More classes
+
Working group to develop scripts / videos (Dustin, Rocco, and Nate W)
+
Catalog / link to existing materials (Rocco)
+
QR codes on everything (Rocco)
+
Put lockouts on machines
+
Class signups on each machine (w/ QR codes) (Rocco)
+
  
4. Lack of follow-thru on rules and policy
+
[[Category:Strategy]][[Category:Organization Information]][[Category:Meeting Minutes]]
Evalutate the rules: Are they self-enforcing? Enforceable? Economics driven?
+
Security deposits for using space (e.g., parking tickets fines) (Dustin)
+
Perp in the dunk tank for offenders
+
Own up to your violations
+

Latest revision as of 13:01, 24 June 2012

Contents

Annual Strategy

This page is for collecting information leading to a year-ahead "what do we want to accomplish for the space" plan. It also documents what has been decided and accomplished ... so far.

Meeting on Jan 17th 2012

  • Matt O. to pursue and foster relationships with other organizations
  • Nate B. to champion rebranding into Make * Meet * Hack ?
  • John ? to champion remodel of kitchen/craft area

Calendar Year 2012

A small group met on 9 Sept 2011 to talk about what we want to do in 2012 ... or sooner. The first thing we did was brainstorm the issues that we need to address. There were three key groups of issues:

(note that these are just the raw ideas - more analysis follows)

Issues

Group A: (12 priority points)

  • Get equipment working

Group B: (8 priority points)

  • Retain people during cold months
  • Drama - not getting along
  • Getting more artists, minorities, kids, and women.

Group C: (10 priority points)

  • People working on projects
  • More group projects and collaboration
  • Wheel truing stand
  • Bike shop revamp
  • Make bread (this was from a metaphor of us being a bakery that doesn't make bread, but just gathers bread making equipment)

Root causes

For each of these groups, we tried to understand the root causes. Here are the thoughts:

Group A: Get Equipment Working

  • Money
  • Time
  • Ownership confusion
  • Lack of updates / communication
  • Don't want / care about it

Group B: People

  • Classes
  • Better lighting
  • Cleaning / housekeeping
  • Lack of activities
  • Weather - hard to get here
  • Dark location (safety?)

Group C: Projects

  • Tool chains not complete
  • Lack of inspiration / communication
  • Intimidated by inexperience and people
  • Lack of clean work areas
  • Lack of follow-through on rules
  • Discouraging surroundings

Proposed Solutions

We picked four root causes to try to develop some solutions and make assignments. In the following, it's important to note that this is the raw list of ideas mentioned. We only agreed on implementing the ones with names attached.

  1. Tool chains incomplete
    • Have zone wardens tell us
    • Promote use of dream list (Matt) [Potluck scheduled with to-do list]
    • Develop tools chains and documents missing elements (Roger) [Working on how to document. See PCB wiki page sample.]
    • Moratorium on new acquisitions until existing stuff is functional or out
    • Post to group to look out for new joiner (Dave S) [Done!]
    • Make list of non-functional tools or tools we should dispose (Rocco) [No update]
  2. Lack of inspiration / Discouraging surroundings / Lack of clean working space
    • Get an intern to blog for us
    • Find project managers or coaches to check in on people about their projects
    • Encourage people to blog about their projects (Matt) [Started. Roger to post Wiki class.]
    • Merit badges [Done!]
    • Awards for best / most projects
    • Limit the number of tools to increase awareness when they are missing
    • Identify a location for each tool [Nate started this on workbench.]
    • Have more clean-up days / potlucks [Scheduled for 19 Nov]
    • Make a list of things to be done on the wiki (Matt) [Agreed to drop this one]
    • Develop a floor plan to make better use of the space (Roger) [No progress]
  3. Intimidated by inexperience and people
    • Tutorial videos (Dustin and Nate W) [Concepts together, need to script and produce]
    • More classes
    • Working group to develop scripts / videos (Dustin, Rocco, and Nate W) [See above]
    • Catalog / link to existing materials (Rocco) [No progress]
    • QR codes on everything (Rocco) [Added to wiki pages. Need to make sample to post.]
    • Put lockouts on machines
    • Class signups on each machine (w/ QR codes) (Rocco) [See above]
  4. Lack of follow-thru on rules and policy
    • Evalutate the rules: Are they self-enforcing? Enforceable? Economics driven?
    • Security deposits for using space (e.g., parking tickets fines) (Dustin) [Agreed to drop this one. Google Doc instead.]
    • Perp in the dunk tank for offenders
    • Own up to your violations

Use these tags around items that have been completed Completed