The 1/3/2/1 Introduction Format: The Only Formula You Need for Attention-Grabbing Introductions

Dario RadečićDario Radečić
5 min read

Staring at a blank page for 30 minutes every time you start writing an article?

Technical writing introductions are tricky because you need to hook the reader immediately while being helpful and proving your article is the only one they need. Most writers get stuck trying to balance being engaging with being informative, and often rewrite the same opening paragraph multiple times. The result? You waste precious time that could be spent on the actual content, and you might even end up with a weak opener that doesn't grab attention.

The 1/3/2/1 format solves this problem by giving you a proven structure to follow every time. This seven-sentence framework takes the guesswork out of introductions and ensures you hit all the right notes - from addressing pain points to introducing your solution.

Here's how to use the 1/3/2/1 format to write compelling introductions that hook readers and keep them reading until the end.

Subscribe to Writing for Developers — The leading newsletter helping developers automate content creation with curated prompts that turn ChatGPT & Claude into your own Technical Content Writing Assistant.

What Is 1/3/2/1 Article Introduction Format

I was first introduced to the 1/3/2/1 format in the book The Art and Business of Online Writing by Nicolas Cole. To say it trasnformed the way I write would be an understatement.

However, the book focuses on writing in general, so some advice doesn't fully translate to technical writing. That's why you're here.

The 1/3/2/1 format is a seven-sentence introduction structure that breaks down into four paragraphs. Each number tells you how many sentences to write in each paragraph - one sentence, then three sentences, then two sentences, then one final sentence.

This format gives readers just enough information to know if you're solving their specific problem. You won't overwhelm them with a long introduction and make them scroll away, and you won't leave them confused about what they're getting either.

The beauty of this structure lies in its predictability.

You can express any idea in seven sentences, no matter how complex the topic might be. It works best for technical pieces and how-to guides. Opinion pieces and listicles need a slightly different approach.

It has concrete benefits for the writer, too.

You'll never stare at a blank page wondering how to start because you have a clear roadmap. Write one hook sentence, expand on the problem with three sentences, present your solution in two sentences, then transition to your main content with one final sentence.

And you're done.

Why 1/3/2/1 Works Wonders for Technical Articles and How-to Guides

The 1/3/2/1 structure hits the sweet spot for technical articles.

Anything shorter like 1/3/1 doesn't give you enough space to address the pain point and provide a solution overview. It might work for opinion pieces or listicles where you want to get to the meat immediately, but technical content needs more setup.

Anything longer than 1/3/2/1 makes readers abandon your article before they reach the good stuff. Seven sentences is the maximum most people will read before deciding if your content is worth their time.

This format addresses four elements that technical readers need:

  • It identifies their specific pain point

  • It builds on the pain point so readers know you understand their problem

  • It shows you have a real solution

  • It tells them exactly what they'll learn next so they can decide if it's worth continuing

The structure forces you to be concrete rather than vague. You can't waste sentences on fluff when you only have seven to work with.

1/3/2/1 Format Explained

Here's exactly how to structure each paragraph and sentence in your introduction.

What each paragraph does

The first paragraph contains one bold sentence that addresses the reader's pain point directly. Hit them where it hurts most.

The second paragraph has three sentences that build on the pain point. Make the reader feel like you've been in their shoes, struggling with the exact problem.

The third paragraph has two sentences that introduce your solution and explain why they should care about it. This is where you transition from problem to solution.

The fourth paragraph has one sentence that bridges your introduction to the article body. Tell them what they'll learn next.

What each sentence does

The first sentence is your bold opener - hit the pain point without hesitation.

The second sentence clarifies your bold opener with more context. The third sentence adds credibility by including exact numbers or a real-world example. The fourth sentence rounds out your argument and guides the reader toward your solution.

The fifth sentence introduces and explains your solution clearly. The sixth sentence expands on why your solution works and why you're confident in it.

The seventh sentence tells readers what comes next in the article.

A Real-World Example of the 1/3/2/1 Structure

Here's the best part - this article's introduction uses the 1/3/2/1 structure.

I didn't write it from scratch though. I used my ChatGPT and Claude prompt called The 1/3/2/1 Introduction Prompt to generate the introduction, then made minor tweaks. The whole process took under two minutes.

For reference, here's what Claude Sonnet 4 produced:

I made a couple of small edits (left = before, right = after):

Compare that to my usual routine - spending 30+ minutes crafting introductions, with most of that time wasted on the opening sentence alone - it's a huge time and energy saver.

Next Steps

Your next order of business is to put the 1/3/2/1 structure to work.

Start by practicing the format manually with your current writing projects. Count your sentences and make sure you hit each part: one bold opener, three pain point sentences, two solution sentences, and one transition. This hands-on practice helps you internalize the structure.

Once you're comfortable with the format, use AI to automate the writing process with my The 1/3/2/1 Introduction Prompt.

Talk soon,

Dario Radecic


Subscribe to Writing for Developers — The leading newsletter helping developers automate content creation with curated prompts that turn ChatGPT & Claude into your own Technical Content Writing Assistant.

0
Subscribe to my newsletter

Read articles from Dario Radečić directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Dario Radečić
Dario Radečić