06/08/2026
A 14-year-old built a working stroke-detection watch in one weekend.
In 2024, Naya Ellis was a freshman at John F. Kennedy High School in New Orleans.
She was fourteen years old.
Her first STEM Saturday project was going to be a wristwatch that detects seizures. On the final weekend before her project was due, her grandmother had a stroke.
She scrapped everything and started over.
By Monday, she had designed a device she called WingItt — a wrist-worn wearable that tracks heart rate, oxygen levels, and shifts in speech to catch the earliest signs of stroke in adults over 55. When it flags a risk, it messages family and calls emergency services. She built it to be affordable, because most commercial stroke-detection technology is not.
She won a championship title at the National STEM Challenge for it.
WingItt is now patent-pending. Naya is 16 now. The device is still in development. And she is still building.
There is a specific lesson in here for anyone working in education, talent development, or youth innovation programmes.
The difference between a school project and a real invention is often just the level of the stakes. When we ask students to design something abstract, we get something abstract.
When a student is designing for someone she loves — a grandmother, a neighbour, a friend — the work sharpens. The constraints get real. The stubbornness required to solve it appears from somewhere it was not visible before.
Naya did not have more resources than her classmates. She had a weekend and a reason.
Her own words about why she built it:
“I just want to do something that can help people who have strokes.”
If you work with young people — as a teacher, mentor, coach, funder, or parent — the question worth carrying this week is a simple one:
What would happen if we stopped asking students to design projects, and started asking them to solve someone-they-love’s problem?