Expert, Mentor, Coach - When to Use Each Mode

The hardest part of getting coaching isn't finding someone to talk to. It's knowing what kind of help you actually need.

When you're stuck on a team challenge, do you need someone to tell you what to do? Share wisdom from experience? Or ask questions that help you figure it out yourself?

The answer is: it depends. And that's exactly why Pictor gives you three distinct coaching modes.

Expert Mode: Tell Me What To Do

When to use it: You need a specific answer or practice to try right now.

Expert mode is for those moments when you're stuck and need a path forward. You're about to facilitate your first sprint planning. You need a retrospective format for a team that's lost its energy. You need to learn about a metric you've never used before.

You don't need self-discovery - you need a concrete practice you can implement tomorrow.

What you get:

• Specific frameworks and formats
• Step-by-step approaches
• Clear recommendations with rationale
• Tactical guidance you can act on immediately

Example conversation:

You: "How do I run sprint planning? This is going to be the first time I'll facilitate such an event with my new team!"

Pictor (Expert): "Before I tailor this for you, a couple of quick questions: How large is your team, and do they have any prior experience with Scrum or sprint planning?"

You: "They have previous experience with Scrum. I just joined their team as Scrum Master. Their size... with the Product Owner and myself we are 7 people."

Pictor (Expert): "Great context, thank you. So you have 5 developers plus a Product Owner, and the team already knows Scrum—that makes your job as a new facilitator much easier. You're not teaching them the process; you're stepping in to lead a ritual they're already familiar with.

Here's how to run an effective sprint planning session with this team:

Start with the sprint goal (~15 min) - Collaborate with the Product Owner to articulate a clear, meaningful sprint goal. "Users can complete checkout without calling support" is a sprint goal. "Work on checkout bugs" is not.

Story review (~40 min) - Product Owner walks through highest-priority items. Your role: facilitate, watch the clock. If a story takes more than 5-7 minutes of discussion, it needs more refinement—note it and move on.

Estimation and breakdown (~25 min) - Team selects stories and breaks them into tasks. Don't change their estimation method on day one. Observe first, adapt later.

The one thing you need to hear: Observe before you change anything. Build trust first, understand why they do things the way they do, then suggest experiments."

Expert mode gives you the answer. The practice. The next step. And it adapts to your specific context.

Mentor Mode: Help Me Understand

When to use it: You need context, wisdom, and the "why" behind practices.

Mentor mode is for when you know that something works, but you want to understand why it works and when to apply it. You're building your judgment as an Agile practitioner.

Good mentorship doesn't just hand you answers - it helps you develop the mental models to adapt practices to your specific context, with real citations so you can go deeper.

What you get:

• Wisdom from documented experience
• The reasoning behind practices with sources
• Trade-offs and when exceptions make sense
• Patterns that apply across situations
• Full citations to go deeper on your own

Example conversation:

You: "We're merging two departments into a 100+ person Agile organization. What scaling framework should we use?"

Pictor (Mentor): "What's the current Agile maturity of each department coming into the merge? Are both teams already practicing Agile, or is one more traditional? And do you know yet how the new org structure will be shaped—are you starting from scratch on team design, or inheriting existing team boundaries? That context matters a lot for which patterns will be most relevant here."

You: "Both teams already practicing Agile and organized in teams. We might need to rethink the overall structure and team redesign."

Pictor (Mentor): "Great context—two Agile-practicing departments merging into ~100 people with a potential team redesign. That's actually a better starting position than most organizations face, but it comes with its own specific risks.

The Core Pattern: Merges Create "Fake Alignment" Matthew Skelton and Manuel Pais document this in Team Topologies: when two organizations merge, there's often a period where people look aligned—same ceremonies, similar terminology—but the underlying team structures and ownership boundaries are mismatched. The antidote: be deliberate about how teams are structured, what they own, and how they interact.

Three Approaches Worth Considering:

1. Team Topologies (Skelton & Pais) - At 100 people, you're looking at stream-aligned teams, platform teams, and enabling teams. The key question: what are the long-lived team structures that minimize dependencies?

2. Flight Levels (Klaus Leopold) - His insight: most Agile problems at scale aren't team-level—they're coordination problems between teams. Focus on Flight Level 2 (coordination) before assuming team practices will sort themselves out.

3. Temporary Coordination Structure - Establish lightweight coordination during transition (3-6 months) that isn't your permanent structure. Prevents chaos without locking you into something you'll regret.

Which resonates most given your situation?"

Mentor mode builds your understanding so you can make better decisions independently—and gives you the sources to learn more.

Coach Mode: Help Me Think This Through

When to use it: You need to discover your own answer through reflection and powerful questions.

Coach mode is for when the best solution is the one you figure out yourself. Maybe you already have the insight but haven't quite articulated it yet. Maybe the situation is so unique to your context that no generic answer will fit.

Professional coaching uses questions to unlock your own thinking. It's slower than getting an answer, but the insights stick because you did the work.

What you get:

• Powerful questions that reframe the situation
• Space to think through your options
• Clarity about what you actually want
• Solutions that fit your specific context
• A concrete action plan with commitment

Example conversation:

You: "We do retrospectives every sprint but I feel nothing ever changes...the team has basically given up on them."

Pictor (Coach): "What does 'given up' look like in the room?"

You: "People go through the process, they add sticky notes but nobody really believes anything will happen."

Pictor (Coach): "What do you think broke that belief?"

You: "I think it's related to the fact that we have the same action items for three sprints running...no actions follow up..."

Pictor (Coach): "Let me make sure I understand. The retro format isn't the problem — the problem is that actions disappear after the meeting, and the team has learned not to trust the process. Is that it?"

You: "Exactly. The retro itself is fine. It's the follow-through that's dead."

Pictor (Coach): "What would need to be different for the team to believe their actions actually matter?"

You: "Someone needs to own each action. And we need to open every retro by reviewing what happened to last sprint's commitments."

Pictor (Coach): "Which of those feels like the place to start?"

You: "The review at the start. If nothing changed, at least we're honest about it."

Pictor (Coach): "Let's make it concrete. What exactly will you do, and when?"

Coach mode doesn't give you the answer. It helps you find it yourself - which often means you find a better answer than anyone could have told you. And because you discovered it, you'll actually follow through.

How To Choose

Here's a simple framework:

Use Expert mode when:

• You're stuck and need immediate direction
• Time is a factor
• You're trying something for the first time
• A proven practice exists for your situation

Use Mentor mode when:

• You want to understand the "why" behind practices
• You need to adapt something to your context
• You're building your judgment as a practitioner
• You're facing trade-offs and want experienced perspective

Use Coach mode when:

• The answer needs to come from you
• Your situation is unique or complex
• You want to develop your own thinking
• You're working through values or priorities

The Real Answer: All Three

Here's what we've learned: great coaching isn't about picking one mode and sticking with it. It's about moving fluidly between modes as the conversation evolves.

You might start in Expert mode ("What retrospective format should I try?"), move to Mentor mode to understand why that format works, then shift to Coach mode to figure out how to adapt it to your team's specific dynamics.

That's exactly how Pictor works. You're never locked into a mode. Switch whenever you need a different kind of support.

Because the goal isn't to receive perfect coaching - it's to get unstuck and move forward with your team.

---

Try all three modes: Each mode unlocks different kinds of insights. Experiment to find what works for your situation. Start a free coaching conversation →