Technology Vigilance: Proactive Technology Intelligence

Structured monitoring of the technology landscape to inform discovery decisions with up-to-date data on trends, maturity, adoption, and risks of proposed technologies.

Guiding Principle

We do not propose technology based on what we know — we propose based on what the market shows.

Technology vigilance is not "staying up to date." It is a systematic process of signal detection, classification by impact, and connection to ongoing architecture decisions.

Vigilance Philosophy

1. Signals before opinions. A Gartner/Forrester data point or a Stanford HAI paper carries more weight than "I believe that...".
2. Multiple sources, one synthesis. A signal confirmed by 3+ independent sources is a trend. A signal from 1 source is a data point.
3. Vigilance ≠ speculation. We report what sources say, with citation. We do not predict the future.
4. Sector context is mandatory. A trend in FinTech does not apply equally in HealthTech. Always connect to the client's sector.

Source Taxonomy

Tier 1: Analyst Firms (Quantitative, Paid)

Tier 2: Open Sources (Qualitative, Free)

Tier 3: Academic and Standards

Tier 4: Individual Thought Leaders

Delivery Structure

S1: Vigilance Context

S2: Detected Signals

Urgency classification:

• 🔴 High: Signal that could change the discovery recommendation
• 🟡 Medium: Signal that should be considered in the roadmap
• 🟢 Low: Informational signal for context

S3: Proposed Technology Positioning

For each technology in the proposed scenario:

S4: Sector Benchmark

Sector-specific signals for the client:

S5: Relevant Thought Leaders

Opinions and frameworks from thought leaders relevant to the project:

S6: Vigilance Recommendations

Source Mapping by Industry

When to Use

• Phase 0 (Plan): include relevant vigilance signals in discovery plan
• Phase 3 (Scenarios): validate proposed technologies against current landscape
• Phase 3b (Think Tank): feed updated radar data to the 7 Sages
• Standalone: technology landscape assessment for any engagement

When NOT to Use

• Highly constrained environments where technology is fixed (regulatory, legacy lock-in)
• Express discovery (time constraint overrides depth)

Trade-off Matrix

Output Configuration

• Language: Spanish (Latin American, business register — simple, clear, concise, direct)
• Attribution: Expert committee of the MetodologIA Discovery Framework
• Tagline: "Construido por profesionales, potenciado por la red agéntica de MetodologIA."

Validation Gate

• Technology stack positioned against >=2 sources
• Signals classified by urgency and impact
• Sector context connected to general signals
• Thought leader opinions cited with source
• Recommendations linked to specific signals
• Evidence tags: [ANALYST], [ACADEMIC], [OPENSOURCE], [REFERENT]

Output Artifact

Primary: A-05_Technology_Vigilance_{project}.md

Diagrams (Mermaid)

• quadrantChart: technology positioning (maturity x adoption)
• timeline: signal detection timeline

Casos Borde

Decisiones y Trade-offs

Knowledge Graph

graph TD
    subgraph Core["Technology Vigilance"]
        A["Signal Detection"] --> B["Source Triangulation"]
        B --> C["Urgency Classification"]
        C --> D["Sector Contextualization"]
        D --> E["Vigilance Recommendations"]
    end
    subgraph Inputs["Inputs"]
        F["Client Sector"] --> D
        G["Current Stack"] --> A
        H["Proposed Stack"] --> A
    end
    subgraph Outputs["Outputs"]
        E --> I["Technology Positioning Table"]
        E --> J["Sector Benchmark Report"]
    end
    subgraph Related["Related Skills"]
        K["dynamic-sme"] -.-> D
        L["scenario-analysis"] -.-> E
        M["multidimensional-feasibility"] -.-> B
    end

Output Templates

Markdown (default)

• Filename: A-05_Technology_Vigilance_{cliente}_{WIP}.md
• Structure: TL;DR > Vigilance Context > Detected Signals table > Technology Positioning > Sector Benchmark > Thought Leader References > Recommendations > Mermaid quadrantChart

HTML

• Filename: A-05_Technology_Vigilance_{cliente}_{WIP}.html
• Structure: MetodologIA Design System v4; interactive signal table with urgency color coding; embedded Mermaid quadrant and timeline; collapsible source citations

DOCX (bajo demanda)

• Filename: {fase}_{entregable}_{cliente}_{WIP}.docx
• Generado con python-docx, Design System MetodologIA v5. Portada con logo y metadata del proyecto, TOC automático, encabezados/pies de página con marca. Tablas con zebra striping. Tipografía: Poppins para encabezados (navy), Montserrat para cuerpo, acentos gold.

XLSX (bajo demanda)

• Filename: {fase}_technology-vigilance_{cliente}_{WIP}.xlsx
• Generado con openpyxl y MetodologIA Design System v5. Encabezados con fondo navy y texto Poppins blanco, formato condicional por urgencia de señal (🔴/🟡/🟢) y veredicto de tecnología, auto-filtros en todas las columnas, valores calculados sin fórmulas. Hojas: Señales Detectadas, Posicionamiento de Tecnologías, Benchmark Sectorial, Thought Leaders, Recomendaciones.

PPTX (bajo demanda)

• Filename: {fase}_{entregable}_{cliente}_{WIP}.pptx
• Generado con python-pptx y MetodologIA Design System v5. Slide master con gradiente navy, títulos en Poppins, cuerpo en Montserrat, acentos gold. Máx 20 slides versión ejecutiva / 30 versión técnica. Notas del orador con referencias de evidencia por slide. Slides sugeridos: portada, contexto de vigilancia, señales detectadas (tabla con semáforo de urgencia), posicionamiento de tecnologías propuestas (quadrant chart), benchmark sectorial, thought leaders relevantes, recomendaciones priorizadas (MUST/SHOULD/COULD).

Evaluacion

Umbral minimo: 7/10 en cada dimension para considerar el skill production-ready.