We're a small but fast-moving team building internal tools for a healthcare practice. The pace is wild—doctors need a new report view yesterday, compliance flags a data mapping issue that needs an urgent fix, and the board wants a demo of the new patient portal next week. Our old Trello board was a well-intentioned graveyard of stale cards. We've tried Jira (too heavy), GitHub Projects (felt bolted-on), and even a frantic Slack channel pinned with messages (do not recommend 😅).
The core tension: we need **rigor** for audit trails and to avoid dropping critical tasks, but also **speed** to match the clinical team's operational tempo. Things *have* to be traceable, but ceremony kills us.
I'm curious about teams in similar high-stakes, high-velocity environments. What actually stuck?
* Did you land on a specific tool (ClickUp, Linear, Asana) that balanced simplicity with enough structure?
* How did you model your workflow? We're thinking: `Triage` -> `Sprint Backlog` -> `In Progress` -> `Review/QA` -> `Done`, with a separate lane for `Urgent/Production Incidents`.
* More importantly, how did you get the *whole team*—developers, QA, and non-technical stakeholders (the doctors and admins)—to actually *use* it without constant nagging?
Here's a snippet of how we're currently trying to enforce some workflow in our scripts, which feels like a band-aid:
```python
# check_pr_for_ticket.py - a pre-commit hook-ish script
import sys
import re
branch_name = sys.argv[1]
# Enforce branch name like "PROJ-123-fix-thing"
if not re.match(r"^[A-Z]+-d+-.+", branch_name):
print(f"ERROR: Branch '{branch_name}' doesn't follow PROJ-123-desc format.")
print(f" Please link to a task in the board.")
sys.exit(1)
```
This feels clunky. I'd love to hear migration stories—not just the tool you picked, but how you handled the cutover without drowning in-flight work.