Chapter 1
Choose a capability
Define the skill you want to practise and the evidence an employer could inspect.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Write a learning goal and current baseline. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 2
Find a bounded project
Choose a problem small enough to supervise and safe enough to learn on.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Create a role and scope before starting. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 3
Work with a real organisation
Agree purpose, communication, confidentiality, ownership and feedback.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Use a written volunteering or project agreement. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 4
Build professional habits
Plan work, record decisions, ask for review and respond to errors.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Keep a weekly evidence and reflection log. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 5
Create portfolio evidence
Use only consented outputs and explain your precise contribution.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Write each sample as context-action-evidence-learning. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 6
Request a fair reference
Ask for factual confirmation of role, dates, behaviours and outputs.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Give the referee a verified role summary, not drafted praise. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.