Apply suggestions from code review

Co-authored-by: James J Balamuta <[email protected]>

Author: lwasser

how-to/editor-in-chief-guide.md

@@ -20,7 +20,7 @@ Here are some helpful resources to support you in your Editor in Chief role:
 The Editor in Chief (EiC) is a rotating position, typically selected from the
 current editorial team. It may also be held by a member of the broader
 pyOpenSci community who is familiar with our organization and software peer
-review.
+review.  Expected time commitment is about 2 hours per week on average, with some weeks requiring more during high submission periods.
 
 The EiC term lasts **3 to 6 months**, or another duration agreed upon with the
 Peer Review Lead. If the EiC needs to step down early, we request at least
@@ -178,6 +178,12 @@ are done, it's time to assign an editor.
 Use the [editorial dashboard](https://www.pyopensci.org/metrics/peer-review/editorial-dashboard.html)
 to check which editors are currently available.
 
+### Factors to consider when assigning editors:
+
+- **Domain expertise**: Match the package's scientific domain
+- **Career stage**: Balance experienced editors with newer ones when appropriate
+- **Current workload**: Check the editorial dashboard for availability
+
 Once you’ve selected an editor:
 
 1. Assign the issue to them in GitHub
@@ -295,3 +301,12 @@ Before stepping down, write a summary of:
 
 Post your reflection in the `#private-editorial-team` Slack channel or share it with
 the peer review lead directly.
+
+### EiC Transition Checklist
+
+- [ ] Set calendar reminder 3 weeks before term end
+- [ ] Contact peer review lead about successor
+- [ ] Document active reviews and their status  
+- [ ] Hand off any reviews you're personally handling
+- [ ] Write reflection summary
+- [ ] Schedule handoff meeting with incoming EiC