What a good roadmap does
A roadmap converts weak signals into calendar actions. It should be specific enough that you know what to do today without deciding from scratch.
Build your roadmap in 4 steps
- Pull weak patterns from Dashboard.
- Pick 2 primary patterns for the next 2 weeks.
- Assign exact session blocks in Practice.
- Add one review checkpoint every Sunday.
Recommended weekly split
| Day type | Focus | Session length |
|---|---|---|
| Build day | New/weak pattern reps | 30-45 min |
| Reinforce day | Repeat solved pattern with less help | 20-30 min |
| Simulate day | Timed interview-style session | 35-45 min |
Keep roadmap quality high
- Limit active patterns (2-3 max per cycle)
- Write measurable targets ("2 medium sliding-window problems")
- Avoid vanity goals ("solve 40 random questions")
FAQ
Should I plan by company list or by pattern list?
Start by pattern list. Company-style rounds mostly test the same pattern families under different wording.
How often should I rewrite roadmap?
Weekly is enough. Daily rewrites usually indicate over-optimization.