Transparency in Development

Nowadays, we're doing a lot of talent-finding for our clients in support of their initiatives. I'm sure everyone can attest to the fact that finding high-caliber tech talent (developers, technical project managers, UI / UX designers) is no walk in the park.

For a long time, we've worked to find and hire talent that's a good "culture fit" for both ourselves and our clients. Over the years, several things have become apparent to us (nine things actually - each of which merit their own post), but the one I've most recently, and perhaps most intensely been thinking about is "transparency."

One of our core tenets at Chairseven is something we call the Transparency Imperative. At its core, the Transparency Imperative is simply a rule that says: "I will communicate my status clearly and involve the rest of the team."

So many times I have heard others complain about a lack of 'transparency' in technical projects. Team members "protecting their turf" or being elusive about where they really stand on a task because of some irrational fear. I posit that all strife can be avoided if we simply, and transparently, communicate with one another.

We've found (particularly in larger, non-technical organizations) that software projects typically seem 'scary' and that software and IT teams have a tendency to not communicate well with non-technical staff (and vice-versa). In an age where software has been commoditized, why is the process of building it, and the process of working with those doing the development still seemingly shrouded in mystery (in many cases)?

As you search for new members of your team, it's hugely important that team members have the heart of a teacher. They should be able to communicate in the real world, and with language that everyone can understand -- to build products that everyone wants to use! Having a culture of transparency means that not only can the business team have a clear picture on where new (or changes to existing) products stand, but business leaders can help technical teams understand why deadlines and certain features are important.

Make sure to spend the time finding people who actually have an interest in working with your team; those who are are capable of acting as a great team member, who can be clear and concise, and who you'll be excited to be around. These skills FAR outweigh which version of a technology they have experience with.

Be transparent and be successful.