I'm unsure if the name is a serious liability or merely tolerable.
We were inspired by Slack, it is somewhat negative as well. Also something that is associated with startups.
What do your users aspire to?
Not burnout.
11–19 of 19 posts
I'm unsure if the name is a serious liability or merely tolerable.
We were inspired by Slack, it is somewhat negative as well. Also something that is associated with startups.
What do your users aspire to?
Not burnout.
Earlier quoted context omitted.
We were inspired by Slack, it is somewhat negative as well. Also something that is associated with startups.
Is slack negative? Generally a system with some amount of slack is resilient and responsive. (counterexample: a computer running at 100% cpu has no slack and consequently feels sluggish to use.) An organisation could reasonably aspire to have more internal responsiveness and relaxedness about communication. What do your users aspire to? Not burnout.
Earlier quoted context omitted.
Is slack negative? Generally a system with some amount of slack is resilient and responsive. (counterexample: a computer running at 100% cpu has no slack and consequently feels sluggish to use.) An organisation could reasonably aspire to have more internal responsiveness and relaxedness about communication. What do your users aspire to? Not burnout.
I'd say in business context it is https://dictionary.cambridge.org/dictionary/english/slack
Whenever I hear the word burnout, I think of serious mental health and relationship problems, with a whiff of divorce and depression. Like, I'm reminded of this blog post: http://jessenoller.com/blog/2015/9/27/a-lot-happens
I usually worry about all-in-one tools being a combination of the most popular features of each specific tool but not being powerful enough to perform the job of said tool. To mitigate this, I think having full pages breaking down each of those sections (instead of just paragraph sections) would be helpful. I like these short summaries, but additionally linking out to full sub-product detail pages would be very helpful. I wonder how each of these sub-products compare to their full product alternatives and don't quite understand from the landing page how interconnected they all are in order to make me willing to forego certain features/functionality for the sake of data organization.
As an example: We use Pipedrive as our CRM - it has concepts like: User ACL, Deals, Contacts, Organizations, Activities, etc. It offers visual workflow automation, a robust API, and advanced filtering searching capabilities. I'd like to see all of the features I'd get with Burnout's CRM to help me evaluate the product before I'd consider switching.
Regarding the name: personally, as a founder/engineer, when I hear the term burnout I think of the negative mental/physical/emotional state that I (and friends/teammates) have experienced in the past - so the name puts me off. A suggestion could be something like (warning: bad ideas alert): Startup (another play on words - since this guides you through starting up) or Blueprint.
It looks like you've built a ton of product here and I'm excited to see a live demo and check it out myself.
I think given the SEO issue, combined with the fact that "Burnout" is something you actively want to avoid in a startup makes this a poor choice.
I would also avoid comparing this with "Slack". Slack has both negative and positive connotations. It also has way better SEO properties since searching for "slack" without additional qualifiers was likely uncommon.
Startups are sufficiently stressful, I don’t need to be reminded constantly that I could burn out any day.
Something around moonshot would sound nicer. Or mission control room. How about “Houston”?
Edit: just read the page, sounds like the tool is huge in scope, are you sure you need all that stuff before launching?
I hate the name, but it doesn’t really matter if the tool’s good. Startups are sufficiently stressful, I don’t need to be reminded constantly that I could burn out any day. Something around moonshot would sound nicer. Or mission control room. How about “Houston”? Edit: just read the page, sounds like the tool is huge in scope, are you sure you need all that stuff before launching?
It’s a fairly bad, but memorable name. It won’t make or break your startup. But spending 3 years in development before launching will.