diff --git a/work/projects/ios-subscription-day7-promo-kickoff.md b/work/projects/ios-subscription-day7-promo-kickoff.md index 161ed58b..e02d1682 100644 --- a/work/projects/ios-subscription-day7-promo-kickoff.md +++ b/work/projects/ios-subscription-day7-promo-kickoff.md @@ -1,64 +1,21 @@ ---- -title: >- - Kick-off: (iOS) Grow active subscriptions by increasing paywall impressions - with a day 7 promo half-sheet -asana: >- - https://app.asana.com/1/137249556945/project/1202406491309510/task/1214800083544612 -due: '2026-07-07' -status: upcoming ---- # Kick-off: (iOS) Grow active subscriptions by increasing paywall impressions with a day 7 promo half-sheet -**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. - ---- - -Zoom link: +Zoom link: https://duckduckgo.zoom.us/my/malex **Stakeholders and their responsibilities** -- Project Advisor: Noelia -- [Other stakeholders](https://app.asana.com/0/0/1207268731049844/f): Alessandro +- 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 **Scope updates** -- iOS port of the Android implementation. See [Android kick-off](https://app.asana.com/1/137249556945/project/72649045549333/task/1211002275165337) for the original — goal reminder, scenarios where users won't have seen the promo by day 7, and prior discussion there. -- Briefly note if you updated the scope significantly in preparation for this call, e.g., removed secondary goal of x. +- iOS port of the Android implementation. See [Android kick-off](https://app.asana.com/1/137249556945/project/72649045549333/task/1211002275165337) for the original. +- Pixels? **Discussion items** -- 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. -- Should we add Phase 1 instrumentation (pixels for users who haven't seen the paywall + Grafana boards), as Android did? Or is Android's data sufficient to validate the iOS opportunity without it? +- Who are the users targeted by this project? Scenarios where a user hasn't seen the subscription promo by day 7: (1) completed onboarding normally but the promo wasn't shown (e.g. installed before the onboarding promo existed); (2) skipped onboarding (reinstaller/returning user path — already covered by the existing reinstaller promo). Worth aligning on whether the scope covers both and how they're handled. +- Do we need to add a Grafana board to monitor the promo impression/tap/dismiss pixels? **Next steps** -- Add immediate next steps and their owners (ideally links to items in the task timeline)