Build an Input Firewall: Filter Feedback, Advice, Trends, and Noise

Let's stay with that beta-reader note for a moment.

“The opening feels slow” describes the reader's experience. “Start with a fight” describes the book they imagine would solve it. You can take the experience seriously without accepting their solution.

Ask where it slowed down. What were they waiting to understand? Had they found a reason to care about the character? Did they know what could go wrong?

You might discover that the opening has plenty happening, but the reader can't tell why any of it matters. Adding a fight would give them more activity while leaving the actual problem untouched.

Or perhaps the reader simply wants a different kind of novel. That deserves a decision too. If you're writing a patient mystery and they want immediate combat, you need to know that before you rebuild the opening around their preference.

Accepting feedback means allowing it into your judgment. It doesn't hand that judgment to the person who supplied the note.

The same distinction applies to writing advice. Someone else's method may be worth trying. Their success doesn't make every part of that method necessary for your work.

The firewall begins with four classes. These are working labels, not grades for the people giving you information.

A trusted friend can give you an irrelevant note. A stranger can spot a factual error. The label belongs to the input, not to your opinion of the person.

Timing matters here. A craft article might help you prepare for revision and derail you halfway through drafting a scene. A pattern across reader reviews might help with positioning a published book. One angry review probably doesn't need access to the next manuscript while you're trying to write it.

That doesn't mean the information has changed. Its usefulness has.

Be especially careful with advice dressed as market evidence. “Readers don't want this anymore” sounds like a fact. Until there's relevant evidence behind it, it's a claim. A confident newsletter or widely shared post doesn't settle it.

Once you've identified what you received, choose an action.

For the slow-opening note, Accept might produce this instruction:

Check whether the first three chapters give the reader a reason to care about the protagonist's next choice.

Notice how different that is from “Add a fight.” You now have a question you can investigate in the actual manuscript.

If you're halfway through a first draft and the note doesn't reveal something that must be fixed before you can continue, Defer may be the better route:

Review the opening during structural revision after the draft is complete.

That is a real deferral. “Think about this later” usually leaves you thinking about it now.

Test is useful when you can learn something without committing the whole book. Save a copy of the opening and try a version that begins later. Compare what the two openings let the reader understand. Keep the original until you've made the decision.

You might Reject the proposed fight while still accepting the concern about pace. You aren't required to treat every part of a note the same way.

You may be thinking that this sounds like a convenient way to ignore criticism.

It can be. If every uncomfortable note goes into Reject, the firewall is doing exactly the wrong job.

Discomfort tells you that you had a reaction. It doesn't tell you whether the criticism is useful. Before rejecting a note, check whether you're judging its relevance or trying to get rid of the feeling it produced.

Some input needs what the worksheet calls accountable review. That means someone responsible for the issue has to examine it and make a decision. You can't simply discard it because it interferes with today's plan.

Use that route for:

• feedback you've agreed to address with an editor;
• factual corrections or demonstrable continuity errors;
• relevant legal, rights, safety, accessibility, or platform concerns;
• contractual and production requirements;
• repeated problems identified by appropriate readers;
• concerns about representation or harm that require knowledge your current team doesn't have.

A claimed requirement still needs verification. An editor's proposed fix can still be discussed. A concern may need clarification before anyone knows what should change. Accountable review means you do that work with the appropriate person and record the resolution where needed.

Suppose a contracted editor points out that a character knows something in Chapter 4 that they don't learn until Chapter 9. You need to check it. If the inconsistency is there, fix it. If the sequence is intentional, discuss whether the reader has enough information to understand it.

Calling it subjective won't answer the question.

Trust is more useful when you can name what you're trusting someone to do.

You might trust one reader to notice where their attention slips, another to understand the genre's expectations, and an editor to identify structural problems. A subject expert may catch errors none of those people would see. They don't all need the same assignment, and their opinions don't carry the same weight on every question.

Before asking for feedback, make the job clear. “Tell me what you think” leaves a reader to decide what kind of help you need. “Tell me where you stopped believing the protagonist would make this choice” gives them something specific to look for.

When a note arrives, ask whether the source has the knowledge and access needed for that claim. Have they read the whole draft? Are they responding as your intended reader? Is this within the editor's agreed scope? Are they describing your book or the book they'd prefer to write?

You don't have to dismiss people whose preferences differ from yours. You do need to understand those differences before changing the manuscript to satisfy them.

Here are a few more examples. All are hypothetical.

The simplest version of the firewall is one place to put incoming material and one time to review it.

A notebook is fine. So is a document or spreadsheet. Choose something you're already likely to use. You don't need another application to decide whether a note belongs in revision.

When something arrives while you're writing, capture enough to find it again. Unless it needs prompt accountable review, leave the decision for the review window.

A weekly review is a reasonable starting point. Adjust it to the project and any editorial deadlines. During that review:

1. Name the current work. Are you drafting, revising structure, doing line work, preparing files, or making a publishing decision?
2. Classify the input. Feedback, advice, market signal, or noise.
3. Check the source's role and any responsibility to respond. Required review comes before an ordinary routing decision.
4. Choose Accept, Defer, Test, or Reject. Give deferred items a trigger and tests a small, reversible scope.
5. Write the next action and close the review. Don't leave every note open as a question you have to carry into tomorrow.

If it takes more effort to maintain the record than to make the decision, simplify the record. The worksheet is there to reduce confusion, not create a second writing project.

And on a low-capacity week, don't insist on processing the entire pile. Handle what requires attention, preserve what mustn't be lost, and let the rest wait. The Degraded-Day Writing Protocol can help you decide how much work belongs in the day.

The tool walks you through one input and produces a note you can copy or print. It asks about the project stage, source, input class, required review, and the action you choose. It doesn't score you or decide whether your book is good.

You don't need to enter manuscript text. Use a short summary, and keep confidential material out of the tool. All processing stays in your browser; entered information isn't saved or transmitted.

The printable worksheet uses the same record:

Download the accessible Input Firewall Worksheet PDF. Use the printer-friendly HTML worksheet.

You don't need a permanent record of every irrelevant opinion. Once you've rejected an item and there's no professional reason to retain it, let it go.

A note on the method

This is a practical framework drawn from the Protect movement of Author as System. It hasn't been validated as a psychological or productivity assessment. It organizes the decision about incoming information; it can't determine truth or replace editorial, legal, accessibility, safety, or subject-matter expertise.

What if two trusted readers want opposite changes?

Look at the experience behind each suggestion. One reader might want you to cut a scene while another wants you to expand it, but both may be struggling to understand why the scene is there. You can accept that problem without adopting either fix.

Should I read reviews of my published books?

Decide what you want to learn from them and when that information can help. Reviews aren't necessarily written as editorial advice to you. A pattern may reveal an expectation worth examining, while an individual reaction may have no useful role in the next draft. There isn't one rule that fits every writer.

Can market information help an unfinished book?

Yes, if it answers a real question about audience, positioning, scope, or publishing. Check the evidence and the cost of acting on it. A claim that requires you to turn the manuscript into a different book deserves more thought than a headline can provide.

What if I disagree with my editor?

Ask what problem the note is trying to solve. Explain your intention, then check whether the text actually communicates it. Discuss a different solution if needed, and honor the review and production obligations you've agreed to. Disagreement can be part of editing; ignoring the note doesn't resolve it.

How do I know the firewall isn't becoming an echo chamber?

Look at what you're rejecting. If you keep only praise, avoid people with relevant expertise, or dismiss the same concern every time it appears, the boundary needs work. A useful firewall still lets difficult evidence reach you.

Choose one piece of input you've been carrying around. Name what it is, check who supplied it and what responsibility you have to address it, then choose a route.

If you're accepting it, write the question it creates. If you're deferring it, name when you'll return. If you're testing it, keep the original and limit the change. If it doesn't belong to this work, stop making room for it.

That is the decision this worksheet helps with. The full Protect system in Author as System goes further into input policy and feedback. And if outside pressure keeps disrupting several parts of your practice, what an author operating system does is a useful place to begin.

For now, decide what you're going to do with the note before you open the manuscript again.

Read more practical ideas for authors.