GROW Content Process

Develop content in an agile fashion (and handle writer’s block)

  5 minute read  

Periodically, new technical writers (and interviewers) ask if I follow a particular process when creating docs.

I generally follow a process I call GROW:

  1. Gather information
  2. Review knowledge
  3. Order into a narrative
  4. Work the plan

At first glance, it seems a bit simplistic. But, I’ve found it helpful for a range of needs.

Each phase guides you through the project in an agile fashion. If you get stuck, step back and focus on the purpose of the active phase. Use that purpose to identify and guide next steps.

Gather information

To begin, collect as much readily-available information as you can.

Many projects have a variety of nuances and challenges. Cast a wide net to learn as much as you can.

Some good questions include:

  • What’s the intent of the result? What problem is being solved and who is the target audience?

  • What’s the value proposition? Why do we care? What do we gain?

  • What resources are available?

    There are multiple facets here:

    • Who’s involved? Who are the partners, stakeholders, gatekeepers, etc.
    • What’s the deadline/schedule?
    • Are there specifications or other source materials that describe design thinking?
    • How stable/up-to-date are the source materials?

  • Who are the subject matter experts, reviewers, or other partners that need to be part of the process?

  • How well do you know what you’re working with? What do you need to create the solution?

  • Are existing examples (or assumptions) accurate? Relevant? Are they functional or illustrative? Can we do better?

Ultimately, you’re trying to figure out:

  • What needs to be done?
  • What have you got to work with?
  • When is it needed?
  • Why is it necessary?
  • What does done look like?

Move on to the next step when you’ve learned what you can in a reasonable time frame or when you feel like you have enough to start.

Review knowledge

Here, review and synthesize what you’re learned. Decide whether you have enough to craft the narrative.

This is a high-level sorting step, one where you try to figure out if you know enough to continue.

Begin by group what you know into large groups relevant to the process. Categories should be general and loosely defined.

Don’t worry about putting things in order or fine details at this point. (That’s the next phase.)

Once you have things into general categories, take a moment to see if you find the general flow of the narrative. Stay high-level and avoid getting bogged down by details.

Ask: Do I have enough to tell the story? Does the story make sense?

  • If no, identity what’s missing and go back to Step 1 to fill those gaps.

  • If yes, proceed to next step.

Order into a narrative

Here, you figure how to tell the story you’ve developed. And, yes, the best presentation may be different than how you originally imagined it.

In this step, develop the outline and a doc plan. Figure out the individual steps (tickets) needed to tell the overall story (epic).

Organize the items in your groups and discard ones that don’t fit the narrative. Choose what to include and how to present it.

If your deliverable has multiple components, prioritize them and lay out a schedule.

At the end of this step, review the outline and ask if if your narrative makes sense.

  • If not, examine the trouble spots gaps and how to address them. Use earlier process steps to focus on each one until you’re satisfied with the plan.

  • When the plan’s good, you’re ready to do the actual work.

Work the plan

Here’s where the plan meets reality. Start with the highest priorities and move through the list until finished.

If your plan is a good one, this step can move very quickly. With practice, the solutions almost write themselves.

If you find things aren’t going well, that’s typically a warning sign. Take time to step back and review. You might need more investigation and time to refine.

When finished, you should have a deliverable solution. It’s a good time for a traditional retrospective.

  • What worked?
  • What could be better?
  • What can you improve?

Handling feedback

If you work with partners or other stakeholders, you’ll want to get their input as early (and frequently) as feasible.

The most opportune times depend on the team and the people involved, but I’ve found it helpful to get feedback on the plan (after step 3) and the solution as it develops.

Complicated projects can benefit from feedback from the Review phase. Be open and flexible.

If you have different levels of review (technical, style, editorial, etc), be sure to communicate progress and provide appropriate lead time. Early review often identifies problems when they’re easier to solve.

Getting past blocks

I’ve found this process helpful in getting past many challenges, including writer’s block. When I’m not sure what to write next, I take a deeper look at my plan and my assumptions. Often, a little more research or validation helps work past the block.

If you’re stuck, try to articulate the sticking point. Step back, walk through the narrative, and look carefully at each step. Doing so often highlights the underlying issue.

The GROW process is fairly intuitive and perhaps even a bit simplistic.

I don’t claim to have invented it and it may be known by a more well-known name.

I have found it very helpful in my work. Your mileage may vary.

Vital statistics

  • 15 October 2024: First post for this website