A agreement between the workers’ council and the management had been ratified, and with it the obligation to align performance‑ and gender‑neutral job titles in the e‑mail signatures of more than 5 000 employees by the end of 2025. At first glance that sounds like a straightforward task: update the signature template and roll it out across the corporate mail system. In practice, however, the project quickly pulled every lever of a classic “head‑and‑heart” implementation: five business units, each with its own external service provider, disparate system landscapes, no existing architecture diagrams, and the handling of personally identifiable information. The challenge was to meet the board’s visible, deadline‑driven demand without a finished concept or a full‑scope plan in place.
Architectural horizon: uncharted
Under severe time pressure the usual project mantra of “analyze first, design second, implement third” is virtually impossible. Instead, a patchwork of ad‑hoc decisions emerges, creating uncertainty at every turn:
- Who owns which part of the system?
- What technical limitations exist in Microsoft’s mail‑signature feature?
- How can we process personal data in a legally compliant way?
- Most specifically, what dependencies tie the five business units and their external providers together?
Without a clear view of the IT architecture, any realistic risk assessment collapses, shaking the organization’s governance foundation.
Approach: Clear Steering over Perfection
Our team contributed not only deep technical expertise but, more importantly, the ability to map complex service chains and cement accountability. The first step was a rapid scan: within a few days we inventoried every involved system, data flow, and interface and captured them in a simple visual architecture diagram. That picture instantly revealed the critical paths, most notably the Microsoft Exchange signature engine, which each business unit configures through separate service providers.
In parallel we instituted transparent communication. Rather than lengthy alignment meetings, we hosted short, agenda‑driven calls with crystal‑clear questions:
- “What must I deliver and by when?”
- “What are the risks?”
- “Who is responsible if something goes wrong?”.
Each provider received a single, well‑defined task and a binding time window. Responsibilities were logged in a project‑steering board, so whenever an issue surfaced the owner was obvious. No one could hide behind “I thought it was someone else’s job”.
A further key was the “Minimum Viable Solution” approach: instead of building a perfect, all‑encompassing signature framework, we defined the smallest functional version that satisfied the contractual expectations. That meant initially integrating only the core job‑title variables and adding optional attributes later. This reduction allowed us to test the Microsoft implementation quickly, work around existing constraints, and still meet data‑privacy requirements like data minimisation and secure handling.
Outcome: delivery ahead of the deadline
Already by mid-December, just before the Christmas holidays, the new signatures were live across the organization. The rollout proceeded without critical errors because every integration point had been validated and documented beforehand. The client not only gained a visible signal of leadership commitment but also a durable artefact: an up‑to‑date IT‑architecture diagram that will serve as a reference for any future policy change. Service providers now know precisely where their responsibility ends, and internal units can coordinate their processes transparently.
The real success, however, lies not in the signature update itself but in the insight that under extreme time pressure the decisive asset is the ability to steer external partners clearly, order dependencies, and assign responsibility unequivocally. Possessing this steering competence lets an organisation fulfil strategically important, short‑notice mandates reliably, without the “best concept” taking centre stage, but rather the effective orchestration of the entire ecosystem.
Conclusion: When multiple service providers, departments, and technical dependencies converge on a tight deadline, clear governance, rapid mapping of the system landscape, and a focused accountability culture outweigh any methodological perfection. That is how a seemingly unmanageable project, such as updating more than 5 000 e‑mail signatures, can be delivered on time, error‑free, and with lasting benefit.
Our whitepaper on IT architecture demonstrates how roles, scopes and decision paths can be modeled ahead of time, so that even short-term expectationss do not cause sleepless nights.
Source of header image: Ferenc Horvath / unsplash
We are IT partners
Our motto: Establish IT in everyday business as a solution, not as a source of problems.
