ba-solution-evaluation

Evaluates solution performance against business value using BABOK KPIs and value realization analysis.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/NestorMonroy/thyrox --skill ba-solution-evaluation-nestormonroy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ba-solution-evaluation
Source: https://github.com/NestorMonroy/thyrox/tree/main/.claude/skills/ba-solution-evaluation
Command: npx skills add https://github.com/NestorMonroy/thyrox --skill ba-solution-evaluation-nestormonroy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? After a solution goes live, teams often lack a structured way to confirm whether it actually delivered the business value that justified the investment. This Skill executes the BABOK v3 Solution Evaluation knowledge area, measuring post-implementation performance against baselines and producing a documented verdict with next-step recommendations. ## Core Features & Use Cases - KPI Dashboard: Compares baseline, target, and actual values for each KPI with achievement thresholds (achieved, partial, not achieved). - Value Realization Assessment: Evaluates business need resolution, stakeholder satisfaction (NPS/CSAT/CES), ROI and payback, adoption metrics, and side effects. - Limitations & Lessons Learned: Documents functional, performance, usability, integration, and data limitations, plus per-KA lessons from the BA process. - Use Case: Thirty days after deploying a new claims-processing system, a business analyst uses this Skill to compare cycle-time and error-rate KPIs against the pre-implementation baseline, run adoption analysis, and recommend whether to close the initiative or launch an improvement iteration. ## Quick Start Ask the assistant to run a BABOK solution evaluation for your deployed solution using the available baseline metrics and production usage data.

Frequently Asked Questions about ba-solution-evaluation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate whether a solution delivered business value after implementation?▼

Compare post-implementation KPIs against the pre-implementation baseline and targets, then assess value realization across business need resolution, stakeholder satisfaction, ROI, and adoption. BABOK Solution Evaluation classifies each KPI as achieved (90%+ of target), partial (60-89%), or not achieved.

What is BABOK Solution Evaluation and when should it be used?▼

Solution Evaluation is the BABOK v3 knowledge area that measures solution performance and assesses whether the original business need was resolved. Use it after the solution is in real production use, typically at 30, 60, or 90 day reviews, never before at least 2-4 weeks of real usage data exists.

How long should I wait before evaluating a solution after go-live?▼

Wait a minimum of 2-4 weeks of real production usage. Process efficiency projects need about 4 weeks minimum, user experience projects about 6 weeks for the learning curve, and business transformation projects about 12 weeks for meaningful results.

How do I calculate ROI for a business solution evaluation?▼

ROI equals (realized benefit minus investment cost) divided by investment cost, times 100. Quantify benefits such as cost-per-transaction reduction, FTE time savings, error reduction, or revenue increase, then compute payback period as investment cost divided by annual benefit.

What are signs of low solution adoption to watch for?▼

Key signals include users running parallel manual processes like Excel workarounds, primary features with under 20% usage, rising support tickets, and users reverting to legacy systems for special cases. Workarounds indicate gaps between the solution and real user needs.

When should solution evaluation not be performed?▼

Do not evaluate before the solution is in real production use, since projections without real data are unreliable. Also do not use it to verify the solution was built correctly, which is a QA and testing concern rather than a business value assessment.