The Federal Enterprise Architecture Framework, commonly called FEAF, is an enterprise architecture approach developed to help public sector organizations align strategy, business operations, information, applications, technology, and performance management.
Executive Summary
FEAF provides a structured way to describe how an organization operates and how change should be planned. Although it originated in government, many of its ideas are useful for any large organization that needs stronger alignment between mission, services, data, technology, and outcomes.
Why FEAF Matters
Large organizations often manage complex portfolios, many stakeholders, shared services, and long planning horizons. FEAF helps create a common structure for understanding those elements and coordinating change across teams.
Core Concepts
Business and Mission
Architecture begins with the mission, strategic goals, services, and business capabilities the organization must support.
Data and Information
Data architecture describes the information needed to deliver services, make decisions, and meet accountability requirements.
Applications and Services
Application views identify the systems and shared services that enable operations and customer or citizen experiences.
Technology and Infrastructure
Technology architecture addresses the infrastructure, platforms, security, networks, and technical standards that support the enterprise.
Performance
Performance measures connect architecture investments to outcomes, service quality, efficiency, and mission results.
How Teams Can Use FEAF
- Start with a mission or business outcome.
- Map the capabilities and services required.
- Identify supporting data, applications, and technology.
- Define current state issues and future state goals.
- Create a roadmap with owners, dependencies, and measures.
Strengths
- Encourages a mission and outcomes focused view of architecture.
- Supports cross organizational planning and shared services.
- Connects architecture with performance measurement.
- Provides a useful structure for large, complex environments.
Common Mistakes
- Using the framework only as documentation.
- Ignoring business owners and operational teams.
- Trying to model every area at the same level of detail.
- Failing to connect architecture findings to funding and delivery decisions.
Key Takeaways
FEAF is useful because it links mission, capabilities, information, technology, and performance. It helps organizations manage complexity while keeping architecture connected to measurable outcomes.
Frequently Asked Questions
Is FEAF only for government organizations?
No. It was created for government, but its approach to mission alignment, shared services, and performance can help many large enterprises.
How does FEAF compare with TOGAF?
Both support enterprise architecture. TOGAF is often used as a general architecture practice framework, while FEAF places strong emphasis on mission, service delivery, and public sector planning.