PARMA Production System 2026
"Technology Factory": 5 subsystems, payroll 59%→45-47% of revenue, utilization 90-92%, Delivery 1.0 (22 sections), DevOps platform, 600+ employees
What doesn't work
IT company with 600+ employees: 2/3 underloaded by 30%+, idle time equivalent to 900+ person-months/year, 25-40% projects off schedule/budget. Payroll ≈59% of revenue with no corresponding output growth. Heterogeneous processes — each department worked differently. No unified methodology, metrics, or recovery systems. Presale-to-delivery gap was the main source of losses.
Architectural approach
Designed a complete production system of 5 interconnected subsystems: (1) Presale pipeline — standardized project preparation, (2) Delivery 1.0 — unified methodology with 22 control sections, (3) Workforce efficiency — Employee Efficiency Index (EEI), standards, idle time dashboard, (4) Technology resilience — DevOps platform (IaC, GitOps, SLO/SLI), DRP/BCP, "doomsday vault", (5) Change management — initiative registry, effect formula, committee. Plus department strategy layer: competencies + technology + AI + operating model.
What made it hard
Scale: 600+ people, 5 subsystems, each affecting everyone — one bad change paralyzes the entire company. Payroll at 59% — touching salaries and utilization triggers maximum resistance. 55% of projects were overdue — people had normalized chaos. Strategy of 53 slides — needed to be simultaneously concrete for executors and convincing for leadership.
My role & contribution
CTO
Author of the production strategy (53 slides). Designed the complete 5-subsystem production system. Developed Delivery 1.0 methodology (22 sections), EEI index, DevOps platform, change management system. Cascaded strategies into 12-18 month department plans.
How it looks
How it works
Current state diagnosis (55% overdue, 30-40% underloaded) → 5 subsystem design → cascade into 12-18 month department strategies. Delivery: 22 sections (architecture, risks, timelines, quality, scope, operations), artifact templates, project health index, portfolio dashboard. Efficiency: bi-weekly load plans, effort standards, EEI (<0.9 — improvement zone, 0.9-1.1 — target, >1.1 — bonus). DevOps: IaC modules, GitOps, SLO/SLI, resilience testing, MTTR audit, secure software supply chain. 2026 roadmap by quarter.
Why this way
Factory model (5 subsystems) instead of point improvements
Improve individual processes (only PM methodology or only time tracking)
Point improvements don't solve systemic issues: with 55% overdue, 59% payroll, and 30% idle, full redesign is needed. 5 subsystems are linked: presale sets input quality, delivery drives execution, efficiency manages economics, resilience ensures continuity, changes enable growth.
Unified production system with KPIs at every level. 2026 quarterly roadmap. Each department — 12-18 month strategy
Results
- 01
- Overdue & loss-making projects: 55% → 15%
- 02
- Employee utilization: 65-70% → 90-92%
- 03
- Payroll/revenue: 59% → 45-47%
- 04
- Schedule deviations: 35% → ≤15%
- 05
- Idle time: ~30% → ≤7%
- 06
- RTO ≤ 4h, RPO ≤ 15 min
- 07
- 50% incidents resolved automatically
- 08
- Change adoption: 40% → 80%+
- 09
- AI contribution to productivity: up to 25%
Impact on business
Payroll drops from 59% to 45-47% of revenue (−12-14 p.p.) — largest cost saving. Idle time cut by 75% (from ~30% to ≤7%), freeing 900+ person-months/year. Productivity grows 10-15% annually via EEI. Project deviations from 35% to ≤15%, planning accuracy ±10%. DevOps platform accelerates delivery 2-3x. Technology sovereignty: 0% critical foreign license dependency.
Algorithms & patterns
Technologies
- Jira
- Confluence
- TFS
- KPI Dashboard
- Portfolio Management
- DevOps Platform
- IaC
- GitOps
- Grafana
- SLO/SLI Monitoring
- DRP/BCP
- SAST/SIEM