Job Organization - Revision history

Rfs: /* Divisions or Departments */

2010-12-30T17:30:10Z

Divisions or Departments

Rfs: /* Divisions or Departments */

2010-12-30T17:29:01Z

Divisions or Departments

Rfs: /* Divisions or Departments */

2010-12-30T17:28:16Z

Divisions or Departments

Rfs at 17:26, 30 December 2010

2010-12-30T17:26:27Z

Rfs at 19:52, 29 December 2010

2010-12-29T19:52:15Z

Rfs at 17:23, 29 December 2010

2010-12-29T17:23:44Z

Rfs: New page: Notes: * each role is a discrete unit of related tasks (or job duties) that need to be performed * put together, all the roles describe all the work that needs to be done at Free Geek * ro...

2010-12-29T17:09:39Z

New page: Notes: * each role is a discrete unit of related tasks (or job duties) that need to be performed * put together, all the roles describe all the work that needs to be done at Free Geek * ro...

New page

Notes:
* each role is a discrete unit of related tasks (or job duties) that need to be performed
* put together, all the roles describe all the work that needs to be done at Free Geek
* roles may supervise or report to other roles as needed
* each role will usually have associated:
** needed experiences (for example from a past job)
** needed certificates (such as a drivers license)
** needed technical knowledge (computer literacy, etc.)
** accountabilities (job duties)
** competencies (skills and abilities)
* a role must be filled in one of three ways, depending on what we need and what we can afford:
*# assigned to a single job description (single responsible person)
*# assigned to more than one job description, usually two (co-responsible persons)
*# assigned to a committee (when greater shared responsibility is desired, or when we can't afford to hire for an important job)
* each job description has one or more person assigned to it

Committees could be in departments (or divisions), which are mostly conceptual at this point. There are at least two divisions:
# administrative services -- the things we need to do to be a functioning organization, but don't say what we are actually doing, for example:
#* HR
#* Internal Tech Support
#* Facilities Maintenance
# program activities -- the things that explain what the organization does, its main activities and reason for existence, for example:
#* all the production related work
#* education program
#* thrift store

The program activities division could be subdivided if desired, for example:
* production related
* education related
* sales related
* warehouse related

@@ Line 29: / Line 29: @@
 == Divisions or Departments ==
-Committees could be in departments (or divisions), which '''are mostly conceptual''' at this point. There are at least two divisions:
+Committees could be grouped into departments (or divisions), which '''are mostly conceptual''' at this point. But it's an important concept that could help clarify what a committee is designed to do. There are at least two divisions:
 # administrative services -- the things we need to do to be a functioning organization, but don't say what we are actually doing, for example:
 #* HR

@@ Line 29: / Line 29: @@
 == Divisions or Departments ==
-Committees could be in departments (or divisions), which are mostly conceptual at this point. There are at least two divisions:
+Committees could be in departments (or divisions), which '''are mostly conceptual''' at this point. There are at least two divisions:
 # administrative services -- the things we need to do to be a functioning organization, but don't say what we are actually doing, for example:
 #* HR

@@ Line 1: / Line 1: @@
 [[Image:Job-descriptions.png]]
-== Schema Notes ==
+* each '''role''' is a discrete unit of related tasks (or job duties) that need to be performed
 * put together, all the roles describe all the work that needs to be done at Free Geek
 * roles may supervise or report to other roles as needed
 * each role will usually have associated:
-** needed experiences (for example from a past job)
+** '''needed experiences''' (for example from a past job)
-** needed certificates (such as a drivers license)
+** '''needed certificates''' (such as a drivers license)
-** needed technical knowledge (computer literacy, etc.)
+** '''needed technical knowledge''' (computer literacy, etc.)
-** accountabilities (job duties)
+** '''job duties''' (accountabilities)
-** competencies (skills and abilities)
+** '''competencies''' (skills and abilities)
 * a role must be filled in one of three ways, depending on what we need and what we can afford:
-*# assigned to a single job description (single responsible person)
+*# assigned to a ''single'' job description (single responsible person)
-*# assigned to more than one job description, usually two (co-responsible persons)
+*# assigned to a ''team'' more than one job description, usually two (co-responsible persons)
-*# assigned to a committee (when greater shared responsibility is desired, or when we can't afford to hire for an important job)
+*# assigned to a ''committee'' (when greater shared responsibility is desired, or when we can't afford to hire for an important job)
-* each job description has one or more person assigned to it
+* each '''job description''' has one or more '''worker''' assigned to it
 == How does this work? ==

@@ Line 1: / Line 1: @@
 [[Image:Job-descriptions.png]]
-Notes:
+== Schema Notes ==
 * each role is a discrete unit of related tasks (or job duties) that need to be performed
 * put together, all the roles describe all the work that needs to be done at Free Geek
@@ Line 17: / Line 17: @@
 * each job description has one or more person assigned to it
 To create a '''full job description''', we would select the roles that go into it, and compile all the accountabilities (job duties), competencies, and "needed" stuff associated with each role. This would tell us what would go in a full job description.
@@ Line 25: / Line 26: @@
 There will be some roles that are designed to apply to many people, for example all staff or all workers in a particular category. These would simply be included in the appropriate job descriptions. Such roles would be named things like "area coordinator" or "all workers", etc.
 Committees could be in departments (or divisions), which are mostly conceptual at this point. There are at least two divisions:
 # administrative services -- the things we need to do to be a functioning organization, but don't say what we are actually doing, for example:

@@ Line 35: / Line 35: @@
 #* Facilities Maintenance
 # program activities -- the things that explain what the organization does, its main activities and reason for existence, for example:
-#* all the production related work
+#* all the reuse (production) related work
 #* education program
 #* thrift store
 The program activities division could be subdivided if desired, for example:
-* production related
+* reuse related
 * education related
 * sales related
 * warehouse related