5 Reasons Solution Architects Fail

1. Define the Problem

Start by asking yourself these questions…

• What is the problem that needs to be solved?

• What are the details necessary to solve this issue?

• What options are available now?

a. Defining the problem is the first step in the process to a successful project outcome. This first step alone sets up the myriad of questions, priorities and skills that will be used for a solution. For example: Is the problem local (one department) or global (organization wide).

b. How important is the problem? Will it affect revenue if not resolved? There may not be a direct correlation to revenue (saving employee time can be a byproduct to decrease expenses instead of directly raising revenue).

c. How far reaching is the problem? Most systems that a company has are purpose built to solve and deal with individual areas but are not cross functional. As noted above if the problem is not a local one, data may be required from somewhere else.

d. Is the problem the cause or the effect? In the standard flow of business is this problem at the beginning of the process, preventing others from accessing the information they need to be effective. This problem could also be the result of poor data, slow data or no access to data from other processes preventing the efficient incorporation of the information where a decision is required.

e. Is there a current solution that is used today for this problem? Are people taking things offline to do their work. Is data consistency an issue? Is the current process creating more work which is what is highlighting this problem,

f. In assessing the problem, look for the root cause of the issue and not symptoms. Planning to address just the symptoms will become far more expensive instead of addressing the root cause. As difficult as it can be, getting others to acknowledge the actual problem may take time and effort. For example: Building a system that will track sales through to shipment is not effective when the sales people will not put in their orders.

g. Another example of this is when information is entered multiple times by a single or multiple individuals into each system. Sometimes additional data is required which is not kept in one system but 70% of the information is duplicated by reentering. The process should be reviewed as this creates a large expense and is prone to error. It is not the root of the problem but it is a byproduct of it.

h. Additional examples are when there is no true Single Source of Truth. Data Management is a place to start to look for the root of problems. In many cases because each system store pieces of information the integrity of data is compromised when there is no core system and each of the cascading systems is allowed updates without informing or updating the system of origination.

i. The Solution Architect (SA) needs information on the complete Business Process in order to grasp the full scope of the issue. The proverbial blind people touching the elephant comes to mind when true perspective is not gained. Most times the SA is told not to worry we have accounted for the sections that you do not see, however, this comes back on the SA.

j. The SA needs information on a large variety of information as this effects issues associated with the problem. For example: if the plan for size of the data is 100 and then a decision is made to roll this out for 1000 then a cascade of the problem exists due to lack of resources to handle the 1000 that was not planned.

2. Devil is in the Details — (Don’t Get Crushed by Detail —Why are we addressing this problem now? Why are we using this technology to address the issue? Why are we doing it this way (vs other options?)

3.Take Action NOW — (When is this required to rollout? Must complete solution be implemented at the same time?)

4. Be Process Centric — (Where in process should the solution fit? Who is involved in this process? Is there a need for data integrity and/or approval?

5. Measure your Success — (How will it be known the solution is a success? Report? Data Requirements and where needed and used? What decisions will be made from solution?)