تخطَّ إلى المحتوى

Public Roadmap

هذا المحتوى غير متوفر بلغتك بعد.

ɳSelf publishes its roadmap at nself.org/roadmap. We use the Shape Up methodology developed by Basecamp.

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.

TermMeaning
BetA feature ɳSelf commits to ship this cycle
Cycle6-week build window
Cooldown2-week buffer after each cycle for fixes and admin work
PitchOne-page write-up explaining why a bet is worth the cycle
AppetiteMax time ɳSelf will spend: S = 1-2 days, M = 1 week, L = 2-3 weeks
CutA bet not finished by cycle end, labeled honestly, not silently deferred
CycleBuild windowCooldown
Q2 2026 Cycle 1Apr 28 – Jun 8Jun 9–22
Q2 2026 Cycle 2Jun 23 – Aug 3Aug 4–17
Q3 2026 Cycle 1Aug 18 – Sep 28Sep 29 – Oct 12

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.

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.

  • 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.