Netcees Leadership Team Update - October

namix · 10-30-2013, 11:39 AM

- - +- -+- -+-+- +-+-+-+- -+-+-+-+ -+-+- -+- -+ - -

Last Updated: 10.30.2013

4.0 The Roadmap/Punch-list:
The leadership team and P.A.C.T. owners will work to define and communicate the plan --- AND following some gap analysis, we will be looking for others to get involved. If you are up for getting down with this, start thinking about where and how you’d like to contribute… and Stay Tuned! :)

The overarching roadmap could be surmised as:

“PEOPLE --=> PROCESS --=> PRODUCT”.

We are working on the people, who will define the process, and improve the product.

Below are the high-level / high priority items for us to address to set the stage to get shit running real fluid-like. Individual priorities within the P.A.C.T. competency areas will be defined at a more granular by the respective owners of the areas.

FOUNDATIONAL ITEMS:
--=)> PHASE 1: Defining the Structure

Mission Statement - COMPLETE (10.13) .... "Creating a productive community of writers, for writers."
Leadership Agreement - COMPLETE (10.13)... to archive & communicate.
P.A.C.T. Ownership - IN PROCESS (10.13)
Role Definition/Gap Analysis/Needs - PENDING (11.13)
Leverage Model, Recruiting - PENDING (11.13)

--=)> PHASE 2: Implementing the Structure

Finalize Teams - OPEN

MISC ITEMS: For future prioritization
To capture high-priority/overarching needs... each P.A.C.T area will have their own plan, informed by the areas owners.

--=)> PRIORITY HIGH: Items for the next 2 months

P.A.C.T. Plan (by functional area)
PROCESS: Recruiting sign-off process
PROCESS: "Leadership Team" growth plan/advancement
ACTIVITY: 2013 wrap-up plan & preliminary 2014 schedule
COMMUNITY: Baseline expectations for the area (how it should be structured, how many mods are needed and where, what kind of permissions are needed)
TECH & PROCESS: User Role / Permission Definition (based on gap analysis / needs & recruiting process) --> informs how a new member progresses within the leadership team (from 'no permissions, but helping a mag' (for example) --> rankings/etc. --> mod abilities in certain forums/ etc.)

--=)> PRIORITY MED.: Notes/etc.

TECH: Web Analytics
TECH: 2014 Key Performance Indicators & Benchmark
TECH & PROCESS: 2014 Forecast

10-30-2013, 11:39 AM	#3
namix been that, done there. Join Date: Jun 2001 Posts: 2,259 Battle Record: 2-1 Accomplishments - OM HOF Rep Power: 85246655	- - +- -+- -+-+- +-+-+-+- -+-+-+-+ -+-+- -+- -+ - - Last Updated: 10.30.2013 4.0 The Roadmap/Punch-list: The leadership team and P.A.C.T. owners will work to define and communicate the plan --- AND following some gap analysis, we will be looking for others to get involved. If you are up for getting down with this, start thinking about where and how you’d like to contribute… and Stay Tuned! :) The overarching roadmap could be surmised as: “PEOPLE --=> PROCESS --=> PRODUCT”. We are working on the people, who will define the process, and improve the product. Below are the high-level / high priority items for us to address to set the stage to get shit running real fluid-like. Individual priorities within the P.A.C.T. competency areas will be defined at a more granular by the respective owners of the areas. FOUNDATIONAL ITEMS: --=)> PHASE 1: Defining the Structure Mission Statement - COMPLETE (10.13) .... "Creating a productive community of writers, for writers." Leadership Agreement - COMPLETE (10.13)... to archive & communicate. P.A.C.T. Ownership - IN PROCESS (10.13) Role Definition/Gap Analysis/Needs - PENDING (11.13) Leverage Model, Recruiting - PENDING (11.13) --=)> PHASE 2: Implementing the Structure Finalize Teams - OPEN MISC ITEMS: For future prioritization To capture high-priority/overarching needs... each P.A.C.T area will have their own plan, informed by the areas owners. --=)> PRIORITY HIGH: Items for the next 2 months P.A.C.T. Plan (by functional area) PROCESS: Recruiting sign-off process PROCESS: "Leadership Team" growth plan/advancement ACTIVITY: 2013 wrap-up plan & preliminary 2014 schedule COMMUNITY: Baseline expectations for the area (how it should be structured, how many mods are needed and where, what kind of permissions are needed) TECH & PROCESS: User Role / Permission Definition (based on gap analysis / needs & recruiting process) --> informs how a new member progresses within the leadership team (from 'no permissions, but helping a mag' (for example) --> rankings/etc. --> mod abilities in certain forums/ etc.) --=)> PRIORITY MED.: Notes/etc. TECH: Web Analytics TECH: 2014 Key Performance Indicators & Benchmark TECH & PROCESS: 2014 Forecast __________________ well fed.