We’ve added three short and simple guides to the Cherryleaf website:
I’m experimenting with using a bullet journal this year, and it’s resulting in some useful ideas for managing and planning technical authoring work.
Setting and achieving targets at the start of the year can be difficult. You may end up needing to spend time on immediate, more pressing tasks, and your list of targets can end up feeling like a statement of the things you have failed to achieve.
One of the ways that people use bullet journals is to keep a track of their performance in a month. This is an example of a habits tracker by Kara Benz:
It works like Key Performance Indicators – you set the measures you want to track, and you record each time you carry out those activities.
By reviewing and reflecting each day or each week, on the things you have done, it helps you spot the items that are being neglected. It also seems to prompt you to do those tasks, like trimming a sail or moving a tiller.
It also encourages continuous growth, rather than proficiency. If you focus only on a target, there is the danger that you stop once you have met your goal. Focusing on achievements is also more positive, from a mental perspective.
You don’t, of course, need a bullet journal to make a tracking journal. You could use any notebook, a Word document, Excel spreadsheet etc.
If you use this method already, do share your experiences below.
We’ve just uploaded some spreadsheets to accompany our online Managing Software Documentation Projects training course.
We will be presenting “Planning user documentation when you are a startup business” at the Technical Communication UK conference in September.
We’ll look at how to plan a user documentation project when you’re working for a startup technology company. Working in this environment gives you the opportunity to work “from a clean sheet,” but it also has its own challenges of working in a dynamic and rapidly changing environment.
We’ll look at the issues around planning user documentation and the additional considerations when you are a startup. Your budget may be limited and the product or service in development may be constantly changing, so how should you work in this situation? What should you be developing, and what is the value of user documentation for a startup?
We will cover:
- What is different about working for a startup
- Lean startup strategies
- The value of user documentation for a startup and why should you provide it
- How to document in this environment
- What you should document
- What you should measure?
- What to do when budgets are limited
- What to do when there is no clear audience
For more information, see Technical Communication UK conference.
We’re currently working on 40 minute webinar on:
- Planning user documentation when you’re a startup business
If you have any questions on this topic, you can email these to us prior to the event. We’ll do our best to make sure we address them in the webinar.
Details on the date for this webinar will be published in the Events section of the Cherryleaf Web site.