What a useful software assessment should produce

Begin with the material that already exists

Software, spreadsheets, forms, reports and support issues often contain the starting point for an assessment. Reviewing them first makes conversations more specific and avoids asking people to reconstruct the whole business from memory.

Follow a representative workflow

Choose a real example and trace the decisions, information and handoffs it requires. Ask the people involved about exceptions and the work they perform outside the official process.

Separate observations from assumptions

Document what the evidence shows and what still needs confirmation. A suspected bottleneck is a question to investigate, not yet a measured business loss.

Produce a recommendation

Explain the practical options and trade-offs. The recommendation may involve a process change, an integration, improvements to existing software or a new system. Include the dependencies and unknowns that affect delivery.

End with a usable next step

The output should help someone make a decision: a defined scope, further technical investigation, a prototype or a decision to leave part of the current setup in place. Agree the depth of the assessment before it begins.

Bring existing evidence into the review

Gather the material that already describes the operation: forms, reports, process notes, screen recordings, support issues and representative records. Include the current software and the tools used around it. The review should build on this material before asking people to repeat it in workshops.

Follow a small number of important scenarios from beginning to end. Record differences between the documented process and the actual work, and ask why those differences exist.

Separate observations from recommendations

Keep a clear distinction between a confirmed limitation, an assumption that still needs investigation and a proposed change. Attach evidence to the important findings so that the business can assess the recommendation.

A recommendation should connect a problem to an option, its expected effect, dependencies and main risks. Sometimes the practical next step is to clarify a rule or improve an integration rather than start a new application.

Finish with a decision-ready scope

The output should help the business choose its next investment. It can include a workflow map, a prioritized problem list, an outline of the options and an initial delivery scope with assumptions.

Agree which questions remain open and who can answer them. If a cost or timeline depends on an unknown integration or data condition, state that dependency directly and propose how to investigate it. Review the plan when new evidence changes a material assumption.

Explore the next step with Perspective Unity.