How to be a Better Stakeholder
20 questions to ask instead of “When’s it going to be done?”
In my last post “Slow Productivity for the Software Industry”, I suggested that reducing Projects In Progress is a great way to increase velocity and prevent burnout. In getting buy-in to do less at once, I wrote:
Overtime hopefully you can train stakeholders to stop asking questions like “when will we get these 5 projects done?” but instead ask:
“Are we working on the 1–2 best things?”
“Would we still do this project if it took 50% more time?”
“How can we deliver something smaller, somewhat sooner?
This may come as a surprise to some, but your job as a stakeholder isn’t primarily to find out when the work is going to be done! Instead your job is to make the best decisions with the information available and to set the team up to execute your goals successfully.
So in the spirit of a former boss who said that the best leaders ask the best questions, here are 20 questions stakeholders¹ can ask instead of “When’s it going to be done?”:
- How can I help you?
- Do you have the business / product / other context you need?
- Do you understand my goals with this work?
- How’s the team’s morale?
- Where is there still risk and uncertainty in the plan?
- What did we learn this week?
- What’s blocking the team?
- Can you fill out this RAID log?
- Is giving me updates slowing you down?
- Is there a sprint/epic/project report being auto generated I can use to follow along?
- Can we deliver important parts of this work before the whole?
- What would you do differently with less time?
- What would you do differently with more time?
- Should we stop / cancel this work?
- What are we not getting to as we focus on this work?
- Are we still doing this work for the right reasons?
- Can I provide hands-on feedback?
- What does the rollout plan look like?
- What are the work’s SLO/SLIs?
- How should we celebrate when we finish?
There are definitely some themes here for stakeholders: question with empathy and play an active role by being helpful. Putting this list together was a good reminder for me- favor assistance over accountability as an engineering director and stakeholder.
Let me know what you think! What questions do you wish your stakeholders would ask? As a stakeholder, what are your favorite ways to learn what you need?
¹ For our purposes, I will define a stakeholder as anyone with a vested interest in the output of a software engineering team.