Information checkedInformation unaudited Information geprüft Information ungeprüft Transparency in the IT demand process
Interview with Severin Beusch, IT Architect
Who or what decides whether a demand is implemented?
Whether an IT demand is implemented depends on several factors. From a technical and strategic perspective, the demand must align with our corporate strategy and deliver real added value – for example, by improving efficiency, quality, or customer satisfaction. Resources and budget also play a role. Organisationally, the solution must fit into our existing IT landscape, and there must not already be a similar solution in use within the company.
Does the complexity of a demand influence the decision and implementation?
Of course – itʼs actually a key factor. A small quick win is more likely to be implemented swiftly than a large-scale project. But the applicant also plays a crucial role: the more clearly the problem or need is described, the better we can understand the request. Larger and more complex demands also require more thorough review and coordination across various areas.
When filling out a demand request, I noticed you refer to T-shirt sizes. What do you mean by that?
We do indeed talk about T-shirts – but in this context, the sizes XS, S, M, and L help us to assess the complexity and scope of a demand. XS and S represent smaller requests that can be evaluated and approved directly by IT Architecture. M and L are more complex, and in these cases, the Architecture Board decides whether and how to proceed. This sizing approach allows us to make structured and efficient decisions.
Do you make decisions in the IT demand process behind closed doors?
No, decisions are always made in collaboration with the specialist departments, IT, Architecture, and sometimes Procurement. This collaborative approach ensures that all relevant perspectives are considered and that the best solution is found for LLB. The entire process and all decisions are completely transparent.
Tips for good demand requests
What makes a good and clearly described demand?
- Clear description: Clear description of need and objective.
- Demonstrate concrete benefits: What is the specific potential for improvement, and how does LLB stand to gain from it?
- Relevance: How important is the solution for your department (and possibly others), and when is it needed?
It is crucial to remain open to solution proposals and to approach the process without bias towards specific products. There are various IT solutions for every need, but not every solution is the right fit for LLB.
We look forward to working together constructively and professionally – and weʼre excited to hear your innovative ideas and suggestions.