Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Knowledge-driven process management is the support and coordination of emergent business work in which evolving knowledge, rather than a fixed goal or a predefined sequence of tasks, decides what should happen next. The overall goal may be vague or may change as the work proceeds, so the process is steered by what is learned along the way.
What the term means
The concept comes from John Debenham, an academic at the University of Technology Sydney, whose 2002 paper “Knowledge-Driven Processes Can Be Managed” was published in the proceedings volume AI 2002: Advances in Artificial Intelligence (Lecture Notes in Computer Science, pages 191–202). The paper’s abstract gives the core definition in one line: “A knowledge-driven process is guided by its ‘process knowledge’ and ‘performance knowledge’.”
A 2005 paper by the same author sharpens the idea. It argues that emergent process management needs an intelligent agent “driven not by a process goal, but by an in-flow of knowledge, where each chunk of knowledge may be uncertain.” The shift is from asking “what is the goal?” to asking “what does the accumulating knowledge say we should do now?”
Recommended Free Tools
Treat this as the author’s framing. No standards body or regulator has been identified that sets a formal definition, and the term is not a synonym for every workflow, knowledge-management programme or AI system.
#1 Best Overall
How it differs from task-driven and goal-driven work
The distinction is easiest to see when the three approaches are placed side by side.
| Question | Task-driven process | Goal-driven process | Knowledge-driven process |
|---|---|---|---|
| What directs the work? | A specified decomposition of activities | A stable goal that drives planning and execution | Contextual process knowledge and performance knowledge |
| Is the goal stable? | Not the central element | Yes, it is fixed for the work | Not necessarily; it may be vague or revised as the process patron learns more |
| Can the next step be specified in advance? | Yes, the sequence is defined | Partly, once the goal is set | Not fully; the next goal or action emerges from the work |
| Typical fit | Routine, repeatable procedures | Work with a clear target but flexible methods | Emergent work such as exploratory organisational decisions and e-market interactions, as described in the literature |
The practical difference is where the decision sits. In a goal-driven process, the goal settles the question of what to aim for and the plan follows. In a knowledge-driven process, the people and systems involved may not know the endpoint until they have some of the knowledge needed to reach it.
Process knowledge and performance knowledge
The definition rests on two kinds of knowledge. Both are tied to a particular process instance, not to the organisation’s general know-how.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Process knowledge
Process knowledge is information relevant to the instance in front of you. It is broad and it grows during the work. It can come from several sources:
- prior knowledge available when the instance starts;
- background information relevant to the case;
- what participants learn while the instance runs;
- information generated by users;
- information drawn from the environment.
Because the list keeps expanding, the process cannot be fully described at the outset. Each new fact may change what the next step should be.
Performance knowledge
Performance knowledge captures how effectively tasks or agents perform, including their reliability. It is used to choose the next task and the participant who should carry it out. A task that has repeatedly failed for a given kind of case, or an agent with a strong record on similar work, becomes a factor in the decision. Performance knowledge is updated after each action, so later choices reflect earlier results.
Rank #4
How the management cycle works
Debenham’s account describes a repeating cycle rather than a single planning step. In plain terms, the cycle runs as follows:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- Review what is known about the process and how earlier actions performed.
- Decide which outcome to pursue next.
- Select a task and the person or agent responsible for it.
- Carry out the task.
- Add the resulting process knowledge and performance knowledge, so the next decision starts from a richer base.
The process patron, meaning the person accountable for the work, keeps the contextual judgment in the foundational account. The system can record what happened and support execution, but it does not claim to understand all of the context behind a decision. Where a sub-process is conventional and a suitable plan exists, an agent or workflow system can run it, while the patron continues to manage the wider emergent process.
Best Value
What a system can and cannot automate
The model does not promise full automation. Several limits follow from the definition:
- Representability is the practical ceiling. Process knowledge can include large amounts of general or common-sense knowledge. If that knowledge cannot feasibly be represented or maintained, a system may support execution without fully managing the process.
- Structured pieces can be delegated. A knowledge-driven process may contain goal-driven sub-processes, and an agent can manage one when it has suitable plans.
- Knowledge-base processes are the easier case. When the relevant knowledge can be represented and accessed, management is more manageable, though this is a special case rather than the general rule.
- Recording is not understanding. A system can capture useful artefacts from the work, but capture alone does not give it the contextual judgment that the patron applies.
Where the term fits among related ideas
A related body of work uses the phrase “knowledge-intensive processes” for work that needs flexible support for non-routine problem solving. A 2021 article in that area argues that conventional business process management tools tend to focus on predefined processes, while knowledge-management systems often lack task context. It proposes an integrated, adaptable approach that can support dynamic work alongside structured procedures.
The two phrases overlap in subject matter but are not the same term. Use “knowledge-driven process” when referring to Debenham’s definition, and present the 2021 work as adjacent context.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteSource status and further reading
The core definition is a conceptual account from 2002, extended in 2005. It has remained stable as a way of describing processes, but it is an academic model rather than an industry standard, and it has not been widely codified in commercial tools. For the original wording, the 2002 chapter in the AI 2002 proceedings is the primary reference; the 2005 paper extends the argument about agents and uncertain knowledge.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
