Most companies do not fail because their people are lazy. They do not fail because their software is bad. They do not fail because they lack dashboards, meetings, slogans, consultants, or executive offsites. They fail because their operating system was never actually designed. It was accumulated. A workflow here. A spreadsheet there. A ticket queue someone inherited. A project tracker nobody trusts. A governance meeting that approves things after the real decisions have alrea

Reflections from Team ’26, Atlassian’s Strategy Collection, and the emerging operating model of the AI enterprise. At Team '26, one theme kept surfacing beneath nearly every serious conversation about AI, transformation, and enterprise execution: Most organizations do not have a strategy problem.They have a structural coherence problem. That distinction matters. A lot. Because for the last decade, most enterprise portfolio management conversations have operated under an assum

By JB Higgins - FrontierOps Advisory There’s a phrase I heard repeatedly at this week that immediately resonated with me: “The Jagged Frontier.” The term comes from Ethan Mollick — one of the clearest thinkers currently writing about artificial intelligence and the future of work through his Substack, One Useful Thing. As someone who has spent decades inside large operational systems — Fortune 25 companies, enterprise transformations, large-scale Jira implementations, executi

I’m at Atlassian Team 26 right now and just saw a slide that said: “Current Data Quality in Jira: 90%” “↓ 40% Decrease Manual Reporting” Clean. Confident. Applause-ready. And completely incomplete. The Seduction of Clean Numbers If you’ve spent any time in enterprise software, you’ve seen this movie before. A system gets implemented. Governance gets layered in. Automation rules are added. Validation fields get tightened. And eventually, someone stands up and declares: “Our d

Why Most Implementations Stall - And How To Fix Them Most Atlassian Implementations Don’t Fail at Go-Live They fail quietly—months later. After the workflows are live.After the dashboards are built.After leadership assumes the hard part is over. That’s when the system starts to drift. Requests slow down Teams work around the tool Data becomes noise Ownership becomes unclear Eventually, the platform that was supposed to bring clarity becomes friction. Across dozens of environm

Every organization believes it understands its work. There are roadmaps, intake forms, governance meetings, and tools—lots of tools. And yet, ask a simple question: “Where is our work actually going?” Most leaders can’t answer it cleanly. Not because they lack intelligence, but because the system itself is lying to them. The Illusion of Control On paper, work looks organized. Planned initiatives sit neatly in roadmaps. Projects are approved through governance. Tickets flow th

Rules Are Good for Keeping Order. Too Many Rules Just Create Good Liars. Every organization eventually faces the same question: How much governance is enough? Rules are necessary. Anyone who has run a team, a company, or even a household knows this. Without structure, entropy wins. Work duplicates. Priorities conflict. People chase pet projects. Budgets drift. Rules create order. But there’s a tipping point most leaders don’t see coming. Add too many rules, and you don’t crea

Every greenfield ITSM implementation starts with optimism. New platform. Clean slate. Excited team. A long backlog of “things we’ve always wanted to fix.” That energy is good. It’s also dangerous. The biggest risk in a new implementation is not underbuilding. It’s building too much, too fast, in the wrong order. The Configuration Trap In the first few weeks of a new JSM instance, you’ll see the same pattern: Assets start getting defined in detail. Custom fields multiply. Serv

Why unclear ownership, broken service models, and unstable operations — not bad tools — are the real reason systems fail Most organizations don’t have a technology problem. They have an operations problem. And that’s not a critique. It’s a diagnosis. The Lie Everyone Quietly Believes Walk into almost any enterprise and you’ll hear some version of this: “We just need better tools.” No, you don’t. You already have: Jira ServiceNow Salesforce Dashboards stacked on dashboards Eno