Writing a test strategy people will open in planning

Strategy documents fail when they read like frameworks. Planning meetings need a page that names risks, proposed automation depth, and the backlog order for the next two releases.

Structure that survives a calendar invite

Context and non-negotiable dates
Risk themes with owners
Automation depth by layer
Explicit accepts (what you will not cover)
Staged backlog with effort ranges

Tone

Write so a sceptical engineering manager can argue with you. Soft language invites polite ignoring. Mild disagreement in the room is a better outcome than silent shelfware.

After the workshop

One revision cycle is enough if discovery was honest. Endless polishing usually means the decision owners were not in the room the first time.