Decide what to commission.
After Roshan’s IT video broke out, the comments gave us a subject for the next essay: graduates struggling to find work. The decision came before the calendar slot. The exercise below asks you to do the same for six possible pieces.
The hit that changed the next commission.
After Roshan Kotla’s Indian IT essay broke out, the obvious follow-up was another video about IT. Rishwajeet’s July 2026 account describes resisting that sequel and reading all 443 comments instead.
The comments suggested a wider concern: people had followed the expected route through education and a supposedly safe degree, yet could no longer rely on the job at the end. Roshan had experience in software and hiring that gave him something specific to contribute to that concern.
That changed the next commission. The follow-up addressed graduates struggling to find work. A third essay approached the middle-class career promise. The recurring audience concern remained; the subjects and arguments changed.
| Decision | What the case shows |
|---|---|
| Tempting next topic | A sequel about the same industry as the breakout video. |
| Audience evidence | A reading of 443 comments, interpreted as anxiety about the education-to-job promise. |
| Creator’s contribution | Roshan’s own experience of software, running a business and hiring. |
| Editorial choice | Find another subject where that concern met his experience. |
| Commission | An essay about graduates unable to find work, followed by the middle-class career promise. |
For your own slate, look for the point where a meaningful audience question meets something the creator can explain from experience. Then test whether each proposed piece has a distinct argument. Changing the nouns in the last successful title is not enough.
The three releases show how the direction developed. Their published cumulative view totals were recorded at different ages; they do not isolate why the follow-ups worked or establish a guaranteed formula. Comments are also a self-selected part of the audience. Treat the interpretation as a reasoned editorial choice that subsequent work can challenge.
Read the case and dated release figures. Read Rishwajeet’s original account.
Six leads through one editorial lens.
Original proposed teaching slate. A city-explainer channel helps residents examine what everyday urban observations actually mean. These are research leads, not verified findings or scheduled releases.
| Proposed premise | Distinct audience job | Dependency |
|---|---|---|
| What the red heat-map patch tells you | Interpret a measurement before sharing a dramatic claim. | A suitable dataset, relevant expert and cleared visual example. |
| Where the shade moves | Notice how an observation changes with time. | Location access and a feasible repeatable visual plan. |
| Who keeps a street tree alive | Understand responsibility after an installation. | A practitioner with firsthand work and supporting records. |
| Why this puddle returns | Investigate a recurring local problem without assuming its cause. | Appropriate expertise and actual site evidence. |
| What a bus-stop map leaves out | Understand a transfer or route information problem. | Current transit information and a cleared observation plan. |
| The sign everyone walks past | Examine a wayfinding decision. | Permission and real observation; no invented user behaviour. |
The topics share an editorial lens, but each asks a different question. The slate is not six variations of “cities should be better.” Its usefulness depends on the evidence and production route behind each premise.
Choose what is ready to become a commission.
For each lead, write the proposed argument, strongest counterargument, source route, visual or conversational engine and production dependency. A researcher should be able to say what would make the premise fail. “We will find some interesting facts” is not a sufficient research plan.
The heat-map piece is the first research candidate because it already has a clear measurement distinction and a primary-source starting point. It still needs a suitable actual asset and verified guest. The shade observation may offer a stronger visual encounter, but its feasibility depends on access and timing. Keep it in development until that is resolved.
Do not confuse confidence with importance. A worthwhile question with weak evidence needs more research. An easy topic with little audience value may not deserve a slot. Use scores, if helpful, to expose a discussion; do not let a total replace the underlying judgment.
A four-slot calendar with real dependencies.
| Slot | Work and owner | Release condition |
|---|---|---|
| First | Heat-map explainer · researcher and editor | Dataset and guest fit verified; claim boundaries and visual rights resolved. |
| Second | Shade observation · producer | Access and a workable observation period confirmed; no predetermined result. |
| Third | Tree-maintenance interview · booking owner | Contributor and evidence support the promised conversation. |
| Fourth | Response to a meaningful audience question · editor | Reserve capacity; select from an actual response after release rather than inventing the audience’s question. |
These are relative slots, not dates already booked. Convert them into a schedule only after checking who can do the work and when decisions are needed. Leave space for research failure, late changes and a useful response to the first releases. A blocked prerequisite should change the plan; a date does not make unsupported material publishable.
Let results change a specific next choice.
Record the hypothesis before publication. For the first piece, it might be that a concrete map-reading problem gives unfamiliar viewers a reason to watch an explanation of measurement. Then inspect the actual opening, viewing behaviour and relevant audience responses. A large view count alone does not say which part of that hypothesis held.
Look for explanations that change the next slate: a misunderstood distinction, demand for a practical follow-up, or evidence that the packaging attracted a different audience. A few comments can suggest a question; they do not represent every viewer. Read them alongside the distribution context and the content itself.
In the Roshan example above, the audience reading changed the subject of the next commission. Apply that level of specificity to a slate review: name the piece you would now make differently and the evidence behind the choice.
Use a slate that can carry a decision.
A usable row includes the audience question, proposed argument, evidence and counterargument, production needs, owner, next decision and expected response. Add the publication date when the piece is commissioned. Preserve the earlier decision so the postmortem can compare intention with what shipped.
Review the slate at a rhythm that matches production. Change what new evidence warrants, while giving makers enough stability to finish. The aim is a stronger sequence of work, not a meeting that constantly reopens every idea. Download the completed slate, relative calendar and blank worksheet.
Questions about the method.
How do I choose YouTube video topics?
Start with a specific audience question and the channel’s editorial promise. Compare possible arguments, evidence, visual or conversational potential, overlap with recent work and production feasibility before assigning a date.
How is an editorial calendar different from editorial strategy?
Strategy establishes audience, purpose and the recurring editorial lens. The slate selects particular pieces. The calendar coordinates the owners, dependencies and dates needed to produce them.
Tell us what you want to make.
Tell us about the channel or idea, the team you have and where you need help. We’ll discuss the scope on a 30-minute call.
Book a 30-minute call rishwajeet@machinehouse.media