Publish Without the Camera: A Beginner’s Seven Day Content System

Inside this ebook

Free Chapter 1 preview

1. Choose a Lane You Can Actually Teach

Day 1 | Your output: a completed Lane Decision Sheet and nine specific post briefs. ### Why this step matters You make production harder when every post addresses a different person and problem. A clear lane gives you a boundary: who you help, what they struggle with, and what you can demonstrate honestly. Your first decision is not what will attract the largest audience. It is what you can explain accurately enough that someone can use it. You do not need to become the authority on an entire subject. You need a small, defensible teaching territory. Today, you will choose that territory. You will leave presentation formats for Chapter 2. ### 1. List three problems you can help solve Start with problems, not category names. “Productivity,” “cooking,” and “technology” are categories. “Finding the correct document among several similar copies” is a problem. You can show what causes it, demonstrate a change, and describe the limits of that change. Write three candidate problems from your own experience. Look at tasks you repeat, questions you have answered, and processes you have recently learned well enough to explain. Ordinary skills count when the instruction is precise. For each candidate, complete this sentence: “You are stuck when ___, and this lesson would help you ___.” If you cannot name the stuck moment, the candidate is still too broad. Next, identify your basis for teaching it. Use three labels: practised, researched, and not yet verified. Practised means you have performed the process yourself and can reproduce it. Researched means you have found reliable support but may still need to test the instructions. Not yet verified means you have a question, not a claim ready for publication. Do not treat personal experience as proof that a method works everywhere. A process that helps you organize personal documents may be unsuitable for a shared workplace system. Your experience gives you a starting point, not unlimited authority. Example: your three candidates might be organizing personal work files, making a weekly household meal plan, and setting up recurring calendar reminders. Each has a visible task and a practical outcome. None requires you to promise a dramatic life transformation. Choose candidates with a finish line you can describe. “Make your computer less chaotic” is hard to verify. “Give one practice document a name that identifies its project, topic, date, and version” is observable. ### Separate knowledge from confidence For each candidate, add a short knowledge inventory. Use three boxes: what you can demonstrate now, what you need to check, and what you will not teach. This prevents a familiar subject from quietly expanding beyond your competence. In the file organization example, you might be able to demonstrate renaming a duplicate document and moving a sample download into a chosen folder. You might need to check whether renaming affects a particular application's links. You should not imply that a simple naming convention establishes a secure backup system. Your “need to check” box is not a reason to abandon every candidate. It tells you where the work is. A narrow question you can resolve using official documentation is manageable. A lesson that depends on expertise you do not have is a different matter. Prefer a candidate whose central action you can test safely. You should be able to create a sample, perform the action, and inspect the result without risking someone else's information or altering an important working system. Set aside ideas that require confidential access to be convincing. If your only demonstration depends on showing a customer's records, the idea is not ready. Ask whether fictional sample information would teach the same principle. If not, choose another problem. Also separate teaching skill from professional authority. You can explain how you personally label a folder without claiming to provide enterprise records advice. You can demonstrate a planning worksheet without claiming that it solves every underlying cause of disorganization. Your useful test is simple: can you show the action, explain why you chose it, and name a situation where it would not be appropriate? If one of those answers is missing, reduce the scope before continuing. ### 2. Describe a person in a specific situation An audience description should help you decide what belongs in a lesson. Age ranges and broad interests rarely do enough on their own. A situation gives you the trigger, obstacle, and desired next action. Use this structure: “You help someone who is doing [task], gets stuck at [moment], and needs [small outcome].” Keep the description focused on the situation rather than inventing a detailed fictional personality. Example: “You help someone working from home who has downloaded several versions of a document and needs to identify the intended draft before editing.” This is more useful than “You help busy professionals become productive.” The specific description tells you what to include. Your lesson may need to explain dates, version labels, or folder locations. It probably does not need advice about morning routines, focus music, or managing a large team. Add one constraint that changes the instruction. Your audience might be organizing personal files rather than shared files, working mainly on a phone, or using a computer they are not allowed to reconfigure. Choose a constraint you can reasonably support, not a collection of guesses. Avoid turning the description into an unsupported claim about everyone in that group. You are choosing whom your content is designed to help. You are not claiming that all people working from home struggle with document versions. Now test your description against a possible lesson. Ask whether the person could recognize the problem from the opening sentence. Then ask whether the outcome would be useful before they learned anything else from you. If the lesson needs a long explanation of who it is for, narrow the situation. If the audience description excludes almost every lesson you can honestly teach, loosen one constraint. Keep the problem concrete while leaving enough room for related instruction. ### 3. Collect actual questions without collecting people Look for wording that reveals where someone gets stuck. Useful places include public help discussions, comments on relevant instructional posts, and conversations you are permitted to use for this purpose. You do not need a large research project to make an initial lane decision. Give yourself a small search boundary. For example, inspect two relevant public discussions for ten minutes. Record up to five questions that connect directly to your candidate problem. These numbers are a practical limit for the exercise, not a research standard. Capture the problem in your own neutral words. Instead of copying a username and a personal story, write: “Needs to distinguish the approved draft from an older download.” Keep enough context to understand the question, but leave out identifying details. Use four columns in your notes: question, situation, location of source, and implication for a lesson. Your source location can be a public page address or a private note that a permitted conversation occurred. Do not paste private material into a public planning document. Permission to read a discussion does not automatically mean permission to republish it. Keep private community conversations private. When an observation is useful, convert it into a general teaching question rather than presenting someone's words as content you own. If you cannot find relevant questions quickly, do not invent them. Mark your proposed questions as assumptions and continue with a provisional lane. You can make useful content from a verified process while remaining honest about how little you know about demand. Treat repetition carefully. Seeing a similar question three times can justify investigating it. It cannot establish how common the problem is across a market, especially when all three questions came from the same discussion. ### Check the source behind the lesson Audience questions tell you what needs explaining. They do not necessarily tell you the correct answer. Keep your question research separate from the evidence you use to teach a solution. Mike Caulfield's SIFT approach to evaluating online information is useful here. Its central lesson for your work is to pause before accepting an unfamiliar claim, investigate where it comes from, compare reliable coverage, and locate the original context. Apply that habit before building an explanation around a confident comment. For a software behavior, start with the software provider's current help documentation and test the action yourself where practical. For a personal organizational preference, explain it as a working choice rather than a universal rule. For a claim outside your competence, either find appropriate support or leave it out. Record the exact claim you intend to make. “This label helps distinguish these sample files” is different from “This is the best naming system for every workplace.” The second claim needs support you are unlikely to establish with a small demonstration. Save a source title, its location, and the date you checked it. These notes make it easier to revisit changing instructions later. A bookmarked page without a note about what it supports is harder to use when you return to the draft. Your research is complete enough for lane selection when you can distinguish supported actions from open questions. You do not need to verify all nine future lessons today. You do need to know that the lane's core promise does not depend on a claim you cannot defend. ### 4. Score your candidates using the Lane Decision Sheet Give each candidate a score from 0 to 2 on three questions. Your maximum total is 6. This is an editorial comparison tool, not a prediction of audience size, sales, or future performance. First, can you name the audience situation precisely? Give 0 if you have only a broad category. Give 1 if you know the audience and general problem but not the stuck moment. Give 2 if you can name a task, obstacle, and practical outcome. Second, can you demonstrate a solution accurately? Give 0 if you would mainly repeat unverified advice. Give 1 if the action seems supportable but needs testing or important checks. Give 2 if you can reproduce the central process and explain its relevant limits. Third, can you list at least nine distinct useful lessons? Give 0 if you have fewer than three clear lessons. Give 1 if you have three to eight. Give 2 if you can identify at least nine without simply rewording the same instruction. Before awarding the final score, make a rough lesson list. Short action phrases are enough for now. You will turn the selected lane's list into stronger briefs in the next step. Example: file organization might score 2 for situation, 2 for demonstration, and 2 for lesson depth, totaling 6. Household meal planning might score 1, 2, and 1, totaling 4. Calendar reminders might score 2, 1, and 1, also totaling 4. These are illustrative judgments about your readiness, not facts about those topics. Choose the strongest supported candidate. If two tie, prefer the one you can demonstrate with fewer assumptions and less sensitive information. If every candidate scores poorly, narrow one rather than forcing a winner. Do not let a high total conceal a weak foundation. A candidate with no accurate demonstration is not ready to become your teaching lane, even if its audience sounds appealing. ### 5. Write one promise and three boundaries Use this template: “You get help with [specific problem] so you can [practical outcome], through [type of demonstration].” Name what the reader gets, not how impressive your content will be. At this stage, “type of demonstration” means the instructional approach: worked examples, before-and-after comparisons, or step-by-step practice. You will choose whether to present it through screenshots, recordings, or slides in Chapter 2. Example: “You get help with confusing work-file versions so you can identify the document you need, through simple file organization demonstrations.” A more conversational version is: “You get simple file organization demonstrations so you can find the document you need without opening five near-identical copies.” The second version uses a recognizable situation to explain the benefit. It is not a measured claim that every reader currently opens exactly five files. Keep that distinction clear when you turn the promise into individual lessons. Next, write three boundaries in your “not covered” box. For this example, exclude cybersecurity, legal retention requirements, and enterprise records management. Those areas involve questions your small lane does not establish expertise to answer. A boundary should change your decisions. If you have excluded cybersecurity, do not turn a naming lesson into a claim that your files are now protected. If you have excluded enterprise records management, do not present a personal folder scheme as a workplace policy. You can still acknowledge dependencies. For instance, a shared team may already have a required naming convention. Your lesson can tell the reader to check that convention without attempting to replace it. Read your promise alongside the boundaries. If the promise appears to include something you have excluded, rewrite it. A useful promise is narrow enough to keep, not merely broad enough to sound attractive. ### Turn three problems into nine teachable briefs Build a grid with three recurring problems as rows and three teaching angles as columns. For this example, your problems are confusing filenames, scattered downloads, and unclear folder homes. Your angles are a quick fix, a common mistake, and a reusable checklist. Each cell needs an action, a demonstration object, and a takeaway. A phrase such as “download tips” is not a brief. You should be able to tell what the reader will learn before deciding how the post will look. Example, confusing filenames, quick fix: rename one duplicate practice document using project, topic, date, and version. Show the original and revised names. Your takeaway is how each part helps identify the file. Example, confusing filenames, common mistake: compare sample names containing “final,” “new,” and “final2.” Show why those labels alone do not reliably communicate a sequence. Your takeaway is to use an agreed convention rather than accumulating vague suffixes. Example, confusing filenames, checklist: inspect one sample name for a recognizable project, specific topic, meaningful date, and consistently applied version. Your takeaway is a short pre-save check, not a compulsory naming rule for every context. Example, scattered downloads, quick fix: move one known practice download into its intended project folder. Show how you confirm the file first. Your takeaway is to assign a home without moving unrelated files in bulk. Example, scattered downloads, common mistake: compare two sample files with similar download names before acting. Show that a familiar-looking name is not enough to establish that two files are interchangeable. Your takeaway is to inspect before replacing or deleting anything. Example, scattered downloads, checklist: use a simple review sequence: identify the file, confirm why you need it, choose its home, and check that you can find it there. Your takeaway is a repeatable review for selected downloads. ### Finish the grid and make the decision Example, unclear folder homes, quick fix: choose one obvious destination for a sample project document. Show how the project name helps you select that folder. Your takeaway is a clear home for this document, not a complete redesign of the computer. Example, unclear folder homes, common mistake: compare sample folders called “Misc,” “Other,” and “New Folder.” Explain why their purpose is difficult to infer. Your takeaway is to name a folder for what belongs inside it. Example, unclear folder homes, checklist: decide where a sample file belongs by asking which project it supports, where related files already live, and whether a shared convention applies. Your takeaway is a placement decision you can explain. Review all nine cells for duplication. If two briefs teach the same action and conclusion, replace one. Different opening lines do not make identical instruction into separate lessons. Then inspect the risk level. Remove briefs that require untested deletion, access to private records, or claims outside your boundaries. Your first grid should make honest teaching easier, not create nine research emergencies. What works best: choose a narrow problem with an observable process you can demonstrate using safe sample information. Watch out for choosing a popular category merely because other people appear to attract attention there. You now have a working lane, not a permanent identity. Keep it stable long enough to produce useful lessons. You can revise it later using evidence rather than changing direction whenever another topic looks exciting. ### Do this now 1. Score three possible lanes and select one: 10 minutes. 2. Write your audience promise and three boundaries: 5 minutes. 3. Fill your nine-idea grid with specific post briefs: 10 minutes.

1. 1.List three problems you have solved, practised, or can verify through reliable sources. Separate what you can demonstrate now from what still needs checking.
2. 2.Describe a person in a specific situation using their task, stuck moment, and practical outcome.
3. 3.Look for relevant questions in places you are permitted to access. Record the problem and source context without unnecessary personal information.
4. 4.Score each candidate from 0 to 2 for audience specificity, accurate demonstration, and at least nine distinct useful lessons. Compare totals out of 6 without treating them as demand predictions.
5. 5.Write your one-sentence audience promise, define three exclusions, and build nine specific briefs from three problems and three teaching angles.