I’m not sure if you know this or not, but the chances are good that Technical Implementer that you rely on to do most of the technical stuff for your business hates your guts (even if you are that person for your business).
Don’t get me wrong, your Technical Implementer probably enjoys doing the actual work and is grateful for the opportunity to work for the company, but the frustration can be overwhelming.
To be fair, they don’t actually hate YOU. They hate the way you DO things.
Let me be a little more clear, the way that you work is driving your technical people insane. Why? Because you don’t know what you want and most of the time they end up feeling like Ryan Gosling in ‘The Notebook’.
It happens every day in millions of places across the planet. Boss person tells the technical person to do something. The technical person does that thing. Boss person doesn’t like it. Boss person tells a technical person to do it differently. Technical person does it differently. Boss person doesn’t like it. Rinse and repeat until results are satisfactory.
As people, the most valuable resource we have is our time. The process I’ve just described has probably stolen more of that valuable resource than any other 1 activity from small businesses.
So how do we break the cycle? The answer is three-fold:
- Know What You Want – I’m talking to you entrepreneur/boss person. Your ability to lead a team and to create things is directly tied to your ability to truly know what you want. Don’t have a general idea. Don’t think that you’ll just know it when you see it. Know it. Period.
- Have a Shared Language – When you know what you want, you have to make sure that you and your team can talk about that thing without confusion. This may seem like overkill, but trust me when I say that what you say isn’t always what gets heard. Spend the time to make sure that you and your team are all speaking the same language.
- Have a Process for Implementation – This is where your implementer needs to make sure that they have a standardized method for executing on the thing that you want (using that shared language). It doesn’t serve you, the company, or the implementer to be executing on your ideas in a different or unique way each time. When they have a process for implementation, you can know what to expect.
The above steps may seem like an over-simplification. We’ve worked with 1,000s of small businesses. Trust us when we say that this is crucial to your success.
If you are interested in learning more about how to put these into practice, we’ve created a free training handbook where we cover the key elements in making your business more predictable.
Do you have a great example of a time when this happened with you and your implementer? Let us know in the comments!