Move an idea through Helix

Understand loops and hypotheses

A loop groups work around a goal. A hypothesis states what capability you expect to improve, how you will measure it and what outcome matters.

Helix moves hypotheses through ten stages: Vision, Discover, Design, Build, Test, Evaluate, Secure, Release, Observe and Learn. Each stage has checks that help your team decide whether the work is ready to move forward.

Create a loop

1. Open Helix in your workspace.
2. If your role permits it, choose New loop.
3. Enter a name and a Loop Goal that explains what the loop should prove.
4. Choose Create loop.

The loop goal can be edited later, but AI Planning needs a goal before it can complete.

Write a testable hypothesis

In a loop, choose New hypothesis. Enter a title, then complete the capability, Measured by, Will reach and Producing fields. Add a Kill criterion that states when to stop or rethink the work.

Choose the appropriate risk tier and uncertainty classification with your team. Start the hypothesis with Start → Vision when it is ready to enter the workflow.

Work through the gates

Open a hypothesis’s Gate panel to inspect its checklist. Gather the required evidence and complete the checks your role permits. Use Advance when the stage is ready.

If advancement is blocked, read the missing checks or rule failures in the panel. Some steps require more than a checked box: review records, evaluation results or authorized security sign-off may be needed. The Test gate can also be blocked by open critical or high defects.

Work-in-progress limits keep stages from becoming overloaded. Gate waivers and limit overrides are permission-controlled; a waiver can expire and block progress again.

Review and learn

Use Planning to organize upcoming work and Review to examine hypotheses that have reached Learn. Capture the outcome and what your team learned before planning the next loop.

Helix’s navigation also brings together Backlog, Prompts, Models, Golden Sets, Knowledge, Agents, Releases, KPIs, Risks, Defects, Incidents and Portfolio. Use the areas relevant to the evidence and operations your project needs.

Understand access

Creating loops, editing hypotheses and approving specialist checks depend on your workspace role and Helix permissions. If a control is unavailable, ask your workspace lead to review the access required for that action.