Aglet

What to learn from an empty project onboarding checklist

The durable lesson from an empty first project is that blankness needs a truthful state and a specific next action. Preserve the distinction between a newly created project, a completed built-in check, and an established project with no work so future empty-state copy remains useful without inventing activity.

Keep the lesson for the next incident

  1. Write the project contract

    Document the states for project creation, setup progress, test-key metadata, built-in check result, and established no-work. Name the action available from each and explain how sample Signal and Work Item evidence is labeled. Keep role limits explicit.

  2. Keep first-use fixtures

    Save synthetic journeys for new workspace, new project, key creation, built-in check success, check failure, restricted role, and established empty project. Assert heading, next action, context, and evidence labels without using customer payloads or production credentials.

  3. Define recurrence signals

    Reopen review when a newly created project loses setup guidance, a sample result is unlabeled, an empty state links to another context, or a restricted role sees an unauthorized action. Record viewport and timing limits and assign an owner.

What to carry forward

Close learning with explicit project states, first-use fixtures, role boundaries, and recurrence triggers for blank surfaces. A clear empty page should remain distinguishable from a failed check or an unobserved external intake path for future reviews.

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