In case, if you haven’t really been following my blog, I generally tend to write about tech, games, some personal thoughts, some thoughts about my work at 13 Llama and some analytics.
What I do not write about is Design … be it any design. Systems design, Visual Design, Brand Design … even solutions design. I know for certain that I have a certain unhealthy fear for engaging with design. So much so that it has now become a mental barrier in my head. Staying away from creativity isn’t necessarily bad, since we do a lot of analytical and logical work. Having said that, breaking down problems into smaller byte sized tasks is now a child’s play and there has become a comfort zone. So much so, that over the past few months I had started to think that we should focus on driving more business in these areas.
What does one do when one doesn’t have an option?
Of late though, some of the mandates we have been getting involved us having to work with and also having to define the design specifications. Some of our new team members were pretty gung-ho about working on design specifications instead of a pure play numbers game.
To add to that, at pretty much the same time, we had a couple of our main clients request that we get involved at a higher level and help guide the marketing briefs.
We could have chosen to keep focused on the analytics niche and not step up to the mantle. However, we decided to step out of our comfort zone and things have been taking an interesting turn.
Stepping out of comfort zones
This often involves stepping into a chaotic situation, spending some time taking stock and then working on multiple fronts and more often than not in an iterative manner. From an engagement point of view, it takes a special sort of client to work with. An organization which understands that is an organization that is also in a sense working out of its comfort zone.
This also means that the team which is actively engaged in stepping out of its comfort zone is very very focused on the purpose at hand.
Instead of worrying about things such as appraisals, office times, leaves and petty office politics, the team is then focused on doing what it takes to get the job done. The line of comfort just disappears and shit gets done.
Organizations and comfort zones
For a lot of organizations, functional teams end up becoming comfort zones. An example of this is when there are functional silos in a firm and cross functional exchanges do not happen as smoothly as expected. This is when both the functions engaging are not stepping out of their zone of comfort. Unfortunately, we have all experienced the adverse effects when customer facing teams do not step out of their comfort zone.
This severely impacts their ability and sometimes even the intent to engage. Symptoms of this condition are cases where the customer facing teams cite company policies, or often play the victim, or end up misinforming or lying to the customer. This builds a trust deficit within and with-out the system.
What can organizations do?
Foster a culture of experimentation and over delivering value. Sometimes force teams to work outside the zone of comfort. Align teams to the grandiose scheme of things and how their mundane job is in fact a purpose centric activity and not a functional silo.
As a concluding note, assuming people are willing to often step out of their comfort zones is such a positive mindset that the rewards of the mindset alone are worth the efforts of stretching one’s boundaries. Over the past few months, I have seen my fledgling team work outside their comfort zones, get over their initial mental barriers and come out for the better. The decision to step out of my own comfort zones has been definitely worth it!
