Knowledge management · FAA Confluence Revamp
Restructuring FAA knowledge around how teams actually search
A large-scale Confluence restructuring driven by requirements discovery, information architecture, and ownership.
Situation
The FAA’s Confluence had grown for years without a plan. Information existed, but teams could not find it or confirm it was current.
Constraints
- Years of legacy content across many spaces
- Multiple teams with different ways of organizing information
What I did
I treated the revamp as a requirements effort rather than a cleanup. I interviewed teams about how they search for information, then rebuilt the structure, ownership model, and governance around that, with transition support so users moved with the change.
Why it worked
A knowledge base is only useful if people trust it. Clear ownership is what keeps it trustworthy.
Result
A knowledge base organized around real usage, with named owners who keep it current.
Work with me
Discuss a role or engagement
A short questionnaire helps me prepare for our first conversation. It takes about three minutes.
Stay in touch through Field Notes
Monthly lessons from real federal delivery work, plus new templates and prompts as they’re released.