Scaling standard work in large research institutions: Bridging the gap between IT strategy and technical execution

The challenge: Institutional inertia and tool resistance

In large-scale academic IT environments, leadership often mandates structured frameworks to ensure governance. However, technical teams frequently find traditional project management tools cumbersome, leading to "shadow work" or the use of static diagrams that quickly become obsolete.

For a major multi-campus institution undergoing a multi-phase database upgrade, the primary obstacle was not the technology itself, but the preservation of institutional memory and the elimination of communication silos. With over 40 project leads coordinating simultaneously, the risk of unmapped dependencies threatened to stall critical upgrades to financial aid and degree-tracking systems.

The solution: Building an operational twin

An operational excellence leader at the university implemented a "visual-first" approach. It was the most effective strategy to empower the team to take full ownership of their deliverables and drive technical excellence, ensuring a collaborative environment focused on high-quality results. 

• Visual dependency mapping: The team visualized dependencies across 40+ owners using color-coded cards and connection lines. This allowed for real-time identification of bottlenecks that would be invisible in a standard spreadsheet.

• The Jira bridge methodology: The visual layer serves as a buffer for change management. Technical teams interact with a drag-and-drop interface, while leadership maintains the governed data integrity required for the system of record.

• Centralized source of truth: By moving away from disparate planners and static files, the institution established a live calendar and roadmap that remains evergreen throughout the project life cycle.

Institutional outcomes

• Reduced friction: System administrators became active participants by using tools that mirror their natural mental models.

• Standardized governance: The transformation office achieved a unified view of the project portfolio without overwhelming staff with administrative overhead.

• Enhanced visibility: Cross-departmental syncs became more efficient, as the visual board allowed leaders to see the future state of the architecture before a single line of code was moved.

"I noticed some people were using visual collaboration tools, some weren't. But now I will say I'm using it every day in some capacity... I'm going to use it even more after this meeting." — Project head at a Tier 1 research institution