Learning path 04 · Lesson 1 of 5
- 4.1Implementing a system is not installing a toolRead
- 4.2Responsibilities, governance and evidenceRead
- 4.3Planning and operating the complete processRead
- 4.4Evaluating and improving without falling for vanity metricsRead
- 4.5Responsible self-diagnosis: from self-assessment to a 90-day planRead
From activity to capability
One person can review publications every day and produce a flawless summary without an organisational system existing. There is activity, but success depends on that person’s initiative: if they change roles, who knows which sources were supposed to be consulted, why they were chosen and what to do when one fails? If urgent news arrives, who can tell a curiosity from a threat that must be escalated?
A system requires stable connections between decisions, intelligence questions, source coverage, information processing, expert judgement, recipients, follow-up and learning. Those connections can start in a shared spreadsheet. Technical sophistication is neither a sufficient nor a necessary condition for having designed the function well.
What matters is not how much data is accumulated, but whether the organisation can answer:
- Which decisions and risks justify devoting resources to monitoring?
- What information are we looking for, and which universe of sources do we NOT cover?
- Who validates and who interprets the signals?
- What product does each recipient receive, when and with what expectation?
- How do we check that the information was useful and adjust the system?
Five symptoms of a superficial implementation
1. Monitoring everything. Without priorities, the team spends its time on visible events and overlooks the decisive ones. 2. Confusing volume with coverage. Thousands of alerts do not prove that the critical source has been reviewed. 3. Publishing without interpretation. A newsletter is no substitute for an explanation of consequences, assumptions and alternatives. 4. Depending on one person. Rules and lessons learned are lost when the analyst changes. 5. Measuring only activity. Counting news items disseminated says little about decisions supported or risks detected.
Interactive · Decide
Diagnose the symptom
Each situation shows a symptom of shallow implementation. Which one?
Activity: identify the symptom of shallow implementation in each situation.
“We get 3,000 alerts a month, so we are well covered.”
“When Ana left, nobody knew which sources she checked or why.”
“We monitor competitors, technology, markets, regulation, talent and everything else.”
“The annual report boasts of 52 newsletters sent.”
“The newsletter gathers 30 summarised news items, without saying what they imply.”
Company A case · simulation
Fictional caseCompany A case: false reassurance
A technician receives news related to thermal storage. They send a fortnightly newsletter to the innovation department. When management asks whether there is a solid signal for exploring alliances, nobody can reconstruct the selection criteria; nor is there anyone responsible for cross-checking patents against pilot tests. Monitoring activity exists, but its connection to the decision is fragile.
Improvement does not start with buying another system. It starts by stating the decision: should Company A explore a technology alliance over the next six months? Next come the questions, minimum evidence, owners and review thresholds. The technology is evaluated afterwards, against those needs.
Educational simulation: fictional information and organisations.
Interactive · Classify
Warm-up: what type of risk is each one?
The person who does monitoring is away for four weeks. Classify what could fail.
Activity: classify continuity risks as method, responsibility, data or tool.
Do it yourself
Do it yourself · Continuity test (15 minutes)
Imagine that the person who currently does the monitoring work is absent for four weeks. Write down what would be maintained, what would stop and which decisions would be left without information. Classify each risk as method, responsibility, data or tool. Choose three measures so that the system also works without that person.
Deliverable: a function continuity sheet with three prioritised risks, an owner and a resolution date.
Common mistakes: starting by comparing licences; confusing assigned tasks with understood responsibilities; documenting a process that nobody uses; promising total coverage. Key takeaway: the system exists when knowledge, criteria and responsibilities outlast any one person and can be reviewed.
Governance, responsibilities and versions
Document who decides, who can publish and how knowledge changes.
See the template →Maturity assessment and 90-day plan
Identify verifiable improvements and assign them a short cycle.
See the template →Check it · self-assessment
Check your continuity test
This part needs professional judgement: there is no automatic marking. Complete your work in the practice, rate it with the lesson's rubric and compare it with the indicative solution.
What your answer should include
- You classify each risk as one of method, responsibility, data or tool.
- There is a dated source inventory and a priority CWF question.
- The substitute has an access procedure and limited authority.
- If the substitute cannot carry out a check, you record it as «needs clarification».
Indicative solution
Model solution: a dated inventory, a priority CWF question, a permitted access procedure, a source health check, an incident log and a substitute with limited authority. Do not claim continuity just because you have a manual.
Mistake to avoid: Treating the purchase of a platform as enough.
Illustrative solution for a fictional case: reasoned alternatives are valid.
Optional extensionExtension · Telling capability, artifact and technology apart
The awkward-question test. An organisation claims to have a monitoring system because it pays for a licence, consults twenty sources and sends a newsletter every Friday. All three statements describe means or activity. They say nothing about who receives the newsletter, which alternative it could change or how an error is assessed. Investing more money in collection does not fix a poorly formulated strategic question.
Work with three layers, which must be auditable separately. Purpose layer: decision, recipient, horizon and the signals that would justify changing an option. Operational layer: sources, declared coverage, cadences, owners, validation, products and exceptions. Learning layer: incidents, changes of criteria and evidence of usefulness. When one layer fails, it cannot be compensated for by inflating another: many sources do not replace an explicit decision; a good decision does not prove that the sources work.
Company A example · Two situations, one unnecessary investment
| Fictional situation | What seems to work | What we do not know | Minimum experiment |
|---|---|---|---|
| A · 180 news items a month | Frequent collection | Whether the critical regulatory register is being observed | Check coverage and log gaps for 14 days |
| B · 8 news items a month | Short summary for management | Whether the conclusion distinguishes a contract from a commercial statement | Review the origin of three claims and log objections |
Do not compare A and B by volume. Compare whether they allow a decision to be supported with visible limits. The simplest option may work better, but we cannot claim it without testing its use.
Optional extension · 30-minute transfer test
Give someone outside the process a decision, a question, the source inventory, the filters and the latest briefing. Ask them to explain what they would monitor tomorrow, how they would detect that a source stopped working and who can issue an urgent alert. Do not let them ask the usual analyst during the test. Record three answers: can execute, needs clarification, cannot execute, with evidence of the obstacle. Fix a single critical failure first, assign an owner and repeat the test. Do not use «everything is documented» as the criterion: the criterion is that another person can actually act.
References and limits
- UNE · Asociación Española de Normalización. UNE 166006:2018. Gestión de la I+D+i: Sistema de vigilancia e inteligencia (2018). DocumentReference framework for watch and intelligence systems. Cited only as context, never as a source of requirements.Reference consulted on 2026-10-18.
- Company A is a fictional case: its data, companies and figures do not describe real markets or organisations.
- The five dimensions and the 0–3 scale are a pedagogical rubric of the Academy: they do not reproduce clauses of UNE 166006, do not replace an audit and do not allow you to declare conformity.
Intelligence Lab · L01
Maturity assessment
Ready to apply it? Open the Maturity assessment in the Lab and identify your improvement priorities in a downloadable result. Output: improvement priorities. Works in the browser, no server, no account and no connected AI. The result may need reviewing and adapting to your case.
Continue learning path 04
Back to learning path 04 · Method, governance and UNE 166006Choose another challenge