Project management is definitely ripe for new competitors. But the pricing sales form dark pattern is so frustrating. Why do people do that? Does it really increase engagement? It legitimately pisses me off, and I'm the decision maker on taking on this kind of software or not.
> Why do people do that? Does it really increase engagement?
It's not for engagement, it's usually because they don't actually have a standard pricing. It signals that they don't want small, self-serve customers, they only want to serve enterprise customers who want to negotiate custom contracts.
Dethrowning Jira is an honorable goal, but all the animation on the landing page is really distracting.
The scrolling use-cases in the hero section causes the with of the page to slightly change, causing other full-width elements to reflow, and
the images cycling below fly by so fast that I couldnt really get anything out of them.
The pricing page is an instant turn off. I want to start a trial but I have no idea how much I'll be paying without contacting you first? Are you kidding me?
Yes large orgs will probably want to contact you for pricing but you are leaving business from smaller orgs on the table. My first reaction when seeing the "contact us for pricing" was "ok whatever I'll just go use a competitor"
To me it suggest that they are indeed targeting enterprises, which makes sense since their visualization feature is really only valuable for complex projects. You probably should just use a competitor.
That is honestly totally fine. Companies dont want to deal with penny pinchers. They want a reliable corporate customer who is willing to commit to a yearly plan.
If information is being concealed, it's never, ever because honest people have good intentions and are engaging in activities that are making the world a better place.
Honestly and clearly displaying the price of products and services is not difficult. When that's deliberately not done, it means some fuckery is afoot.
For "enterprise" and large scale corporate sales, it usually means large contracts are negotiable on a case by case basis, but even then, the pricing will still fall within a range that's not difficult to explain at all. The only functional reason to withold information is to force potential customers into contact with salespeople and use everything they can to close (regardless of whether a customer is a penny pincher or not).
Every project management tool seems like a subset of features from 1990's project management tools, with the occasional UI innovation supporting collective decisions.
It's unclear (from the name and web site) how meegle differs or is better.
The key issue is granularity and accuracy of planning. This does not speak to that, and thus offers no promise to planners or implementors.
This is a deal breaker for me. You might have the coolest product but in this space I’ll buy something I can quote the price for to management without having to waste my time trying to talk to a sales rep.
Anyone else find the carousel on the homepage SUPER irritating. It's set to cycle faster than reasonable to read the diagrams etc. and gives 1998 pop-up-ad vibes which made me tab out.
Now, I call that management porn. Just like developers (like me) love to discuss matters like tabs vs spaces, vim vs emacs, linux vs bsd, go vs rust, monoliths vs microservices, orms vs plain sql, etc., managers tend to do the same, although perhaps it's not that obvious.
I just want to find a good mechanism to see a cross-project dependency graph so i can understand the broader impact of individual stories in any particular sprint. Eg two different five point stories that unblock external dependent stories. One rolls up to a finops poc and the other rolls up to a regulatory audit response.
JIRA obviously allows one to customize workflows as well, and I frankly don't really care about the visualization of it. The problem is that at many companies, there is one group that is allowed to change the workflow and they are more interested in conformity than allowing teams to work well.
Laggy landing page. Default template. No pricing. Just feels like a soulless cashgrab, whose name is entirely based on what domain name was available at the time.
It's not for engagement, it's usually because they don't actually have a standard pricing. It signals that they don't want small, self-serve customers, they only want to serve enterprise customers who want to negotiate custom contracts.
The scrolling use-cases in the hero section causes the with of the page to slightly change, causing other full-width elements to reflow, and the images cycling below fly by so fast that I couldnt really get anything out of them.
Yes large orgs will probably want to contact you for pricing but you are leaving business from smaller orgs on the table. My first reaction when seeing the "contact us for pricing" was "ok whatever I'll just go use a competitor"
Honestly and clearly displaying the price of products and services is not difficult. When that's deliberately not done, it means some fuckery is afoot.
For "enterprise" and large scale corporate sales, it usually means large contracts are negotiable on a case by case basis, but even then, the pricing will still fall within a range that's not difficult to explain at all. The only functional reason to withold information is to force potential customers into contact with salespeople and use everything they can to close (regardless of whether a customer is a penny pincher or not).
It's unclear (from the name and web site) how meegle differs or is better.
The key issue is granularity and accuracy of planning. This does not speak to that, and thus offers no promise to planners or implementors.
> The journey continues with even more to explore. Contact us for pricing
Now, I call that management porn. Just like developers (like me) love to discuss matters like tabs vs spaces, vim vs emacs, linux vs bsd, go vs rust, monoliths vs microservices, orms vs plain sql, etc., managers tend to do the same, although perhaps it's not that obvious.
For ICs, the biggest feature would be not having to use the tool; to have it infer everything from the tools actually used for work.
This is not a wallpaper problem. It’s a building codes problem. Until you can solve that,you might as well improve Jira.
Just a big “ugh, nah” for me
Has nice feature too, can create child issues in a few clicks from the parent.