If you’re interested in having me work with you, let’s get in touch.
I normally work on contract, either by the hour or for a fixed price, but I’ll consider other arrangements.
Currently, I’m not looking to become a permanent employee, but if you have an interesting position you think I would fit, that’s something we could discuss.
Most often clients bring me on to fill a role in their project team. My title will typically be business analyst, content developer, technical writer, or something similar. But over the course of the project I’ll work to develop my role in whatever way maximizes the value I add.
I like team work, and I value working collaboratively with creative and committed people. If that sounds like your organization, I’d love to work with you.
Some projects are best done solo. These are typically writing or editing projects that benefit from the focused attention of a single individual. They frequently require a senior skill set: a mastery of the relevant technical skills, plus first-class abilities around information-elicitation and stakeholder management.
The right team often does things better and faster than a single individual. If the job you need me to do is large or complex, consider a team approach. I can probably source the right resources out of my professional network – people I’ve worked with, whose capabilities I know and respect.
For IT projects, it sometimes makes sense to pair a senior and junior BA, or a senior and junior technical writer. The development of a software prototype or small web application may fit a BA–developer duo, where the BA interprets the requirements and leads on user-interface design and testing. Other situations call for different patterns.
Writing and content-development roles
Professional publishers have used a team approach for decades. The classic quartet of lead editor, writer, copy editor, and proofreader is a proven method of assuring quality output.
At need, one person can fill more than one role, but the workflow should distinguish each role clearly. Except for the smallest projects, it’s advisable to have at least two actual bodies.
Content development works the same way, with the addition of a few new roles. For example, every web strategy today should be SEO-savvy; this means an SEO role, and maybe dedicated resource, on the content side.
Dynamic content, interactivity, data visualization – these (and other) Web 2.0–style innovations are changing what content means. I think they will transform the structure of content-development teams, and I hope to contribute to that change.