Graduate Starters: What Actually Prepares Someone for Their First Job

Ask a graduate three months into their first job what they found hardest. Almost nobody says the software.

They say they did not know when it was acceptable to ask for help, or how many times. They say they could not tell whether their work was good, because nobody told them and asking felt like fishing. They say a piece of feedback landed much harder than the person delivering it seemed to intend.

Now look at what a typical graduate induction covers: the systems, the org chart, the policies, the tools, a compliance module, and a talk from someone senior about values. All useful. Almost none of it touching the actual difficulty.

Why the gap exists

Education is unusually explicit about standards. There is a syllabus. There are marks. Someone tells you where you stand several times a year, in writing, against criteria published in advance.

Work is the opposite. Standards are mostly implicit, feedback is irregular and often indirect, and the criteria live in someone's head. A graduate is not lacking intelligence or willingness. They have spent sixteen years in a system that told them how they were doing and have entered one that largely does not.

That is a transition problem, and it is not solved by explaining the expense system.

The five things new starters actually struggle with

1. Calibrating when to ask

Ask too often and you look incapable. Ask too rarely and you waste two days on something someone would have unblocked in four minutes. Nobody states the rule because there is no rule, only a norm that varies by team.

What helps is being told the norm explicitly. A manager saying "if you are stuck for more than thirty minutes, come and ask" removes an enormous amount of private anxiety and costs one sentence.

2. Receiving criticism without collapsing or arguing

Most graduates have received criticism as a mark, privately, on finished work. Receiving it verbally, in progress, from someone they want to impress is a different experience and the first few times are genuinely hard.

The skill is separating the work from yourself, and it is learned rather than innate. Nobody is born able to hear that a draft is not good enough and treat that as information.

3. Working out what good looks like

In the absence of stated standards, most graduates either over-polish, spending three days on something wanted in three hours, or under-deliver because they cannot see what was implied.

Both are failures of calibration, not effort, and both are fixed by seeing examples. The most useful thing a new starter can be given is three pieces of previous work labelled: this was excellent, this was fine, this was not good enough, and here is why.

4. Managing upward

Nobody teaches this and everybody needs it. Knowing what your manager needs to hear and when, how to flag a problem early without seeming to complain, how to disagree with someone more senior in a way they can accept.

For graduates in workplaces with steeper hierarchies, which describes much of Asia, this is the single largest determinant of how the first two years go, and it is almost never part of a graduate programme.

5. Recognising the difference between not knowing and not being able

Early on these feel identical. Both produce the feeling of being out of your depth. But not knowing something is temporary and ordinary; not being able would be permanent and it is almost never the actual situation.

Graduates who leave a role in the first year often do so having confused one for the other, quietly, without telling anyone what they concluded.

What a graduate programme should include

1. Explicit norms, written down. When to ask for help, expected response times, what to do when stuck, how to flag a slipping deadline. Everything the culture assumes and never says.
2. Worked examples with quality labelled. Not a style guide, actual past work with a judgement attached and the reasoning shown.
3. Feedback early and small. The first piece of critical feedback should arrive in week two on something minor, so the first experience of it is not a large one at month six.
4. A named person who is not their manager. Somewhere to ask the question they cannot ask the person who writes their review.
5. Something that persists past the induction week. Almost every graduate programme front-loads everything into the first fortnight, which is exactly when a new starter has the least context to absorb any of it.

That last one is the one most often missed. The questions a graduate most needs answered arrive in month four, not week one. By then the induction is over, the cohort has dispersed to different teams, and the person who ran it has moved on to the next intake.

Where our Starters fit

We build a set of short courses called Starters, so this section is ours and should be read accordingly.

They are deliberately about why something matters rather than a procedure for doing it. That is a choice with a reason: procedures for professional behaviour vary by organisation and a general course teaching one is often wrong for the reader's actual workplace. Understanding why difficult conversations are avoided transfers anywhere; a five-step script for having one does not.

There are seven, and two are free with a free account. The wider platform addresses the persistence problem above: an assessment so a new starter knows something real about how they work before anyone gives them feedback on it, and a mentor that is available in month four when the actual question arrives, rather than only during the induction week when it had not occurred to them yet.

The honest limit is the same one that runs through all of this. A mentor that is AI cannot replace a good manager who explains the norms, shows examples of good work, and gives feedback early. If a graduate has that, they need much less of anything else. Most do not have it, and the gap is what we built for.