 |
VOOZH | about |
|
VOOZH | about |
We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.
Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.
Follow TNS on your favorite social media networks.
Become a TNS follower on LinkedIn.
Check out the latest featured and trending stories while you wait for your first TNS newsletter.
Platform engineering makes technology work better for different needs and improves the experience for developers. Think of it as a tool that connects and improves various tech parts, helping businesses run smoothly and innovate more. This helps companies reach new levels in their industries.
Yet, seeing the real effects of platform engineering can be tricky. It’s like trying to spot the changes in a puzzle, where some pieces might not show results right away. Evaluating things like a better experience for developers and smoother operations can be hard because some benefits might take time to appear.
To help with this, we use two well-known concepts: leading and lagging indicators. Leading indicators are like early signs that predict what might happen in the future. In contrast, lagging indicators look back at past events to confirm long-term patterns. These tools help us connect the efforts of platform engineering with its results, giving us a deeper understanding of its many advantages for a company. Let’s dive deeper into these.
When putting platform engineering into action, the goal is to make operations smoother, improve the way developers work and boost how we use cloud technology. Here’s how it usually goes:
First, we use “leading indicators.” These early signs or hints quickly show whether our operations are working well. Since we can see these signs early on, we can quickly change or improve things if needed. They’re like the dashboard lights in your car, alerting you to any immediate issues.
After that, we look at “lagging indicators.” These are the results we see after some time, showing how well our platform engineering changes have worked in the big picture. They give feedback on things like how efficient our tech setup is, how well software gets put into action and how tough and reliable our operations are. They’re like looking back at a journey to see how well you did, in contrast to leading indicators that focus on what’s happening right now or about to happen.
In simple terms, we first use leading indicators to check on things as they’re happening, and then lagging indicators to see the full results later on. Now, let’s explore some important lagging and leading indicators we use to see how good our platform engineering is.
To provide clarity on the functionality of these indicators, let’s delve into some illustrative real-world scenarios.
| Lagging Indicator | Leading Indicator | Before Implementation | After Implementation |
| Reduction in Ops Mundane Tasks | Reduction in Ops Tickets | 50 tickets per week raised to Ops for various tasks. | Reduced to 10 tickets per week. |
| Reduction in Provisioning New Environments | Used to take a week for ops teams to provision new environments for testing. | With self-service and automation, developers can provision their environments, reducing the provisioning time to a few hours. | |
| Improvement in Developer Experience and Local Productivity | Time to Onboard New Team Members | Two months to fully onboard a new team member. | Reduced to two weeks due to standardization. |
| Increase in Release Velocity | Deployments occur once every two weeks. | Deployments occur daily with increased confidence and less dependency. | |
| Improvement in Cloud Posture | Cost-Based Reduction | $10,000 a month for running non-production environments. | Reduced to $6,000 a month with optimized, standardized templates. |
| Time Spent on Upgrades | A week every quarter, causing downtime and reduced productivity. | Reduced to a day with frequent upgrades, reducing downtime. | |
| Better Cloud Security Posture | Reduction in Non-Compliances in Scans | 30 non-compliances found in quarterly penetration testing. | Reduced to five non-compliances with no recurring issues. |
Platform engineering helps operations run smoothly, even if it often goes unnoticed. It helps us see and measure our progress. Metrics are our way to gauge transformations. Think of leading indicators as previews of what’s coming next, helping us make quick fixes for future success. On the other hand, lagging indicators show us the results, like how efficiently things are working and how happy our developers are.
Together, these indicators give us a full picture of our progress. They help organizations decide how to improve the work environment, solve problems, use cloud technology better and boost productivity.
In short, platform engineering is about continuous improvement. By regularly checking our metrics, we make sure we’re moving in the right direction. This attention to detail is key for any business wanting to make the most of platform engineering. It helps improve operations and sets the stage for long-term success in tech. The goal is to stay focused, keep improving and adapt to the fast-paced tech world.
This is part of a series on platform engineering. Read the entire series:
