Organize a library of small resources that answer concrete questions and can be reused across channels. The factory turns a question backlog into prioritized pieces with a format, owner, review date, and library location. It is not one LinkedIn lead magnet: it manages a reusable resource system for web, email, sales, support, and social channels.
When to use it
Use it when related questions keep appearing, several people create similar resources, or you need to keep a library current. It is useful for content teams, consultancies, and businesses with repeatable processes.
Do not use it to fill a calendar with pieces nobody requested, duplicate content without a job, or publish on sensitive subjects without appropriate review. A micromagnet should solve a bounded task and state what it does not cover.
Question backlog
Record each question with its source, date, and observed frequency:
| ID | Question | Source | Frequency | Audience | Status |
|---|---|---|---|---|---|
| Q-01 | [exact wording] | [call, support, search] | [n] | [segment] | [new/in progress] |
Clustering and opportunity scorecard
Cluster questions by the job the reader is trying to complete, not only by keywords. Score each group from 1 to 5:
- Observed frequency
- Problem impact
- Fit with the offer
- Reuse across channels
- Production effort, scored in reverse
Add the first four and subtract effort. Record evidence rather than an assumption about demand.
Format choice
- Checklist for verifying steps.
- Template for producing a document.
- Calculator or sheet for a repeated decision.
- Script for a conversation or process.
- Annotated example for teaching judgment.
- Mini guide when several short decisions are needed.
Production workflow
- Capture verbatim questions and remove personal data.
- Cluster them by task and name each group with an outcome.
- Score opportunities and select one priority row.
- Write a brief with audience, promise, exclusions, and format.
- Produce a small first version with one complete example.
- Test it with a representative user and record friction.
- Publish through the right channels from one source version.
- Add it to the library map and link related resources.
- Schedule a review and record changes in the log.
Complete cluster example
Three agency-operations clients ask:
- “What belongs in a weekly report?”
- “How do I separate activity metrics from outcome metrics?”
- “What should I do when a KPI has no data?”
They form the cluster “prepare an actionable weekly report.” The scorecard is frequency 5, impact 4, fit 5, reuse 5, effort 2. Result: 17. The chosen format is a one-page editable template with a completed example and a three-minute guide. It is published on the website, delivered after a sales call, linked in an email sequence, and adapted into a post. A monthly review checks definitions and links.
Production brief
# [Outcome] for [audience]
Source question and evidence:
[wording, source, date, frequency]
Narrow promise:
[task the reader will complete]
Out of scope:
[limits]
Format and channels:
[checklist, template, sheet, guide] / [web, email, sales, social]
Required inputs:
[data, permissions, tools]
Steps:
1. [step]
2. [step]
3. [step]
Example:
[small, complete case]
Owner and review:
[name] / [date]
Library location:
[folder, URL, tags, related links]
Quality checklist and update log
Before publishing, check clarity, accessibility, links, mobile layout, example data, permissions, brand consistency, and unsupported promises. Record every update:
| Date | Change | Reason | Owner | Next review |
|---|---|---|---|---|
| [yyyy-mm-dd] | [what changed] | [evidence] | [name] | [date] |
Library map
Use a stable path: topic > task > format > version. Link each micromagnet to the question it answers, preceding and following resources, and the channels where it appears. This lets you retire one piece without losing its dependencies.
Copyable final artifact
## Prioritized backlog row
ID: [Q-##]
Question: [exact wording]
Cluster: [reader job]
Evidence: [source, frequency, date]
Score: frequency [#] + impact [#] + fit [#] + reuse [#] - effort [#] = [total]
Priority: [high/medium/low]
## Resource brief
Outcome: [completed task]
Audience: [segment]
Promise: [scope and time]
Out of scope: [limits]
Format: [type]
Channels: [list]
Content: [steps, fields, and example]
Owner: [name]
Version and review: [v# / date]
Location and links: [path]
Reuse this system for the next cluster and update the log after each change. Consider a business audit only when production is recurring, involves a team, has meaningful volume or spend, handles sensitive data, or creates a material bottleneck.