Most new graduates lose weeks of productive momentum because they’re waiting for instructions at work that may never come. Here’s the short answer: you don’t need permission to start most tasks. What you need is a framework for knowing which tasks warrant a question, which ones you can begin on your own, and how to make a reasonable first attempt look like initiative rather than guesswork. That framework exists, and it’s learnable.
Why Do New Graduates Feel Like They Need Permission to Start?
The feeling that you need permission to start is almost universal among people entering the workforce. It makes sense. School rewarded you for following instructions precisely. You waited for the assignment brief, the rubric, the teacher’s clarification. Doing something wrong wasn’t just inefficient; it cost you marks.
Work doesn’t function that way. Managers are often too busy to hand-hold, briefs are frequently vague, and the expectation shifts from “follow instructions” to “show initiative.” Research published in the Journal of Vocational Behavior found that role ambiguity, the experience of being unclear on what to do, is one of the top three stressors reported by employees in their first year of work. The problem isn’t personal inadequacy. It’s a genuine mismatch between what school trained you for and what work actually requires.
Psychologist Adam Grant, in his 2013 book Give and Take, describes a pattern he calls “proactive socialization,” where new employees who seek out tasks before being asked build credibility faster and feel less anxious about their standing. The act of starting, even imperfectly, builds confidence faster than waiting for certainty ever does.
What Actually Happens When You Wait for Clarity Before Starting?
Waiting for perfect instructions before you begin feels responsible. It isn’t. A study by the project management firm Planview found that knowledge workers spend an average of 42% of their time on work they describe as “low value or unclear,” much of that time consumed by the friction of not knowing how to begin.
When you’re constantly waiting for instructions at work, three things happen. First, you miss windows. Deadlines creep up while you’re still in the “I’ll start once I understand it better” phase. Second, your manager notices. Not necessarily in the moment, but over time, consistent hesitation reads as low confidence or low capability. Third, and this is the one people don’t expect: waiting makes the task harder, not easier. Unstarted tasks accumulate psychological weight. Research on the Zeigarnik effect, first documented by psychologist Bluma Zeigarnik in the 1920s, shows that incomplete tasks create a persistent mental load that disrupts focus on other things.
Starting badly is almost always better than not starting. A rough draft, an incomplete plan, a first pass with obvious gaps: all of these are objects your manager can respond to. Silence is not.
How Can You Tell When to Ask vs When to Start?
This is the practical question that most workplace advice skips over. The answer isn’t “always ask” or “always figure it out yourself.” It’s a simple decision hierarchy that experienced workers run almost unconsciously.
Start without asking when: - You have enough information to make a reasonable first attempt - The cost of a wrong direction is low (the work is early-stage or easily revised) - The question you’d ask is something you could answer yourself with 10 minutes of research - You can make your assumptions explicit and share them alongside your work
Ask before starting when: - Getting it wrong would require significant rework for multiple people - The task involves irreversible actions (sending communications, publishing, spending budget) - You genuinely can’t form a working hypothesis with the information available - A five-minute conversation would save five hours of work
The key shift is moving from “I’m unclear on what to do” as a reason to pause, to “I’m unclear on what to do” as a reason to form a hypothesis and test it. Research published in the Academy of Management Journal found that employees who frame ambiguity as a problem to solve rather than a signal to wait are rated significantly higher on performance by their managers after six months.
What Does a Good “First Attempt” Actually Look Like?
One underrated skill is learning to show your working. When you start a task under ambiguous conditions, you don’t have to pretend you knew exactly what you were doing. You can be transparent.
A practical format: begin the task, document your assumptions at the top of whatever you produce (“I interpreted this as X, so I’ve structured it as Y”), and flag the one or two decisions where you’d genuinely welcome input. This approach does several things at once. It demonstrates initiative. It gives your manager something concrete to respond to. And it protects you if you’ve misread the brief, because you’ve shown your reasoning, not just your output.
Organizational psychologist Tasha Eurich, in her 2017 book Insight, found that self-aware employees who communicate their reasoning process are perceived as more competent, not less, even when they make mistakes. Competence in the workplace isn’t about being right the first time. It’s about being able to explain how you got somewhere and adjust when needed.
This matters especially in the first six months. According to research from the Harvard Business Review, new employees who ask fewer but better-targeted questions, combined with taking more independent first attempts, are promoted faster than those who either ask constantly or never ask at all.
How Do You Break the Habit of Waiting for Instructions at Work?
This is partly a mindset shift and partly a behavioral one. The mindset shift: your manager’s job is not to pre-chew tasks for you. Their job is to oversee outcomes. The gap between “here’s the brief” and “here’s the finished work” is yours to fill.
The behavioral shift is about building a small routine. Before you flag a task as “blocked” or send a clarifying email, run through three questions. What do I know? What can I reasonably assume? What would a sensible first draft look like based on those assumptions? Most of the time, you’ll find you can make a start. The question you were about to send becomes a note in your document instead.
A contrarian take worth considering: many new graduates overcommunicate questions because it feels safer, not because they genuinely need the answer. Asking a question offloads the risk. If you ask and then follow the answer, you can’t be blamed for the direction. Starting on your own means owning the direction. That accountability is uncomfortable. But it’s also exactly what builds a professional reputation.
Researchers at Stanford’s Graduate School of Business, in work on proactive behavior at work, found that employees who demonstrate ownership over ambiguous tasks receive significantly higher ratings on leadership potential, even in junior roles. Initiative, it turns out, is visible earlier than most people think.
How Does Procrastination Connect to Waiting for Permission?
Waiting for clarity before starting is, in many cases, procrastination wearing a professional disguise. It feels responsible. It looks like diligence. But the underlying mechanism is the same: avoiding the discomfort of uncertain action.
Researcher Fuschia Sirois, writing in the British Journal of Health Psychology in 2016, identified that procrastination is fundamentally an emotion-regulation strategy rather than a time-management failure. People delay not because they’re lazy but because starting a task activates anxiety, self-doubt, or fear of judgment. Waiting for instructions at work plugs neatly into this pattern. The instruction becomes a permission slip that removes the emotional risk of choosing a direction.
Understanding this reframes the problem. The fix isn’t better time management. It’s learning to tolerate the discomfort of an uncertain start. Small, concrete first steps reduce that discomfort faster than any amount of planning or clarifying. Apps and tools that help you break tasks into their smallest possible first action can be genuinely useful here, precisely because the barrier they lower is emotional, not logistical.
Time Is Luck is built around this principle: that the hardest part of any task is the start, and that structure helps you begin before you feel ready.
FAQ
Is it ever wrong to start a task without asking first?
Yes, sometimes. If a task involves irreversible actions, significant budget, or communications to external stakeholders, a quick check-in is the right call. The goal isn’t to never ask; it’s to ask strategically rather than habitually. Reserve your questions for the decisions where getting it wrong would be genuinely costly to reverse.
What should I do if I start a task and realize I’ve gone in the wrong direction?
Be direct and early about it. A short message saying “I’ve made a start on this and I want to check one assumption before I go further” is much better received than delivering something entirely off-brief. Managers notice who catches their own errors early far more than who makes them.
How do I handle a manager who gives very unclear briefs regularly?
Start building a one-page summary habit. After any verbal brief, send a short written summary of your understanding and your intended approach. This creates a record, prompts your manager to correct anything you’ve misunderstood, and removes ambiguity before you’re deep into the work.
Won’t starting without asking make me look presumptuous or like I’m overstepping?
Rarely, and the risk is much smaller than most new graduates think. Most managers respond positively to a first attempt with documented assumptions. The way to overstep isn’t by starting; it’s by starting and refusing to accept feedback on your direction.
How long should I try to figure something out on my own before asking?
A useful rule of thumb: spend 15 to 20 minutes genuinely attempting to form a working hypothesis or make a start. If you’re still genuinely blocked after that, ask. This isn’t a hard rule, but it stops both the instant-question reflex and the hour-long spiral of unproductive confusion.