Whether you are personal blogging or writing TechNet Wiki articles, a common complaint is finding time to write. People usually wait until they have large blocks of time. Unfortunately, you never have hours to set aside. Instead, you need to be strategic in your composing and take an iterative approach.
An iterative approach to writing means you don’t build the finished article all at once. You build upon it over several drafting sessions until you feel it’s complete. It is the same as if you were to develop a software application. You work on it slowly, over time, until the application is done.
How does this fit with the TechNet Wiki community?
You might have heard the phrase “Writing is rewriting” and it’s true for the TechNet Wiki community. Nothing of quality comes out perfect the first time and all items are a work in progress, Working on your items over time improves your writing. With a wiki post, you can publish items you feel have something worthwhile to say but are perhaps not “perfect.” This is where the community comes in.
Once the article is posted to the TechNet Wiki, the community can help improve it. They can expand on your original ideas and work to create an article encompassing of your original topic. The article is in constant iteration within the wiki.
Not that you should create posts full of mistakes. You should work to post something you are proud of. You should still revise your work after setting it aside for 24 hours (time away from your article lets you see it with “fresh eyes”) and by using a tool like Grammarly.
What I am advocating is not holding onto articles until they are 100%. By posting early and adding revisions consistently, the article becomes an iterative work in progress. Perfection comes at the end instead of when you first published.