Building First Company Office Policy Manual
Established the company's first official policy system. A clear, logical information architecture built from scratch
Client
Northpoint Asset Management
Role
UX Design Lead, research, systems design, content strategy & designer, internal UX thinking
Duration
3 months
Year
2024
01 — Brief
Project Brief
The company had no existing office policy manual for new or current team members. Expectations were undocumented, inconsistent, and dependent on individual managers. I identified this gap and led the creation of a comprehensive Office Policy Manual from scratch, applying UX and design thinking principles to define, design, and document a clear internal system.
02 — Challenge
The Challenge
The challenge was not organizing existing content it was defining the rules, structure, and logic of the system itself while balancing fairness, usability, and enforceability. Without a centralized policy system:
Key pain points
- 01New hires lacked clarity on expectations and norms
- 02Managers enforced rules inconsistently
- 03Institutional knowledge lived in peoples heads
- 04Routine issues escalated unnecessarily
- 05Operational and compliance risk increased with growth
"Designing the policy manual revealed that most operational friction comes from unclear or assumed expectations, not misuse of rules. Treating internal documentation as a user experience rather than a compliance artifact improved clarity, adoption, and trust across teams."
03 — Solution
The Solution
I designed a centralized Owner Onboarding System that guided owners through a clear, step-by-step digital flow. The system consolidated legal agreements, property details, financial preferences, and communication expectations into a single experience removing ambiguity and reducing the need for manual follow-ups.
04 — Process
Design Process
Discovery & Research
Interviewed managers to surface undocumented rules. Identified recurring questions, conflicts, and edge cases. Audited operational and compliance risk areas. Benchmarked industry standards and best practices.
Define
Reframed the problem as a clarity and consistency gap, not a documentation task. Design Question: How might we create a policy system that makes expectations explicit, reduces ambiguity, and supports fair, consistent decisions?
Structure & Information Architecture
Defined a policy taxonomy from zero. Grouped policies by behavioral and operational context. Established a predictable hierarchy and navigation model.
Design & Prototype Phase
Wrote policies in plain language with authoritative tone. Separated principles from procedures. Designed for scanability and quick reference. Embedded if/then logic for common scenarios.
Validation & Iteration
Tested flows against real-world edge cases. Adjusted language to remove ambiguity. Ensured consistency across sections. The final system was designed to scale, adapt, and remain usable over time.
05 — Impact
Impact & Results
Established the company's first official policy system
Plain-language policies written for comprehension, not legal density
Defined escalation paths and exception handling
The result was a policy system employees could actually reference and managers could confidently enforce
Improved clarity and confidence for new hires
Enabled managers to apply policies consistently
Reduced ambiguity-driven conflict and escalation
Created a scalable operational foundation for growth
06 — Artifacts
Visual Artifacts
