Blog Highlights
- IT service operational complexity management is a data problem before it is a governance problem. It builds up in the gaps in between the systems, the processes and the governance and it’s not visible until it reaches in report form.
- 34% of IT services firms cite poor operational effectiveness in project delivery (at four points higher than average). Professional services firms are spending, on median, $60,000 a year just on non-billable coordination activities.
- Shadow approval issues lead to bad governance reporting, damage the relationship between change orders and billing, and remove the ability to perform corrective action. It costs the IT services firms 66% relying on disjointed environments of delivery management.
- Operational complexity management doesn’t need more governance-it needs “governance that is connected”-in essence: the single source of truth, immediate visibility to resource cost and portfolio, linked change order and billing processes
- Kytes manage the enterprise from project conception through delivery in a unified AI PSA that integrates project governance, resource management and project financials. The results for clients show delivery cycle speed by 21%, utilization gains of 12% and margin increase of 9%.
QUICK ANSWER
Operation complexity management is the systematic process to remove the non-apparent costs created by fragmented processes, separated systems and ill-defined governing structures which are incrementally gained within IT services enterprises when they expand. A missed target, diminishing margin or reports being generated and never acted upon can be some of the indirect costs that build up within a business at IT services enterprises as and when they grow. A direct cost shows up on your balance sheet, an operational complexity cost just shows up late-cost to me and you is already borne and when it appears the report has landed on your desk the expense has already taken place.
The Report Always Arrives on the Fifteenth
A delivery head for an IT services company of 700 individuals, based in Chennai, obtained the monthly portfolio report every fifteenth. He had project data on projects on schedule; delayed; at risk. What he did not have were the facts of what had happened.
A senior architect had been on the bench since the third of the month. A change request against a fixed-price engagement had been “approved” on slack, never formally initiated, leading to additional scope being developed without a trigger against billable, not for any other reason than due to lack of formal process. Three project managers, were all using different templates to track the same class of deliverables; and the merging required two days of each sprint. On the 15th of the month, twelve days of operational complexity had been run, which had cost the company more than the travel budget of last quarter, and the portfolio report listed neither a trace nor a breath of any of that.
What Is Operational Complexity in IT Services?
The operational complexity of IT services is nothing more than added friction within the delivery engine-the number of additional steps, the ambivalence of ownership, the fragmentation of data, and mismatched processes that add unnecessary expense to every project yet go unforecasted and unbudgeted. The core distinguishing fact is its invisibility at point of incurrence. Bench cost builds from day 1.
Scope add-ons ship to the customer beginning in sprint 1.
Reconciliation effort accumulates week 1. None of these appear in the company’s financial systems until someone decides to reconcile the data-usually on the 15th of the month in most IT services companies. Three structural aspects fuel the IT services’ complexity premium: multi-client pool resource management; wherein the decision regarding resources for Client A impacts Client B’s planned capacity, variable delivery models; wherein T&M, fixed-price, milestone billed, and retainer contracts exist simultaneously while utilizing different trigger criteria for invoicing, and onshore-offshore reconciliation coordination overhead. Each handover of a deliverable, to a client, to another team member, or to an onshore offshore resource has some inherent probability of the new party either being unsure about scope, unaware of allocated capacity, bypassing approval processes.
The Shadow Approval Problem
Governance breaks when it moves to WhatsApp. In an IT services setting, a formal governance system sits along side informal approvals. An unwritten resource move confirmed in Slack doesn’t enter the allocation system. An accepted out-of-scope scope expansion confirmed during a client call won’t be entered as a change order. An agree to push that delivery decision during a sprint stand-up doesn’t land with the money system in the project. The structure of governance is sound. The actual approval of the decision doesn’t touch the formal structure.
This is shadow approval-the difference between how governance is set up and governance as it’s practice. This is what happens when formal governance is moving at a pace slower than how delivery is needed, where a change order requires 4 signatures and the client need an answer in four hours.
Three ways that the shadow approval problem gets paid: inaccurate government reports, because one reality is displayed on the formal system when in fact decisions led to a different one; disruption of the change order-billing chain, because change which was introduced through the shadow system never creates a billing event; impossibility of corrective action, because the PMO was not present for the actual decision it needs to address.
The Four Types of Operational Complexity in IT Services
Complexity management of operations manifests in four forms, each being containable. Neither of these is transparent without an underlying delivery and financial infrastructure supporting them.
What Operational Complexity Management Actually Requires
Operational complexity management does not require more governance. It requires better connected governance. For IT services enterprises, this means four specific things.
A single source of truth for delivery and financial data
When project execution and finance is in the same system, governance relies on last Friday’s status. When they live on separate systems governance is based on last Wednesday’s status – and hence complexity just quietly building up: ’til I get my report.
Real-time resource cost visibility at the point of allocation
Every staffing decision should make available for review, the cost rate, billing rate and margin effect on every candidate resource before committing them. Managing the complexity of operations becomes controlling finance: scheduling decisions transform into control decisions.
Connected change order and billing workflows
If the scope changes, the financial response has to be automatic- not to be left to discretion; not to be delayed; not based on an account manager’s memory to submit the change order after sprint end- the change is logged, the budget is updated, etc.
Portfolio-level financial visibility for PMO heads and CFOs
Meeting should illustrate the status (financial) of all open project at same time, it should not be combined from different (delivery, finance) systems after the end of the month.
How Kytes Supports Operational Complexity Management for IT Services
Through our engagements with the IT services enterprise domain, we found that operational complexity in the industry was largely a function of scattered data, and not, as though generally, a strategic issue. And herein is the problem of complexity: frameworks exist. What is absent is a connect of those frameworks so that the delivery head does not get his report on the 15th and learns what happened on the 3rd.
Kytes is an Agentic AI enabled PSA tool for the IT services enterprise industry.
Kytes governs enterprise delivery comprehensively end to end, integrating project governance, resource management, project financials, and compliance, into a single integrated platform. Kytes does not put a governance layer atop existing complexity. Kytes gets rid of the lacuna through which complexity can build up undetected.
A project performance management system that surfaces the financial impact of scope changes at the point of scope deviation, closes this gap. The change order workflow is triggered before the cost accumulates, not after the billing cycle. The margin protection happens at the moment the decision is made.
Integrated project governance
The Portfolio Dashboard within Kytes visually captures delivery status, financial condition, billing activities, risk triggers for all simultaneously open projects. These are viewed identically by PMO leaders, as well as by CFO’s, on their respective desks. Governance becomes decision centered rather than reporting.
Resource management with cost and margin visibility
When project demand is raised, Kytes AI scans the entire resource pool-competency, availability, cost rate, and billing rate, and presents the recommended allocation with potential margin impact shown in advance for approval. Benching cost hits PMO Dashboard at the moment when the resource is released from a project.
Change order and billing automation
As the scope increases, Kytes brings that impact of finances to the surface in real time, driving the change order workflow even before additional work is delivered. Certified timesheets refresh your project’s financial position & billable inventory automatically, closing the leakage gap left open for the every sprint to a manual change order workflow.
Oracle ERP and SAP integration
Kytes interfaces with your Oracle ERP, SAP, and HRMS. Flow of financial information with no manual data transfers between so the project performance picture, is the same picture as the enterprise financial picture. No reconciliations.
When complexity costs more than cost, there will be no more governance to solve this problem. Rather, there will be ‘connected’ governance. Kytes makes the daily practice of managing complexity of operation. The report will never be three weeks late after the cost will occur.
Frequently Asked Questions
