Ten Habits That Make You Worth Keeping

Over the years I have onboarded a lot of people, and the ones who stand out are rarely the ones with the flashiest résumé. They are the ones who are easy to rely on. Here is the advice I find myself giving over and over, distilled into ten habits. It grew out of consulting, but none of it is specific to that; it applies to just about any professional.

1. Set expectations

Most friction on a project comes from unspoken assumptions about who is doing what and when. Ask when something is due, provide an estimate for when you will finish it, and when you hand work to someone else, assign it to a specific person with a specific date. Tasks assigned to a group are tasks assigned to no one. Good fences make good neighbors, so ask for the scope document, the project plan, and the timeline rather than guessing.

2. Meet expectations

Setting a date only matters if you hit it, and if you are going to miss it, the time to say so is early. Raise the issue well before the task is due, and keep your tracking up to date so anyone can see progress without asking. Five o'clock on the day something is due is not the moment to tell a project manager it will not be done.

3. Pay attention to the small things

The unglamorous habits are what build trust. Submit your status report every week even when nobody asks for it, enter your timecard and expenses on time, and keep your task tracker current. These take minutes and they are the difference between someone who has to be chased and someone who does not.

4. Treat email as a professional skill

Proofread before you send. Use the subject line to say what the message is actually about, and use the To and Cc fields for their intended purpose so people know whether they need to act or just stay informed. Set up a signature with your cell number, address the message to the right audience, and make any action items and follow-ups unmistakably clear.

5. Ask for help the right way

Your time is always more valuable to you than mine is, so learn when to ask and when to search for the answer first. When you do ask, remember that the person helping you has not been staring at your screen for the last half hour. Bring three things every time: the steps to reproduce the issue, including URLs, usernames, and navigation; what you actually saw, whether that is an error message or a blank page; and what you expected instead, with a sentence on why.

6. Use the right tool for the job

Email is for documented communication several people need to see. SharePoint is your document repository with version control, so save the file there and send a link instead of an attachment. Jira is for tracking tasks, not your inbox. Teams messages are for quick one-off questions, and a text or a call is for something genuinely urgent that needs an answer now. Matching the tool to the message saves everyone time.

7. Never try to solve a huge problem

Break a big problem into smaller ones and isolate the piece that is failing. If a web service call is not working, confirm you can do the same thing in the application first. Never assume the inputs are what you think they are, so when you run code against a new file, check that the file meets the same criteria as the last one. Always double-check that you are actually seeing what you expect to see.

8. Ask why

Understand and question why you are doing something rather than working on autopilot. If you copy a block of code, break it down and understand it instead of blindly reusing it. If you start from a template, learn why each section is there so you can drop the parts that do not apply. Curiosity here pays off for years.

9. Work with balanced urgency

Do not put something off just because it is not due today, but do not rush it either. Getting it done right comes first, and getting it done quickly comes second. Make sure deliverables are polished and the work is tested, and balance a realistic timeframe against the ideal solution. Something reusable deserves to be elegant, while a one-off you will throw away can be brute force.

10. Own the outcome

Underneath all of these is one idea: be the person who owns the result. When you set and meet expectations, sweat the details, communicate clearly, and deliver polished work, people stop worrying about your part of the project. That reputation is the most valuable thing you can build, and it is entirely within your control.