https://engineering.hinshelwood.com/concepts/observability/ Recent content in Observability on Engineering as a Leadership System Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/ Wed, 11 Jun 2025 06:45:00 +0000 https://engineering.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/ Shipping software without telemetry leaves teams guessing about usage, performance, and user behavior, which prevents learning and improvement. Teams that make telemetry a core part of their Definition of Done catch issues early, validate outcomes with real data, and make better decisions. To deliver real value, define telemetry needs upfront, automate data collection, review feedback regularly, and act on what you learn. https://engineering.hinshelwood.com/tags/lead-time/ Fri, 11 Apr 2025 06:00:00 +0100 https://engineering.hinshelwood.com/tags/lead-time/ Lead Time is an essential observability metric that quantifies the duration from the initiation of a work item to its delivery to the customer. It is a practical implementation of Cycle Time often used in flow-based systems such as Kanban. This metric provides end-to-end visibility into workflow performance, helping teams identify inefficiencies and optimise delivery for improved predictability and responsiveness. By exposing how long it takes to deliver value, Lead Time enables real-time insight into system health and team effectiveness, supporting continuous improvement across Agile, Lean, and DevOps environments. https://engineering.hinshelwood.com/tags/throughput/ Wed, 09 Apr 2025 14:41:23 +0000 https://engineering.hinshelwood.com/tags/throughput/ Throughput is a critical observability metric that quantifies the volume of work completed by a system within a defined timeframe, serving as an indicator of the flow of value delivered by teams. Originating from Agile and Lean methodologies, throughput is utilised to assess system performance holistically rather than focusing on individual contributions. By monitoring throughput, teams can uncover trends, pinpoint bottlenecks, and evaluate the impact of workflow modifications on overall efficiency. Visualisation tools such as cumulative flow diagrams and flow analytics facilitate real-time tracking of throughput data, enabling teams to inspect flow health alongside other metrics like lead time and cycle time. This empirical approach fosters informed decision-making, guiding adjustments in work-in-progress limits, team structures, and planning processes. Ultimately, throughput enhances transparency and supports a culture of continuous improvement, allowing organisations to optimise their processes without relying on subjective evaluations of performance. https://engineering.hinshelwood.com/concepts/observability/ Wed, 09 Apr 2025 14:00:00 +0100 https://engineering.hinshelwood.com/concepts/observability/ Observability is the practice of gaining comprehensive insights into systems and processes, enabling teams to understand work flows and value delivery. It transcends traditional monitoring by offering a holistic view of system behaviour, which allows teams to identify patterns, diagnose issues, and make informed decisions based on real-time data. This capability is essential for fostering transparency and collaboration within teams and across organisational silos. By implementing observability, organisations can improve their ability to deliver value predictably and sustainably, supporting continuous improvement through learning and adaptation. It encompasses not only technical telemetry but also signals reflecting team dynamics, product experiences, and alignment with strategic goals, thus providing a complete view of performance that includes both human and technical factors. When integrated into daily practices, observability cultivates a feedback-rich environment that enhances decision-making and strengthens delivery capabilities. It represents a cultural shift that empowers teams to take ownership of their processes and outcomes, aligning with Lean and Agile principles focused on understanding flow and eliminating waste. By embedding observability into the organisational framework, teams can create a resilient environment that leverages data-driven insights, ultimately leading to improved products, stronger teams, and more strategic business outcomes. https://engineering.hinshelwood.com/tags/revenue-per-employee/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/revenue-per-employee/ Revenue per Employee is a crucial observability metric that measures an organisation’s financial efficiency by calculating total revenue divided by the number of employees. This metric provides valuable insights into how effectively an organisation converts its workforce capacity into revenue, allowing for the analysis of systemic performance rather than focusing on individual contributions. It serves as a financial signal that facilitates empirical examination of workforce alignment, throughput, and productivity trends over time. When utilised appropriately, Revenue per Employee aids in strategic planning, identifies delivery constraints, and assesses the operational impact of organisational changes, such as the adoption of Agile methodologies or Lean transformations. By monitoring this metric over time, organisations can uncover the effects of restructuring, automation, or changes in team composition. Although it is not a diagnostic tool on its own, it plays a significant role in a broader set of delivery and business metrics, enabling leaders to evaluate the performance of their systems. This perspective positions Revenue per Employee as a lens through which to understand system health, rather than as a means of assessing individual or team accountability.