Before sharing a campaign learning, capture one useful conclusion, link its evidence, name its owner and confirm who may see it. Then give it a clear approval status and a reference to the decision it will support. This proposed “Knowledge Promotion Receipt” gives teams a concrete way to distinguish working notes from knowledge ready for reuse.
The AIM Knowledge Library overview describes private organisational knowledge, deliberately shared network knowledge and ideas adopted into projects or campaigns. It also explains why ordinary conversations should not automatically become shared records. The workflow below turns those principles into a practical proposal—not a description of verified product functionality.
Separate storage, sharing and adoption
A useful starting point is to treat three questions separately: where does this knowledge belong, who may access it, and has anyone chosen to use it?
- Private knowledge: organisational methods, research, decisions and brand rules that remain within the organisation’s authorised audience.
- Shared knowledge: material deliberately approved for contribution to the AIM community.
- Adopted knowledge: an idea a team has chosen to use in a project, campaign or prototype.
Adoption should not be treated as proof that an idea works. A team can select an approach before testing it. Likewise, approval for internal use does not establish permission to publish the underlying evidence externally.
Start with the decision, not the archive
Before searching for reusable knowledge, write down the decision you need to make. For example: “Which message should we test in the next campaign?” Then specify what evidence would help and how the test will be assessed.
This decision-first approach is a proposal worth testing, rather than a demonstrated improvement. Its practical purpose is to make gaps visible: a relevant learning may come from another channel, lack supporting evidence or contain information that cannot be shared. Those limitations belong beside the conclusion, not hidden in the original conversation.
Create a minimum viable promotion receipt
Use a short record rather than copying an entire discussion. The proposed minimum is:
- Conclusion: one specific learning, with its limits stated plainly.
- Evidence reference: where the supporting material can be reviewed by an authorised person.
- Owner: the person responsible for accuracy and review.
- Sharing scope: private by default, with any wider audience explicitly identified.
- Approval status: draft, awaiting review or approved for a stated use.
- Reuse reference: the relevant campaign, project, decision or parent knowledge record.
Add topic, channel, country, method and confidence when they help someone interpret or retrieve the learning. Keep the first step short, but do not remove context that changes its meaning. A campaign observation without its conditions may be easy to read and difficult to use responsibly.
Review the conclusion and the permission separately
A proposed review workflow has three stages. In draft, the owner checks the evidence and looks for an existing record covering the same conclusion. In review, a named approver assesses both the wording and the intended sharing scope. Approval then records the permitted audience and use.
These checks answer different questions. Evidence review asks whether the conclusion is supported. Permission review asks whether the material may reach the proposed audience. A well-supported finding can still contain confidential information; an approved document can still contain a weak claim.
Keep reviews proportionate, but agree who can approve sharing and how approval can be withdrawn. The supplied overview does not establish reviewer roles, permission inheritance or revocation behaviour. These need verification before relying on any implementation.
Hypothetical example: promoting a campaign learning
Hypothetical example—not a reported customer outcome: a marketing team finishes a message test and wants to preserve its interpretation for a later campaign.
The owner drafts a narrow conclusion: “Consider retesting the service-led message with a comparable audience.” The receipt points to the internal test record and notes that the evidence does not justify a general claim about every audience or channel. Its scope remains private while a reviewer checks the interpretation and access permissions.
The next campaign references this receipt when planning its test. If the team later proposes a community contribution, it prepares a separately reviewed summary without confidential details. Any subsequent result is linked back to the adopted idea rather than presented as independent support for the original conclusion.
Preserve provenance without multiplying records
Before creating a new receipt, check whether the conclusion already exists. Update or reference the existing record when appropriate, while keeping genuinely independent evidence distinguishable. Several summaries derived from one test should not appear to be several separate tests.
The Library overview describes knowledge genealogy: references connecting original evidence, later improvements, adoption and measured results. A pilot can explore this using manual references. Automated connections between Library records, Network Hub ideas and campaigns should not be assumed from the overview alone.
Use approved knowledge carefully in PR briefs
A proposed secondary use is a claim-checking brief containing the intended claim, supporting source, limitations and explicit public-use permission. Internal approval alone is insufficient. Check the evidence quality and rights for every claim, and leave unresolved material out of public-facing copy.
Test the workflow before expanding it
First confirm the intended users and approval responsibilities; marketing teams and knowledge owners are a plausible audience, not a validated one. Then measure how representative users perform the current task before comparing it with the receipt prototype.
Suggested pilot criteria are four of five participants completing promotion unaided, all correctly identifying sharing scope, and no unauthorised access succeeding in permission tests. A 25% reduction in median task time is a proposed target, not an observed result. Track duplicate creation, missing context and keyboard completion too. Faster promotion is only useful if evidence remains understandable and sharing controls remain intact.

Add an example, conclusion or question.
Short, specific responses help AIM Community improve future articles and product decisions.