marketing/content
Buffer's search-led tutorial production
A writer explains how search research becomes a reviewed tutorial and distributed content.
AI Work Commons / work in practice
Explore how people turn information into useful work.
Follow a pattern. Inspect an example. Find what
transfers.
Source eligibility permits a process reference, not a claim of effectiveness. Counts describe this sample, not popularity.
Choose a family to focus. Cases can belong to several.
Select a pattern to see families assigned to the same cases. These are shared-pattern connections, not prerequisites or proven sequences.
Uncertain needs or situation → questions, responses, and a progressively clarified account
Purposeful elicitation from people or stakeholders, with unresolved questions guiding further inquiry
Excludes: Merely retrieving existing documents or running a diagnostic repair
Shared classification with P01 in 1 source account, including IDEO.org field-learning download . Not evidence of order or frequency.
Shared classification with P01 in 1 source account, including UCA develops a shared digital strategy through flexible workshops . Not evidence of order or frequency.
Shared classification with P01 in 1 source account, including Product Talk opportunity-to-assumption discovery . Not evidence of order or frequency.
Shared classification with P01 in 2 source accounts, including Product Talk opportunity-to-assumption discovery . Not evidence of order or frequency.
Shared classification with P01 in 1 source account, including Turn a retrospective into assigned improvements . Not evidence of order or frequency.
Distributed source material → traceable retrieval, synthesis, or a decision-ready evidence packet
Organize existing evidence and preserve its relation to claims or questions
Excludes: Generating unsupported content or making the authoritative decision itself
Shared classification with P02 in 1 source account, including IDEO.org field-learning download . Not evidence of order or frequency.
Shared classification with P02 in 4 source accounts, including Buffer's search-led tutorial production . Not evidence of order or frequency.
Shared classification with P02 in 2 source accounts, including Outcome Harvesting for strategic learning . Not evidence of order or frequency.
Shared classification with P02 in 2 source accounts, including PagerDuty evidence-linked postmortem . Not evidence of order or frequency.
Shared classification with P02 in 3 source accounts, including Atlassian DACI decision record . Not evidence of order or frequency.
Shared classification with P02 in 5 source accounts, including Atlassian DACI decision record . Not evidence of order or frequency.
A brief, source, or existing artifact → a usable draft or adaptation meeting explicit audience, format, or content constraints
Produce or transform a deliverable; quality checks may be automated or human
Excludes: Treating the resulting artifact as approved simply because it was generated
Shared classification with P03 in 1 source account, including UCA develops a shared digital strategy through flexible workshops . Not evidence of order or frequency.
Shared classification with P03 in 4 source accounts, including Buffer's search-led tutorial production . Not evidence of order or frequency.
Shared classification with P03 in 1 source account, including Oxford interprets anonymized staff survey feedback with AI . Not evidence of order or frequency.
Shared classification with P03 in 1 source account, including Investigate a service complaint and communicate findings . Not evidence of order or frequency.
Shared classification with P03 in 2 source accounts, including Basecamp's shaped project pitch . Not evidence of order or frequency.
Shared classification with P03 in 1 source account, including Mailchimp single-variable email experiment . Not evidence of order or frequency.
Shared classification with P03 in 1 source account, including Define a role before assessing applicants . Not evidence of order or frequency.
Incoming item → clarified category, priority, eligibility, or accountable destination
Determine handling path and resolve missing intake context
Excludes: Downstream investigation or final substantive approval
Shared classification with P04 in 1 source account, including GitLab supplier-invoice intake . Not evidence of order or frequency.
Shared classification with P04 in 1 source account, including FinOps cost-anomaly investigation . Not evidence of order or frequency.
Shared classification with P04 in 1 source account, including Teachers College conflict-management plan . Not evidence of order or frequency.
Shared classification with P04 in 5 source accounts, including GitLab's shared-responsibility issue routing . Not evidence of order or frequency.
Claim or record plus reference evidence → checked agreement, discrepancies, and a substantiated correction or certification
Check factual or accounting correspondence against independent reference material
Excludes: Generic stylistic review, forecasting, or diagnosis without a reference comparison
Shared classification with P05 in 2 source accounts, including Outcome Harvesting for strategic learning . Not evidence of order or frequency.
Shared classification with P05 in 1 source account, including Oxford interprets anonymized staff survey feedback with AI . Not evidence of order or frequency.
Shared classification with P05 in 1 source account, including GitLab supplier-invoice intake . Not evidence of order or frequency.
Shared classification with P05 in 1 source account, including Tennessee receipt-to-invoice match . Not evidence of order or frequency.
Unexpected failure, anomaly, or complaint → investigated explanation and a bounded remedy or recovery path
Inspect evidence, distinguish causes or explanations, then prepare or attempt resolution
Excludes: Routine intake routing or speculative future risk
Shared classification with P06 in 2 source accounts, including PagerDuty evidence-linked postmortem . Not evidence of order or frequency.
Shared classification with P06 in 1 source account, including Investigate a service complaint and communicate findings . Not evidence of order or frequency.
Shared classification with P06 in 1 source account, including FinOps cost-anomaly investigation . Not evidence of order or frequency.
Shared classification with P06 in 1 source account, including Tennessee receipt-to-invoice match . Not evidence of order or frequency.
Shared classification with P06 in 1 source account, including Ahrefs page-by-page content audit . Not evidence of order or frequency.
Shared classification with P06 in 4 source accounts, including PagerDuty NTP incident recovery . Not evidence of order or frequency.
Options and contextual criteria → reasoned ranking, recommendation, or recorded authorized choice
Make criteria, tradeoffs, evidence, and decision authority explicit as available
Excludes: Ranking without purpose or treating advice as authority
Shared classification with P07 in 1 source account, including Product Talk opportunity-to-assumption discovery . Not evidence of order or frequency.
Shared classification with P07 in 3 source accounts, including Atlassian DACI decision record . Not evidence of order or frequency.
Shared classification with P07 in 1 source account, including Ahrefs page-by-page content audit . Not evidence of order or frequency.
Shared classification with P07 in 2 source accounts, including Product Talk opportunity-to-assumption discovery . Not evidence of order or frequency.
Shared classification with P07 in 3 source accounts, including Atlassian DACI decision record . Not evidence of order or frequency.
Proposed activity, dependencies, or disclosed risk → identified hazards and specific mitigation plans
Prospective risk analysis, mitigation assignment, and review
Excludes: A current incident investigation alone or a generic approval gate
Shared classification with P08 in 2 source accounts, including Basecamp's shaped project pitch . Not evidence of order or frequency.
Shared classification with P08 in 1 source account, including Teachers College conflict-management plan . Not evidence of order or frequency.
Shared classification with P08 in 2 source accounts, including Atlassian project premortem . Not evidence of order or frequency.
Shared classification with P08 in 1 source account, including Scottish contract-variation control . Not evidence of order or frequency.
Hypotheses or alternatives → deliberate test, observed results, and updated selection or next action
Explicitly gather new evidence through a test or structured learning cycle
Excludes: Ungrounded critique, passive monitoring, or a theory diagram without a test
Shared classification with P09 in 2 source accounts, including Product Talk opportunity-to-assumption discovery . Not evidence of order or frequency.
Shared classification with P09 in 1 source account, including Mailchimp single-variable email experiment . Not evidence of order or frequency.
Shared classification with P09 in 2 source accounts, including Product Talk opportunity-to-assumption discovery . Not evidence of order or frequency.
Shared classification with P09 in 1 source account, including Amazon two-phase protocol rollout . Not evidence of order or frequency.
An objective involving people or teams → accountable next actions, handoffs, tracking, and agreed closure
Maintain ownership, timing, unresolved work, and completion conditions
Excludes: A one-time routing decision without subsequent coordination
Shared classification with P10 in 1 source account, including Turn a retrospective into assigned improvements . Not evidence of order or frequency.
Shared classification with P10 in 5 source accounts, including Atlassian DACI decision record . Not evidence of order or frequency.
Shared classification with P10 in 1 source account, including Define a role before assessing applicants . Not evidence of order or frequency.
Shared classification with P10 in 5 source accounts, including GitLab's shared-responsibility issue routing . Not evidence of order or frequency.
Shared classification with P10 in 4 source accounts, including PagerDuty NTP incident recovery . Not evidence of order or frequency.
Shared classification with P10 in 3 source accounts, including Atlassian DACI decision record . Not evidence of order or frequency.
Shared classification with P10 in 2 source accounts, including Atlassian project premortem . Not evidence of order or frequency.
Shared classification with P10 in 2 source accounts, including GOV.UK service-retirement transition . Not evidence of order or frequency.
Existing operational state → coordinated transition that manages affected parties, dependencies, and verification
Migration, retirement, or distributed changes with explicit continuity or consistency concerns
Excludes: Any ordinary edit, or indefinitely preserving a restricted state without a change rollout
Shared classification with P11 in 1 source account, including Scottish contract-variation control . Not evidence of order or frequency.
Shared classification with P11 in 1 source account, including Amazon two-phase protocol rollout . Not evidence of order or frequency.
Shared classification with P11 in 2 source accounts, including GOV.UK service-retirement transition . Not evidence of order or frequency.
AI-enabled and conventional work. Desk research, not tested implementations.
marketing/content
A writer explains how search research becomes a reviewed tutorial and distributed content.
marketing/content
The audit diagnoses content performance and identifies appropriate improvements rather than treating every low-traffic page alike.
marketing/content
A draft enters an independent editorial gate with a recorded reason for the change.
marketing/content
The procedure sends controlled message variants and determines which should reach the remaining audience.
marketing/content
The team used a reusable prompt to scaffold glossary entries and then invested in human enrichment.
product
A bounded proposal makes a project discussable without prematurely specifying its final design.
product
Product options are compared using explicit estimates rather than enthusiasm alone.
product
Cross-cutting issues receive a tentative owner followed by negotiated ownership rather than repeated silent reassignment.
product
Retirement is planned around continuing user needs and alternate access paths.
product
A team links an intended outcome to observed needs, alternative solutions, and tests of their risky assumptions.
design/research
Researchers and observers separate observations, interpretations, and actions while building shared findings.
design/research
A moderator observes users attempting realistic tasks without revealing the intended path.
design/research
Team members externalize fresh field experiences so individual knowledge becomes shared material.
design/research
Participants group content items to reveal how they organize a domain.
design/research
Stakeholders review an end-to-end user story rather than disconnected feature progress.
leadership/strategy / administration/project coordination
A decision has an explicit coordinator, decision-maker, contributors, and affected audience.
leadership/strategy
Participants anticipate project threats and enabling conditions, then convert selected concerns into commitments.
leadership/strategy
A team articulates how activities are expected to produce a desired change.
leadership/strategy
Evaluators work backwards from observed changes to investigate plausible program contributions.
leadership/strategy
An executive assistant's custom GPT gives proposal authors a first review.
leadership/strategy
Employees query a curated strategy notebook.
finance
Assigned preparers substantiate balances; separate reviewers certify them.
finance
Invoice processing depends on vendor setup, complete evidence and an appropriate purchase-order route.
finance
Bank differences are classified before correction requests and certification.
finance
An accounting adjustment is supported and checked by a second person.
finance
Unexpected spend is investigated using granular usage and ownership data.
engineering/IT
A clock-drift incident escalated after runbook recovery did not resolve it.
engineering/IT
A named owner constructs an evidence-linked account and reviewed follow-up actions.
engineering/IT
Predeployment compatibility tests precede a prepare-then-activate production transition.
engineering/IT
Incoming defects acquire severity and ownership without losing unresolved information requests.
engineering/IT
A ticket captures access scope, approvals and provisioning ownership.
legal/compliance
Requested records are scoped, searched and checked before secure disclosure.
legal/compliance
Risk analysis feeds mitigation decisions back into project planning.
legal/compliance
Legal review starts with a complete contextual packet and ends with an executed copy.
legal/compliance
Disclosed conflicts trigger layered review and a recorded management plan.
legal/compliance
Counsel-scoped preservation overrides routine record disposal until a scoped release.
procurement/operations
Independent technical judgments are reconciled into documented final scores.
procurement/operations
Proposed prices are tested against comparable evidence with contextual adjustments.
procurement/operations
Independent physical counts are reconciled before comparison with the ledger.
procurement/operations
Actual receipt is recorded and matched against both order and invoice.
procurement/operations
Service issues are checked against agreed terms, corrected and escalated if persistent.
procurement/operations
Proposed changes pass impact and authority checks before negotiation and record updates.
sales
Qualify an opportunity, then develop the evidence needed for a customer-specific value proposition.
sales
An account executive maintains an opportunity record linking business rationale, closing risks and agreed next actions.
sales
Sales development transfers a qualified opportunity to an account executive with scheduling and acceptance expectations.
customer service/success
Support checks request type and entitlement before correcting routing and collecting missing diagnostic context.
customer service/success
A designated owner coordinates a cross-team account problem with explicit exit criteria.
customer service/success
On-call support validates an emergency, engages the customer and chooses a recovery path.
customer service/success
A support leader describes linking feedback to cases and combining it with sales observations to prioritize fixes.
customer service/success
A model procedure links investigation evidence, response to affected parties and possible remedies.
people/HR
A hiring team writes goals and assessment criteria before opening the role.
people/HR
A hiring manager prepares a role-specific question-and-answer document before first interviews.
people/HR
Teammates and managers write separate reviews, then discuss them and calibrate promotion recommendations.
people/HR
A shared issue distributes general and role-specific onboarding work and supports compliance follow-up.
people/HR
The voluntary departure workflow separates employment records, communication planning and access deprovisioning.
people/HR
Some candidates complete a practical test or work trial before a final hiring recommendation.
administration/project coordination
A facilitated retrospective elicits team experience and assigns fixes before the next cycle.
administration/project coordination
Teams collaboratively update a roadmap that connects a service vision to measurable iterations.
administration/project coordination
A project team identifies affected systems, risks and recurring stakeholder feedback.
administration/project coordination
Assigned reviewers examine their part of a purchase request and either decide or ask for missing context.
administration/project coordination
A person reviews recent decisions and clarifies where uncertainty, information or approval habits slowed progress.
operations/coordination
An operations employee replaced repeated cabinet checks with arrival notifications and voluntary collection.
operations/booking administration
DHL reports extracting and structuring booking information before validation and shipment-record creation.
operations/food planning
Kitchen teams use daily waste data to understand excess preparation and change purchasing and ingredient use.
finance/billing operations
Pre-Admission Centre staff changed paper-based charging into daily automated checks and manual exception handling.
customer service/billing enquiries
A former claims counter became a phone/email team handling broader billing enquiries in a shared Business Office.
operations/referral intake
Referral staff use generated document summaries as a checked handoff artifact instead of scanning every fax page.
Community learning and collaborative authorship
An organization-development collective describes making a guide through creative workshops, then inviting outsiders to reshape its first internal draft.
Institutional planning and consultation
Jisc describes helping an arts university develop a digital strategy through research, staff workshops and continuing conversations.
Community insight and internal communication
A university community manager describes using Copilot and Gemini for an initial survey synthesis, preserving time for interpretation and stakeholder communication.
Process improvement and internal tool design
A grants officer describes using ChatGPT as a design collaborator for journal automation and document-naming tools.
Editorial planning
A program interview describes a Mexican newsroom’s modular system for connecting outside news signals to its own audience data.
Creative journalism and format experimentation
A JournalismAI participant describes turning a difficult-to-explain reporting concept into a demonstrable narrative-game prototype.
Try fewer search terms or reset the filters. A gap in this sample is not evidence that a workflow does not exist.
Select up to two cases with “Compare”. Selection stays while you explore other functions.
marketing/content
Topic · Search data · Supporting examples → Published tutorial · Channel adaptations · Performance record
Hypothetical: a training team could turn recurring support questions into reviewed learning guides and channel-specific excerpts.
Limit: Search-demand evidence does not establish instructional effectiveness.
marketing/content
Existing pages · Traffic and link data · Competing pages → Page-level improvement decisions
Hypothetical: a knowledge-base owner could distinguish stale, redundant, and essential low-use guidance before revising it.
Limit: Traffic cannot substitute for mandatory access, compliance, or user usefulness.
marketing/content
Draft · Reason for change → Reviewed publication or returned draft
Hypothetical: an operations team could apply this gate to employee-facing process announcements.
Limit: Reviewer independence and notification behavior must be implemented in the destination system.
marketing/content
Audience · Message variants · Selection criterion → Test results · Selected message
Hypothetical: an internal enablement team could test two subject lines with consenting recipients before a larger campaign.
Limit: Tool-selected winners are not necessarily statistically reliable or causally generalizable.
marketing/content
Glossary terms · Prompt → Enriched glossary entries
Hypothetical: a procurement team could scaffold a supplier-terminology guide, then add verified definitions and examples.
Limit: Uniform structure does not establish truth; specialized terminology needs authoritative review.
product
Shaped idea · Problem evidence · Time appetite → Decision-ready pitch
Hypothetical: a museum could propose a new visitor program using an effort ceiling, visitor problem, rough experience, and exclusions.
Limit: Roughness is useful only if critical feasibility risks have already been considered.
product
Project options · Reach, impact, confidence, effort estimates → Ranked options · Explicit tradeoffs
Hypothetical: a communications team could compare campaign proposals by plausible audience benefit, confidence, and effort.
Limit: Different objectives or incomparable impacts can make a single ranking misleading.
product
Issue report · Ownership categories · Relevant expertise → Owned issue or reasoned closure
Hypothetical: a university service desk could route cross-department inquiries without leaving the requester between teams.
Limit: Ownership labels alone cannot resolve contested budgets or responsibility.
product
Retirement decision · User journeys · Successor-service knowledge → Transition communications · Redirect plan · Information-retention arrangements
Hypothetical: a software team could retire an internal reporting tool after mapping replacement workflows and notifying every access channel.
Limit: Legal data duties and mandated-service obligations vary; this is not legal advice.
product
Outcome · Customer interview stories → Opportunity map · Assumption-test evidence · Next decision
Hypothetical: a library could compare approaches to reducing catalogue-search frustration by testing their distinct assumptions.
Limit: Qualitative discovery does not by itself estimate population prevalence or prove business impact.
design/research
Session notes · Recordings · Observer recollections → Grouped evidence · Findings · Proposed actions
Hypothetical: an operations team could synthesize service-desk observations while preserving which statements are facts versus interpretations.
Limit: Discarding isolated observations can hide rare but important failures; the transfer needs explicit minority-evidence handling.
design/research
Research questions · Service or prototype · Task guide → Task observations · Usability issues
Hypothetical: a logistics team could test whether a new dispatch checklist is understandable using fictional orders.
Limit: Artificial tasks and dummy data may miss real contextual problems.
design/research
Field notes · Photos · Quotes · Impressions → Shared record of learning
Hypothetical: an exhibition team could combine separate venue visits into a shared planning record.
Limit: Impressions must remain distinguishable from observations if the output will support consequential decisions.
design/research
Content labels · Participant explanations → Groupings · Candidate category labels
Hypothetical: a support team could learn how customers group help topics before redesigning a help centre.
Limit: A plausible taxonomy is not proof that users can find items within a finished navigation interface.
design/research
User outcomes · Prototype or working solution → Feedback · Alignment or identified gaps
Hypothetical: a visitor-services team could walk partners through an entire arrival-to-exit journey before opening a new venue.
Limit: A compelling story can conceal operational faults unless reviewers inspect realistic evidence.
leadership/strategy / administration/project coordination
Decision question · Evidence · Options and constraints → Decision and rationale · Follow-up tasks
Hypothetical: a festival team could select a venue using a named decider, explicit criteria, and a record of rejected alternatives.
Limit: Assigning roles cannot create authority absent from the organization.
leadership/strategy
Project context · Participant concerns · Past lessons → Prioritized risks · Mitigation actions
Hypothetical: a publishing team could anticipate why an issue might miss its release date and assign early safeguards.
Limit: Voting reflects the group's knowledge, not calibrated risk probability; rare severe risks can be outvoted.
leadership/strategy
Problem context · Intended audience · Long-term goal → Explicit change model
Hypothetical: a training team could map learning activities to observable behavior changes before measuring impact.
Limit: The model is a hypothesis, not evidence that activities caused results.
leadership/strategy
Documents · Reported changes · Informant accounts → Substantiated outcome descriptions · Evidence-based answers
Hypothetical: an ecosystem partnership team could investigate unexpected changes in partner behavior and assess its own plausible contribution.
Limit: This is not experimental causal identification; competing explanations must remain visible.
leadership/strategy
Draft · Internal reference material → Structured critique
Hypothetical: a research institute could help project leads pressure-test grant concepts against published program criteria before committee review.
Limit: An executive's preferences are not objective merit; a reviewer must avoid suppressing legitimate dissent.
leadership/strategy
Strategy sources · Employee question → Source-linked answer
Hypothetical: a conservation organization could let local teams query how an approved regional plan applies to their projects.
Limit: Citations establish inspectability, not correctness; access control and version precedence must be designed.
finance
Ledger balances · Supporting schedules → Approved reconciliation
Hypothetical: Reconcile software-license entitlements with assigned seats and reopen certification after inventory changes.
Limit: Balance definitions and accounting judgments do not transfer automatically.
finance
Supplier invoice · Purchase order · Vendor record → Processable invoice or correction request
Hypothetical: Match a reimbursement request to approved travel before reimbursement review.
Limit: Approval thresholds, authority and payment rules are organization-specific.
finance
Bank statements · Financial records · Department records → Certified reconciliation · Correction requests
Hypothetical: Compare a warehouse ledger with a carrier delivery ledger before correcting either.
Limit: Accounting timing and correction authority need local equivalents.
finance
Entry proposal · Supporting documentation → Initialed journal entry
Hypothetical: Require an independent reviewer for a master-data correction and its supporting documents.
Limit: Accounting correctness requires domain expertise beyond balanced fields.
finance
Cost and usage data · Allocation metadata · Expected spend → Owner alert · Documented resolution
Hypothetical: Investigate support-ticket surges by product and owner before changing staffing.
Limit: Spend, user demand and service value must be interpreted together.
engineering/IT
Clock-drift alerts · Runbooks · Service ownership → Restored services · Postmortem assignment
Hypothetical: Coordinate recovery from a failed payroll batch across upstream owners and downstream consumers.
Limit: Technical restoration is not equivalent to reversing financial transactions.
engineering/IT
Logs · Chat history · Metrics · Call recording → Reviewed postmortem · Action tickets
Hypothetical: Analyze a failed procurement exercise using correspondence and decision records.
Limit: Root-cause certainty may remain limited; legal accountability differs.
engineering/IT
Old/new protocol · Fleet inventory · Representative tests → Compatibility-preserving rollout
Hypothetical: Prepare all reporting consumers for new taxonomy before producers begin using it.
Limit: Legal agreements and physical actions may be irreversible in ways software is not.
engineering/IT
Bug report · Reproduction details · Component ownership → Triaged defect or information request
Hypothetical: Triage supplier defects using evidence completeness and service impact.
Limit: Severity definitions and release consequences are product-specific.
engineering/IT
System/group identifier · Requested role → Provisioning ticket · Approval record
Hypothetical: Route permission to use restricted research datasets through a scoped approval ticket.
Limit: Permission granting remains security-sensitive; no universal approval exemption.
legal/compliance
Access request · Located records → Reviewed disclosure package · Disclosure record
Hypothetical: Prepare an audit evidence pack while excluding unrelated confidential material.
Limit: Legal disclosure rules must be reassessed; this is descriptive research, not current compliance advice.
legal/compliance
Proposed processing · Stakeholder views → Assessment · Mitigations in project plan
Hypothetical: Assess operational risks of a new supplier onboarding process before launch.
Limit: Privacy risk criteria and regulatory escalation do not transfer wholesale.
legal/compliance
Contract draft · Background · Related documents → Reviewed contract · Executed contract record
Hypothetical: Submit a security architecture review with context and retain the approved implementation record.
Limit: Legal review scope and signature authority cannot be replaced by generic approval.
legal/compliance
Disclosure → Approved management plan · COI status record
Hypothetical: Manage a procurement evaluator's potential conflict through a reviewed recusal plan.
Limit: Do not infer that all conflicts are manageable or that screening proves absence.
legal/compliance
Litigation notice · Record locations · Custodian list → Hold register · Preservation plan · Lift notice
Hypothetical: Freeze selected procurement records during an internal audit and release only the relevant freeze.
Limit: Retention obligations and privilege require qualified legal oversight.
procurement/operations
Bid submissions · Published criteria and weights → Justified final technical scores
Hypothetical: Evaluate grant proposals independently before a documented consensus meeting.
Limit: Procurement fairness and communication rules are jurisdiction-specific.
procurement/operations
Proposal · Comparable prices · Terms and market context → Price-reasonableness analysis
Hypothetical: Compare software-benchmark claims only after aligning workloads and measurement conditions.
Limit: Statutory pricing requirements and procurement discretion remain domain-specific.
procurement/operations
Warehouse ledger · Physical stock → Count results · Discrepancy record
Hypothetical: Independently count active software deployments before reconciling an asset register.
Limit: Physical movement controls differ from continuously changing digital state.
procurement/operations
Purchase order · Delivered materials · Invoice → Receipt record · Discrepancy evidence
Hypothetical: Match a contracted training session, attendance evidence and supplier invoice.
Limit: Service acceptance may require qualitative criteria beyond quantities.
procurement/operations
Contract · Performance issue → Corrective action record
Hypothetical: Address recurring internal data-delivery failures with an owner, due date and escalation route.
Limit: Contract remedies and supplier negotiations do not map directly to internal work.
procurement/operations
Change request · Existing contract · Impact analysis → Approved variation · Updated operational records
Hypothetical: Review a changed data definition for downstream impacts before updating reports and owners.
Limit: Negotiation rights and statutory modification tests cannot be generalized.
sales
Prospecting notes · Customer responses → Pre-call plan · Better understood needs and buying process
Hypothetical: A service designer could use sequential interviews to clarify a service request.
Limit: Transfer the inquiry loop, not sales qualification criteria.
sales
Customer discovery · Opportunity stage and value → Living opportunity plan · Dated review actions
Hypothetical: A project sponsor could maintain a funding decision packet with unresolved assumptions.
Limit: Deal thresholds and forecast cadence do not generalize.
sales
Qualification evidence · Meeting details → Accepted handoff · Qualification feedback
Hypothetical: A research team could hand off an implementation request with evidence and acceptance criteria.
Limit: Do not import prospect criteria into operational requests.
customer service/success
Ticket · Account status · Product environment → Routed or redirected ticket · Diagnostic context
Hypothetical: A facilities desk could separate covered repairs from external responsibilities.
Limit: Eligibility errors can deny service; transfer needs local policy and review.
customer service/success
Account problem · Customer impact → Escalation case · Owned actions · Closure record
Hypothetical: An administrator could coordinate a delayed onboarding spanning several departments.
Limit: Urgency and communication rights must be adapted.
customer service/success
Emergency ticket · Operational evidence → Recovery path · Customer updates
Hypothetical: A venue coordinator could apply the communication structure to a last-minute operational failure.
Limit: Software recovery actions and entitlement rules do not transfer.
customer service/success
CSAT comments · Support case metadata · Sales observations → Prioritized improvements · Coaching context
Hypothetical: A university administration team could aggregate service-desk feedback to improve enrollment guidance.
Limit: Self-reported process; no causal evidence that the method produced a particular improvement.
customer service/success
Complaint · Investigation evidence · Party comments → Reasoned response · Remedy where warranted
Hypothetical: A membership organisation could use a similar evidence-and-response structure for complaints.
Limit: Healthcare law, confidentiality and remedy authority cannot be copied into another context.
people/HR
Business need · Team input → Role definition · Assessment criteria
Hypothetical: A procurement team could define vendor success criteria before reviewing bids.
Limit: Hiring fairness and lawful criteria need specialist judgment.
people/HR
Recurring candidate questions · Role and team details · Interview transcripts containing new candidate questions and answers → Pre-interview Q&A document
Hypothetical: A project coordinator could send stakeholders an orientation brief before kickoff.
Limit: No formal approval process or fixed maintenance cadence is established.
people/HR
Role expectations · Self-review · Manager evidence → Discussed review · Promotion recommendation or decision
Hypothetical: A review panel could independently score project proposals before discussing differences.
Limit: Employment consequences and private personnel data require stronger safeguards than ordinary document synthesis.
people/HR
Onboarding template · Role and start date → Completed checklist · Follow-up requests
Hypothetical: A membership service could track new-member setup across departments.
Limit: Automatic closure is not evidence of actual completion.
people/HR
Resignation · Last working date · System access inventory → Employment record · Offboarding checklist
Hypothetical: A project closeout could coordinate archive, ownership transfer and access removal.
Limit: Employment decisions and access revocation require authorized human control.
people/HR
Candidate work sample · Hiring-team feedback → Evaluation packet · Hiring recommendation
Hypothetical: A vendor pilot could evaluate working practices before a broader engagement.
Limit: Employment selection needs fair access, accommodations and lawful review.
administration/project coordination
Recent work experience · Team observations → Assigned improvement list
Hypothetical: A sales team could review a campaign and assign process changes.
Limit: An action list without follow-through is not evidence of improvement.
administration/project coordination
Vision · User research · Performance analysis → Prioritized roadmap
Hypothetical: A nonprofit could map service improvements against observed beneficiary needs.
Limit: Do not treat provisional roadmap dates as delivery guarantees.
administration/project coordination
Project scope · Team knowledge → Dependency map · Risk actions
Hypothetical: An HR team could map dependencies for a relocation program.
Limit: A diagram does not verify that counterpart teams have accepted obligations.
administration/project coordination
Purchase request · Supporting documents → Approval outcome · Information request
Hypothetical: A grant administrator could organize eligibility and budget reviews into separate gates.
Limit: Approval authority, financial limits and segregation of duties remain local.
administration/project coordination
Recent work records · Personal reflection → Decision audit · Future reminders
Hypothetical: A customer-service lead could review delayed exceptions to clarify escalation thresholds.
Limit: Self-reflection cannot by itself grant permission or establish causal improvement.
operations/coordination
Mail-arrival signal · Collector response → Shared arrival notice · Visible collection ownership
Hypothetical: an office equipment team could replace repeated availability checks with arrival notices and visible voluntary claims.
Limit: A claim is not proof of delivery; escalation for unclaimed work remains a design question.
operations/booking administration
Booking correspondence · Customer-specific CW1 rules → Structured booking fields · Created or enriched shipment record
Hypothetical: an events team could extract registration correspondence into a staging record before staff validation.
Limit: Parsing accuracy and permission to write to the destination system must be separately established.
operations/food planning
Daily waste measurements → Waste-source insights · Revised preparation and purchasing choices
Hypothetical: a print room could use discarded-job measurements to revise batch sizes and material purchasing.
Limit: Waste reduction must not compromise service quality or safety; causal attribution requires a comparison.
finance/billing operations
Performed-service records · Billing accounts → Posted charges · Exception list
Hypothetical: an equipment-rental office could reconcile completed hires to invoice drafts and review unmatched records.
Limit: Automation of payment or billing still needs domain-specific authorization and dispute handling.
customer service/billing enquiries
Patient billing enquiries · Shared billing knowledge · Email template → Single-contact responses
Hypothetical: an employee expenses team could consolidate fragmented enquiries and teach generalists a shared response framework.
Limit: One contact point needs actual cross-domain competence; centralizing a queue alone can create bottlenecks.
operations/referral intake
Referral document packet → Reviewed cover sheet · Forwarded referral
Hypothetical: a grant office could summarize an application packet into a staff-checked intake cover sheet.
Limit: Compression can hide consequential omissions; the original packet and qualified review remain necessary.
Community learning and collaborative authorship
Practice experience · Initial chapters → Collaboratively rewritten guide · Continuing community of practice
Hypothetical: an operations team could invite partner organizations to rewrite its onboarding guide together.
Limit: Co-authorship needs trust and genuine influence, not just solicited comments.
Institutional planning and consultation
Staff perspectives · Existing systems · Sector evidence → Digital strategy · Presentation
Hypothetical: a nonprofit network could jointly shape a shared information strategy through local workshops.
Limit: Consultation alone does not prove implementation or genuine power sharing.
Community insight and internal communication
Anonymized survey data · Audience and format requirements → Checked insight summary · Presentation ideas
Hypothetical: an association could interpret anonymous member feedback for its board.
Limit: Anonymization and minority-view preservation require substantive judgment.
Process improvement and internal tool design
Workflow problems · Code · Draft interface behavior → Internal tools · Improved practitioner understanding
Hypothetical: a museum administrator could co-design a collection-request helper while learning its mechanics.
Limit: A plausible design explanation does not establish security or production readiness.
Editorial planning
News feeds · Audience metrics → Editorial recommendations
Hypothetical: a public-library programming team could combine local-interest signals and attendance patterns to consider events.
Limit: Popularity is not a substitute for public-interest judgment.
Creative journalism and format experimentation
Reporting themes · Peer feedback · Creative concept → Narrative-game prototype
Hypothetical: a training team could prototype an interactive scenario when a policy explanation fails to engage colleagues.
Limit: A compelling prototype does not prove safe distribution or audience reach.