For example, take New Relic (https://newrelic.com/)...
"New Relic One is an observability platform built to help engineers create more perfect software. From monoliths to serverless, you can instrument everything, then analyze, troubleshoot, and optimize your entire software stack. All from one place."
I'm going to be really blunt here. What on earth does all of that mean? From that explanation alone I have no clue what New Relic is. I'm going to have to use it first to even know what it does.
So on my quest to figure out what New Relic actually is, I decided to research "observability". Let me just say, WikiPedia did not help...
"In control theory, observability is a measure of how well internal states of a system can be inferred from knowledge of its external outputs. The observability and controllability of a linear system are mathematical duals." - Wikipedia
I've put myself out there and called out, what I've heard is, an excellent product. I'm just saying, I can't get a clear explanation on what it actually is from the website. Now it's your turn...
What's your best example of a website that doesn't do a good job of telling potential customers what the product actually is? Why is it like this? Am I missing out on something? What do I have to do to become the type of developer that doesn't cry when I have to investigate a new product solution?
Potential customers should be able to answer these questions within 5 SECONDS of reading the site, or marketing material: 1. What do you offer? 2. How will it make my life better? 3. What do I need to do to buy it?
You can do this with fewer than 300 words on your sales page.
I’ve lost count of the number of times dev types have been put in marketing or management roles because someone thought that stuff is easy. Imagine putting a marketing type in charge of your server.
Writing, marketing, product management: these are all real, solid skills, and quite often (not always), devs or startup CEO’s don’t have them.
1. It is hard to guess what someone else will understand.
2. There is a trade-off between using words everyone knows, being concise, and getting enough richness of meaning across.
One of the world's top professionals in technical communication has a book where he uses diagrams and only the ten hundred most common English words to explain subjects[1]. However, this sort of thing can people feeling condescended-to[2].
3. Different forms of communication have different goals.
The goal of that page is not to help every software engineer understand what New Relic is without them using it.
The goal of that page is to sell software. There are multiple audiences for that, which means making communication tradeoffs
4. Sometimes people fail at doing things well. That includes copy-editing.
------------------------
> What do I have to do to become the type of developer that doesn't cry when I have to investigate a new product solution?
I empathize with the feeling of overwhelm.
I’m a copywriter that specializes in SaaS tools, and it’s literally always the case.
The founders are brilliant nerds but haven’t a cooking clue about the first thing when it comes to marketing, product positioning or delivery of their value proposition.
I'd guess they would have a few pages explaining its features but it seems the website is down atm.
If the language is compelling to the people who actually buy the product (who may be quite nerdy/technical themselves), then it doesn't matter if it's confusing to the average person.