![[Old] Gitcoin Passport (Marketing Hub)](/_next/image?url=https%3A%2F%2Fwww.notion.so%2Fimage%2Fhttps%253A%252F%252Fprod-files-secure.s3.us-west-2.amazonaws.com%252Fd5441ecb-756c-4608-a398-8b34fc71ebe8%252Fd886024d-2042-49a3-84db-6fade4d44647%252FGroup_1000003588.png%3Ftable%3Dblock%26id%3D633c29a9-02c1-48fd-85d6-44ad43cdcbeb%26cache%3Dv2&w=3840&q=75)
Gitcoin Passport New Feature Launch Checklist (November 2023 Edition)
Context
This is a process for launching new featuresārecently vetted by product team and devrel. (Comments have not been integrated)
This is a proposed process to support cross-functional coordination for launching new features for Gitcoin Passport.
To see how integrator marketing works, see .
Gitcoin Passport Integrator Co-Marketing Approach (June 2023 Briefing)
Ā
Phase 1: Engineering Complete
Tasks
Exit Criteria
Phase 2: Documentation Complete
Tasks (Within 2 weeks of Engineering Complete by default)
Exit Criteria
Phase 3: Public Launch
Tasks (Within 2 weeks of Documentation Complete by default)
Phase 4: Review Reception
Phase 1: Engineering Complete
Tasks
- Complete all feature development and internal testing.
- Let DevRel and Marketing know a week before pushing feature to production that a new feature will be pushed.
- Create a GitHub issue for tracking and feedbackāwhich includes a link to test the feature in staging.
- Provide DevRel and Marketing a PRD lite or "Consider and Explore" brief, as well as Visual Designs and GitHub Issue link for feature, and link it in Passport roadmap
- Update the Passport roadmap "Delivery date" to match the engineering complete date.
New columns for āPRD / Consider and Explore briefā, āVisual designsā, and āGitHub Issueā should be created in Passport roadmap
Ā
Difference in utility between GitHub issue and PRD lite (or C&E Brief)?
For features not already in staging or prod, business stakeholders provide feedback on via our PRD lites, and then the product managers convert that feedback into GitHub tickets.
If we have product feedback for features that are already live on staging or prod, that's when we would use GitHub to file feedback for product/eng team.
Ā
Exit Criteria
- All features are internally tested and approved.
- DevRel and Marketing are briefed as mentioned above, with Passport roadmap updated.
Phase 2: Documentation Complete
Tasks (Within 2 weeks of Engineering Complete by default)
- Update existing documentation based on new features or changes. Updates should include new UI designs related to the new features.
- docs.passport.gitcoin.co if developer facing (Dan owns this)
- https://support.gitcoin.co if holder facing (Gary to lead with support from Lolu)
- Get product to review documentation before publishing changes.
- Add a 'changelog' to the dev documentation site if developer-facing change.
Ā
Exit Criteria
- All new documentation was reviewed and is updated.
Phase 3: Public Launch
Tasks (Within 2 weeks of Documentation Complete by default)
If the feature is backend improvementsā¦
- Tweet from Danielās personal handle (@lebraat) and amplified by Passport
Ā
If the feature is public-facingā¦
- Publish tweet(s) about the feature; post about it on Lens and Farcaster
- Share about the feature in Passport Holders Guild (Telegram)
- Consider making a blog post if itās a big enough of a change
- Consider making a demo video
- Consider emailing Gitcoin newsletter subscribers who have opted in to hear about Passport updates if itās a big enough of a change
- Consider updating marketing website (gitcoin.co/passport) if itās a big enough of a change, and we want to promote the feature prominently on the website.
- Consider updating Potential Integrator One-Pager and Sales Deck if itās a big enough of a change
- Marketing to brief Passport BD team on the changes made to collateral if so
- Send a message sharing about the change in our Telegram groups with key partners if the change is relevant to them
Ā
Phase 4: Review Reception
After two weeks, alongside product team, review the reception of the new feature in a meeting. Discussā¦
- Google Analytics data
- Blog data
- What weāre hearing from integrators, and/or holders, and/or public at large
- Passport adoption data
- new integrators?
- new holders?
Ā
With this in mind, identify what actions we want to take based on this information.
Example: We launched this new functionality for ID Staking, and adoption shot up 30% overnight. An action could be to interview some people who started staking to learn why they adopted since the changes to ID Staking.
Ā
Ā
Ā
Ā
Ā
How can Marketing track these phases?
Iām thinking I update the table to have a āFeature Launch Phase (if applicable)ā column.
Upcoming Announcements/Communications for Gitcoin Passport
Ā
Ā
Ā