Here are some tips to keep in mind before you start on a development project:
1. Explore your dream product. The first step to take before starting the design process is to create an outline of exactly what you want the software to do. How do each of the parts relate to the others? How does the system interact with the other systems you’re using? Where can you automate procedures? How can you ensure that there are no gaps for something to be missed?
In the exploration stage, leave nothing unexplored – the more you explore in this stage, the fewer problems you’ll have later. It may be helpful to draw a workflow map so you can visually see how everything in the system flows.
2. Involve your team. Talk to the department managers and leaders. Talk to users. Find out their frustrations and get their insights into this project. In order for the project to be successful, you need the support of everyone involved. And they’re also likely to have helpful points that you wouldn’t have thought of that should be incorporated into the project.
As I work with my clients, I find that the users have a lot to say about what will make the system successful for them. And it really all depends on the users – if they won’t use the new system, or it’s difficult for them to interact with it, the system will not be successful. And that’s definitely not what you want.
3. Find the right developer. This is not the right place to save money. Your system is an investment for your company’s future. You want a developer – whether external or on staff – to have the right experience and tools to get the job done professionally and in a timely fashion. You want someone who understands your goals, the ideal user experience, and someone who can adapt their style to work best with the unique dynamics of you team.
Only use someone who speaks your language well. Language is important – you will need to communicate frequently and accurately. I have not seen any client yet that had a good experience working with a developer that spoke a different language.
4. Share your goals. Make sure the entire team working on the project (and especially the developers!) share a mutual understanding of the goals of the system and how it will benefit the company. When the objective is understood by everyone involved, your entire team will be committed to creating a quality system.
5. Test, test, test. Ideally, the developer will do thorough quality assurance (don’t hire them if they won’t – development time will be double what they quote if they’re not including a testing phase). It’s your responsibility to make sure that the system is tested completely before you implement it throughout your company. Once it’s launched, your users will expect perfection. If they experience problems in their initial use of the system, the credibility of the system will be destroyed, even if the problems are fixed later.