Sometimes, when it can go wrong, it does. A friend of mine does a sterling job of compiling and editing a print journal (4 issues a year) for specialist community of interest. Let's not even go into the job of pulling in the contributions; I haven't done the analysis but I'm sure that an awful lof the contributors are of the big picture, go with the flow preferences (NP).
There's actual never anything 'mission critical' about when the journal actually goes out, but - let's call her Freda - likes to keep her promises.
So stage one of compiling the content is complete. Step two involves graphics, typesetting, printing, distribution etc. She sends the content off; doesn't hear anything; starts to chase and finds out that her graphics person has been rushed into hospital with a serious medical emergency.
A few days down the line I get an email from her giving me the story. A bit tongue in cheek, (we both know type) I respond to her worries along the lines of:
And deadlines don't really matter (especially not to the Ps; and the Is won't know it's late, and the Fs will sympathise with you); and if the TJs want it any different, tough luck!Yes ok - quite a lot of my Thinking humour here - but it did the trick. The response back was:
Thanks for your observations re the various preferences' reactions to the delayed journal - that actually helped me a lot since I had been rushing around in circles really worrying that everyone would be critical of me not getting it out on time!!Phew - nice to know I got it right this time!