TZM Network Expansion Proposal .pdf

File information

Original filename: TZM Network Expansion Proposal.pdf
Title: Microsoft Word - TZM Network Expansion Proposal.docx
Author: Barret Vollmer

This PDF 1.3 document has been generated by Word / Mac OS X 10.8.3 Quartz PDFContext, and has been sent on on 01/04/2013 at 06:56, from IP address 66.108.x.x. The current document download page has been viewed 1291 times.
File size: 309 KB (20 pages).
Privacy: public file

Download original PDF file

TZM Network Expansion Proposal.pdf (PDF, 309 KB)

Share on social networks

Link to this file download page

Document preview

Presentation Transcript

Please note that some explanations in this document directly reference visuals
from the video presentation titled “TZM Network Expansion Proposal”. This can
be viewed at the following link:
Hello everyone, welcome to my presentation of the TZM Network Expansion
Proposal. This presentation was created to address some issues I’ve
observed within the volunteer structure of TZM, or it could be seen as a
general improvement proposal to the internal structure of the movement in
the effort ease the ability of “arm-chair” activists in becoming more
involved within the movement beyond the scope of social network and
online forum activism.
To start, I’ll summarize a few concerns that I have observed among TZM
activists of late regarding currently ongoing initiatives, the global chapter
structure, and overall productivity within the movement itself. Please note
that these concerns may either be true or false depending on the specific
situation, and I, personally, have not delved into a great amount of
research regarding these issues as I tend to prefer an outward focus in my
activism. However, recent and frequent posts within the Facebook and
forum communities have lead me to briefly alter my focus in trying to find a
solution amongst all the noise. Thus, in this slide, I only mean to highlight
my observations.
First, a lack of volunteer organizational structure, many desire an outlet to
volunteer and collaborate in an organized fashion, and while the Chapter
portal and structure, TZM blog, forum, social network, etc. have all made
tremendous strides towards this effort, many feel there is a need for
something more, something easier within which to work, communicate, and
Second, a need for transparency. In this case, I see transparency as an
overall ease of communication. Like I stated before, all existing projects
have made great efforts toward this goal, but many are still seeing difficulty
in communicating with those currently working in the movement as a
coordinator, a primary contact for an ongoing initiative, etc. People want to
know who to contact, what everyone’s working on, and what they can do to
help. In other words, transparency.
Third, a need for variety in initiatives as well as a variety in contributors.
The formerly mentioned lack of transparency is holding back new
volunteers from, 1.) Entering what projects currently exist as well as, 2.)
Stifling the creation of new ideas and new projects and their possible

fruition. To clarify on the first point, it is important to note that if anyone
really took the time to search for a means and thereby get into contact with
current project coordinators about assisting with an ongoing project, I’m
sure most would find that this is entirely possible. What this particular
need means to point out is the ease of accessibility of this process. That is,
it is much more likely that a person would be more so motivated to get into
contact with a project coordinator if the information was their right in front
of their face. Make it so it’s another few clicks and a Google search away,
and the person is less likely to consider getting involved. As for the second
point, the transparency that is currently lacking in assisting with the ease
of creation of new projects and ideas is that of a communication medium
through which to introduce new ideas, potentially gain support, and start a
new project with that support. This lack of a central medium through which
to facilitate this growth is what most have sited as a primary cause for the
lack in variety of new initiatives and contributors.
Fourth, to go off of this idea of variety and the central medium through
which its growth is facilitated, it is important to consider extending
transparency not just among those who are already highly involved, but
those who desire to become involved and want to get their credentials and
interests out there for people to see. A searchable database of sorts has
been proposed by a few activists where potential volunteers can list their
experience, what they’ve done in the past, and what they’re currently
interested in or pursuing as far as raising awareness of the ideas TZM
And finally, a need for accountability and respect among volunteers and
those working hard towards a noble cause through which they are receiving
no monetary compensation. As of now, there seems to be little social
pressure to encourage volunteers to follow through with what they say they
are going to do, to complete certain tasks within a reasonable timeframe,
or to even continue their work all together. This phenomenon’s existence is
obvious when you consider our current social standing in the zeitgeist.
Since we have all yet to reach a system of global access abundance, and
money is still the primary facilitator of our society, we cannot rely on
having the respectful, ever-committed, ever-dedicated mind-set of our
volunteers that one would see ideally happening in an NL/RBEM to uphold
the integrity our current volunteer social structure. People want to see
dedication and commitment, and to be able to allow others to treat them
with the same respect and dignity. However, this is stifled by our current
overbearing priority to survive by way of making money. Therefore, many
have suggested a system of accountability that will help our volunteers to
establish and follow through with generally accepted social standards and

So, let’s add another form of consideration to the previous concerns. Or, if
you prefer, let’s even forget about all those issues and focus on what
activists in TZM want to see produced from this movement. As a means to
our end goal, what aspects can we incorporate into the movement to allow
it to flourish into something that truly shifts our social paradigm towards
that of a scientific worldview?
First and most obviously, we’d like to see an overall productivity. In this
instance, we want to see projects from volunteers that, upon their fruition,
can directly contribute to our cause.
Second, to truly exhibit efforts toward what we call a “leaderless
movement”. Open-source contributions are very important part of this
aspect. But it becomes very difficult to facilitate these contributions unless
there is some sort of underlying organizational structure to keep things
afloat. We want to make opportunities to contribute so abundant that no
one can ever say they have nothing to give. We want to allow people to start
new projects, give input to currently existing projects, and to grow and
prosper with ease. With as little roadblocks and as little frustration as
Third, we want too see collaboration with groups and movements outside of
the TZM label that are helping to contribute to the paradigm shift we seek.
We don’t want to be closed in completely, as that would certainly defeat the
purpose of spreading awareness.
So now let’s look at what the movement itself is made of, volunteers. What
attributes of working towards a transition are going to help maximize this
productivity we seek amongst the volunteers that literally are the
movement itself? What is going to keep people motivated, inspired, and
decrease the movement’s propensity to lag or potentially dissipate entirely?
Here’s what one report suggests to be the most primary incentives to
volunteer. You may find most of these incentives to be quite obvious. What
has yet to be realized in this movement, however, is in what way we can
build an incentivized system that allows for the realization and output of
these attributes automatically. What can we do to highlight and showcase
these incentives to volunteers to create continual growth?
So, we come to the final area of assessment as we take a look into what
successes within TZM have already created a vast amount of this previously

mentioned productivity that we seek. These projects are great examples of
people becoming their own leaders, taking the initiative, and expanding the
depth and quality of the movement over a surprisingly short amount of
time. And as we connect these successes with the concerns and
observations listed in the previous slides, the conclusion we can all agree
on is that we want more of this. We want lots more. We want everyone to do
this, we want everyone to want to do this, and we want to make it easy for
everyone to do this. The goal here is to help facilitate this vast amount of
potential, while keeping all previously mentioned insights and observations
in mind.
Thus, we have the idea for a proposal to achieve this very goal. A user
interface expansion to the already created TZM Network. For those of you
who are unfamiliar with this project, please go to it and join it. You can find
it at It is essentially a free social network, similar in
construct to Facebook, but specifically made for TZM/TVP activists. It is
yet another wonderful example of the ability of volunteers and activists
within the movement, and a great base upon which to build an all new user
interface to cater to the needs of a project team coordination structure.
And just a quick aside, this new logo I have created was simply for the use
of visualizing TZM Network, upon the fruition of this expansion project,
becoming a more primary, involved and interwoven aspect of The Zeitgeist
Movement itself. It certainly does not have to be used as the primary logo
for the website, I only created it as an artistic expression. So, I have posted
it for anyone to use as they wish on the Zeitgeist Media Project page.
To explain my proposal, I will break the explanation down into 5 sections
and will attempt to describe my vision as concisely and completely as
possible. Please note there are certain details within this proposal as far as
user functions and specific layouts that I will not delve into to avoid tedium
in viewing this presentation and to save time explaining an idea that could
potentially be altered or scrapped for something better should more input
be received.
The first section of this proposal will cover the basic aspects of the Project
Coordination user interface. Much like creating pages on Facebook, this
interface will hopefully be a useful extension with a familiar layout.
The second section will describe how this Project Interface will expand into
individual user’s TZM Network profile pages.

The third section will go over the expanded search utility that will help to
maximize connectivity between those who want to get more involved in the
movement and those who are already involved and are looking for help.
The fourth section will outline the overlaying project structure and how it
will assist in expanding the ideas and projects within TZM.
And the final section will cover the built-in accountability system and how it
will allow users and coordinators to optionally set social standards or
benchmarks for their team as well as hold their peers accountable for these
standards which will hopefully help alleviate the issues that arise when
deviations occur.
The first place to start when describing this new user interface is the
project coordinator, or the originator of the project. When someone has a
new idea for a project, they will have the option to create a new “Project”
page. This will be much like starting a “Page” on Facebook, but altered a
bit to cater to the needs of facilitating a specific set of tasks to achieve a
goal. Upon creating the Project, the creator is automatically set as the one
Administrator and has the option of inviting others to have the same
administrative privileges. For the sake of consistency, we will refer to
anyone that has administrative power over a project as a coordinator.
The coordinator then has the option to fill in The Project’s objective or
objectives, phases, categorizations, and tags. This would be most similar to
filling out the “About” section of a Facebook page or group, but becomes a
little more involved when inputting the categorizations and tags of the
project. Categorization will break down into a few sections with a set of
predetermined options from which to choose to best describe the type of
project that’s being created. These sections could hypothetically be
limitless in number, but we’ll stick to the basics for now. Examples of these
categorization sections could include the locality of the project (so whether
or not it’s local, regional, or worldwide), the workplace of the project
(whether it involves mostly online work, physical labor, or both) and the
pace of the project (This would be the overall hours per week the team
members are expected to contribute their time).
Then there is tagging. Much like categorization, this will seek to best
describe the nature of the project using terms that are little more difficult
to set as predetermined options. Ideally, the coordinator would have the
option of inputting two or three primary tags that would best showcase
what the project is all about. For example a project that seeks to create
instructional videos for our friends at Open Source Ecology would have the
primary tags Open Source Ecology, Video Media, and Education. The

coordinator then has the option of adding as many secondary tags as they
see fit. Both the categorization and tagging processes will help to narrow
down searches for those interested in working on specific project types.
So after the coordinator is done describing the project, they will now have
the option of creating tasks while simultaneously inputting the human
resource or resources needed to complete these tasks. Tasks can range
from being very specific with a low time frame for completion to being very
broad with a larger or unlimited time frame. This is all dependent on the
preference of the coordinator. There will be an input section to describe the
task, an input section to set the time frame for completion (if any), an input
section to describe the skills, experience or profession of the person or
persons needed, and a section for tagging the task (much like tagging the
project) for search specification purposes. In essence, creating tasks will
not only facilitate the work needed to reach the project's objective, but it
will also act as a primary tool for project recruitment. The breadth of use of
this tool will become more apparent as we move through this presentation.
New tasks and their respective human resource needs would appear on the
Project’s page as well as being included in a Craig’s list type searchable
database which I will describe in more detail later in this presentation.
Now lets take a look at what a regular user who is interested in helping with
a project can do to get involved. Users will be able to seek out new projects
and tasks through the project search utility, social encouragement from
their peers, and through posts and updates they will see on TZM Stream.
Once they have found a project that they are interested in helping with,
they can subscribe to the project, which would be exactly the same thing as
“Liking” a Facebook page, so that any wall posts or newly created tasks or
progress updates will be posted on the user’s TZM Stream and can
optionally be set to stream into the user’s notifications.
To actually get involved and officially become a project team member, a
user would have to submit themselves for task assignment. This is simply
done by clicking the “Submit for Assignment” button on the particular task
the user is interested in helping with. Once this is done, a notification will
be sent to the coordinator of the project, whereupon they would be able to
visit the candidate’s user profile to review their credentials, message the
user for more information or any other interview-like questions they may
have, and finally, if they find the candidate to be suitable for the task
assignment, accept the candidate’s request. This will automatically make
the user an Active Team Member of the project, which will allow the user
access the Project Team Page, which I will explain in a moment, it will send
notifications to all coordinators and team members that a new member has

joined the effort, and, if the task only requires one person to begin, the task
will automatically switch from the “pre-assignment” phase into the “in
progress” phase, which will start the timer countdown to the deadline for
completion if a designated time frame was inputted when the task was
created. If the task requires more than one assigned team member to
begin, the task will remain in the “pre-assignment” phase until the quota is
met. Once the team member begins working on a task, they have the
option to post progress updates on the task, which would be as easy as
commenting on a Facebook post. These progress updates will be available
for public viewing, and will be a great way to let everyone know how the
project is coming along. Once the task is completed, the team member
submits for acceptance of completion, which is then verified and accepted
by the coordinator. Once a task is verified as being completed, it will
automatically switch into the “completed” phase. The team member, left
with nothing to do, will then have 30 days to find another task to assign
themselves to in order to remain as an active team member of their
particular project. If 30 days pass with no activity, they will cease to be an
active team member and their work on the project will be recorded in the
history section of their profile. This user will always have the opportunity to
renew their active team member status should they be assigned to another
task in the future. Please also note that any user has the ability to be a
coordinator or an active team member of any number of projects at the
same time, with the limit of the number of current projects set to how well
the user can manage taking on multiple responsibilities at once.
Now, to describe this Project Team Page that I just mentioned, I will first
describe the Project Public Page, as they will be very similar in form and
function. The Project Public Page is essentially how the public, meaning
anyone who is not a project team member, will view a particular project.
The page, as I have mentioned before, will be formatted much like a
Facebook or a TZM Network Page with a few added details to maximize
At the top of the main page you will see the project’s picture, a brief
description of the project, the name of the creator, and link to the project’s
reviews that will house the reviews of the project itself and of the creator.
Below this general information heading, you will see the wall. The wall will
be for coordinators to post general project information such as progress
updates and anything else they would like to post to promote their project,
and it will also be for general TZM Network users to post comments,
criticisms, encouragements, questions, anything they would like to post
concerning the project.

Next to the wall will be the Task Stream. The tasks stream will allow any
TZM Network user to see what is currently being done with this project,
who’s doing it, and how far along they are with their efforts. It will be
broken up into three sections respective to the task “phases” I previously
described. The first section will house all “pre-assignment” phase tasks,
which will be good for users interested in getting involved in the project to
look into. The second will house the “In Progress” phase tasks, and the
third will house the “Completed” phase. For all the tasks in the 2nd and
3rd phases, users will be able to see who is assigned to the tasks and any
progress updates posted to those tasks.
In the “about” portion of the Project Public Page, users will be able to view
all general information about the project as well as all current and past
project coordinators and team members. Having all of this information
available to the public will be crucial for maximizing transparency and
avoiding confusion.
Now, the Project Team Page, that will be exclusively available for project
coordinators and active team members, will be exactly the same as the
Project Public Page with the exception of the wall. The wall, in this
instance, will be solely for the purpose of internal communication and will
not be available for public view. This is not meant to be for the purpose of
hiding anything from others, but only to allow the active team members a
familiar and easy way to communicate information amongst themselves
that would otherwise be irrelevant and tedious for public viewing.
As a conclusive note to this section, the layouts presented here are meant
to present a very basic framework. The visuals I've created are specifically
to ease the process of visualizing my explanation, and are in no way
complete or drawn to scale. I expect the format will change and evolve
overtime if it is actually integrated into the current TZM Network page
layout and that new features will be added as more input is received.
Let's take a look at what changes will be seen on TZM Network user’s
profile pages should this expansion be made. The first thing you're going to
notice is the coordinator or team member designation that will appear near
the profile picture. These symbols will tell what the user's current volunteer
positions are. If they held a position in the past that they either no longer
hold or haven't had any activity within in the past 30 days, those
designations will be noted in their history, which ill get to in a moment.
There will be a difference between the symbols for project creator, project
coordinator, sub-project coordinator, and active team member. I will

explain these sub-project designations in a later section. Users will be able
to click on these symbols, taking them to the "info" section of their profile
to see what this particular person is currently involved in. If, say, a person
may be working on more than one project as a team member or
coordinator, the number of projects they are currently involved in will
display just below the designation symbol.
The second thing you'll notice will be on the wall of the person's profile.
Along with the typical social network activities, you will see any live updates
pertaining to project developments. For instance, if the person created a
project, this will be noted, if a person has updated information on the
project, whether it be changing the categorization, posting a task, or
posting on the project's public wall, this will be noted. If the person assigns
themselves to a task, posts an update on the task, or completes a task, this
will be noted. Other accountability notifications that will be explained in
more detail later, such as if a person missed a deadline, will also be noted.
When we move into the info portion of the user profile, you will see a
Current Project Activities section. This will house all information pertaining
to what projects they are currently involved in, what their designation is
with those projects, what tasks they are currently working on, and their
most recent updates to these tasks.
You will then see a Project History section, which will house all information
pertaining to previous work done on TZM Network Projects in a similar
format to that of the Current Project Activities section. Now, if they do
exist, you will also see links next to the work done for a review of this work
as well as any "unsatisfied responsibilities". I will talk about this in more
detail in the accountability section of my presentation.
Finally, the "interests", "experience", and "education" section of a user's
profile will seek to serve a function that will go one step further than just
being there for informational purposes. Users will be allowed to add tags to
these sections of their profile, enabling a connection between them and the
human recourse needs posted by project coordinators. Thus, when a user
is searching for a project in which to get involved, the top recommended
matches based on this information will show up first. That is, the project or
task that generates the greatest amount of matches among inputted tags.
This seems to be an ideal time to transition into an explanation of the new
enhanced project search utility.
This database and utility will serve as a way for project coordinators to find
or recruit potential team members and fellow coordinators, and for

prospective team members to find projects and tasks that cater to their
experience and interests. The ease of the search will be facilitated through
the various tags inputted by the coordinator to categorize projects and
tasks and the tags inputted by regular users in their interests, experience,
and education sections of their profile. The overall matches made between
those tags will create recommendations that will show at the top of the
search page upon entering specified inputs into the utility.
So let’s go over some examples. Next to the main search bar, their will be
the option to select the "Project" search by clicking on this symbol. Once
the user has reached the project search page, they will enter a maximum of
3 specification inputs to start their search. The first will be what they're
looking for. The choices for this input will include potential coordinator,
potential team member (these choices would obviously be most useful for
coordinators looking for help), or potential projects and potential tasks,
which would be used for those who wish to find something to work on, and
the final option would be a general search.
So let’s say we’re a coordinator named Bob looking for team members to
help out with a project. The second input would be for what purpose are
they searching for this person. These options would depend on the user
doing the search, as the first options the user would see would be whatever
projects or tasks they themselves have created, are currently coordinating,
or are currently an active team member of, if any, with the final option
being a general search specified by the first input. So, for example, one
could potentially search for a prospective team member to assign to a
specific task that you have created by entering only two inputs. Here, we’ll
say that Bob wants to search for someone to match the experience
required to perform Task 1 of Bob’s Project. The subsequent search results
would be the highest matched people based on the tags entered when
creating the task and the tags entered in the various users' profile
If the user has not created or is currently not coordinating anything and
still wishes to search for potential coordinators or team members for
something they may want to create in the future, then they would default to
a general search, whereupon they would enter the third and final input
consisting of key words or tags to describe what they are looking for. Bob is
currently participating in two projects right now, but he’s going to go ahead
and click general search anyway to see who he can find that is interested in
Solar Power. The resulting user data matches anyone who has Solar Power
written into their about section of their profile page.
If the user enters prospective projects or tasks as their first input, the
search results will have already automatically generated as the best

matches to whatever tags and info they have in their profile information.
However, quite similar to what Bob did when he searched for team
members interested in Solar Power, one would also have the ability to
override these results by entering inputs into the general search bar should
they wish to search for a project or a task beyond their own previously
entered interests and experience. Bob lives in New York City, so he wants
to see if he can find any projects specific to that area. Thus, the following
information results.
Finally, if Bob wishes to search for anything New York City, he will choose
“General Search” as his first input, enter in New York City, and thus have
the results for all matching Coordinator, Team Members, Projects, and
Tasks for that location.
In addition to this enhanced project search utility, I would also propose
occasional notifications or emails to be automatically be sent to users that
would act as recommendations or encouragements to look into a projects
or tasks that match their profile information. These encouragements would
obviously be more frequent for those users who have yet to hold or are not
currently holding any project designations. These notifications would
generate automatically upon creation of a user account, but would be
capable of being turned off through the user's notification settings.
Now that we've gone over all the basic interactive utilities in this expansion,
I would like to talk a bit more about the project structure. The structure in
this proposal, similar to the interdisciplinary team structure often
discussed as being a part of an NL/RBE, seeks to maximize the potential
and advantages of both the top-down and bottom-up approaches to social
organization given the currently available technical resources and abilities
of the activists in the movement. While a bottom-up approach is necessary
for organic growth of new ideas, the advantages to top-down coordination
are also quite apparent, given that the coordination's application to a team
setting does not overstep the boundaries that, upon overstepping, will
inhibit the creation and growth of new ideas. This is what the TZM network
project coordination interface will seek to do by expanding the options for
integration and creation of ideas as much as possible, thus creating a
"Multidimensional" expansion of progress. The most apparent of these
features, as I have already explained, would be the familiarity and usability
of creating a project page. This will greatly ease the process of creating
your own initiatives, gathering support, and achieving your goals, which will
hopefully jump start an avalanche of progress among those currently more
or less stagnant activists and be a key contributor for new bottom-up ideas
to emerge and grow within the movement.

Another feature that I wanted to include here could be what would be called
a branching out I projects into separate sub projects. This is where the
Sub-Project Coordinator designation I mentioned before comes into play.
For example, say Jimmy Johnny Willy Philly, otherwise known as James
Phillips started a TZM Education Project and a member of the team wanted
to split into a focus group that would focus specifically on creating
educational material on the subject of computer science. This team
member, after discussing and agreeing upon this plan with James would
then be able to create a brand new sub-project page with a more specified
purpose, but still residing under the affiliation of the TZM Education
Project. The team member that created this sub-project would request
affiliation with TZM Education Project, whereupon James would accept,
thus creating the affiliation. The broad range goals and categorizations of
the main project would automatically carry over to this sub-project, while
also allowing for an additional set of inputs to be entered to specifically
describe the sub-project. The creator would also henceforth be known as
the coordinator for this sub-project, thus dubbing them the designation of
sub-project coordinator.
The first and foremost advantage that will come with this branching off
process will be that the original coordinator, James, will be able to delegate
a portion of his responsibilities to another coordinator. This will be
especially effective when a project has multiple coordinators with multiple
initiatives all under the same project page. Creating these branches will be
able to simplify the process without destroying the overall integrity of the
original project's intentions and goals. Upon the creation of these subprojects, TZM Education Project page will now be able to optionally host all
their sub-project's respective real time task update feeds on the main
project page. The sub projects will also be able to host the main project's
task feed as well. As with most features on this system, this will be optional
depending on the coordinator's preference of maximizing transparency.
Finally, all main project and sub-project participants will have access to
both the main and sub-projects' internal team communications interface.
Each individual user also will have the option to receive notification updates
from each of these projects as they choose. Any coordinators of the main
project will be able to send out messages to all participants in the main
and sub-projects. Being a coordinator of the main project will allow
administrative powers in all branches. Being a coordinator of a sub-project
will only grant administration powers to that specific branch. Affiliations
and additional main project coordinators can only be added and un-added
by the original creator of the main project.

As a conclusive note to this section, anyone, whether it be a main
coordinator, a sub-project coordinator, or a team member has the option to
de-affiliate from a project and pursue their own interests as they see fit.
This, with exception of the original creators of the project or subproject, is
possible without any essential requirements. In the case of the original
creator, they either have to find someone to replace them and have that
person accept the responsibility, or they have the option to leave the
project stagnant until someone fills their position, or delete the project all
together. Deleting a sub-project all together is not a power granted to a
sub-coordinator, though. Once an affiliation is made, that power only lies
with the main project creator. Any transition process such as this is
expected to be done with a level of integrity and respect for the people
affected. Any process that fails to consider this courtesy to the many
people who are working hard towards a noble cause will witness the effects
that ensue from the built-in system of accountability, which brings me to
the next portion of the presentation...
In speaking on accountability, it should first be noted that creating a
project, coordinating a project or sub-project, or submitting oneself for a
task assignment is expected to require a respectable level of dedication
and commitment, of which is judged by the collective group-mind based on
the current commonly held social standards. Thus, when creating an
accountability system within this new organizational structure, we must
allow for the simplest and easiest facilitation and implementation of these
constantly changing social standards. There will be no imposing of any set
of standards of any kind. Rather, the user, coordinator, and team member
will be allowed to optionally implement standards based on their personal
preference, while at the same time realizing that a failure to follow through
with these standards may result in reasonably assessed, socially derived
criticisms and feedback. Don't let the wordy explanation fool you, though,
as the proposed process is actually quite simple.
First, coordinators will have the option to set a timeframe for the
completion of any task they've created. Once a user has submitted and
been approved for assignment of a task, the time frame will begin counting
down, allowing the coordinator and team member to see the time left for
the task to be completed as well as the time and date for the deadline of
completion. The team member, having knowledge of the allotted time
frame before submitting themselves to the task, will be held responsible by
the coordinator and his peers for completing the task before it
expires. Another added responsibility that will come standard with all
assigned tasks will be the simple requirement to post a progress update to
a task at least once every 30 days. These posts will not have any built-in

minimum word or letter requirement; it merely just is there to indicate that
the user is still actively working on the task.
Not posting regular progress updates will result in a loss of assignment of a
task, and, if this is the only task the user is currently assigned to, a loss of
Active Team Member status. In Addition, failure to complete a task before
the deadline as well as, in the case that there is no deadline, failing to post
a progress update to a task at least once every 30 days will result in an
"Unsatisfied Responsibility" being added to the user's history section of
their profile. This has the potential to reflect negatively on the user's
commitment when viewed by other coordinators looking to work with them,
but there are couple ways that a user can have the deviation expunged
from their profile.
Anytime after the "unsatisfied responsibility" is posted on a user's profile,
the user has the option to write an official statement to appeal against their
deviation. This can be anything from the user ran out of time to the
coordinator wasn't responding to attempts at communication, etc. When an
official statement is posted by a team member, the coordinator is notified.
Now, the coordinator can respond to this by either extending the timeframe
at any time before or after its expiration, or they also have the ability to
"forgive" any unsatisfied responsibility outright should the fact that the task
isn't completed no longer be an issue. Both of these actions will erase the
"unsatisfied responsibility" from the user's history. Now, it is expected that
any coordinator who creates these time frames will alter or extend them
sparingly. If the coordinator finds themselves extending time frames more
often than not, it is suggested that this coordinator either extend their
average given time frames or discard their use of the timeframe function all
together to avoid further confusion. Too much confusion with this process
from the coordinator's end could end up having a negative effect toward the
coordinators review assessment, which I will get to in a moment. If, say,
the coordinator is unresponsive to the appeal, the user has the option to
suggest that his friends like the appeal. If the appeal gets, say, 30 likes,
then the deviation will be erased. That number could change subject to
further input.
Finally on to reviews. Peer reviews will be another central part of assessing
one's ability to work in a respectable and committed manner. These will be
more applicable to coordinators and projects because, even though
coordinators can assign themselves to tasks in different projects, their work
as a coordinator should also specifically be assessed to maintain
accountability. So, all TZM network users can post a review of their peers'
work in the TZM Network Project community. If a user holds a number of
different positions, one has the option to review their performance in the

context of each individual designation, or the person as a whole. Obviously,
in these cases, it would be better for fellow active team members to review
a user's work in that specific project in order to specify the most relevant
context and therefore create a more accurate review. Users will also have
the option to review projects as a whole. While coordinator reviews will help
the coordinator to be better on a personal level, project reviews will help
coordinators gauge the performance of their own project and whether or
not they need to make structural changes outside of their own personal
Reviews can be viewed by anyone at anytime, and be voted up or down
based on how accurate and complete one feels the review to be. The review
with the most positive votes will be the front most review when viewing at a
user's review stats. Review stats for users and projects will show unweighted averages as well as weighted averages, which will give a higher
weight ratio to reviews that have the higher amount of positive votes.
As far as the scale and criteria used to determine a review score, the user
would first write an overall review in their own format, and then rate a
specific set of criteria on a scale of one to ten that would average out to
create an overall review score. The set of criteria used is something I would
love to leave up to the users to determine by themselves, but I am finding it
difficult to develop a format that would allow for such input with making
the review process too arduous. I am very open to suggestions on how this
can be done.
In the mean time, ill stick to five predetermined criteria for each
designation, which I am also very open for input in determining, and an
option to fill in any additional "other" criteria as the user sees fit.
For projects:
1.) Transparency
2.) Structure balance/fluidity
3.) Team member satisfaction
4.) Pace
5.) Relevance to progressing toward a sustainable future
For sub-projects:
1.) Transparency
2.) Structure balance/fluidity
3.) Team member satisfaction
4.) Pace
5.) Relevance to progressing main project’s goals

For project and sub-project coordinators,
1.) General respect for their peers
2.) Accessibility
3.) Encouragement
4.) Accountability
5.) Quality and fluidity of task creation and assignment
For active team members:
1.) Respect
2.) Accessibility
3.) Quality of work
4.) Accountability (holding peers accountable)
5.) Pace of work
As a conclusive note to the built-in accountability system, everything that
has to do with this system is optional, with the exception of the
requirement to post progress updates to maintain active team member
status. This is meant to be something that is used when needed. I can
imagine it may be something that is used more often in the beginning as
everyone is getting used to the system and still in the process forming a
generally accepted set of social standards. As this set of standards
becomes more and more self-evident, I can see the accountability system
losing relevance and eventually phasing itself out. Until then, volunteers
taking time out of their lives in the monetary system to better the world will
likely need a little push to hold them accountable to their commitments
and a reasonable level of respect.
So I think that pretty much sums up the basic idea behind my expansion
proposal. While many specifics and details were purposely left out due to
time, I hope you all see the merit and viability in adapting this online
interface into the movement. If you didn't, let me quickly summarize the
advantages to this system and how it will help this movement move. Yes,
it's a rather simple idea. You could generalize it as merely tacking on the
task system to the already existent page creating function. But my hope is
that it will be much more than that, that this interface will grow in usage
and quality of usage as a result of further input and new ideas. My hope is
to provide an immediate place for those interested in getting involved with
the movement to come see what the movement is doing to be the change it
wants to see and to be inspired to do the same.
So, first, we're creating a social network to facilitate not only basic social
interaction, but a social participation and contribution structure. In this
effort, we are interweaving the best things about social networks, sharing,

liking, and commenting with the progress creating attributes like
coordinating, encouraging, and achieving.
Second, we are easing the process of connecting and communicating
through the project search utility, project page interface and user profile
expansion. Additionally, allowing all users access to coordinator and team
member information and task progress updates will help increase
transparency, thereby increasing productivity.
Third, through the multidimensional expansion project structure, we will
see an ease in the ability to make individual contributions to projects that
are in need of new talent/insight, as well as the ability for ground-up
projects to emerge and gain momentum.
Forth, we are allowing participants the means to hold each other
accountable while also providing a means to make amends and be forgiven,
which will serve to create a healthier, respectful, and therefore more
productive online environment.
And, as a final note on initiatives and organizations outside of TZM that are
looking for a way to facilitate their various volunteer based projects, we are
creating and environment specifically for that purpose. Anyone can join
TZM Network and use this free utility as a means to facilitate progress
within their organization, and, at the same time, engage with TZM activists
in an online social environment, sharing ideas, expanding the boundaries
outside of the TZM community, and truly becoming a global movement.
It seems most appropriate in an environment of critical thought to finalize
this presentation with some possible concerns with this proposal as well as
some questions to ask ourselves.
As for concerns:
First, Healthy interaction within this system will be dependent upon
commonly recognized social respect standards, which leaves the risk of
outliers that may have an effect on the integrity of the system. However,
much of these instances would likely be systematically phased out as a
result of coordinator and team member reviews holding participants
socially accountable. It is also my positive outlook and general experience
with people who really want to help with this movement and the ideas that
it promotes that these types of instances will most likely not arise. I think,
generally, people will see the advantages to being respectful to one another
considering they all share a common overlaying goal of progress and
prosperity and all are doing so on an optional volunteer basis. However,

because my assessment and dismissal of this issue is rather subjective, I
felt it worth acknowledging as a real and possible issue here.
Second, favoritism among a common number of reviewers over a select
group of users could occur, which would subjectively drive a certain bias
toward a select group of people within the system, although I do not see
this as likely in such a highly populated interface where opportunities for
development are too vast for only a few to succeed in all areas of interest
and gain social favoritism for their success. Again, not likely, but worth
mentioning here.
I'm sure there are more concerns to list here, but I want to move on to
some questions I would like to ask all of you viewing this presentation.
First, should we seek to move forward with this project, how can we
integrate the chapter structure into this open-source project type system?
Is it even possible? If so, would it even be a good idea?
Second, the amount of development abilities and skills and time it will take
to actually have this be a fully functioning part of TZM Network is
something I have no knowledge of. This question I will leave to the TZM
Network development team and other website developers interested in this.
I am only one person, and I have no advanced coding and software
development skills whatsoever. So, that's certainly something to discuss.
Lastly, does there exist another online interface that more or less mimics
the function that I've described in this proposal that we can use in some
form another in place of this idea, and am I living so far under a rock that I
just don't know about it? If so, please let me know, and I will go cry for a
few days when I've realized I've wasted all this time creating this
All right, I think that concludes this presentation. I have started a thread on
TZM Blog for discussion of this presentation found here:
I have also created a Facebook page here with the address Please visit this page and
provide your feedback, criticisms, questions, and discussion, and I will do
my best to answer anything that I can.

In the possible happening that this is a good enough idea for developers to
begin working on it, please feel free to contact me via this Facebook page
as well if you need any help with graphic design. As you can see here, that
has been my primary focus thus far in the movement, so I am more than
willing to help out in this area as much as I can.
Thank you for watching this presentation. I hope it has presented some
good ideas about how we can move forward as a movement and as a
civilization. Keep thinking, keep communicating, keep collaborating, and,
as always, do as this guy does.

Related documents

tzm network expansion proposal
ecc applications 2015
2 i 70 title vi complaint
joinjob offerjune 2019
briefy cover letter 1
zinc networktechnical responsefinal

Link to this page

Permanent link

Use the permanent link to the download page to share your document on Facebook, Twitter, LinkedIn, or directly with a contact by e-Mail, Messenger, Whatsapp, Line..

Short link

Use the short link to share your document on Twitter or by text message (SMS)


Copy the following HTML code to share your document on a Website or Blog

QR Code

QR Code link to PDF file TZM Network Expansion Proposal.pdf