Thomas Sowell opines in Basic Economics that “[…] the real cost of anything is still its value in alternative uses. The real cost of building a bridge is whatever else could have been built with that same labor and material. The cost of watching a television sitcom or soap opera is the value of the other things that could have been done with that same time.”
[ You might also enjoy: 5 ways to ruin a sysadmin's day ]
Organizations make this determination every time they choose to work on one ticket, project, or objective and key result (OKR) over another. Making this value judgment explicit is critical to a well-functioning organization. To do this effectively, organizations must understand and communicate priorities, and individuals must be incentivized to work towards those priorities.
If an organization does not understand its own priorities, it is impossible to prioritize the “right work” since that term is undefined. Organizational goals, explicitly communicated in a format like OKRs, align disparate teams around a clear set of objectives. Even on teams that collaborate effectively, a formalized, regular goal-setting process minimizes drift and overlap across teams and departments.
Furthermore, incentivize individuals to fulfill these organizational priorities. If an organization rates employees on their response times to customer requests, but the OKRs are all centered around long-term internal projects, this misalignment means workers will never achieve the organizational goals. Either adjust the employee ratings to align with the OKRs or adjust the OKRs.
[ Getting started with containers? Check out this free course. Deploying containerized applications: A technical overview. ]
Apply this thinking to your day-to-day tasks. Is this ticket or project worth working on in light of your team, department, and organizational priorities? Are incentives structured in a way that encourages individuals to work on the projects you want them working on? If such organizational priorities are not set at all or are not clearly communicated, start a dialogue with leadership around these topics. Encourage them to provide this guidance so everyone on the team can make better decisions.
Always consider the bridge not built.
Über den Autor
Jonathan Roemer is a senior DevOps engineer at Drizly with an interest in security, automation, and the human side of IT. He can usually be found hiking or reading a book on his porch.
Ähnliche Einträge
Bridging the gap: Red Hat Academy shaping open source talent in APAC
Behind the scenes of RHEL 10, part 3
Command Line Heroes: Season 2: Bonus_Developer Advocacy Roundtable
The Overlooked Operating System | Compiler: Stack/Unstuck
Nach Thema durchsuchen
Automatisierung
Das Neueste zum Thema IT-Automatisierung für Technologien, Teams und Umgebungen
Künstliche Intelligenz
Erfahren Sie das Neueste von den Plattformen, die es Kunden ermöglichen, KI-Workloads beliebig auszuführen
Open Hybrid Cloud
Erfahren Sie, wie wir eine flexiblere Zukunft mit Hybrid Clouds schaffen.
Sicherheit
Erfahren Sie, wie wir Risiken in verschiedenen Umgebungen und Technologien reduzieren
Edge Computing
Erfahren Sie das Neueste von den Plattformen, die die Operations am Edge vereinfachen
Infrastruktur
Erfahren Sie das Neueste von der weltweit führenden Linux-Plattform für Unternehmen
Anwendungen
Entdecken Sie unsere Lösungen für komplexe Herausforderungen bei Anwendungen
Virtualisierung
Erfahren Sie das Neueste über die Virtualisierung von Workloads in Cloud- oder On-Premise-Umgebungen