Portfolio
Modernising a National Platform You Do Not Control
vr.de created national interest in the cooperative banking group’s services, helped visitors understand their needs and directed qualified demand to local banks. Funded by those institutions, the platform had to do more than look current; it had to work on their behalf. After a recent relaunch, however, much of the site still lacked a coherent mobile experience.
The shared banking CMS imposed substantial dependencies: a limited supplier pool, infrequent releases and several layers of decisions. At VR-NetWorld, I coordinated the work across the BVR, internal teams and the design and implementation agencies. My formal title was Content Manager; the responsibilities on this project included requirements, solution development and delivery coordination.
Process
Phase 01
Turning a Known Gap into a Business Case
I combined market standards, vr.de’s own traffic data, plausible abandonment risks, the BVR’s “webErfolg” principles and the platform’s role in the lead journey into an investment case, supported by an initial cost range and delivery outline.
Phase 02
Prioritising Components, Not Pages
The agencies and I chose to work component by component. We prioritised the building blocks and organised them into batches, first developing a coherent design for BVR approval and then implementing it incrementally.
Phase 03
Decoupling CSS, Markup and Release Trains
A technical kick-off separated CSS-only improvements from components requiring markup or backend work. I placed the latter into the data centre’s planning early; with only two central releases a year, timing was not an administrative detail but part of the solution architecture.
Phase 04
Delivering Time to Budget
I worked through the components with the implementation agency sprint by sprint, balancing progress against maintenance and incoming client priorities. I handled briefing, review and coordination. In year two, lower-priority components were fitted around available capacity, allowing the programme to continue alongside normal operations.
Phase 05
Turning Local Needs into Platform Improvements
Where an improvement was relevant beyond vr.de, I aligned with the team evolving the banks’ shared web platform. Some components therefore entered the central standard rather than becoming bespoke exceptions — more leverage, fewer snowflakes.
Methods
Business Case Development
Connect usage signals, strategic policy, lead responsibility and cost into an investment argument decision-makers can use.
Component-led Roadmap
Prioritise reusable components by impact and dependency rather than treating symptoms one page at a time.
Dependency Management
Manage agencies, CMS constraints, backend work and central release planning as one connected delivery system.
Trust as Infrastructure
Clear requirements, regular check-ins and transparent scope decisions stabilised an agency relationship that had previously been defined by escalation.
Key Takeaways
Agility Needs a Stable Direction
Flexible prioritisation worked because the target state and technical dependencies were clear, not because the direction changed every fortnight.
Constraints Belong in the Concept
CMS limits and release windows were not obstacles discovered after design; they were parameters for shaping the roadmap.
Platform Before Exception
The strongest answer to a local requirement may be an improvement that benefits the wider ecosystem.
The mobile experience was systematically modernised over roughly two years. The client was satisfied, collaboration with both agencies worked well, and selected improvements entered the shared standard for bank websites. I cannot now substantiate a change in referral numbers. The demonstrable contribution is the delivery itself: turning an acknowledged gap into a prioritised series of improvements that could move through a complex organisation.