-
Notifications
You must be signed in to change notification settings - Fork 228
Leading a Shadowing process
If you have been asked to let someone 'shadow' you during an editorial peer review and you agree to this, these guidelines are here to help you think through that process to offer the best possible learning experience. Please feel empowered to say no when asked if someone can shadow you. We recognize this may not always be convenient or appropriate.
-
Before you begin, take a moment to remember what it was like for you when you first joined. What types of questions did you have and what did you find useful in terms of your own training or development? Think also about the limits of your knowledge. Are you primarily working on translations? New Lessons? How does this match to what the new editor is likely to be doing?
-
The more experienced editor and the shadowee should have a conversation before beginning that outlines the expectations and needs of both sides. Different people may prefer different approaches. For example, some shadowees may like to watch and be cc'd into correspondence. Others may prefer the chance to take the lead, with comments and interjections from their more experienced colleague. There is no one approach, and the conversation will help you decide what will work best for you.
-
Do not assume that your shadowee has seen or knows how to use the ph-submissions repository or the differences between proposal and submission tickets, so it is a good idea to give them a tour and to point them to any resources you think may be helpful for better understanding it. You can see what they've already been asked to learn on the Onboarding Process for New Editors page.
-
Shadowees may not be used to being in the position of power during a peer review process. Guidance on managing that responsibility should be welcome. If they have experienced the dreaded 'reviewer 2' in the past, they may think this is what peer review is or should be. They should be helped to see the benefits of a more collegial approach to peer review.
-
Choosing peer reviewers can be difficult for new editors. A good shadowing experience should include a discussion as well as tips on how to best identify suitable peer reviewers, and how to approach them effectively. To make this easier we have produced two short videos on how one might approach peer reviewers: Finding Peer Reviewers and Approaching Peer Reviewers. Shadowees should be reassured that they will probably not know peer reviewers personally, but need to feel comfortable approaching them.
-
Shadowees may have concerns or questions about tone or style. They may not be sure how often or how much to post. It is a good idea to discuss this with them, pointing to examples of other reviews as necessary. It may help to direct them to one of your past peer reviews that you think went well so they can see how the whole process unfolded.
-
Troubleshooting technical issues can be difficult. Make sure you discuss who the shadowee can turn to for support if they are editing a lesson and run into trouble.
-
After the shadowing experience is over, we recommend that both parties discuss the process and learn from each other how they could strengthen the experience in future. This is also a good time to ask further questions.
- Copyediting
- Copyedit comments
- Typesetting
- Archival Hyperlinks
- Copyright
- DOI
- Gallery image
- Checklist comment
- Handover comment
- Closing comment
- Opening comment Phase 0
- Phase change comment 1 to 2
- Phase change comment 2 to 3
- Phase change comment 3 to 4
- Opening comment Phase 4
- Phase change comment 4 to 5
- Phase change comment 5 to 6
- Phase change comment 6 to 7
- Tracking lesson phase changes
- Organisational Structure
- Trustee Responsibilities
- Trustee and Staff Roles
- Services to Publications
- Funding
Training
- Onboarding-Process-for-New-Editors
- Leading-a-Shadowing-process
- Board-of-Director---Continuing-Development
The Ombudsperson Role
Technical Guidance
- Making Technical Contributions
- Creating Blog Posts
- Service Integrations
- Brand Guidelines
- French Translation Documentation
- Technical Tutorial on Translation Links
- Technical Tutorial on Setting Up a New Language
- Technical Tutorial on Search
- Twitter Bot
- Achieving-Accessibility-Alt-text-Colour-Contrast
- Achieving-Accessibility:-Training-Options
Editorial Guidance
- Achieving Sustainability: Copyediting, Typesetting, Archival Links, Copyright Agreements
- Achieving Sustainability: Lesson Maintenance Workflow
- Achieving Sustainability-Agreed-terminology-PH-em-português
- Training and Support for Editorial Work
- The-Programming-Historian-Digital-Object-Identifier-Policy-(April-2020)
- How to Request a New DOI
- Service-Agreement-Publisher-and-Publications
- ProgHist-services-to-Publications
- Technical Tutorial on Setting Up a New Language
- Editorial Recruitment
Social Guidance
Finances
- Project Costs
- Spending-Requests-and-Reimbursement
- Funding Opportunities
- Invoice Template
- Donations and Fundraising Policies
Human Resources
- Privileges-and-Responsibilities-of-Membership
- Admin-when-team-members-step-down
- Team-Leader-Selection-Process
- Managing-Editor-Handover
- Checklist-for-Sabbaticals
- New Publications Policy
- Parental-Leave-Policy
Project Management
Project Structure
Board of Trustees