Go/No-Go

How to Utilize Buildr's Go/No-Go Feature

Buildr’s Go/No-Go process can help you decide whether or not a project is worth spending your time and resources on. Through a series of questions created by your team, you can quickly decide whether to move forward or pass on a potential project.


Enable Go/No-Go

To get started, navigate to Settings & select the Go/No-Go tab. Click “Enable Go/No-Go.”

Once enabled, you will see a list of default questions. You can add or modify your account go/no go questions to best suit your process.

Note: Only admin users can enable the Go/No-Go feature and customize questions. However, once enabled and customized, all users will have the ability to utilize the tool on all projects.


Customize your Go/No-Go Questions

To edit existing questions, simply click the pencil icon to make your edits.


To add new questions, type your question into the text box and click "Add question".

Once your Go/No-Go questions are customized to your team's process, click "Publish". Once published, your Go/No-Go questions will be available on all projects.


Using Go/No-Go Questions on Projects

Navigate to a specific project and select the Go/No-Go tab. Click "Get Started" to add your Go/No-Go questions to the project.

Complete the questionnaire by answering yes or no to each question. Once all questions have been answered, that project will receive a Go/No-Go score. Buildr recommends establishing Go/No-Go goals within your company before referencing the score given.

The following is an example of how to interpret a Go/No-Go number score:

  1. 80 (or above) - GO, no need for further discussion, try to win the job!
  2. 60 (or below) - NO GO, do not spend any more time or resources on this job.
  3. 60 to 80 - Leadership approval required, this job isn't amazing, but might be worth
    pursuing. Make a case for it to leadership!

The Go/No-Go score will be listed under Opportunity Information.



To view the Go/No-Go scores on your project list view, click "Board" at the top of the page (see below).