Est modus in rebusThere is a measure in all things
Bringing order, one step at a time
In twenty years of working in IT, I have learned that, to make a system work, you first need to understand the needs of the people who use it. Then you act, one step at a time.
I started in user support, at a company with strong seasonal peaks in its workload. That is where I came to understand how much IT affects everyday work.
For eleven years I worked for an international group in a regulated sector, moving from system administrator to head of IT. Today I hold the same role at an Italian manufacturing group and report directly to the owners.
I present management with the risks, the total costs and the possible alternatives, together with a recommendation. My job is to give decision-makers what they need to make a considered choice.
I have worked at the help desk and at the boardroom table. From both sides I have seen how much it matters that a system works without being noticed.
Foundations first
Years ago I took charge of a server room after a flood. I started with a broom. Then I dealt with the cooling, the cabling, the power supply and the machines, now raised a metre off the floor. Only later did I introduce redundant systems to keep the service running even in the event of a failure.
From that experience I drew a sequence of work that I still follow.
01
Understand
I spend the first month getting to know the existing situation: I review the documentation, check systems and tools, and draw up an inventory. I avoid making changes until I have a clear picture, while the business carries on as usual.
02
Secure
I start with the elements the whole system depends on: access control, data backups and protection against external threats.
03
Improve
I make one change at a time. Every change includes a backup, a functional test and a procedure for restoring the previous state if something goes wrong.
Artificial intelligence
I also use artificial intelligence as a working tool, with three clear rules: decisions remain mine; before proposing or writing anything, the AI must examine the existing documentation and materials; I consider a piece of work finished only after I have checked it myself.
From urgent requests to a plan
When I joined the group, IT was dealing almost exclusively with urgent requests. There were twenty open projects and the priorities had yet to be defined.
In the first ninety days I introduced a scoring system to set priorities and a limit on the number of activities in progress at any one time. Management could then rely on a clear plan, with a clear sequence of work and explicit choices about what to tackle straight away and what to postpone.
3/4
Of the 452 activities recorded in that period, 340 — about three in four — were important and planned.
Knowing where to stop
I work in seven areas, together with in-house IT and suppliers.
The activities listed below fall outside my remit. When they are needed, I make this clear from the outset and help find the most suitable specialist.
| Number | Area | Label |
|---|---|---|
| 1 | Leadership and working with management | Proven |
| 2 | IT governance, costs and suppliers | Proven |
| 3 | Infrastructure and business continuity | Proven |
| 4 | Security and compliance | Proven |
| 5 | Business systems and data | Practised |
| 6 | AI and digital tools | Practised |
| 7 | Digital for sales and marketing | Practised |
- Proven measured results, in more than one setting or over several years
- Practised applied on real projects, in a single setting or without a comparable measure
Outside my scope
- Configuring the ERP system
- Developing software products
- Plant automation
- Continuous security monitoring and penetration testing
- Legal opinions and certification audits
- Selling hardware or licences
A daily commitment
A system stays in good order as long as someone looks after it over time.
To discuss your company's needs, you can find me here.
Let's talk
- Email[email protected]
- LinkedInlinkedin.com/in/aldobrunello