Skip to content
Question Vault?
Free to readNo accountNo email wallNo invented statisticsNo ads on medical, legal or end-of-life pagesCopy or print any set and take it with you
03 · Professional & Academic

Questions to Ask About Teamwork

Questions for a one-to-one or a team retrospective about how the group actually works together. Written for managers and team members who want concrete answers about handoffs, disagreement, and credit rather than a general talk about collaboration.

20 questions · each with a note on why · conversation guide

The questions

Open any question for the note

  1. What's working well on this team at the moment?

    Why ask it

    Opening here is not politeness. What someone names first is what they would defend if you tried to reorganise things, and it is easy to break by accident later. A blank answer this early is itself a signal worth noting.

  2. What slows you down most in a normal week?

    Why ask it

    Asking about a normal week rather than problems in general gets you the recurring friction: a handoff that waits, an approval nobody chases, a system two people know how to use. These are usually fixable and rarely reported upward.

  3. When you get stuck, who do you go to first?

    Why ask it

    The answers map the real support network, which is often two or three people carrying everyone else. If several people name the same colleague, you have found both a strength and a single point of failure.

  4. How do you want to be kept in the loop: a message, a call, or the weekly catch-up?

    Why ask it

    This looks like a preference question but it prevents a specific failure, the person who missed a decision because it happened in a channel they do not read. Ask what they have missed recently to find the gap.

  5. Is there work you're doing that you think somebody else should own?

    Why ask it

    People rarely volunteer that they have inherited something outside their job, but they will answer if asked directly. What comes up is often the leftover task that landed on whoever was nearest two years ago.

  6. When you disagree with the room, what makes it easier or harder to say so?

    Why ask it

    The useful answers are structural rather than emotional: who speaks first, whether the decision is already made, whether the disagreement happens in writing. Those you can change, unlike a general request to be more open.

  7. Was there a recent decision where you never understood the reasoning?

    Why ask it

    This surfaces where communication broke without asking anyone to complain about a person. It is also a fair check on yourself, since the decisions you thought you explained well are usually the ones that come up.

  8. How do you prefer to get feedback, in the moment or written up afterwards?

    Why ask it

    People who need time to process will hear in-the-moment criticism as an ambush, and people who want it immediately will read a written note as a formal escalation. Getting this wrong makes reasonable feedback land as a threat.

  9. Which of our recurring meetings would you cancel?

    Why ask it

    Naming one is easier than answering a general question about whether meetings are useful. If everyone names the same one, you have a decision to make rather than a discussion to have.

  10. Where do you think we duplicate work without realising it?

    Why ask it

    Duplication is invisible from the middle of it and obvious from next to it. The answer usually names two people producing overlapping documents, reports, or tracking, neither of whom knows about the other.

  11. When something goes wrong here, what usually happens next?

    Why ask it

    This is the safety question asked sideways, and it gets a much straighter answer than asking whether people feel safe. Listen for whether the account is about fixing the problem or about establishing who was at fault.

  12. Is there work you've done that you think went unnoticed?

    Why ask it

    Invisible work is often the maintenance, coordination, and cleanup that keeps a team functioning, and the people doing it tend to assume nobody wants to hear about it. Asking directly is usually the only way it comes up.

  13. What would you warn a new joiner about in their first week?

    Why ask it

    Framing it as advice for someone else lets people say the awkward true thing without it being a complaint. The warnings are typically about an unwritten rule, a fragile process, or a person to approach carefully.

  14. Is there a working relationship here you'd like to be easier?

    Why ask it

    Keep it on the relationship rather than the person's faults, or you are collecting grievances. What is usually underneath is a mismatch in pace or communication style that neither party has ever named out loud.

  15. What have you learned from someone else on this team recently?

    Why ask it

    Tells you whether knowledge is actually moving between people or whether everyone is working in a private lane. If nobody can name anything, that is a sign the team is a group of individuals sharing a manager.

  16. What do you need from me that you're not getting?

    Why ask it

    Uncomfortable to ask and worth it, but only if you can hear the answer without defending yourself. Expect silence the first time and a real answer the second, once they have seen what you did with the first.

  17. What's a skill you want to use more that this work doesn't ask for?

    Why ask it

    People leave over this more often than over pay. The answer is sometimes a small reallocation away, and knowing about it a year early is the difference between a quiet adjustment and a resignation.

  18. How would you want us to handle it if you were struggling with your workload?

    Why ask it

    Asking in advance, while nothing is on fire, gets a usable answer. Under pressure people usually say nothing, so a plan agreed in a calm week is what makes the difficult conversation possible later.

  19. If you could change one thing about how we work together, what would it be?

    Why ask it

    The single-change limit forces prioritisation and gives you something actionable. Note if the answer is about process when you expected people, or the reverse, since that gap tells you where your attention has been.

  20. Six months from now, what would tell you this team had got better?

    Why ask it

    Ends on something you can check, which also commits you to revisiting it. Vague answers about culture are worth a follow-up: ask what would be observably different on a Tuesday.

Running these conversations

Practical guidance for the conversation itself

Before you start

One-to-one, not a team meeting

Most of these get honest answers only in private. The questions about disagreement, unnoticed work, and difficult relationships will produce nothing useful in a group, however good the group is.

Say what you will do with the answers

State up front what you will act on, what you will share, and what stays between you. Without that, people default to the safe answer, and you will spend an hour collecting things you already knew.

Pick four, not twenty

Working through the whole list turns the conversation into an audit. Choose the few that match what you are actually trying to change and leave room for the tangents, which is usually where the real information is.

What to listen for

  • Names and specifics rather than themes. "Communication could be better" is a placeholder; ask which message, which week, which decision.
  • Repeated mentions across different people. One person's irritation is a preference, four people's is a process problem.
  • What they do not raise. If nobody mentions workload or credit, consider whether it is genuinely fine or genuinely unsafe to say.
  • Hedging before an answer. A pause and a "this is probably just me" usually precedes the most useful thing in the conversation.

Where these conversations go wrong

Asking and then doing nothing

The second round of these questions gets worse answers than the first if nothing visible changed. If you cannot act on something, say so and explain why, which people accept far better than silence.

Defending yourself mid-answer

The moment you explain why a decision was actually correct, the conversation is over even if it continues. Write the objection down, thank them, and take the argument somewhere else.

Collecting complaints about individuals

Questions about difficult relationships need to stay on what would make the work easier. Once it becomes a character assessment of an absent colleague, you have created a problem rather than found one.

Treating preferences as requirements

Feedback style and communication preferences are worth accommodating where you can, but four people wanting four different systems means you still have to pick one. Say which and why rather than promising everyone their own.