Here are 100 lines of Lisa Adkins–style Agile coaching questions and reflections, designed to help you “think agile”—focusing on mindset, self-awareness, collaboration, and system thinking (inspired by her book Coaching Agile Teams and her Agile coaching approach):
What assumptions am I making right now?
How might I be contributing to the very problem I’m describing?
What does “done” really mean for me or my team?
What outcome do I want to create, not just the activity to complete?
How do I know I’m adding value right now?
What’s one thing I could stop doing to make space for better collaboration?
Am I reacting or responding with intention?
What story am I telling myself about this situation?
How would I handle this if I trusted the team completely?
What experiment could I run instead of making a big decision?
How am I embodying the Agile values myself?
Where am I being rigid in my thinking?
How could curiosity change the way I see this?
What is the smallest next step that moves us forward?
How can I help the team own this, rather than me driving it?
What feedback loop could I create to validate this assumption quickly?
Am I measuring progress or just activity?
What does success look like from the customer’s perspective?
How would a truly agile thinker frame this challenge?
What am I learning about myself through this process?
What’s blocking you from doing your best work right now?
How might the team solve this without my input?
What have you tried already? What happened?
What does “working together” look like for you?
What patterns do you notice in how the team communicates?
What do you think the team needs from me as a coach right now?
What might you learn if you stopped trying to fix things?
What kind of team do you want to be part of?
What are you proud of in how your team collaborates?
What one improvement would have the biggest impact on the team?
How could we make our retrospectives more meaningful?
What’s one norm that no longer serves this team?
What’s underneath the conflict we’re seeing?
How does trust show up—or not show up—on this team?
What conversation are we avoiding that needs to happen?
How can I hold space for the team to find their own answers?
What does empowerment look like here, not just talk about it?
What experiment could we run this sprint to build trust?
How do we celebrate learning as much as delivery?
What would make this team unstoppable?
What’s the system optimizing for right now?
Where are we creating bottlenecks without realizing it?
How does work really flow through this system?
Who benefits most from the current process—and who doesn’t?
How can we make invisible work visible?
What’s the real problem, not just the symptom?
What data could help us see the system clearly?
How might a small change ripple across the system?
What constraints are actually helping us be creative?
Where are decisions getting stuck?
How could we shorten our feedback loops?
What’s one process we could simplify right now?
Where are we over-engineering solutions?
Who needs to be in the conversation but isn’t?
What dependencies are slowing us down?
How could we design for learning, not perfection?
What would happen if we trusted the system to self-correct?
What signals are we missing because we’re focused on output?
What’s the cost of not changing this system?
How can we make the system more humane, not just efficient?
What does servant leadership look like in action here?
How can I model vulnerability as a leader?
What behaviors do I reward—intentionally or unintentionally?
How do I respond when things go wrong?
What would it look like to lead through questions instead of answers?
How can I remove fear from this environment?
What values drive our daily decisions?
How can I help others step into leadership?
How am I reinforcing agility—or bureaucracy?
What’s one courageous conversation I need to have this week?
How could I use storytelling to reinforce our Agile values?
What legacy do I want to leave through my leadership?
How do we handle conflict—productively or defensively?
How can we align purpose, autonomy, and mastery here?
What would happen if we measured happiness as seriously as velocity?
How could we create more safety for experimentation?
What’s one ritual that strengthens our Agile culture?
How can I help others see failure as data, not disaster?
What am I doing to build transparency across the organization?
How can I make space for reflection in a busy system?
What’s the customer asking for that we haven’t heard yet?
How do we know our work is creating real value?
What can we learn from this iteration—success or failure?
What does simplicity look like here?
How might we deliver this in smaller, testable pieces?
What’s the minimum viable outcome?
How can we adapt our plan based on what we just learned?
What assumptions should we test next?
How do we keep learning at the center of our process?
What’s the real risk we’re afraid of?
What would it look like to collaborate cross-functionally here?
How might automation help—not replace—our creativity?
What’s the story our metrics are really telling us?
How do we ensure quality without slowing down agility?
What feedback do we need that we’re not getting?
How might we make our process more visible to everyone?
How could we celebrate small wins more consistently?
What’s one improvement we could try in the next sprint?
How can I keep curiosity alive in this team?
What does “thinking agile” mean to me, right now, in this moment?