This article is based on reporting originally published by SD Times and a 2019 announcement from the DevOps Institute.
Why the Human Side of DevOps Matters
DevOps conversations are often dominated by toolchains, automation pipelines, and infrastructure-as-code. But the DevOps Institute argues that technology alone is not the limiting factor in most DevOps transformations — people are. To address this, the Institute introduced the SKIL Framework, a structured model designed to guide individuals and organizations through the process of upskilling for DevOps.
“We really feel very strongly that while automation is obviously a critical success factor for DevOps, it really is the human factor that’s going to make a difference,” said Jayne Groll, CEO of the DevOps Institute, in an interview with SD Times.
What Is the SKIL Framework?
SKIL is an acronym standing for Skill, Knowledge, Ideas, and Learning. It is a holistic model created by the DevOps Institute to give practitioners and organizations a coherent path to developing DevOps competencies — without prescribing allegiance to any single methodology such as ITIL or Agile.
“We recognize that we needed to create a framework that helps people understand how to transform without being specific to things like ITIL or Agile,” Groll said. “DevOps is really about continuous learning and mastery.”
The Skills Gap Driving the Framework
According to the Upskilling: Enterprise DevOps Skills Report 2019 published by the DevOps Institute, organizations identified the top three skills they needed as:
- Automation skills — scripting, CI/CD tooling, infrastructure automation
- Process skills — workflow design, release management, value stream mapping
- Soft skills — collaboration, communication, empathy, and adaptability
The inclusion of soft skills in the top three was described as unexpected by the report’s authors, but it reinforces the DevOps Institute’s position that technical proficiency alone is insufficient. Groll noted that a shortage of these critical skills is behind many of the challenges organizations face when attempting to adopt or scale DevOps practices.
The Four Elements of SKIL
Each element of the framework targets a different dimension of professional development:
1. Skill
Focuses on measurable, demonstrable career growth. This includes certifications, skill assessments, and defined learning paths that individuals can point to on a CV or résumé. The goal is to give practitioners tangible credentials that validate their expertise to employers and peers.
2. Knowledge
Covers rich, substantive content that supplements day-to-day practice. This includes research reports, case studies, whitepapers, and books. Knowledge resources are meant to provide deeper context and insight beyond what a certification or course syllabus can cover.
3. Ideas
Emphasizes peer-to-peer exchange and community engagement. This element encompasses Skillup events, Slack community groups, networking opportunities, and forums where practitioners can share experiences, debate approaches, and learn from one another’s successes and failures.
4. Learning
Supports continuous, lifelong learning rather than point-in-time training. This includes listening to thought leaders, following emerging research, and pursuing structured learning paths that lead toward genuine mastery rather than checkbox compliance.
Context for Individuals and Organizations
One of the practical problems the SKIL Framework aims to solve is the lack of direction that many practitioners face when they are told to “upskill” without being given guidance on how. There is no shortage of available resources — bootcamps, MOOCs, university programs, conference talks, and freely available video content all exist — but without a structured framework, it can be difficult to know where to start or how to sequence learning effectively.
Groll stated that SKIL is intended to provide that context both for individual contributors trying to advance their careers and for engineering managers or HR leaders trying to build upskilling programs for their teams.
Where SKIL Fits in the Broader DevOps Landscape
Unlike prescriptive frameworks that mandate specific tools or processes, SKIL is deliberately methodology-agnostic. It does not compete with Agile, SAFe, ITIL 4, or any other framework — instead, it acts as a meta-layer that helps practitioners navigate whichever methodologies are relevant to their context.
For DevOps engineers and platform teams, the practical takeaway is straightforward: technical skills matter, but they are not sufficient on their own. Building knowledge, staying connected to the broader community, and committing to continuous learning are equally important factors in a sustainable DevOps career or a successful organizational transformation.
More information about the DevOps Institute and its programs is available at devopsinstitute.com.