Recruiting Pipelines documents and messaging

[rjdoria]

Overview

Gather all 'Recruiting Pipelines' documents and messaging in one place
Create missing 'Recruiting Pipeline' documents
Document process for creating new docs in Guide

Action Items

Identify the following three documents for each CoP:

• 'Recruiting Pipelines' google form
• 'Recruiting Pipelines' response spreadsheet
• Messaging document or examples of messaging in Slack

(Pipeline documents need to be revised or created)

Progress:

• Make guide for creating 'Recruiting Pipeline' form and response sheet
• Pilot guide with another team member
• Ensure 'Recruiting Pipeline' form and response sheet created for each CoP

Link to documents in Resources for the each CoP:

• UI/UX
• Data Science
• Development (programming)
• Ops
• Product Management
• Marketing
• Fundraising

Resources/Instructions

Guide: Create Recruitment Pipeline Form and Response Sheet
UI/UX - Pipelines form, Pipelines response sheet, Messaging
Data Science - Pipelines form, Pipelines response sheet, Messaging
Development - Pipelines form, Pipelines response sheet, Messaging
Ops - Pipelines form, Pipelines response sheet, Messaging
Product - Pipelines form, Pipelines response sheet, Messaging
Marketing - Pipelines form, Pipelines response sheet, Messaging
Fundraising - Pipelines form, Pipelines response sheet, Messaging

[rjdoria]

@tan-zhou Would you mind piloting the Guide for me? I included it in the Resources. The Practice Area to create would be Ops.

Also, could you take a look at the UX Pipeline Response Sheet? There are three channels we can add into the main response sheet. Thanks!

[tan-zhou]

I'll take this issue to Thad and ask his advice on how we should formulate the Google sheet. Will come back and update the issue with his answers

[rjdoria]

Obstacles

• New responses on Response tab still insert a new line; even if formulas on Display Sheet are properly set up on creation they will fail to read new responses unless formulas are updated
• Even after deleting test responses, new responses are inserted on a lower row which may create gaps on the Display Sheet

Questions:
How to create solution to automatically update formulas?
Any other solutions regarding connectivity between Form and Response Sheet that eliminates this issue?

[tan-zhou]

After the current Google sheet behavior issue has been solved, we should add column to pipeline spreadsheet for length of joining process e.g. how long does it take from requesting to join to being proved in the group?

[rjdoria]

Using Zapier to create issue to validate new Pipeline response:

• Signed up to Zapier using Civic Opp gmail
• Connected to Google Sheets using [email protected]
  • [email protected] needs access to Pipeline documents in Google Drive

Concerns:

• Triggers when new row added to bottom of spreadsheet, potential problem for existing Pipeline documents with responses
  • Issue with existing responses, will move forward pilot with empty response sheets
• Any better emails to use for sign up or Google Sheet trigger?

[rjdoria]

Next steps:

• Give [email protected] access to Google Drive
• Sign up [email protected] for GitHub
• Add [email protected] to Hack for LA on GitHub
• Create zap for Marketing Pipeline response sheet
• Pilot creation of Issue from zap trigger
• Revise Pipeline docs for new Zapier process
• Create zaps for other Pipeline docs

Blockers:
Need to have [email protected] added to the Hack for LA organization on GitHub (sn: Civic-Opportunity-Project)

[rjdoria]

Zapier pilot with Marketing repo: Issue #38

Progress:

• Zapier connection to Marketing repo tested with success
• Zapier trigger (new row on Marketing Pipelines response sheet) test failed
  • Marketing Pipelines already have responses, pilot with an empty response sheet instead

Zapier pilot with Revenue repo: Issue #15

Progress:

• Zapier trigger test successful

[rjdoria]

Pilot final updates with Fundraising Recruiting docs

Progress:

• Fundraising Pipeline response sheet revised with Display sheet and refreshed link with Form
• Updated Create Issue text with link to Response Sheet and channel details
• Test successful and document is now live, see Issue #19
• Links updated in Open Roles repo and this issue's resources

[rjdoria]

Progress:
Steps

• Unlink form and reconnect to fresh response sheet, rename as Responses
• Create new Zap and connect to pipeline doc
• Set up 'Create Issue' action with issue details, link to pipeline doc
• Test connection to set up, enter column hints as final test response
• Update Display column and Display Sheet formulas
• Update links in Issue Recruiting Pipelines documents and messaging #124 resources and Open Roles board

Zapier tests completed

• Product Issue #217
• Data Science Issue #31
• Engineering Issue #12
• Ops Issue #9

[rjdoria]

Progress:
Finished updating Engineering pipeline docs.

Next steps:
Finish up guide with Zapier steps.
Pilot guide and create Ops pipeline docs

[rjdoria]

Progress:
Created Ops pipeline docs

Concern:
Max 5 Zaps before upgrading Zapier plan

[ExperimentsInHonesty]

Hi @rjdoria, I went to the pipeline link on ux community of practice and it took me to the pipleline page instead of the display page, because that pipeline page is not hidden yet, etc. please make sure that the viewer only sees the display page

https://docs.google.com/spreadsheets/d/1TuDelZ_pCg1pc9murZaYMsnv7CgEwXvoVtH5Jkt32XM/edit#gid=34538959

[rjdoria]

No progress yet. I will pick back up next week.

Next steps:

• Refresh link to Form and manually re-enter submitted responses for the following CoPs
  • Marketing
  • UI/UX
• Turn on Zapier automation
  • Create new gmail
  • Marketing Zap
  • UI/UX Zap

[rjdoria]

Refreshed link to Form and manually re-submitted responses for Marketing and UI/UX.

Next steps:

• Update formatting for Display Sheet
• Turn on Zapier automation

[rjdoria]

Progress:

• Created [email protected] and saved login in 1Password
• Created Zapier and Github accounts (use @hackforla Github account)
• Updated response sheet and created new Zaps for Marketing and UI/UX

Next steps:

• Need to connect Zapier to @hackforla Github instead

[rjdoria]

Progress:

• Used [email protected] for GitHub login in Zapier
• Zapier tests completed, Zaps are turned on and docs are live
  • Marketing Issue #49
  • UI/UX Issue #82
• Updated links in Issue Recruiting Pipelines documents and messaging #124 resources and Open Roles board

[alexilee]

Moving to 'Done' to clean up board.