I’ve always been one of those people who can figure out how to do a lot of things. Give me a new piece of software, an unfamiliar document, a messy project, or a problem nobody quite knows what to do with, and there’s a pretty good chance I’ll start poking around until I understand it. Over more than twenty years of working for myself, that has been useful. I write and edit, manage projects and documents, organize information, research, build processes, pull apart requirements, put together proposals, and create a perfectly respectable graphic when I need one.
The catch is that being able to do something doesn’t necessarily mean I’m the best person to do it every time.
That sounds obvious until you’re in the middle of a project with a deadline coming at you. If you already know how to do something, doing it yourself can seem faster than explaining it, handing it over, or admitting that somebody else might do it better. Sometimes you really are the right person for the job. Other times, “I can do this” is not nearly as useful a question as “Who can do this best, and what does the project actually need?”
I’ve created plenty of graphics over the years. I can take a complicated idea, figure out what belongs on the page, and turn it into something clear and useful. I’m good at that part. Then I hand the graphic to someone who actually specializes in graphics and get reminded why that person is the specialist. They see spacing, balance, hierarchy, and visual possibilities I don’t. What I created may already have told the right story, but they can make that story easier to see and make the whole thing look considerably better while they’re at it.
That doesn’t make my original work bad. It means someone else can make it better.
Being Good at Something Isn’t the Same as Being the Best Person for It
I think this is one of the quieter lessons of professional life. There’s what you can do, what you do well, what you genuinely excel at, and what somebody else can do better or faster. Those categories overlap, but they aren’t identical.
Knowing the difference can save an astonishing amount of time. I could spend hours trying to take something from good to great because I know enough to keep fiddling with it. Or I can recognize that another person has deeper expertise and can get it there in a fraction of the time. If the goal is strong work rather than proving how many things I can personally accomplish, that’s a pretty easy decision.
Being responsible for the final result doesn’t change that. In fact, I think it makes the distinction more important. If I’m responsible for bringing an entire project together, my job isn’t to demonstrate that I could theoretically perform every task inside it. My job is to make sure the pieces work together and support whatever we’re trying to accomplish.
That means I need to know enough about the whole to recognize when something is missing, when two pieces contradict each other, when the story has wandered off course, or when a perfectly good individual contribution doesn’t quite fit what the larger project needs. It also means I need to know when to get out of somebody else’s way. As corny as the old saying may be, “teamwork makes the dream work” really does apply sometimes.
There’s a Reason We Work with SMEs
A proposal manager doesn’t need to know more about engineering than the engineers. An editor doesn’t need to know more about a technical subject than the person who has spent a career studying it. At the same time, the engineer may not see that his perfectly accurate three-page explanation has to become half a page or a single paragraph. And the subject-matter expert may not notice that a reader outside the field is going to get lost somewhere between the opening line and the final paragraph.
Everybody brings a different kind of expertise to the work, and the finished product usually gets better when we remember that.
This is also where knowing your own soft spots becomes useful. We all have them. Maybe you tend to skim administrative details because the interesting work is calling your name. Perhaps you trust your memory a little too much. You can be excellent at seeing the big picture and still occasionally get bitten in the butt by one tiny detail. And, of course, the old editing adage to “kill your darlings” applies when you become so attached to a good sentence that you stop noticing the paragraph around it isn’t doing its job.
Experience doesn’t make those things magically disappear. What it can give you is enough self-awareness to know where another set of eyes might help, where you need to slow down, and where your own confidence may be getting a little too comfortable. There’s a big difference between saying, “I’m terrible at this,” and recognizing, “I can do this perfectly well, but someone else can do it better.”
When Expertise Meets the Reality of the Project
The harder version of this happens when you really are the expert. You ARE the SME who was brought in to do something because it’s your strong suit. You know what you’re doing, you know how to make strong recommendations, and you can explain exactly why you think one approach is the right one. Then the project reminds you that expertise isn’t the only thing in the room.
There may be a budget you can’t change, a deadline nobody is moving, a page limit that doesn’t care how much useful information you have, or a requirement that takes up space you would rather use somewhere else. A client may want to see something presented in a particular way because that’s what matters to them. Another person involved in the project may know something about the customer, audience, history, or decision-making process that changes what the strongest answer looks like.
None of those things make your expertise less valuable. They simply mean the technically best answer in isolation may not be the best answer for this particular project.
That distinction shows up constantly in writing and consulting work. I may think a section needs more explanation, but the document has a hard page limit. I may prefer one structure, but the client wants to see the information another way. I may know exactly how I would approach something if I were making every decision myself, but I’m not always making every decision myself. Sometimes the work has to fit a larger story, a tighter constraint, or a decision someone else ultimately gets to make.
The Point is to Know Your Lane
My responsibility in those moments is still to bring what I know to the table. If I see a problem, I need to say so. If I think a different approach would be stronger, I should explain why. There’s no point in hiring someone for her expertise and then expecting her to simply agree with whatever is already on the page. But offering expertise and having final authority aren’t the same thing, and neither one means working in a vacuum.
Knowing your lane means understanding what you’re there to contribute and recognizing what other people are there to contribute as well. Sometimes that means leading with your expertise. Other times it means listening because someone else knows more about a particular part of the work. And often it means stepping back far enough to see how all of those pieces fit together. The point isn’t to guard your territory. It’s to understand where your judgment is most useful and where someone else’s experience, perspective, or authority needs to shape the work.
That’s part of working with other people, and it’s where that aforementioned teamwork matters. Strong projects are rarely the result of one person having all the answers. They get stronger when people bring what they know, pay attention to what others know, and keep the larger goal in view. Knowing your lane is really about understanding how your contribution fits into the work as a whole.
Good Work Usually Takes More Than One Kind of Expertise
Most of the projects I enjoy are complicated enough that no one person is going to see every angle or have the strongest answer to every part of them. That’s one of the things that makes the work interesting. A good team brings together people who notice different things, ask different questions, and bring different kinds of expertise to the table.
The best results usually come from knowing how those pieces fit together. One person may understand the technical details better than anyone else in the room. Another may see how those details need to be presented for the audience. Someone else may notice a gap, a contradiction, or a constraint that changes the direction entirely. The work gets stronger when everyone is able to contribute what they know without assuming that one kind of expertise should dominate every decision.
And perhaps that’s where knowing your lane becomes less about the boundaries of a job description and more about the work itself. What do I bring to this particular project? What does someone else bring that I don’t? And what does the work need from all of us to become as strong as it can be?
There are plenty of things I can do well. There are also plenty of times when someone else can make a piece stronger, faster, clearer, or simply better. And there will always be projects where the best answer has to balance expertise with deadlines, budgets, client preferences, page limits, and all the other realities that come with getting work out the door.
Being good at your work isn’t about proving you can do everything. It’s about knowing what you bring, knowing what the work needs, and helping those two things meet.