Dear tech companies and or employers,
If there is a will, there’s a way. Try remote work (distributed team). It is NOT a perfect means of working, however, offers more pros than cons.
Employees who can work productively remotely and or as part of a distributed team display high sense of discipline, as it requires a lot of personal composure to stick to one’s own routine.
It’s terribly easy going to work 8 to 5 each day, 5 days. Conforming to routines rigged for us is pretty easy to stick to. However, for one to stick to their own routine, yet be a productive developer is as equally valuable teammate.
‘We don’t have provision for remote work’
You don’t need to figure out the a-z of supporting distributed/remote developers to start doing remote.
Start with one or two teammates. It could be part time. Refine how the process and productivity pipeline works for your use cases.
Do not create the impression ‘remote workers’ are “enjoying” than their 8-5 colleagues. Such comparison only spurs jealousy, and diminishes the potential of the in-office team mates.
As a matter of fact, not all roles of a company can be remote. But the ones that can offer the option of remote work, can you give it a try?
As in any new adventures, test the waters. Start slow. Refine what you learn. Improve. Think outside the box.
Unless micro-management is the thing the company enjoys more, otherwise focusing on milestones, targets, deadlines, sprint targets and productivity is paramount.
Unless looking at the face of the in-office 8 am to 5 pm developers makes money for the business, trying distributed team offers benefits hardly known unless tried.
Again, remote work isn’t a perfect form. A mixture is best. However, tech companies in Ghana treating their tech/developers like bank cashiers, in many cases, cripple their possible full potential.
Exclusive: Google asked 5,600 employees about remote work. This is what they learned
Working together when we’re not together
Thank you.
