About

This document is utilizing content that is generated by AI (GenAI) and utilizes the thesis (Report) on the graduate diploma in International Business which was written by Peter Flemming Teunissen Sjoelin, Lene Skov Mikkelsen, Emil Jensen, and Jonas Jensen  in 2009, but reference and quote other sources as well, and these are declared in the “References” section of the paper. The document is licensed under Creative Commons Share Alike and Attribution (CC-SA-BY). The person to credit is Peter Flemming Teunissen Sjoelin (2026).

Structural Architecture and Historical Evolution

The organizational architecture of modern financial institutions must reconcile the competing demands of localized operational agility and centralized structural coherence (Rogers 2003).¹ In the case of Nykredit, a prominent Danish financial services group, this structural tension is managed through a complex matrix configuration (Sjølin et al. 2009).² The primary dimensions of the Nykredit matrix consist of specialized business entities (selskaber), such as Totalkredit, Nykredit Bank, Forstædernes Bank, and various insurance, brokerage, and investment divisions, which are intersected by key customer segments, including Private, Commercial, Markets, and Partners (Sjølin et al. 2009).²

Operating outside of this formal matrix structure is Koncernudvikling og IT (KUDV), a centralized corporate staff function charged with directing the group’s technological and business development strategies (Sjølin et al. 2009).²

The consolidated structure of KUDV is the result of a multi-decade organizational evolution designed to bridge deep historical divisions (Sjølin et al. 2009).² Prior to 2001, IT development was structurally and geographically isolated from business development; the dedicated IT subsidiary, known as Data, operated out of Aalborg, while the business-oriented Koncernsalg og Udvikling (KSUE) department was located in Copenhagen (Sjølin et al. 2009).² This fragmentation created a severe misalignment between corporate strategies and the IT systems designed to support them, with the bank frequently initiating technology projects that failed to deliver strategic business value (Sjølin et al. 2009).²

In 2001, executive leadership consolidated these departments into a single entity, Koncernudvikling (Corporate Development), while establishing JN-Data as a joint venture with Jyske Bank to manage foundational IT operations and infrastructure (Sjølin et al. 2009).² In 2002, this structure was further refined and renamed Koncernudvikling og IT (KUDV) to reflect the complete integration of business and technology development (Sjølin et al. 2009).²

This integrated configuration, however, faces a severe resource imbalance relative to the broader Danish financial market (Sjølin et al. 2009).² KUDV operates with a development staff of approximately 400 employees, which is small compared to major domestic competitors; for example, Danske Bank maintains an IT and development organization of more than 3,000 personnel (Sjølin et al. 2009).² To compensate for this resource gap, Nykredit relies heavily on decentralized, business-led development (forretningsudført udvikling), where individual business units initiate and run their own localized development projects (Sjølin et al. 2009).²

While this decentralized approach provides rapid operational responsiveness, it also introduces substantial risks of duplicate development, technological fragmentation, and security vulnerabilities (Sjølin et al. 2009).²

To establish effective corporate governance over this decentralized landscape, KUDV created the Business Analysis and Architecture (FAA) department in early 2009 (Sjølin et al. 2009).² The FAA department was formed by merging two distinct, highly skilled professional cohorts within KUDV: Enterprise Architects (EAs), who were moved from the former Architecture, Technology, and Tools (ATV) department, and Business Analysts (FAs), who were consolidated under a newly established Center of Excellence for Business Analysts (CoE-FA) (Sjølin et al. 2009).² The remaining technical staff from the ATV department were reorganized into the Udviklingsmiljøer og IT-infrastruktur (Development Environments and IT Infrastructure) department (Sjølin et al. 2009).²

By bringing together EAs and FAs under a single management team, the FAA department was designed to act as a structural bridge, facilitating communication and alignment between centralized strategic planning and decentralized operational execution (Sjølin et al. 2009).²

Methodological Framework and Empirical Dataset

To evaluate the operational impact of the FAA department, this white paper adopts the sociological paradigms of Burrell and Morgan (1979).³ Rather than relying on a traditional functionalist view—which treats IT systems and organizational structures as objective, deterministic engineering projects—this study is grounded in the Interpretive Paradigm (Burrell & Morgan 1979).⁴ This perspective assumes that social reality is co-created and sustained through the subjective perceptions, language, and interactions of human actors within their specific organizational contexts (Burrell & Morgan 1979).⁴

By focusing on how individual employees, project managers, and executive leaders interpret the role of technology and formal processes, the interpretive researcher can expose the hidden cognitive, political, and communicative boundaries that hinder knowledge sharing and innovation within the firm (Burrell & Morgan 1979).⁶

The empirical data supporting this analysis was collected through a series of ten qualitative, semi-structured interviews conducted within KUDV and across several associated business segments at Nykredit (Sjølin et al. 2009).² These interviews were designed using an elaborative approach, where the interview guides were continually updated as new information emerged from previous sessions, ensuring a comprehensive exploration of the corporate landscape (Sjølin et al. 2009).²

To mitigate this risk, the research team actively triangulated his statements by conducting independent interviews with external project managers and by reviewing official internal documents and emails (Sjølin et al. 2009).²

Second, the historical baseline of KUDV is heavily shaped by the 104-minute interview with Jens Gadgaard, whose 24-year tenure at Nykredit makes him a key historical witness but also introduces the risk of retrospective bias (Sjølin et al. 2009).² This risk was managed by comparing his recollections with official corporate announcements and organizational charts (Sjølin et al. 2009).²

Theoretical Framework: Innovation Diffusion and Capability Maturity

To analyze the role of the FAA department in driving technological innovation, this study utilizes Everett Rogers’ (2003) Diffusion of Innovations framework.¹ Rogers defines diffusion as the process by which an innovation is communicated through specific channels over time among the members of a social system (Rogers 2003).¹ Within an organization, this process is structured into initiation and implementation phases, containing five distinct stages (Rogers 2003) ¹:

Within this framework, the FAA department operates as a centralized gatekeeper during the initiation phases (Agenda-Setting and Match-Making) (Sjølin et al. 2009).² It evaluates whether a proposed technological change (the innovation) aligns with the firm’s broader business and IT strategies (Sjølin et al. 2009).²

Furthermore, the members of the FAA department act as change agents (Rogers 2003).¹ Because of their broad, cross-functional role, these architects and analysts often operate as “strangers”—individuals who are members of the social system but are not deeply embedded in any single, localized business unit (Rogers 2003).¹

While this detachment allows them to remain objective and introduce innovative technical standards across the organization, it can also generate friction (Sjølin et al. 2009).² Localized business managers, who are often focused on immediate project deadlines and tight budgets, can view these change agents as external bureaucrats who introduce unnecessary architectural requirements that delay project delivery (Sjølin et al. 2009).²

To move beyond a purely technical focus, this study also integrates Esther Baldwin and Martin Curley’s (2007) IT Capability Maturity Framework (IT-CMF) ⁸ . The IT-CMF emphasizes that driving business value through technology requires shifting the organizational focus from technical implementation (“invention”) to value realization (“innovation”).² 

This ecosystem view is central to Arnoldo Hax and Dean Wilde’s (1999) Delta Model, which contrasts traditional, product-focused strategies with customer-centric “Total Customer Solutions” and platform-based “System Lock-In”.¹²

The creation of the FAA department represents a strategic shift away from a transactional, client-supplier model of IT delivery and toward a customer-centric “Total Customer Solutions” model (Sjølin et al. 2009).² In this model, IT architecture is designed around “customer bonding”—building deep, systemic integration with business units and external partners (such as JN-Data) to drive mutual value creation (Hax & Wilde 1999).¹³

The Strategic Clarification (SA) Process and Governance Gates

At Nykredit, the primary mechanism for proposing and validating technological innovation is the Strategic Clarification (Strategisk Afklaring or SA) process (Sjølin et al. 2009).² An SA acts as an internal business case, outlining a localized business need and proposing a technological or operational solution (Sjølin et al. 2009).²

Prior to 2009, this process lacked centralized coordination; business units submitted SAs directly to their assigned Key Account Managers (KAMs), who then brought them to the executive prioritization table (Sjølin et al. 2009).² This decentralized approach led to significant administrative inefficiencies, as identical or conflicting projects were initiated by different departments, and low-quality, poorly defined business cases frequently reached the executive level only to be rejected and sent back for revisions (Sjølin et al. 2009).²

To resolve these governance issues, KUDV implemented a centralized, formalized quality-assurance workflow in early 2009 (Sjølin et al. 2009).² Under this updated process, all newly drafted SAs must be routed through the newly established SA Secretariat, which is staffed by three dedicated FAA members (Sjølin et al. 2009).² 

The SA Secretariat enters the SA into a centralized tracking database, which maintains records of all corporate development initiatives dating back to 2005 (Sjølin et al. 2009).²

An FAA analyst or architect is then assigned to review the document and draft a standardized SA Summary (Sjølin et al. 2009).² This review evaluates the proposal’s strategic alignment, architectural fit, and potential synergies with other projects across the organization (Sjølin et al. 2009).²

The standardized “SA Summary” is a highly structured document designed to enforce rigorous, objective evaluation across all proposed initiatives (Sjølin et al. 2009).²

The table below maps the specific sections, metadata fields, and analytical criteria required for each SA Summary:

Summary Section	Targeted Metadata Field	Operational Input & Evaluative Criteria	Strategic Function in Governance
Section 1: Executive Briefing	Business Client	Identifies the initiating business unit or segment within Nykredit (e.g., Markets, Private).2	Establishes formal ownership.2
	Authors & Contributors	Lists the business and IT professionals who drafted the proposal.2	Identifies key project contacts.2
	Content & Deliverables	Standardized summary of the project scope and expected outcomes.2	Summarizes technical deliverables.2
	Financial Profitability	Summarizes the projected cost, business value, and ROI of the project.2	Enforces economic justification.2
	Assigned KAM & PM	Identifies the Key Account Manager and designated Project Manager.2	Clarifies project leadership.2
Section 2: IT & Architectural Review	Strategic Alignment	Evaluates whether the proposed innovation supports the group’s business strategy.2	Prevents strategic drift.2
	Process Ambition Level	Classification: Adjusting (minor process change), Optimizing (efficiency-focused), or Renewing (true innovation).2	Measures operational impact.2
	Architectural Ambition Level	Classification: Minor, Medium, or Major impact on existing systems.2	Measures technical risk.2
	Infrastructure Deviations	Identifies any proposed technologies that deviate from corporate standards.2	Minimizes technical debt.2
	Corporate Synergy Check	Compares the proposal against the historical database (2005-present) to find duplicate initiatives.2	Prevents redundant development.2
	FAA Recommendation	Official recommendation: Approve as-is, merge, defer, or reject.2	Guides executive decisions.2
Section 3: Executive Decision	Chefmøde Decision Log	Records the final decision of the KUDV Executive Committee.2	Standardizes corporate accountability.2

This quality-assurance workflow introduces formal checkpoints into Nykredit’s development pipeline (Sjølin et al. 2009).² 

Gatekeeping, as defined by Rogers (2003), is the process of controlling whether an innovation is allowed to spread to a group of potential adopters.¹ At Nykredit, the SA must pass through three distinct gates:

1. Gate 1 (Inception): Managed by the local Department Manager, who evaluates the proposal’s localized utility and authorizes staff to spend time drafting a formal SA (Sjølin et al. 2009).²
2. Gate 2 (Validation): Managed jointly by the area Key Account Manager (KAM) and the FAA SA Secretariat (Sjølin et al. 2009).² The KAM manages the business relationship, while the FAA conducts technical quality assurance and drafts the SA Summary (Sjølin et al. 2009).²
3. Gate 3 (Approval): Managed by the KUDV Executive Committee (chefmøde), chaired by the Director of KUDV and attended by development chiefs, which makes final prioritization and capital allocation decisions (Sjølin et al. 2009).²

This gatekeeping architecture reveals a significant structural redundancy at Gate 2 (Sjølin et al. 2009).² While the KAM holds formal responsibility for the business relationship, the FAA department conducts the actual technical review and architectural validation (Sjølin et al. 2009).²

This split in responsibilities adds administrative delay to the process; the KAM often serves as an intermediary pass-through, receiving the SA, routing it to FAA, waiting for the review, and returning it to the business unit (Sjølin et al. 2009).² This redundancy suggests that consolidating these responsibilities within a single department could streamline the governance process (Sjølin et al. 2009).²

The Role of ‘Rammepapirer’ (Framework Papers)

In addition to reviewing SAs, the FAA department is responsible for developing and maintaining Nykredit’s Rammepapirer (Framework Papers) (Sjølin et al. 2009).² A rammepapir is a formal document that establishes standard principles, technical patterns, and guidelines within a specific technological or operational domain (e.g., customer data management, IT security, or portal architecture) (Sjølin et al. 2009).²

These documents are structured in two distinct parts:

Part 1 describes the current technical environment and its operational limitations, while Part 2 outlines the strategic target state and provides a roadmap for how the organization can transition to that model over time (Sjølin et al. 2009).²

To prevent these documents from becoming outdated quickly, the FAA department designs rammepapirer at a high level of abstraction, focusing on general guidelines rather than rigid, low-level technical specifications (Sjølin et al. 2009).² This abstract approach ensures that the guidelines remain relevant over multi-year cycles while still allowing project teams the flexibility to choose specific, modern technologies that fit within the broader corporate standards (Sjølin et al. 2009).²

Importantly, the empirical interviews conducted across Nykredit revealed a strong consensus that these rammepapirer do not act as barriers to innovation (Sjølin et al. 2009).² Both internal FAA staff and external project managers reported that the documents provide helpful guardrails that prevent project teams from building incompatible systems, ultimately making it easier to integrate new solutions into the bank’s broader infrastructure (Sjølin et al. 2009).²

Empirical Assessment of Organizational Innovativeness

To understand Nykredit’s capacity to generate and adopt innovations, the research team analyzed KUDV and the FAA department across the eight structural variables defined by Rogers (2003) as the key determinants of organizational innovativeness.¹

The table below summarizes this empirical analysis, contrasting Rogers’ theoretical expectations with the actual operational realities observed within Nykredit:

Innovativeness Determinant (Rogers 2003)	Theoretical Correlation with Innovativeness	Empirical Findings & Operational Realities at Nykredit	Second- and Third-Order Strategic Implications
Attitude Toward Change	Positive: Receptive leadership and staff promote creative experimentation.1	High receptivity within KUDV and FAA.2 Executive leadership introduced “Tænk Nyt” (Think New) as a core corporate value alongside Insight, Effort, and Empathy.2	Segmented Receptivity: While KUDV and FAA embrace change, localized business units (e.g., credit) are highly conservative due to resource pressures, requiring change agents to demonstrate clear business value to gain support.2
Centralization	Negative: Concentrating power at the top limits autonomy and stifles bottom-up ideas.1	High centralization of IT quality assurance within FAA.2 Decision-making for all major development projects is concentrated within the KUDV Executive Committee.2	The Governance Paradox: Theoretically negative, centralization is necessary at Nykredit to provide structural coordination for decentralized development, preventing duplication and ensuring architectural compliance.2
Complexity	Positive: High levels of diverse expertise and education foster creative problem-solving.1	High complexity.2 FAA staff are highly educated (candidates, MBAs, HDs) with extensive industry experience, and the Center of Excellence preserves valuable business analysis expertise.2	The Translation Challenge: High technical expertise can alienate business unit stakeholders, creating a cognitive barrier where business managers view FAA as an academic, out-of-touch bureaucracy.2
Formalization	Negative: Rigid rules, standardized procedures, and bureaucracy inhibit creative thinking.1	High formalization.2 All project proposals must go through the standard SA process and comply with strict architectural rammepapirer.2	Administrative Friction: Strict adherence to the SA process ensures architectural compliance but slows down execution, forcing agile business units to view the central IT department as an operational bottleneck.2
Interconnectedness	Positive: Strong internal networks and cross-functional ties facilitate knowledge sharing.1	Moderate.2 The formation of FAA integrated EAs and FAs.2 However, EAs spend 80% of their time in-office, while FAs spend 80% of their time embedded in external projects.2	Siloed Co-location: Co-locating EAs and FAs has not resolved their operational differences; their differing daily schedules limit spontaneous, informal knowledge sharing.2
Organizational Slack	Positive: Unallocated resources (capital, time) allow teams to explore speculative, high-reward ideas.1	Extremely low.2 Highly restrictive resource levels.2 Project managers face intense pressure to cut project scope rather than exceed budgets.2	Suppression of Innovation: The lack of resource buffers forces project managers to minimize risk and avoid complex, innovative solutions in favor of safe, incremental improvements.2
Size	Positive: Larger organizations possess greater infrastructure and resources.1	Nykredit is a large financial institution, but KUDV is relatively small (400 staff) compared to major competitors like Danske Bank (3,000 staff).2	Resource-Constrained Scale: While Nykredit has the financial scale of a major bank, its small IT footprint forces it to rely on decentralized development, making effective central governance essential.2
System Openness	Positive: Active exchange with external partners and competitors imports new perspectives.1	High openness.2 Nykredit works closely with research firms (e.g., Gartner) and collaborates with competitors (e.g., Danske Bank, Nordea) on non-competitive issues like data warehousing.2	Collaborative Commons: By collaborating with competitors on foundational infrastructure, Nykredit offsets its smaller scale, focusing its limited development resources on customer-facing innovations.2

Comparative Analysis of Strategic Solutions

To improve Nykredit’s capability to innovate, the research team developed a comprehensive set of strategic recommendations (Sjølin et al. 2009).² These recommendations are designed to address the key organizational bottlenecks identified in the empirical analysis, focusing on the innovative process, gatekeeping architecture, and structural determinants of innovativeness (Sjølin et al. 2009).²

The table below provides a comparative analysis of these proposed solutions, detailing their operational advantages, implementation costs, resource demands, and potential risks:

Proposed Strategic Solution	Targeted Bottleneck	Operational Benefits & Advantages	Required Corporate Resources	Implementation Challenges & Risks
Strategic Strategy Communication	Agenda-Setting: Poor alignment between corporate strategy and localized business proposals.2	Aligns bottom-up business proposals with corporate strategies, reducing the “mismatch” rate of SAs during review.2	Low: Leverages existing communication channels (blogs, meetings, intranets).2	Requires active, ongoing commitment from senior leadership to sustain clear communication.2
Gartner Knowledge Library	Match-Making: Limited awareness of modern, industry-standard solutions.2	Provides development teams with direct access to global market research, improving the quality of proposed technical solutions.2	Medium: Capital allocation for research subscriptions and portal maintenance.2	Low adoption if the library is not actively integrated into standard project-definition workflows.2
Communities of Practice (COPs)	Interconnectedness: Limited informal contact and technical silos within KUDV.2	Builds informal networks that cross department boundaries, facilitating organic knowledge sharing and collaboration.2	Low: Small time commitments for meetings and basic administrative support.2	Can quickly lose momentum if not supported by an active, collaborative work culture.2
Consolidated SA Intake within FAA	Gatekeeping Redundancy: Unnecessary hand-offs between KAMs and FAA.2	Simplifies the SA lifecycle, shortening review times and bringing the specialist team closer to the business units.2	Low: Structural realignment of responsibilities within existing KUDV staff.2	Potential resistance from KAMs who may view the change as a loss of authority.2
Fast-Track Approval Pathways	Formalization: Heavy bureaucracy that delays time-sensitive projects.2	Gives business units the autonomy to rapidly deploy minor, time-sensitive innovations without lengthy reviews.2	Medium: Allocation of dedicated, decentralized development budgets.2	Risk of architectural drift if fast-track projects are not monitored for basic compliance.2
EA/FA Workflow Alignment	Interconnectedness: Silos and limited communication between EAs and FAs.2	Aligns top-down architectural design with bottom-up operational realities, improving the quality of strategic standards.2	Low: Adjusting internal meeting schedules and reporting structures.2	Cultural friction if EAs and FAs resist changing their established daily routines.2
Flexible Funding Buffers	Organizational Slack: Risk aversion due to strict, rigid budget controls.2	Encourages project managers to explore complex, innovative solutions by reducing the fear of minor budget overruns.2	High: Capital reserves to absorb minor budget variances.2	Requires a significant cultural shift in finance departments toward value-driven cost management.2

Strategic Recommendations and Implementation Roadmap

To implement these recommendations without disrupting Nykredit’s ongoing operations, the research team developed a phased, five-stage transformation roadmap (Sjølin et al. 2009).² This roadmap is structured to prioritize low-cost, high-impact changes first, building the organizational trust and alignment necessary to support more complex cultural shifts later in the cycle (Sjølin et al. 2009).²

This phased approach ensures that foundational improvements—such as strategic alignment, simplified gatekeeping, and internal collaboration—are established first (Sjølin et al. 2009).² Once these governance mechanisms are in place, Nykredit can safely introduce more complex cultural changes, such as flexible funding buffers and fast-track approval pathways, without risking technological fragmentation or strategic drift (Sjølin et al. 2009).²

By transitioning from a transactional, client-supplier model of IT delivery to a collaborative, customer-centric corporate ecosystem, Nykredit can maximize the value of its technology investments and build a sustainable competitive advantage in a rapidly changing market (Hax & Wilde 1999, Rogers 2003).¹

References

Andersen, I., 2006. Den skinbarlige virkelighed. 3rd ed. København: Samfundslitteratur. ²

Avison, D. & Fitzgerald, G., 2006. Information Systems Development. 4th ed. Maidenhead: McGraw-Hill. ²

Baldwin, E.C.M. & Curley, M., 2007. Managing IT Innovation for Business Value: Practical Strategies for IT & Business Managers. Hillsboro: Intel Press. ²

Burrell, G. & Morgan, G., 1979. Sociological Paradigms and Organisational Analysis – Elements of the Sociology of Corporate Life. London: Heinemann. ²

Hax, A.C. & Wilde II, D.L., 1999. The delta model: Adaptive management for a changing world. Sloan Management Review, 40(2), pp. 11-28. ²

Rogers, E.M., 2003. Diffusion of Innovations. 5th ed. New York: Free Press. ¹

Sjølin, P.F.T., Mikkelsen, L.S., Jensen, E. & Jensen, J., 2009. IT-innovation i Nykredit. Bachelor Thesis, Copenhagen Business School. ²