Back To Basics: Deep Dive Part 6
Software Analysis: What are you building on – Part 2
The main role of the analyst is to design the changed business process and the system that goes with it in order to solve a business problem or achieve a goal.
So, how can you even start doing this if you do not fundamentally understand your customer’s existing systems and tech landscape?
"If you don’t know where you are, a map won’t help." – Watts Humphrey
A. Understand Key Applications
This is a hard one, because it can take a considerable amount of time to understand the existing key applications.
However, failing to understand this will be a critical mistake. It is wise to expand the team with key people who truly understand the specific key systems by heart. Trying to do this alone will drown you.
People’s existing skill set
The existing people in an organisation and their respective skill sets play a critical role in determining the solutions and subsequent impact thereof.
In creating new solutions and processes, there’s always a change management component (different subject all together). However, pointing out the impact of the new solution on people is critical, and it’s the responsibility of the software analyst. People may need to be reskilled, training and onboarding can be complex and possibly require in-person sessions. Additionally, some jobs might become redundant (one of those unfortunate things that often happen with new systems efficiency and technological enhancement.)
Draw existing system process
Drawing process diagrams of the existing system processes is really very helpful to ensure you understand and confirm the starting point. This level of detail will facilitate an understanding of who is involved and what their roles are. If done accurately, it quickly highlights pain points such as inefficiencies, delays, or errors. Additionally, discussions with users about the actual process flow can identify areas for improvement.
Understand user’s jobs on systems
Including the user’s level or skill in the system’s process flow is an important foundation. This becomes a critical input for the change management and training team.
What happen outside systems
This is often what needs to change. You must understand if users understand how the system works (for example, a calculation on excel by manually entering system data and using that calc for certain process decisions).
Not understanding this will create a HUGE GAP in your work that will be revealed during training if users ask questions about how certain things will now work.
B. Hurdle: For the not so technical analyst
I call this a hurdle, because the not so technical will tend to brush this principle aside as not really their job and disagree with me here.
My point is, these matters are so critical to the end solution, to ignore this will cause an analyst to design something of little value because it is totally out of touch with reality.
If you are not very technically inclined, pull in the technical experts. We all have limits to our skills and knowledge. So, pull in the architects, senior developers, super users, system analyst and DBA.
C. The data can’t lie
Herein lies a significant truth. One of the best ways to understand existing applications/system/user landscape and flows is to understand the data and flow of data.
The data cannot lie. It’s black and white. The state of the data also reveals a lot about the existing system and the people process behind it.
It is wise to look at the data as you work your way through the existing process. Again, don’t be shy to get help – you may be SQL proficient, but may lack the time to do so. It takes time to analyse data properly.
Brand new systems projects (called greenfield projects) are few and far between. Even they are build on some other existing business process. For many analysts, this will require a mindset change. Without understanding this, it is like building a house on shaky or non-existent foundation – you do not know what you are building on.
You can download the whitepaper from https://jalia.co.za/services/
Author: Henk Maritz (jalia.co.za)
© 2025 Jalia Technologies (Pty) Ltd – jalia.co.za. All rights reserved.
No part of this publication may be copied or used in any form without prior written permission from the author.