[matte_black]

The problem I have with products like Asana has always been context. It’s just too much hassle for businesses with very unique processes, often requiring something more custom built, and of course, a deep introspection of data.

[radicaldreamer]

There are way too many "highly opinionated" productivity apps which are not built with enough freedom and "leeway" for anything but a very basic workflow. It's almost like the software is built for how the company itself works or from an idealistic design standpoint than for the messiness of complicated work.

I still think a properly configured JIRA instance is the best framework for a growing software company to build upon. It's very easy to misconfigure or mess up JIRA but done correctly, it's one of the best pieces of software for getting things done at a larger company (50+ people).

[ggg9990]

And then you have VSTS which can probably be configured to be a chess engine and thus takes 5 minutes to log a bug.

[matte_black]

Personally I’m not even thinking about software companies, I’m talking about the vast majority of companies out there in countless industries.

It’s just not possible to have a good generic app to serve all of them. There’s just too much variety in workflows and edge cases to capture them all, and few companies will change the way they work to accommodate the opinionated workflow of some productivity vendor.

The best solution is still to build custom applications for each company, molded around the way they work, and owned by them 100%, so they can feel fully confident that the product will not disappear or change in ways they don’t like.

[rushabh]

On non-tech setups, such systems are called ERP systems. The its a mature multi-billion dollar market with hundreds of entrenched players. The moment an application like Asana tries to cross that threshold, they get compared to the ERP products that are designed to handle specific workflow.

ERP products lack flexibility and generally have very poor user experience (since the buyers are not the users). I think there is a separate place for both these products and it depends on the organization when the switch from one domain to another.

[matte_black]

Thank you for that term ERP, I hadn’t heard it before but it describes precisely what I’m talking about.

[karthikvellanki]

I think it boils down to tradeoffs. For example- The best option (custom solution) may cost you 100k and drives max productivity. But if Asana (a more one size fits all product) costs you 20k and drives about 70% of max productivity - Asana might be the better option if the additional 30% productivity is not worth 80k.

[matte_black]

The risk with Asana though is vendor lock in. If your business comes to depend on Asana too much you’re at the mercy of whatever they do, including “shutting down and going out of business”.

[beachy]

The other solution, and a better one IMHO, is to extend the 80% product using their APIs. I'm not familiar with Asana but Trello has fantastic APIs including webhooks all that events in the tool can trigger activity in your integration.

[lbotos]

> It's almost like the software is built for how the company itself works or from an idealistic design standpoint than for the messiness of complicated work.

Isn't this a take on Conway's law?

As for your Jira point, so many people abused it to build bad process that it's flexibility is a negative point these days.

[tnolet]

Thank you. People love dissing Jira, but the current cloud product is actually by far the best and flexible software project management tool I’ve used in 20 years.

[eecc]

80% true, except for JIRA being an 80/20 tool that always leaves a bad taste in the details.

There’s plenty of issues like JIRASERVER-1330

[ex3ndr]

Try a cloud one, completely different product

[EGreg]

Why not Redmine? It's open source and super flexible!

Why can't people just make nicer themes for it lmao

[undecidabot]

Looks like what https://plan.io/ is doing. Looks good. Never used it myself, not affiliated in any way.

[PeterStuer]

The deep problem is that products like Asana are built around the paradigm of repeatable orchestrations of piecework, while business processes are exception prone choreographies of intelligent actors.

(Full disclosure: I work with a competitor of Asana, https://tasksinabox.com )