We’ve all been there
Everyone, at some point in time, has been in that spot. For whatever reason we’re stuck doing something that pushes us and we need help. Generally this means we don’t know underlying concepts or ideas that are critical to success, or are unaware of how tools work. Some common examples include:
Being asked to perform data analysis
Managing a system or tech
Developing / maintaining a process
On the whole we are very intelligent and skilled at what we do. The problems crop up when we’re asked to do work outside our normal wheelhouse. It may be presented as a stretch goal, or an opportunity to grow, but frequently we are left in a bit of a lurch since our background and expertise is in other areas (imagine a software engineer being told to manage a help desk, or an HR specialist being told to develop analytics).
On the plus side, we are (generally) very smart and talented. On the down side we’ve got basically no idea what we’re doing. This is where connections between technical and non-technical teams is critical.
These connections form several ways, but in general I find they are either organic or prompted.
Organic Connections
Eventually we end up bumping into someone who knows more about what we’re trying to do. This might take the form of a content strategist commenting on posts, or a database engineer asking why queries are written the way the are. In some very lucky instances we can reach out for help proactively, but generally we have to get lucky….
How this connection forms is critical, as it dictates how the relationship, and end product, will unfold. Generally it goes one of three ways:
The expert reacts negatively - demanding to know why it was done this way, or why a specific process wasn’t followed
The expert reacts neutrally - either not showing much interest, or just fixing the problem, without connecting with the individual doing the work
The expert reacts positively - attempts to establish a relationship and help grow the individual with the work
Most commonly I see the neutral reaction occur. While this may be seen as a positive thing since it results in a good (or . acceptable) outcome, it doesn’t really serve anyone. It robs t he individual doing the work of the opportunity to improve by learning the proper way, and it robs the expert of the opportunity to educate their partners.
Fortunately I don’t see the first very often. I imagine this only really happens in highly controlled environments, or when someone is having a bad day.
Almost as uncommon though, is the third, which strikes me as very interesting since it is by far the most beneficial to everyone. Not only will the expert help solve a problem more quickly, they will also better understand their partners needs allowing them to head off future potential problems. The individual needing to do the work also gains a valuable contact, and likely learns a little bit more about how everything works.
Prompted Connections
While organic connects crop up when we basically randomly bump into an expert, prompted connections connect when someone helps us get an introduction. This may take the form of a manager knowing who to talk to, a coworker having a friend in another department, or a process requiring submission of plans/questions. I personally find these connections to be a bit weaker than organic ones, mainly due to the more artificial aspect of them (e.g. Organic connections tend to arise around a shared challenge, whereas prompted feel more like a job requirement), but they are still incredibly valuable ways of connecting partners.
Regardless of how connections form, they are absolutely critical to everyones success; even aa one-person company needs them to survive. I do my best to build new connections, and enrich existing ons, every change I get. I find them rewarding both in terms of learning new things, but also in terms of getting to know the people around me. They not only make my job a bit easier, but a but more enjoyable since I’m meeting new people, and picking up new skills.