6 ms·

It really strikes me how many times new products fail to describe efficiently what they do. It often seems they're explaining what the project/service does to

It really strikes me how many times new products fail to describe efficiently what they do. It often seems they're explaining what the project/service does to someone who already knows it rather than to someone who just landed on their website. Many Apache products lack of proper explanation, in my opinion. Some times even AWS services. Well, it could be I'm bad at understanding their explanation. Am I the only one thinking this?

pachico 7y ago
I hope you guys at Kogito take this in a constructive way. For instance, once you want to know more and you read "examples", as user, I want to fully understand what does it do! Instead, I find a link to https://github.com/kiegroup/kogito-examples/releases https://github.com/kiegroup/kogito-examples/releases . I have no doubt your software is amazing, I just would like you to help me understand what it does and if it suits me. :)
- evacchi 7y ago
  we will! We are currently working on making our documentation and getting started experience more accessible. We welcome constructive feedback like this :)
mxuribe 7y ago
You are not alone. Many amazing groups fail to properly communicate and describe what they do/offer.
ericol 7y ago
Funny enough, this happens in my company. We have two products in market. An "old" one (that actually paid the bills for a looong time). And another, newer one that was supposed to replace the old one way to long ago as well (That didn't happen yet, but to be honest... it's complicated). Every time I was shown what the new product does, it was a demonstration of how it works, related to the old one. The question "what does this product provides to our customers that the old one doesn't" hasn't been answered in years. Epilogue: Couple years back we got a beast of a sales man, and he's shoving the new product down the customers throat as if it was heroin laced candy. I'm not complaining, but would we had dedicated the dev time to the old product, we would probably be a main competitor in our market.

pachico 7y ago

I hope you guys at Kogito take this in a constructive way. For instance, once you want to know more and you read "examples", as user, I want to fully understand what does it do! Instead, I find a link to https://github.com/kiegroup/kogito-examples/releases https://github.com/kiegroup/kogito-examples/releases . I have no doubt your software is amazing, I just would like you to help me understand what it does and if it suits me. :)

evacchi 7y ago
we will! We are currently working on making our documentation and getting started experience more accessible. We welcome constructive feedback like this :)

mxuribe 7y ago

You are not alone. Many amazing groups fail to properly communicate and describe what they do/offer.

ericol 7y ago

Funny enough, this happens in my company. We have two products in market. An "old" one (that actually paid the bills for a looong time). And another, newer one that was supposed to replace the old one way to long ago as well (That didn't happen yet, but to be honest... it's complicated). Every time I was shown what the new product does, it was a demonstration of how it works, related to the old one. The question "what does this product provides to our customers that the old one doesn't" hasn't been answered in years. Epilogue: Couple years back we got a beast of a sales man, and he's shoving the new product down the customers throat as if it was heroin laced candy. I'm not complaining, but would we had dedicated the dev time to the old product, we would probably be a main competitor in our market.