Why start from questions instead of platforms
A destination-first plan ('one TikTok, one carousel, one thread') produces the same point in several shapes. A question-first plan produces different answers for different readers, which is what makes a repurposed asset worth seeing a second time. The destinations still matter, but they are a later choice, made once you know what each version has to do.
A question also gives each row a test you can apply before publishing: does this version, on its own, answer the question for someone who never saw the original? If it does not, the row is not ready, however good the format looks.
The five columns and what each one forces you to decide
The matrix has one row per derivative and five columns. Each column exists to stop a specific mistake.
| Column | What goes in it | The mistake it prevents |
|---|---|---|
| Audience question | The reader's question in their words, and who that reader is | Making a version nobody asked for |
| Evidence | The exact part of the source that answers it: a timestamp, a section, a figure, a quote | Stretching the source beyond what it supports |
| Format | The shape that suits how that reader consumes content: a checklist, a short clip, a single image, a long post | Choosing a format because it is trending rather than because it fits |
| Next action | The one thing the reader should do after: save it, read the full piece, try a setting, reply | Versions that end without a reason to continue |
| Decision | Make, adapt an existing version, or reject, with the reason | Producing every row because it exists on paper |
Illustrative example: one tutorial, six questions, two rejected
This example is illustrative, not a customer case. The source asset is a 12-minute video tutorial from a creator who teaches home baking: how to tell when sourdough has fermented long enough, with a side-by-side of an under- and over-proofed loaf, a short section on kitchen temperature, and a recipe card at the end.
The matrix below is what the creator fills in before deciding where anything goes. Two rows are rejected, and the reason is recorded so the same idea is not reconsidered every week.
| Audience question | Evidence | Format | Next action | Decision |
|---|---|---|---|---|
| Beginner: 'How do I know my dough is ready?' | The poke test, 4:10-5:30 | Short vertical clip of the poke test, captioned so it works without sound | Watch the full tutorial | Make |
| Beginner: 'What went wrong with my flat loaf?' | The side-by-side cut loaves, 7:45 | Single annotated image comparing the two crumbs | Save it for the next bake | Make |
| Experienced baker: 'How much does room temperature change the timing?' | The temperature section, 8:30-10:00, and the creator's own timing notes | Written post or newsletter section with a small timing table | Reply with their kitchen temperature | Make |
| Anyone: 'Can I get the recipe?' | Recipe card, 11:20 | Text post with the recipe and a link to the full video | Read the full recipe | Adapt: the recipe card already exists, only the caption changes |
| 'Is this the best sourdough method?' | None: the tutorial shows one method and makes no comparison | None | None | Reject: the source does not support a 'best method' claim |
| 'Ten bread mistakes' | Only two mistakes are shown in the source | Listicle carousel | Follow the account | Reject: eight of the ten would be invented to fill the format |
Rejected rows are the useful part
The two rejected rows are the ones a volume target would have produced. The 'best method' post would make a claim the source never tested. The 'ten mistakes' carousel exists because the format wants ten slides, not because the creator has ten things to say. Google's guidance on helpful content names this pattern among its warning signs: producing lots of content in the hope that some of it performs, and content that mainly summarizes what others have said without adding much value. That guidance is about search, but the question behind it applies to social posts as well.
Write down the reason for each rejection. Next month, when someone suggests the same derivative, the matrix answers in one line, and if new evidence appears (the creator actually tests three methods), the row can be reopened honestly.
Build your own matrix in seven steps
Use one source asset at a time. A matrix that covers a whole content calendar turns back into a list of destinations.
- Pick one source asset you made yourself and still stand behind: a video, an article, a talk, a long post.
- Write down two or three kinds of reader who could use it, such as a beginner, an experienced practitioner, and someone who only needs one fact.
- For each reader, write the questions they would actually ask, in their words. Comments, replies and support emails are better sources than guesses.
- For each question, find the exact evidence in the source: a timestamp, a paragraph, a figure. If you cannot point to it, mark the row rejected.
- Choose the format that suits how that reader consumes content, then the one next action you want from them.
- Decide make, adapt or reject for every row, and record the reason for rejections.
- Only now choose destinations for the rows you are making, and check each version against the destination's own limits before publishing.
Blank template to copy
Copy this into a spreadsheet or document. Add one row per derivative and keep the rejected rows in the same table.
| Audience question | Evidence | Format | Next action | Decision and reason |
|---|---|---|---|---|
| Who is asking, and what exactly do they ask? | Timestamp, section or figure in the source | Clip, image, checklist, post, thread or newsletter section | Save, read, try, reply or follow | Make / adapt / reject, because... |
Where Ferryman fits
The matrix is an editorial decision, and it stays with you. Ferryman helps once you know what each row is. In Chat Mode you can develop a row's angle into publishable copy, and each sync destination can have its own custom instruction for tone, length or structure. In the composer you start from shared content, review each destination's preview, and edit the version for a single platform before you publish or schedule it.
Ferryman does not decide which questions your readers have or whether the source supports a claim. Those columns are the reason the matrix exists.
FROM GUIDE TO WORKFLOW
Explore this workflow in Ferryman
Draft and adapt with AI, then review
Develop an idea in Chat Mode, give each destination its own instruction, and inspect every platform version before anything is approved.
Publish tailored versions across platforms
Start with shared content, review destination previews, and make per-platform edits before publishing to selected accounts.
Sources & further reading
Written by Ferryman. Sources checked Nov 2, 2026. Platform rules can change; consult the linked documentation for current requirements.