Start with the goal.
Build the plan around it.

Team invitations / Existing customers / First 14 days after launch

01 / You define the goal

Describe the change you want to see.

Give Skene the launch, its audience and the intended outcome. Start with your product goal, without having to name the events yourself.

Your launch brief

Help more invited teammates become active.

Target: 40% activation in the first 14 days.

02 / Skene drafts the journey and plan

Review the milestones and their requirements.

Skene uses the connected code and schema to map the journey. You review the draft plan. Each required milestone has available evidence or a named gap.

Skene drafts the measurement plan

Team invitations

For your review

Goal defined by your team

More invited teammates become active.

Audience: Existing customers
Target: 40% activation
Window: First 14 days after launch
Formula: Activated teammates / invitations sent

Skene connects two milestones: invitation sent and teammate activated.

03 / Your team reviews the tracking change

Complete the missing activation event.

Skene supplies implementation instructions. A coding agent prepares the new tracking. Engineering reviews and merges the change before releasing it.

Skene’s implementation requirement

Record teammate_activated when the invited teammate becomes active.

Output: a proposed change for engineering review

Adding an event that never existed is different from restoring a deleted tracking call.

The draft plan’s evidence requirements

01 / Invitation sentinvitation_sent

Found in code

02 / Teammate activatedteammate_activated

Required event missing

04 / Skene checks the required evidence

Confirm the data needed for the result.

After the change is released, Skene checks the requirement again. Code coverage and received events stay distinct. This later state has the data the formula needs.

After implementation, review and release

Both required events are received.

invitation_sent: Events received
teammate_activated: Events received

Skene can now use the available data in the plan’s success formula.

05 / Skene compares. Your team decides.

Read the result against the original target.

The first 14 days produce 482 activations from 1,248 invitations. Skene computes 38.6% against the 40% target. Your team decides what to adjust.

Skene compares the observed result with your target

Team invitations · First 14 days

Invitations sent1,248

Teammates activated482

Activation38.6%

Target40%

Cumulative activation rate

Target 40%

Release dayDay 14

Activations to date divided by invitations sent to date, within the first 14 days. The line illustrates this example’s progression.

Target not reached

1.4 percentage points below target. Your team decides what to try next.

One invitation per teammate. All 482 activations occur inside the same first 14 days after launch. Available tracking is not the same as an achieved target.

Product preview

Keep it measurable / After the first release

Later code change

The plan still needs the original event.

A renamed call can leave the experiment’s measurement incomplete. With pull request reviews enabled, Skene checks the change against the requirement.

Required event · teammate_activated

~~teammate_activated~~member_ready

Skene: required event name no longer matches

Engineering reviews the correction. Skene checks the corrected branch before the result is trusted.

Connect the source each stage needs.

Code supports the plan and review.

A linked repository lets Skene inspect tracking calls and review pull requests when enabled.

Explore connections

Data supports the measured result.

The success formula needs event or database data. Missing evidence remains unavailable rather than becoming a zero.

Read how measurement works

Bring your next release into focus.

Define the goal. Let Skene draft the plan.

Start with Skene

Follow one launch from its goal to its result.

Start with the goal.Build the plan around it.