CNM Event Organizer

From CNM Wiki
Jump to: navigation, search

A CNM Event Organizer (hereinafter, the Org) is an incumbent of the scholar-tier CNMCyber practice (hereinafter, the Practice) that The Economic Group has developed to practically introduce CNMCyber patrons to event organizing. The Orgs generally practice in organizing CNMCyber events or other meetings and conferences, including their preparation, moderation, and post-event activities. A CNMCyber event that the Org is about to organize, hereinafter, is referred as the Event.

The Orgs may develop either:

  1. Those Events that the Orgs are authorized to produce, or
  2. Those requirements that would allow hiring Careerprise contractors to develop those CNMCyber events that the Orgs don't produce directly, on their own. The Practice belongs to the first quarter of CNMCyber Bootcamps. This quarter's lessons are called Event Organizer Bootcamp (hereinafter, the Bootcamp); are designed to prepare the Orgs to that Practice.

The Practice is offered to those CNMCyber patrons who successfully pass CNM Event Organizing Exam at the end of Bootcamp's lessons. Successful completion of the Practice qualifies the Residents as KSA Certified Event Organizers.


Choice of practice

The Orgs can choose between:
By default, the Orgs choose those Events that suit them best. Since timing of some CNMCyber events cannot be moved, the Orgs can pick those events which schedule work for the Orgs.

Effort cycles

To perform effectively, the Org is encouraged to follow the DREPD cycles, particularly:
  1. Discover the needs via reviewing the CNMCyber Event-Driven Projects wikipage, other events on the market, and communicating with stakeholders.
  2. Research event requirements and available resources -- one can call it "researching this very knowledge base, similar events on the market, and, if anything is unclear, asking questions about what should be done and whether requirements to how it should be done are available" in order to prioritize and prepare assumptions for the those parts that are not covered by the requirements.
  3. Envision the event including all of its possible details; and, finally;
  4. Plan the design of the upcoming meeting.
  5. Discover the needs via facilitating the already designed meeting and commissioning the event records in order to restart the cycle.

How to start

Are you interested in getting started as the Org? Please follow a step-by-step instruction as follows:
  1. Succeed as a CNM Website Developer.
  2. Until Event Organizer Bootcamp is fully developed, briefly review the following wikipages:
    1. This very wikipage since it describes your event organizing Practice specifically,
    2. Event organizing since this wikipage describes management of meetings and conventions generally, not specifically to your Practice, but your Practice can correlate to it,
    3. Event 5W3H since your Practice will deal with event settings,
    4. CNMCyber event wikipage since it describes the events you are about to organize, and
    5. CNMCyber Event-Driven Projects since this wikipage describes those events that are authorized to practice with.
    You can also refresh your knowledge of the CNMCyber practice wikipage.
  3. Ask questions.
  4. At the CNMCyber Event-Driven Projects wikipage, pick up the event you would like to organize or advance.
  5. Present your pick during a CNMCyber This Week event, while stating (a) the event you picked, (b) what you plan to deliver, and (c) how much time you expect to work in order to deliver what you plan to deliver.
  6. Wait for CNMCyber Customer's approval or feedback to start your Practice this week or modify your proposal.


The Org's Practice touches many occupations. They may include one or more of the following:
  • Convention planning such as Meeting, Convention, and Event Planners as long as the Orgs plan events.
  • Document production such as Desktop Publishers, Information and Record Clerks, News Analysts, Reporters, and Journalists, and Technical Writers as long as the Orgs produce documents before, during, and after events.
  • Marketing such as Customer Relationship Manager, Market Research Analysts and Marketing Specialists, Marketing Managers, Online Merchants, Public Relations Specialists, Sales Engineers as long as the Orgs introduce upcoming events and their records to the public, as well as position them on the market.
  • Knowledge management such as Document Management Specialists, Production, Planning, and Expediting Clerks as long as the Orgs manage documents before, during, and after events.
  • Product design such as Business Analysts, Business Intelligence Analysts, Product Managers, Product Owners, Requirements Engineers as long as the Orgs collect stakeholders requirements and design events.


What Orgs produce

Most importantly, the Orgs are expected to acquire their new knowledge, skills, and abilities (KSA) and other benefits as their result of the Practice. As a part of CNMCyber Team, the Orgs shall produce two categories of measurable outputs:
  1. Internal documents that the Org who practice utilize in the organizing process and that the other Orgs may further utilize in their Practice as prototypes and training materials.
  2. Public deliverables that event consumers will obtain as results of the event.

Public deliverables

Attendees' experiences

Event records

Scripts, videos

Media footprints

Outreach materials

Internal documents

For the purposes of this very wikipage, internal documents refer to those documents which target audience differs from the general public regardless of whether those documents are available to the public or not. A particular Org who practices with a particular CNMCyber event shall use internal documents for development process; the other Orgs who will further work on other events, may use those documents as prototypes and training materials. As work products of the Orgs, documents shall be published at CNM Wiki.

Event wikipages

For the purposes of this very wikipage, event wikipages refer to those pages of CNM Wiki that describe CNMCyber events as parts of Careerprise Funnel and other products that the Event cycles are intended to create.
At CNM Wiki, any event wikipage belong to one of two groups:
  1. Event group wikipages describe common features of one group of events. CNMCyber This Week, CNMCyber Guided Tours, and CNMCyber Welcome Session wikipages describe series of events. The CNMCyber event wikipage describes common features of all events that the Orgs organize. Event group wikipages include deliverable requirements, organizational and technical documentation such as standing operating procedures (SOPs), minutes of the meetings, testing and other reports, etc. Those pages are listed at the "CNMCyber Events" category.
  2. Single event wikipages describe particular events. Category names of single events depend on the names of the series they belong to; for instance, "CNMCyber This Week" category, "CNMCyber Guided Tours" category , and "CNMCyber Welcome" category.

Project documents

Location of project documents such as project charter, asset register, competency register, stakeholder register, requirements traceability matrix, project scope baseline, project schedule baseline, project cost baseline, and acceptance criteria, as well as those communications, memos, meetings, etc. that are related to developments of CNMCyber events depends on predictability of events. Project documents for:
  1. Predictable events such as CNMCyber This Week, CNMCyber Guided Tours, and CNMCyber Welcome Session are published on their event group wikipages altogether with their standing operating procedures (SOPs). For the purposes of this very wikipage, predictable events refer to those meetings and conventions that have known agendas, descriptions, locations, speakers, timing, and titles.
  2. Unpredictable events are published on single event wikipages. For the purposes of this very wikipage, unpredictable events refer to those meetings and conventions which agendas, descriptions, locations, speakers, timing, and/or titles are not known at the moment when the Org starts organizing them.
Progress on projects to develop particular CNMCyber events is documented using the CNMCyber Event-Driven Projects wikipage. It belongs to the "Event Projects" category.


For the purposes of this very wikipage, events refer to meetings or conferences that are planned for special purposes. While organizing events, the Orgs are engaged in the What Orgs do activities.

Authorized events

Those Events that are authorized to practice with are listed on the CNMCyber Event-Driven Projects wikipage.

Outreach events

Outreach events, which are CNMCyber events organized to promote the Cyber, the Cloud, CNMCyber Team, technologies, needs, and services to outreach to current and potential clients and participants. Specifically to the Coords, the outreach products include CNMCyber This Week events, which are weekly meetings of the Coords who present (a) what they accomplished last week, (b) what they plan to do next week, and (c) what assistance do they need. The outreach events are normally published on the CNMCyber Meetup group.

What Orgs do

No final instructions exist. Blueprints below represent just suggestions, not strict directions. Based on timing of their Effort cycles, the Orgs' practice can be divided in sets of processes.

Whenever is appropriate

Whenever is appropriate, the Orgs shall:
  • Respond to possible comments of the Event participants.
  • Observe whether anything related to the Event goes not as it has been planned.
  • Raise the challenging issues and general observations in the CNMCyber Users space.
  • Update event wikipages at CNM Wiki whenever new data emerges, as well as CNMCyber Meetup, WorldOpp fb-page, and announcements when the Event 5W3H settings change.
  • Request (a) assistance of other members of CNMCyber Team when additional resources are needed and/or (b) changes to the series and/or CNMCyber event wikipages when new data from existing and/or new sources of data prompt so.
  • Report on progress of the event organizing using the CNM Event-Driven Projects wikipage; the report shall include proposed or implemented improvements to the Event.
  • Present the progress, plans and possible concerns during CNMCyber This Week meetings.

Preparing the Event

To prepare the Event, the Orgs:
  • In about 6 days and 23 hours before the Event, shall:
    1. Follow the How to start recommendations.
    2. Join the CNMCyber Users space.
    3. Create a single event wikipage for the Event at CNM Wiki. The Org should use the previous event page if your event is a part of a series.
    4. Make sure that the wikipage that the Org has just created addresses all of the required settings of the Event 5W3H framework.
    5. Identify the business need that the Event you are about to organize shall satisfy.
    6. Explore existing CNMCyber events, their documentation at CNM Wiki, other events related to career services that are available on the market and that address similar business needs.
    7. Compare existing CNMCyber events, their documentation at CNM Wiki, as well as other websites related to career services that are available on the market to detect opportunities to improve existing CNMCyber events.
    8. Decide whether the Org is changing anything to make the Event better.
    9. Publish the Event at the CNMCyber Users space, while implementing those changes that don't contradict the corresponding series and CNMCyber event wikipages.
    10. Check whether the particular Org has event organizer rights in the CNMCyber Meetup group. The particular Org should be able to edit events there.
    11. Publish the Event on the CNMCyber Meetup group unless the event has already been published as a repetitive event. Copying a similar event, if such event is available, tends to save time.
    12. Adjust the Event's URL to the[event-label]-[2-digit-month]-[2-digit-day]] format; for instance,
    13. Finalize the Event's settings; here, the Org shall improve them based on the Org's exploration of the market.
    14. Check whether the particular Org has event organizer rights on the WorldOpp fb-page. The particular Org should be able to edit events there.
    15. Publish the Event on the WorldOpp fb-page unless the event has already been published as a repetitive event.
    16. Adapt the Event's URL and other settings similar to the ones in the CNMCyber Meetup group.
  • In about 15 minutes before the Event, shall:
    1. Make sure that the Event is ready to go on.
    2. Enter the recording room.
    3. Login into CNM Talk as a "Record bot".
    4. Create the videoconference using CNM Talk.
    5. Make sure that the "Record bot" is a conference moderator; the squared letter "M" shall emerge on the bot's icon.
  • In about 5 minutes before the Event, shall:
    1. Switch on the recording function of CNM Talk.
    2. Start the recording function of another tool.
    3. Leave the created videoconference as a bot.
    4. Enter the created videoconference as the particular Org.
When (a) the Event is fully planned and documented at CNM Wiki, (b) its announcement is published at, CNMCyber Meetup, WorldOpp fb-page, (c) the videoconferencing is started as by the "Record bot" from the recording room, (d) the Event's recording in the recording room has been started, (e) the Org left the recording room, and (f) the Org has entered the videoconference as the Org, the Event should be considered as prepared.

Facilitating the Event

To facilitate the Event, the Orgs shall:
  1. Remember that the Org who organizes the Event is not only a participant but also the host of the event. Particularly, that means that the Orgs should mention that they act as simple participants when they do so.
  2. Begin greeting the participants at the time that is announced as the start time; that would indicate that the Event has been started on time.
  3. Present themselves and welcome the participants.
  4. Preview the Event to the participants, while stating its key points.
  5. Disclaim that the Event is recorded.
  6. State where the recording will be available after the end of the Event.
  7. Introduce new sections of the Event.
  8. Recognize the Event's speakers.
  9. Moderate the questions and answers (Q&A) part of the Event, if any.
  10. Indicate why CNMCyber organizes such events.
  11. Invite the participants to attend upcoming CNMCyber events.
  12. If some participants are not a part of CNMCyber Team, invite them to join.
  13. Close the Event while restating its key points, follow-ups, location of the recording.
  14. Leave the created videoconference as its participant.
  15. Enter the recording room.
  16. Login into CNM Talk as a "Record bot".
  17. Switch off the recording function of CNM Talk.
  18. Stop the videoconference.
The Event is closed when its videoconference is stopped.

Commissioning the records

To commission the Event's records, the Orgs shall:
  1. Create the Event's summary on the event wikipage of CNM Wiki.
  2. Publish the recording and the Event's summary at CNM Tube.
  3. Publish the recording and the Event's summary at the CNMCyber at YouTube channel. Please note that YouTube will not save any links such as to CNM Wiki and CNMCyber Meetup.
  4. Create the recording script of the meeting using the CNMCyber at YouTube channel; you don't need to edit the script.
  5. Publish the script on the event wikipage of CNM Wiki.
  6. Publish the link to the recording that is hosted by CNM Tube as an Event comment in the CNMCyber Meetup group.
  7. Publish the link to the recording that is hosted by CNM Tube as an Event comment on the WorldOpp fb-page.

recording function of another tool.


Everyone is welcome to apply. Attracting participants of event is not a part of the Org role. Usually, CNMC Event Administrator is responsible for that task.


An initiative group is currently looking for a "Meeting Organizer" to join our future team. This is an entry level position with opportunity for growth. The candidate is expected to organize one or more weekly meetings to discuss challenges, especially in recruitment, that the Community faces.
Job Description:
Primarily, organize one or more CNMCyber roundtables. In addition:
  1. Research and recommend new sources for active and passive candidate recruiting;
  2. Network and maintain relationships with key talent communities for short and long-term opportunities;
  3. Develop a sustainable talent acquisition and hiring strategy to meet growth needs of the Community;
  4. Find bottlenecks in the recruiting process and provide suggestions for improving the candidate experience;
  5. Develop a broad professional network of top talent;
  6. Stay current on market trends and competitors within our industry.
  1. Must be able to read, write, speak, understand and comprehend some level of English;
  2. High School Diploma or equivalent is not required; Bachelor's Degree or graduate degree may be an obstacle;
  3. Excellent communication skills and/or ability to acquire those skills are required;
  4. Must be able to work or learn to work as part of a team;
  5. Strong problem-solving and analytical skills and/or ability to acquire those skills are required.

What to expect

  1. If you succeed to state what valuable you would do for this project, you will get a job offer for 5 hours weekly. In this particular project, the job offer is more like a beginning rather than the destination point. Your skills would be assessed based on your performance, not "interviewing".
  2. If you succeed not to state anything concrete (let say, you say some nonsense similar to "I will deliver on this project by scheduling meetings and ensuring they are successful and their outcome can be felt immediately"), you can be offered to organize one meeting just to see that you are able to do something valuable knowing that you are not able to write.
  3. When you start working, you can expect detailed feedback. Questions, creative solutions, and taking risks are especially welcome. Under any circumstance, you will not be punished for taking a risk if your endeavor is undertaken within the scope of the project. Your charges will be disputed if you try to charge the financier for your personal stuff such as working on other projects, chatting to your friends on Facebook, etc.
  4. If you succeed to organize at least one meeting within a week, your contract will be extended. A bad meeting is better than no meeting at all -- no one is perfect, so is your performance expected to be.
  5. If you succeed to organize no meeting within a week, the contract will be paused, you will be asked why and, if no clear output is achieved, the your contract will be ended. This doesn't mean that we cannot work on other projects.
Please note that Gary aka "Igor" is widely available for soliciting additional requirements from him. All currently available requirements are posted at CNMCyber roundtable -- please visit the link. It is under constant development, but it reflects the current state of development.



The role was identified in early July of 2018. The job announcement was published on July 10th. Fourteen initial job offers were sent; two of them were never accepted and eight of contractors either have never started working or started in unacceptable ways.
On August 2nd, 2018, michael succeeded to organize the first meeting. On August 4th, Gary aka "Igor" sent the following message to every of four contractors working on the role:

Today marks three weeks that we have been collaborating on the project. Since we have already had the first meeting, it is successful. In a week, I will be evaluating your contributions to its success. If you don't organize any meeting and/or contributed to the wikipages, I will end our contract, while marking your work as success, giving all-star rating, and positive feedback. Meeting my expectations is not a challenge. You have met those and I appreciate your service. However, we need to keep going forward. I would like to see that you are able to move this project to the next level, which are development/brainstorming meetings every day and fully staffed Thank you so much for everything you have done!

See also

Related concepts

Related lectures