FDE Adoption and Value for Openclaw

Convert post-POC evidence into a traceable adoption plan, value measurement framework, and evidence-based investment decision.

xukun0821
v1.0.0
Aug 7, 2026
0
281
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install fde-adoption-and-value

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install fde-adoption-and-value using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is FDE Adoption and Value?

FDE Adoption and Value is a structured workflow for moving from a successful proof of concept to a defensible conclusion about user adoption, business value, and continued investment. It analyzes real users, task behavior, technical outcomes, baselines, data sources, risks, enablement needs, and scale conditions without fabricating ROI or treating positive opinions as proof of value.

As part of Openclaw Skills, this skill produces an Adoption and Value Review Package that separates technical performance, task success, sustained usage, business outcomes, and risk. It helps teams decide whether to scale, correct, pause, or stop while preserving traceability between each claim and its evidence.

FDE Adoption and Value Use Cases

  • Post-POC reviews that need to determine whether real users will continue using the solution.
  • Adoption acceleration initiatives involving training, permissions, workflow integration, trust, incentives, or support barriers.
  • Business-value evaluations requiring baselines, targets, owners, data sources, and measurement windows.
  • Pre-scale planning for a new user cohort, department, workflow, or production environment.
  • FDE exit, customer takeover, enablement, support, and production-operations handoff planning.
  • Investigation of adoption and value conflicts, such as high usage with low value or low usage with high value.
  • Evidence-based reinvestment recommendations that account for implementation, operations, human review, integration, support, and risk costs.
  • Productization discovery based on repeated customer needs, implementation patterns, and cross-scenario evidence.

How FDE Adoption and Value Works

  1. Read the POC Run and Validation Report and revisit the frozen success criteria in the POC Engagement Charter.
  2. Freeze the target users, eligibility rules, adoption events, and measurement window.
  3. Recover business and task baselines from the charter and historical workflow, marking unavailable data as unvalidated.
  4. Build a metric tree that connects technical outcomes to task success, adoption, business outcomes, and risk.
  5. Segment users by role, scenario, frequency, experience, and risk to avoid generalizing from expert users.
  6. Track the adoption funnel from awareness and access through first success, repeat use, and workflow dependence.
  7. Interview users who adopt, refuse, or stop, distinguishing capability, value, trust, workflow, incentive, and enablement issues.
  8. Connect every value claim to a definition, baseline, target, data source, collection frequency, owner, and evidence label.
  9. Calculate incremental costs and document attribution limits, seasonality, business volume, staffing, and simultaneous policy changes.
  10. Design training, support, permissions, governance, operating conditions, and stop conditions for the next cohort.
  11. Decide whether to scale, correct, pause, or stop based on evidence rather than sunk cost.
  12. Handoff repeated cross-scenario needs and effective implementation patterns to fde-playbook-productizer for productization.

FDE Adoption and Value Setup

Prerequisites

  • Load this skill in the Openclaw Skills environment.
  • Provide the POC Run and Validation Report from fde-poc-runner.
  • Provide the POC Engagement Charter and its frozen success criteria.
  • Make available user, task, business-owner, baseline, workflow, and measurement data where possible.
  • Review the supporting references: adoption-input-guide.md, adoption-rules.md, value-measurement.md, and enablement-and-handover.md as applicable.

Installation and configuration

This skill defines a documentation-driven analysis workflow. The supplied specification does not require a package installation, API key, runtime service, or external CLI command. Configure the workflow by making the required POC artifacts and reference files available to the agent, then request an Adoption and Value Review Package.

The analysis should explicitly label unsupported claims as unvalidated and must not replace contract pricing, financial audit, procurement decisions, or formal commercial negotiation.

FDE Adoption and Value Data Schema & Taxonomy

Core evidence layers

Layer Required information Purpose
Technical System metrics, quality results, reliability, and limitations Determines whether the solution performs technically
Task User, task, workflow, completion, correction, and workaround data Determines whether users can complete meaningful work
Adoption Target population, denominator, active-use event, first success, repeat use, and drop-off Measures sustained behavior change
Business Outcome definition, baseline, target, data source, owner, and measurement window Tests whether value improved
Risk Negative effects, support load, permissions, governance, operational cost, and attribution limits Defines safe scale conditions and stop criteria

Metric metadata taxonomy

Every metric should include:

  • Definition: What is being measured and how it is calculated.
  • Population and denominator: Which users, tasks, or business volume are included.
  • Baseline: The pre-change or comparison value, or an explicit baseline gap.
  • Target: The threshold or directional outcome expected.
  • Data source: System telemetry, workflow records, interviews, business systems, or another source.
  • Collection frequency: The cadence for gathering and reviewing the metric.
  • Measurement window: Short windows for first success and longer windows for repeat adoption and business outcomes.
  • Owner: The person or team responsible for collection and interpretation.
  • Evidence status: customer-confirmed, FDE-inferred, or unvalidated.
  • Attribution limits: Seasonality, staffing, business volume, policy changes, correlation, and other confounding factors.

Review outputs

The Adoption and Value Review Package should organize target users, adoption events, metric trees, user segments, resistance findings, value claims, incremental costs, enablement requirements, scale conditions, stop conditions, and the recommendation to scale, correct, pause, or stop.

FDE Adoption and Value Advanced Features

  • Separates technical outcomes, task behavior, sustained adoption, business outcomes, and risk instead of collapsing them into a single success score.
  • Supports traceable metric trees from technical performance through task success, adoption, business value, and risk.
  • Diagnoses adoption resistance across workflow integration, trust, training, permissions, incentives, support, and change management.
  • Detects use-value conflicts, including high use with low value and low use with high value.
  • Segments users by role, scenario, frequency, experience, and risk before making scale recommendations.
  • Uses independent tasks and failure drills to validate knowledge transfer instead of relying on attendance counts.
  • Accounts for full incremental cost, including operations, human review, integrations, support, and risk.
  • Applies explicit evidence labels to distinguish customer-confirmed, FDE-inferred, and unvalidated claims.
  • Defines rollout conditions, governance requirements, cohort support, and stop criteria for safer scaling.
  • Handoffs repeated customer needs and effective implementation patterns to fde-playbook-productizer.
  • Prevents unsupported ROI claims, correlation-as-causation errors, and investment decisions driven only by sunk cost.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*