I have to admit, some of the suggestions in the article are terrible and really bad learning practice.
Use premade templates for the course design
Using templates is fair enough, though I don't know how using a template will speed up approval? Be it using your own template or one from the web, if the client doesn't like something then it will take the same amount of time to change it and resubmit for sign off.
Unless the goal here is to tell the client, 'We can't change that, it's the template.'
Quiz only at the end of the course
This doesn't make sense at all. Given a quiz will have to be written to the content, it should be written as the content is being written and therefore there is no gain to have it at the end.
Also, the comment about the 'essential quiz' that is often at the end is baseless. The trend across the industry is away from this approach of having a quiz at the end and having checkpoints throughout. There is no such thing as an 'essential quiz at the end' unless the client is demanding it.
Stick with multiple choice questions
The heading I can agree with as a rule, but the statement 'Ideally your quizzes contain a variety of question types throughout the course' is utterly wrong. If you're asking a learner a question, why make them respond in a different way each time? This is basic UX. If there is no need for a different question type, don't use a different question type as it's just a frustration for the learner. I often find that people use this idea of having all different question types that make the learning 'interesting' to high bad instructional design.
Just for some perspective, imagine you receive a call on your phone. You answer it by touching the 'answer' button. The next time you receive a call you can't touch the 'answer' button, but instead you have to slide it across the screen. The next call, you have to answer a number sequence.
Now, as a used, would you find this 'interesting' or 'frustrating'?
Once the learner has learnt how to interact with the course, you want to leverage this knowledge so they can focus on the content and topic, rather than having them re-learn new activities every 2nd page... or all at the end of the course based on the recommendation above.
Use one program for course creation
This is probably the only point I can agree with. Today's authoring tools are quite powerful and you can create very nice, intuitive and effective solutions all in the tool itself.
I have to admit, I find it really concerning to read these sorts of tips. So here are a few of mine.
Work with the client
Collaboration = efficiency. If you have a really tight deadline for creation a solution, work with the client more rather than have multiple review and sign off points.
I was working on a large scale project that consisted of creating 11 five to ten minute learning bites. At first we used a traditional approach where we provided various deliverables for review, amendment and sign off. This left a lot up to interpretation and there was always amendment feedback, implementation, and sign off.
We decided this wasn't working as it was too slow and changed to a model where the instructional designer worked with the client to create the storyboard for each piece. This meant that review, amendment and sign-off all happened during the writing process. Huge savings in time and effort for both the client and us.
Just because you may have a outlined development process, don't stick to it if it's not needed. Be fluid in your approach to the needs of the solutions you are working on. If a deliverable or step can be eliminated by slightly changing another, do so.
Set expectations well
There is nothing more detrimental to keeping a project on track than misaligned expectations. If the client isn't fully aware of what they are getting and the limits of the scope, review times blow out, feedback is more than scoped, etc.
Too often, expectations are misaligned when the solution provider assumes that the client understands what they are saying. In my experience, often the client sets their expectations on a set of assumptions that are different to those of the solution provider.
Keep it simple
This is something I see so many providers struggle with. Overcomplicating a solution so that it's 'elegant' or 'perfect'. The issue is, that ultimately this leads to the solutions being written for other instructional designers, rather than the audience. If you are able to invest time in something that the learner will most likely not notice, don't do it.