Decision Maker
HomeFeaturesPricingBlogUse CasesFAQContactDocumentationLogin
Write what should not be forgotten.
Isabel Allende

Decisions

Decisions are the heart of Decision Maker. Decisions have a status lifecycle, Creating, In Progress and Completed. Decisions are shown in the Decision Register page under the different statuses that decision can have.

New decisions can be created using the plus button on the right hand side of the page. Decisions can be opened for editing, scoring and viewing by clicking on it. Additional functionality can be accessed by clicking on the triple dot menu.

The three statuses that a decision can have are: Creating, In Progress and Completed. Decisions can be dragged and dropped into the different status lanes to change the status or the decision can be edited and the status manually updated. Decisions in the "In Progress" lane shows how much of the scoring has been completed while decisions in the "Completed" lane shows the outcome of the decision making process.

Creating

A decision with the Creating status is under construction and this allows you to assign users and create categories and criteria.

You need to at least enter the Summary of the decision, what you are trying to Compare and at least one Category and Criteria.

The fields in the Decision Editor are as follows:

  • Summary: A brief description of what the decision is for

  • Description: An optional more detailed description of the decision

  • Linked Issues: Any Jira Issues that are related to this decision

  • Status: The current status of the decision that also indicates which lane it is in for the Decision Register

  • Owners: The users that can use the window to edit the decision. These users can also score the decision when it is In Progress

  • Assignees: The users that can score this decision

  • Compare: The outcome/product/service that this decision will compare (up to five items).

  • Search Labels: Additional keywords that can be used when searching for this decision

  • Category: This contains a group of criteria. Use this to separate the criteria into related groups and/or a general group.

  • Criteria: This is a requirement/fact/statement that you what to use in choosing which of the compare items is the best. This should be a verb (i.e. ability to do..., be able to..., provide after-hours support..., can scale to...).

  • Importance/priority: Decision Maker uses the MoSCoW Methodology for indicating how important (how high a priority) the criteria will be. So if the criteria is vital to the decision then you would mark it as a Must and if it has little impact on the decision you would mark it as Could and if it is not applicable then it gets a Wont

The MoSCoW methodology uses Must for Must have, Should for Should have, Could for Could have and Won’t for Won't have. ​The plus button next to the category and criteria fields allows you to create new categories and criterias. The trash can icons are used to delete the category/criteria. ​

In Progress

Once all of the Decision details have been entered and saved, the decision can be moved to In Progress. Decisions in the In Progress status are ready for scoring. An In Progress decision, when clicked upon, will look like the example shown below.

The decision has now been fully constructed and the assignees/owners will find the answers for all of the criteria. When an answer is found, the certainty (the value Yes/No/Maybe) can be entered for each item being compared.

Decisions in this status can be moved back to Creating if more criteria needs to be added. When all of the scoring has been done the Decision can be moved to Completed.

Completed

The Completed status indicates that the Decision has been completed and that you are not expecting to do any changes. Completed Decisions show the outcome of the Decision on the Decision Register, displaying the total score for each option you are comparing and the winner(s). If any of the scoring needs to be adjusted then the Decision can be moved to In Progress.

Clicking on a completed decision shows a screen like the example below.