Sprint board with your columns
To do, In progress, In review, QA, Done, or whatever your process actually is. Priority, assignee, due date and custom fields like story points on every ticket.
Feature details
Software & product teams
Ship the release, not the status meeting.
Engineering teams have the worst case of tool sprawl: a tracker, a wiki, a chat app and an AI that has seen none of them. Tenon puts the spec next to the ticket, the decision next to both, and an assistant that can tell you what is actually stuck.
Recommended: Tenon Cloud Team, or self-hosted Pro
1,200app switches / day
The average digital worker toggles between apps roughly once every 24 seconds. Developers, with a tracker, a wiki, chat, CI and an editor open, are the worst affected.
Source: Context Switching Statistics 2026
What goes wrong today
The three problems we hear most from software & product teams.
- The spec drifted from the ticketThe design doc lives in a wiki, the work lives in a tracker, and when they disagree the ticket wins. Six months later the wiki is fiction.
- "Are we on track?" has no honest answerA card that has sat in In Progress for nine days looks exactly like one moved there this morning. Percent-complete hides uncertainty.
- Decisions evaporate in chat"We agreed that in Slack" is followed by twenty minutes of scrolling. The new hire builds what the spec said, not what the thread decided.
How Tenon fits
Four things that change on day one.
Hill charts for the messy middle
Uphill means the approach is still unknown; downhill means execution. A scope stuck uphill for two weeks is the real agenda item, and the chart makes it visible.
Feature detailsDesign docs inside the project
Write the RFC as a page, link it from the tickets it spawns, and see backlinks so you know which tickets still depend on it before you edit.
Feature detailsBrain reads the sprint
Ask "what is blocked on the payments epic?" and get the tickets, owners and last comments. Draft the follow-up tickets from the retro conversation in one click.
Feature details
In the product
What it looks like for software & product teams.
Sprint boardCustom columns, priorities and the stuck flag, on one board.
Strategy viewWhere each scope really is: still being figured out, or being executed.
AnalyticsBurndown and workload feed the AI status report.
Three projects, ready to copy
How to set up the board, the fields and the pages.
These are complete configurations, not suggestions. Create the project, add these columns and custom fields, create the pages, and the rituals column tells you which Tenon features carry the week.
Two-week sprint
Deliver the committed scope with visibility on what is stuck.
Board columns
- Backlog
- To do
- In progress
- In review
- QA
- Done
Custom fields
- Story points (number)
- Epic (select)
- Environment (select)
Pages
- Sprint goal
- Retro notes
- Definition of done
Rituals
Async standup every weekday at 9:00 with an AI digest posted to #team-platform. Stuck-ticket flag reviewed at the Wednesday check-in.
Feature RFC to release
Take a large feature from proposal to shipped without losing the reasoning.
Board columns
- Proposed
- Shaping
- Building
- Verifying
- Shipped
Custom fields
- Target release (text)
- Risk (select: low, medium, high)
- Customer ask (text)
Pages
- RFC
- Rollout plan
- Release notes draft
Rituals
Hill chart reviewed weekly. Decisions recorded as decision cards in #feature-payments and linked to the RFC page.
Incident and postmortem
Run the incident in one channel and turn the postmortem into tracked actions.
Board columns
- Triage
- Mitigating
- Root cause
- Action items
- Closed
Custom fields
- Severity (select)
- Customer impact (text)
- Detected by (select)
Pages
- Incident timeline
- Postmortem
- Runbook updates
Rituals
Incident channel per event. Brain drafts the action-item tickets from the postmortem page; owners and due dates set before the channel is archived.
A week with Tenon
What Monday, Wednesday and Friday look like.
- Monday: the sprint board is open. Two tickets carry the stuck flag from last week. Maya reassigns one, adds a due date, and drops a comment. Brain writes the morning briefing: one overdue, two in review, the burndown slightly behind.
- Wednesday: the hill chart shows the offline-sync scope still uphill. That becomes the one agenda item for the sync. The decision (defer conflict resolution to the next sprint) is recorded as a decision card and linked to the RFC.
- Friday: the standup digest lists what shipped, what is blocked and who has not submitted. Maya clicks Generate status report, edits one sentence, and posts it to #leadership as a page card. No slide was made.
Illustrative scenario based on how teams in this sector describe their week.
Questions
Common questions from software & product teams.
Can we import from Jira or Linear?
Pages import from Word and PDF today. For tickets, the REST API and webhooks are the path, and Team and Enterprise customers get migration help. Tell us what you are moving from.
Does Tenon integrate with GitHub or CI?
Through webhooks and the REST API. Native Git integrations are on the roadmap; the API is versioned so what you build today keeps working.
Can Brain see our code?
No. Brain reads projects, tickets, pages and conversations in Tenon, with the same permissions as the person asking. It does not connect to repositories.
Other industries
Similar problems, different vocabulary.
Set it up for your team this afternoon.
Start free on Tenon Cloud, or self-host it. Copy one of the project setups above and you have a working board in ten minutes.