Habit, Not Hack: Following Instructions (Mentor)

People don't always miss instructions because they lack discipline. Sometimes they miss them because nobody explained why those details matter.

The candidates were strong.

Smart, polished, accomplished. Dr. Patel had been on enough hiring committees to recognize genuine ability, and the people interviewing that day had it. The science was solid. The thinking was clear. On paper, the pool was one of the best he'd seen.

But as the day went on, something kept snagging.

What the Committee Noticed

The instructions had been explicit. Ten minutes. Three slides. Focus on reasoning, not results.

And yet.

Extra slides, presented without acknowledgment that the limit had been exceeded. Presentations that ran to fifteen, eighteen minutes while the panel watched the clock. Long digressions into work nobody had asked about, offered with the enthusiasm of someone who assumed more was always better.

The panel was polite. They listened. They asked their questions.

During the debrief, someone said it plainly: "They know a lot. But they didn't follow the instructions."

The room went quiet in the particular way rooms go quiet when something true has been said that nobody wanted to say first.

Dr. Patel sat with it. Not defensively — he hadn't trained most of these candidates. But with the specific discomfort of recognizing something he had probably contributed to, in his own lab, in ways he hadn't examined.

The Assumption He Had Never Questioned

He had always assumed, without quite articulating it, that following instructions was obvious. A baseline. Something competent researchers just did.

But thinking back through his own mentoring, he could see the places where that assumption had broken down — and where he had reinforced the opposite.

Fast timelines praised. Conservative ones questioned. Trainees who brought extra work to meetings received with something that looked like approval. Presentations that exceeded the brief treated as evidence of thoroughness rather than misalignment. The implicit message, delivered consistently and never once stated out loud: more is better, and doing more than asked signals that you take it seriously.

His trainees had learned what he had taught. They had learned that over-delivery was rewarded, that brevity required justification, that exceeding the brief was ambition and staying within it was timidity. None of that was what he meant to teach. But incentives don't require intention to be effective.

By the time those trainees walked into an interview room where the rules had changed — where the brief was the test, not a floor to exceed — they had no framework for that. Nobody had given them one.

The Habit: Explain What Every Constraint Is Testing, Not Just What It Is

That semester, he changed how he framed every assignment he gave.

He stopped listing instructions and assuming they were self-explanatory. He started explaining what each constraint was actually measuring.

"The time limit isn't about speed. It's about prioritization — about whether you can identify what matters most and commit to it."

"The slide limit isn't about minimalism. It's about clarity — about whether you can make a complex idea legible without hiding behind volume."

"The word count isn't arbitrary. It's asking whether you can be precise."

These were not long explanations. They took thirty seconds each. But they did something the instruction alone couldn't do: they told the trainee what success actually looked like from the evaluator's side of the table. Not here is the rule but here is what following this rule demonstrates about you.

The Question He Stopped Answering

Dr. Patel also stopped rescuing people who ignored the brief.

When trainees asked "can I add just one more slide?" he used to say yes, or say nothing, or quietly let it go. He recognized now that each of those responses had been a signal — that the limit was negotiable, that extra was welcomed, that the brief was a suggestion from someone who hadn't seen how much they had to show.

He started answering differently.

"You can. But I want you to know what signal that sends — and to make that choice deliberately rather than by reflex."

Not a prohibition. A reframe. He was not trying to prevent them from adding the slide. He was trying to give them the information they needed to decide whether to — information that, in an actual interview, nobody would provide. The panel would simply note it and move on.

The first time he said it, the trainee paused for a long moment, then said: "I didn't think about it that way."

That was the point.

What Shifted in the Lab

The questions trainees asked in preparation for assignments started changing.

Before, the questions had been about content — what to include, how to make the work look strong, whether a particular figure was compelling enough. After, the questions started with the brief. What is this time limit testing? What does focusing on process over results mean they're not asking about? What would "exactly what they asked for" look like here?

The work that came out of those questions was not bigger. It was better targeted. Tighter. More confidently shaped. The difference between a presentation that tries to demonstrate everything and a presentation that answers a specific question is not a difference in effort — it's a difference in understanding what was actually being asked.

The quality improved not because the standards went up, but because the effort finally landed in the right place.

What This Habit Asks of You

Three specific changes, none of which require restructuring how your lab runs.

Explain what each constraint is testing. When you give an assignment with a time limit, a word count, a scope restriction — say out loud what that constraint is designed to reveal. Not as a lecture, just as information. "This limit is testing X." Once your trainee knows what's being measured, they can try to demonstrate it. Before that, they're guessing.

Say clearly when doing more is not better. This needs to be a direct statement, not an implication. Most trainees have spent years in environments where more was always safer. They need to hear explicitly, from you, that certain contexts operate by different rules — and that exceeding the brief in those contexts doesn't signal strength. It signals that they substituted their own judgment for the stated requirements.

Give feedback on alignment, not just content. When reviewing assignments or mock presentations, evaluate explicitly whether they did what was asked. Not just whether the science is good, not just whether the slides are clear — but whether the response fits the brief. If it doesn't, name that as specifically as you would name any other flaw. "The work is strong, but you're over the limit by four minutes, and in an interview that would be the first thing the panel noticed."

A Note on What This Isn't

This is not a habit about teaching trainees to be small or cautious or deferential. Dr. Patel's lab did not become a place where ambition was penalized or where nobody went beyond what was required.

What changed was the targeting. Ambition directed at the actual question is more impressive than ambition directed at a question nobody asked. The trainee who reads the brief precisely, designs for it completely, and delivers it cleanly signals something that the trainee who brings twelve slides when three were asked does not: that they can be trusted with a real constraint, in a real setting, with real stakes.

Excellence isn't only what someone can do. It's whether they can do what was asked.

The skills your trainees show up to interviews with are, in large part, the skills your lab taught them to value. If following instructions exactly has never been named as a professional skill in your lab — never explained, never modeled, never praised — then your trainees have no reason to treat it as one.

You have the opportunity to change that before the interview room does it for them.

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.