How SRP thinks about work
Several things in SRP look wrong at first if you come from another tool. No health on a project. No “on track” or “at risk” you can set by hand. No per-seat price. Each one follows from an idea below.
Push, not pull
Section titled “Push, not pull”Most project tools hold the answer and wait for you to dig it out. SRP computes the answer and brings it to you: what is slipping, and why. You should not need a status meeting to learn what your own tool knows. Pull vs Push.
Typed status is always late
Section titled “Typed status is always late”A status field only changes when a person changes it, and a person changes it after the fact. So SRP does not ask anyone to type “at risk”. It derives risk from due dates, owners, blockers, linked issues and capacity, while there is still time to act. Why Your Tool Can’t Warn You Early.
Everything must be in
Section titled “Everything must be in”A computed signal looks current even when the data under it is missing. A person you left out, a project you did not add, a subcontractor with no account: each one is a hole, and a picture with holes is worse than none because you trust it. This is why members without sign-in are free and unlimited, and why only sign-ins are priced. Green Because Fine, or Green Because Blind?.
Health lives where there is a deadline
Section titled “Health lives where there is a deadline”Only things with a date and a boundary can be late: iterations, work items, initiatives. A project is a folder. Giving it a health would turn it into a permanent red count. The work model.
Less surface
Section titled “Less surface”Every view, field and module you do not use is still in the way. SRP ships the set a small team needs to run work and watch it, and stops. A tool the team quietly stops opening is worse than no tool. Every Feature You Don’t Use Is Still in Your Way.
The longer version is Why I built SRP.