Jira Product Discovery's onboarding flow sparks joy.
-
Jira Product Discovery's onboarding flow sparks joy.
I know this is a thing that doesn't get said often for Atlassian tools, but I actually like this one.
-
Jira Product Discovery's onboarding flow sparks joy.
I know this is a thing that doesn't get said often for Atlassian tools, but I actually like this one.
@mayintoronto Jira is Built For Demo and Onboarding, it's the using it's not built for -
@mayintoronto Jira is Built For Demo and Onboarding, it's the using it's not built for
@silverwizard Isn't that the entire software industry?
Anyway, I know what I'm doing (for once), so it's good for me. It's a rare thing to see a tool that's not hated by the product community at large.
I can see how people could mess it up by putting too many rules in place.
-
@silverwizard Isn't that the entire software industry?
Anyway, I know what I'm doing (for once), so it's good for me. It's a rare thing to see a tool that's not hated by the product community at large.
I can see how people could mess it up by putting too many rules in place.
@mayintoronto Yep, I think it is!
Also - yeah - I assume you know the topic way more than me. I just can't pass up opprotunities to hate Atlassian
-
@mayintoronto Yep, I think it is!
Also - yeah - I assume you know the topic way more than me. I just can't pass up opprotunities to hate Atlassian
@silverwizard Yeah. Think of Jira like a spreadsheet. If you don't know what you're doing, it turns into your company's sales database when it's definitely not supposed to be that way.
Endlessly customizable. People forget what its purpose was in the first place.
-
@silverwizard Yeah. Think of Jira like a spreadsheet. If you don't know what you're doing, it turns into your company's sales database when it's definitely not supposed to be that way.
Endlessly customizable. People forget what its purpose was in the first place.
@silverwizard It's the same thing for every tool that's not opinionated. "You can do anything!" tools often have customers saying they suck, because
A) You definitely can't do just **anything**,
B) Your current processes have inherent issues, but there is only budget for tooling, not reworking your org,
C) You implement this tool that can be made to enforce the current way of working, which add Process and solidifies everything, the good and the bad, including the stuff that won't work with the new tooling because it's still a new workflow........ and
D) You can never change it again because when are you ever going to get the budget and the time to overhaul your whole workflow implementation? Every new request added more complexity, and now it's been 6 years of these quirks, known only to your Jira admin, who's retiring next year.
-
R relay@relay.mycrowd.ca shared this topic