Skip to content

Commit

Permalink
metrics blog post
Browse files Browse the repository at this point in the history
  • Loading branch information
MikeGrace committed Aug 3, 2024
1 parent 2dfc225 commit 4fa2801
Show file tree
Hide file tree
Showing 3 changed files with 107 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ If the script doesn't run as expected, follow these steps:
```bash
sudo udevadm monitor --environment --udev
```

Note that when you run this and first connect your Garmin to USB, you will see a flury of activity from this monitor but your script will not yet be triggered. It isn't until the USB drive is mounted that it should be triggered. So just be patient. If you don't see it mounted in the files like a external drive, then it shouldn't be triggered yet.

3. **Check System Logs:**
Expand All @@ -138,5 +138,3 @@ If the script doesn't run as expected, follow these steps:
```bash
journalctl -xe | grep udev
```


Original file line number Diff line number Diff line change
@@ -0,0 +1,106 @@
---
title: Knowing Your Questions: The Key to Effective Metrics Collection
layout: post
categories:
- Agile
- Metrics
- How-to
---

Recently, my brother shared a story that resonated with me and inspired this post. He talked about his excitement in purchasing a set of energy monitors for his home, only to find himself ignoring the data after the first week. His goal was to understand his energy consumption after a high bill, but without clear questions driving the data collection, the effort fizzled out.

This got me thinking about how often we see the same scenario play out in the world of project management and Scrum. We invest in tools and systems to collect all kinds of metrics, hoping they'll magically reveal insights. But just like my brother's energy monitors, without a clear purpose, these metrics often end up as digital shelfware—cool but unused.

## The Importance of Asking the Right Questions

Before diving into data collection, it’s crucial to ask ourselves: What do we really want to know? What questions are we hoping these metrics will answer? It’s easy to get caught up in the excitement of new tools and technologies, but without a focused approach, we risk wasting time and resources.

## The Process of Effective Metrics Collection

To make the most out of your metrics collection, consider these steps:

![Flowchart showing steps towards actionable data generated using mermaid.js](/assets/2024/08/2024-08-03-steps-towards-actionable-data.png)

```mermaid
flowchart TB
A[Desire for Improvement]
B[Identify Questions]
C[Identify Actions]
D[Assess Value]
E[Cost-Benefit Analysis]
F[Plan Data Collection]
G[Collect Data]
H[Analyze Data]
I[Take Action]
A --> B
B --> C
C --> D
D --> E
E --> F
F --> G
G --> H
H --> I
```

1. **Desire for Improvement:** Recognize the need or desire to make a decision to improve something.
2. **Identify Questions:** Determine the specific questions that, if answered, would enable a good and informed decision.
3. **Identify Actions:** Define the potential actions that would be taken based on the answers to these questions.
4. **Assess Value:** Evaluate the value of getting these answers and taking the identified actions.
5. **Cost-Benefit Analysis:** Decide if collecting data is worth it based on the value of the actions and the cost of data collection.
6. **Plan Data Collection:** Determine the resources (time and money) to allocate for collecting data and decide on the methods for data collection.
7. **Collect Data:** Gather the relevant data as planned.
8. **Analyze Data:** Format and interpret the data to specifically address the identified questions.
9. **Take Action:** Based on the insights gained from the data, take informed actions and aim to realize the value of these data-informed decisions.

As you can see in the flowchart[^1], the metrics collection step is just one step of many on the journey to actionable insights.

## Beyond the Basics: Expanding Your Metrics Approach

This post touches just the surface of metrics. There are lots of other angles and aspects to using metrics to drive actionable insights for your business. Here are a few more points for you to consider:

1. **Align Metrics with Business Goals:** Metrics should always align with your overarching goals, such as increasing revenue, improving customer satisfaction, or enhancing operational efficiency.

2. **Understand Your Target Audience:** Metrics related to customer demographics, behaviors, and preferences will help you tailor your strategies effectively.

3. **Identify Key Performance Indicators (KPIs):** KPIs are the key drivers of your business that directly impact your goals.

4. **Establish Review Cadence:** Regular reviews ensure that you stay on track and can make timely adjustments.

5. **Benchmark Against Industry Standards:** Comparing your metrics to industry benchmarks helps you understand where you stand relative to your peers.

6. **Balance Leading and Lagging Indicators:** Leading indicators help you anticipate problems and seize opportunities before they become evident in lagging metrics.

7. **Visualize Your Metrics:** Use charts, graphs, and dashboards to present your metrics in a way that's easy to understand at a glance.

8. **Ensure Proper Access:** The right people in your organization should have access to the metrics they need to perform their roles effectively.

9. **Be Willing to Adapt:** Don't be afraid to revise and refine your metrics as your business grows and changes.

Happy questioning and may your insights always be actionable!

## Footnotes

[^1]: Here is the Mermaid flowchart code used to create the flowchart:

```mermaid
flowchart TB
A[Desire for Improvement]
B[Identify Questions]
C[Identify Actions]
D[Assess Value]
E[Cost-Benefit Analysis]
F[Plan Data Collection]
G[Collect Data]
H[Analyze Data]
I[Take Action]
A --> B
B --> C
C --> D
D --> E
E --> F
F --> G
G --> H
H --> I
```
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 4fa2801

Please sign in to comment.