Team Voice
Team Voice was an HR-tech platform designed to facilitate secure, anonymous communication between employers and employees to improve engagement. Despite conducting deep user research and building a pilot group of 10 HR managers, the startup failed because it tried to solve a "human problem" with a "technical tool" for users who didn't have the time to use it.
The Autopsy
| Section | Details |
|---|---|
| Startup Profile | Founders: Kirill Vechtomov Funding: Bootstrapped (Personal savings) |
| Cause of Death | Market Fit: Yes |
| The Critical Mistake | The "Tactical" Overload: HR managers (the target audience) were too busy with daily tactical tasks (hiring, screening, job descriptions) to focus on "strategic" engagement software. The CEO Education Barrier: For the product to be successful, it required the CEO or CFO to care about engagement metrics enough to mandate its use. Educating these high-level executives was a sales effort the founder didn't have the time or resources to sustain. Human vs. Tech Problem: Many of the issues the app "uncovered" were culture or management issues that a software tool couldn't fix without human intervention/coaching. |
| Key Lessons |
|
Deep Dive
In his interview with Failory, Kirill Vechtomov shared the irony of having high engagement in research but low adoption in reality. The "Supportive" but Busy User: Kirill had a group of 10 HR professionals who were "super helpful" and loved the idea. However, because Kirill worked a full-time 9-to-5 job, he could only meet them after hours. Since HR managers are B2B users who only work during business hours, he couldn't get the "real-time" feedback needed to iterate fast enough while they were actually in their work environment. The Public Shaming Origin: Kirill's motivation for entrepreneurship began when he was 8 years old in the USSR, selling toys and being publicly shamed by a teacher for his "capitalist" behavior. This drive kept him going, but he eventually realized that "80 hours of work for the sake of 80 hours" wasn't enough to solve a problem that required a massive shift in corporate mindset. The Legacy: Team Voice is a classic case of "Selling a Strategic Solution to a Tactical User." It serves as a reminder that your user and your buyer might have different priorities. Kirill now applies his UX and research skills to help other entrepreneurs avoid "building in a vacuum" through his consulting project.
Key Lessons
Selling a Strategic Solution to a Tactical User: Your user and your buyer might have different priorities.
The Pilot Group Paradox: Having high engagement in research but low adoption in reality.
The "Supportive" but Busy User: You can't get "real-time" feedback when you can only meet after hours.