-
Before you announce a feature: check who can actually use it
Before sending a release announcement, check which users can complete the promised task. Use a fictional worked example and a reusable availability note.
-
When the expert is away: a 30-minute handover rehearsal for tech teams
Find the gaps in a routine handover before they interrupt delivery, using a supported rehearsal, a fictional example and a reusable observation sheet.
-
Your app says ‘file deleted’. What does that actually mean?
Separate expired access, removed active files and recoverable copies, then use a practical worksheet to check what your product can honestly promise.
-
How to write an accessibility bug report a developer can reproduce
Turn an accessibility concern into a clear, reproducible issue with a worked example, a reporting template and a practical retest plan.
-
JavaScript recursion stuck? Trace the work left before changing the code
A stopping condition is only useful when each recursive call moves towards it. Practise with a small JavaScript example and a reusable trace sheet.
-
Digital change that works: stakeholder engagement and product adoption
Plan digital change around people, dependencies and real tasks, with a practical readiness check for stakeholder engagement and product adoption.
-
Better requirements: working with developers, standards and suppliers
Learn how to clarify requirements with developers and suppliers, make standards usable and plan for the failures an integration must handle.
-
How to connect product strategy to measurable value
Connect organisational priorities to product decisions, define meaningful measures and review benefits with a practical one-page strategy and value note.
-
Work keeps carrying into the next sprint? Investigate before changing the estimate
Use three recent unfinished items to understand what changed, then agree one focused experiment without blaming the team or lowering quality.
-
How to contribute to a technical discussion when you do not know every term
Ask useful questions in technical meetings, connect the discussion to user needs and record decisions without pretending to understand every detail.
