> For the complete documentation index, see [llms.txt](https://jamiewen00.gitbook.io/tech-lead-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jamiewen00.gitbook.io/tech-lead-handbook/prioritisation/pros-and-cons.md).

# Pros and Cons

## The What

There are multiple options to achieve the same goal, it can be challenging to determine the most suitable or "good enough" option. That's where we could conduct a **Pros and Cons** comparison among different options. It is a more effective solution compared to other prioritisation processes.&#x20;

## The How

The use the Pros and Cons framework, follow these steps: First of all, you should clarify the Context, Goal, and Key Drivers. Secondly, think of possible options

Option 1: Focus on the Preferred Option

* 🟢 List of good points
* 🟢 ...
* 🔴 Also consider some drawbacks or limitations

Option 2: Explore the Alternative Option

* 🟢 Benefits of the alternative option
* 🔴 ...

Option 3: Fast Track or Ignore Unrealistic Options

* ... ...

## :white\_check\_mark: Exceptions

Be aware of the following exceptions when using the Pros and Cons framework:

* Not suitable for over-complex problems
* Not suitable if you have many metrics to compare
* Not suitable for a large number of options

## :red\_circle: Red Flags

If you find yourself writing a lengthy essay when using the Pros and Cons framework, it's a signal that you may want to consider using [Decision Matrix](/tech-lead-handbook/prioritisation/decision-matrix.md) instead

## :scroll: Tips

* Pros and Cons only work on relatively simple questions
* There are other tools you can leverage to make decision

## :hole: Pitfalls


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://jamiewen00.gitbook.io/tech-lead-handbook/prioritisation/pros-and-cons.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
