Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Decoding markup symbols and shorthand
Most seniors still mark printed pages with proofreading symbols, arrows, circled numbers and private shorthand such as 'sp', 'conf', 'tie' or 'pls bkup', and a junior who guesses wrong loses an hour and some credibility. Building a one-page key from real markups in your group means the next scrawl reads as instructions rather than a puzzle.
First tasks
- Pull five marked-up drafts from the last month of group work
- List every symbol, arrow and abbreviation you find on them
- Ask an associate to confirm the marks you could not read
- Print the finished key and keep it at your desk
Comment log for every turn
A markup with forty comments spread over twenty pages cannot be held in your head at two in the morning. Numbering every comment into a simple log, with page, request, status and any question, turns a messy markup into a checklist you can work down, hand over or prove complete when a senior asks 'did you get my note on page 14?'.
First tasks
- Set up a log with number, page, request, owner, status and question columns
- Number every comment on your current markup directly on the page
- Enter each numbered comment into the log before editing anything
- Close every row as done, queried or not done with a reason
Style notes for each senior you work for
One VP wants every footnote sourced to the screen, another hates more than two colours on a chart, and the MD only reads the headlines. Keeping a short profile per senior, built from what their markups actually say, lets you pre-empt the comments they always make and turn the ones they do make in the way they expect.
First tasks
- List every senior who has marked up your work in the last two months
- Write five recurring comments for each from their past markups
- Note each senior's preferred format for receiving a turned draft
- Add one new line to a senior profile after each markup @recurring(monthly:20)