The problem: every system held part of the truth
The laboratory's new head of digital transformation owned a problem familiar to every large technology organization. ServiceNow was becoming the system where work was supposed to live, but teams also worked in Jira, Azure DevOps, GitLab, spreadsheets, and Power BI. Each tool held a fragment of the truth. None of them could produce a trusted view from idea to demand to project to product to feature to outcome.
The gaps compounded. ServiceNow's demand form is powerful but heavy, so early-stage ideas often never entered the system cleanly. Leadership reporting was assembled by hand from exports and dashboards, and it was stale by the time anyone reviewed it. Then a first Snapshot looked at real capacity and found teams allocated at 180%: the same scarce experts promised to nearly twice the work they could possibly deliver.
What we did: become the connective layer, not another replacement
Iteright did not ask the laboratory to rip anything out. The goal was the opposite: make ServiceNow and the execution tools more useful by surrounding them with the governance layer they were missing. Working with the transformation leader, we defined the operating model, ingested the messy demand and project data behind it, and separated ideas from demands from projects, three categories the existing systems blurred together.
The result is a live portfolio view leadership can actually use: what teams are working on, which work is planned and which is unplanned, how work maps to strategic priorities, and where teams are drifting from the plan they committed to.
How we did it: start with application development governance
The first use case was deliberately concrete: application development governance. Iteright integrates with, or ingests exports from, ServiceNow and the execution tools, and adds the operating capabilities the stack lacked: lightweight idea intake that people will actually complete, structured validation, prioritization, roadmap alignment, and executive-ready reporting built from live data instead of hand-stitched summaries.
That gives leadership direct answers to questions they previously could not settle. What are teams actually working on? Which work should become a formal demand or project? How much capacity goes to planned work versus operational noise? Which initiatives align to strategic goals? And what should we stop, start, or accelerate?
The outcome: a Snapshot that became a production system
The entry point was a single Strategy Snapshot. Its findings were concrete, the 180% capacity picture chief among them, and the laboratory moved Iteright into production. The deployment is now expanding from one transformation team toward ten, following the arc set at the start: prove the model in one division in the first 90 days, then scale it across additional IT groups.
The trajectory points at something larger than one portfolio view: a standardized governance layer for the whole laboratory, a PMO-grade operating picture above the tools teams already use. Most large organizations already own ServiceNow, Jira, and a reporting stack. What they lack is the layer that connects those tools to strategy. That is the gap this deployment is closing.