{"id":827,"date":"2009-05-12T05:10:18","date_gmt":"2009-05-12T13:10:18","guid":{"rendered":"https:\/\/www.caddmanager.com\/CMB\/?p=827"},"modified":"2009-05-10T19:24:11","modified_gmt":"2009-05-11T03:24:11","slug":"cad-standard-concept-not-a-how-to","status":"publish","type":"post","link":"https:\/\/www.caddmanager.com\/CMB\/2009\/05\/cad-standard-concept-not-a-how-to\/","title":{"rendered":"CAD Standard Concept – Not a “How To”"},"content":{"rendered":"

<\/a><\/p>\n

I have posted a lot of scattered concepts that may impact your CAD Standard.\u00a0 Here are some of them… and a new one.<\/p>\n

The Standard is an Ideal \u2013 you may never reach perfection<\/a><\/p>\n

The Standard is a target to be hit, not a path to follow<\/a><\/p>\n

The Standard is not to be Set in Stone<\/a><\/p>\n

If the Standard is silent \u2013 users can do whatever they want<\/a><\/p>\n

Now a new one…<\/p>\n

The Standard is not a \u201chow to\u201d manual<\/strong><\/p>\n

Do not make the standard into a how to manual or a training manual. <\/span>The reason I say this is that I think those docs need to be separate from the actual Standard. <\/span>Remember my statement above about the Standard being a target to hit, but not a path to get there embodies this concept.\u00a0 Some people like to make one book out of it – I do not. <\/span><\/p>\n

I say to keep them apart is for the following reasons:<\/p>\n

The training will change for each version.<\/em><\/p>\n

There is a chance that the training manual will change as you update the software. <\/span>From release to release there are subtle changes in the commands that are changed by the developers. <\/span>It is out of your control. <\/span>This would require an update of the training manuals.<\/p>\n

Your training docs may not get updated as often as your standard<\/em><\/p>\n

If you are starting to define you standard it will keep evolving and expanding as you move into ever increasing areas of definition. <\/span>As you add pages to your standard, you impact the whole document. <\/span>Your training efforts may skip a release or two, but your standard should not.<\/p>\n

Your \u201chow to\u201d may be documented in several places.<\/em> <\/span><\/p>\n

Some may be written, some may be video and some may be screen caps. <\/span>Having training modules embedded in your standard just clutters things up.<\/p>\n

You may have to share your standard with others.<\/em><\/p>\n

A lot of clients and consultants may ask for a copy of your standard.\u00a0 This is a good thing.\u00a0 Share it.<\/p>\n

But, if you include your training portion with it, then you are giving away your methods.\u00a0 You should avoid doing that.\u00a0 Sharing a standard does not give away trade secrets, or let people know how you do things.\u00a0 Everyone has a standard.\u00a0 Yours is nothing special.\u00a0 But the methods you use to achieve that standard may be unique and you would not want to let everyone know your inside productivity methods.<\/p>\n","protected":false},"excerpt":{"rendered":"

I have posted a lot of scattered concepts that may impact your CAD Standard.\u00a0 Here are some of them… and a new one. The Standard is an Ideal \u2013 you may never reach perfection The Standard is a target to be hit, not a path to follow The Standard is not to be Set in […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[8],"tags":[],"series":[],"class_list":["post-827","post","type-post","status-publish","format-standard","hentry","category-cad-standards"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t