Managing a $120 billion federal IT portfolio isn't for the faint of heart. It's not just spreadsheets and slide decks—it's a complex orchestration of budget cycles, policy frameworks, and data-driven decisions. I recently wrapped up a stint at the Office of Management and Budget (OMB) in the Executive Office of the President, where I helped steer this beast as an IT Portfolio Management and Policy Analyst (GS-14). My mission? Develop investment guidance, champion a user-centered overhaul of ITDashboard.gov, and propose a project-oriented budgeting structure to modernize government IT. At the core of it all was Technology Business Management (TBM)—a framework adapted to fit the federal beast. Here's an inside look at how it works, why it matters, and where it's headed.
The Federal Budget Dance: Cycles and Timelines
Federal budgeting is a marathon, not a sprint, unfolding across three overlapping cycles: formulation, approval, and execution. Formulation kicks off 18 months before the fiscal year—think spring 2022 for FY 2024—when agencies draft their requests. By summer, they're "preparing the book"—a massive tome of priorities and numbers—for the OMB Director to refine and present to the President by late fall. Approval spans Congress's review from February to September, culminating in appropriations. Execution runs the fiscal year itself (October 1 to September 30). For IT, this means a $120 billion portfolio gets diced, debated, and disbursed over two-plus years—making agility a pipe dream without sharp tools like TBM.
TBM Unveiled: Layers and Evolution
TBM isn't just jargon—it's a structured lens for aligning IT costs with business value, born in the private sector but increasingly vital for government. It's built on layers:
- Cost Pools: Raw expenses—hardware, software, labor—mapped to funding sources.
- IT Towers: Functional buckets like compute, storage, or applications (think NIST 800-145 categories).
- Services: What IT delivers—email, cloud hosting, cybersecurity—tied to user value.
- Business Units: Who consumes them, from VA hospitals to IRS tax processing.
Enter OMB Circular A-11, Section 52—the Capital Planning and Investment Control (CPIC) playbook. Updated annually, it's the federal IT budgeting bible, mandating agencies report investments via Exhibit 53 (portfolio summary) and Exhibit 300 (business cases). When I joined OMB in September 2022, CPIC was evolving. Recent revisions—spurred by the Modernizing Government Technology Act—added a "Solutions Layer" to TBM, bridging towers and services with specific platforms (e.g., AWS, Salesforce). This shift, rolled out in FY 2022 guidance, demanded granularity: not just "cloud costs," but "GCP Vertex AI for fraud detection." My challenge? Adapt TBM's commercial roots—optimized for profit—to government's mission-driven sprawl.
Tailoring TBM for Government: My Vision
Government isn't a corporation—ROI isn't profit, it's citizen impact. TBM needed a federal twist. At OMB, I proposed a project-oriented structure inspired by SAP's Project Management (PM) Module, using Work Breakdown Structures (WBS) rooted in TBM layers. Picture this: every IT investment—say, a $50M VA telehealth upgrade—broken into WBS elements (compute, app dev, cybersecurity), mapped to cost pools, and tracked via services (patient portals). The goal? Standardize how IT managers plan and deliver, syncing investments with outcomes. I envisioned rolling this out agency-wide, feeding data into the Folio tool (OMB's portfolio tracker), and ultimately reflecting it on ITDashboard.gov—creating a unified, transparent pipeline from budget to execution.
Redesigning ITDashboard.gov: TBM Meets User-Centric Design
ITDashboard.gov, launched in 2009, was the public face of this $120 billion portfolio, but by 2022, it was creaky. Users, Congress, CIOs, taxpayers, struggled with clunky navigation and stale visuals. I led a redesign, jumping into Figma to craft high-fidelity prototypes. Leveraging TBM, I reimagined dashboards: cost pools visualized as heatmaps, services ranked by citizen impact (e.g., uptime for SSA benefits), and a Solutions Layer spotlighting platforms like Azure or Tableau. My user-centered approach, tested via stakeholder feedback—cut search time by 20% in mockups, proving data could be both accessible and actionable. The catch? Scaling it demanded OMB-wide buy-in, a work still in progress when I left.
Why It Matters—and What's Next
TBM at OMB wasn't just about numbers, it was about clarity. My WBS structure aimed to tame a $120 billion beast, aligning IT with missions like veteran care or tax equity. Circular A-11's Solutions Layer pushed this further, forcing agencies to justify not just spending but platforms, a boon for accountability. Yet gaps lingered: adoption was uneven, and Folio's integration with ITDashboard.gov remained aspirational.
Looking ahead, I'd urge OMB to double down, mandate WBS-style budgeting, unify tools under TBM, and fast-track the dashboard revamp. My stint there, ending Jan 2023, taught me that government IT thrives on structure, not chaos. With TBM as the backbone, we can turn a sprawling portfolio into a strategic asset, delivering value one project at a time.