How to Write a Process Post That Shows Your Decisions

A recipe tells you what to do. A process post tells you why. That difference is the whole point. Anyone can list the steps it took to bind a notebook, carve a spoon or design a poster, but the post that people bookmark and come back to is the one that lets them see inside your head while you worked.

This guide is about writing that second kind of post: one that walks readers through the choices behind a piece, so they can make better choices in their own work. It is not a strict tutorial format, and it does not need to be reproducible step for step. It needs to be honest about how you think.

What a process post is, and what it is not

A process post sits somewhere between a how-to and a diary. It follows a real project from start to finish, but instead of only listing actions, it focuses on the forks in the road: the points where you had two or three options and picked one.

It is not a sales page for the finished piece. It is not a complete course on the craft either. If you try to explain every basic technique along the way, the post becomes a textbook and the story disappears. Assume your reader knows roughly what you know at the start, and link out, or to your own earlier posts, for the fundamentals.

A good test: if a reader finishes your post and could explain why you chose this paper, this stitch or this colour palette, you wrote a process post. If they could only list what you did, you wrote instructions. Instructions are useful too, but they are a different job.

Find the decisions worth explaining

Every project contains hundreds of tiny choices. Only a handful are worth a paragraph. Before you write, go through your notes or photos and look for three kinds of moment:

• Trade-offs: places where you gave something up to gain something else, such as choosing a cheaper material and accepting a rougher finish.
• Reversals: places where you changed your mind halfway through, and what made you do it.
• Constraints: limits that shaped the work, such as a tiny apartment, one free weekend or a single colour of ink.

Pick the four to six strongest moments and build the post around them. Everything else becomes connecting tissue: a sentence or two to carry the reader from one decision to the next.

If you documented the project as you built it, this step is much easier, because the reasons are written down already. Our post on documenting a project while you are still building it explains how to set up that kind of log.

Structure the post around the stages of the work

Readers need a map. The simplest one is the order the work actually happened in. Give each stage its own heading, and inside each stage, lead with the decision rather than the action.

Compare these two openings for the same section:

"Next I cut the boards to length and sanded the edges."

"I almost bought pre-cut boards to save an afternoon. I cut my own because I wanted the grain to run the same way across the whole shelf."

The second version still tells you what happened, but it also tells you what mattered. A reader who does not care about grain direction can skim on. A reader who does has just learned something.

A structure that works for many projects:

1. The brief: what you set out to make, and any limits you were working within.
2. Early exploration: sketches, tests, samples and the ideas you dropped.
3. The main build: two or three stages, each with its key decision.
4. Finishing: the details that turned it from almost done into done.
5. Looking back: what you would keep and what you would change next time.

On WhizArts, longer posts get a table of contents built from your headings, so clear section titles do double duty: they guide the reader and they make the contents list readable.

Show the work in progress, not only the result

A process post lives or dies on its in-between images. The finished piece belongs at the top and maybe at the end. Everywhere else, show the stages: the pencil sketch before the ink, the test swatch, the joint before glue-up, the screen full of rejected layouts.

Place each photo right next to the paragraph it supports. A wall of images at the end forces readers to scroll back and forth to match pictures with words. Posts on WhizArts let you drop images between paragraphs for exactly this reason.

Write a short caption-style sentence before or after each image that tells the reader what to look at. "Notice how the left edge has lifted" is more useful than letting them guess. If you are not sure your photos are clear enough, our guide to photographing your work for a blog post covers light, backgrounds and consistent angles.

Write in your own voice, in your own language

Process posts are personal by nature. You are describing how you think, so let it sound like you. Short sentences are fine. Jokes are fine. Admitting you had no idea what you were doing on day one is more than fine; it is often the most reassuring line in the post.

A few things help readers keep up:

• Define any term a curious beginner might not know, in a few words, the first time you use it.
• Use the same name for the same thing throughout. If it is a "bracket" in paragraph two, do not call it a "support" in paragraph six.
• Give rough numbers where they matter: how long a coat took to dry, how many test prints you made. Your own numbers from your own project are honest and useful.

Many posts on WhizArts are written in Vietnamese, and the platform keeps every diacritic intact, so write in whichever language you actually think in about your craft. Readers can tell when a writer is comfortable.

Close with what someone else can take away

End with a short section that turns your experience into something portable. Not a summary of what you did, but a handful of lessons a reader could apply to a different project. "Test your glaze on a scrap tile first" is portable. "My vase turned out blue" is not.

It also helps to invite a conversation. Ask readers how they would have handled one of your trade-offs, or what they would have done differently. Comments on WhizArts are reviewed before they appear, which tends to keep these discussions on topic. If you are new to the community, the guidelines explain what makes a comment welcome.

Finally, be generous with credit. If a technique came from another maker's post, a book or a class, name it and link to it. Process posts are part of a long chain of people learning from each other, and your post is now one more link in that chain.