Aglet

How to verify a useful first project empty state

Verification should prove that a first-time owner can move from a newly created project to the built-in check with one clear next action. Also test an established project with no current work so onboarding guidance does not overwhelm a returning user or imply that empty means broken.

Check whether the outcome improved

  1. Verify the new path

    Create a workspace and project from synthetic fixtures. Assert the page names the project, exposes setup or the next core action, and preserves context after refresh. Create the non-production test key and verify its one-time display rule and later metadata-only state.

  2. Verify built-in evidence

    Run the built-in check and assert the sample Signal and linked Work Item appear with explicit built-in labels and actionable links. Confirm a failed or pending check gives a truthful retry or status message rather than an empty success state.

  3. Verify established states

    Open a project with no sample or current work as owner and restricted role. Assert each empty state has appropriate guidance and no unauthorized action. Check narrow layout, keyboard focus, and readable link targets for the primary next step.

What to carry forward

Accept when a new project has a clear path to setup and labeled sample evidence, while established empty projects remain honest and scoped. Mark timing or producer behavior partial when the controlled fixture cannot prove it; do not imply external intake success.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow