My Daily Track

As a wearables reviewer, I'm often asked what I track on a daily basis. Living an optimized life can be overwhelming, but I'm here to give you a glimpse into my daily routine and what I monitor to evaluate products and claims.

Introduction to My Tracking Routine

My tracking routine changes depending on the time of year and the products I'm reviewing. During the winter months, my load is lighter, but as product launch season approaches, I'm testing multiple devices at once.

Currently, I'm focusing on metabolic tech and building a digital twin for my metabolism using various health sensors and devices.

My Current Tracking Roster

I'm testing a range of devices, including screenless fitness trackers, smart scales, and sleep trackers. These devices feed into a system that helps me create a comprehensive picture of my health and metabolism.

Dexcom G7 (a continuous glucose monitor)
Twin Health scale
Apple Watch Ultra 3
Medline blood pressure cuff
Garmin Cirqa (a screenless tracker)
Withings BodyScan 2 (a smart scale)

Comparing Devices and Tracking Metrics

I compare devices to control devices, such as the Oura Ring, to evaluate their performance and accuracy. I also track various metrics, including sleep quality, readiness scores, and AI-generated daily insights.

I start my day by syncing all my wearables and noting their battery levels. I then review each device's app to see how they've tracked my sleep and other metrics.

Morning Routine and Data Review

After syncing my devices, I review my fasting glucose level and overnight patterns using the Dexcom G7 app. I also skim through AI-generated daily insights to see if there are any significant deviations or unusual recommendations.

Conclusion and Takeaways

Technology teams are watching my daily track closely because changes in this space often arrive faster than internal policies can adapt.

For product and engineering leaders, the practical question is how this could reshape roadmaps, vendor choices, and security reviews over the next few quarters.

Organizations that document lessons early tend to respond more calmly when similar patterns appear again.

In many companies, the first impact shows up in planning meetings: teams reassess priorities, revisit risk registers, and check whether existing tooling still fits.

Smaller businesses feel these shifts too. A single platform change or market move can affect customer trust, delivery timelines, and hiring plans.

The most resilient teams treat stories like this as input for quarterly reviews rather than one-day headlines.

If your business depends on modern software, ERP, VoIP, or customer-facing apps, staying informed helps you separate noise from decisions that require action.

Looking ahead, disciplined follow-through matters: assign owners, set review dates, and measure whether your response improved outcomes.

Security and compliance stakeholders should ask whether current controls still match the pace of change described in this update.

Operations leaders can reduce friction by translating the headline into a short internal brief with clear next steps for each department.

Customer support teams may see early signals through tickets, outages, or policy questions long before leadership reviews are scheduled.

Finance and procurement groups should note whether licensing, vendor risk, or implementation costs need revisiting after this development.

Training programs benefit from timely updates so staff understand what changed, what did not change, and what requires escalation.

Architecture reviews are a practical place to test assumptions, especially when new tools, platforms, or threats enter the conversation.

Documentation quality often determines how quickly a company recovers from surprises; capture decisions while context is still clear.