Take part in your own learning.
Being a good team member isn’t about just following instructions without question. While it’s important to do what you’re asked, real growth comes from thinking deeper about your work. When you get a task, don’t just finish it quickly. Take a moment to see how your work fits into the company’s bigger goals.
Self-sabotage often happens in two ways: either you never ask questions and risk making big mistakes, or you ask too many questions without trying to solve things yourself. If you depend on your manager for every step, it can make you seem less independent. But if you stay silent when you’re confused, you might miss deadlines and lose trust.
To strike a good balance, try the “15-Minute Rule.” If you get stuck, spend fifteen minutes trying to solve the problem yourself. Check old files, read the training manual, or search online. If you’re still unsure, go to your manager and explain what you’ve already tried. For example, you could say, “I hit a snag here, and I tried X and Y. Which direction do you think makes the most sense?”
Taking this proactive approach changes how others see you. Instead of just following orders, you become someone who solves problems. It shows your team that you respect their time, value their knowledge, and can think critically. Being coachable means taking part in your own learning, not just listening.
Put these approaches into practice.
Let’s look at practical ways to transition from an order-taker who escalates every problem to a critical thinker who presents calibrated solutions.
“I used to think my value was measured entirely by how fast I closed out my task tickets. I spent an entire morning rushing through a client data cleanup, only to realize later that I had deleted key legacy tags the analytics team needed for their quarterly forecasting. Rushing cost the team two days of recovery work. Now, before I start any task, I spent three minutes mapping out who relies on my data downstream.”
DON’T rush blindly through an assignment just to cross it off your checklist, ignoring how your immediate output connects to the organization's overarching milestones.
DO take a deliberate pause before executing a task to understand how your specific workload fits into the company’s bigger goals.
“When I first started, I would message my supervisor on Slack every time a software tool threw an error code. I thought I was being transparent, but she eventually pulled me aside and noted that my frequent micro-pings were derailing her focus. I switched to the 15-Minute Rule. The next time the system errored, I researched our internal Wiki page first, found the patch, and fixed it myself. It was an incredible confidence boost.”
DON’T default to sending instant, knee-jerk messages to your manager the second you hit a system snag or minor point of confusion.
DO enforce the "15-Minute Rule" by dedicating an isolated block of time to exploring old files, internal knowledge hubs, or manuals before requesting help.
“I ran into a budgeting mismatch on our project spreadsheet. Instead of saying 'The numbers don't match, what do I do?', I approached my lead and said: 'Our tracking sheets show a $5,000 variance. I verified the invoice log and confirmed the math adds up. I see two paths: we can either re-allocate it from the marketing surplus or log it as a one-time variance. Which makes the most sense?' He smiled and told me he appreciated that I brought him a decision framework instead of an errand.”
DON’T present a raw, unexamined roadblock to your team, forcing your supervisor to do the cognitive heavy lifting of figuring out the next steps.
DO structure your help requests by clearly stating the exact issue, detailing the avenues you already explored, and presenting a choice between calibrated options.
“During team onboarding, I used to passively write down exactly what my peers told me to do without processing the underlying systems. It kept me dependent. I shifted my style—I began taking those raw notes, converting them into a clean, searchable step-by-step SOP document for our team drive, and sending it to my manager to verify. Turning my learning curve into a permanent corporate resource proved I wasn't just consuming training; I was building operational assets.”
DON’T sit back as a passive observer who simply nods along to directions, treating your manager as a human instruction booklet.
DO engage as an active participant in your own development, using your resourcefulness to prove you respect your team's time and value their expertise.
“I was handed a complex portfolio audit assignment that used terminology I had never seen before. Fear told me to stay quiet so I wouldn't look unqualified, but I knew hiding would cause a massive bottleneck. I spent twenty minutes looking up industry definitions, mapped out what I understood, and then reached out: 'I’ve mapped our target metrics, but I want to ensure my calculation methodology aligns with our historical standards before I run the final script.' That proactive check protected our data accuracy and proved I was reliable.”
DON’T remain frozen in total silence when you are profoundly confused, masking your hesitation until a deadline is missed and trust is shattered.
DO recognize that targeted, well-researched clarification is an indicator of professional maturity, protecting the business from downstream operational errors.
Before you send that next quick instant message to your manager asking for help, have you spent at least ten minutes exploring potential solutions on your own so you can present options instead of just a problem?
Integrate these professional strategies into your workflow—whether you’re refining your own work or mentoring your team or clients.
Live coaching hour for new professionals.
TUESDAYS AT 12 PM ET
Meet up with fellow professionals—0-3 years into their career—in a virtual space where you can track your work accomplishments, articulate your skills, troubleshoot challenges, share experiences, and receive guidance in addition to what your organization provides.
Subscribe for free to participate.