INF2170H Chap.7 IA Strategy, Governance and Maintenance
IA Strategy, Governance and Maintenance
Turn a proposal into a maintained system
The published strategy week pairs information architecture strategy with maintenance and governance work. This chapter links structural options to mission, resources, users and content, then assigns decision rights and review triggers.
It avoids invented maturity scores and compares options through explicit consequences.
Govern the shared seams
Shared fields, vocabularies, source of truth rules and retirement decisions deserve clear authority because many routes depend on them. Local presentation can remain flexible within those boundaries.
A strategy becomes actionable when it has sequencing, ownership, preserved rationale and a repeatable verification method.
Assign authority to specific structural decisions
Content ownership, schema stewardship and platform operation are related but distinct.
A subject specialist can judge factual accuracy, an information architect can maintain field and vocabulary rules, and a platform owner can implement validation and indexing. One person may hold several roles, but the decision rights should remain visible. Name who proposes, approves, implements and verifies each significant change.
Govern according to shared consequence.
Core object types, fields, controlled terms, source of truth and retirement rules affect many routes and deserve consistent control. Local presentation can remain flexible when variation does not break retrieval or understanding. Centralisation is not automatically better.
Preserve meaningful community language through synonyms or scoped extensions where forcing one term would erase context.
Use evidence triggers to maintain the architecture
A review should begin when content, audience, policy, ownership or use changes. New object classes, repeated query failures, accumulating category exceptions and moved responsibilities are practical triggers.
Pair the trigger with a named owner, preserved rationale and verification method. That structure prevents a review calendar from becoming ritual while silent drift continues between meetings.
Sequence work through dependencies. Resolve authoritative content and ownership before polishing navigation built on duplicates. Stabilise shared metadata before tuning search against inconsistent values.
Compare strategy options through consequences for priority tasks, accessibility, maintenance and capacity rather than invented numerical maturity levels. The selected option should include the condition that would make another path preferable later, keeping the strategy open to evidence rather than protecting it from revision.
What this chapter covers
- 01
Information strategy
- 02
Decision rights
- 03
Schema ownership
- 04
Governance scope
- 05
Review triggers
- 06
Maintenance evidence
Worked example · free
Govern a controlled vocabulary
- 2Define the shared concept and scope.
- 3Assign proposal and approval roles.
- 2Set a review trigger and verification.
Key terms
- Decision Right
- Decision Right assigns authority to propose, approve, implement or review a structural change.
- Governance Trigger
- Governance Trigger starts review when content, audience, policy, ownership or evidence changes.
- Source Truth
- Source Truth identifies the authoritative content object when several access routes or placements exist.
IA Strategy, Governance and Maintenance FAQ
What belongs in information architecture governance?
Govern shared structural decisions whose inconsistency affects retrieval, navigation or maintenance: object types, field definitions, controlled terms, category criteria, source of truth and retirement rules. Allow local presentation choices where variation does not break those dependencies.
Why are review triggers useful?
Calendar reviews can become ritual. Event triggers respond when a new object class appears, policy changes, query patterns shift, ownership moves or a category accumulates exceptions. Pair each trigger with evidence and an accountable reviewer so review produces an action.
How can options be compared without a scoring model?
State the problem, evidence and constraints, then compare consequences for priority tasks, content fit, accessibility, maintenance and organisational capacity. Select an option through a transparent narrative and name the condition that would make another option preferable later.
Assessment move
For each proposal, write the structural decision, affected systems, owner, trigger and verification method. Compare two options through consequences rather than invented weights. Practise distinguishing shared schema control from local presentation flexibility. Draw a decision route from observed problem to evidence, proposed structure, implementation responsibility and review.
Name every consumer that inherits a changed term or category, including navigation, search, reports and local publishing tools. Where teams need different displays, identify the shared semantic rule that must remain stable and the presentation choices that can vary. Create a small governance record with an owner, contributor, approver, rationale, effective date and review trigger.
Test the record against staff turnover and a new content type: another person should be able to recover why the rule exists and know when to reconsider it. Compare alternative designs through traceable consequences for users, operations and maintenance, not through invented precision. Add a rollback or migration note where a change affects existing records.
Finish each proposal with one verification method and one monitoring signal. Strategy becomes credible when a design choice can survive implementation, change and disagreement without depending on undocumented memory.
