Case study 01
Three teams aligned to one workflow for predictable six-week releases
A Healthcare IT vendor with 50+ users, 10+ Jira projects, and a need for unified release visibility across software development teams.
Process Alignment
Clean-up
Jira Cloud
Support Tactics
Delivered 2025
Role: Architect + System Admin + Support
6 weeks
Kick-off to aligned workflow
Plan said 6 to 8
10+ → 1
Workflows consolidated
10+ project schemes unified
6 months
Follow-up guidance & support
Process Tactics into Support Tactics
3 teams
Unified under one outcome
100% cross-team visibility
The situation & adoption
What was missing, how the teams aligned, and what made it stick.
The engineering teams knew how to build software, but each team operated in its own silo with custom Jira statuses, separate project schemes, and divergent handoffs. Releasing new Healthcare IT software every six weeks was becoming unpredictable due to missing cross-team visibility and fragmented tracking.
I was brought in as advisor, architect, and system administrator to audit the existing Jira Cloud setup, consolidate project workflows, and establish full transparency across all teams.
Following the initial Process Tactics engagement, I provided six months of ongoing Support Tactics—offering lightweight guidance, resolving edge cases, and keeping teams on track as they adapted to the new cadence.
The honest limit
Aligning three teams to deliver one joint outcome required every team to compromise on how work items were processed and give up individual habits. New workflows don’t stick overnight: the six-month follow-up period was crucial to enforce daily discipline, ensuring Jira remained the single source of truth rather than teams falling back into old patterns.