-
An urgent API change: seven questions to plan the work before you rush
An urgent change needs more than a deadline. Work through seven questions about purpose, scope, capacity and sequencing before committing your team.
-
One customer asks for a feature: check whether it belongs in the shared product
Separate a customer request into supported configuration, a shared product change or account-specific work, using a practical example and review note.
-
The same problem is back in your retrospective: turn the lesson into a change
Writing down a lesson does not show that the team has learned it. Follow one reporting problem from evidence to a change, then check whether the change helped.
-
Followership in tech: improve team decisions without a leadership title
You can improve a team decision without being the person who owns it. Explore constructive challenge, shared purpose and clear boundaries through a practical dashboard example.
-
Customers can’t sign in: rehearse an authentication-provider outage
Your platform is online, but customers cannot sign in. Rehearse the decisions your software team needs to make when its authentication provider goes offline.
-
Red teaming for product teams: challenge the plan before everyone agrees
A convincing product plan can still rest on weak assumptions. Use a structured challenge to find missing evidence and make a clearer decision before committing.
-
Clear goals, less micromanagement: what tech teams can learn from mission command
Clear goals and trust give tech teams room to make better decisions. Explore what mission command can teach us about ownership, autonomy and leading with purpose.
-
Accessible sign-in: check passwords, verification codes and recovery
Review a returning user’s full sign-in journey, including paste, password managers, verification codes and recovery, with a worked example and review template.
-
Your first stretch project: agree the decisions before you start
Taking the lead for the first time? Agree what you can decide, what needs review and when to ask for help, using a worked example and a seven-line project agreement.
-
Using AI to support backlog refinement: questions before acceptance criteria
Review an existing backlog item with AI, expose missing behaviour and draft acceptance examples without inventing product policy or estimates.
