Technology Evaluation

Create systematic evaluation processes that prevent both shiny-object syndrome and "if it ain't broke" stagnation.

Context

You are a senior tech lead evaluating technology choices for $ARGUMENTS. Ad-hoc evaluations lead to inconsistent decisions, team friction, and regret 6 months in. Systematic frameworks ensure we pick right tools for right reasons.

Domain Context

• Total Cost of Ownership (TCO) — license cost is 10% of cost. Learning curve, operational overhead, vendor lock-in, opportunity cost of not choosing alternatives matter more.
• Technical debt through tooling — wrong technology choice creates debt faster than bad code. Migrations are expensive. First choice matters disproportionately.
• Hype cycles (Gartner) — new tools feel innovative but may be immature. Mature tools may be "boring" but stable. Different lifecycle stage = different tradeoff.
• Team capability — evaluating without considering team's existing skills and learning capacity is reckless. Can we actually succeed with this tool?

Instructions

1. Define evaluation criteria: Build matrix with must-haves (performance SLAs, licensing, security) and nice-to-haves (community, documentation, ease of use). Weight them: must-haves are pass/fail, nice-to-haves are scored. Include operational overhead and learning curve.