Skip to main content

The habits that get you trusted with more in your first year in IT

In your first year, the people around you are deciding how much they can hand you without checking. Ask at the right moment, say early when something has gone wrong, leave a written trail anyone can follow, and walk into each probation review and appraisal knowing what you want to take on next.

6 min read Sources checked 21 November 2026 UK
A hand ticking items on a handwritten checklist in a notebook
Photo: Jakub Zerdzicki on Pexels

Employment rights here are for England, Scotland and Wales; check your own contract and policies as well.

Nobody expects you to know the estate in your first year. What your team is working out is how much they can give you without checking it afterwards. That decision rests on habits more than on knowledge: whether you ask before you are stuck for a day, whether you say so early when something breaks, whether your notes let someone else pick up the work, and whether you use your reviews to ask for the next thing. Each of those is something you can start in your first week.

Read the paperwork in week one

Your written statement and your employer's probation policy, if it has one, tell you how your first months will be judged. By law your employer must give you a principal written statement of employment particulars on your first day, and GOV.UK lists what it has to contain: your pay, your hours, your holiday, any obligatory training and how long any probation period is and what its conditions are. A wider written statement follows within two months.

Read the probation section closely. Acas describes probation as a period at the start of a job for the employer to check you suit the role, and for you to check the role suits you. There is no legal requirement to have one, and it can be any length, so yours is whatever your statement says. Probation does not switch off your basic rights: Acas lists the minimum wage, paid holiday and protection against discrimination among the rights that apply from day one. One detail catches new starters out. Your employer can delay enrolling you in the workplace pension for up to three months, but Acas says they must enrol you if you ask.

If the statement mentions probation reviews, find out when they are and put them in your calendar now. Acas calls them formal checkpoints and recommends regular reviews plus a final one, so the outcome is never a surprise. Treat each one as a deadline for having something to show.

Learn the place before you change it

The fastest way to lose goodwill early is to fix something in a way nobody else on the team would. Spend your first weeks learning how your team does the routine things: where tickets go, who approves a change, what is documented and where, which systems are fragile and who knows them. Write it down as you go, in your own notes and, where it is missing, in the team's documentation. A new starter who fills the gaps in the onboarding notes is doing work everyone notices and nobody else wanted.

The SFIA framework, which describes seven levels of responsibility in IT work, is a useful mirror here. Its level 2, Assist, describes someone who works under routine supervision, uses limited discretion on routine problems and "decides when to seek guidance in unexpected situations". Level 3, Apply, describes someone who works under general direction, takes "a methodical approach" to moderately complex issues and "determines when issues should be escalated". Much of a good first year is the move from the first description towards the second, and the wording tells you what to practise.

Ask well, and at the right time

There are two ways to get asking wrong. One is asking before you have looked; the other is spending a day stuck because you did not want to look slow. A workable rule is to set yourself a time limit for a problem, say half an hour on a routine ticket, then ask, and to arrive with what you have already tried.

A good question has three parts: what you are trying to do, what you have checked, and where exactly you are stuck. "The printer on the second floor shows offline; it pings, the queue on the print server is paused and I don't have rights to resume it" gets a fast answer and shows your working. "The printer doesn't work" gets a sigh. Write the answer down when you get it, so you only ask once.

SFIA puts the same habit in its level 2 description: listening to understand and asking relevant questions to clarify. It also lists recognising your own gaps and seeking ways to fill them, which is the polite way of saying that "I don't know that yet, can you show me?" is a strength at this stage.

Say early when something has gone wrong

At some point in your first year you will break something: delete the wrong account, push a change to the wrong group, click a link you should not have. What happens next matters more than the mistake. Tell your lead straight away, say what you did and what you have already seen, and do not try to quietly undo it first, because a hidden fix that goes wrong turns a small incident into a large one.

Teams that run well are built to receive that message. The Google SRE book describes the blameless postmortem, a written record of an incident that looks for contributing causes "without indicting any individual or team", and says plainly that writing one is not punishment. It warns that where people are blamed and shamed, they stop bringing problems to light. The NCSC makes the same point about phishing: staff who fear reprisals will not report mistakes promptly, if at all, and an organisation should want reports even when the link has been clicked. If you click something, report it. You are doing exactly what security teams ask people to do.

When the dust settles, offer to help write up what happened. Being the person who explains a mistake clearly, including your own part in it, is one of the quickest ways to be trusted with more.

Leave a trail anyone can follow

Most of the work that gets noticed in a first year is visible because it is written down. Ticket notes another engineer can act on without phoning you. A short how-to for the job you have now done three times. A change request that says what will happen, how you will know it worked and how to undo it. The non-technical skills guide covers writing for other people in more detail.

Keep a private record too: a few lines a week on what you fixed, what you learned and anything you did beyond your tickets. You will not remember in eleven months, and you will need it for your reviews. The promotion and pay rise guide explains how to turn that record into a case.

Use your reviews, don't sit through them

Acas describes a performance review as a chance to discuss what you are doing well, what could improve, whether you need more support or training, and your career and development objectives, and recommends having one at least once a year. Go in with your own answers to all four. Bring two or three examples from your record, one area you know you need to work on and what you are doing about it, and one specific thing you would like to take on next: a system to learn, a type of ticket to own, a shadowing slot with second line or the network team.

Training is the obvious ask, so find out what your employer offers before you pay for anything yourself. If you work for an organisation with at least 250 people, GOV.UK says that once you have been an employee there for 26 weeks you can formally ask for time off for training that helps you do your job better, though that time is usually unpaid unless your employer agrees to pay it. The page lists exceptions, including agency workers and some 16 to 18 year olds already in education or training, so check it applies to you. You will rarely need the formal route, but knowing it exists makes the informal conversation easier.

By the end of the year

A good first year usually leaves you with a short list of things you can point to: problems you now solve without help, documentation you wrote that the team uses, one or two areas where you have become the person people ask, and a clear next step agreed with your manager. If you are on a service desk, the first line to second line guide covers what that next step usually looks like. If you are not yet sure which direction to take, choosing an IT specialism is a good place to start thinking about year two.

Common questions

Can I be dismissed during probation without a reason?
Protection from unfair dismissal depends on how long you have worked there, not on probation. Acas says that from 1 January 2027 it becomes a right after 6 months in a job, so early in a new job you will usually not have it yet, and even with it an employer can still dismiss fairly. Protections such as those against discrimination apply from day one. Read the Acas pages on probation and dismissal, and your written statement, if you are worried.
Should I study for a certification in my first year?
Often yes, but pick one that matches the work in front of you, and ask your manager first: your employer may pay for it, and a certification they chose for you is easier to turn into new responsibilities.

Sources

Every figure and rule in this guide comes from these pages, read on 21 November 2026. Pay rates, exams and schemes change: check the source before you rely on one.

  1. Employment contracts: Written statement of employment particulars (GOV.UK)
  2. What probation is (Acas)
  3. Probation reviews (Acas)
  4. Level 2 - Assist (SFIA Foundation)
  5. Level 3 - Apply (SFIA Foundation)
  6. Levels of responsibility (SFIA Foundation)
  7. Postmortem Culture: Learning from Failure (Google (Site Reliability Engineering book))
  8. Phishing attacks: defending your organisation (National Cyber Security Centre)
  9. Reviews and appraisals: performance management (Acas)
  10. Training and study at work: your rights (GOV.UK)

Spotted something wrong or out of date? Tell us and we will correct it.

Keep reading

More careers guides

All careers guides
Share this guideXLinkedInFacebookEmail
All careers guides

The KBY Brief

A short email about twice a week with new runbooks, configuration traps and fixes from KBY Technologies.