"This isn't what we asked for." The autopsy of every failed feature starts here. And most of the time, the root cause is the same: product made technical decisions without technical input, then labeled the fallout a "collaboration problem."
The spec-as-handoff model is the culprit. PM spends weeks crafting a specification, hands it to engineering, engineering builds exactly what was specified, and the result is wrong. Both sides blame each other. Neither examines the process that guaranteed the failure.
The Structural Fix
Involve engineering before the spec exists. Not after. Before.
The spec-as-handoff is a power structure masquerading as a process. It establishes that product "figured it out" and engineering's job is to implement. This breaks because PMs optimize for user outcomes but lack the technical context to know which solutions are cheap and which are expensive, which are fragile and which are robust. Engineers have that context but never get asked.
A PM was about to spec a complex reporting dashboard based on user requests for "better analytics." The engineer who actually sat in on the user calls heard something different. Users didn't want dashboards. They wanted three specific metrics delivered reliably. An automated email with those three numbers -- two days of work instead of two months.
The shift: stop asking "How fast can you build X?" Start asking "What could we build to solve Y?"
The Leading Indicators
When the collaboration is working, two things happen. Specs get shorter, not longer -- because engineers in the room early means fewer edge cases need documenting. And features ship differently than originally planned, without anyone being upset -- because someone had a better idea mid-stream and the process accommodated it.
When neither of those is true, you have a handoff process, not a collaboration.
The Prerequisite
Most eng-product dysfunction isn't a process problem. It's a respect problem. PMs who don't value technical input will never collaborate authentically. Engineers who treat product thinking as "not my job" will never contribute strategically.
No framework fixes a respect deficit. Address that first. Everything else is theater.