Test strategy
The standing approach to testing across an organisation or product: what gets automated, which risks justify which depth, which environments are maintained, how defects are triaged. A strategy outlives releases. A test plan applies it to one of them, which is why copying strategy text into every plan is a sign that neither document is doing its job.
Decisions, not descriptions
A strategy is useful when it settles questions people would otherwise argue about on every release. Which layers get automated tests and which stay manual. How deep testing goes for a payments change compared with a copy change. Which environments the team maintains and who owns their data. What blocks a release and what only gets logged. A document that describes testing in general terms without making those calls is an introduction, not a strategy.
Strategy versus plan
The strategy changes when the product, the team or the risk changes, perhaps once or twice a year. A test plan changes every release. When a plan contradicts the strategy, one of them is wrong, and it is worth finding out which before release day.
Who owns it
Usually the QA lead or head of QA, with engineering leadership agreeing to the parts that cost them time, such as test environments, automation ownership by developers and release gates. A strategy written by QA alone and never agreed by engineering tends to describe the testing QA would like rather than the testing that happens.
Signs it is not being used
Nobody can find it. Automation decisions are made case by case in standups. Release gates differ by who is on call. If any of those sound familiar, rewrite the strategy as a short list of decisions and link it from every plan.
In QAM Hub
A strategy is a document, not a feature. What a test management system adds is the evidence for it: which suites are automated, what the release gates showed, where defects escaped. The background is in what a test management system is and what to automate first.