{"id":3913,"date":"2019-02-09T12:12:46","date_gmt":"2019-02-09T17:12:46","guid":{"rendered":"https:\/\/wproadmaps.com\/?p=3913"},"modified":"2019-02-09T12:25:03","modified_gmt":"2019-02-09T17:25:03","slug":"get-content-from-the-client-on-time","status":"publish","type":"post","link":"https:\/\/wproadmaps.com\/get-content-from-the-client-on-time\/","title":{"rendered":"4 Best Practices Successful WordPress Providers Use to Get Content from the Client on Time"},"content":{"rendered":"
All you have to do is pose a question in a WordPress Facebook group<\/a> or other WordPress-focused forum regarding getting content from the client. Chances are you will get a litany of responses that clearly indicate this a large and common problem for both WordPress agencies and independent consultants.<\/p>\n The answer to this problem can be simple but most WordPress practitioners aren\u2019t willing to take the time necessary to employ these 4 best practices.<\/p>\n You need a repeatable process that you can refine over time so that you improve your estimating skills regarding the content needs for a project. For example, I have created the WP Roadmaps Website Content Catalog and Estimating Tool (spreadsheet) that takes your imported site map pages and allows you to quickly determine a rough order of magnitude for the proposal (among other calculations). This will be available along with the Content Collection Roadmap that I am expecting to release in the next week or so.<\/p>\n When you break down the content needs like this, and share it with the client, it has a huge impact on their decision whether to try and craft the content themselves, hire you to do it, or take on a third party solution. Repetitively using the same process means you will become more and more precise in your estimating over time and can use this also as a selling point.<\/p>\n If you haven\u2019t adopted a content-first design approach (and mindset), you are probably doing your client a disservice. But that is another topic for another article.<\/p>\n Regardless of when you are dealing with content-related activities, content should be highlighted in all meetings with the client as well as your project-defining documents (proposal, statement of work, etc.). When you consistently (and gently) remind the client of their role in content activities and the potential impact of delays (make it scary), the client is more likely to complete their activities as agreed.<\/p>\n Here is a list of the many places you have the opportunity to set the proper content-related expectations for the client. The Content Collection Roadmap will include more specific instructions and example language for each of these.<\/p>\n In situations where the client insists on getting their own content together and you have a sense there might be delays, then work in some incentives to get them to comply. Here are some possible ideas:<\/p>\n <\/p>\n Depending on the client, you may come up with some different incentives.<\/p>\n There are a number of online tools that will allow you to create a sitemap, translate that into content collection forms, set it up so your clients log in to upload content, and other website planning tasks.<\/p>\n The objective here is twofold: 1)increase your efficiency and 2)make the process easy (and fun) for the client. The easier and more pain-free you can make the process, the more likely the client will get the work done. For most clients, using an online tool fits that bill. Others may be more comfortable with a paper-based system.<\/p>\n Here are a few examples of online website planning tools. Some have free plans but, of course, you get more features with a paid plan. You should do your own research and determine which might work best for your processes. I personally use Slickplan but I am not affiliated with any of the products listed below.<\/p>\n \n By implementing these best practices, you increase the likelihood of your client complying with the content tasks on the project schedule because you are:<\/p>\n \u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Showing them the magnitude of the content tasks (in numbers).<\/p>\n \u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Reminding them often of their responsibilities and the incentives they will receive if they meet their agreed-upon dates.<\/p>\n \u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Using online tools and other techniques to make the content collection task fun and painless.<\/p>\n Want the entire roadmap for creating, collecting, and organizing content for your WordPress project?<\/strong>\u00a0 <\/span><\/em>Stay tuned because I will be releasing the WordPress Website Content Collection Roadmap<\/strong><\/em> in the next few days!<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" All you have to do is pose a question in a WordPress Facebook group or other WordPress-focused forum regarding getting content from the client. Chances are you will get a litany of responses that clearly indicate this a large and common problem for both WordPress agencies and independent consultants. The answer to this problem can…<\/p>\n","protected":false},"author":2,"featured_media":4466,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kadence_starter_templates_imported_post":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"categories":[29,15,20],"tags":[],"yoast_head":"\n1.\u00a0\u00a0\u00a0 Use a Repeatable Process for Estimating Content Needs<\/h3>\n
2.\u00a0\u00a0\u00a0 Set Client Expectations Regarding Content Early and Consistently<\/h3>\n
\n
3.\u00a0\u00a0\u00a0 Incentivize the Client for Meeting Deadlines<\/h3>\n
\n
4.\u00a0\u00a0\u00a0 Automate Where Possible<\/h3>\n
Slickplan Features<\/a><\/h4>\n
ContentSnare \u201cHow it Works\u201d<\/a><\/h4>\n
FlowMapp Features<\/a><\/h4>\n
DYNO Mapper Features<\/a><\/h4>\n
<\/h3>\n
<\/h3>\n
<\/h3>\n
<\/h3>\n
<\/h3>\n
<\/h3>\n
<\/h3>\n
In Summary<\/h3>\n