Turn Changes into Qualified Intelligence
Create an evidence-to-decision schema and triage observed changes consistently.
Why this decision matters
The observation states what the captured evidence shows. An attributed claim states what the competitor or reviewer says. Interpretation explains why the evidence might matter. A recommendation proposes a bounded next step. Confidence describes evidence strength, not emotional certainty. Threat and opportunity labels are useful only when their scoring anchors are visible and when no-action remains available.
This lesson advances the same capstone used throughout the course: the Competitor Intelligence Monitor Pack. The learner is not collecting ideas for later. The workbook record created here becomes an input to the next module and must be specific enough that another operator could review it. Where evidence is incomplete, the artifact should show the gap instead of smoothing it over.
Source evidence and limits
C6-S1 requires facts and interpretation to be separated. C6-S2 requires facts over opinions and honest competitor assessment. C6-S3 routes events while preserving source tier, confidence, unknown entities, and human gates.
The sources support the operating method stated above. They do not prove universal performance, guaranteed savings, complete market coverage, causal impact, or a client result. Any date-sensitive product, platform, competitor, legal, pricing, or policy fact must be checked against a current primary source before publication or operational use.
Continuing fictional example
Example: HarbourOps is a fictional Toronto workflow consultancy monitoring three invented competitors: BeaconFlow, TaskHarbor, and RelayDesk.
HarbourOps records that BeaconFlow's fictional pricing page now requests contact for the Starter tier. The possible implication is reduced price transparency, but pricing strategy and revenue intent remain unknown. The recommendation is to verify geography and account state, then review HarbourOps' own transparency - not to claim BeaconFlow raised prices.
Example boundary: Every company, page, event, and result in this example is fictional. It demonstrates the method and is not observed market evidence.
Workbook application
Use Workbook Section 5: Turn Changes into Qualified Intelligence. Complete Workbook Section 5. Classify five fixture observations into fact, attributed claim, interpretation, unknown, threat, opportunity, and recommended review. Cite the source for every factual clause.
- Write the current evidence or input before adding interpretation.
- Apply the lesson's decision rule and state the reason for the classification.
- Mark uncertainty, missing information, and the human owner for the next decision.
- Check that the result stays inside the course boundaries and can be tested.
Failure modes to inspect
Calling a job post proof of budget; treating complaints as prevalence; hiding competitor strengths; turning a recommendation into a forecast; and assigning numerical confidence without defined anchors.
A polished output can still fail if its evidence, permissions, identity, denominator, source date, or action boundary is wrong. Review the underlying record rather than grading tone alone. The correct repair may be to narrow the scope, gather a permitted source, label an unknown, or stop the proposed action.
Decision rules
Use plain labels. Explain what would raise or lower confidence. A recommendation must remain proportionate to the evidence. If the evidence is contradictory, escalate the contradiction.
Record the rule in the workbook in language two reviewers can apply consistently. A rule that depends on intuition alone cannot support a deterministic fixture. If reviewers disagree, preserve both readings, identify the missing evidence, and revise the rule before automation.
Three application checks
1. BeaconFlow replaces a visible price with Contact sales. Which statement belongs in the observation field?
2. Three public reviews complain about onboarding. What qualification is defensible?
3. Two credible sources conflict about whether a feature is available. What should the triage record do?