Brian is a long-time user of both a MacBook Pro (M4 Pro) and a Windows laptop. In his daily workflow, he frequently switches between the two devices using a TESmart dual USB-C KVM.
Over extended use, he noticed a persistent behavior that didn’t align with his usual experience:
When the MacBook was plugged in, it should have maintained around 80% battery charge, but after using the KVM, it consistently stayed at 100%.
This was not a “device failure” report, but a user highly sensitive to battery health questioning the rationale behind product behavior.
Customer Perspective: Not a Complaint, but a Professional Inquiry
Core question from the customer:
“I’m wondering if somehow the MacBook briefly detects a power change (when switching between machines with the KVM) and starts recharging the battery past 80%.”
The essence of this question isn’t “Why is your product broken?”
Rather:
👉 Could the KVM’s power delivery and switching logic inadvertently interrupt macOS’s battery management system?
Customer’s original words:
“My question mostly centered on whether or not using the KVM to switch between the two computers could somehow be triggering the Mac to start charging beyond 80% when it would normally not do so.”
And more importantly:
“I thought that if I supplemented power, there would be less stress on the TESmart device.”
This extended the personal concern into a focus on the product’s long-term stability and design resilience.
The Key Moment of Growth Driven by the Customer
Through multiple rounds of communication with Brian, we gradually realized:
-
The product itself had no “faults.”
-
But user expectations regarding whether power delivery behavior is sufficiently intelligent had evolved.
Brian wasn’t asking for a bug fix;
he was helping us understand that when USB-C handles both “signal + power,”
users begin to expect more advanced power management semantics—not just “it charges.”
And that’s exactly where our growth occurred.
