3 ms·
So, I wonder if you're thinking of starting a business based on one of these "I hate using" stories. If you are, I'd advise caution entering a market you don't
by SwellJoe 17y ago
So, I wonder if you're thinking of starting a business based on one of these "I hate using" stories. If you are, I'd advise caution entering a market you don't actually understand personally. Yes, we all make software that eventually grows to do things we don't use ourselves (I use functionality that touches less than 10% of our total codebase on a daily basis, and never hit more than 20% of it, for example), but without understanding the core problem set of your target audience, I'm not sure you can build effective software to solve those problems.
When I worked in scientific computing, one of the founders of the company I worked for had done doctoral work in the areas the software was covering, and the company hired domain experts, who also happened to know a bit about software development, whenever they moved into new fields.
This is the reason I've never gone into medical billing, despite the fact that I know the medical billing software industry is a mess, and also an incredibly lucrative market. I know it is a mess, because my sister owns a medical billing firm, and I've seen the software her company uses. But, without spending a few months working in the field, I wouldn't be effective at solving those problems. If I ever did decide to start a company in that field, I think I'd need to spend some time in the trenches of that particular field.
Likewise, I suspect if you do find yourself a lucrative and currently poorly served market niche to focus on, you will need to also find a few companies to work closely with, so you actually understand the problems and how they can be solved. Also, keep in mind that the harder existing software is to use, the more training existing users will have had to know how to use it. Don't underestimate how hard it is to convert someone from using "complicated but familiar" solutions to using "easy but new" solutions.
Not seeking to rain on the "I hate X" parade, just pointing out that if you aren't scratching your own itch, to some degree, you have a lot of work to do just to begin to understand the problem domain.
- abalashov 17y agoThank you, very good post. Echoes my own thoughts. It is a response that I have frequently entertained in my mind to entrepreneurial cheerleaders (and even sometimes PG's statements, insofar as they relate to solving truly niche commercial software problems, although I don't think he intentionally suggests that you can do it without the experience by any means). But yes, I'm in telecom and I see outside consultants and vendors who are basically general IT in their orientation show up all the time and think that they can create better OSS/BSS (operational support/billing support systems) solutions, switch provisioning and monitoring software, and workflow/process management in the highly bureaucratised and rather regulated carrier space (i.e. Local Number Portability). Then I see them get fired a few months later because they just haven't the foggiest earthly clue what minefield they stepped into. They would have benefitted from hiring at least one omnicurious person who has actually worked for a competitive carrier first.