Implementation is broken down into two discrete, but deeply inter-related, jobs: editorial work and technical work. These jobs are done by (at least) two people.
The Editorial Worker (EW) is part of the Digital Communications team, and reports to the Coordinator. The EW helps the Coordinator craft material for publication on various digital platforms. The EW can play several roles, including: producer, editor, copy-writer, and proof-reader. There may be multiple EWs on the communications team, with varying levels of responsibility and specialization.
The EW works closely with the Technical Worker (see below) to implement directives from the Coordinator and Strategist. The EW consults with the Technical Worker to provide practical feedback to the Digital Comms group on day-to-day publication needs.
Occasionally, when assigned by the Coordinator, the EW works with others in the organization to help develop material. This could include coaching or assisting program coordinators, activists, field-workers, interns, and volunteers to help develop digital assets for publication.
The EW interacts primarily with words and with people to facilitate the creation of effective messages. This work relies efficient collaboration and communication systems, including:
Fundamentally, the work of the EW is to help get the “stuff” on the “thing.”
This can include:
The Technical Worker (TW) is part of the Information Systems team and reports to the Information Technology Manager. The TW helps maintain and develop digital publication and communications platforms. The TW can play several roles, including: front-end developer, back-end developer, systems administrator, database administrator, and webmaster.
The TW works closely with the Editorial Worker (see above) to implement directives from the IT Manager. The TW consults with the Editorial Worker to provide feedback to the Information Systems group on day-to-day technical needs relating to digital publishing and communications.
Occasionally, when assigned by the IT Manager, the TW works with others in the organization to help develop their digital literacy and communication skills. This could include coaching or assisting program coordinators, activists, field-workers, interns, and volunteers.
The TW works primarily on systems and processes to facilitate efficient collaboration and publishing. The TW maintains and develops:
Fundamentally, the work of the TW is to help keep the publication and communications systems running smoothly safely.
This can include:
Editorial and technical support is highly desirable at Amnesty International. Given limited budgets and ambitious goals demand will always exceed supply. Be careful about how you spend your time and efforts.
The editorial and technical workers have more access to computer systems than most. With this access comes the heightened need for safety. Two-factor authentication is recommended:
a strong secret key = (something you have) + (something you know)
Documentation is crucial! Not everyone can afford to spend hours every day cultivating digital literacy. Documentation helps bridge the gap. Commit a regular portion of your work time to completing documentation.
This documentation was created using the Sphinx tool to provide structure. The code is hosted on Github and you are reading the output on https://readthedocs.org
See Write the Docs for help getting started with documentation.
If you are collaborating with non-technical people on documentation, use a version-controlled system like Draftin.com or Google Documents to collaborate.
Documentation culture is an uphill battle at most organizations. Amnesty International is in the process of a cultural change towards understanding and appreciating the need for documentation.