Form Follows Function

The importance of putting functionality before structure in software development. (Prague, 23.4.2015)

Two Tests For Software

Be able to define the user value, and the business value for any software feature. (Prague, 8.4.2015)

Put users first

Define your users and their desires so you can solve real world problems. (Prague, 1.4.2015)

Software For People

Start with understanding your users and what they want to achieve. (Prague, 24.4.15).

What makes Williams Technical Different?

We focus on people and processes, making sure goals are understood. (Prague, 2011)

Ideal Project verses Reality

How to provide at least basic user instructions at the end of the project? (Prague, 2013)

Exageration and Ambiguity

Fred talks about avoiding exageration and ambiguity. (Prague, 2011)

Key Skills of a Technical Writer?

Empathy, confidence and honest curiousity matter. (Prague, 2013)

Writing for User Personas

How do describe YouTube to 70 year old Mildred Thistlebottom? (Cologne, 2010)

Testing Requirements

Fred describes how to write requirements and test cases together. (Cologne, 2010)

Choosing Terminology

Use the language of your users. (Cologne, 2010)

Writing Requirements

How to write Waterfall type requirements. Using imperatives and “stong” vs “weak” modals. (Cologne, 2010)

Levels of Details

Who wants to read about what? Users, administrators, and developers have differing interests. (Cologne, 2010)

Documentation Patterns

User documentation. What, where, why, when, and who should use the feature. (Cologne, 2010)

Cats Eat Rats – Active Voice

How to identify passive English, and change it into clear active voice. (Cologne, 2010)

Intro to Technical Documentation

Fred gives the outline of a “typical” user instruction, with Description, Steps, and Outcome. (Prague, 2011)

The A.A.R.T. of Writing User Stories

Agile Conference Prague : The A.A.R.T. of Writing User Stories. (September 2013)