The story behind the guides

About

What we do, why we do it, and how every guide gets made.

Friends, family, coworkers. Everyone kept asking us the same things. How do I take a screenshot on my Chromebook? How do I check my tire pressure? How do I get rid of ants in the kitchen? We found ourselves explaining the same steps over and over, sending the same texts, drawing the same diagrams on napkins.

So we started writing them down. Clear steps, no filler, no ten paragraphs about our childhood before the actual answer. That's how howtodo was born.

What this site is

Practical over clever. We'd rather give you a good answer in two minutes than a perfect one in twenty. Every guide is written for someone who just wants to get the thing done.

Honest about what we don't know. If something is outside our expertise, we say so. If a guide touches on health or money or wiring, we tell you to check with a professional.

Written for real people. No jargon walls, no assumed knowledge, no "as a prerequisite, ensure you have configured your environment variables." Just plain language.


What this site isn't

A content farm churning out filler for ad revenue
Sponsored posts disguised as honest advice
Written by someone who Googled it five minutes before you did

How every guide gets written

Research We dig into the topic, read what already exists, and figure out what's missing or poorly explained.
Try it When we can, we do it ourselves. We check tires, cook recipes, reset passwords, and unclog drains.
Write it We write like we're explaining to a friend. No jargon, no padding, no "in this article we will discuss."
Edit it We cut everything that doesn't help. If a sentence doesn't earn its place, it goes.
Update it When things change, we go back and fix it. Guides aren't blog posts. They should stay accurate.

Get in touch

We're a small team and we read every message. Whether you spotted an error, have a suggestion, or just want to say thanks.

support@how-to-do.net