GISCH CONSULTING

Systems

When we ask about a system, we mean more than the software. There may be a spreadsheet people trust, a paper form that travels with a job, or someone who knows which details need checking before information goes to accounts. We look at how all of that works together before discussing what to change.

Where the information goes

A detail entered when a job is quoted may be used much later by someone planning the work or preparing an invoice. Along the way, it may be copied, renamed or combined with something else. Understanding that journey helps us see why a report is hard to assemble or why an apparently small change affects another team.

Two reports can also be answering different questions. One might describe work planned for a project; another might show what has been invoiced. Before connecting them, we need to know what the people reading them expect the figures to mean.

When the software sees the job differently

An example from Anita's research involved budgets arranged as a matrix. The teams needed to see internal fees, contractors and other costs within each project phase. The software held tasks and costs in separate flat lists, so people had to reconstruct the phase view outside it. They understood how to use the software. Its way of organising the information did not match the view they needed.

That is the sort of detail we look at when assessing a product. A feature called project budgeting may work quite differently from the budget a team already uses. Working through an actual example makes the difference easier to discuss.

Sometimes the existing product can support the work with a change to its setup or the way it is used. Where another product is needed, we can work through selection and implementation, including data migration and connections to other systems.

Working in live systems

We start with read-only access when assessing an existing system. Before changing live records, we show what is proposed and ask for explicit approval. Test data lets us try things without treating a client's working records as an experiment.

Why systems come third

There is usually a reason someone wants to change a system. We want to understand that reason, including what other people depend on, before making a product choice. The work may take us into process design or a business decision as well as software.

Anita's PhD examines Australian small businesses adopting cloud technology. The thesis was completed at the University of Technology Sydney in 2024 and is available through UTS OPUS.

Systems: selection, implementation and integration | Gisch Consulting