Trusting procedure, documenting well, staying objective

Every Task Early On Is a Test

That first assignment you’re given might not be glamorous.

Sometimes it feels like a setup. No clear scope. Conflicting inputs. Unrealistic timelines. You might even inherit something that’s already failed once or twice.

I’ve seen the same half-baked task passed from graduate to graduate, year after year. Nothing ever really gets delivered.

But here’s the reality:

Every early task is a test.

Not just of your technical ability, but of your mindset, discipline, and professionalism.

Control What You Can

You can’t control the politics, the legacy issues, or whether the task was well defined in the first place.

But you can control:

• How you show up
• How well you document
• Whether you ask questions or stay silent
• Whether you follow procedure or take shortcuts

When you focus on what’s in your control, the frustration doesn’t disappear, but it becomes manageable.

You shift from reacting to operating.

Control is process. Outcome is a bonus.

Failure Isn’t Failing

You’re not expected to fix everything. Some projects are destined to fail.

You are expected to handle them properly.

If you inherit a broken task, your job isn’t to rescue it overnight. Your job is to work through the process to a clear decision point.

That looks like:

• Leaving a clear record others can build on
• Identifying inputs from others and tracking delivery, especially when they become roadblocks
• Communicating issues early, not hiding them
• Following process, even when others don’t

That’s how trust is built.

That’s how careers are made in messy environments.

Process Is the Real Win

In engineering, process is not bureaucracy. It’s protection.

• It keeps people safe
• It prevents repeat failures
• It allows large teams to coordinate over time

Even when the outcome is uncertain, process gives you structure:

• Procedures protect the site
• Documentation protects the team
• Objectivity protects your reputation

If the job fails but your process was solid, people notice.

If the job succeeds but your process was poor, that catches up with you later.

Practical Takeaways

• Define the scope before you start. If it’s unclear, write down your assumptions
• Write as you go. Don’t rely on memory or try to reconstruct later
• Track inputs from others and make roadblocks visible
• Raise roadblocks early. Don’t sit on problems hoping they resolve themselves
• Separate facts from opinions in your communication
• Follow the procedure, even when it feels slow
• Close the loop on tasks. Don’t leave things half-finished
• Prioritise learning as an outcome, especially when the result is uncertain

Reflection Prompts

• What exactly is in my control on this task?
• If this fails, will my process hold up under scrutiny?
• Have I made my assumptions and limitations clear?
• Who am I waiting on, and have I made that visible?
• If someone else takes this over, will they understand where it’s at?

Final Thought

You won’t always get a clean task.

Some jobs are unclear from the start. Some are constrained. Some are already heading in the wrong direction.

That’s not your responsibility.

What is your responsibility is how you handle it.

Stay structured. Stay objective. Follow the process.

Because in the long run, people don’t remember whether a single task succeeded or failed.

They remember how you worked.