# Task Templates

Background
---
There have been a number of previous formats for gathering problem statements, sourcing solutions and creation of tasks. They have been designed with slightly different uses in mind. Below are links to past initatives.
- [vPA Treasury Templates]()
- Improvement Request
- Funding Request
- Change Request
- [CGO/SWARM Task Template](/s/features)
- Simon's First Dework task template draft
1. Describe. Roughly outline the problem, and (optionally) one/several potential solutions.
- The bounty hunter's task is to elaborate on the problem and/or analyse one/several solutions
2. Define priority. Low, medium, high.
3. Define task points/effort.

Design considerations
---
We want to choose a template based on a number of important decision variables.
- Simple. A community member should easily grasp what to do.
- Flexible. It should suit a wide range of task types.
- Clear. Expected outputs should be obvious.

Template Suggestion v.1
---
This alternative means we have only one task template for all dework tasks.

**What is the problem?**
*... Please limit yourself to ~250 characters, or ~40 words. We suggest you start by writing "The problem is that...". For example, "The problem is that there is no clear point of entry for newcomers to learn how to engage in Catalyst".*

**Please summarize potential solutions** (optional)
*...Please limit yourself to ~250 characters, or ~40 words, per solution. We recommend you create a HackMD if you want to elaborate on your solution ideas. Please add a link to this document under the "Current working documents" on our [HackMD master page](https://hackmd.io/dDho_qgwR4yeiJmrJFaAgw?both). For example, "Conduct interviews with newcomers to understand how to redesign our entry points."*

**What are the acceptance criteria for this task?**
*...This defines what it takes for the task to be "done". After work is submitted, the bounty manager presents it to a working group who will either reject or accept it in accordance to the acceptance criteria. For example, "Survey of the Catalyst onboarding experience with at least 10 participants".*

**When does this task need to be done?** (optional)
*If the solution cannot be implementable unless it is ready by a specific point in time, then please note it here. Please also explain why it has to be done before this date.*

**Please provide additional background and links here** (optional)
*These links will help the bounty hunter understand the context better.*

**Please mention the skills relevant for this task** (optional)
*This will speed up the problem-solving process.*

###### tags: `Tasks` `Dework` `Templates`

Template suggestion v.2
---

*This template exists for two reasons. First, to make sure tasks are concisely written yet contain all the necessary information for bounty hunters. Second, to ensure appropriate accountability and criteria for the release of (scarce) treasury funds. The italicized text are instructions.*

**What is the problem?**
*... Please limit yourself to ~250 characters, or ~40 words. Tip: Who does this problem affect? We suggest you start by writing "The problem is that...". For example, "The problem is that there is no clear point of entry for newcomers to learn how to engage in Catalyst".*

**Please summarize potential solutions** (optional)
*...We recommend you create a HackMD if you want to elaborate on any solution ideas. Please add a link to this document under the "Current working documents" on our [HackMD master page](https://hackmd.io/dDho_qgwR4yeiJmrJFaAgw?both). For example, "Conduct interviews with newcomers to understand how to redesign our entry points."*

**What's the "Definition of done" for this task?**
*...This is also known as "acceptance criteria". After work is submitted, the bounty manager manages a discussion and poll amongst the community who can either accept, or ask for revision in accordance to the acceptance criteria. For example, "Survey of the Catalyst onboarding experience with at least 10 participants".*

**Why does this task need to be completed by the indicated deadline?** (optional)
*If the solution cannot be implementable unless it is ready by a specific point in time, then please note it here.*

**Please provide additional background and links here** (optional)
*These links will help the bounty hunter understand the context better.*

**Please mention the skills relevant for this task** (optional)
*This will speed up the problem-solving process since it allows bounty hunters to self-select by their interest and/or skills.*

### (pre-set) To-Do's
* Initiate discord discussion and a "approve/disapprove/revise" poll for this Task
* Revise the task and resubmit for discussion/poll (if needed)
* Update status to "To Do" upon approval of task (Reviewer/Bounty Manager)
* Update status to "In progress" after Reviewer/Bounty Manager approves assignee
* *The task itself*
* Upload screenshot of evidence, tag Bounty Manager/reviewer to approve completion, and send ADA address to Board of Trustee/ex officio officer
* The Bounty Manager informs the Treasury Board of Trustees about the task completion of this task.

Feedback drop
---

#### From Felix [SWARM]
- Time deadline can be put in the task itself
- Skills required can also be put in task itself

#### From Stephen [QADAO]
- What's the purpose of this template? Clarify in beginning
- Who manages process? Data? Who decides on "completion"? Can support be withdrawn?

#### From CallyFromAuron#1714 in CGO discord

That said, my comments on the actual structure that you've given here are:
1) Add "Who does the problem affect?" as the 2nd question. This can be a very clarifying/focusing question; but it's also really useful, not so much to see "which groups are facing problems", since all groups do; but more "which groups' problems are being heard, recognised, and getting solutions".
2) If you want to "move away from presupposing that the person writing the task/who identified the problem is also the one dictating what the solution is going to be", (which I think is a really good idea, btw) I would suggest :

(a) rephrase We recommend you create a HackMD if you want to elaborate on your any of the solutions (just to make it clear that people are not supposed to give purely their own solutions) and
(b) structure the "potential solutions" section so that people can say where a solution originated from - i.e. whether it's their own, or has been developed as a group or in consultation with anyone. Ideally, I would want to see this structured so it can show any correlation there might be between "who is affected" and "where does the solution come from", because often in Catalyst we get people suggesting solutions to problems they have not actually experienced and do not fully understand. A solution that comes from those affected is always more powerful and more empowering, and usually more effective. So maybe there needs to be a field to say "who has been consulted or had input into this solution?"

I would also suggest a rephrase of What are the acceptance criteria for this task?, which is kind of management-speak and a bit obscure, to something clearer like "How can we tell when the task is "done"? or How can we define "finished" for this task?

**From ...**