Home 9 The Profession 9 Problem First, Solution Second: Why Elegant Engineering Needs a Real Need

Problem First, Solution Second: Why Elegant Engineering Needs a Real Need

by | Sep 2, 2025

Why tech-startup founders must start with pain points, not features, and then build solutions that matter.
Source: George Wylesol.

Hunter McDaniel, Ph.D., founder and CEO of UbiQD, shares a lesson many science-driven founders learn the hard way: elegant technical innovation isn’t enough. It’s meaningful only when it solves a real problem, says this interesting article on IEEE Spectrum. McDaniel built safer, more stable, and cheaper quantum dots than existing options, but that technical edge didn’t sell itself.

Here’s what matters:

  • Start with the problem. Before coding or prototyping, spend time with users. Ask what keeps them up at night, not what they think they want. Only then can you design an elegant, must-have solution, not just a nice-to-have feature.
  • Don’t just throw your tech over the fence. At first, UbiQD shipped research-grade samples and waited for customers to figure out what to do with them. That approach falls flat when you’re offering something novel. Founders must guide the discovery process, translate how technology maps to needs.
  • Be willing to shelve your favorite ideas. For example, UbiQD’s solar-window concept for greenhouses seemed clever, but growers weren’t trying to cut energy costs—they needed higher crop yields. That product got scrapped. Instead, they developed greenhouse films that tweak light to boost plant growth; something users actually care about.
  • View competition as validation. If no one else is trying to solve the problem, it might not matter. Competition signals you’re on the right track, but you still need defensible tech, IP, partnerships, or data to stand out.

Elegance in engineering isn’t just about smart design; it’s about solving something that people truly need, and sticking with what works, not just what’s clever.