Why the new ‘Golden Triangle’ for IT service management is Low-Code, AI and Observability
By Sascha Giese (pictured), Global Tech Evangelist, SolarWinds
Across Australia and New Zealand, IT service desk leaders are feeling the pressure. Ticket queues are ballooning, skilled engineers are scarce and users want instant answers. The levers that once expanded capacity – outsourcing, self‑service portals and larger support teams – are now delivering ever‑smaller returns.
Three forces are converging to change the equation: low-code development, Artificial Intelligence (AI) and real-time observability. Together, they form a ‘golden triangle’ that can transform a reactive service desk into an automated, self-healing engine.
The convergence is already underway
Low-code has crossed from hype to habit. By 2026, developers outside of formal IT departments will account for at least 80% of the user base for low-code development tools. An analyst who once waited months for a development sprint can design a runbook, publish a form or integrate a workflow all before lunch.
Artificial intelligence forms the second side of the triangle. Yesterday’s AI in IT service management (ITSM) meant basic chatbots that deflected password resets. Today, large language models can summarise incident reports, send human-sounding email responses, draft knowledge base articles and, crucially, recommend fixes by analysing historical tickets. Atlassian’s State of AI in Service Management Report 2024 found 88% of organisations are already using AI in their service operations. The brain is in place; it simply needs richer inputs.
This is where observability comes in. Continuous streams of metrics, events, logs and traces give AI the situational awareness it needs and give automation the trigger that tells it when to act. Without it, AI lacks the context, and automation and runs blind. With it, the service desk becomes proactive rather than reactive.
Picture a rogue memory leak in a microservice. Observability detects the anomaly seconds after it starts. A low‑code runbook spins up a replacement container, reroutes traffic and posts a status update, while an AI assistant drafts a plain‑language summary for the product owner. Diagnosis, decision and action unfold in one flow, and no ticket ever clogs the queue. This is the practical power of the triangle.
A playbook for the chief information officer
Budgets for FY26 are being finalised, and finance teams want proof of return on every headcount request. Showing automation will absorb ticket growth without adding desks suddenly offers a strong story to tell. Fortunately, getting to this golden triangle doesn’t require a grand transformation project. A simple 90-day pilot can surface value quickly.
Start with your data
Audit which metrics are collected, how often they are updated and where the gaps exist. Once the data foundation is firm, choose a single, high-volume workflow to automate – laptop purchasing, new-hire onboarding or license provisioning. Measure cycle time, the number of human touchpoints and user satisfaction along the journey. If the cycle time halves and touchpoints fall close to zero, the business case almost writes itself.
Ensure process clarity
Many service desks still rely on ad hoc approaches and undocumented workflows. Defining and standardising core processes – with guidance from low-code tools – creates a foundation for consistent performance. Runbooks are key here, offering structure and repeatability while also reducing onboarding time and human error.
Layer AI for faster wins
By training a bot on the 10 most‑consulted articles, many organisations see an uptick in ‘how‑do‑I’ queries resolved without human intervention. Every ticket resolved, email answered and anomaly flagged is a learning opportunity. Over time, this growing dataset allows AI to deflect more queries, offer more precise recommendations and enable faster resolution. As service desks mature, they spend less time firefighting and more time optimising other areas.
Remember it’s not a ‘set and forget’ process
Success demands more than technology; governance must keep pace with autonomy. Every automated action needs clear ownership, a rollback plan and an audit trail. A fusion team – consisting of a service-desk lead, site-reliability engineer, security analyst and process owner – should meet regularly to review incidents, refine thresholds and retire automations that don’t work.
The golden triangle will not solve every support challenge, nor can it be implemented overnight. But it offers a credible route away from traditional IT staffing models that have defined ITSM for decades. In a region where talent is scarce and expectations are rising, the shift to low-code, AI and observability is no longer optional – it is the path to survival.
