Established escalation protocol for Product blockers
Situation
When Product (specifically Dawson) does not respond to meeting requests blocking engineering work, Nathan should explicitly request the meeting, then escalate to Peter and Bjorn via Slack if no response within 1-2 days. This creates a documented pattern of Product blocking Engineering.
Reasoning
Building a documented pattern of Product blocking Engineering to make the case to Bjorn. Escalation creates visibility and accountability - Bjorn needs to see this pattern firsthand. Gives Nathan a tool to escalate without it feeling like going over someones head - it is now the defined process. The AMD blocker is a symptom of a broader Product/Engineering alignment problem that needs executive attention.
Additional Context
AMD support project (~3-month engineering effort) is blocked because it is #37 on Product priority list but scheduled for February on the Mural Board. Dawson is not scheduling required meetings to unblock engineering decisions.
Related Context
fathom
Nathan will explicitly request meetings from Dawson. If no response in 1-2 days, Nathan will Slack Peter & Bjorn to escalate. This pattern of escalation is needed to create a clear record for Bjorn of how Dawsons actions are blocking progress.
Outcome
Getting clearer picture on where product is unintentionally obstructing engineering work.
Rating: 4/5
Decision ID: 3f4a6946-cb0c-46da-846c-5adcc61d9d7f