Method
How Signal sees the work.
Three systems run continuously. Together they read the state of your work and write a briefing that tells you what to do, not what happened.
Attention Engine
Most systems tell you everything that happened. The Attention Engine tells you what matters from what happened. It runs continuously across every project, task, and team activity — not on rules you write, but on patterns it recognises. Overloaded individuals. Dependencies that have stalled. Projects that have gone quiet without resolution. Work moving faster than expected in the wrong direction. The output is a ranked view of what deserves your attention today.
Blockers: tasks waiting on something with no resolution in sight
Stalled work: open items with no recent activity or ownership
Dependency failures: downstream work blocked by upstream inaction
Workload concentration: too much live work sitting with one person
Momentum shifts: projects accelerating or decelerating sharply
Missed deadlines: due dates passed with no completion or update
Inactive projects: open scopes with no movement in 7+ days
Bottlenecks: recurring patterns of work stopping at the same point
Plain-English Insights
The briefing is written in sentences a person would write. Not "velocity delta of -14%" but "this project is slowing down". Not "resource utilisation at 87%" but "too much work landed this week". The translation is not cosmetic. It forces the system to form an actual view of the work, not just surface a number and leave interpretation to you. If the system cannot say it plainly, the insight is not ready.
Plain sentences, no jargon or metric names
Active voice: "this project is blocked" not "blockage detected"
Cause included: what is blocked, and why it matters
No FYI items: if it has no consequence, it is not written
Confidence calibrated: uncertain signals are held back, not hedged
Priority Compression
The goal is not completeness. A list of 84 open tasks is not a briefing. Priority Compression takes everything the Attention Engine surfaces and reduces it to the three to five things worth acting on today. The compression is deliberate — it considers urgency, consequence, and reversibility. A blocked task that will cascade is surfaced over a late task that can be rescheduled. A quiet risk that is growing is surfaced over a completed item that underperformed slightly.
Maximum of three to five items per briefing block
Urgency weighted against consequence, not just due date
Reversibility factored: high-consequence, low-reversibility items ranked up
Cascade potential: blockers that will fan out are prioritised
Noise suppressed: minor variances and expected delays filtered out
No configuration. No dashboards. Nothing to set up. The Signal reads your work and writes the briefing.
Private beta
Signal is in private beta. Request access.