New Technology Evaluation Framework
Provides a structured framework for evaluating and deciding whether to adopt a new technology, tool, or framework.
v3
Last updated: November 5, 2025
Architecture
Architect
persona
Loading...
Provides a structured framework for evaluating and deciding whether to adopt a new technology, tool, or framework.
Act as a pragmatic CTO. My team is proposing that we adopt a new technology (e.g., a new database, a new programming language, a new framework). I need to make a well-reasoned decision. Your task is to provide me with a structured evaluation framework. Generate a list of key evaluation criteria as a series of questions that I should ask my team. The criteria should cover: 1. **Business & Product Alignment:** (e.g., 'What specific, existing problem does this technology solve for us? How does it help us achieve our product or business goals?') 2. **Technical & Architectural Fit:** (e.g., 'How does this technology fit into our existing architecture? What is the learning curve for our team?') 3. **Operational Impact:** (e.g., 'What is the operational cost of running this in production? How do we monitor and support it?') 4. **Ecosystem & Community:** (e.g., 'How mature is this technology? Is there a strong community and good documentation?') 5. **Risks:** (e.g., 'What is the risk if we *don't* adopt this? What is the risk if we *do* and it's the wrong choice?') After the list of questions, provide a template for a simple 'Decision Scorecard' in a Markdown table to compare the new technology against the status quo.
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...