NENYA HORIZON + E-COACH · FOCUSED PILOT
Test one real workflow. Decide what comes next.
Evaluate one real workflow with Horizon and E-Coach. Finish with documented examples, a scorecard against agreed criteria and a recommendation to expand, adapt or close.
focused use case
users
after setup
A 30-minute working session to draft the use case, owner and success measures.
ILLUSTRATIVE PILOT SCENARIO
The release is due. What should give?
The date is committed. Defects are increasing, and the team is fully occupied with promised features. What should change?
OPTION 01
Hold date + scope
PROTECTS
The release commitment and promised features.
TRADE-OFF
Less room for quality work. Remaining release risk needs explicit acceptance.
OPTION 02
Reduce scope
PROTECTS
The release date and time for quality work.
TRADE-OFF
Some promised customer value moves to a later release.
OPTION 03
Move the date
PROTECTS
The planned scope and time for quality work.
TRADE-OFF
Customer commitments and dependent plans must be renegotiated.
Evidence informs the decision. Your context makes it useful.
Horizon makes quality and delivery evidence visible. Your team adds commitments, capacity and risk considerations. E-Coach helps examine goals, assumptions and trade-offs.
Your team decides the action, owner and review point.
The context carries into E-Coach
REAL PRODUCT EXAMPLE · DEMO DATA
Horizon’s Active Defects context carries into E-Coach. The conversation starts by clarifying the goal.
100
active defects
≤ 6
target
Product screenshot with demo data. Six is a target, not an achieved result. Tap or click to enlarge.
E-COACH QUESTION · SAME DEMO EXAMPLE
“Given this context, what is your primary goal in addressing the high Active Defects KPI?”
A decision the team can revisit
Illustrative team working note — not a product screenshot or automatic output.
CHOSEN OPTION
Reduce scope. Keep the date conditional on the readiness review.
Create capacity for prioritised quality work while protecting the release commitment.
Evidence considered
The defect trend, readiness assessment and team capacity in this illustrative scenario.
Assumptions to verify
Deferred features are not contract-critical, and the reduced scope creates sufficient capacity.
Accepted trade-off
Some customer value arrives later; residual release risk remains.
Owner and review
Release lead. Revisit at the next readiness review, or earlier if the assumptions change.
Agree what useful looks like
Before starting, agree which cases to compare, who will assess them, the quality rubric and the threshold for a useful result. Choose two or three success measures for the workflow.
Decision effort
PERSON-MINUTES
Preparation and review effort in person-minutes until a decision, owner and review point are agreed.
Track elapsed calendar time separately when relevant.
Quality of the rationale
Agree the rubric before starting:
01 Clear goal
02 Evidence and assumptions distinguished
03 Relevant options and trade-offs
04 Action, owner and review point recorded
A fair comparison
Compare similar cases with and without the tools, using the same criteria. Record relevant differences in complexity and user experience. If there are too few comparable cases, report that limitation and review the documented examples without claiming a measured effect.
Task measures go into the pilot scorecard. Horizon provides its supported engineering KPIs.
Your four weeks after setup
Before day one
Prepare the workflow
Agree the use case, baseline, target and success measures. Prepare approved inputs and access. Setup is planned for a few days once these are ready.
Week 1
Establish the comparison
Start with 5–10 users. Establish the baseline and compare similar decision cases using the agreed criteria.
Weeks 2–3
Use it in real work
Use the tools in real work. Review the measures, gather brief weekly feedback and record changes that affect the comparison.
Week 4
Review and decide
Review the documented examples and agreed scorecard. Nenya recommends expand, adapt or close; your team decides.
Clear responsibilities
Your team
A pilot owner, 5–10 users, approved inputs and the business context for real decisions.
Nenya
Configuration, onboarding, pilot records and a final recommendation. We agree the scope before the pilot starts.
A different starting point
The pilot can also focus on product or domain decisions, with Horizon where relevant, or on a defined internal-knowledge application with E-Coach. It is separate from the E-Coach free trial.
Let us define a pilot worth measuring
Bring one recurring challenge. Leave the working session with a draft use case, an owner and success measures.
We agree the scope, responsibilities, success criteria and commercial terms before the pilot starts.