Affichage des articles dont le libellé est Hans van der Meij. Afficher tous les articles
Affichage des articles dont le libellé est Hans van der Meij. Afficher tous les articles

26/05/2015

Minimalist documentation is not a suitcase!

Designing minimalist documentation is increasingly in demand. In particular, due to documentation experts migrating their content to DITA.

 

Not surprising, aliens now decide to board the train of minimalism  ... and miss the step because minimalism is not a suitcase!

What is minimalism?

"Minimalism consist in identifying the smallest amount of instruction that allows for the successful completion of a task "
 

In other words, providing the minimal dose of information for the user to reach his goal.
Not cutting words, using icons or pouring safety and security measures on your website and in all of your content...


What's in this minimalist suitcase? 

  • Re-use                                                                                                                                                                                                                               

    The suitcase owner suggests to "think about the multi-use value of a piece of information. A well-designed graphic, for example, can be useful in multiple topics." 
    Unfortunately, documentation re-use does not belong to the minimalism approach. Saving documentation cost by re-using topics is the main goal of a DITA implementation.

    Minimalism was developed in the late eighties by researchers in cognitive science. It focused on the USER's needs for information on performing a task.
     

    DITA development started in 2001 with IBM developers looking to reduce documentation costs by re-using content. This was a business-oriented authoring perspective, not user-oriented.
    You can design a "minimalist" user guide without considering content re-use!
    • Universally appealing design                                            
    The author stresses: "For documentation: always select a design and style that is universally appealing (or at least inoffensive) and will not cause problems during localization."
    It would be interesting to see an example of a "universally appealing" piece of
    user's documentation. 
    Indeed, our colleague Ron Blicq demonstrates that publishing for the US, UK, Australia, etc
    "means tackling many more differences than just changing the spelling and general terminology... Readers who encounter expressions that can be misinterpreted or simply not understood may downplay the importance of the information or comment disparagingly on the writer’s capability as a communicator."
    If writing for an English-speaking (mother tongue) audience spread over several continents is challenging, how do you provide universally appealing documentation for multi-lingual audiences?
    BTW, minimalism never considered localisation... although we could include it in  "helping the user to perform a task  in the user's language. "
    • Layer                                                                                               
    "For documentation: don’t try to dump all information onto the user at once. Layer it with techniques like DHTML, allowing the user to reveal information as needed."
    Why DHTLM? How to prevent "dumping all information onto the user at once" in a paper document (i.e. without DHTML)?
    Users of minimalist documentation don't need DHTML to quickly find the information they need. Thanks to a clear and precise Table Of Contents and a carefully designed Index (based on meaningful titles), they quickly find the small piece of information they are looking for.
    In addition, a minimalist document increases findability (i.e. "revealing information")  because "Minimalism means [creating] small non-linear chunks readable in any order"
    Minimalism authoring does not need TOOLS such as DHTML, it needs the author's BRAIN!
    • Compress to icon                                                               
    "Think of ways that you can compress content to get it out of the way; for example, DHTML or graphics that can compress to a small icon when clicked."
    Using icons to compress content? This brings two questions:
    • Does this help the user reach his objective?
    No, because users hardly understand the meaning of an icon:"Most icons continue to be ambiguous to users due to their association with different meanings across various interfaces. This absence of a standard hurts the adoption of an icon over time, as users cannot rely on it having the same functionality every time it is encountered."
    • Does this reduce the amount of content?
    No, because icons are useless if you have to explain them.You are just adding graphics to text:"Due to the absence of a standard usage for most icons, text labels are necessary to communicate the meaning and reduce ambiguity."
    Therefore, are we using icons to help users find the right information ...or just adding more confusion to the documentation?
    • Critical info
    The author stresses:"For documentation: make sure that your users can find the critical info, such as your company contact info, quickly. Include safety and security measures on your website and in all of your content."
    Are we sure the end-user is going to look for critical info on the website ? Why do we publish paper manuals? 
    Research has demonstrated that putting safety measures "in all of your content" is counterproductive. In "Warning: Superfluous Warnings Are Hazardous" Jakob Nielsen reveals:
    "Most instruction manuals are littered with "important" warnings that caution against obvious stupidities, burying actual dangers amid a mass of irrelevancy .
    An out-of-control legal system has made a joke of the entire warnings concept; products are now less safe because nobody bothers to read warnings anymore"
    BTW, the user NEVER opens the manual to search for a warning message. He just wants an information to perform a specific task safely. He wants clear instructions. He does not want to be frightened.

     

    Dancing the tango with your suitcase (one step forward, two-step backwards)

    In 2013 the author explained why minimalism fails.One reason was: 
     "because [users] don’t understand big conceptual issues, such as the internal
    mechanisms of the product."

    Sorry, but I don't understand how my good-old-car works. This does not prevent me from driving it to a smart conference.

    Mid-2015, when everybody is showing enthusiasm for minimalism, she makes a nice 180 degree turn advocating for minimalism... Dancing the tango with a suitcase?

    Minimalism outside the suitcase

    To pack your suitcase with effective and efficient minimalism guidance, you could start by following two (genuine) "minimalism" gurus:




    John Carroll (receiving an Award at STC annual conference June 2015... time to listen to him!)


    keynote speaker at 
    DITA Europe 2015 conference

     __________________________________________________________

    Essential further reading  

     _____________________________________________________

    Getting trained in minimalism 

    If you want to know more about minimalism, check these workshops and add this book to your suitcase!

     

     

    28/05/2014

    Minimalism authoring: some resources


    The essence of the minimalist approach is to obstruct as little as possible the learner’s selfinitiated efforts to find meaning in the activities of learning.” (John M. Carroll)


    Basics by John M. Carroll and Hans van der Meij


    Applications




    Academic research

    •  The minimalist Approach to Online Instructional Videos, by EH Pflugfelder, published in Volume 60, Number 2, May 2013 l Technical Communication
    • Applying Minimalist Principles, Strategies, and Techniques, by Susan M.J. Lester

    • Goal-orientation, goal setting and goal-driven behavior in (minimalist) user instructions,  by  Dr. Hans van der Meij, IEEE Transactions on Professional Communications, 50 (4) 295-205


    Complementary reading


    Se former aux techniques du minimalisme 

    Le prochain atelier "documentation minimaliste" aura lieu les 29 et 30 septembre 2014 à Liège. Qu'on se le dise ;-)


    19/06/2013

    Minimalisme : action et réaction ...

    Dans son excellente présentation "Designing instructions that work, using the 4 Components Model", Dr. Hans van der Meij  -un des pères du minimalisme- nous rappelle d'emblée, que les instructions doivent être :

    Effective  –  enable the user to successfully complete a task
    Efficient  –  consume as little time and effort as possible
    Satisficing  –  stimulate the user to act and help keep up a positive mood

        





    En prenant l' exemple de la carte électronique, Dr. van der Meij démontre la transformation qu'il opère après avoir appliqué ses principes d'efficacité, efficience et de satisfaction.

    AVANT_____________________________






     APRES_____________________






    L'auteur lui-même nous donne la liste des modifications :

    Main differences
    • Construction of sub-goals
    • Distinction between action and reaction
    • Numbered each action step
    • Removed alternative method
    • Removed conjunctions


    Au-delà de la numérotation des étapes et l'élimination des conjonctions -deux règles
    bien connues maintenant des rédacteurs professionnels-, ce qui retient vraiment
     l'attention ici, c'est la

    "distinction entre l'action et la réaction"




     Mais que vient faire cette loi de la physique dans notre modèle d'instruction ?...







    Ce qu'entend Dr. van der Meij, c'est la différence essentielle entre l'action que doit effectuer l'utilisateur et la réaction de l'outil (du produit).

    Grosso modo, lorsque l'on donne une instruction de type :
    •  Pour démarrer, appuyez sur le bouton vert
    on peut indiquer (souvent pour rassurer l'utilisateur)  le résultat de cette action :
          Le logo Coucher-de-soleil-sur-Maubeuge s'affiche.

    Nous sommes d'accord qu'il faut bien distinguer
    • les tâches -c'est-à-dire les actions que doit effectuer l'utilisateur pour atteindre l'objectif qu'il s'est fixé-
              des
    • informations qui n'impliquent aucune action de sa part.                                                                                                                                                                                                                     En général, on fait la distinction entre  :


    - l'action de l'utilisateur: numérotation ---> verbe d'action

    - l'information : absence de numérotation--> verbe descriptif

    -
     Le distingo de Dr. van der Meij est nettement plus expressif, plus précis (et passera certainement mieux dans l'esprit des novices) : toute action d'utilisateur doit amener une réaction du produit (outil).
    Ainsi, pour bien marquer la différence, l'exemple de la carte électronique, non seulement numérote les étapes, mais présente les _réactions_ en italique.

     L'utilisateur va s'habituer à cette variante et immédiatement assimiler le processus.

    Brillant,  n'est-il pas ?

    ... comme tout l'ensemble de l'intervention de Dr. Hans van der Meij lors de la conférence Intelligent Energy 2013 à Utrecht (Pays-Bas).

    25/05/2012

    Le minimalisme... mais ça vient d'où ?



    Est-ce le dernier mouvement hype du XXIe siècle ? La documentation technique minimaliste deviendrait-elle "très tendance" ?...
    Au risque de vous décevoir : et bien non !

    Le minimalisme trouve ses origines dans les travaux de  John M. Carroll (qui n'avait pas l'honneur d'être un authentique "technical writer", lui).
    Le manuel fondateur date de 1990 : "The Nurnberg Funnel - Designing Minimalist Instruction for practical Computer Skills", aux éditions du MIT

    Le second ouvrage de John Carroll s'intitule "Minimalism beyond the Nurnberg Funnel",  toujours chez  MIT Press.

    Effaré de constater que l'on tendait à enseigner les bonnes pratiques de la documentation utilisateur selon les mauvaises pratiques dites "de l'entonnoir de Nuremberg" ("Nurnberg funnel"), En effet, la méthode du bourrage de crâne n'a pas vraiment fait ses preuves (sauf pour l'abrutissement de l'apprenant).
    Pire encore : "Carroll observed that modern users are often already familiar with much of what is described in the typical long manual. What they need is the information to solve the particular task at hand. They should be encouraged to do them with a minimum of systematic instruction."
     On notera que, pour Carroll, le fondement de la rédaction technique est bien de donner à l'utilisateur l'information dont il a besoin pour accomplir une tâche, et ceci avec un minimum d'instructions. 


    Depuis le premier ouvrage de Caroll, un beau bouquet d'articles a été publié. Prenez le temps de jeter un oeil sur :