The Dework Process revisited [Draft]

There has been lack of communication regarding how people are deciding to process Dework Tasks, and how those tasks are being documented as paid.

I am going to build an exhaustive breakdown of every possible dework process I can think of, to try and bring clarity to how CS can build the dework program for maximum productivity.

 

This is a living document, so it should (when iterations occur) change. Communication is HARD, with me, and with others. So sometimes, the best way to move forward is via the distribution of communication This will be broken down into sections. 1. Definitions. 2. Walkthroughs, and 3. Workflows. Lets Begin.

 

First, lets take a look at the why:

Dework tends to be the end all be all task management system. We decided to use dework as the end all be all for task management. Not sure if its because its web3, or because we got tired of using the notion bounty board but we moved forward, and used Dework. I think I may have been slightly trigger happy with using the process, but we can figure out how to make this tool work.

in order for Dework to actually work out well for others, you have to be able to be comfortable with using dework. This can be a quick process, but this can also be a process that takes time. You must be comfortable with the fact that you might not become acclimated to dework immediately. However, I’m going to help you get through those dework hurdles together! Lets start with some definitions first.

Definitions:

Task - The task is what needs to be completed. This can be as simple as writing a newsletter entry, or as complex as a Seasonal Retrospective. Typically, when you have a task that needs to be completed, you should input that task as the first thing that you do in your leadership process. Delegation is very important when it comes to being a leader. The Picture Below shows what a task looks like.

Subtask - a Subtask is a task that has to be completed in order to complete another task. For Example. If I were to create a content edit for an episode. I would also need to upload the video file to Premiere Pro. In this scenario, the subtask would be my uploading the video file to premiere pro, the task that I have completed the subtask for is the parent task. I have pointed to the title of the main task above, and I have pointed to the subtask below.

Due Date - This is the date that the task is due. In order to properly create a task in dework, its recommended that you add a due date to the task. You should break the habit of adding tasks to dework after they are completed. You can add your “evidence” that you’ve created the work needed to complete the task after you’ve finished the task, but for these purposes, you want to make sure that you create your task in dework BEFORE you actually complete your task in the real world. Every task should have a due date. We can not properly move on to the next part of the project if we don’t have a due date for the previous step to adhere to. As a collective, running a podcast network should definitely learn to utilize due dates in the structure.

1. to add a due date to a task -
click the 3 dots next to where the word “skills” is located



‘set due date’ appears - click set due date



pick your due date. for today’s purposes, i selected today, december 9th

2. Title - This is the title of your task. I’ve heard that there have been quite a few difficulties with titling. In order to have a title that doesn’t cause the finance department to jump down your throat, you want to stick to one form of titling. Take a look at the picture below - Apparently one of these tasks had a great titling system. The other one did not have a great titling system. Take a guess which one.

NOTE: Going forward, if the task you are working on is related to a podcast epiosde, you would need to have titling completed like this:

(DEPARTMENT - DUE DATE - NAME OF EPISODE - TYPE OF TASK)

• note: this can change, if you decide to create tasks in your own space, and not in the flagship space

• note: this can depend on your feelings in regards to the proper way of titling a project. you may see a poll in the future that could change this titling, or this will confirm the

 

Space - This is an area that can be dedicated to one specific kind of project. Examples include: Project Rebranding, Design, etc. Typically more focused projects should be housed in this area that are only meant for one particular department. Spaces usually appear on the left side of your dework dashboard.

Creating a Space: There are two places where you can create a space. I’ve placed arrows pointing towards where those two spaces are.

1. You can either click the spaces area when first checking out the dashboard and seeing the overview section. there will be a blue/purple/lavender ish color button that says “create”

2. the second spot is on the left side of the screen. there, you will see a greyed out add button that says “+create”

the option pops up to either create a task without importing, import the task from notion, trello, or github. IMPORTANT: BanklessDAO does not have notion integration. Since this notion was built as a project of bankless dao, we will not be able to sync directly between dework and notion.

The Settings function (three buttons) on the top right corner of the space card: This gives you the option to duplicate the space.

Templates -

templates are used when you do not want to recreate the entire task over again. This can be beneficial for recurring tasks, because dework doesn’t give you the ability to add tasks for recurring items. This can also be a detriment, if the template is not created properly. Typically, you will find the section to create templates in the main dashboard area, by pressing the space where you want to create the template. Next, press “settings” (the gear)

From there, press templates.

Next, press new template. You will see a new screen pop up.

You can then fill out your task in the way that you appreciate. With Title, priority, tags, task points, and more.

Check to see if you want the task already assigned, or if you want to have contributors apply for the task, or whether you want to have multiple submissions for the project.

When you open the topic up to applications, you run the risk of having non contributors applying for tasks. keep that in mind, or make sure you lock down the people who are able to apply by selecting roles that have the ability to apply.

You can breakdown roles to role gate applications.

you can also role gate who can claim tasks as well (direct claiming)

You cannot role gate the multiple submission options. However, you can accept submissions from different roles. You can decide on how many winners you will take out of the group of submissions.

you can also create a submission form for this task. This can be done by pressing advanced to open the advance option.

Task Points -

Task points can be used in lieu of bounties, if you have issues with compiling bounties properly in the system. As the screenshot says, you can use this for time accounting, for rewards, and more.

Priorities -

Use Priority markers for urgent tasks. Priority levels include No Priority, Low Priority, Medium Priority, High Priority, and Urgent