Nexus is a working data request intake and prioritization app — designed to make cross-team data workflows visible, structured, and trackable.
I built Nexus as a concrete demonstration of what a structured data request process looks like in practice. In most organizations without a formal intake layer, requests arrive through Slack, email, and hallway conversations — creating invisible queues, missed context, and frustrated stakeholders on both sides.
Nexus gives requesters a structured intake experience and real-time visibility into where their request stands. It gives Data Science, Analytics Engineering, and Data Engineering teams a shared queue with lifecycle tracking, risk flagging, and cross-team sign-off coordination. It gives leaders a clear picture of what's blocked, what's in flight, and what's coming next.
Building a process is ultimately about people and alignment — not software. But I've found that showing stakeholders what the end state looks like, concretely and interactively, is the fastest way to build that alignment. This is that artifact.
Requesters submit and track. Teams triage, sign off, and manage lifecycle. Admins have full access.
Submit data requests and track where they stand in the queue
Triage, review, and manage incoming requests across teams
Edit or delete any request — full access to all records
A four-step intake form captures the business domain, request type, priority, target date, known risks, and cross-team dependencies — turning informal asks into structured data.
Requesters see exactly where their work stands — queue rank, lifecycle stage (Triage → Inflight → Complete), and whether anything is blocked. No more chasing Slack messages.
Each request tracks approval status from Data Science, Analytics Engineering, and Data Engineering independently — surfacing sign-off gaps before they become delivery blockers.
Teams can flag requests as High, Medium, or Low risk, and mark requests as blocked with a written note — giving leadership the context they need to intervene early.
A shared milestone calendar lets teams mark planning windows, delivery dates, freeze periods, and reviews — connecting individual requests to the broader data delivery rhythm.
Three distinct roles — Requester, Data Team, and Admin — with different views and permissions. Admin requires a passphrase and enables full edit and delete capability.