A wearable interrupted a conversation. That changed everything.

This is a personal account of one person's experience tracking health data through a health event. It is not medical advice, and it does not describe what any app or device can do for you. Individual experiences vary.

Six years ago, my Apple Watch flagged an unusual heart rate reading while I was standing still at a party. I wasn't dancing. I wasn't exercising. I was talking to friends.

The number didn't match the situation.

It wasn't a dramatic moment. No chest pain, no dizziness, nothing that would have made me leave early. But the reading stayed with me, and within days I was sitting in a cardiologist's office trying to understand what might be behind it.

What followed was a multi-year process that included further investigations, a period of managed cardiac rhythm instability, and eventually a procedure to address it. I'll describe that process across this series — not because it's an unusual story in itself, but because of what it taught me about data, uncertainty, and structured thinking under pressure.

My background is engineering and management. My instinct when something looks wrong is to collect data, look for structure, and try to understand the system behind the signal rather than just react to the event. That instinct turned out to be useful here.

What started as a single unexpected reading from a consumer wearable eventually evolved into a structured daily monitoring system that now runs as a native app drawing from Apple Health. That app is Trendwell.

But the beginning was much simpler: a number that didn't make sense, and a decision to investigate rather than ignore it.

Our bodies generate continuous health data. Most of us have more of it available than we realise, and most of it goes unexamined. This series is about what happens when you start looking at it systematically — and what kind of thinking that requires.