Policy Development
Policy Development is the deliberate process of turning a recurring problem or risk into a written rule everyone can be held to, built through research, drafting and real consultation rather than a memo from the top.
Boxes link in sequence, carrying a problem from first flagged to a fully adopted rule, with consultation sitting squarely in the middle.
Reach for this when…
- The same dispute keeps landing on your desk because there is no rule to point to.
- A regulator or auditor asks for a written policy you do not have.
- Different managers are making the same call three different ways.
How to run it
- Name the problem or risk the policy needs to solve.
- Research how it is handled elsewhere and what the law requires.
- Draft the policy in plain language with whoever will have to live by it.
- Test it against real cases before you sign it off.
- Publish it, train people on it, and set a date to revisit it.
A worked example
Situation. Karim Belhaj ran a small agricultural finance cooperative in Tunis, Tunisia, where loan officers were each waiving late fees on their own judgement.
Applied. He named the real problem, inconsistent waivers rather than lax officers, then drafted the late-fee policy with three of his loan officers instead of alone in his office.
Result. Waivers dropped to a handful of genuinely hard cases, and officers stopped taking complaints personally because the rule, not them, made the call.
The catch
A policy written by one person in isolation gets ignored the moment it is inconvenient. Policy Development is also slow by design, so it is the wrong tool for a decision you need this week, and a policy nobody revisits calcifies into a rule nobody remembers the reason for.
If the people bound by the policy never saw a draft, expect it to be quietly ignored within a year.