SENAR Guide: Onboarding New Team Members
Reading Order
- Day 1 (30 min): Read SENAR Core — understand the 8 rules, 2 gates, verification checklist
- Day 1 (15 min): Read Guide Quickstart — internalize the 6 habits
- Day 2 (30 min): Read Guide Worked Example — see a complete task end-to-end
- Day 2 (20 min): Read Guide AI Review Checklist — your verification reference
- Week 1: Read Guide Tool Guides — set up your AI tool with SENAR practices
First Task Protocol
Your first SENAR task should be:
- Small scope — a bug fix or simple feature (< 1 hour)
- Paired with an experienced Supervisor who reviews your gates
- Full ceremony — do every step explicitly, even if it feels slow
Checklist for your first task:
- Write goal + acceptance criteria before touching code
- Define what’s in scope and what’s NOT
- Run Start Gate checklist
- Work with AI, noting any dead ends (> 15 min)
- Verify each AC with evidence
- Run Done Gate checklist
- Document any dead ends, decisions, or gotchas
Ramp-Up Timeline
| Week | Focus | Expected Outcome |
|---|---|---|
| 1 | Core rules + 2-3 supervised tasks | Understand the workflow |
| 2 | Independent tasks with post-review | Comfortable with gates |
| 3 | Full independence + checklist internalized | FPSR tracking meaningful |
| 4 | Knowledge contribution + peer review | Full team member |
Common New-Member Mistakes
- Skipping the negative scenario — Rule 1 requires at least one “what should NOT happen”
- Not documenting dead ends — Even “I tried X and it didn’t work” is valuable
- Treating the checklist as optional — Start with Standard tier every time
- Confusing exploration with implementation — Exploration is free, but committing requires a task
What NOT to Worry About
- Metrics (FPSR, Dead End Rate) — your first 10 tasks are baseline, not graded
- Perfect knowledge entries — any capture is better than none
- Speed — the process gets faster with practice, not by skipping steps