In 2009, I was named one of Federal Computer Week's Federal 100. The Federal 100 recognized 100 people a year from government, industry, and academia who had made a meaningful contribution to how the federal government bought, used, or managed information technology.
I received the recognition for my work on the OMB MAX Federal Community. At the time I was serving as a consulting Chief Architect supporting the Office of Management and Budget's Budget Systems Branch and the government-wide Budget Formulation and Execution Line of Business.
The work
What we were building
What we were building sounds fairly ordinary today. Federal employees needed secure places where people from different agencies could work together, share information, develop documents, organize communities, and collaborate without every activity being trapped inside a single agency's technology environment.
That was much less ordinary in the late 2000s. Most federal systems were still organized around agency boundaries, individual applications, and fairly rigid ideas about who owned what.
MAX approached the problem differently. We were trying to make collaboration follow the work rather than the organization chart. That meant treating secure online communities, shared workspaces, identity, access control, collaborative authoring, knowledge management, and government-wide participation as parts of the same problem rather than as separate procurements.
MAX started around federal budgeting and financial management, but it grew well beyond that original use case. Over time it became one of the federal government's largest secure cross-agency collaboration environments, eventually supporting tens of thousands of users across more than 100 federal agencies.
That scale matters, but it is not the part of the story I find most interesting. The more important idea was that technology could create a trusted operating environment across institutional boundaries.
That problem has shown up repeatedly throughout my career. I have seen versions of it in government, healthcare, enterprise software, interoperability, platform design, security, and now AI-enabled organizations. The technology changes. The underlying question does not.
How do you allow people, systems, and organizations to work across boundaries without losing security, accountability, context, or control?
The Fed 100 recognition matters to me because it was an early external validation of that kind of work.
Context
The story behind the award
The MAX story did not start with me, and I do not want this page to imply that it did.
Andrew "Andy" Schoenbach, who led OMB's Budget Systems Branch, was one of the key leaders behind the MAX Federal Community. Federal Computer Week named Andy a Federal 100 winner in 2008 for his leadership in creating and championing MAX. I received the Federal 100 the following year for my work on the MAX Federal Community as consulting Chief Architect.
I think that sequence says something useful about how meaningful technology work actually happens. Someone has to see the institutional possibility. Someone has to create the conditions for the work. Then architects, engineers, operators, subject matter experts, and users have to turn the idea into something that actually works.
The architecture
What MAX was really about
I was not particularly interested in building another government website. The interesting problem was how to make work cross agency boundaries securely.
The questions that actually consumed the design work:
- How do you know who someone is?
- What should they be able to see?
- What should they be able to change?
- How do people from different organizations collaborate without giving up institutional controls?
- How do communities form around a problem rather than an organization chart?
- How do you create shared knowledge without creating another uncontrolled information silo?
Those were architectural questions, but they were also organizational questions. That distinction has shaped much of how I think about technology.
Looking back, MAX was an early version of a pattern that has become increasingly important. Technology is most valuable when it changes the shape of the work, not merely when it automates the existing shape of the organization.
That idea still influences how I think about platforms, interoperability, AI, organizational design, and technology leadership.
For the record
What the Federal 100 was
The Federal 100, usually called the Fed 100, was Federal Computer Week's annual recognition of 100 individuals from government, industry, and academia who had made an important contribution to federal information technology.
2009 Federal 100
- Recognized 100 individuals from government, industry, and academia.
- The 2009 awards recognized work performed primarily during 2008.
- Recipients were honored at the Federal 100 gala on March 25, 2009.
- The 100 recipients were not ranked against one another.
- It was not a lifetime achievement award.
Reflection
Why I still care about it
I have received other forms of recognition since then, and I expect this section of the site to grow. But I wanted to start with the Fed 100 because it represents something foundational in how I think about my work.
The award was not really about a particular technology stack. Most of that technology has changed dramatically. It was about architecture, institutional boundaries, collaboration, trust, and finding a way to make technology support how people actually needed to work.
Those problems have aged remarkably well.
References
- 01Federal 100 awards programFederal Computer Week / Nextgov FCWPublisher material describing the annual Federal 100 program.
- 02MAX Federal CommunityOffice of Management and BudgetOMB material describing the MAX Federal Community and its cross-agency use.
- 03Budget Formulation and Execution Line of BusinessOffice of Management and BudgetArchived federal record of the government-wide line of business MAX supported.
- 04Professional biographies documenting the Fed 100 recognitionshahidshah.comLong-standing bios citing the Fed 100 award for the Federal Community work.