Which small office skills are worth learning first?

Six pages in this library are about small skills at a desk, and none of them asks for a course. Write it down while they show you is the notebook in the first week. Say the letter, then a word is spelling a surname down a phone line. Spell it out the first time is the abbreviation that sends work back. Try ‘him’ before you write ‘whom’ is the cursor that stops. Is this deck for the room or for the inbox? is the wall of text on slide one. Learn the spreadsheet you already open is the alternative to ‘learn to code’. They are ordered here roughly as a working week meets them, and each names the person it is not for.

Write it down while they show you. Write it down while they show you starts with the people who do the training, who keep saying the same thing with the same weariness: they show a new hire a task, no notes appear, and a week later the same person is back asking to be shown again; the one writing as they watch barely comes back at all. One trainer put the whole split in a sentence, that the note-takers simply do better than the memory-trusters. The page says the mechanism is not about intelligence: a new job pours more procedure into a week than anyone’s memory is built to hold, and every gap has only two exits, re-ask or wing it, where notes give you a third. On whether taking notes makes you look like you cannot keep up, the page says the people training you read it the opposite way; a notebook signals that their explanation is being kept. What to write is the steps, in your own words, while they happen, plus the answer to every question you ask, because a question asked once shows attention and the same question asked three times to the same person wears thin. The page carries one longer arc: a person leaving an entry-level job after sixteen months was stopped by their manager, thirty-five years in the role, who asked to keep the handwritten training notebook, because it held the only current notes on how the department’s work was actually done. Its caveat draws a line between a private notebook and writing up the whole process for the company, which a few people pushed back on, because the write-up tends to travel upward without your name on it; the private notebook, the page says, nobody resents and nobody inherits.

Say the letter, then a word. Say the letter, then a word is for the call that goes ‘B.’ ‘D?’ ‘No, B.’ Eighteen separate conversations say a fixed spelling alphabet cuts the errors of spelling aloud on the phone, and the list they mean is the one used by pilots, the military and radio operators, which the page prints, checked against the alliance that adopted it in 1956: Alfa, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee, Zulu, with Alfa and Juliett spelt that way on purpose. But the page’s own counsel is the format rather than the list: three accounts in one objection say the other person does not need to know any spelling alphabet if you say the letter first and the word after it, so ‘K as in Kilo’ works on someone who has never heard Kilo used that way, while ‘Kilo Foxtrot India’ on its own, one caution with two accounts says, produces confusion. Whether to use the official words or plain ones the listener knows is argued two accounts across two conversations against five across three, with ten more single-conversation exchanges running the same axis, and two separate conversations saying the official list is useless with the general public, who hear Sierra and write C, and the accounts’ decider is who is listening. You do not have to learn all of it: the trouble is concentrated in a few pairs, four accounts in one note on M and N and on G and J, a nine-conversation joke about the letter M, ‘M as in Mancy’, and five accounts in one note who cannot find a word for K under pressure; learn those six words, the page says, and you have most of the benefit. On numbers, two single accounts: read a long number one digit at a time, and say a phone number twice on a voicemail. One caution says dictating anything long, a password, a reference, this way is slow if the person typing is slow, and one account says it fails when the other end does not know the words, and the page hands the question of whether you should be reading a password down a phone at all to its linked page on treating any incoming call as live.

Spell it out the first time. Spell it out the first time says the fix for the reader who hit three capital letters and stopped is a small mechanical habit that costs about eight words: write the full term the first time it appears, put the short form in brackets right after it, and use the short form from then on; if you will only use a term once or twice, do not abbreviate it at all. The page says this is a rule and not a preference, across professional, academic, legal and scientific writing, and two conversations describe work being sent back by a client, a supervisor or a reviewer for nothing more than undefined initials. The reason it is more than manners is the reader you cannot see, and the cases pile up in its conversations: the same letters meaning a hospital department to one reader and something intimate to another; a workplace shorthand a new hire misread for months; codes for a US state that are also codes for an Australian one. Two conversations make the point the page says matters most for a site like it: readers working in a second language find heavy abbreviation genuinely hard to parse even after years of study, and the feeling it produces is not confusion so much as exclusion. The page keeps the joke that runs through its conversations, which is on the writers: across several separate discussions, posts giving exactly this advice opened with an undefined abbreviation of their own, and readers noticed every time. Its lesson is that your own jargon is invisible to you, so the habit has to be mechanical, not ‘would my reader know this?’, which you will always answer yes, but ‘is this the first time these letters appear?’ The one place the rule bends is writing for specialists who all share the vocabulary, where the accounts agree the bracket can be noise; and the one gap the page names is very short-form writing, a headline, a label, where there is no room for the full term.

Try ‘him’ before you write ‘whom’. Try ‘him’ before you write ‘whom’ carries the test twelve separate conversations give, the widest agreement in its set: answer the sentence’s question with ‘he’ or ‘him’ and copy the shape. ‘Who wrote this?’, ‘he wrote it’, so who; ‘the colleague whom I emailed’, ‘I emailed him’, so whom. Two conversations give the memory aid, that whom and him both end in m, and three point out it is the same test you already half-know for ‘I’ and ‘me’: take Tom out, and ‘she sent it to I’ tells you it was ‘me’ all along. The page carries the accounts’ own caution, rated high, that the test misfires on sentences built on ‘is’ or ‘was’, ‘it is he’, not ‘it is him’, so ‘who is it’, and on passive sentences, and one caution says that if you are not sure, ‘who’ is the safer error, because a wrong ‘whom’ reads worse than a wrong ‘who’. Relative clauses, ‘the man who/whom I saw’, are the case the page says its conversations leave open. Then the argument, which the page says is bigger than the test: seven conversations say never write ‘whom’ at all, because ‘who’ is accepted almost everywhere now and a wrong ‘whom’ sounds like trying too hard, while twelve teach the test because they think it is worth knowing; the exchanges run three to four, three to three, five to two, and where the accounts settle it they settle it by register. The page’s own position, marked as its own: the test for the page, ‘who’ for the pub. Two corrections it keeps: ‘whomever’ is real, and ‘never end a sentence with a preposition’ was never a rule of English at all.

Is this deck for the room or for the inbox? Is this deck for the room or for the inbox? names the mechanism of the boredom in a wall-of-text slide: you read faster than a speaker talks, so you finish the slide, wait, and stop listening. The usual repair is a rule, fewer words, fewer bullets, and the page says its conversations argue at length, from real workplaces, about where the rule fails; what survives is a question. Decide the deck’s job before you design a single slide: a deck you present live stays sparse, because you are the information and the details go in your notes, while a deck that travels without you is a document and needs a document’s detail, and walls of text come from forcing one deck to do both jobs. For the deck that stays in the room the craft notes are consistent: key phrases only, a chart, a diagram or a picture over text, every full sentence into the speaker notes, and more than one conversation lands under ten slides for a fifteen-to-twenty-minute talk; for executive rooms one account recommends stating the conclusion on slide one, because decision-makers interrupt. For the deck that travels, the consulting deliverable, the finance read-ahead, the engineering trip report, the page says density is not a sin, and it carries that camp as correct in its context rather than argued away. Where one file must do both, its bridges are a sparse front section with the density in an appendix, hidden slides that ship in the file but stay off the screen, or two versions of the same deck. On technology, a few practised presenters describe kits that rhyme, the file in more than one format and place, every clip saved locally, their own adapters and cables and their own laptop where allowed, a full dry run on the actual equipment, and one person puts the deepest backup flatly: if you cannot deliver your material without the slides at all, you are not ready yet. On slide numbers, the better-evidenced side says the ‘of 30’ countdown pulls attention off the content and onto the clock, and the practical middle is small numbers for navigation without the total.

Learn the spreadsheet you already open. Learn the spreadsheet you already open says ‘learn to code’ has been shouted at office workers for a decade and mostly produces guilt, the course bought in January and abandoned by February, and offers the version the people who did it keep giving: you do not have to become a programmer, and deep skill in the spreadsheet you already open every day is the cheapest and, in its accounts, the best-repaid technical upgrade an office career has. The page describes working life as running on shared spreadsheets, fragile, half-broken ones maintained by nobody, and says the person who can sort and filter cleanly, build a pivot table, and use a lookup to join two lists is the person the file obeys. The method that stuck in its accounts is not a course but a problem: pick a real task from your own week, the report rebuilt by hand every Monday, and learn exactly the trick that kills it, then the next. Its natural ladder, roughly as people climbed it: sorting, filtering and conditional formatting first; pivot tables the week a summary is needed; lookups the week two lists must talk to each other; the built-in import-and-cleanup tools when the same messy file arrives every month; and a recorded macro the day something must happen fifty times. Free materials cover all of it, and the page’s sharpest warning is aimed at the paid shortcuts, the ads promising a six-figure tech salary in twelve weeks. On pay, the split is carried straight: one person credits spreadsheet skill with doubling their salary over a chain of promotions, others say in plenty of offices intermediate spreadsheet work is now simply expected, and the resolving observation is that the payoff comes from what the skill lets you visibly do. The page keeps two quieter skills the same accounts rank above every formula: writing a clear document, and being genuinely easy to work with. Three warnings from the people who went furthest: a spreadsheet is not a database, and when a file becomes the system a team depends on, the fix is asking for a proper tool, not heroics; never test a script or macro you found online against live work files, and copy the data somewhere safe first; and installing tools or running code on a work machine can cross IT policy, so ask.

Who these pages are not for. The notebook page is about a private notebook, not official documentation, and names the tension in writing up the whole process for the company. The spelling page is written for the speller: if you are the one taking the letters down and you are hard of hearing, one account says the system helps them on that end, and how you prefer to be spelt to is yours to say. The abbreviation page bends for specialists who share the vocabulary and has no answer for a headline or a label. The pronoun page says that if you are speaking rather than writing, the seven conversations are right and you may stop reading, and that if your first language marks its nouns for case, two conversations say you probably get this right already, by instinct English speakers were never given. The deck page says that if anyone in your audience is hearing-impaired, joining by a bad connection, or reviewing the file later, a sparse deck may be no record at all, and that contraindication outranks style; and that if the deck is fine and the standing-up part is the wall, that is stage fright, a subject it does not cover. And the spreadsheet page carries an argument about who this is for, three accounts to three, and its own note: if you try and it will not stick, that is information about the tool, not about your worth, and if your work is not at a desk at all, the page was never your tool.