What I'd Skip: When the Honest Pick Is Not to Buy

Here’s a slightly funny thing to admit on a site with “pick” in its name: some of the most useful posts you can write end with no pick at all. You tried the air fryer everyone keeps raving about, or the planner app your whole group chat swears by, and your honest answer is “I wouldn’t bother.” That answer can save someone money, an afternoon of setup and a trip to the returns counter. It deserves a proper post.

A “what I’d skip” post is trickier to write than a rave, though. It’s easy to slide into a rant, to get clever at somebody’s expense, or to lose your nerve and tack on a limp “but it might work for you!” at the end. So here’s how we’d go about it: when to write one, how to earn the no, and how to leave readers better off than a thumbs-down would.

Decide whether it deserves a post

Plenty of things you dislike don’t need an article. Before you start, run the idea past three questions:

• Are people actually about to buy it? The best candidates are popular, heavily advertised or the default choice in their category. Nobody needs warning off something they were never going to hear about.
• Does your no travel? “Not my taste” helps almost nobody. “It needs a paid account before the main feature works” helps anyone who can read.
• Did you give it a fair go? One evening with the manual still in the box doesn’t count.

Also check whether you’ve really got a skip on your hands. One annoying flaw in an otherwise lovely product belongs in the “what I didn’t like” part of an ordinary review. This format is for when you’ve added everything up and the downsides win.

And think about size. A big brand’s bestseller can take a public no. A one-person shop’s wobbly first batch is a different matter, and a friendly private note may do more good than a post. Skipping the skip is allowed.

Earn the no before you say it

Readers go easy on praise and check a negative verdict closely, especially if they already own the thing or were about to order it. So show your homework early, with a short testing note near the top: how long you used it, how you got it and what it was up against.

A skip needs one extra line, which is what you did to make it work. Did you read the instructions? Install the update? Try other settings? Contact support? That list answers the first reply you’d otherwise get, “you must have been using it wrong”, and readers who already bought it can try those fixes too.

Then say what you can’t know. You probably tested one unit, so yours might be a dud. Say so, and say whether you tried a second.

Check your own position too. A post that says “skip this one, buy that one” looks very different if you earn from a link to “that one”. Put the tie right beside the alternative, in plain words. Our picking rules ask for links that go where their text says, and a skip is a poor place to get sneaky.

Write about the thing, not the people

Rule four of those picking rules says to argue with ideas and never with people. It’s written with comments in mind, but it suits negative reviews just as well. Here’s a made-up line about a made-up blender, written two ways. First the satisfying version:

A cynical cash grab from a company that clearly couldn’t care less about its customers.

Now the useful one:

The jug started leaking at the base after three weeks. Support answered within a few days and sent a new one, which began leaking after two. I stopped there, so I can’t say whether a third would have lasted.

The first version claims to know what’s going on inside a company. The second sticks to what happened on one kitchen counter, gives support the credit it earned and lets the reader decide. It’s also far more damning, which is a nice bonus for being fair.

A few more habits keep the tone friendly:

• Name what it does well. If the soup really was smooth, say so. Your no gets more believable.
• Leave the fans alone. People who love it aren’t fools. They may simply want different things from you, and saying what those are can be the most helpful line in the post.
• Keep claims to your size. “It leaked on me twice” is your report. “It’s dangerous” or “they’re hiding a defect” is an accusation you probably can’t back up.

Say no early, then say who should ignore you

Don’t save the verdict for the last paragraph as a twist. Someone with a basket open wants the answer now, so give it in the first few lines and spend the rest of the post explaining it: “I’d skip this one, mainly because of the leak and the price of replacement parts.”

Then go looking for the exception, because there’s nearly always one. Try finishing this sentence: “I’d skip it, unless…” A loud vacuum might be fine for someone with a big house and no thin walls. A fiddly app could suit a person who enjoys tinkering and has no deadline.

Keep the exception narrow enough that most readers can tell they’re not in it. “Your mileage may vary” only blurs the verdict you worked for. A specific “unless” sharpens it, because everyone outside that small group now knows the no applies to them.

Give readers somewhere to go

A no solves half a problem. The reader still has lumpy soup, or a messy calendar, or whatever sent them looking in the first place. So finish by pointing onward, and choose the option that’s actually true:

• Something else you’ve used. Hold it to the same standard, flaws included.
• Something you haven’t used. Fine, if you label it clearly and say why it looks promising.
• What they already own. A good knife and five spare minutes may beat the gadget entirely.
• Waiting. If you’ve got a real reason to think a fix or a new version is on the way, say it, and mark it as a guess.
• Nothing at all. Sometimes the problem doesn’t need buying your way out of. That’s a pick too, and easily the cheapest one on the site.

Keep the no fair after you publish

A skip can go stale just like a recommendation. Makers fix things, updates land and prices drop. Put the date you tested near the top, come back when you hear something has changed, and show readers what changed instead of quietly editing the old verdict. Turning a no into a yes in public tells readers your opinion follows the evidence.

Expect some disagreement as well. Comments on PepPick are checked by hand before they appear. If someone shows you got a fact wrong, fix it and say so. If they simply had a better time than you did, let that sit under your post, because readers learn from both.

Before you hit publish, one last read-through with four questions:

1. Is every complaint something I saw for myself, or clearly marked as a guess?
2. Did I name at least one thing it does well?
3. Would I be comfortable if the person who made it read this?
4. Does the reader know what to do next?

Four yeses and you’re ready. Don’t worry about seeming negative, either. Readers can trust your yes because they’ve seen you say no, so every honest skip quietly makes your next pick worth more.