4 Ways Companies Sabotage Their Developers (and themselves)

sabotageHiring and contracting developers is essential for every company in the mobile app world. But how many of these companies are dooming their projects (and their developers) before they even get started? Perhaps more than you think.

The success of a mobile app hinges upon the combination of quality development and vision of the designers. If your search for the correct developer is rushed and not well planned out, you will almost certainly receive a product different than what you were aiming for.

Take a look at this article about the 8 details to include in a job brief, and see how many you included (and did so thoroughly) the last time you posted a job brief. If you find that you may have done a less than stellar job, you are not alone. Here are four major mistakes that companies often make, unintentionally shooting themselves in the foot:

  • Ignoring your background – This can go two ways. If you or someone at the company has a technical background, describe it in the brief. Developers will be excited to work with someone that better understands what their work will entail. Don’t fret if you don’t have a tech background, just be more flexible and open minded in your goals. Remember you are hiring a developer for their expertise, so heed their input.
  • Vague or rushed briefs – This goes for all the suggestions listed in the above article. Even if you touch upon each, vague or unclear briefs will leave developers with a fuzzy picture of what they need to accomplish. Even the best developers will struggle when they are forced to “figure out” what the company wants.

  • Not Segregating features – As the article stated, listing and segregating the features into must-haves and nice-to-haves will be extremely helpful. Not only will this allow developers to better estimate time and cost, it will also keep you more in control of how the app turns out. As time runs short, without a prioritized list, developers will be forced to decide themselves which features make it into the first version.
  • Failing to investigate additional areas of assistance – This is probably the most overlooked. If you ask for assistance in other areas related to your app, it can provide two things. First, thanks to networking, the developer may be able to point you in the right direction of people they know do quality work. Secondly, if a developer is enthusiastic about helping outside the realm of developing, you know they are dedicated to making your app successful.

Much like most contracting work, developing a mobile app can be difficult because you will likely have something in mind different than those with whom you choose to work with. Making sure both sides of the project are on the same page throughout the process will help ensure that your company is not one that sabotages itself in the app development process, and guarantee that your company is receiving the best possible product!

Do you find yourself falling short on any of these suggestions for creating briefs? What ways are you setting up your developers (and therefore your apps) for success? Make sure to let us know in the comments!


Leave a Reply

Your email address will not be published. Required fields are marked *