What Claude is, in plain English
Who makes it, how it differs from a search engine, and the one mental model that saves people a fortnight of confusion.
ReadTwenty short pieces, none of them longer than a coffee. No jargon, no hype, and no pretending the tool is better than it is. If one of them saves you a meeting, it has done its job.
Three ways in. If you have never really used it, start with what Claude actually is. If the licences are already paid for and half the team has quietly stopped opening it, skip to why the results are patchy. If you are weighing up whether to spend anything at all, the four questions are the thing to read, and two of them cost nothing to fix.
Who makes it, how it differs from a search engine, and the one mental model that saves people a fortnight of confusion.
ReadOne mechanism sits underneath every strange thing you have noticed, and it takes five minutes to understand properly.
ReadWhat it holds, what it does not, and why filling it up is usually a mistake rather than an achievement.
ReadA short map for someone who wants to know where to type, not what the whole product range is called.
ReadThree assistants far closer to one another than the comparison articles admit, and the one difference anybody has measured.
ReadWhat the tiers are for, what they cost relative to each other, and why most people never make this choice at all.
ReadTwo separate things are packed into every model name. One is a decision you make, the other is just a date.
ReadHallucination is a misleading word for something quite ordinary, and knowing what it describes changes how you read the output.
ReadThe tasks it handles reliably, drawn from what people produce with it in a real week rather than from any product page.
ReadFive things it will not do well for you, and which of them the next release is not going to fix.
ReadFive categories I tell senior teams to keep away from it, including one that costs nothing measurable and matters most.
ReadFour things every decent prompt carries, from the same before and after example I use in sessions.
ReadAbout an hour a week at first, from the dullest parts of your diary, and a fair slice of the rest is not a saving at all.
ReadTwo people swear by it, the rest opened an account once, and nobody raises it because raising it sounds like a confession.
ReadFour questions to answer before you spend anything. Two of them you can settle yourself on a Friday afternoon.
ReadWhat to do when nobody in the room is neutral, and why the useful setting is the one that argues back.
ReadGenuinely useful on contract summaries and clause comparison. First pass, never the final word.
ReadStrong on drafting, weak on judgement, and the raw material of the work is somebody's livelihood.
ReadThe function that adopted these tools fastest is the one now paying for it. Sounding like everyone else is the risk.
ReadThe process that lives in one person's head, and the afternoon nobody has spare to get it written down.
ReadTwenty articles is a long way round to answer one question. Tell me in three lines what is not working and I will tell you whether training moves it, which two of these to read instead, or that you are already fine and should keep the budget. I have given all three answers this year.
Write to meA reply from me, not an assistant, inside two working days. If you would rather take something to your leadership team first, there is a one-page version of the four questions made for exactly that.