Predictive Signals
How StartConsole detects risks before they happen and what to do when a prediction appears.
Predictive signals flag issues before they become problems. While standard signals react to conditions that already exist, predictive signals analyse trends and project forward — giving you time to act.
How predictive signals work
StartConsole monitors five types of trends across your portfolio:
- Velocity decay — delivery progress is slowing across consecutive periods. If the trend continues, the initiative may miss its target date.
- Budget burn projection — at the current spending rate, the budget will be exhausted before the work is complete.
- OKR trajectory — key result progress is not on pace to reach the target by the end of the quarter.
- Dependency cascade — a dependency your initiative relies on is itself at risk, which may block your work.
- Owner inactivity trend — the initiative owner's activity is declining, which may signal disengagement before it becomes critical.
Recognising a predictive signal
Predictive signals appear alongside standard signals on the Signals page. Look for the Predicted badge — this distinguishes them from reactive flags.
Each predictive signal includes:
- A description of what was detected and why it matters
- A projected impact date — when the issue is expected to materialise if the trend continues
- A confidence level — based on how much historical data supports the prediction
Acting on predictions
Open the affected initiative and review the area the signal highlights. For a velocity decay prediction, check deliverable progress and upcoming deadlines. For a budget burn projection, review the Budget tab and consider reallocating or descoping.
Predictive signals resolve automatically when the underlying trend reverses — for example, if delivery velocity recovers over the next two computation cycles.
Predictive signals are available on Growth and Enterprise plans. They appear in the Signals tab of your My Work page for initiatives you own.