Atlassian finds 80% exclude engineers
- Atlassian’s 2026 State of Product report says 80% of product teams still leave engineers out of early-stage work, creating avoidable rework and late surprises. - The same survey, based on 1,000-plus product professionals across the U.S. and Europe, also found 84% fear their current products may fail. - That matters because tighter cross-functional collaboration is now a delivery issue, not just a process preference.
Product development has a coordination problem. Not a tooling problem first, and not an AI problem first — a people problem. Atlassian’s State of Product 2026 report puts a sharp number on it: 80% of teams do not involve engineers early in the process. That sounds like a workflow detail, but it’s really a bet that design, scope, feasibility, and timing can be sorted out later. Usually, they can’t. (atlassian.com) ### What did Atlassian actually measure? Atlassian surveyed more than 1,000 product professionals across the U.S., France, and Germany — including product managers, engineers, designers, and program managers — for its first annual State of Product report, published on September 3, 2025. The report is broad, but the standout point is simple: most teams still bring engineering in too late. (atlassian.com) ### Why is “early” such a big deal? Because early is when the expensive decisions still look cheap. A product idea can seem clean in a doc or mockup, but engineers see the hidden constraints fast — architecture limits, latency, security, migration pain, integration debt, weird edge cases. If those show up after a roadmap is blessed, the team either cut(atlassian.com)ate engineering involvement to missed opportunities and last-minute surprises. (atlassian.com) ### Isn’t that just how handoffs work? Basically, yes — and that is the problem. A lot of organizations still run product as a sequence: product defines, design shapes, engineering implements. That feels orderly, but it hides the real trade-offs until the end. Cross-functional teams work better when the trade-offs are exposed up front, because UX, perf(atlassian.com)ferent context: transformations are far more likely to succeed when the right leadership mix works together from day one. (bcg.com) ### Why is this showing up now? Because product teams are under more pressure than they used to be. Atlassian says 85% feel they have a seat at the strategic table, but that influence comes with scrutiny. The same report says 84% worry their current products won’t succeed in the market, and many teams lack enough time for strategy, roadma(bcg.com)hat makes bad handoffs more damaging. (atlassian.com) ### Where does AI fit into this? AI helps around the edges, but it does not solve the core coordination issue. Atlassian says most teams use 1 to 3 AI tools a day and save about 2 hours, mostly on routine tasks and documentation. But the report also says AI is not yet doing much of the high-value work teams actually want help with — prioritization, pla(atlassian.com)need for early engineering judgment. (atlassian.com) ### What does early engineering change in practice? It changes the conversation from “can we build this spec?” to “what is the smartest version of this outcome?” That is a huge difference. Engineers can suggest simpler architectures, flag risky dependencies, and reshape features before anyone gets emotionally attached to the wrong solution. The best ve(atlassian.com)he problem is still being framed. (atlassian.com) ### So what’s the bottom line? The Atlassian number matters because it shows how many teams still treat engineering as downstream execution. In 2026, that is less a cultural quirk than a delivery liability. When 80% of teams wait too long to bring engineers in, the surprise is not that products slip or get watered down. The surprise is that anyone still expects otherwise. (atlassian.com)
