Back to all case studies

Turning a Black-Box Legacy System into a Company-Wide Delivery and Support Operating System (Jira Cloud)

Snapshot

Delivery model: Principal-led engagement (Stefan, Founder & Principal Consultant) Client: Ironbridge ERP (German ERP vendor for equipment trade and rental) A mid-market German ERP vendor serving industrial equipment trade and rental modernised its internal project and service-case management after years of ad-hoc, interrupt-driven work and low organisational IT maturity. Vionix led a five-month engagement (2-month development pilot + 3-month company rollout) with a 35-person organisation and handed over full administration at the end.

The Challenge

The client relied on an in-house management system for project work and service cases that forced unrealistic 15-minute time tracking and encouraged shadow processes like paper notes and batch-entered time blocks, so reported effort didn't match reality.

Change documentation was effectively manual and frequently skipped, leaving developers with little visibility into colleagues' work and creating a siloed "everyone works in a black box" dynamic.

Support intake and assignment lacked consistent triage and transparency: tickets could be self-classified (new vs duplicate), assigned arbitrarily, then disappear, forcing repeated customer explanations and constant manual chasing of blockers.

Constraints

The company culture was heavily sales-led, with limited engineering and project-management expertise across leadership, which made governance and prioritisation hard to sustain.

The initial mandate was to modernise development without formally redesigning support and consulting processes, even though the pain spanned the whole operating model.

The legacy system was also not tamper-resistant (anyone could edit or delete history), which had created a print-and-archive culture to protect against manipulation and disputes.

Approach

1. Diagnose the real operating model: Conducted interviews and meetings across teams to confirm that project and service management, not coding practices alone, was the core bottleneck.
2. Run a controlled pilot in development: Introduced Jira Cloud as the source of truth for delivery, while dual-running the legacy system only for intake and closure marking during the pilot.
3. Reduce friction and increase traceability: Trained developers to link version-control commits directly to Jira issues, replacing manual write-what-you-changed admin work with auditable workflow.
4. Make prioritisation a daily, explicit decision: Implemented short daily briefings to review and reorder priorities so developers could plan their day and work with fewer interruptions.
5. Stop drive-by tasking: Established strict routing rules. Support, sales, and consulting could not assign work directly to developers; requests went through development leadership and Jira.
6. Align business and engineering daily: Set up a daily coordination meeting between development leadership and sales and consulting leadership to reconcile customer reality with delivery capacity.
7. Fit Jira to reality: Iteratively tuned Jira workflows during the pilot to reflect how work actually moved through the organisation.

Delivered artifacts included the Jira Cloud configuration and training materials (presentations used for internal enablement sessions).

What Was Delivered

• Jira Cloud operating model: End-to-end company rollout replacing the legacy internal management system.
• Workflow governance: Routing and prioritisation rules that removed direct developer interruption patterns.
• Traceable delivery process: Commit-to-ticket linkage and auditable work history for development and service work.
• Enablement artifacts: Training sessions, presentations, and admin handover for sustained internal operation.

Results

Within the pilot, developer morale improved and complaints about constant interruption and unstructured work dropped sharply. Developers regained focus because daily expectations became predictable.

The company reduced reliance on paper, saving an estimated 500-1000 printouts per month, because Jira provided better history and transparency than the editable legacy system.

Support and consulting gained enough visibility to communicate concrete status and blockers to customers, which improved customer satisfaction, especially through clearer answers and better service reporting for example monthly service volume and recent trends.

A key organisational outcome was stabilised attrition: newer developers were less likely to quit early once the work stopped feeling chaotic and opaque.

The final adoption hurdle was support leadership resistance (fear of losing "tribal knowledge" advantage and concern about a new tool). Targeted one-on-one coaching shifted buy-in in roughly two weeks, enabling the full rollout.

After three additional months, the entire company operated in Jira Cloud and the 20-year legacy system built on an early DotNET stack was retired, with the client taking full ownership of administration and ongoing management.

Why It Worked

Whole-system diagnosis over narrow tooling fixes The bottleneck was not just development tooling; it was the operating model across development, support, and consulting.

Pilot-first de-risking Vionix started with a two-month development pilot to prove value under real operating conditions while preserving rollback safety. This reduced adoption risk and created the evidence needed for full rollout.

Behavioral rules, not just software configuration Routing rules, daily prioritisation, and leadership alignment removed structural interruption patterns that software alone would not solve.

Targeted adoption work Focused coaching on the final resistant stakeholder group converted blocking resistance into operational buy-in.

How Vionix Worked

Vionix ran a five-month solo engagement, starting with a two-month pilot in development and followed by a three-month company-wide rollout. Work combined facilitation, process design, configuration, and team coaching. Administration and ongoing governance were fully handed over at the end.