Policy is the Common Language in Organisations – Write It. Align It. Own It. 政策是組織的共同語言 – 撰寫・對齊・主導

Deane Lam
Apr 23
10 min read

Updated: Apr 24

📌 繁體中文版本請見下方 / Traditional Chinese version available below.

Every organisation has a strategy. But strategy only works when people, culture, processes, and policies are aligned.

People do the work. Culture shapes how they work together. Processes make the work flow. And policy is the common language that holds it all in place.

When policies are clear, people know what to do. When policies are missing or inconsistent, people guess – and they usually guess wrong.

The core principle is simple: clear, aligned, and easy to follow.

The approach in this guide – clear, simple, and practical – works for any policy. From core values to company-wide policies (like HR and Finance) to department policies – the same framework applies. Company-wide policies take much longer and involve legal review, multiple stakeholders, and formal approval. Department policies focus on your team's daily operations. Same framework, different scale.

Why Your Organisation Needs Department Policies

Policy is your organisation's common language.

Without written policies, different teams follow different rules. New staff guess what to do. Managers make inconsistent decisions. Cross-department collaboration becomes frustrating.

When policies are written down and stored in one place:

New team members learn faster
Existing teams work smoother
Leaders make decisions with confidence

Company-Wide vs. Department Policies

Your department policy can add to a company policy. It cannot contradict it.

Company-wide policies such as HR, Finance, and IT apply to everyone. Department policies apply only to your team. For example:

Company policy: "Overtime must be approved by the department head."
Your department policy can add: "Overtime requests must be submitted to the supervisor by Thursday noon."
But your department policy cannot say: "Supervisors can approve their own overtime."

Why? Company policies exist for legal compliance, fairness across teams, audit control, and accountability. A department cannot override them without breaking the system.

What if operational needs require faster approval?

If operational needs require faster approval, HR must first agree to amend the policy or create a formal exception process. Again, company policies exist for legal, regulatory, and fairness reasons – so every team follows the same rules. Operational needs do not override company policy. If the policy does not fit, follow the proper process – do not bypass it.

So before you write, check three things:

Does a company policy already cover this?
Does my draft contradict any company policy?
For people or money rules, check with HR or Finance.

Policy vs. Procedure – A Simple Distinction

What exactly is a policy? And what is a procedure? Understand this:

	Policy	Procedure
What it is	A rule or standard	Step-by-step instructions
Answers	"What must be done?"	"How exactly do we do it?"
Example	"All products must be inspected before shipment"	"Step 1: Take sample. Step 2: Weigh. Step 3: Record."
Who writes it	Department head	Team member or supervisor

Most organisations need policies first. Procedures can come later.

You Can Draft One Policy in 15 Minutes

You do not need weeks. You need five questions.

Ask yourself (or a trusted team leader/manager who knows the daily work):

What is one rule your team follows every day?
Why does this rule exist?
Who does it apply to?
What happens if someone breaks it?
Is there any exception?

Write the answers. Turn them into 1–2 sentences. That is one draft policy. You can then use it to align with company policy and across departments. For example:

Factory Department

Policy: Equipment Maintenance - All equipment must be maintained according to schedule. Every maintenance check must be signed and dated.

Applies to: Production and maintenance teams

Cafe Outlet

Policy: Customer Complaints - All customer complaints must be acknowledged within 10 minutes. Escalate to manager if not resolved within 30 minutes.

Applies to: All service staff

Logistics

Policy: Delivery Documentation - Every delivery must have a completed manifest signed by the driver and receiving party.

Applies to: Drivers and logistics coordinators

Repair Team

Policy: Repair Prioritisation - Critical repairs (safety or production stop) must be responded to within 2 hours. Standard repairs within 24 hours.

Applies to: Repair team

Cross-Department Alignment – Why It Matters

Alignment does not mean every department has the same policy. It means policies do not contradict each other.

When each department writes its own policies in isolation, you create a new problem: inconsistent rules across teams.

For example:

Logistics policy says delivery drivers must wait for signature
Cafe policy says staff are too busy to sign during peak hours
Result: conflict, delay, and frustration

Review your department policy with the other department heads whose teams work closely with yours. Discuss any overlaps or conflicts, especially where work handoffs happen. Agree on a consistent approach, update your policy if needed, and store all policies in a central library for department heads to access.

A simple rule for alignment:

Your policy should not make another department's job harder.

Before finalising a policy, ask: "Who else does this affect? Have we talked to them?"

Aligning People and Culture in Your Policies

If a policy would make you feel disrespected or distrusted as an employee, rewrite it.

Policies are not just about rules and compliance. They actually shape how people behave and what kind of culture you build.

If your policies are too rigid, people stop thinking for themselves. If your policies are unclear, people make up their own rules. If your policies are unfair, people lose trust.

Five Questions to Check People and Culture Alignment

Does this policy treat people fairly?
Unfair policies create resentment and low morale.
Does this policy encourage the right behaviour?
Policies should reward what you want to see more of.
Does this policy reflect our company values?
If your value is "respect", your policies must show respect.
Can people easily understand and follow this policy?
Complicated policies frustrate people and get ignored.
Does this policy allow for exceptions when needed?
Rigid policies break trust and common sense.

Culture-Focused

Policy: No Blame for Raising Issues - Any employee who reports a safety, quality, or ethical concern in good faith will not be penalised, even if the concern turns out to be unfounded.
Why this works: It encourages people to speak up without fear. This is the foundation of a healthy culture.

People-Focused

Policy: Self-Learning - All employees have access to the company's online learning library. No approval is required to access any course. Managers cannot question or restrict an employee's choice of learning.
Why this works: It removes barriers to development. People can learn what interests them, not just what their manager approves.

Before finalising a policy, ask: "Would I want to work under this rule?"

Ownership and Accountability

As a department head, you can work with a trusted team leader or manager who knows the daily operation best to work out the draft with you. But you remain accountable for reviewing, approving, and aligning it with other departments.

You decide who assists you. Not the whole team.
You review and approve everything before it goes anywhere.
You share the policy with other departments.
You communicate the policy to your team – when you are ready, in your own way.

This is not a team exercise. This is a leader-led process with limited, controlled support.

Delegate the drafting. Not the accountability.

For policies related to legal, regulatory, or high-risk areas (e.g., safety, data protection, financial controls), always involve HR, legal, or compliance before finalising. This approach works well for mid-sized organisations. Larger or highly regulated organisations will need additional review.

What to Do Next

You do not need to do everything at once. One policy at a time.

When policies are clear, people know what to do. When policies are aligned across departments, collaboration works. When policies respect both legal requirements and operational reality, the organisation can move forward with confidence.

Start small. One policy at a time. Keep it simple. Align with other departments. And never forget: company policies set the floor. Department policies can raise the bar – but cannot dig under it.

That is how we build a foundation that supports our strategy.

政策是組織的共同語言 – 撰寫・對齊・主導

每個組織都有策略。但策略要成功，必須靠人才、文化、流程及政策互相對齊。

人才負責執行工作。文化影響他們如何合作。流程讓工作順暢運作。而政策是將一切凝聚起來的共同語言。

當政策清晰，員工就知道該做什麼。當政策缺失或不一致，員工就會猜測 – 而且通常會猜錯。

核心原則很簡單：清晰、對齊、容易執行。

本指南的方法 – 清晰、簡單、實用 – 適用於任何政策。從核心價值到公司層面政策（如人力資源、財務），再到部門政策 – 相同框架皆可應用。公司層面政策需時更長，涉及法律審核、多位持份者及正式審批。部門政策則專注於你團隊的日常運作。相同框架，不同規模。

為什麼你的組織需要部門政策

政策是組織的共同語言。

沒有書面政策，不同團隊就會跟隨不同的規則。新同事靠猜測做事。主管做出不一致的決定。跨部門協作變得令人沮喪。

當政策寫下來並存放在同一地方：

新同事學習更快
現有團隊運作更順暢
領導者能更有信心做決策

公司政策 vs. 部門政策

你的部門政策可以補充公司政策，但不能與之矛盾。

公司政策（如人力資源、財務、IT）適用於所有人。部門政策只適用於你的團隊。

例子：

公司政策	你的部門政策可以補充	但不能
加班必須由部門主管批准	加班申請必須在星期四中午前提交給主管	主管可以自行批准自己的加班

為什麼？ 公司政策的存在是為了法律合規、團隊間的公平性、審計控制及問責。任何部門都不能為了方便而繞過公司政策，否則整個制度就會崩潰。

如果營運需要更快的批准怎麼辦？

如果營運上需要更快的批准，必須先由人力資源部同意修改政策，或建立正式的例外程序。公司政策的存在是為了法律、監管及公平性原因 – 確保每個團隊都遵守相同的規則。營運需要不能凌駕公司政策。如果政策不符合實際運作，請跟隨正式程序調整 – 不要繞過它。

動筆之前，先檢查三件事

是否已有公司政策涵蓋這個範圍？
我的草稿是否與任何公司政策矛盾？
如果涉及人事或財務規則，先與人力資源部或財務部確認。

政策 vs. 程序 – 簡單區分

	政策	程序
是什麼？	規則或標準	逐步操作步驟
回答什麼問題？	「必須做什麼？」	「具體怎麼做？」
例子	「所有產品出貨前必須檢查」	「第一步：取樣。第二步：磅重。第三步：記錄。」
誰負責撰寫？	部門主管	團隊成員或組長

大多數組織需要先有政策。程序可以之後再補充。

15分鐘內草擬一項部門政策草稿

你不需要花幾星期。你只需要五條問題。

問自己（或一位熟悉日常運作的團隊主管/經理）：

你的團隊每天遵守的一條規則是什麼？
這條規則為什麼存在？
適用於哪些人？
如果有人違反，會有什麼後果？
有沒有任何例外情況？

寫下答案，濃縮成1至2句話，這就是一項政策草稿。然後你可以用它來對齊公司政策及跨部門協作。實例:

工廠部門

政策：設備保養 – 所有設備必須按時保養。每次檢查必須簽名及寫上日期。

適用對象：生產及保養團隊

咖啡店

政策：客戶投訴 – 所有客戶投訴必須在10分鐘內確認收到。30分鐘內未能解決，需上報經理。

適用對象：所有前線服務人員

物流部門

政策：送貨文件 – 每次送貨必須有完整的貨單，並由司機及收貨方簽署。

適用對象：司機及物流協調員

維修團隊

政策：維修優先次序 – 緊急維修（影響安全或生產）必須在2小時內回應。一般維修在24小時內回應。

適用對象：維修團隊

跨部門對齊 – 為什麼重要

對齊不代表每個部門都要有相同的政策。對齊的意思是政策之間不會互相矛盾。

當每個部門各自撰寫自己的政策時，會產生一個新問題：跨部門規則不一致。

例子：

物流政策說：送貨司機必須等待簽收
咖啡店政策說：繁忙時間員工無法即時簽收
結果：衝突、延誤、沮喪

與工作緊密合作的部門主管一起檢視你的部門政策。討論任何重疊或衝突的地方，尤其是工作交接的環節。達成一致的做法，按需要更新政策，然後將所有政策存放在中央政策庫，供各部門主管查閱。

一個簡單的對齊規則：

「你的政策不應該讓另一個部門的工作更難做。」

在定稿前問自己：「還有誰會受影響？我們跟他們談過了嗎？」

讓政策對齊人才與公司文化

如果一項政策會讓你覺得作為員工不被尊重或不信任，請改寫它。

政策不只是關於規則和合規。它們實際上會塑造員工的行為和公司文化。

如果政策太死板，員工會停止獨立思考。如果政策不清楚，員工會自行創造規則。如果政策不公平，員工會失去信任。

五個問題檢查政策是否對齊人才與公司文化

問題	為什麼重要
這項政策是否公平對待員工？	不公平的政策會造成不滿和士氣低落
這項政策是否鼓勵正確的行為？	政策應該獎勵你想看到更多的事情
這項政策是否反映公司的價值觀？	如果你的價值觀是「尊重」，政策就必須展現尊重
員工能否容易理解並遵守這項政策？	複雜的政策令人沮喪，最終被忽視
這項政策是否允許必要時的例外？	死板的政策破壞信任和常識