Core Definitions

Purpose: Standardize key terms so teams can execute without ambiguity.

Outcome

Shared vocabulary across startup teams, program managers, and mentors.

Canonical definitions

• Assumption: A belief that must be true for the initiative to succeed. Assumptions are where uncertainty starts. They matter because teams often carry them implicitly and then act as if they were already proven.

• Hypothesis: A testable statement derived from one assumption. A hypothesis translates belief into something measurable. It creates the bridge between uncertainty and testing.

• Experiment: A structured test that can validate or invalidate a hypothesis. An experiment is not just action. It is action designed to generate evidence that informs a decision.

• Learning: A documented takeaway from experiment evidence. A learning is what changed in the team’s understanding because of evidence, not because of preference or interpretation alone.

• Insight: A synthesis of one or more learnings that informs a decision. Insights connect individual learnings to broader meaning, implications, and possible next moves.

• Decision: A clear commitment (go, iterate, pivot, stop) based on insights. A decision closes the loop. It turns knowledge into action, ownership, and direction.

Distinctions that reduce rework

• Assumption is not hypothesis.

• Activity is not experiment.

• Opinion is not learning.

• Summary is not insight.

Why these distinctions matter in practice

These distinctions are not semantic preferences. They directly affect speed and quality.

• If a team treats an assumption like a hypothesis, it may never design a clean test.

• If a team treats activity like experimentation, it may complete a lot of work without learning anything useful.

• If a team treats raw observations like learnings, it may overstate what the evidence actually supports.

• If a team treats a summary like an insight, it may sound thoughtful without actually clarifying a decision.

• If a team treats discussion like a decision, it may leave meetings with no ownership and no clear next step.

Common confusion points

Assumption vs hypothesis

An assumption is what must be true. A hypothesis is how you will test whether that assumption appears true.

Experiment vs activity

An activity becomes an experiment only when it has:

• a clear hypothesis,

• an expected outcome,

• a defined signal or result,

• and relevance to a decision.

Learning vs observation

An observation is something noticed. A learning is what the team can responsibly conclude from evidence.

Insight vs decision

An insight explains what the learnings mean. A decision defines what the team will do about it.

What good looks like

At this stage, good looks like a team that can look at any artifact and answer:

• What kind of artifact is this?

• What stage of the loop does it belong to?

• What should come next?

• Is it strong enough to move forward?

Definition of done

• Team can classify work artifacts correctly.

• Team can explain the loop using canonical terms.

Next step

Continue to Learning System Overview.