Trying to find the balance between operational clarity and overwhelming documentation.
What systems/templates/tools are working for your teams?
Anytime i try to document something people see it as bureacracy
I’m happy to share that I’ve passed the ITIL Foundation Version 5 exam with a score of 34 out of 40.
This was part of a beta test focused on the Italian translation of the official materials and exam. Overall, it was an interesting experience and a useful contribution to the improvement process.
The translation quality was generally good, especially considering this was an early version.
The sample papers felt somewhat easier compared to the official exam, which is something to keep in mind when preparing.
At the same time, some parts of the translation could be improved in future iterations, a few questions were not fully fluid or natural in Italian. That said, this is understandable for a first release, and I expect further refinements as more feedback is collected.
From a content perspective, the exam reflects a strong evolution of best practices in IT Service Management. It is clearly aligned with today’s AI-driven, product-centric, and digital-first environments, which makes it more relevant to current industry needs.
Overall, it was a positive experience: both as a certification milestone and as a contribution to improving the localization and quality of the official material
Most design projects fail not because of bad ideas, but because the team never truly understood the people they were designing for.
They built what they assumed users needed. Not what users actually needed.
Here's the first principle that changes everything. 🧵
DTMethod isn't "designing nice products".
It's a structured, human-centred approach where every decision traces back to real human needs.
Focus on People breaks down as follows:
Solutions must help stakeholders → every output serves a real human need
Research before assumptions → data over gut feel
Empathy is the starting point → understand before solving
The user is the judge → validation comes from the people, not the team
This matters because teams tend to fall into the trap of "we know what they want." But Design Thinking research consistently shows: the further you are from the user, the more distorted your picture of their needs.
DTMethod forces you back to the source.
Where teams get it wrong:
❌ Skipping user research to save time
❌ Confusing stakeholder opinion with user insight
❌ Designing for the loudest voice in the room
❌ Treating empathy as a soft skill, not a method
Focus on People isn't a value statement. It's an operating principle, one that anchors every phase of DTMethod to real human outcomes.
How well does your team actually know the people you're designing for?