We’ve built Neo.Tax to handle your data no matter how messy it is. Our system can work even better by following a few simple practices.

This guide can help you improve ticket management practices to produce more accurate projects and time allocations in Neo.Tax.

The three top tips:

1. Epic/Project names should describe the actual goal

   1. "Banking - New 1099 Filing Features" not "Banking Work"

2. Ticket titles should explain what you're building

   "Move MongoAuthProcess into driver source tree to increase stability" not "Auth fixes"

3. Always move tickets to "In Progress" when you start work

   1. Skipping this step makes your team look less productive than they are and breaks time tracking

For more specific tips, check out the relevant section below.

1. Team/Project Organization

Core Principles

• Use Projects (JIRA) / Teams (Linear) to organize work by team boundaries
• Rationale: Clean team separation leads to better project outcomes and clearer ownership
• Scale appropriately: Companies with 20+ engineers should maintain multiple projects/teams that grow with organizational size
• Align with business structure: For R&D teams, map projects to actual business products or product groups when possible

2. Epic/Project Naming & Structure

Structure and Naming