Get the FREE Ultimate OpenClaw Setup Guide →

Technology Assessment

Scanned
npx machina-cli add skill zircote/sigint/tech-assessment --openclaw
Files (1)
SKILL.md
5.8 KB

Technology Assessment

Overview

Technology assessment evaluates technologies for strategic fit, technical feasibility, and competitive advantage. This skill covers frameworks for making informed technology decisions.

Assessment Dimensions

Technical Maturity

  • Proven vs. emerging
  • Stability and reliability
  • Community/ecosystem size
  • Documentation quality

Strategic Fit

  • Alignment with business goals
  • Competitive differentiation potential
  • Integration with existing systems
  • Scalability trajectory

Risk Profile

  • Technology risk (will it work?)
  • Adoption risk (will people use it?)
  • Vendor risk (will they survive?)
  • Security risk (vulnerabilities)

Economic Factors

  • Total cost of ownership
  • Time to value
  • Resource requirements
  • Opportunity cost

Technology Readiness Levels (TRL)

LevelDescriptionCharacteristics
TRL 1-3ResearchConcept only, no implementation
TRL 4-6DevelopmentPrototype, limited deployment
TRL 7-8ProductionProven at scale, enterprise-ready
TRL 9MatureWidely adopted, commoditized

Gartner Hype Cycle Mapping

Position technologies on the hype cycle:

  1. Innovation Trigger: New technology emerges
  2. Peak of Inflated Expectations: Hype exceeds reality
  3. Trough of Disillusionment: Reality sets in
  4. Slope of Enlightenment: Practical use cases emerge
  5. Plateau of Productivity: Mainstream adoption

Build vs. Buy Framework

Build When:

  • Core competitive differentiator
  • Unique requirements not met by market
  • Long-term cost advantage
  • Internal expertise available
  • Control is critical

Buy When:

  • Commodity functionality
  • Time-to-market critical
  • Proven solutions exist
  • Maintenance burden undesirable
  • Lower total cost of ownership

Build vs. Buy Matrix

FactorWeightBuild ScoreBuy Score
Strategic importance30%1-51-5
Differentiation25%1-51-5
Time to market20%1-51-5
Total cost15%1-51-5
Risk10%1-51-5
Weighted Total100%X.XX.X

Technology Stack Analysis

Layers to Assess

Infrastructure

  • Cloud provider (AWS, Azure, GCP)
  • Compute (containers, serverless, VMs)
  • Storage and databases
  • Networking

Platform

  • Application frameworks
  • Runtime environments
  • Development tools
  • CI/CD pipeline

Application

  • Core product technologies
  • Third-party integrations
  • APIs and services
  • Security stack

Stack Evaluation Criteria

CriterionQuestionWeight
PerformanceDoes it meet requirements?High
ScalabilityCan it grow with us?High
MaintainabilityEasy to support?Medium
SecurityMeets compliance needs?High
CostFits budget?Medium
TalentCan we hire for it?Medium
CommunityActive ecosystem?Low

Trend Indicators for Technologies

Apply three-valued logic:

INC (Increasing adoption)

  • Growing community
  • Increasing job postings
  • Rising search interest
  • New investment/funding

DEC (Decreasing adoption)

  • Shrinking community
  • Declining job postings
  • Migration to alternatives
  • Vendor instability

CONST (Stable)

  • Mature, established
  • Steady usage patterns
  • No major changes

Competitive Technology Analysis

Assess how competitors use technology:

CompetitorKey TechnologiesStrengthsWeaknessesTrend
A[Stack][Advantage][Gap]INC/DEC/CONST
B[Stack][Advantage][Gap]INC/DEC/CONST

Technical Due Diligence

For M&A or partnership evaluation:

Architecture Review

  • System design and patterns
  • Scalability approach
  • Technical debt level
  • Documentation quality

Code Quality

  • Testing coverage
  • Code review practices
  • Security practices
  • Performance benchmarks

Operations

  • Deployment processes
  • Monitoring and observability
  • Incident response
  • SLA track record

Team

  • Skills and expertise
  • Key person dependencies
  • Knowledge documentation
  • Retention risk

Output Structure

## Technology Assessment Summary

### Technology: [Name]
**TRL**: [Level]
**Hype Cycle Position**: [Stage]
**Trend**: INC/DEC/CONST

### Evaluation Matrix
| Dimension | Score (1-5) | Notes |
|-----------|-------------|-------|
| Technical Maturity | X | [Note] |
| Strategic Fit | X | [Note] |
| Risk Profile | X | [Note] |
| Economic Factors | X | [Note] |
| **Overall** | X.X | |

### Build vs. Buy Recommendation
[Recommendation with rationale]

### Competitive Position
[How this tech compares to alternatives]

### Risk Assessment
- **Primary Risk**: [Risk and mitigation]
- **Secondary Risk**: [Risk and mitigation]

### Recommendations
1. [Recommendation]
2. [Recommendation]

### Monitoring Indicators
- [What to watch]
- [What to watch]

Best Practices

  • Evaluate against actual use cases, not theoretical
  • Include non-technical stakeholders in assessment
  • Consider long-term maintenance, not just implementation
  • Document assumptions and update as they change
  • Prototype before committing to major decisions

Additional Resources

For detailed frameworks, see:

  • references/tech-evaluation-matrix.md - Complete evaluation template
  • references/build-buy-analysis.md - Detailed build vs. buy
  • examples/tech-assessment-report.md - Sample assessment

Source

git clone https://github.com/zircote/sigint/blob/main/skills/tech-assessment/SKILL.mdView on GitHub

Overview

Technology Assessment helps you evaluate technologies for strategic fit, technical feasibility, and competitive advantage. It leverages frameworks like TRL, Gartner hype mapping, Build vs Buy, and stack analysis to inform technology strategy and roadmaps.

How This Skill Works

The process analyzes technical maturity, strategic fit, risk, and economic factors; it maps readiness using Technology Readiness Levels and Gartner hype cycle stages; it guides Build vs Buy decisions and evaluates stack layers (infrastructure, platform, application) to produce actionable recommendations.

When to Use It

  • When evaluating a new technology for strategic fit and ROI
  • During tech stack analysis for a new product or platform
  • To decide between building vs buying a component or capability
  • When assessing technology trends and readiness for roadmap planning
  • During due diligence or vendor risk assessment for critical tech

Quick Start

  1. Step 1: Define decision scope, success criteria, and key stakeholders
  2. Step 2: Map candidate technologies to TRL, strategic fit, and risk dimensions
  3. Step 3: Run Build vs Buy matrix, then generate a recommended action with owners

Best Practices

  • Define success criteria upfront across technical, business, and security dimensions
  • Use TRL and Gartner Hype Cycle to benchmark maturity and hype versus reality
  • Apply the Build vs Buy Matrix with weighted factors (strategic importance, differentiation, cost, risk)
  • Assess total cost of ownership, time to value, and resource requirements
  • Engage cross-functional stakeholders (architecture, security, product, and finance) in the decision

Example Use Cases

  • Evaluating whether to adopt a cloud-native service vs build in-house for a core product feature
  • Selecting a technology stack (infrastructure, platform, application) for a scalable SaaS offering
  • Performing vendor due diligence for a mission-critical integration
  • Mapping a technology roadmap using TRL levels and hype cycle stages
  • Competitive technology analysis to understand how rivals leverage the same tech and where differentiation exists

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers