It is now available as a free download by clicking HERE.
Thursday, March 4, 2010
Writing Technical Comics
My article on "Writing Technical Comics" was selected as the lead feature article for this month's issue of the STC magazine, INTERCOM.
It is now available as a free download by clicking HERE.
It is now available as a free download by clicking HERE.
Tuesday, February 23, 2010
Tech Comm Ts
You've seen all those t-shirts with fun slogans for programmers, scientists, chemists and virtually every other profession. So why not have a range of fun t-shirts for Technical Communicators?
We've decided to solve that shortage in the market by setting up an online store called Tech Comm Tech T-Shirts.
To start with each design will only be available for a month.
Kicking things off, and available till the end of February is the "I CAN SPELL XML" shirt.
You can get yours at the online store.
Look for more designs over the coming months.
We've decided to solve that shortage in the market by setting up an online store called Tech Comm Tech T-Shirts.
To start with each design will only be available for a month.
Kicking things off, and available till the end of February is the "I CAN SPELL XML" shirt.
You can get yours at the online store.
Look for more designs over the coming months.
Friday, February 12, 2010
10 Questions You Must Ask Before Implementing a Wiki #10
Ask yourself and your team the following questions before you start to implement a wiki, and be truthful with the answers.
Think about the issue you are trying to solve, and then see how a wiki might be applied, but remember don’t just focus on the positive, think about the potential down sides too.
10. What sort of controls will I need, if any?
It can be argued that the first rule of wikis is that there isn’t any rules. It is true that wikis function best when they are driven by the community that uses them, but you need to think about a few basics of control before you start. Do you need logins, if so who will authorize those. Will you have some sort of initial structure? What about giving users a ‘sandbox’ area to learn the wiki in? Who can see, read and edit what pages? Who will monitor recent changes and do any necessary roll backs? What’s the philosophy for rolling back content, incorporating comments? You will find that these answers change and evolve along with the wiki, but it is good practice to at least set a baseline.
Think about the issue you are trying to solve, and then see how a wiki might be applied, but remember don’t just focus on the positive, think about the potential down sides too.
10. What sort of controls will I need, if any?
It can be argued that the first rule of wikis is that there isn’t any rules. It is true that wikis function best when they are driven by the community that uses them, but you need to think about a few basics of control before you start. Do you need logins, if so who will authorize those. Will you have some sort of initial structure? What about giving users a ‘sandbox’ area to learn the wiki in? Who can see, read and edit what pages? Who will monitor recent changes and do any necessary roll backs? What’s the philosophy for rolling back content, incorporating comments? You will find that these answers change and evolve along with the wiki, but it is good practice to at least set a baseline.
Thursday, February 11, 2010
10 Questions You Must Ask Before Implementing a Wiki #9
Ask yourself and your team the following questions before you start to implement a wiki, and be truthful with the answers.
Think about the issue you are trying to solve, and then see how a wiki might be applied, but remember don’t just focus on the positive, think about the potential down sides too.
9. Which type of wiki should I use?
There are many different types of wiki in the marketplace, don’t just decide to use one type because it’s the only one you’ve heard of, go and do some research. Talk to people who have used wikis for similar implementations that you have in mind, find out what they used, and why. Find out what they rejected and why. Develop a short list of at least three wikis to prototype and test.
Think about the issue you are trying to solve, and then see how a wiki might be applied, but remember don’t just focus on the positive, think about the potential down sides too.
9. Which type of wiki should I use?
There are many different types of wiki in the marketplace, don’t just decide to use one type because it’s the only one you’ve heard of, go and do some research. Talk to people who have used wikis for similar implementations that you have in mind, find out what they used, and why. Find out what they rejected and why. Develop a short list of at least three wikis to prototype and test.
Wednesday, February 10, 2010
10 Questions You Must Ask Before Implementing a Wiki #8
Ask yourself and your team the following questions before you start to implement a wiki, and be truthful with the answers.
Think about the issue you are trying to solve, and then see how a wiki might be applied, but remember don’t just focus on the positive, think about the potential down sides too.
8. Where will the wiki be hosted?
The location and hosting of a wiki can be a contentious issue and it is one that needs addressing early. In large organizations the IT group may want to host it (or they may actively be against the idea), in certain circumstances it may be better hosted at a departmental or project team level (and trends seem to indicate that these sort of bottom-up wiki implementations are usually the most successful ones), or even by a third party wiki hosting company outside the firewall.
Think about the issue you are trying to solve, and then see how a wiki might be applied, but remember don’t just focus on the positive, think about the potential down sides too.
8. Where will the wiki be hosted?
The location and hosting of a wiki can be a contentious issue and it is one that needs addressing early. In large organizations the IT group may want to host it (or they may actively be against the idea), in certain circumstances it may be better hosted at a departmental or project team level (and trends seem to indicate that these sort of bottom-up wiki implementations are usually the most successful ones), or even by a third party wiki hosting company outside the firewall.
Tuesday, February 9, 2010
10 Questions You Must Ask Before Implementing a Wiki #7
Ask yourself and your team the following questions before you start to implement a wiki, and be truthful with the answers.
Think about the issue you are trying to solve, and then see how a wiki might be applied, but remember don’t just focus on the positive, think about the potential down sides too.
7. Who will own the wiki?
Every wiki needs a wiki maven to maintain it, but it also needs someone with a sense of ownership. Be aware of inherent ‘not my idea’ resistance in championing a wiki implementation, and be prepared that even though it may have been your idea, you may have to give up ownership in order to ensure implementation
Think about the issue you are trying to solve, and then see how a wiki might be applied, but remember don’t just focus on the positive, think about the potential down sides too.
7. Who will own the wiki?
Every wiki needs a wiki maven to maintain it, but it also needs someone with a sense of ownership. Be aware of inherent ‘not my idea’ resistance in championing a wiki implementation, and be prepared that even though it may have been your idea, you may have to give up ownership in order to ensure implementation
How a Great Story Can Help Your Brand
Yesterday evening I spent a couple of hours interacting with other local business people and entrepreneurs at this month's Network In Austin event. As usual it was an excellent opportunity to meet and learn about a whole new bunch of local businesses.
In the space of two hours I must have heard about at least a dozen new businesses, what they did, and what they were called. That's a lot of information to take in in a short time.
As I drove home I did a quick mental review to see if I could recall the salient points from each conversation. I managed to recall something about everyone, but what struck me was that the first two businesses that came to mind were the two that had stories attached, and one in particular that had a story attached to the brand name.
The lady who ran the company had told a fun short story of how the company name came from an expression her father used to use a lot.
Several years ago I used to write a regular marketing newsletter that included the stories and histories behind some of the most well known brand names. That section was always the most popular part of the newsletter. It gave me the idea of maybe writing a book on the subject - but then I found out that someone had already done it...
And Evan Morris' fun book "From Altoids to Zima" is now one of the most thumbed books on my marketing bookshelf.
There is a story behind most company and brand names. I've worked for companies named after bags of chips, science fiction villains, a historical event, and even one that got it's name from a typo.
Discover your story - work it in to your pitch, put it on the website, and people will remember it, and they will remember you.
In the space of two hours I must have heard about at least a dozen new businesses, what they did, and what they were called. That's a lot of information to take in in a short time.
As I drove home I did a quick mental review to see if I could recall the salient points from each conversation. I managed to recall something about everyone, but what struck me was that the first two businesses that came to mind were the two that had stories attached, and one in particular that had a story attached to the brand name.
The lady who ran the company had told a fun short story of how the company name came from an expression her father used to use a lot.
Brand names with a story behind them stick.
Several years ago I used to write a regular marketing newsletter that included the stories and histories behind some of the most well known brand names. That section was always the most popular part of the newsletter. It gave me the idea of maybe writing a book on the subject - but then I found out that someone had already done it...
And Evan Morris' fun book "From Altoids to Zima" is now one of the most thumbed books on my marketing bookshelf.
There is a story behind most company and brand names. I've worked for companies named after bags of chips, science fiction villains, a historical event, and even one that got it's name from a typo.
Discover your story - work it in to your pitch, put it on the website, and people will remember it, and they will remember you.
Monday, February 8, 2010
10 Questions You Must Ask Before Implementing a Wiki #6
Ask yourself and your team the following questions before you start to implement a wiki, and be truthful with the answers.
Think about the issue you are trying to solve, and then see how a wiki might be applied, but remember don’t just focus on the positive, think about the potential down sides too.
6. Who will use the wiki in the future?
Of course one of the great things about wikis, and the central theme of this book, is that they foster growth and further collaboration. There are numerous examples of cross pollination of wikis inside organizations as one team sees the benefits that another gain from using a wiki. Before you start even the first wiki, spend some time thinking about areas of potential growth and possible future cross functional collaboration. Make sure you make plans for scalable growth and allow easy access for anyone who may need to contribute, or observe, not just on the initial projects, but on potential future ones as well.
Think about the issue you are trying to solve, and then see how a wiki might be applied, but remember don’t just focus on the positive, think about the potential down sides too.
6. Who will use the wiki in the future?
Of course one of the great things about wikis, and the central theme of this book, is that they foster growth and further collaboration. There are numerous examples of cross pollination of wikis inside organizations as one team sees the benefits that another gain from using a wiki. Before you start even the first wiki, spend some time thinking about areas of potential growth and possible future cross functional collaboration. Make sure you make plans for scalable growth and allow easy access for anyone who may need to contribute, or observe, not just on the initial projects, but on potential future ones as well.
Sunday, February 7, 2010
The Week in Wikis - Week #5
Here's the list of wiki related articles that caught my attention over the last week.
- DoD ‘Wiki’ Increases Technical Collaboration
- Geo-Wiki - Combining wiki with Google Earth
- Wiki technology fuels collaboration, at Ohio State
- The Internet Engineering Task Force has set up a wiki to document which of its standards were successful and why.
- NASA + Wikipedia = OpenLuna - an open source, wiki-based attempt to design a leaner, meaner, public driven moon mission.
As always the full list of all Wiki Week links can be found at http://delicious.com/wikiweek/
- DoD ‘Wiki’ Increases Technical Collaboration
- Geo-Wiki - Combining wiki with Google Earth
- Wiki technology fuels collaboration, at Ohio State
- The Internet Engineering Task Force has set up a wiki to document which of its standards were successful and why.
- NASA + Wikipedia = OpenLuna - an open source, wiki-based attempt to design a leaner, meaner, public driven moon mission.
As always the full list of all Wiki Week links can be found at http://delicious.com/wikiweek/
Friday, February 5, 2010
10 Questions You Must Ask Before Implementing a Wiki #5
Ask yourself and your team the following questions before you start to implement a wiki, and be truthful with the answers.
Think about the issue you are trying to solve, and then see how a wiki might be applied, but remember don’t just focus on the positive, think about the potential down sides too.
5. Who will use the wiki initially?
While you may be implementing a wiki to meet one particular business need, think about every area of the company, or community, that could benefit or contribute to solving that problem. Try to move beyond functional boundaries and think about the skill sets and the knowledge base of all who would benefit. In some cases this may even be people located outside the organization.
Think about the issue you are trying to solve, and then see how a wiki might be applied, but remember don’t just focus on the positive, think about the potential down sides too.
5. Who will use the wiki initially?
While you may be implementing a wiki to meet one particular business need, think about every area of the company, or community, that could benefit or contribute to solving that problem. Try to move beyond functional boundaries and think about the skill sets and the knowledge base of all who would benefit. In some cases this may even be people located outside the organization.
Subscribe to:
Posts (Atom)
