01–02 / Analysis and reorganisation
Analyse the process, then reorganise it.
I map out how an activity works: steps, people, tools and exceptions. Then I reorganise it. Often the first improvement needs no software: removing unnecessary steps, clarifying who does what, configuring existing tools better. Remotely or on site, anywhere in Italy.
01 / When it helps
When it can help.
The problem is clear, the cause is not
Delays, errors and constant chasing are visible, but the actual workflow does not match the documented procedure.
The work passes through too many tools
Email, PDFs, Excel and other applications require copying, checking and piecing information together, making the work hard to follow.
One step depends on a single person
Exceptions, criteria and important information live only in the memory of whoever runs the process day to day.
02 / See it working
Map out how requests from different channels are sorted.
Illustrative example · not a client case study
- ChannelsEmailWeb formPhone
- SortingBy hand, every morningUrgency: no shared ruleNo category: forwarded by hand
- AssignmentAlways the same personDepends on one person
- ReplyFrom the assigned owner
Reorganise before buildingCase: classify requests before assigning them
Sample
What arrivesFictional emails, forms and attachments, together with the rules described by the team.
Map and case
What it proposesA map of the steps and a defined case: classifying requests before they are assigned.
Validation
Who checksThe people who run the process validate categories, responsibilities and the points where judgement is needed.
Outside the rules
If something is offRequests of unclear urgency and those that fit no category are set aside, rather than forced into a rule.
- People remain responsible
- Priorities, final assignment and the handling of exceptions.
03 / How I work
Observe before recommending.
The analysis covers one process, not the whole company, and gives concrete evidence to decide whether to stop, reorganise, configure or develop.
- 01
Observe
I start from the people, materials and steps actually in use.
- 02
Map out the process
I note inputs, tools, waiting times, responsibilities and exceptions.
- 03
Define the scope
I narrow the scope to one problem or a case that can be assessed.
- 04
Recommend
I compare the alternatives: stop, reorganise, configure or build only what is needed.
- 05
Prepare the next step
If a trial is needed, I define its objective, checks, dependencies and responsibilities.
04 / What can remain
Define the scope of the analysis.
The work focuses on a clearly defined operational problem. Depth and materials depend on authorised access and the people who know the work.
Map of the observed process
Steps, tools, roles, waiting times and exceptions, mapped within the agreed scope.
Record of problems and dependencies
Evidence, constraints, missing information and points where the workflow breaks down or becomes hard to monitor.
Operational recommendation
A reasoned decision between stopping, reorganising the process, configuring existing tools or defining a trial.
05 / Questions and boundaries
Frequently asked questions.
Do you analyse the whole company?
No. One process at a time, not a complete mapping or an audit of every process.
Does software have to be developed after the analysis?
No. If what exists is not enough, the next step may be developing custom software or integrating AI, scoped separately.
What do the conclusions depend on?
On the evidence gathered and the access the company can authorise.
What is not included?
Legal or privacy responsibilities, managed cybersecurity, PC and network administration.
Is it worth starting with training?
It can help: AI training aligns people, criteria and precautions before choosing a process.
Which activity costs you the most time?
For a first phone call, an outline of the steps, people, tools and expected result is enough. You do not need a solution already defined.