Failure is a must
Our ISO-3864-man fails somewhat awkwardly, but he remains completely himself … and … he gets back on his feet.
Too quickly failure is considered negative. Failure planned and considered as a necessary part of further development can be very useful when introducing new methods and processes in technical authoring. The key is the small-scale, sequential approach. In contrast to classical project management with planning, execution, and evaluation, a small-scale approach allows you to deal with failure in a relatively relaxed manner. And even more so, you are more light-hearted and thus more easily open to new approaches. Failure is then what it should be, a learning opportunity and not the end of a project.
Three short examples
Develop a graphic guide
Don’t spend months and many meetings creating the perfect graphic guide, but start with ready-to-use “Technical Illustration Notes” and let them grow into a graphic guide.
Do not evaluate Corel DESIGNER and Lattice3D Studio and then roll out the software, but rather work through the entire process chain at one workstation and then introduce the software.
Introduce editorial system
Do not simply place authers in front of a perfectly installed XML editing system, but rather jointly develop and refine guidelines for using the editing system.
And how does the ISO-3864 man fail in the image to this article? … with the Corel DESIGNER!
The person and body parts according to ISO 3864 can be perfectly and functionally realized in Corel DESIGNER:
- Exact geometries
… with drawing precision of 3 decimal places and extensive modes for object snap
- Functional geometries
… semantic object structure, naming and rotation points
- Functional object properties
… with styles