You've just developed the best looking application - great graphics, informative and easy to use. The database is well designed, performs beautifully and is dynamically driving the system. Unfortunately, the boss just came by and stated that the company doesn't work that way. We do X not Y, steps 1, 2 and 3 are after 4, 5 and 6 but before 10, 11, and 23 while step 13 is actually handled by an outside source and the whole section Z is useless. So much for the six month effort you just put in.

​

It's not glamorous and it can be annoying, but you must perform business analysis before you begin designing and coding. You have to understand what the business needs are, where the pain of doing business is and what are the desires of the business. Three different goals with three different outcomes. Successful business analysis involves performing and documenting all three analysis areas and then prioritizing according to a few simple dimensions. Once this phase of the analysis is complete, you can begin documenting Workflow and Dataflow in the company as it currently operates and how this can change with the implementation of the new system. The only way you get all this information is by asking questions... lots of questions. That's the annoying part. Your business probably hasn't had this type of in-depth analysis performed before so you will have to go through this process to ensure you get what you need / desire and solve the areas of pain.

​

Data Futures has been doing just this type of analysis since 1995 for businesses big and small, international and local. Let Data Futures help you give your project a better chance for success by creating your "road map" through our expert business analysis... it will save you time, money and frustration.