Positioning Yourself to Coworkers as a Stealth Consultant
In a nod to yesterday’s announcement, I’m going to demonstrate how just unaltered the DaedTech blog might be, content-wise. To wit, here’s a both that qualifies in both my reader questions series and my “developer to consultant” series. This makes sense, since it’s a question about the developer to consultant series.
Today I’ll talk about positioning yourself as if you were an independent consultant, but with the caveat that you’re trying this out on your coworkers.
Positioning Revisited, But Internal to a Company
When it comes to posting on this blog, I love not having to make the caveat that my opinions aren’t my employer’s, or whatever. The more used to that I’ve become over the years, the fewer punches I’ve bothered to pull. And so it went with my first developer to consultant post. In that post, I unapologetic declared that every developer should become a consultant.
If I were writing a book, that post would have been the prologue. Chapter one, then, would have been this post about positioning. It’s a long read, but I recommend it for understanding the nuance of positioning. At the 10,000 foot-iest of 10,000 foot views, your positioning is your plan to ace the question, “why should I hire you, specifically?”
The reader question came in the comments of that post. And here it is.
For an employed software engineer, what are some of the ways to “signal” your positioning strategy? In other words, how do you let the org/team/manager know what your unique value prop is? I’d love to get your thoughts on this.
This is an interesting thought exercise, because to participate in the standard hiring process is to have the worst possible positioning strategy. When you do this, you’re saying, “I’m slightly better than dozens of otherwise interchangeable resources whose resumes you’re holding, so hire me.” To have a good positioning statement as a consultant is to say “I’m the only person that can deliver X for you in exactly the way you need.”
So today’s topic is about how to develop the latter flavor of positioning strategy in the former world. But who am I to shy away from nuanced topics?