In future, the real world is set to combine with the virtual at BMW Service. BMW Augmented Reality creates this bridge and extends the real world by adding virtual information. BMW Service is planning to use this technology as a means to assist BMW Service staff in their highly demanding technical work.
Ashkan Karbasfrooshan has written an article called “Context is King: How Videos Are Found And Consumed Online“, in which he argues:
Times have changed. In fact, less and less often do consumers even seek out content by actually going to a given site.
To paraphrase Jeff Jarvis, if something is important, it will find me, be it via newsletter, Facebook, Twitter or a shared link in an email…
The context – Facebook, Twitter, email – in which people are introduced to media and consume it is becoming more important than the content itself. Content is no longer king, context is…
This is why you need both lots of content and a diversity of it.
Karbasfrooshan is talking about videos, but will the same be said about user assistance?
Today, we assume users will seek out Help and other forms of technical documentation, but will that change? Will technical communicators need to disseminate their content via an increasing number of channels?
This is an edited version of a transatlantic interview we carried out with Sarah O’Keefe, CEO of our US partner Scriptorium Inc., on DITA. We discussed a range of topics relating to DITA, but these clips focus on the business case for DITA – why and when it makes sense to move to this standard for producing documentation.
If you need assistance in assessing the value of DITA to your business or in implementing DITA, then Cherryleaf (in Europe) and Scriptorium (in the USA) can help you.
Dr Atul Gawande is currently in London, touring the radio stations to promote his book “The Checklist Manifesto“. Dr Gawande is a surgeon in Boston Mass., who has been looking at how to deal with complexity in surgery and elsewhere.
He has discovered that complex systems work, mostly through people using checklists. Furthermore, no matter how expert you were, well-designed checklists could improve outcomes. So, with some assistance from Boeing, he developed a 90 second checklist (download it here) that reduced surgical deaths and complications in eight hospitals around the world by more than 30%.
In the book, he shows how low-cost checklists actually work, why some make matters worse and why others make matters better.
According to The Guardian, Dr Gawande argues that the right kind of checklist liberates rather than stifles professional intuition. A concise sumary of what might go wrong, and what to do if it does, galvanises groups of professionals into tighter teams. Indeed, one of the key factors, included in the checklist, was to introduce everyone in surgical team to each other: it leads to people having the confidence to speak up.
Michael Scriven, at Western Michigan University, author of a paper called The Logic and Methodology of Checklists commented,
Checklists have long been regarded as beneath the level of serious consideration by methodologists and others interested in the logic of the disciplines. But they are more sophisticated than they appear–and are perhaps the key methodology of those disciplines that really treat theory and practice as equals, e.g., surgery, engineering, neural and public economics, program and product evaluation.
For more on checklists, see:
Guidelines for Checklist Development and Assessment by Daniel Stufflebeam
The Ten Commandments, Constitutional Amendments, and Other Evaluation Checklists by Daniel Stufflebeam
Useability Evaluation Report for the Evaluation Checklist Project Web Site by Barbara Bichelmeyer
Here is the edited version of Cherryleaf’s transatlantic Web interview with Alan Porter on wikis and their use for technical documentation:
Scriptorium Inc has uploaded the “Beyond Documentation” Webinar Ellis delivered back in August 2009. In this session he looked at the future of technical writing and likely changes to the ways in which user assistance is delivered.
Are we moving beyond documents?
If so, what does this mean for technical communicators?
You can see more videos on Cherryleaf’s YouTube channel.
In 2008, we first raised the potential of using augmented reality in technical documentation. We used instructions on repairing an engine as an example:
Fast forward to today, and you can now see a video from the Department of Computer Science at Columbia University demonstrating a prototype of such a system:
Yet another sign that quick reference cards are back in fashion:
Plans to be set out in the Families Green Paper will propose better advice and information for couples and address the balance between work and childcare by considering ways to make public services more “family friendly”.
Under the Green Paper, new fathers will be given a manual to help them adjust to the role.
The ‘Dads’ Guide To…’ cards are A6 sized quick reference cards printed on both sides with important messages for dads and male carers about their child’s development and how they can get more involved in their child’s life and learning.
Sadly, one question asked by many new fathers remains still unanswered: where do you take the baby’s batteries out?
Intellect’s SaaS group has published recently a paper called “The business case for Software as a Service“. The paper lays out the technical and cost benefits of SaaS, together with checklists covering selection criteria, legal considerations and comparisons of SaaS applications to traditional in-house systems.
Cherryleaf made some minor contributions to this paper – so minor we didn’t think they merited our listing as contributors to this paper (a mistake in hindsight).
The report states, SaaS applications are generally easy to use and don’t require a great deal of training and online Help. So why is this?
In part, it’s because:
1. SaaS applications are newly developed applications. This means the developers have been able to build upon the recent developments in usability, when they’ve developed the application.
2. SaaS products typically deal with familiar business tasks, such as finance and sales prospecting. Where a SaaS application does try to explain new concepts or tasks (viz. Google Wave), users can still find they struggle to use the application.
3. SaaS applications can be fixed quickly and are usually subject to continuous improvement. Pilot programmes can be much smaller and quicker to conduct. SaaS applications can be measured and tested more easily, using Web Analytics.
Hopefully, the checklists in the paper will serve as good guides and help you navigate the hype that currently surrounds SaaS and avoid any pitfalls.
We’re starting to conduct a series of interviews with Documentation Managers; our goal is to provide case studies of best practice and innovative ideas.
We’ll be publishing edited versions of these interviews on Cherryleaf’s YouTube channel.
- What questions do you think should we ask?
- What would you like to know from Documentation Managers?
Also, if you’d like to be interviewed, then do email us.