Blog / Company
How we run our own projects with clarity and focus
Ethan Calloway ·
We run neevio on neevio. Every initiative is broken into epics and issues, scheduled against real capacity, and reported by the system rather than by people. The weekly status meeting was deleted two years ago and has not been missed.
One system, not four
The most expensive thing a small team can do is spread its work across a planning tool, a docs tool, a code review tool, and a chat app, then spend its Mondays reconciling them.
Everything we ship starts as an initiative, breaks into epics and issues, carries its spec beside it, and closes when the pull request that references it merges. No re-entry, no summarising one tool into another.
How we killed the status meeting
Status meetings exist because nobody trusts the tool to be current. Fix the currency problem and the meeting has no reason to exist.
Project updates are written where the work happens, and progress reports itself from what actually changed. The hour came back, and so did a few nobody was counting.
The rules we actually keep
Short list, kept deliberately short:
- If it is not an issue, it is not work.
- Every issue has one owner, not a team.
- Specs live beside the work, never in a separate wiki.
- A cycle is time-boxed. Scope moves; the date does not.
- Anything discussed twice gets written down once.