Public Roadmap
How Shape Up cycles work at ɳSelf and how to follow what we are building.
ɳSelf publishes its roadmap at nself.org/roadmap. We use the Shape Up methodology developed by Basecamp.
What Shape Up means
Most product roadmaps are infinite backlogs dressed up as plans. Shape Up is different. Every 6 weeks, the team picks a small set of bets, features we commit to completing in that window. If a bet does not ship, it is cut, not deferred. The next cycle starts fresh.
| Term | Meaning |
|---|---|
| Bet | A feature ɳSelf commits to ship this cycle |
| Cycle | 6-week build window |
| Cooldown | 2-week buffer after each cycle for fixes and admin work |
| Pitch | One-page write-up explaining why a bet is worth the cycle |
| Appetite | Max time ɳSelf will spend: S = 1-2 days, M = 1 week, L = 2-3 weeks |
| Cut | A bet not finished by cycle end, labeled honestly, not silently deferred |
Cycle calendar
| Cycle | Build window | Cooldown |
|---|---|---|
| Q2 2026 Cycle 1 | Apr 28 – Jun 8 | Jun 9–22 |
| Q2 2026 Cycle 2 | Jun 23 – Aug 3 | Aug 4–17 |
| Q3 2026 Cycle 1 | Aug 18 – Sep 28 | Sep 29 – Oct 12 |
Community bets
High-vote bounties from nself.org/bounties surface on the roadmap as Community Bets when the ɳSelf team officially accepts them into a cycle. Community Bets are labeled on the roadmap and link back to the originating bounty.
RSS feed
Subscribe to shipped bets at /roadmap/feed.xml. Every time a bet ships, a new entry
appears in the feed with a summary and a link to the release.
What you will not see
- Infinite backlogs
- “Coming soon” columns with no dates
- Requests that “are on the roadmap” but never ship
If something is not in an active or upcoming cycle, it is not a current commitment. That honesty is the point.