Team hackathon prototype
Mission Control: proactive insight
Mission Control interprets evidence across workplace systems and proactively raises alerts when something needs attention. It points towards agent workflows triggered by those findings.
Mission Control: proactive insight
A report still leaves someone to read through it and identify what needs attention. Our team built Mission Control for an internal hackathon to take that next step: infer what is happening across workplace systems and proactively raise an alert for investigation. One demo example is a commitment made in a meeting that never became tracked work. The alert brings the supporting records together so someone can understand the issue and respond.
The Programme Relationship Graph was an earlier step in that progression. I refactored it to infer relationships from live delivery evidence, so I could ask grounded questions about dependencies and risk. Mission Control moved from answering questions on demand to bringing issues forward without waiting for someone to ask.
The next stage is to use those findings as triggers for agent-assisted workflows. An alert could start work to gather missing context, prepare a response or coordinate follow-up, with review at the appropriate point. That changes the role of the system from presenting information to helping initiate the work that follows.
Status: Mission Control is shared hackathon work in a colleague's repository, using simulated data from Jira, Slack, Zoom, Confluence, Miro and GitHub. PRG is a self-used working prototype on live delivery data. Trigger-driven agent workflows are the next stage, not an operational capability.
View the simulated Mission Control demo →
