Using the Human–AI Knowledge Base Tool: A NaturFlourish Example
The Human–AI Knowledge Base Tool uses guided collaboration between people and AI to quickly develop candidate organisational knowledge, connect it across different organisational views, and test it against reality.
NaturFlourish provides a practical example of what the cycle produces at each stage.
The objective is not to create an authoritative AI-generated model.
It is to progressively develop a shared, connected and testable Knowledge Base that people can understand, challenge and improve.
The Human–AI Knowledge Base Cycle
The cycle begins with candidate stakeholders and progressively connects:
Stakeholders → Outcomes & KPIs → Value Propositions & Value Flow → Capabilities, Data & KPIs → Process Step Mapping → Gemba Validation → Learning, Reframing & Revision
The sequence provides a disciplined direction of enquiry, but it is not a waterfall. Any stage may reveal evidence that requires reconsidering an earlier assumption, boundary, or model element.
The entire cycle operates within Purpose, Ethics and Governance.
Every output begins as candidate knowledge. AI can research, compare, synthesise and propose structures rapidly. Humans contribute context, lived experience, practical judgement and accountability. Gemba provides the reality test.
From Knowledge Base to Operating Model
The Human–AI Knowledge Base Tool does not produce isolated artefacts. It develops a connected model of the organisation in which stakeholder outcomes, value, capability, data, work and consequence remain traceable to one another.
It progressively develops the relatively stable shared knowledge foundation on which the more variable operating model depends.
The foundation connects:
- Business Capabilities — what the organisation must be able to do;
- Data — what the organisation must understand and govern;
- and the Capability–Data relationship that connects organisational ability, information ownership and performance.
Upon that foundation sits the more variable superstructure through which value is created and delivered:
- stakeholder engagement,
- value propositions,
- value streams,
- processes,
- roles,
- decisions,
- systems,
- and other operating arrangements.
These views remain distinct, but they are explicitly connected.
The Human–AI Knowledge Base Cycle provides the method for developing and continually testing that connected organisational understanding.
What the cycle produced for NaturFlourish
Candidate Stakeholders
Question: Who matters?
AI develops an initial candidate view of the people, groups, and organisations that contribute to, depend on, influence, or experience consequences from NaturFlourish.
Deliverable
| Stakeholder | What matters |
| Customers / consumers | Safe, effective and understandable products; reliable service; trustworthy claims |
| Employees & contractors | Safe work, manageable workload, voice, clear authority and learning |
| Suppliers | Clear specifications, fair dealing and predictable demand and payment |
| Regulators | Compliance, trustworthy evidence, traceability and truthful representation |
| Practitioners, retailers & channel partners | Reliable products, clear information, fulfilment and reputation protection |
| Owners / Board | Long-term viability, trust, responsible growth and resilience |
| Community | Employment and contribution without unacceptable local burden |
| Environment / ecological systems | Avoidance of unacceptable emissions, waste and resource depletion |
| Logistics & distribution partners | Clear requirements, safe handling and predictable hand-offs |
This is a starting hypothesis, not a final stakeholder map.
- Stakeholder Outcomes & KPIs
Question: What matters to them, and what evidence would show it?
An outcome describes a condition experienced by the stakeholder. A KPI provides evidence about whether that condition is emerging.
| Stakeholder | Candidate outcome | Candidate evidence |
| Customers | Customers can obtain safe, effective and understandable products they can trust. | Repeat purchase, complaints, product-quality incidents, OTIF delivery |
| Employees | People can perform required work safely with manageable workload, reliable information and appropriate authority. | Safety indicators, engagement, fatigue/workload signals, rework |
| Suppliers | Suppliers can meet clear requirements without unreasonable transfer of cost, uncertainty or quality risk. | Supplier conformance, delivery reliability, disputes, corrective actions |
| Regulators | Regulators can rely on complete, traceable and trustworthy evidence of compliance. | Compliance incidents, deviations, release evidence, audit findings |
| Owners / Board | NaturFlourish remains viable while protecting trust, quality and organisational resilience. | Revenue growth, gross margin, innovation conversion, compliance |
| Environment | Products and operations avoid unacceptable waste, resource depletion and displaced environmental harm. | Carbon/waste intensity, energy use, yield and material loss |
No single measure tells the whole story. Speed must be read with quality, cost with stakeholder outcome, and throughput with human and environmental burden.
Status: Candidate Outcomes and KPI evidence — targets have not been assigned.
Value Propositions & Value Chain
Question: How does NaturFlourish propose to create value?
Example Value Proposition — Customers
For our customers and consumers, NaturFlourish provides safe, effective, and understandable nutraceutical products through evidence-based product design, controlled manufacture, truthful representation, and reliable supply, while protecting product integrity and trust.
Candidate Enterprise Value Chain
Trigger: an evidenced customer or market need.
Terminal value state: a safe, compliant product has been delivered and experienced, and the resulting evidence has entered organisational learning.
Different stakeholders experience this same flow differently. Customer, workforce, regulator and environmental perspectives are therefore represented as Stakeholder Value Views, rather than creating a different Value Stream for each stakeholder.
Status: Candidate Enterprise Value Chain and Principal Value Stream — pending Gemba validation and accountable ownership.
The value chain bridges what stakeholders value and what the organisation must be able to do.
- BCM – L3 Capabilities, KPIs & Data
Question: What must NaturFlourish be able to do and know?
Figure 1: NaturFlourish BCM as generated
The full Business Capability Model remains stable and manageable. For our worked example, only Manufacturing Management is opened to L3.
Manufacturing Management
The ability to plan, execute, control and improve manufacturing so NaturFlourish produces safe, compliant and effective nutraceutical products at the required quality, cost and service levels.
Manufacturing Planning & Control
- Master Production Scheduling
- Capacity Planning
- Material Requirements Coordination
Production Operations
- Batch Execution
- In-Process Control
- Yield & Loss Management
Packaging & Labelling Operations
- Packaging Line Setup
- Label Control
- Final Pack Verification
Manufacturing Systems & Execution Enablement
- Batch Record Management
- Equipment & Calibration Coordination
- Manufacturing Data Capture
Example of L3 Convergence
At L3, three views come together:
L3 Capability = Entity Ownership + Activity Set + KPI Cluster
Batch Record Management
Capability
The ability to create, review, complete, retain and retrieve authoritative batch records and associated evidence.
Principal information
Batch Record — the authoritative evidence of what occurred during a specific manufacturing batch.
Candidate Activities
- Create Batch Record
- Maintain Batch Evidence
- Review Batch Record
- Retain & Retrieve Batch Record
Candidate KPI evidence
- Batch record completeness
- Record correction/error rate
- Record completion timeliness
- Contribution to On-Time Batch Release
This makes the relationship visible:
What NaturFlourish must be able to do → what it must know → the work performed → how the capability can be judged.
Status: Capability and entity are Candidate Knowledge; the Activity Set and KPI cluster are Pattern Proposals for Gemba testing.
This begins to show not only what NaturFlourish must be able to do, but what it must know and measure to do it reliably.
Process Step Mapping
Question: How do capabilities combine when real work is performed?
Capabilities are not processes. The Process view shows how stable work from different capabilities is coordinated through conditions and sequence.
Example — Execute and Release a Production Batch
Production requirement authorised
- Confirm production and material readiness
- Authorise manufacturing work
- Execute the production batch
- Perform in-process control and capture evidence
- Complete the authoritative batch record
- Package, label and verify finished product
- Complete quality and release decision
- Transfer released finished goods into inventory
Released finished goods are available for fulfilment
The Process uses capabilities, Activities, information and decisions without taking ownership of them. The same capability or Activity may participate in other Processes and Value Streams.
Status: Pattern Proposal — sequence, exceptions, responsibility boundaries and actual Task Types require Gemba validation.
Gemba Validation
Question: Where does our model fail to describe what actually happens?
NaturFlourish already provides a useful example of why this matters. This is taken from the book Lead, Transform & Navigate, when Bruno’s updated BCM is taken to the Manufacturing Gemba for review.
Initial framing
Packaging may seem like a downstream choice made after product formulation.
Reality challenged the framing
When NaturFlourish examined real product options, packaging and formulation could not be separated.
A packaging option that worked mechanically required excipients that would undermine a proposed 100% organic claim.
Sachets could control dosage without some of those binders, coatings, or flow agents—meaning the packaging could do work otherwise imposed on the formulation.
Compostable formats introduced another trade-off: they better protected the environmental promise but created tighter operational and shelf-life constraints.
What changed
The issue was no longer:
Which package should we use?
It became:
How do formulation, packaging, manufacturing, claims, customer trust, environmental consequence, shelf life and economics remain coherent as one connected value system?
That is a reframe, not merely a correction to one specification.
It demonstrates the learning loop:
Model → Reality → Challenge → Reframe → Revised Knowledge Base
The model did not become weaker because reality contradicted its original framing.
It became more useful.
The discipline is simple:
- The model goes to Gemba.
- Gemba challenges the model.
- Humans and AI learn.
- The model changes.
A coherent model that has not survived informed challenge at Gemba remains a hypothesis.
What this example demonstrates
The NaturFlourish example shows that Human–AI collaboration can help an organisation:
The six deliverables together
WHO MATTERS? Candidate Stakeholders
→ WHAT MATTERS TO THEM? Stakeholder Outcomes & KPI Evidence
→ HOW IS VALUE CREATED? Value Propositions & Enterprise Value Chain
→ WHAT MUST WE BE ABLE TO DO AND KNOW? BCM + L3 Capabilities + Entities + Activities + KPIs
→ HOW DOES THE WORK COME TOGETHER? Process Step Mapping
→ DOES IT SURVIVE REALITY? Gemba → Confirm / Revise / Reframe
↺ The Knowledge Base changes
All of this remains contained by: Purpose · Ethics · Governance
AI may generate at machine scale. Humans can only validate at human scale.
The Knowledge Base must therefore remain mind-sized, discussable and testable.
Explore the NaturFlourish HAK Workbook
Open the candidate Human–AI Knowledge Base used in this worked example. The workbook is deliberately presented as a strawman for socialisation, challenge and Gemba validation.
Open the NaturFlourish HAK Workbook
Explore further
- 📝 Human–AI Knowledge Base Development
- 📝 Knowledge Operating System
- 📝 Gemba
- 📝 Stakeholder Engagement
- 📝 Value Stream
- 📝Business Capability Model
- Source Note: Human–AI Knowledge Base Development Guideline