← All kits · SQL Plan Builder
A short SQL plan, built around your goal
Answer four quick questions. You get three, five, or seven short days of work, each inside an hour, and every step tells you why it is there. The last day ends with a win you can say out loud.
Your wins
Earned, not given. They stay here between visits.
Four questions
Pick one answer in each row. The plan builds itself below.
Where is your SQL right now?
What kind of work do you want it for?
How long a run?
When in the day will you actually do it?
No idea what to pick? Let the planner deal you a hand. Every combination is a real plan.
Why the planner works the way it does
- It asks when, not just what. People who wrote down a date and a time for a task followed through at meaningfully higher rates than people who just intended to do it; date alone was not enough (Milkman and colleagues, 2011; Gollwitzer and Sheeran, 2006).
- Your progress bar never starts at zero. In a classic field test, people handed a card with two stamps already on it finished at 34 percent versus 19 percent for an empty card with the same real work left (Nunes and Dreze, 2006).
- The five and seven day runs include one emergency skip. A hard goal with explicit slack built in beats both an easier goal and a rigid one, and a slip stops being a reason to quit (Sharif and Shu, 2017).
- A missed day is never shown as failure. Research on streaks finds that showing people a broken streak suppresses the behavior itself, while repairable misses do not (Silverman and Barasch, 2023). One missed day also does not damage an emerging routine (Lally and colleagues, 2010).
- Wins are recognized after you do the work, never dangled before it. Expected do-this-get-that rewards measurably undermine interest in the task itself; recognition of demonstrated skill strengthens it (Deci, Koestner and Ryan, 1999).
- Every day after day one starts by retyping from memory. Pulling yesterday's query back out of your head is retrieval practice, the most reliable finding in learning science.