[2026-07-06] eagle: work/projects/ios-subscription-day7-promo-kickoff.md
This commit is contained in:
Alexey Martemyanov
@@ -7,70 +7,56 @@ asana: >-
|
||||
due: '2026-07-07'
|
||||
status: upcoming
|
||||
---
|
||||
# Kick-off: iOS Day 7 Subscription Promo Half-Sheet
|
||||
# Kick-off: (iOS) Grow active subscriptions by increasing paywall impressions with a day 7 promo half-sheet
|
||||
|
||||
> **Asana:** [1214800083544612](https://app.asana.com/1/137249556945/project/1202406491309510/task/1214800083544612)
|
||||
> **Parent project:** [iOS: Show subscription half-sheet promo to new installers who don't see it during onboarding](https://app.asana.com/1/137249556945/project/1207260194172075/task/1214798984829406)
|
||||
> **Due:** 2026-07-07
|
||||
**Before the call:**
|
||||
|
||||
1. Review the project scope. Are the goal, success criteria, and tasks **correct** and **succinct**? Don't be afraid to delete other peoples' words; you're responsible for the project now.
|
||||
2. [Should this project have a Hack Phase?](https://app.asana.com/0/0/1209887118493776)
|
||||
3. Add any remaining open questions or points of ambiguity to the kick-off task under **Discussion items**.
|
||||
4. Take 10 mins to consider **timeline accelerators**, **premortem**, and supporting processes from [Pre-Kick-off Questions](https://app.asana.com/0/0/1207268731049843/f).
|
||||
- If [Pre-Kick-off Questions](https://app.asana.com/0/0/1207268731049843) inspires improvements, update the scope/task timeline!
|
||||
- If [Pre-Kick-off Questions](https://app.asana.com/0/0/1207268731049843) might benefit from discussion, add them to **Discussion items**.
|
||||
5. Fill in remaining fields.
|
||||
6. On the project, add stakeholders then post a comment with a link to this kick-off task, ideally at least 48 hours in advance of the call but don't let this slow you down.
|
||||
|
||||
*Reminders:*
|
||||
|
||||
- *~~Add the project to [Current Objectives](https://app.asana.com/0/72649045549333/1203937055064396) as soon as you begin preparing your kick-off.~~*
|
||||
- *~~Add the kick-off task to the [Kick-off Calls](https://app.asana.com/0/492600419927320/list) project and as a subtask of the project you are kicking off.~~*
|
||||
- *Use the due date field to set the date and time.*
|
||||
- *Ideally schedule for Mon/Tue/Fri and within or contiguous to an existing standing meeting (e.g., the relevant Objective meeting). Avoid Wednesday (no meetings day). Bias towards scheduling quickly, broadcasting the time, and being willing to reschedule if people can't make it.*
|
||||
- *Create a calendar event in Outlook if none exists and invite attendees.*
|
||||
|
||||
**During the call:**
|
||||
|
||||
1. Say hi, share the kick-off link in the chat, jump right into **Discussion items**. Do not read out the other sections.
|
||||
2. Notice when ambiguity or risks cannot be solved in the call and determine a mechanism for resolving it after the call, e.g. a one day investigation, a prescheduled mid-mortem...
|
||||
3. Close the call by briefly stating **Next steps.**
|
||||
|
||||
**After the call:**
|
||||
|
||||
1. Close the kick-off task and comment on the project that the kick-off is done (with link), and any takeaways that would be useful for people to know.
|
||||
2. Update the scope again to reflect any changes, and to be as simple and true as it can be. Continue to do so as the project progresses.
|
||||
|
||||
---
|
||||
|
||||
## Before the call
|
||||
Zoom link: https://duckduckgo.zoom.us/my/malex
|
||||
|
||||
- [ ] Review project scope — goal, success criteria, and tasks are correct and succinct
|
||||
- [ ] Consider: [Should this project have a Hack Phase?](https://app.asana.com/0/0/1209887118493776)
|
||||
- [ ] Add open questions / ambiguity to **Discussion items** below
|
||||
- [ ] 10 min: review [Pre-Kick-off Questions](https://app.asana.com/0/0/1207268731049843/f) — timeline accelerators, premortem, supporting processes
|
||||
- Update scope/task timeline if prompted
|
||||
- Add any discussion-worthy items to **Discussion items** below
|
||||
- [ ] Fill in remaining fields (Zoom link, stakeholders)
|
||||
- [ ] Add project to [Current Objectives](https://app.asana.com/0/72649045549333/1203937055064396)
|
||||
- [ ] Add this kick-off task to [Kick-off Calls](https://app.asana.com/0/492600419927320/list) project and as subtask of the parent project
|
||||
- [ ] Post comment on project with link to this kick-off (ideally 48 h in advance)
|
||||
- [ ] Create Outlook calendar event and invite attendees
|
||||
- [ ] Schedule Mon/Tue/Fri, within or adjacent to an existing standing meeting; avoid Wednesday
|
||||
**Stakeholders and their responsibilities**
|
||||
|
||||
---
|
||||
- Project Advisor: https://app.asana.com/1/137249556945/profile/1201807753392396
|
||||
- [Other stakeholders](https://app.asana.com/0/0/1207268731049844/f): https://app.asana.com/1/137249556945/profile/1200848785550295 https://app.asana.com/1/137249556945/profile/1206329551987277 https://app.asana.com/1/137249556945/profile/1211198099252476 https://app.asana.com/1/137249556945/profile/1200727780991749
|
||||
|
||||
## Zoom link
|
||||
**Scope updates**
|
||||
|
||||
<Zoom link>
|
||||
- Briefly note if you updated the scope significantly in preparation for this call, e.g., removed secondary goal of x.
|
||||
|
||||
---
|
||||
**Discussion items**
|
||||
|
||||
## Stakeholders and their responsibilities
|
||||
- Add any unresolved ambiguity, *timeline accelerators*, *premortem* risks, or open questions.
|
||||
- For any significant items that cannot be resolved in discussion, decide on a mechanism to resolve them, e.g. a prescheduled mid-mortem at 1 week, and update the scope accordingly.
|
||||
|
||||
- **Project Advisor:**
|
||||
- **Other stakeholders** ([reference](https://app.asana.com/0/0/1207268731049844/f)):
|
||||
**Next steps**
|
||||
|
||||
---
|
||||
|
||||
## Scope updates
|
||||
|
||||
- <!-- Briefly note any significant scope changes made in preparation for this call, e.g. "Removed secondary goal of X." -->
|
||||
|
||||
---
|
||||
|
||||
## Discussion items
|
||||
|
||||
- <!-- Unresolved ambiguity, timeline accelerators, premortem risks, open questions -->
|
||||
- <!-- For items that can't be resolved on the call: decide on a resolution mechanism (e.g. prescheduled mid-mortem at 1 week) and update the scope -->
|
||||
|
||||
---
|
||||
|
||||
## Next steps
|
||||
|
||||
- <!-- Immediate next steps with owners (link to task timeline items where possible) -->
|
||||
|
||||
---
|
||||
|
||||
## During the call
|
||||
|
||||
1. Say hi, share the kick-off link in the chat, jump straight into **Discussion items** — do not read out other sections
|
||||
2. Note any ambiguity/risks that can't be resolved on the call; agree on a mechanism to resolve them after
|
||||
3. Close by briefly stating **Next steps**
|
||||
|
||||
## After the call
|
||||
|
||||
1. Close the kick-off task and comment on the project that kick-off is done (with link) + any useful takeaways
|
||||
2. Update the scope to reflect any changes; keep it simple and true
|
||||
- Add immediate next steps and their owners (ideally links to items in the task timeline)
|
||||
|
||||
Reference in New Issue
Block a user