The operating model
How a fictional team could define ownership and review rituals around this system.
The original version has 2 updates your draft doesn’t have.
Northstar Systems2026Draft narrative7 min read
Turning migration signals into a useful path forward
I connected an observable customer behavior to a small, reusable intervention the team could test without disrupting the core journey.
Synthetic editorial fixture. No customer or production data is shown.
- Role
- Design lead
- Team
- Growth · Platform · Content
- Timeline
- Two-week prototype
- Scope
- Three eligible surfaces
The audience was active, but the migration path was easy to miss
Show me the next useful step without taking over the page.
Meet the cohort in context without competing with the page
Reuse the existing targeting layer
Known inputs
The audience query and eligible surfaces already existed.
Design rationale
A small prompt could connect an existing visit to the right guidance.
My contributionI shaped the intervention and aligned the page-level trade-offs.
Key insight
The cohort skipped migration guidance but kept exploring the rest of the site
What we learned
Why it mattered
Friction
- Existing visits
- Audience match
- Relevant prompt
- Migration guidance
Map existing visits
Identify the pages the cohort already used.
Confirm eligibility
Narrow the list to surfaces that support targeting.
Align owners
Agree on placement, timing, and disruption limits.
Acquisition system · conceptual reconstruction
One prospect signal, carried through the system
The launch experience connected a public CTA to capture, operational handoff, scheduling, and a human conversation.
Framer website boundary
- 01
Prospect intent
Website CTA
A prospect chooses to begin from an Arca page.
In Framer - 02
Capture
Typeform
Contact and qualification details are collected.
- 03
Operational handoff
Lead ingestion
The submitted lead moves into downstream operations.
- 04
Routing
Cal.com
Scheduling and advisor routing return inside the site.
In Framer - 05
Human outcome
Advisor conversation
The digital journey resolves into a matched conversation.
Known handoffReconstructed relationship
Known tools and handoffs are based on the launch account. Sequence and system boundaries are reconstructed for explanation; no CRM vendor or production data model is implied.
Design one adaptable system instead of several isolated screens
Prompt within the page
Embedded walkthrough
Design leadSystem and alignment
Platform
Targeting capability
Page owners
Context and constraints
Content
Message quality
The team left with a testable system and explicit evidence boundaries
1 system
adaptable across three surfaces
Measurement plan ·
2 weeks
from brief to implementation-ready prototype
Shipped ·
Synthetic fixture outcomes demonstrate the editor without claiming production performance.
- I led
- Experience strategy
- Cross-team alignment
- I made
- Reusable interaction pattern
- Partners
- Platform team — Targeting infrastructure
Implemented
Reusable interaction pattern
Influenced
Cross-team review rhythm
Partnered
- Platform team
- Targeting infrastructure
Before
After
Before
After
Before
After
Final
Before
After
Final
| Signal | Before | After |
|---|---|---|
| Prompt seen | Rarely | Every visit |
| Next step | Unclear | One click |
{
"surface": "product-page"
}More we can talk about
A few adjacent decisions are better unpacked in conversation than compressed into this case study.
Evidence boundaries
How to separate observed signals, assumptions and a future measurement plan.
Cross-team alignment
A walkthrough of the synthetic facilitation approach used in this fixture.
Define measurement language before launch
The next iteration would align event definitions and reporting windows before the implementation begins.
Made with
- Synthetic cross-functional teamFixture collaborator