Research
Ask whether account relevance can be explained through suitable sources.
Growth teams
Give the activity a question the evidence can answer.
Connect research, outreach, and content to one shared hypothesis. Define what each workstream can tell you, keep alternative explanations visible, and review the next decision together.
Example
experiment canvas
Does the evaluation question feel relevant?
- Hypothesis
- A defined engineering audience recognizes the incident-review question.
- Prepared action
- Research relevance and review one conversation angle.
- Measurement to define
- Eligible audience, response categories, and review period.
- Decision
- Refine the audience, wording, or next research question.
Example.
Agree on the evidence job before the activity starts.
Jalli's orchestration brings workstreams into the same plan. A useful review still needs definitions and responsibility.
Conversations
Inspect actual responses to the reviewed question and context.
Content
Notice which explanations prompt useful questions or misunderstandings.
Evidence and denominators
Define what a response means before comparing it.
Record the eligible population, exclusions, observation window, and response categories. Keep the numerator and denominator attached to a rate so a changed definition does not masquerade as a changed outcome.
Explore Analyticsmeasurement specification
Define the comparison before filling it in.
- Population
- Accounts meeting the reviewed audience criteria.
- Numerator
- Responses meeting the pre-agreed relevance definition.
- Denominator
- Eligible contacts in the same defined review window.
- Values
- Record the observed responses using the agreed definitions.
Example.
Cross-functional responsibility
Keep the hypothesis with every handoff.
Name who reviews account context, wording, and response interpretation. Send the next person the question and its limits alongside the prepared artifact, so each function contributes to the same learning decision.
Explore Workflowsexperiment handoff
A task keeps its evidence purpose.
- Research owner
- Reviews audience fit and source limits.
- Communication owner
- Reviews the angle and appropriate external conditions.
- Review owner
- Checks definitions, exclusions, and alternative explanations.
- Shared question
- Does the defined audience recognize this evaluation question?
Example.
Observation, explanation, and next test are different artifacts.
Keep what was recorded separate from the explanation and the next planned check.
Describe the record before interpreting it.
Record responses with the relevant population, definition, and period. Keep each observation tied to the records reviewed.
evidence view · Observation
What would the team record?
- Record
- Actual responses within the agreed review window.
- Keep attached
- Eligible denominator, categories, and exclusions.
- To record
- Responses observed during the review period.
- Review question
- Are the compared records defined the same way?
Example.
Example
Learning into the next plan
Change the brief when the evidence changes the decision.
Distinguish an observation from the explanation for it. Carry the reviewed learning and remaining uncertainty into the next hypothesis rather than treating completed activity as proof of progress.
Explore Growth strategynext-plan note
Retain the uncertainty with the learning.
- Inspect
- Observed responses using the agreed population and definitions.
- Challenge
- Audience, timing, delivery, wording, and missing information.
- Choose
- One bounded question for the next review.
- Avoid
- Claiming a single cause from a rate change alone.
Example.
Make the review useful to the next plan.
Carry the evidence, alternatives, and next question forward together.