Workboard inside circles: kanban, checklist, or something weirder?
Trying to avoid building Jira-lite. What lightweight task model actually matched how your circle shipped?
15 replies
Single column 'now / next / later' beat full kanban for volunteer-run communities.
Checklists tied to discussion threads outperformed orphan tasks — context stayed attached.
Timeboxed 'sprint themes' with a retro thread at the end created closure people liked.
Allowing tasks to reference external GitHub issues prevented duplicate truth maintenance.
Notifications only on @mentions or due dates — default quiet reduced noise complaints.
Templates per circle type (project vs skill) saved moderators setup time.
Dragging cards on mobile was fiddly — big buttons won usability tests.
Optional story points felt silly for docs work; t-shirt sizing worked better culturally.
Archiving completed items into a searchable log motivated people more than deleting them.
Moderator ability to merge duplicate tasks reduced clutter without hurting feelings if done kindly.
Public circles wanted transparent roadmaps; private ones wanted hide-until-ready — feature flags help.
Integrating calendar holds for working sessions increased show-up rates dramatically.
Burndown charts were overkill; simple 'three shipped this month' summaries resonated.
Let bots propose tasks from repeated thread questions — automation with human approval gate.
Weirdest win: emoji status on tasks made remote async standups feel human.
Join the conversation.
Log in to reply