Productivity & Collaboration
For tools, time management, communication, teamwork.
-
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.
-
When everything is urgent: how to have a useful priorities conversation
Turn competing urgent requests into a clear decision, with questions, practical wording and a completed priority conversation note.
-
How to ask for learning time at work, with a practical one-page plan
Prepare a clear request for learning time, with a six-part plan covering practice, workload trade-offs, support and follow-up.
-
The security update cannot wait: how to prioritise urgent fixes
Use a fictional delivery scenario to turn an urgent vulnerability alert into an owned plan for mitigation, testing and stakeholder communication.
-
Is your AI summary reliable? Build a five-case evaluation pack
A five-case exercise for checking AI summaries without letting invented actions or deadlines slip into a handover.
-
Your sprint is full of finished code. Why is nothing ready to release?
A practical queue review for sprint planning: inspect waiting work, identify the next action and agree one team experiment.
-
How to mentor junior developers when AI can finish the task for them
A practical mentoring session that checks understanding, makes questions easier to ask and builds independent problem-solving.
-
Stop reopening the same product decision: use a six-part decision log
Make recurring product discussions actionable with a clear question, decision owner, evidence and review trigger.
-
From Developer to Product Owner: a practical transition plan
You enjoy building software, but you are becoming more interested in the decisions around it. Which problem deserves attention? What should happen first? How will anyone know whether the feature helped? Those questions…
