Focus On the What, Not the How
Friday, September 23rd, 2011OBSERVATION
More often than not, when I begin systems analysis for new custom development project clients, they have already decided on technology platforms (and in many cases already acquired them), created detailed screen designs, and created database elements before consulting a systems analyst from a software development firm.
Their intentions are well-founded–that they want to get started right away when they find a developer.
However, going through this process with a developer rather than alone has great value. Seasoned systems analysts and developers have been through projects, so they know what details will suit you best in terms of tech platforms, dev languages, hardware, and design. Even if you yourself are strong in I.T., just beware–custom development projects are their own animal, and they can become a loss to your organization if you start off in a wrong direction.
ISSUES CAUSED BY FOCUSING ON THE HOW
Misplaced confidence in you as the manager–if you present a developer with purchased hardware, a decided systems stack, and a plan, they are likely to take it and move forward with complete confidence that you know what you’re talking about–you’re the boss. Beware–you’ve relieved them from a huge service you should probably be demanding–consulting and advice. If you’ve truly made the wrong choices for your project’s needs, it will wind up being at your expense.
Ignoring valuable experience–you may have some strong knowledge; perhaps you’ve even worked in the area of technology before and have a good feel for it. Don’t let that lead you into thinking that you can effectively micro-manage a seasoned vendor who does custom development for a living. They likely have a more mature or proven way to solve various things you’ve been trying to design a solution for that could save cost in the long run. It may not fit the picture you had in mind or follow the same path you imagined. Remember–development peoples’ personalities tend to be such that they will only push back so much–so they will likely give in to your way, so if it’s wrong–it will cost you.
FOCUSING ON THE WHAT
In custom software development from the ground up, a development vendor is most effective when presented with a detailed and prioritized list of requirements–what is this system supposed to do? Who will it serve, and why? Which requirements are the most critical to the business?
A seasoned software vendor will have a process for requirements-gathering during systems analysis. Staying focused during this phase of the project, and “worrying about the what and not the how” will result in your project’s best chances for long-term success.
