content or design - chicken or egg

How a Content-First Approach Can Help Control WordPress Scope Creep

First, let’s look at how things typically happen on a WordPress web development project, or ANY web development process for that matter.

  1. You and the client agree on the site design and a target date for project completion.
  2. The client is tasked with gathering the content necessary to complete development.
  3. To save time, you begin developing the site using “dummy” content.
  4. The client does not provide the content in the agreed-upon timeframe.
  5. The project stalls and the completion date is pushed out (which forces you to postpone the next project on your schedule, negatively affecting your cash flow). The client may even miss the second date.
  6. By the time the client provides the content for their site, you are busy with another project and they become angry that you cannot finish it in the original agreed-upon time-frame.

On the other hand, if you insist on a content-first development strategy, you stand to reap the following benefits:

  • Very often new requirements are uncovered when content is being created and organized. If you have NOT started development yet, the impact of such changes is minimal because there is no development rework needed.
  • If your client is too busy to be involved with content gathering, they may want to contract you or your agency to do the content gathering for them (an upsell).
  • Development time is typically reduced when all the “pieces and parts” are already assembled and there is less chance of “getting it wrong.” This makes you look like a rock star to your client.

If you are using a content-first approach, you should include a description of the process and expectations in the project proposal Management Approach section. For an example of this section, check out our Proposal Template which you can download (if you haven’t already).

In summary, all the other principles are really subsets of Principle # 1 – Define the Job in Detail with a Content-First Approach. The documents and project assets YOU use to define the job in detail for YOUR clients will be a matter of trial and error as well as personal preference. The Complete WordPress Project Management Roadmap, slated for launch later this year, will include everything you might need to define the job in detail as well the content-gathering forms I use in my practice.

Well I better get back at it so I can get some more goodies out to you. Until next time…

PS – You will want to be sure to watch for next week’s blog post as I’m going to give you some insight into how to accomplish Principle #2 – Get the Right Resources Involved (People, Plugins, and Blocks).