Last week, I attended a fantastic tech comm conference – Write the Docs Prague 2018. Hosted for the fifth time in the beautiful city of Prague, WTD allowed me to meet, chat, and share the experience with the fellow tech writers, information architects, and information developers from all over the world. Exciting!
Write the Docs is one of the most prominent technical communication conferences that brings people of the documentation development field together, promotes sharing of ideas, as well as encourages professional development.
I cannot but share the gist of 3 talks that boosted my motivation and inspired me at this year’s conference in Prague. Continue reading
Earlier this summer, I had a chance to attend a lecture called “The power of deep interviews” by Maryna Ptashnyk of Bambuk Design Studio. Targeted at designers doing field interviews with customers, it provided several tips & tricks that made me rethink how I myself as an Information Developer prepare and ask questions during the interviews.
Nowadays, public speaking is a crucial skill, which can help you greatly in communicating your ideas to various audiences, be it your team members, customers, or a group of people interested in educational camp on Information Development. Whether you like public speaking or not, chances are you will need it, and when the time comes, it’s better to be prepared with a good neat presentation and the accompanying story than read text from slides, or, what’s worse, mumble words hoping to end it all fast as can be. If the last words strike a chord with you, then the book Show and Tell: How Everybody Can Make Extraordinary Presentations by Dan Roam may be just for you. Continue reading
As an Asian saying goes, it is better to see something once than to hear about it a thousand times. When somebody describes you some concept you can try to imagine each tiny detail, every piece of the whole, each brick in the wall, but there is always a thing that somehow slips your mind.
When I heard the news about switching to Scrum, I was at a loss. The first question that popped up in my head was “How am I going to write documentation for the feature that is not there yet?” According to Scrum, everything should be finalized at the end of each sprint: working feature and corresponding documentation.