The Catalpa Handbook
  • The Catalpa Handbook
    • Handbook guidelines
  • 1. ABOUT CATALPA
    • 1.1 About Catalpa
    • 1.2 Vision, Values and Strategic Plan 2022
    • 1.3 Governance at Catalpa
    • 1.4 Organisational structure of Catalpa
    • 1.5 Our projects and key contacts for each
    • 1.6 Our key products
      • Bero
        • Content
          • Exams
          • Targeting Content to Users
            • Resizing images for Bero
        • Design
        • Requirements
        • Theming
      • Gathr
      • Openly
  • 2. OUR PEOPLE AND HOW WE WORK
    • 2.1 How we work and the tools we use
      • Google Drive
      • Trello
      • Github
      • InVision
    • 2.2 Communicating internally
      • All Hands Stand-up (weekly / Mondays)
      • Tutorial Tuesdays
      • Show & Tell
      • Guide to Slack
      • Team meetings
      • Other Events
    • 2.3 Mission Driven Teams
    • 2.4 Recruitment and Onboarding
      • Hiring Guidelines
    • 2.5 How we support our people to thrive
      • Onboarding a new hire
        • Onboarding Trello
        • Onboarding buddy guide
        • 30/60/90 Day Plan
      • Goal Setting
      • Regular work/task based 1X1's
      • Quarterly Catch Up's
      • Feedback
      • Managers - Managing Underperformance
    • 2.6 Offboarding
    • 2.7 Leave and public holidays
      • Leave
      • Public Holidays
    • 2.8 Supporting our Mental Health
    • 2.9 Working from home & remotely
    • 3.0. Learning & Development Allowance
  • Page
  • 3. EXTERNAL COMMUNICATIONS
    • 3.1 Guide to Communication
      • Describing Catalpa
      • Guide to photography
      • Guide to social media
      • Writing: style guide
      • Writing: grammar
    • 3.2 Procedures for the collection, storage and use of stories, photos and video
    • 3.3 External Complaints and Feedback Policy
  • 4. PARTNERSHIP AND GROWTH INCLUDING BUSINESS DEVELOPMENT
    • 4.1 Introduction / overview
    • 4.2 Pre-bid stage including networking and partnering
      • Networking
      • Positioning for priority bids
      • Tracking bid opportunities
      • Partnering
        • Partnership brokering
        • Due diligence of downstream partners /subcontracting agencies
        • Pre-bid agreements
    • 4.3 Go / No Go
      • Go / No Go meetings
      • Selection criteria and guidelines
    • 4.4 Tender planning and preparation
      • Project planning and design pre-submission
      • Key templates and links for bid planning and preparation
      • Bid Writing - full proposal or concept note
        • How to appoint an external bid writer
        • Key templates
        • Commonly required building blocks / required materials for tenders
        • Guides
    • 4.5 After a bid has been submitted
  • 5. PROJECT AND PRODUCT CYCLE MANAGEMENT
    • 5.1 Introduction
    • 5.2 Planning and pre-submission design
      • 5.2.1 Monitoring, Evaluation & Learning
        • Project-level M&E
        • Catalpa's organisational approach to MEL
      • 5.2.2 Risk Management
      • 5.2.3 Cross-cutting issues in projects
        • Gender equality
        • Disability inclusion
    • 5.3 Mobilising a new project
      • Handover from BD team to PM team
      • Program Summary Document
      • Team Kickoff Meeting
      • Team Charter
    • 5.4 Post-contract implementation
      • Stage 1 - Learn: Design and Discovery
        • Human Centred Design
        • Our Tools
        • Creating a product
      • Stage 2: Create and Ideate
        • Our model
        • Agile Project Management
          • Getting started
          • Product design and development phases
            • 0. Contracting
            • 1. Learn
              • 1.1. Prepare
              • 1.2. Discovery
              • 1.3 Empathise
            • 2. Create
              • 2.1 Ideate
              • 2.2 Implement
            • 3. Refine
            • 4. Evaluate
          • Product Roadmap
          • Defining releases
          • Create the solution
          • Make a global plan
          • User Stories
          • Prototyping
          • Incremental development
          • UX & UI
          • Conducting tests
      • Stage 3: Refine and Release
        • Introduction and overview
        • Data privacy on a project basis
        • How-tos
          • Retrospective
        • Scrum methodology
          • Daily standup
          • Sprints
          • Sprint prep
          • Sprint meeting
        • Release
          • Epics
          • Epic selection
          • Epic planning
          • Product Q&A, deployment and implementation
          • Make it available
          • Delivery
      • Stage 4: Evaluate
        • Define the maintenance support plan and team
        • Customer support
        • Ongoing user data collection and analysis
      • Glossary of Terms
    • 5.5 Project close-out
      • Product transition and handover
      • Transition to governmen
      • SMA
      • Licenses / handover documents
      • Migrating to Gov owned data-center or cloud hosting
  • 6. POLICIES AND PROCEDURES
    • 6.1 Register of policies and compliance
    • 6.2 Policy Development Procedure
    • 6.3 Code of Conduct
    • 6.4 Data Privacy & Storage Policy
    • 6.5 Human Resources Policies
      • Breastfeeding and Work Policy
      • Occupational Health and Safety Policy
      • Domestic and Family Violence Policy
      • Gender Equality Policy
      • Disability & Discrimination Policy
      • Use of Catalpa Vehicles Policy - PNG
      • Anti-Bullying, Harassment and Discrimination Policy
    • 6.6 Safeguarding Policies, Templates and Training
      • Child Safeguarding Policy
      • Prevention of Sexual Exploitation, Assault and Harassment Policy (PSEAH)
      • Safeguarding templates
      • Safeguarding training
      • Safeguarding procedure for collecting, storing and using images / stories
    • 6.7 Financial and Asset Management
      • Fraud & Corruption Policy
      • Vehicle Use
    • 6.8 Complaints and Feedback
      • Internal Complaints and Feedback Policy
      • External Complaints and Feedback Policy
      • Whistleblower Policy
    • 6.9 Contract Development Procedure
Powered by GitBook
On this page

Was this helpful?

  1. 4. PARTNERSHIP AND GROWTH INCLUDING BUSINESS DEVELOPMENT
  2. 4.3 Go / No Go

Go / No Go meetings

Previous4.3 Go / No GoNextSelection criteria and guidelines

Last updated 11 months ago

Was this helpful?

You can find the Guide to "Go / No Go" meetings below, which should be read in conjunction with the

Guide purpose: The purpose of this checklist is to guide any Go / No Go meeting. It was compiled by the Partnership and Growth team in May 2024.

  1. When to hold a Go / No Go meeting

(i) When there is a specific business development opportunity i.e. a donor has contacted us and invited us to submit a Concept Note; or an opportunity has been publicly advertised, and

(ii) The Manager - Partnerships and Growth has:

  • Looked into the opportunity and seen potential

  • Summarised the opportunity and existing information for other internal Catalpa stakeholders to assist with the discernment process (or delegated to another member of the Partnerships and Growth team to do so) including the Partnership and Growth team doing the initial review of the basic .

  1. What information needs to be shared by the Partnership & Growth Team with participants in the "Go / No Go" Meeting prior to the Meeting taking place

(i) Must have information:

  • Donor priorities

  • Summary of the opportunity

  • Budget envelope

  • The result of the Partnership and Growth team doing the initial review of the basic and also share the whole Criteria template so people can have a read-through of the criteria before the meeting.

(ii) Good to have information (i.e. highly desirable if the Manager - Partnerships and Growth can obtain / request it prior to the meeting but if impossible to obtain at this point the Go / No Go meeting should still be held in its absence):

  • Template or structure of the submission (to get a sense of the workload needed)

  • External information to request from donor:

    • Start date of the project

    • Budget window

  • Internal information to request from Catalpa stakeholders, to bring to the meeting:

    • Availability (or otherwise) of key personnel who would be involved in the project

    • Availability (or otherwise) of key personnel who would be involved in the bid / tender process

  • Other:

    • Potential partner organisation or consultants to work with us

    • Any recent networking with this donor and/or other inside information we have

    • Any other information that is pertinent

The information outlined above should be shared three business days in advance wherever possible so that people can read it prior to the meeting and the meeting time can be focused on discussing and arriving at a decision.

This information should be shared prior to the Go / No Go meeting via a Slack chat set up by a member of the Partnership and Growth team after having been delegated to do so by the Manager - Partnerships and Growth. The Slack chat should have a wider group of stakeholders than those in the Go / No Go meeting, including a representative from the Finance team who would be working on the budget.

  1. Who should be in a "Go / No Go" meeting

(i) Manager - Partnership and Growth:

  • Responsible for delegating to a member of the Partnership + Growth team to administer the meeting and share info prior to the meeting and providing that member of the team with the names of who should be invited to the meeting

(ii) Member of Partnership and Growth team (i.e. Ona, Nicole, Rebekah)

  • Responsible for finding a time that suits everyone setting up a meeting time and setting up a Slack chat with bookmarked link to a Google folder with any information about the opportunity (RFT if available, or info about donor / upcoming opportunity) and a document in which to take notes from

(iii) Senior sponsor of relevant work area (David - Health, infrastructure &/or anything in PNG; Anders - health, social protection, governance & /or anything in Timor; Kara - Education)

(iv) Wherever possible i.e. if enough is known about the opportunity to establish what technical expertise may be needed and/or where schedules do not preclude their participation:

  • Relevant technical expertise (e.g. Juliana / Peter / Pedro)

  • Representative from Programs team (i.e. Kate or Sharon)

  1. Go / No Go meeting

(i) The Go / No Go Meeting should be chaired by the Manager - Partnerships and Growth.

(ii) The agenda should be:

  • 5-10 mins: Introduction to the discussion:

    • Summarise the opportunity

    • Time for any clarifying questions

  • 5 mins: Quickly review the scores and feedback for the Minimum Criteria (this is the initial assessment undertaken by the Partnership and Growth team before the meeting). If any criteria result in a “no,” discuss and decide if the opportunity should be dropped.

  • 25 mins: For opportunities that pass the Minimum Criteria, discuss the Detailed criteria. Each participant shares their scores and insights.

    The Six hats activity is a concept used during the Go/NoGo meetings to discuss various aspects of an opportunity. Each hat represents a different phase of thinking:

    • White Hat: Focuses on objective data and facts.

    • Red Hat: Centres on intuitive and emotional response

    • Black Hat: Considers negative aspects and potential problems.

    • Yellow Hat: Looks at positive aspects and benefits.

    • Green Hat: Encourages creative thinking and new ideas.

    • Blue Hat: Manages the thinking process and organisation

  • 10-15 mins: Decision. Options are:

    • Go

    • Go for now but reconvene once more information has been found for a final decision (this is relevant if we have insufficient information at the time of the meeting or expect information to change)

    • No Go

  • 5 - 10 mins: Action items and Next steps:

    Next steps:

    • If the decision is a ‘No Go’, then archive the Slack channel three working days after sharing the meeting notes in the Slack channel

    • If the decision is a ‘Go for now but more info is needed before final decision’ then ask the Catalpians involved how quickly they can get that extra information (from donor, potential partner, government stakeholders etc.) and set another meeting in line with the timeframe for getting that info and also the timeframe for submission.

    • If the decision is a ‘Go’, move to the Tender Preparation stage - refer to the Checklist for tender planning and preparation; set up a time for the next meeting to discuss the tender planning (ahead of that meeting set up a Tender Planning + Preparation checklist and a Team Charter for the development of the bid to discuss in the meeting)

This decision can be revisited in future if more information arises to change the scoring / likelihood

of success with this bid.

Action items:

  • Decide who will communicate the decision to any external stakeholders (i.e. potential partners and / or consultants we had contacted or the donor if they contacted us to ask us to submit a Concept Note)

  • Notes from the Go / No Go Meeting should be shared on the Slack channel by a member of the Partnership and Growth team so that all Catalpian stakeholders are aware.

  • Partnership and Growth Team to update status in coda.

30 mins: Go through the - see Minimum Criteria

Go / No Go checklist here
BD Selection Opportunity Criteria
BD Selection Opportunity Criteria
BD Opportunity criteria