Where should other PostHog products hand people to Workflows? #218

Activity

1. Silthus

   added

   wayfinder:research

   on Oct 3, 2026
2. Silthus

   added a parent issue on Oct 3, 2026

   • Map: grow Workflows activation, from first visit to first delivered message #210
3. Silthus

   marked this as blocked on Oct 3, 2026

   • What should a paying team's first ten minutes in Workflows feel like? #212
4. Silthus

   marked this as blocking on Oct 3, 2026

   • Rank the growth bets and choose which get their own map #219
5. Silthus

   self-assigned this

   on Oct 5, 2026
6. Silthus commented on Oct 5, 2026

   

   Silthus

   on Oct 5, 2026

   OwnerAuthor

   More actions

   Answer

   Rank the hand-offs by how much intent the source page already carries. Pages that already name an audience or a trigger come first. Generic discovery surfaces come last. Every hand-off lands in the accepted first run (#212, built in #253) and skips only the choice the source page already made.

   Ranking is reasoned, not measured. It assumes the first run in #253 exists. Effort sizes are guesses.

   Rank	Entry point	Effort	Pre-fill	Why here
   1	Saved cohort	S	batch trigger + cohort audience	"Message this cohort" already exists in CohortEdit.tsx; needs the new landing and a guard for behavioral cohorts
   2	Support notification settings	S	the card's support event	the cards in NotificationsSection.tsx name an event but link to a blank workflow
   3	Event and action pages	S	event/action trigger	next to the replay hand-offs in DefinitionView.tsx and ActionEdit.tsx; ActionEdit already records cross-product intent
   4	Insight people / funnel drop-off	M	static audience snapshot + recovery starter	PersonsModal already builds a static cohort from the actors query
   5	Survey responses	M	survey sent trigger for future responses, or a snapshot for past ones	must settle past vs future responders
   6	PostHog AI suggestions	M	proposed trigger, audience and starter	AI creation today skips "Make it yours" and goes straight to the editor
   7	Early access rollout	M	enrollment-property audience + announcement starter	enrollment property key exists
   8	Feature flag rollout	M	an explicit eligibility or exposure snapshot	evaluated users differ from eligible users, so the audience meaning must be explicit
   9	Global New menu	S	nothing, the event-filtered gallery	explicit creation intent, no context
   10	Product recommendations	M	a starter only when the project's events support it	weaker intent
   11	Sidebar	S	nothing	discovery only

   Gaps the hand-offs need first

   These matter to the first-run build (#253) too:

   • Template plus trigger pre-fill. The new-workflow route takes templateId and a validated trigger, but template loading returns before the trigger pre-fill applies (workflowLogic.ts). A hand-off cannot combine a starter with its source's trigger or audience yet.
   • Event-aware gallery. The template gallery filters by search and tags (workflowTemplatesLogic.ts), not by what the project's events can drive.
   • Behavioral audiences. There is no cohort-entry or inactivity trigger, and batch audiences reject behavioral cohorts (hog_flow.py). Rank 1 and 4 hand-offs need static cohorts or a guard. See What would it take to let behavior drive Workflows? #215.

   Product intent

   Only the list page's "New workflow" button records Workflows product intent (WorkflowsScene.tsx). These paths create workflows without it:

   • the empty-state CTA;
   • blank, template and direct-editor creation;
   • the cohort and support links;
   • the Customer Analytics hand-off;
   • duplication;
   • the Broadcast wizard;
   • API, MCP and AI creation;
   • desktop loops.

   Recommendation: record intent once, after a workflow is created successfully, with the source product attached. Measure activation as a delivered message, not as an active workflow. Today the activation check (facade/api.py) only asks whether an active workflow exists.
7. Silthus

   closed this as completedon Oct 5, 2026