Home/AI Capability
The category
AI capability is what remains when the novelty wears off.
Tool access arrived quickly and evenly. Capability did not. This page sets out what we mean by AI capability, why we treat it as measurable, and how the whole Edney Learn architecture follows from that one definition.
A working definition
AI capability is the demonstrated ability to produce professional work through a redesigned AI-native workflow — one that integrates human expertise, AI, tools, explicit standards, verification and evidence — repeatedly, and to a stated quality. Operating that workflow is what makes a professional AI-augmented.
Every word in that definition is doing work.
- Demonstrated, not self-reported. There is a record.
- Redesigned workflow, not the old process with AI bolted onto one step.
- Integrates — human judgment and AI contribution are allocated deliberately, not by default.
- Explicit standards: the definition of good is written down before the work starts.
- Repeatedly — once is an anecdote. A system produces the next one too.
- To a stated quality — measured against something, not against a feeling.
What that looks like in practice
- Choosing which parts of the work AI should touch, which it should not, and being able to say why.
- Checking an output against a written professional standard before it leaves you, not against a feeling.
- Running a repeatable workflow in which who owns each decision is visible, not assumed.
Why measurable
Not because measurement is inherently virtuous, but because the alternative has failed. Organisations have spent three years running AI pilots that produce enthusiasm, then dissipate. Individuals have spent three years accumulating impressive outputs and no transferable skill. In both cases the missing element is the same: nothing was ever baselined, so nothing could be improved, defended, or built on.
If you cannot say where you started, you cannot say whether you moved.
The one-line version
Build the system. Produce the output. Retain the capability.
The architecture
How Edney Learn helps you build capability.
Everything we offer is a configuration of one shared architecture, which is how we serve an author and a project manager without becoming two companies. Start with what's current.
01 · Diagnose Pilot / CDR
Developmental diagnostic
A common core of seven dimensions plus a role overlay. Produces a self-reported baseline, a developmental interpretation and a suggested next step. One optional entry route, not a required first step.
The developmental profile02 · Design
Workflow design method
Ten stages that take you from target output to a documented operating procedure you own: run once per workflow, not once per task.
The method03 · Develop
Applied learning
Self-study packs, live implementation workshops and bounded coaching. You learn to operate and adapt the workflow, not to follow a prompt.
Programmes04 · Evidence
Capability evidence
Operating the workflow generates a record: judgment applied, AI contribution, validation decisions, output quality against standard.
Evidence policyWhat may come later
Institutional deployment (Licence) and assessment of demonstrated capability (Microcredential) are future architecture — scoped institutional pilots are available now, but there is no licence to buy or credential to earn today. Licensing → · Microcredentials →
Boundaries
What this is not.
The short version: tool fluency is being quick with a model; capability is operating a workflow to a standard you can evidence. The distinctions that follow all come back to that.
| Not this | Why the distinction matters |
|---|---|
| A prompt library | Prompts without workflow, standards, verification and evidence architecture produce inconsistent output and no capability. We do not sell collections of prompts. |
| An AI tools course | Tool training goes stale in months and transfers poorly. The workflow design method outlasts any particular model or vendor. |
| A done-for-you service | If we produce the output, you have an output. The point is that you retain a system that produces the next one without us. |
| Automation consulting | Our method deliberately preserves human judgment at defined points, and builds in stop conditions. Maximum automation is not the goal. |
| A certification body | Any future microcredential would assess demonstrated capability within a stated scope. It is not professional licensure and does not imply universal competence. It is future architecture. |
And it is not unbounded
Every workflow we help design carries explicit escalation triggers. Legal, medical, financial, compliance and other regulated matters go to qualified professionals. Decisions requiring accountable human judgment stay with a responsible human. Rights, permissions and confidentiality get reviewed, not assumed. See the escalation rules →
Start with a baseline