Habit, Not Hack: Following Instructions (Trainee)

Doing more than asked isn't always impressive. Sometimes it's just evidence that you didn't follow the instructions.

The instructions were clear.

Three slides. Ten minutes. Focus on process, not results.

So why did Jordan walk into the interview with twelve?

The Reasoning That Felt Reasonable

Jordan had stayed up late the night before, and the decisions had all made sense at the time.

I need to give context. They should see how much work I did. What if three slides looks too simple? What if they think I'm not thorough?

So Jordan polished figures nobody had asked for. Added backup slides just in case. Squeezed in an extra experiment because leaving it out felt irresponsible. The extra work was real, the reasoning was understandable, and by the time Jordan finished, the presentation was genuinely impressive — dense with evidence, careful in its detail, twelve slides of someone who clearly knew their stuff.

What it wasn't was what had been asked for.

What Happened in the Room

The panel smiled. Nodded. Took notes.

At slide four, someone interrupted.

"Can we pause you there? We're running short on time."

Jordan rushed. The story that had been carefully constructed across twelve slides had to be compressed into the remaining minutes in a way it was never designed to survive. The conclusion felt abrupt. The narrative unraveled. Not because the work was weak — the work was strong — but because the structure had been built for a presentation that nobody in the room had agreed to receive.

The feedback came later, and most of it was fine. But one comment stood apart from the rest.

"We were evaluating how much you know. But we were also evaluating whether you can follow constraints."

That sentence stung more than any critique of the science.

What Jordan Had Gotten Wrong

Jordan had treated the instructions as suggestions — as a rough framework that could be adjusted upward by someone who had enough to say and enough confidence to say it. As guidelines for people who weren't quite ready, rather than requirements for people who were.

But instructions are not suggestions. They are data.

They tell you what the evaluator actually values. They reveal what the real test is. A ten-minute limit is not a test of how fast you can talk — it's a test of whether you can prioritize. A three-slide limit is not a test of minimalism — it's a test of whether you can identify what matters and commit to it. A focus on process, not results instruction is not a stylistic preference — it is a direct statement about what the panel is trying to learn about you.

Every constraint in an evaluative brief is a piece of information about what success actually looks like. Jordan had ignored all of them and substituted their own definition.

And the panel had noticed — not the extra work, but the substitution.

What Jordan Did Differently the Next Time

The next assignment arrived a few weeks later. Another take-home, another presentation, another set of instructions.

This time, Jordan printed them out before opening a single software program.

They read each constraint and wrote next to it, in the margin, what they thought it was testing. Time limit — prioritization. Slide limit — clarity. Process focus — judgment about methodology, not just outcomes. They built the entire outline inside those limits before adding a single piece of content. They cut work they were proud of because it didn't serve the ask. They cut context they thought was necessary because the instructions didn't ask for it.

The result wasn't flashier than the previous attempt. It was quieter, tighter, more deliberately shaped.

The feedback was different too.

"You did exactly what we asked."

Which, Jordan realized, was not faint praise. It was the specific thing that had been tested — and the thing Jordan had failed the first time.

The Habit: Treat Instructions as Requirements, Not Suggestions

This habit has one core practice, and it comes before any other work begins.

Before starting any interview task, take-home assignment, or evaluative presentation, read the instructions the way you would read a paper's methods section — as precise, intentional, information-dense text that tells you exactly what the experiment is designed to measure.

Then ask: what are they really testing by setting these constraints?

A time limit tests prioritization. A slide limit tests clarity. A word count tests concision. A specific focus area tests whether you can subordinate your own interests to the question being asked. Each constraint is a piece of the evaluation rubric, stated plainly.

Once you know what's being tested, design only for that. Not for what would impress in a broader context. Not for what would demonstrate the full scope of your work. For what was asked — precisely, completely, and without addition.

A Note on What This Isn't

This is not a habit about doing less or being less ambitious. Jordan's work was genuinely strong. The problem wasn't the quality of what they prepared — it was the mismatch between what they prepared and what the situation required.

There are contexts where doing more is exactly right — where going beyond what was asked demonstrates initiative, thoroughness, and genuine engagement. Learning to read which context you're in is part of the skill.

In evaluative settings — interviews, take-homes, formal assignments with explicit constraints — the context is almost always one where following the brief precisely is not the floor of acceptable performance. It is the ceiling of what's being measured. Exceeding the brief in those settings doesn't signal more capability. It signals that you substituted your own judgment for the evaluator's stated requirements, and that is not the signal you want to send to someone who is deciding whether to hire you.

For Supervisors and Mentors

When trainees ignore instructions in evaluative settings, the instinct is to address the content — the extra slides, the overtime, the scope creep. But the more useful conversation is about the reasoning underneath it.

Most trainees who exceed the brief are not being arrogant. They are operating on a mental model — built over years of being rewarded for doing more, going further, showing more — that over-delivery is always better. They have not been told explicitly that this model breaks down in certain contexts, because nobody told them. It was assumed to be obvious.

It isn't obvious. It needs to be said directly: in this setting, doing more than asked is not a signal of strength. Following the brief exactly is. And then it needs to be reinforced when they get it right — because the instinct to over-deliver is strong, and it needs a counter-signal that is equally explicit.

Excellence isn't only what someone can do. It's whether they can do what was asked — under the conditions that were set, within the limits that were given, for the purpose that was stated.

The instructions were the test. They always were.

That's not a hack. That's a habit.

✨ Following instructions is easier when expectations are explicit rather than assumed. The Communication, Boundaries & Professionalism tools help teams discuss communication preferences, response expectations, and working norms before small misunderstandings become larger frustrations. Click to explore.