Held on: March 15, 2012, 11:40am
Secretary: Brian Robertson

Made changes to: Technology Services Circle

Name changed:
  • Technology Services Circle
Accountability added:
  • Triaging usage-limiting issues in serviced technology platforms and fielding tactical database updates as requested by internal client roles

Made changes to: GlassFrog Account Manager

Accountability added:
  • Informing appropriate users of scheduled maintenance periods for GlassFrog

Made changes to: GlassFrog Product Manager

Accountability added:
  • Scheduling maintenance periods required for GlassFrog

Made changes to: Legal

Accountability added:
  • Evaluating and registering potential trademarks for the Organization
Domain added:
  • The Organization's trademarks

Made changes to: Operations

Accountability removed:
  • Selecting and administering health insurance programs for organization members
    • Recurring Project (annual): Review insurance options, update if appropriate

Made changes to: Content & Outreach

Domain removed:
  • Materials, information, & programs that convey Holacracy

Policy removed: Marketing Authorizing Derivative Works

Policy removed:
  • Marketing may authorize external parties to create derivative works of any IP owned or duly-licensed by HolacracyOne and released by HolacracyOne under a Creative Commons license that normally excludes derivative works, provided that such external party agrees that HolacracyOne shall retain sole ownership of the derivative work. However, Marketing may offer an attribution to the creating party in the derivative work, and a license for the creating party to publish and distribute such work provided such party does not charge for it.

Policy added: Role-Based IP Ownership

Text changed:
  • Whenever a Role creates work product for which HolacracyOne would otherwise hold intellectual property (IP) rights, the Role which created that work product shall automatically be considered to hold an implicit Scope covering the created IP, unless: (a) the IP unambiguously falls within a governance-defined Scope of another Role, in which case such other Role shall hold such rights, or (b) the IP was created as a service to another Role via such other Role engaging a Service Accountability of the creating Role, in which case such rights shall cede to the Role triggering such creation, or (c) the creation happened via Individual Action outside of a Role, or by a Role which no longer exists, in which case such rights shall cede to the Circle from which such creation happened and be held by the Lead Link of such Circle unless or until further differentiated or transferred. This implicit Scope may be explicitly transferred to another Role outside of governance by a decision, communicated in writing to the target of such transfer, made by whichever Role then-currently holds such implicit Scope.Scope; provided, however, that for a transfer outside of the Circle containing the Role so transferring, approval must also be given, in writing, by the Lead Link of such Circle, and, if such Circle does not hold an explicit Scope clearly covering such IP, then by such Circle's Super-Circle's Lead Link, recursively.
Policy added:
  • Whenever a Role creates work product for which HolacracyOne would otherwise hold intellectual property (IP) rights, the Role which created that work product shall automatically be considered to hold an implicit Scope covering the created IP, unless: (a) the IP unambiguously falls within a governance-defined Scope of another Role, in which case such other Role shall hold such rights, or (b) the IP was created as a service to another Role via such other Role engaging a Service Accountability of the creating Role, in which case such rights shall cede to the Role triggering such creation, or (c) the creation happened via Individual Action outside of a Role, or by a Role which no longer exists, in which case such rights shall cede to the Circle from which such creation happened and be held by the Lead Link of such Circle unless or until further differentiated or transferred. This implicit Scope may be explicitly transferred to another Role outside of governance by a decision, communicated in writing to the target of such transfer, made by whichever Role then-currently holds such implicit Scope.

Policy changed: Forwarding Requests to Community Engagement

Text changed:
  • All Circle Members receiving or creating service requests to be fielded by Community Engagement @Customer_Relations shall forward them to the Service Request Queue in H1's customer information system.

Policy changed: Frequent Flyer Miles

Text changed:
  • Airline tickets purchased with citizen's Partner's frequent flyer miles for business travel are reimbursable at the airline's published lowest-available coach fare.

Policy changed: CE Cross-Link to Training Business

Title changed:
  • CE Cross-Link to Training Business
Text changed:
  • The GCC’s Community Engagement (CE) role shall be linked into Training Business (as a “cross-link”) and be entitled to participate in Training Business (TB) Governance, Tactical, and Strategy Meetings as a representative of the GCC’s CE function; Training Business may add scope items or accountabilities to the CE role within TB’s own Governance Meetings if such added items fall within TB’s own scope, but may not add anything beyond TB’s own scope nor amend anything defined by the GCC.The GCC’s @Customer_Relations Role shall be a Cross Link into @Training_Business.

Policy changed: Strategy Meeting Process

Text changed:
  • The Circle shall use the following process for Strategy Meetings:In lieu of the Lead Link specifying strategies, the Circle shall regularly engage in the following "Strategy Meeting" process to define strategies:

    1. Check-in Round
    2. Review Purpose, Scope, & Accountabilities of Circle
    3. Retrospective: Reflect & Capture…
      a) What was done as a result of the previous strategy
      b) Notable facts & events; external changes, opportunities, trends, data, etc.
    4. Record Tensions surfaced in retrospective
    5. Brainstorm to diverge (Mind Map): "What might make sense to emphasize operationally to address these Tensions?" (Capture output as phrases starting with -ing verbs)
    6. Distill Key Threads & Patterns from Brainstorming
    7. Discuss to converge: "What strategy should guide our decision making? What should we emphasize?"
    8. Lead Link proposes output(s); one or more strategies; process with proposal via IDM
    9. Closing RoundUnpack the Strategy: Brainstorm, what could change to better embody the new strategy; capture Next-Actions as-needed
    10. Closing Round

    The outputs of the Strategy Meeting Strategies shall use the form of "Emphasize x x, even over y", where x and y are both -ing verb phrases, and represent two connected poles of a polarity with both poles having value independently.

Policy changed: Current Strategy

Text changed:
  • All Circle Members shall apply the following strategies in their work for the Circle:All Circle Members shall align their prioritization and attention with the following strategies:

    Emphasize:
    - Documenting & Aligning to Standards
    over:
    - Developing & Co-Creating Novelty

    • Emphasize "Documenting & Aligning to Standards", even over "Developing & Co-Creating Novelty"