GRYD.IO ads

If you want sugar-coated Jira advice... I’m not your guy. 🙅🏼♂️ My job is to fix what’s broken. And that’s exactly what happened with Patricia C. I pulled together a 2-minute highlight reel showing the 3 biggest problems she faced and the fixes I suggested. 1. Too many required fields. 2. Reporting on active sprint data. 3. Stories being added during active sprints. By the end of our session, she had everything she needed to take action immediately to fix the core work management problems at Eaglebrook 𝗣.𝗦. 𝗪𝗮𝗻𝘁 𝗮 𝘁𝗼 𝗯𝗼𝗼𝗸 𝘆𝗼𝘂𝗿 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆 𝘀𝗲𝘀𝘀𝗶𝗼𝗻? Grab a slot here! https://lnkd.in/gx-5EEEg

3 reasons to use Team Managed Projects in Jira: 1. 2. 3. There are none. Now go clean your backlog. #AtlassianCreator #Jira Atlassian

How I helped a PM at a $70B company fix Jira in 27 minutes. Cash Coyne, Product Manager at Moody's - aka a massive enterprise financial organization booked a free consultation with me. We went through a ton of stuff to whip Jira back into shape. - Gamification - Labels fields - Issue hierarchy You name it, we hit it. Full video dropping soon on YouTube. https://lnkd.in/gAdbDpJ9 Subscribe if you want to watch a PM wrestle Jira into submission (and win). Gotta say - Cash Coyne is surprisingly good at managing his Jira environment. I was almost disappointed I didn’t get to roast him more. #AtlassianCreator #Jira Atlassian

Managing customers in Jira? They deserve better. 🤝 (The feature every JSM admin overlooks 🤦♂️) When I set up Jira Service Management, there’s one feature I always enable: 𝗖𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗮𝗻𝗱 𝗢𝗿𝗴𝗮𝗻𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗣𝗿𝗼𝗳𝗶𝗹𝗲𝘀. Why? Because without it, you’re guessing. Here’s what you unlock when you enable it: 🏢 See which organization each customer belongs to 📝 Relate custom fields to users and organizations 🔗 Track every request tied to that organization For teams juggling multiple customers, it’s a gamechanger. Most admins overlook this simple tweak. Don’t let it be you. #AtlassianCreator #Jira #Productivity Atlassian

Month 1: “We can fix this.” Month 3: “We’re still fixing this.” Month 6: “It’s unfixable... we need to start over.” Teams spend 6 months "fixing" a workflow that should have been deleted on day 6. You're not improving anything. You're prolonging the suffering. 𝗛𝗼𝘄 𝘁𝗼 𝗸𝗻𝗼𝘄 𝘆𝗼𝘂𝗿 𝗽𝗿𝗼𝗰𝗲𝘀𝘀 𝗻𝗲𝗲𝗱𝘀 𝘁𝗼 𝗱𝗶𝗲: Every stage has problems ↳ Not one or two stages - EVERY stage ↳ Your team expects things to break ↳ People sit around waiting for the fix ↳ Workarounds are part of the "official" process 𝗛𝗼𝘄 𝘁𝗼 𝗸𝗻𝗼𝘄 𝘆𝗼𝘂𝗿 𝗽𝗿𝗼𝗰𝗲𝘀𝘀 𝗻𝗲𝗲𝗱𝘀 𝗺𝗶𝗻𝗼𝗿 𝗳𝗶𝘅𝗲𝘀: ↳ One isolated problem area. ↳ Minor friction that doesn't halt progress. ↳ Everything else runs smooth. 𝗪𝗵𝗮𝘁 𝗜 𝘀𝗲𝗲 𝗺𝗼𝘀𝘁 𝘁𝗲𝗮𝗺𝘀 𝗱𝗼: Month 1: "Let's just adjust this one thing" Month 3: "Okay, maybe we need to fix this part too" Month 6: "Why does everyone still hate this process?" Sound familiar? Stop being a workflow doctor trying to save a dead patient. Sometimes the most productive thing you can do is admit your process sucks, throw it away, and build something that actually works. Is your team patching problems, or solving them? #AtlassianCreator #AtlassiaChampion #Jira #Process Atlassian

4 tools you should cancel today: Word, Smartsheet, Asana, Zendesk. Most teams are drowning in software. ↳ Word for docs ↳ Excel for tracking ↳ Asana for projects ↳ Zendesk for support That’s 4 or 5 tools, Jira and Confluence can do everything those tools can (but better!). The problem isn’t a lack of tools. It’s not knowing how to fully use the ones you’ve got. Atlassian isn’t just for devs. You can run projects, track requests, build workflows, write docs... All inside Jira and Confluence. ↳ Less context switching ↳ Lower license costs ↳ One source of truth Max out what you already have. Then think about adding more. But in most cases… You won’t need to. #AtlassianCreator #Jira #AtlassianEverything Atlassian