Search across all documentation pages
Solana products fail slowly when engineering and product talk past each other: "ship Friday" vs "audit blocked." These practices align roadmaps, specs, and communication without turning engineers into ticket machines or PMs into accidental security reviewers.
Enough to read specs and ask smart questions; security review stays with engineering.
PM prioritizes outcomes; tech lead injects harden/scale with veto on safety gates.
ADR for technical fork; exec for date vs safety with written risk memo.
Governance forum for params; eng blog for implementation - PM bridges both.
Written specs over verbal; record design reviews for async PM in other TZ.
DORA + user metrics in same QBR slide - connect delivery to outcomes.
PM defines rollout cohort; eng implements on-chain + client guards.
Comms lead role; not every engineer-PM pair - rotate training.
PM still signs spec acceptance before eng build.
Read ADRs, attend incident drill, ship one small devnet feature with eng pair.
Stack versions: This page was written for Agave 4.1.1, Solana CLI 3.0.10, Anchor 0.32.1, anchor-lang 0.32.1, Rust 1.91.1, @solana/kit 7.0.0, Surfpool 0.12.0, and LiteSVM 0.6.x.
Reviewed by Chris St. John·Last updated Jul 16, 2026