Activity Calendar LOTE#5

Workspaces LOTE5 “Fail / Unfail”
, , ,
1

This is a 2-months overview of a fairly ambitious masterplan to unfail LOTE5:

  • venue set in 4 weeks,
  • 8 ambassadors and speakers engaged in 3 weeks,
  • 8 partners (media, allies, etc.) + 1 supporting partner on board in 5 weeks,
  • 2 campaigns (development + ?) in 6 weeks,
  • catering and supporting activities set in 6 weeks.

​All accompanied by an updated budget, on-the-go wikis on partners/venues/event programme, community calls, community engagement and proposal writing.

LOTE5 timeline.jpg960×720 65.2 KB

I suggest we create a detailed plan every two weeks (see below). All tasks are open to any person in the community up to help. As in past LOTEs, LOTE5 tickets aren’t for sale but you can get one by completing one or more tasks (in sales/fundraising efforts, storytelling/research/documenting, social media/communication, etc.) that will enable LOTE5 to rise and shine. A discussion on the threshold of the task effort/ticket correspondance will be launched in the platform by this Wednesday Nov, 4th and closed during this Thursday community call.

2-8 November

TASK: define who is getting in contact with which venue

MS: 4/5 VENUES CONTACTED

TASK: Launch poll/post to define the ticket policy –> @ireinga

TASK: Decide the ticket policy

MS: JOIN THE TEAM PAGE CREATION —> @ireinga

MS: OPENING POST DEVELOPMENT TRACK —> @KiraVde

TASK: Track leader engages 3 LOTE5-to-be-participants in writing content and pushing social media attention on the blog posts

TASK: Set up community call (Edgeryders + FB + social media) —> @ireinga

TASK: Invite key people joining the community call

MS: WEEKLY COMMUNITY CALL

TASK: Notes and update of tasks resulting from Community call —> @ireinga

MS: CREATE ONE PAGE DESCRIPTION LOTE5

TASK: Engage ambassadors and keynote speakers

TASK: Update activity calendar and breakdown of tasks

MS: CREATE LIST/WIKI of SUPPORTING PARTNERS —> @ireinga

TASK: Assign who is getting in contact with which supporting partner

9-15 November

TASK: Engage ambassadors and keynote speakers

MS: FIRST 4 SPEAKERS/AMBASSADORS ONBOARD

TASK: Evaluate development track opening post impact

TASK: DEVELOPMENT TRACK: 2ND ARTICLE PUBLISHED

TASK1: Opening post/opportunity to collaborate on tracks: who has a fail/unfail topic that would like to curate?

TASK2: Edgeryders post announcing a new track call for action + Social Media push

TASK3: Closing of track research announcement

MS: TRACK LEADER DEFINED

TASK: Update venue wiki

TASK: Update supporting partners wiki

TASK: Engage ambassadors and keynote speakers

TASK: Set up community call (Edgeryders + FB + social media)

TASK: Invite key people joining the community call

MS: WEEKLY COMMUNITY CALL

TASK: Notes and update of tasks resulting from Community call

1 Like
2

This is an unfriendly draft

For the next two weeks, I’m going to update it tomorrow and push it till the end of January. If someone already has feedback of any kind I would love to hear it before I keep working on the same mindset.

As soon as it gets farer in time there will be less detail that will be update on-the-go, of course.

Also, we need to assign these tasks. I wonder how I/we could do it. Creating a task on the group everytime there is one sound like an overload on the workspace. Let me know your thoughts.

Final note: there are tasks/milestones missing in the overview I made, like Logistics + Catering + Budget + Ethnography.

1 Like
3

Tasks help structure information and keep track of contributions

Makes it easy for me to step in and help if I have overview of what needs to be done and can pick one of a set of well-defined tasks.

Also makes online engagement easier imho: " Want a ticket? complete this task" + link to task.