K
Knowles Training Institute
Guest
- Thread Author
- #1
Knowles Knowledge Centre•Role Mapping
The same five stages look different at each level. This matrix sets out what each one actually looks like as observable behaviour.
Organisations frequently send every document owner on the same procedure writing course and are then surprised that the manual goes stale at the same rate. The cause is usually not the content. It is that the evidence about where a procedure is wrong exists only at the level of the people performing it, while the one change that keeps procedures current — giving the method its own approval route — can only be made at the top.
This guide maps the five stages across three organisational levels, states the observable behaviour at each intersection, and identifies where the obligations genuinely differ.
Decision-support guide•Singapore organisational context•Updated September 2026
EmployeePerforms the steps ManagerOwns and reissues the method LeaderOwns the approval routes
SAME DOCUMENT
About this guide
Published byKnowles Training Institute
PurposePrioritising documentation work by audience level
Use withOne walk through a live procedure, not as a standalone syllabus
The document is the same. What each level can do about it is not.
EmployeePerforms the steps, which nobody can do on their behalf. Can say which instructions are the duty and which are habit, name the steps that have no owner and are being done as a favour, walk a procedure they did not write and record where it stops, and log a departure — but cannot reissue the document, cannot authorise their own departure, and will not log anything while logging reads as a confession.
ManagerOwns and reissues the method. Can sort the sentences into obligation and method, rewrite every step as one role doing one thing, send somebody new to walk it rather than convene a review, authorise a departure within the working day, and reissue the method where the same departure recurs. Each of those costs hours; sending somebody to walk it costs them the comfort of a document that has passed every review.
LeaderOwns the approval routes. A leader decides whether the method shares the obligation’s gate, whether logging a departure is separated from the process for breaching the duty, and whether a reissue is cheaper to obtain than a reminder. Those three decisions determine whether anybody below them can keep a document current, and none of them is a drafting matter.
A manager taught the author’s version of this method will write an excellent procedure and watch it go stale on a quarterly approval route they do not control.
Five stages by three levels. Each cell describes observable behaviour — what somebody at that level visibly does when the stage is being worked properly.
Stage
Employee
Manager
Leader
Split the why
Can say which instructions are the duty and which are current habit
Sorts the sentences and gives each document a single owner
Gives the method its own approval route, separate from the duty
Name the doer
Names the steps with no owner that are performed as a favour
Rewrites each step as one role doing one thing in one place
Checks that every named role survived the last reorganisation
Walk it once
Walks a procedure they did not write and records every stop
Sends somebody new to walk it instead of convening a review
Requires a walk after each system change, not once a year
Log the break
Logs a departure, having been told plainly it is not a confession
Authorises a departure within the working day, not the quarter
Separates the register from the process for breaching the duty
Move the line
Finds out what changed after they logged something
Reissues the method where the same departure recurs three times
Makes a reissue cheaper to obtain than a compliance reminder
Read down a column for a level’s obligations. Read across a row to see why a manual cannot be kept current at one level alone.
Three transitions cause most of the difficulty, and none of them is solved by more content.
1
The move from doing the work to owning the document changes the unit from “can I do this” to “can somebody who has never done it do this.” A newly appointed owner who performed the work expertly will write a procedure that assumes everything they know, because the assumed knowledge is invisible to them and shared by about four people.
The stage has not changed. Its point of application has. Development at this transition is mostly one uncomfortable act: sending somebody who does not know the work to attempt the document, and writing down every place they stopped.
2
The move to senior leadership shifts the unit again, from one document to the approval machinery. A leader can insist on excellent procedures and will still preside over a stale manual, because the system names sit in governed documents and nobody raises a governance item to change a platform.
This transition is where the first stage matters most, and the leader’s version of it is not sorting sentences. It is giving the method its own owner and its own route, which converts every future system change from a governance exercise into an afternoon’s work and is the single most durable change available in this method.
3
For most capabilities the middle level holds the most leverage: a manager can create the conditions for a team and operate within what the organisation allows. Here the middle cell is the weakest of the three. The only person who knows that step five cannot be performed is the person who tried, and the only person who can stop the method sharing the obligation’s approval route is a leader. The procedure’s owner sits between the evidence and the remedy and controls neither.
The practical consequence is that this is the one method in the series where training the document owners alone reliably fails. They will write better procedures, which go stale at the same rate, because the stale-making mechanism is an approval route and the stale-detecting mechanism is a register that junior staff will not use. Both ends have to move, and the middle can only ask.
Do not read the employee column as a lesser version
The three levels are not stages of increasing skill. An operator who says that step five has been impossible since the upgrade has supplied the only finding that exists, and no amount of seniority produces it. Treating the leader column as “advanced” produces work that is irrelevant to the people performing the steps.
The matrix is a scoping tool. Used properly it narrows the work rather than expanding it.
Start from the step that was not performed, not the grid. Name the step and the substitute behaviour, then locate the one or two cells describing who could change the situation. Work built from a whole column trains the level that neither holds the evidence nor controls the route.
Check the level before the behaviour. When a register stays empty, establish whether the constraint sits in the leader’s cell rather than anybody’s willingness. Teaching staff to log departures will not help where logging one is routed through the same process as breaching the duty.
Expect different formats, not just different content. Employee-level behaviour responds to one walk and a plain statement that logging is not a confession. Manager-level behaviour needs the sorting exercise on their own document, including the discovery of how much of it is method. Leader-level behaviour is usually better served by changing one committee’s terms of reference than by any programme.
A practical sequence: diagnose the cause using how to identify whether your procedures are being followed, locate the affected cells in this matrix, then scope the work to those cells only.
Should document owners and the people performing the steps attend together?Usually yes for the third stage, and separately for the rest. The walk works best with both present, because the owner has to watch somebody stop at step five rather than be told about it afterwards. The other stages diverge: sorting sentences is an owner’s task, and a session in which staff are asked to log departures is pointless until a leader has separated logging from discipline.
?
Which behaviour matters most for new document owners?Sending somebody new to walk it. In matrix terms, the manager’s cell on the third stage — a change in how they test rather than in how they draft. An owner who watches a new joiner stop at step five has the whole finding, and has done nothing else.
?
How does this matrix relate to Singapore’s Critical Core Skills?Critical Core Skills defines three proficiency levels — Basic, Intermediate and Advanced — describing increasing responsibility, autonomy and complexity. Those levels relate to, but are not identical with, organisational level. The framework reaches no stage of this method at the third row: none of the sixteen skills describes performing a written procedure in the live environment in order to find out where it is wrong.
?
Can one person sit at different levels on different stages?Commonly, yes. An owner may be at leader level on sorting sentences and at employee level on authorising a departure, and the second is usually what keeps their register empty. Assuming a uniform level across the five stages is one of the more frequent scoping errors.
?
Does this replace a competency framework?No. A competency framework defines the standard an organisation holds people to, usually with assessment attached. This matrix is a scoping aid for deciding whose behaviour has to change for a document to keep describing the work, and it carries no assessment weight.
The five stages do not change with seniority. What changes is which part of the document’s life a person can act on:
EmployeeWhether it can be done
ManagerWhat it says
LeaderHow fast it can change
Most disappointing documentation training traces back to effort aimed at the document owners, who hold neither the evidence about their procedure nor the route to reissue it quickly.
Naming the cell before commissioning the work removes most of that risk, and usually points at a committee’s terms of reference rather than at a course.
The underlying five-stage structure is set out in what separates a policy from a procedure. Organisations that have identified the level and the stage they need can review the Writing Policy and Procedure Documents Course in Singapore, checking that the design matches the level that controls the approval route rather than the level that drafts the steps.
Published by Knowles Training Institute. Evidence base: SkillsFuture Singapore.
The post A Policy and Procedure Writing Matrix for Employees, Managers and Leaders appeared first on Corporate Training Courses in Singapore.
A Policy and Procedure Writing Matrix for Employees, Managers and Leaders
The same five stages look different at each level. This matrix sets out what each one actually looks like as observable behaviour.
Organisations frequently send every document owner on the same procedure writing course and are then surprised that the manual goes stale at the same rate. The cause is usually not the content. It is that the evidence about where a procedure is wrong exists only at the level of the people performing it, while the one change that keeps procedures current — giving the method its own approval route — can only be made at the top.
This guide maps the five stages across three organisational levels, states the observable behaviour at each intersection, and identifies where the obligations genuinely differ.
Decision-support guide•Singapore organisational context•Updated September 2026
EmployeePerforms the steps ManagerOwns and reissues the method LeaderOwns the approval routes
SAME DOCUMENT
About this guide
Published byKnowles Training Institute
PurposePrioritising documentation work by audience level
Use withOne walk through a live procedure, not as a standalone syllabus
Why one programme for everyone underperforms
The document is the same. What each level can do about it is not.
EmployeePerforms the steps, which nobody can do on their behalf. Can say which instructions are the duty and which are habit, name the steps that have no owner and are being done as a favour, walk a procedure they did not write and record where it stops, and log a departure — but cannot reissue the document, cannot authorise their own departure, and will not log anything while logging reads as a confession.
ManagerOwns and reissues the method. Can sort the sentences into obligation and method, rewrite every step as one role doing one thing, send somebody new to walk it rather than convene a review, authorise a departure within the working day, and reissue the method where the same departure recurs. Each of those costs hours; sending somebody to walk it costs them the comfort of a document that has passed every review.
LeaderOwns the approval routes. A leader decides whether the method shares the obligation’s gate, whether logging a departure is separated from the process for breaching the duty, and whether a reissue is cheaper to obtain than a reminder. Those three decisions determine whether anybody below them can keep a document current, and none of them is a drafting matter.
A manager taught the author’s version of this method will write an excellent procedure and watch it go stale on a quarterly approval route they do not control.
The policy and procedure matrix
Five stages by three levels. Each cell describes observable behaviour — what somebody at that level visibly does when the stage is being worked properly.
Stage
Employee
Manager
Leader
Split the why
Can say which instructions are the duty and which are current habit
Sorts the sentences and gives each document a single owner
Gives the method its own approval route, separate from the duty
Name the doer
Names the steps with no owner that are performed as a favour
Rewrites each step as one role doing one thing in one place
Checks that every named role survived the last reorganisation
Walk it once
Walks a procedure they did not write and records every stop
Sends somebody new to walk it instead of convening a review
Requires a walk after each system change, not once a year
Log the break
Logs a departure, having been told plainly it is not a confession
Authorises a departure within the working day, not the quarter
Separates the register from the process for breaching the duty
Move the line
Finds out what changed after they logged something
Reissues the method where the same departure recurs three times
Makes a reissue cheaper to obtain than a compliance reminder
Read down a column for a level’s obligations. Read across a row to see why a manual cannot be kept current at one level alone.
Where the levels genuinely diverge
Three transitions cause most of the difficulty, and none of them is solved by more content.
1
From performing to owning the method
The move from doing the work to owning the document changes the unit from “can I do this” to “can somebody who has never done it do this.” A newly appointed owner who performed the work expertly will write a procedure that assumes everything they know, because the assumed knowledge is invisible to them and shared by about four people.
The stage has not changed. Its point of application has. Development at this transition is mostly one uncomfortable act: sending somebody who does not know the work to attempt the document, and writing down every place they stopped.
2
From owning a method to owning the route
The move to senior leadership shifts the unit again, from one document to the approval machinery. A leader can insist on excellent procedures and will still preside over a stale manual, because the system names sit in governed documents and nobody raises a governance item to change a platform.
This transition is where the first stage matters most, and the leader’s version of it is not sorting sentences. It is giving the method its own owner and its own route, which converts every future system change from a governance exercise into an afternoon’s work and is the single most durable change available in this method.
3
The evidence is at the bottom and the remedy is at the top
For most capabilities the middle level holds the most leverage: a manager can create the conditions for a team and operate within what the organisation allows. Here the middle cell is the weakest of the three. The only person who knows that step five cannot be performed is the person who tried, and the only person who can stop the method sharing the obligation’s approval route is a leader. The procedure’s owner sits between the evidence and the remedy and controls neither.
The practical consequence is that this is the one method in the series where training the document owners alone reliably fails. They will write better procedures, which go stale at the same rate, because the stale-making mechanism is an approval route and the stale-detecting mechanism is a register that junior staff will not use. Both ends have to move, and the middle can only ask.
Do not read the employee column as a lesser version
The three levels are not stages of increasing skill. An operator who says that step five has been impossible since the upgrade has supplied the only finding that exists, and no amount of seniority produces it. Treating the leader column as “advanced” produces work that is irrelevant to the people performing the steps.
Using the matrix to set priorities
The matrix is a scoping tool. Used properly it narrows the work rather than expanding it.
Start from the step that was not performed, not the grid. Name the step and the substitute behaviour, then locate the one or two cells describing who could change the situation. Work built from a whole column trains the level that neither holds the evidence nor controls the route.
Check the level before the behaviour. When a register stays empty, establish whether the constraint sits in the leader’s cell rather than anybody’s willingness. Teaching staff to log departures will not help where logging one is routed through the same process as breaching the duty.
Expect different formats, not just different content. Employee-level behaviour responds to one walk and a plain statement that logging is not a confession. Manager-level behaviour needs the sorting exercise on their own document, including the discovery of how much of it is method. Leader-level behaviour is usually better served by changing one committee’s terms of reference than by any programme.
A practical sequence: diagnose the cause using how to identify whether your procedures are being followed, locate the affected cells in this matrix, then scope the work to those cells only.
Frequently asked questions
?Should document owners and the people performing the steps attend together?Usually yes for the third stage, and separately for the rest. The walk works best with both present, because the owner has to watch somebody stop at step five rather than be told about it afterwards. The other stages diverge: sorting sentences is an owner’s task, and a session in which staff are asked to log departures is pointless until a leader has separated logging from discipline.
?
Which behaviour matters most for new document owners?Sending somebody new to walk it. In matrix terms, the manager’s cell on the third stage — a change in how they test rather than in how they draft. An owner who watches a new joiner stop at step five has the whole finding, and has done nothing else.
?
How does this matrix relate to Singapore’s Critical Core Skills?Critical Core Skills defines three proficiency levels — Basic, Intermediate and Advanced — describing increasing responsibility, autonomy and complexity. Those levels relate to, but are not identical with, organisational level. The framework reaches no stage of this method at the third row: none of the sixteen skills describes performing a written procedure in the live environment in order to find out where it is wrong.
?
Can one person sit at different levels on different stages?Commonly, yes. An owner may be at leader level on sorting sentences and at employee level on authorising a departure, and the second is usually what keeps their register empty. Assuming a uniform level across the five stages is one of the more frequent scoping errors.
?
Does this replace a competency framework?No. A competency framework defines the standard an organisation holds people to, usually with assessment attached. This matrix is a scoping aid for deciding whose behaviour has to change for a document to keep describing the work, and it carries no assessment weight.
Conclusion
The five stages do not change with seniority. What changes is which part of the document’s life a person can act on:
EmployeeWhether it can be done
ManagerWhat it says
LeaderHow fast it can change
Most disappointing documentation training traces back to effort aimed at the document owners, who hold neither the evidence about their procedure nor the route to reissue it quickly.
Naming the cell before commissioning the work removes most of that risk, and usually points at a committee’s terms of reference rather than at a course.
The underlying five-stage structure is set out in what separates a policy from a procedure. Organisations that have identified the level and the stage they need can review the Writing Policy and Procedure Documents Course in Singapore, checking that the design matches the level that controls the approval route rather than the level that drafts the steps.
Published by Knowles Training Institute. Evidence base: SkillsFuture Singapore.
The post A Policy and Procedure Writing Matrix for Employees, Managers and Leaders appeared first on Corporate Training Courses in Singapore.
Last edited: