The policy analyst's knowledge base has a distinctive requirement that differs from other knowledge professions: policy knowledge expires. The stakeholder landscape that was accurately documented in a KB entry from two years ago may no longer reflect current positions; the evidence base for a policy instrument may have been significantly updated by new program evaluations; the political configuration that made a particular approach viable may have shifted. Policy expertise requires not just accumulating knowledge but maintaining dated entries that can be assessed for currency when retrieved.
Four knowledge domains constitute the policy analyst's professional knowledge base: policy research and evidence (the substantive knowledge about what the evidence shows for different policy options); stakeholder and political landscape intelligence (the knowledge about who holds what positions, what political constraints operate, and how institutional dynamics work); analytical methods and institutional expertise (the analytical craft knowledge that makes policy analysis technically competent); and professional network and relationship knowledge (the contacts, relationships, and institutional intelligence that make policy advice practically useful).
Domain 1: Policy Research and Evidence
Policy research and evidence is the substantive knowledge base: what does the research show about different policy interventions, program designs, implementation approaches, and policy instruments? This is the knowledge that grounds evidence-based policy analysis in something more than assertion.
Organization by policy area:
The primary retrieval path for policy research knowledge is by policy area — retrieving what's known about housing affordability, workforce development, or education financing when beginning an engagement in that area.
POLICY RESEARCH AND EVIDENCE KB
BY POLICY AREA:
Policy area: [e.g., "Minimum wage policy" or "Charter school expansion"]
Last reviewed: [Date — entries without dates may be outdated]
WHAT THE EVIDENCE SHOWS:
Summary: [Current state of the research]
Evidence quality: [ ] Strong [ ] Moderate [ ] Mixed [ ] Limited
Key sources: [Most authoritative references]
Key researchers/organizations: [Who to watch for new work in this area]
WHAT THE EVIDENCE DOESN'T SHOW:
Major gaps: [What the research can't tell us]
Contested claims: [Where researchers disagree and what the dispute is about]
Where findings don't generalize: [Context-specific limitations]
POLICY DESIGN IMPLICATIONS:
What implementation evidence shows: [What makes policies in this area work or fail]
Equity considerations: [Distributional effects; who benefits; who bears costs]
Political feasibility factors: [What political dynamics research identifies]
RECENT DEVELOPMENTS:
What's changed since prior review: [New evidence that updates prior understanding]
Emerging research directions: [What new work is coming]
BY POLICY INSTRUMENT:
Instrument: [e.g., "Refundable tax credits" or "Housing vouchers"]
WHAT WORKS:
When this instrument is effective: [Evidence on success conditions]
Evidence quality: [How strong is the evidence]
WHAT DOESN'T:
When this instrument fails: [Evidence on failure modes]
Why: [Mechanisms behind failure]
IMPLEMENTATION CONSIDERATIONS:
Administrative requirements: [What effective implementation requires]
Equity effects: [Distributional implications]
Interaction effects: [How this instrument works with or against other policies]
"What the evidence doesn't show" is the most important analytical integrity field in the research KB. Policy advocacy routinely overstates the strength of evidence for preferred policy approaches; policy analysis at its best is honest about what the evidence shows and what it can't determine. The analyst whose KB includes explicit documentation of evidence limitations is better positioned to give clients accurate guidance about what evidence actually supports.
"Last reviewed" discipline: research knowledge in policy-relevant areas should be flagged for review on a time-based schedule: every 12-18 months for active specialty areas, whenever a major new study or program evaluation appears. An undated entry may accurately describe the evidence base as it was three years ago; without the date, the analyst can't assess whether it's current.
Domain 2: Stakeholder and Political Landscape Intelligence
Stakeholder and political landscape intelligence is the knowledge of who holds what positions, what political dynamics operate in different policy areas, and how institutional processes work. This is the knowledge that converts technically sound policy analysis into practically useful policy advice.
STAKEHOLDER AND POLITICAL LANDSCAPE KB
BY STAKEHOLDER / ORGANIZATION:
Organization: [Name]
Type: [ ] Industry association [ ] Advocacy organization [ ] Think tank [ ] Government agency [ ] Legislative office [ ] Other
Policy areas: [What policy areas they're active in]
POSITIONS (DATED):
Issue: [Policy question]
Position: [Where they stand]
Position basis: [Public documents, testimony, prior engagement — not rumor]
As of: [Date — positions change; undated positions may be outdated]
INTERESTS:
Core interests driving their positions: [The underlying motivations]
What would change their position: [What conditions might shift them]
POLITICAL CAPACITY:
Influence: [Their capacity to affect policy outcomes in this area]
Relationships: [Who they're connected to that matters]
Approach: [How they operate — lobbying, litigation, media, grassroots, coalition]
RELATIONSHIP HISTORY:
Interactions: [Prior engagements with this organization]
What's worked: [What approaches have been productive]
What to avoid: [What hasn't worked or created friction]
BY POLITICAL DOMAIN:
Domain: [Legislative / Executive / Regulatory / Judicial — and level]
CURRENT CONFIGURATION (DATED):
Key power holders: [Who matters in this domain, as of when]
As of: [Date — political configurations change]
POLICY DYNAMICS:
What this domain is currently focused on: [Priority issues]
Political constraints: [What limits viable options in this domain]
Policy windows: [Current or anticipated opportunities for policy change]
HOW IT ACTUALLY WORKS:
Formal process: [Official procedure]
Informal reality: [How decisions are actually made]
What I've learned: [Institutional wisdom from experience]
"As of" dates on stakeholder positions is the non-negotiable discipline in stakeholder intelligence. A stakeholder organization's position on a policy question may change when leadership changes, when political circumstances shift, or when the policy in question is modified. Stakeholder intelligence without dates may be accurate for a past political landscape that no longer exists. The analyst who presents current analysis based on outdated stakeholder positions is giving inaccurate advice.
"The underlying motivations" (interests, not positions) is what makes stakeholder intelligence analytically useful rather than simply descriptive. If I know that an industry association opposes a regulation because of compliance cost concerns but not because of opposition to the regulatory goal itself, I can assess whether a phase-in approach or cost-reduction mechanism might shift their position. If I only know "they oppose it," I have no analytical leverage.
Domain 3: Analytical Methods and Institutional Expertise
Analytical methods and institutional expertise is the knowledge of how to conduct policy analysis: the technical methods, the institutional knowledge about how policy processes work, and the professional craft knowledge that makes policy analysis practically useful.
ANALYTICAL METHODS AND EXPERTISE KB
BY ANALYTICAL METHOD:
Method: [e.g., "Cost-benefit analysis" or "Program evaluation interpretation"]
WHEN TO USE:
Appropriate applications: [What this method is well-suited for]
Requirements: [Data, expertise, or resources required]
WHEN NOT TO USE:
Limitations: [What this method can't do]
Common misapplications: [Ways this method is often used incorrectly]
TECHNICAL NOTES:
Key considerations: [What I've learned about applying this well]
Common errors: [What goes wrong in practice]
Resources: [Technical references for this method]
BY POLICY PROCESS / INSTITUTION:
Institution: [Legislative body / regulatory agency / executive office / etc.]
HOW ANALYSIS IS USED:
Decision points: [Where analytical input actually matters]
Format requirements: [What decision-makers in this institution actually use]
Timing: [When to provide analysis to have influence]
HOW TO BE EFFECTIVE:
What works: [What I've observed about effective policy analysis in this context]
What doesn't: [What doesn't land or gets used incorrectly]
Key contacts: [Who to know to be effective here]
HOW IT ACTUALLY WORKS:
Formal process: [Official]
Informal reality: [Actual decision dynamics]
Non-obvious things: [What I've learned that isn't obvious from the outside]
"Common misapplications" is the quality control field. Policy analysis methods — cost-benefit analysis, regression discontinuity, difference-in-differences — are technically demanding and commonly applied incorrectly. The policy analyst who has developed expertise in identifying methodological errors in policy research has a significant quality advantage. Documenting the specific misapplications I've seen is more useful than generic methodological cautions.
Domain 4: Professional Network and Relationship Knowledge
Professional network and relationship knowledge is the institutional and relational intelligence that makes policy analysis practically useful: the academic contacts who can advise on specific research questions, the contacts within relevant government agencies, the peer analysts whose work overlaps with mine, and the relationship history that enables effective professional collaboration.
PROFESSIONAL NETWORK AND RELATIONSHIP KB
BY PROFESSIONAL CONTACT:
Name: [Full name]
Title + Organization: [Current role]
Policy areas: [What they work on]
Expertise: [What they know that's useful to me]
HOW TO ENGAGE:
Best contact method: [Email / phone / in person]
Response time: [How quickly they typically respond]
Best for: [What kinds of requests they're useful for]
RELATIONSHIP HISTORY:
How we know each other: [Context of relationship]
What we've collaborated on: [Prior professional engagement]
What's worked: [What I've found effective in working with them]
PROFESSIONAL INTELLIGENCE:
Their perspective on issues I work on: [How they think about overlapping areas]
What I should know about their work: [Relevant professional context]
Last contact: [Date]
BY EXPERT DOMAIN:
Domain: [A specific subject matter area]
GO-TO EXPERTS:
Expert: [Name + affiliation]
What they're best for: [Specific type of questions they're most useful for]
Relationship: [How to reach them]
The Pre-Engagement Knowledge Retrieval Sequence
Before beginning a new policy analysis engagement:
-
Policy research KB: what do we know about this area? What are the key evidence gaps? Are research entries current (check dates)?
-
Stakeholder KB: who are the key stakeholders in this area? What are their positions (check dates)? What are their underlying interests?
-
Political landscape KB: what's the current political configuration in the relevant domain? What are the political constraints and opportunities?
-
Methods KB: what analytical approaches are appropriate for this engagement? Are there institutional format requirements I know about?
-
Network KB: who are the right academic experts for this area? Are there contacts at relevant agencies or legislative offices who provide useful context?
This retrieval sequence converts the accumulated knowledge base into a head start — replacing the pattern of starting every engagement without the benefit of prior professional experience.
Key Takeaways
-
All policy knowledge entries need dates. Policy knowledge expires; undated entries may be silently outdated when retrieved.
-
Stakeholder positions need "as of" dates and underlying interests. The interest behind a position is more analytically useful than the position itself.
-
"What the evidence doesn't show" is an analytical integrity field, not an admission of weakness. Honest evidence appraisal is more useful to decision-makers than overclaiming.
-
"How it actually works" is the institutional intelligence field. The informal reality of how decisions are made differs from the formal process in virtually every institution.
-
The pre-engagement retrieval sequence converts the knowledge base into a head start. The value of accumulated professional knowledge is realized when it's actually retrieved and used.
Conclusion
The policy analyst's knowledge base organizes four domains: policy research and evidence ("what the evidence doesn't show" as the analytical integrity field; "last reviewed" dates as the currency discipline; policy instrument knowledge with success conditions and failure modes); stakeholder and political landscape intelligence ("as of" dates on all stakeholder positions; interests not just positions; "how it actually works" as the institutional intelligence field); analytical methods and institutional expertise (when to use and when NOT to use; "common misapplications" as quality control; institutional format requirements); and professional network and relationship knowledge (expert domains with go-to contacts; relationship history with what's worked). The pre-engagement retrieval sequence — research, stakeholder positions, political landscape, methods, network — converts accumulated professional knowledge into a practical head start on new work.
Related reading: The Ultimate Guide to Web Clipping.