Section 372 of 440
Complete canonical tutorial. This reader section contains the same teaching body as PWR-190 · Transactive memory. Open the Power dossier.
PWR-190 · SELF GUIDED full tutorial
Build a team expertise directory with retrieval, verification and backup
The community-fair cards turn transactive memory into a checkable directory: validated holders answer permit, power and accessibility questions, cite their source and nominate a backup. A second round removes the permit holder to test updating and retrieval. Success belongs to this stable fictional task, not to institutional knowledge in general.
1 · Permission and limits
Know exactly what you may do
2 · Get ready
Gather what you need and check the starting conditions
What you need
- Declared Transactive memory fixture: A three-person “community fair” team has separate verified cards for permits, power and accessibility. Six questions must be routed, and a second round removes the permits holder.
- Setup aid for Validate the directory: Define who may see and edit the directory.
- Transactive memory log: Correct retrieval, redundancy and task outcome across delay and membership change; retain Transactive memory errors, assistance, stop and fallback.
- Transactive-memory source grid: compare “Group Versus Individual Training and Group Performance: The Mediating Role of Transactive Memory” with the longitudinal knowledge-worker-team study. Record directory formation, specialisation, retrieval, verification, time point and performance outcome. Use TeamSTEPPS to check the six fair questions and the permit-holder absence without treating recall as institutional truth.
- Fictional source cards: PERMITS P1—food stalls use form P-2, amplified sound uses form P-4, and all forms are due 12 April. POWER W1—each outdoor outlet has a 16-amp cap, leads must be outdoor-rated, and the checked source is revision 3 dated 1 May. ACCESS A1—keep a 1.2-metre clear aisle, provide a quiet seating point, and caption stage announcements. Directory entries must name P1, W1 or A1 and their dates.
- Validation questions with keys: V1 food-stall form? P-2; V2 amplified-sound deadline? 12 April; V3 outdoor outlet cap? 16 amps; V4 required lead type? outdoor-rated; V5 aisle width? 1.2 metres; V6 which announcements need captions? stage announcements. New routing round: Q1 quiet seating domain, Q2 food stall form domain, Q3 outlet load domain, Q4 captioning domain, Q5 amplified sound domain, Q6 lead rating domain. Correct domains are ACCESS, PERMITS, POWER, ACCESS, PERMITS, POWER.
- Absence and update cards: remove the permits holder, then ask Q7 “Which form covers amplified sound?” (P-4) and Q8 “When are forms due?” (12 April); the backup must retrieve P1. After that round reveal W2, revision 4 dated 8 May: “outdoor outlets remain 16 amps, but every lead now also needs the blue inspection tag.” The team must replace W1’s current pointer rather than silently mixing revisions.
Before you start
- Use fictional records and no real confidential organisational knowledge.
- Define who may see and edit the directory.
- Start check for Transactive memory: No member is labelled a general expert.
- Top-of-sheet stop for Transactive memory: Stop if the directory exposes private, security-sensitive or personnel-evaluation information.
3 · The method
Follow these steps in order
- Name bounded domains
List permits, power and accessibility with what each domain includes and excludes.
Why: No member is labelled a general expert.
Check: No member is labelled a general expert.
- Validate the directory
Give each holder two answer-key questions in their domain and record correct, uncertain and corrected responses.
Why: Directory entries are based on task evidence, not self-confidence alone.
Check: Directory entries are based on task evidence, not self-confidence alone.
- Store who-knows-what
Create a shared card with holder, backup, source location, last check and contact route.
Why: Every domain has a primary holder and a source that others can reach.
Check: Every domain has a primary holder and a source that others can reach.
- Route before searching randomly
For each new question, consult the directory, ask the holder and log the route taken.
Why: The question reaches the relevant person without repeated team-wide searching.
Check: The question reaches the relevant person without repeated team-wide searching.
- Verify the returned answer
The receiver checks the named source and records any correction.
Why: Knowing whom to ask does not replace source verification.
Check: Knowing whom to ask does not replace source verification.
- Add minimum redundancy
Teach the backup where the source is and how to recognise an out-of-date answer, without duplicating every detail.
Why: A second person can retrieve the source when needed.
Check: A second person can retrieve the source when needed.
- Run the absence test
Remove the permits holder for round two and answer two permit questions using the backup and record.
Why: The team completes the task and shows any extra time or error.
Check: The team completes the task and shows any extra time or error.
- Update after change
Correct the directory when a source, membership or domain changes and date the revision.
Why: Stale expertise is not carried into the next round.
Check: Stale expertise is not carried into the next round.
4 · Worked example
See the whole method used once
Scenario
A three-person “community fair” team has separate verified cards for permits, power and accessibility. Six questions must be routed, and a second round removes the permits holder.
Walkthrough
- The team validates Mina on permits, Jo on power and Rae on accessibility using two practice cards each.
- It creates a directory with one backup and source folder for each domain.
- Six new questions are routed; each answer is checked against the named fictional source.
- In round two Mina is unavailable, so Jo uses the permits backup entry and source folder.
- The team answers both permit questions correctly but takes two extra minutes, which is recorded as a resilience cost.
- It updates the directory after discovering one power source card has a newer date.
Result
The team retrieves and verifies all answers, including during one simulated absence. This shows a working directory for this stable task, not institutional knowledge or universal resilience.
5 · Right and wrong
Compare correct or safer execution with the common wrong version
| Moment | Right / safer | Wrong / riskier | Why it matters |
|---|---|---|---|
| Domain boundary | Say exactly what the person knows and does not know. | Call someone the team’s universal expert. | Expertise is task-specific and can become stale. |
| Directory evidence | Use practice answers and source ownership. | List the most confident or senior person. | Confidence and rank can misroute questions. |
| Answer verification | Check the source after retrieval when completing the community-fair expertise directory. | Treat “Alex said so” as proof. | Transactive memory locates knowledge; it does not guarantee correctness. |
| Member change | Maintain a backup and dated record. | Keep all critical knowledge in one person’s memory. | Absence or turnover can break retrieval. |
6 · Common mistakes
Spot the error and apply the correction
| Mistake | Fix |
|---|---|
| Call someone the team’s universal expert. | Split broad labels into validated domains. |
| List the most confident or senior person. | Validate on the actual question type. |
| Treat “Alex said so” as proof. | Link every answer to the current source. |
| Keep all critical knowledge in one person’s memory. | Teach source location and update rules to a backup. |
7 · Practice
Turn the steps into a usable skill
First session
- Community-fair directory run: A three-person “community fair” team has separate verified cards for permits, power and accessibility. Six questions must be routed, and a second round removes the permits holder.
- Bounded-domain map: Name bounded domains: List permits, power and accessibility with what each domain includes and excludes.
- Routed retrieval and source check: Route before searching randomly, then Verify the returned answer.
- Universal-expert correction: if “Call someone the team’s universal expert.” appears, apply “Split broad labels into validated domains.”
- Revision update: Update after change: Correct the directory when a source, membership or domain changes and date the revision.
Repeat plan
Run six retrieval questions weekly for three weeks. Test one member absence in week two and a source update in week three; review the directory monthly or immediately after membership or scope changes.
Progress when
- No member is labelled a general expert.
- Directory entries are based on task evidence, not self-confidence alone.
- Every domain has a primary holder and a source that others can reach.
- At least 90% of questions reach the right bounded domain, all answers cite a current source, and one-member absence is handled without an unverified guess.
Do not progress when
- Do not continue while this error remains: Call someone the team’s universal expert.
- Pause until this correction works: Validate on the actual question type.
- This Transactive memory stop ends the block: Stop if the directory exposes private, security-sensitive or personnel-evaluation information.
8 · Check the result
Measure what changed
Correct retrieval, redundancy and task outcome across delay and membership change
How: Baseline fixture: A three-person “community fair” team has separate verified cards for permits, power and accessibility. Six questions must be routed, and a second round removes the permits holder. Enter success checks from “Name bounded domains” and “Verify the returned answer”. If “Call someone the team’s universal expert.” occurs, apply its named fix; then score Correct retrieval, redundancy and task outcome across delay and membership change on the unused “Update after change” item.
Good result: At least 90% of questions reach the right bounded domain, all answers cite a current source, and one-member absence is handled without an unverified guess.
This does not prove: Boundary for Transactive memory: “Correct retrieval, redundancy and task outcome across delay and membership change” describes only A three-person “community fair” team has separate verified cards for permits, power and accessibility. Six questions must be routed, and a second round removes the permits holder. It cannot establish “Build a team that never forgets”.
Self-check
- Without the example, demonstrate: No member is labelled a general expert.
- Find the fault in this attempt: “Call someone the team’s universal expert.” Apply “Split broad labels into validated domains.”; what changes?
- What evidence in the completed record shows that this is wrong: “List the most confident or senior person.”?
- Transactive memory stop decision: Stop if the directory exposes private, security-sensitive or personnel-evaluation information.
9 · Stop, adapt or get help
Keep the safety boundary practical
Stop and get help
- Stop if the directory exposes private, security-sensitive or personnel-evaluation information.
- Pause when a holder or source is outdated, unavailable or outside scope.
- Use formal knowledge, records and continuity processes for regulated or safety-critical operations.
Accessibility and adaptations
- Provide the directory in searchable text, large print, icons or audio, with more than one contact route.
- Use asynchronous questions and allow response windows rather than treating speed as expertise.
10 · Evidence and limits
Why these instructions are here
- primary research
Registered support for Transactive memory: “Group Versus Individual Training and Group Performance: The Mediating Role of Transactive Memory”. It bears on Correct retrieval, redundancy and task outcome across delay and membership change inside the Transactive memory fixture. It does not validate “Build a team that never forgets”.
Group Versus Individual Training and Group Performance: The Mediating Role of Transactive Memory - primary research
Constraint for Transactive memory, drawn from “Knowledge and Performance in Knowledge-Worker Teams: A Longitudinal Study of Transactive Memory Systems”: Evidence relied on stable small groups and bounded tasks.
Knowledge and Performance in Knowledge-Worker Teams: A Longitudinal Study of Transactive Memory Systems - official guidance
TeamSTEPPS boundary for Transactive memory: apply engagement while observing “Correct retrieval, redundancy and task outcome across delay and membership change”. Rehearse Validate the directory, then use the Transactive memory teach-back and debrief.
TeamSTEPPS 3.0
Limits
- Transactive memory boundary: interpret “Correct retrieval, redundancy and task outcome across delay and membership change” only for A three-person “community fair” team has separate verified cards for permits, power and accessibility. Six questions must be routed, and a second round removes the permits holder.
- A successful result does not establish “Build a team that never forgets”.
- Transactive memory limiting finding: Evidence relied on stable small groups and bounded tasks.
- Transactive memory limiting finding: Face-to-face communication effects did not generalize to every channel, and observational field associations do not prove causation.
- Scope remains Transactive memory: A three-person “community fair” team has separate verified cards for permits, power and accessibility. Six questions must be routed, and a second round removes the permits holder. Recheck the comparator, support and “Correct retrieval, redundancy and task outcome across delay and membership change” after any configuration change.
Open the complete canonical research register
- Primary empirical supportLimiting / contraryGroup Versus Individual Training and Group Performance: The Mediating Role of Transactive Memory
Diane Wei Liang; Richard Moreland; Linda Argote · 1995 · Primary research
- Primary empirical supportLimiting / contraryKnowledge and Performance in Knowledge-Worker Teams: A Longitudinal Study of Transactive Memory Systems
Kyle Lewis · 2004 · Primary research
- Official boundary contextTeamSTEPPS 3.0
Agency for Healthcare Research and Quality · 2023 · Official training framework
- Limiting / contraryOfficial boundary contextEmployment practices and data protection: monitoring workers
Information Commissioner’s Office · 2023 · Official guidance
Read the complete evidence interpretation on the Power dossier.
Tutorial delivery controls
Learn, adapt, troubleshoot and resume
Progress is saved only in this browser on this device.
Step-by-step learner mode
Each activity includes its success check, a nearby accessible alternative and an “I’m stuck” correction path. Alternatives preserve the target where possible; when they change the task, Titan labels them as related rather than equivalent.
Name bounded domains
List permits, power and accessibility with what each domain includes and excludes.
No member is labelled a general expert.
No member is labelled a general expert.
I’m stuck on this step
Reset: Re-read this authored instruction — “List permits, power and accessibility with what each domain includes and excludes.” — and its success check, then attempt only this step.
Possible snag: Call someone the team’s universal expert.
Correction: Split broad labels into validated domains.
Possible snag: List the most confident or senior person.
Correction: Validate on the actual question type.
Stop / get help: Stop if the directory exposes private, security-sensitive or personnel-evaluation information.
Validate the directory
Give each holder two answer-key questions in their domain and record correct, uncertain and corrected responses.
Directory entries are based on task evidence, not self-confidence alone.
Directory entries are based on task evidence, not self-confidence alone.
I’m stuck on this step
Reset: Re-read this authored instruction — “Give each holder two answer-key questions in their domain and record correct, uncertain and corrected responses.” — and its success check, then attempt only this step.
Possible snag: The result from “Give each holder two answer-key questions in their domain and record correct, uncertain and corrected responses.” does not yet meet this declared check: Directory entries are based on task evidence, not self-confidence alone.
Correction: Return to the start of “Validate the directory”, reduce complexity or pace, and repeat only the part needed to satisfy: “Directory entries are based on task evidence, not self-confidence alone.”
Stop / get help: Stop if the directory exposes private, security-sensitive or personnel-evaluation information.
Store who-knows-what
Create a shared card with holder, backup, source location, last check and contact route.
Every domain has a primary holder and a source that others can reach.
Every domain has a primary holder and a source that others can reach.
I’m stuck on this step
Reset: Re-read this authored instruction — “Create a shared card with holder, backup, source location, last check and contact route.” — and its success check, then attempt only this step.
Possible snag: Keep all critical knowledge in one person’s memory.
Correction: Teach source location and update rules to a backup.
Stop / get help: Stop if the directory exposes private, security-sensitive or personnel-evaluation information.
Route before searching randomly
For each new question, consult the directory, ask the holder and log the route taken.
The question reaches the relevant person without repeated team-wide searching.
The question reaches the relevant person without repeated team-wide searching.
I’m stuck on this step
Reset: Re-read this authored instruction — “For each new question, consult the directory, ask the holder and log the route taken.” — and its success check, then attempt only this step.
Possible snag: The result from “For each new question, consult the directory, ask the holder and log the route taken.” does not yet meet this declared check: The question reaches the relevant person without repeated team-wide searching.
Correction: Return to the start of “Route before searching randomly”, reduce complexity or pace, and repeat only the part needed to satisfy: “The question reaches the relevant person without repeated team-wide searching.”
Stop / get help: Stop if the directory exposes private, security-sensitive or personnel-evaluation information.
Verify the returned answer
The receiver checks the named source and records any correction.
Knowing whom to ask does not replace source verification.
Knowing whom to ask does not replace source verification.
I’m stuck on this step
Reset: Re-read this authored instruction — “The receiver checks the named source and records any correction.” — and its success check, then attempt only this step.
Possible snag: The result from “The receiver checks the named source and records any correction.” does not yet meet this declared check: Knowing whom to ask does not replace source verification.
Correction: Return to the start of “Verify the returned answer”, reduce complexity or pace, and repeat only the part needed to satisfy: “Knowing whom to ask does not replace source verification.”
Stop / get help: Stop if the directory exposes private, security-sensitive or personnel-evaluation information.
Add minimum redundancy
Teach the backup where the source is and how to recognise an out-of-date answer, without duplicating every detail.
A second person can retrieve the source when needed.
A second person can retrieve the source when needed.
I’m stuck on this step
Reset: Re-read this authored instruction — “Teach the backup where the source is and how to recognise an out-of-date answer, without duplicating every detail.” — and its success check, then attempt only this step.
Possible snag: Treat “Alex said so” as proof.
Correction: Link every answer to the current source.
Stop / get help: Stop if the directory exposes private, security-sensitive or personnel-evaluation information.
Run the absence test
Remove the permits holder for round two and answer two permit questions using the backup and record.
The team completes the task and shows any extra time or error.
The team completes the task and shows any extra time or error.
I’m stuck on this step
Reset: Re-read this authored instruction — “Remove the permits holder for round two and answer two permit questions using the backup and record.” — and its success check, then attempt only this step.
Possible snag: The result from “Remove the permits holder for round two and answer two permit questions using the backup and record.” does not yet meet this declared check: The team completes the task and shows any extra time or error.
Correction: Return to the start of “Run the absence test”, reduce complexity or pace, and repeat only the part needed to satisfy: “The team completes the task and shows any extra time or error.”
Stop / get help: Stop if the directory exposes private, security-sensitive or personnel-evaluation information.
Update after change
Correct the directory when a source, membership or domain changes and date the revision.
Stale expertise is not carried into the next round.
Stale expertise is not carried into the next round.
I’m stuck on this step
Reset: Re-read this authored instruction — “Correct the directory when a source, membership or domain changes and date the revision.” — and its success check, then attempt only this step.
Possible snag: The result from “Correct the directory when a source, membership or domain changes and date the revision.” does not yet meet this declared check: Stale expertise is not carried into the next round.
Correction: Return to the start of “Update after change”, reduce complexity or pace, and repeat only the part needed to satisfy: “Stale expertise is not carried into the next round.”
Stop / get help: Stop if the directory exposes private, security-sensitive or personnel-evaluation information.
Correct versus incorrect execution
These accessible process diagrams are built from the tutorial’s own right/wrong teaching. They are not anatomical illustrations and do not add technique beyond the canonical tutorial.
Say exactly what the person knows and does not know.
Call someone the team’s universal expert.
Use practice answers and source ownership.
List the most confident or senior person.
Check the source after retrieval when completing the community-fair expertise directory.
Treat “Alex said so” as proof.
Maintain a backup and dated record.
Keep all critical knowledge in one person’s memory.
Method-structure checklist
10 of 10 structural checks present
- Ordered, Power-specific instructions — present
- Every activity has a success check — present
- Materials or supplied records are declared — present
- Measurement or assessment rule is present — present
- Tutorial-specific troubleshooting is present — present
- Stopping or escalation boundary is present — present
- Every activity has an adjacent alternative — present
- Correct-versus-incorrect comparison is present — present
- Evidence context is bound to the Power record — present
- Planning metadata is present — present
The method-readiness band and presence checklist assess tutorial presentation and are separate from evidence quality for the underlying Power. They are automated editorial aids, not human approval.
Manual editorial sign-off: Pending. This tutorial must not display a human-approved state until an identified editor signs the exact content hash.