Skip to content

A Team Lead, a Blank Page and One Junior Engineer’s Next Step

Published November 9, 2026 by Beena Yadav

The team in this story is invented, assembled for illustration, but anyone who has worked in a small platform group will recognise the shape of it. Five engineers, one product, a quarterly review looming. The lead, Femke, has been asked to write down “the career path for the team” so that the review can tick a box. She opens a blank document, writes a heading and stares at it for twenty minutes. Nothing she types is wrong. Nothing is useful either. This is the story of how she fixes that by writing for one person, and what changed on the team afterward.

The first draft nobody needed

Femke’s first draft was thorough. It described levels from junior to principal, listed skills for each level and ended with a paragraph about continuous learning. It could have been pasted into any company handbook in the country. When she showed it to the team, there were polite nods. Then Joris, the most junior engineer, asked a quiet question: “So what should I do next month?”

The document did not answer. It described a ladder; Joris wanted a step. That gap between a general description and a specific next move is where most career documents fail, and it is a close cousin of the problem in many technical docs: they describe the whole system when the reader needs the next action.

The decision to write one page for one person

That evening Femke tried something different. She closed the handbook draft and wrote a page addressed to Joris by name. She asked herself what he was good at, what worried him and how much time he had. Joris was strong at scripting, nervous about being on call, and sharing his time between support tickets and a half-finished migration. He had, realistically, a few hours a week to spare for growth.

With that picture in mind, the page nearly wrote itself. It said: your scripting is already helping the team, so keep doing it and write short notes on each script. Your on-call fear is common and fixable, so shadow two shifts before taking your own. Your time is limited, so pick one learning goal for the quarter, not five. It was about half a page long.

What the page contained

It was plain, and it is worth listing what it had because the structure is reusable:

  • One strength to build on, named specifically.
  • One worry, acknowledged without drama.
  • One goal for the next quarter, with a way to tell whether it was reached.
  • One thing the team would do to help, such as pairing sessions.
  • One date to look at the page again.

The shape resembles career guidance found in articles like this outline of the route from entry-level to senior engineer, but with a crucial difference: it treated the route as something walked by a specific person at a specific pace.

How the team reacted

Joris read it twice, which Femke noticed, and then asked whether the two shadow shifts could start the following week. They did. The remaining engineers saw the page, because Joris mentioned it, and within a few days two of them asked for the same. Kasper, a former system administrator, wanted a page that took his operations background seriously and pointed him towards automation without implying he was behind. Femke wrote it, drawing on the kind of reasoning found in a discussion of moving from system administration and support into DevOps roles, then rewrote every sentence for Kasper alone.

Not one of the pages matched another. That was exactly the point, and it was also the part Femke had feared most. She had assumed that individual pages meant more work than one shared document. In practice each took under an hour, because each had a short list of questions to answer and one reader to answer them for.

The review, and what happened to the original handbook draft

At the quarterly review, Femke did not present a ladder. She showed, with permission, how each engineer’s page had a goal and a date. The reviewers asked sensible questions about consistency and fairness, and she answered that the common frame, strength, worry, goal, help, date, was identical, while the contents varied. Consistency of process, not sameness of content.

The handbook draft did survive, trimmed to two pages, as background reading. It was no longer the main event. It had become what it should have been from the start: reference material for people who wanted to see the whole map, written after the useful part.

The small habits that kept it going

Femke added two routines so the pages did not become a one-off gesture. First, a ten-minute slot at the end of each monthly one-to-one, where the page was reopened and one line updated. Second, a rule that nobody wrote a page for someone else’s report without asking the owner first, so that the idea did not turn into something done to people rather than with them.

She also noticed a side effect she had not planned. When engineers wrote their own worry in their own words, the team learned things it would never have heard in a stand-up: that one person dreaded giving demos, that another felt invisible during planning. Those were fixable problems, and several were fixed simply because they were finally written down.

What went wrong

No story is complete without a stumble. Femke’s first attempt at Kasper’s page was too gentle; she hedged so much that he missed the actual advice. He told her so, kindly, and she cut the hedging. Another time she wrote a page for an engineer she knew less well, leaned on guesses and got the worry wrong. The lesson was to ask before writing: ten minutes of conversation, then the page.

There was also the temptation to turn the pages into performance reviews. She kept them separate. The page was a note of support from a lead to a colleague, not an evaluation, and mixing the two would have made people write defensive replies.

Where the lessons travelled next

Months later Femke started jotting what she had learned, in the shape of short pieces for an imagined newly promoted lead. She posted them on iBlogUp, an online home for writers, with personal subdomains for their pieces and an RSS feed for subscribers, mostly because the setup was simple. A few engineers from other companies subscribed. One wrote back saying she had written her first page for a colleague and it had gone better than expected.

The practical takeaways

For readers who would like the story boiled down to actions, here they are:

  1. When a document feels empty, ask who is reading it. Name one person.
  2. Ask that person two questions before writing: what worries you, and how much time do you have?
  3. Give the page one strength, one worry, one goal, one offer of help and one date.
  4. Keep it short. Half a page is enough.
  5. Write the general reference material after, not before.
  6. Expect to get the first one slightly wrong, and welcome the correction.

Joris, in this telling, took his own on-call shift after the second shadow shift. It went unremarkably, which is the best result an on-call shift can have. The team never did produce the grand career document the review had originally asked for. What it had instead was something more useful: five short pages, five real people, and a habit of asking what the next step looked like for the person sitting across the table.