How does human-centered design differ from feature-based product strategy in B2B software?
Answered at 2:00 in Enhancing Fleet Management With AI with Sasha Kucharczyk of Preteckt · Leaders of B2B Podcast - Interviews on Business Leadership, B2B Sales, B2B Marketing and Revenue Growth
How does human-centered design differ from feature-based product strategy in B2B software?
The shift from feature lists to usability and human-centered design became clear through the failure of Microsoft's Zune, which competed on impressive features against the iPod but lost because it overlooked user experience. Sasha's realization was that technology should be understood not as a feature set but as an experience, addressing the question: how do you turn something overwhelming or scary into a beneficial experience that users want to interact with?
Full answer and detailsRead the whole answer, key facts and every other question from this episode
In short
The shift from feature lists to usability and human-centered design became clear through the failure of Microsoft's Zune, which competed on impressive features against the iPod but lost because it overlooked user experience.
Sasha Kucharczyk, Co-founder at Preteckt · Enhancing Fleet Management With AI with Sasha Kucharczyk of Preteckt · Leaders of B2B Podcast - Interviews on Business Leadership, B2B Sales, B2B Marketing and Revenue Growth · answer at 2:00
Key takeaways
- The shift from feature lists to usability and human-centered design became clear through the failure of Microsoft's Zune, which competed on impressive features against the iPod but lost because it overlooked user experience.
Quote to remember
“How can you empower people with the knowledge of the maintenance needs of the vehicles before they bring it in, but also help the dealership with that side of stuff?”
— Sasha Kucharczyk
The full answer · about 2 min
The shift from feature lists to usability and human-centered design became clear through the failure of Microsoft's Zune, which competed on impressive features against the iPod but lost because it overlooked user experience. Sasha's realization was that technology should be understood not as a feature set but as an experience, addressing the question: how do you turn something overwhelming or scary into a beneficial experience that users want to interact with?
Key facts
- Trucking fleet vehicles cost $150,000 and are kept for four to five years before they flip, with $15,000 to $20,000 per year in maintenance costs
- Municipal transit buses cost approximately $1 million, are kept 12 to 18 years, and cost $35,000 to $40,000 per year in maintenance
- Municipal transit buses operate approximately 40,000 miles per year within a city
- Long-haul trucking vehicles operate over 100,000 miles per year between cities, states, and countries
- Sasha studied robotics and AI starting in the early 2000s before pivoting from academia to business to pursue shorter time horizons—one to three years versus five to ten plus years
People, companies and topics mentioned
More answers from this episode
- 5:00How did Preteckt pivot from personal vehicle maintenance to municipal transit fleet management?
- 11:00How should entrepreneurs evaluate whether to pivot toward a demanding customer segment or focus on the addressable market?
- 14:00What are the key operational differences between municipal transit buses and long-haul trucking for predictive maintenance modeling?
- 23:00What experimental design challenges does Preteckt face when validating maintenance prediction outcomes with transit fleet customers?