Pictor adapts its approach based on your needs—teaching when you're stuck, sharing wisdom when you're exploring, asking questions when you need to think. ChatGPT can't do that.
No credit card required • All features included • Start in 30 seconds
Generic AI answers Agile questions. pictor coaches Agile practitioners. The difference is everything.
"When was the last time ChatGPT asked you what you'd tried first — and then held you accountable for what you committed to next?"
ChatGPT is a brilliant generalist. pictor is your dedicated Agile coach — and there's a difference between being answered and being developed.
Pictor doesn't make you pick a mode. It reads what you actually need — a direct answer, a documented pattern, or a question that gets you to your own answer — and responds accordingly. Here's what that looks like in practice.
Ask a direct question, and Pictor gives you a direct, context-aware answer — not a generic checklist.
No more generic guides. Pictor understands your specific context—team size, experience level, role—and delivers actionable guidance you can use today.
Stop bouncing between the Scrum Guide, half-relevant blog posts, and busy colleagues. Ask your question, share your context, and get a clear answer you can walk into the room with today.
"How do I run sprint planning? This is going to be the first time I'll facilitate such an event with my new team!"
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?
"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."
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.
How are you feeling about the session? Is there a specific part you'd like me to go deeper on?
"We're merging two departments into a 100-person Agile organization. What scaling framework should we use?"
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.
"Both teams already practicing Agile and organized in teams. We might need to rethink the overall structure and team redesign."
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?
When the right move isn't obvious, Pictor draws on documented patterns and named sources — not guesses.
Pictor helps you see where your real problem lives before recommending solutions.
Drawing on documented wisdom from thought leaders and the Agile community, you get 2-3 distinct approaches with full citations—so you know where the thinking comes from and can go deeper.
No generic advice. No made-up stories. Every pattern cited, every source named—and always the failure mode worth avoiding before the solutions worth trying.
When you're working through something more personal — team dynamics, a hard call as a leader — Pictor asks the question that gets you to your own answer, instead of handing you one.
The toughest problems aren't technical—they're human. Pictor doesn't give you answers when you're exploring. It asks the question that makes you realize you already had one.
Through deep listening, honest reflection, and questions that cut to the core, you see what's really happening—then turn your insight into a specific, time-bound action you'll actually follow through on.
"We do retrospectives every sprint but I feel nothing ever changes..the team has basically given up on them."
What does "given up" look like in the room?
"People go through the process, they add sticky notes but nobody really believes anything will happen."
What do you think broke that belief?
"I think its related to the fact that we have the same action items for three sprints running….no actions follow up.."
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?
"Exactly. The retro itself is fine. It's the follow-through that's dead."
What would need to be different for the team to believe their actions actually matter?
"Someone needs to own each action. And we need to open every retro by reviewing what happened to last sprint's commitments."
Which of those feels like the place to start?
"The review at the start. If nothing changed, at least we're honest about it."
Let's make it concrete. What exactly will you do, and when?
"I'll open this Friday's retro with last sprint's actions, who owned them, what happened, honest review. Five minutes maximum."
So your action is: open Friday's retro with a five-minute honest review of last sprint's commitments — who owned what, what happened. How does that land?
"Sounds good!"
That's yours. You figured it out.
Reading advice is one thing. Saying the actual words out loud, to someone who pushes back, is another. In the Coaching Dojo, Pictor plays the other person — and tells you what you missed only after the scene ends.
Pick a scenario — a disengaged senior engineer, a silent teammate, a blame-deflecting lead — or describe a real situation you're facing. Pictor builds the person and plays them straight, reacting to what you actually say, not a script.
Nothing about what they're really carrying is visible during the scene. That's the point: you find out what worked the same way you would in real life — afterward.
Alex · Senior Engineer
In character — Guided rehearsal
Coach's corner — that's a judgment with no Permission or Placement first — it's likely to land as an ambush.
Scene debrief — Alex
What Alex was actually carrying
Already primed to read this check-in as surveillance — the new tracker felt like an Autonomy hit, and shifting deadlines had eroded Certainty.
“I've noticed your performance is lower than expected”
An unattributed judgment, no Placement first — reads as an ambush, triggers a Status/Fairness threat response.
“...but this is what people are saying”
Hedged, secondhand feedback without ownership — erodes trust rather than opening a real conversation.
When you end the scene, Pictor drops character and shows you the psychology you were actually navigating — plus the exact moments that helped or cost you, each one named against a real coaching framework, not a vague “good job.”
Pictor reads your intent and automatically uses the right coaching approach—direct guidance, documented wisdom, or powerful questions. No manual switching. No mode selection. Just natural, flowing conversation. Here's how:
Pictor uses this when you need immediate answers.
Direct, context-aware guidance. Share your situation and get a precise answer you can walk into the room with today — not a generic framework, but specific advice for your team, your challenge, right now.
Pictor uses this when you need proven patterns.
Documented wisdom from the Agile canon and thought leaders who shaped the field. For every challenge, you get multiple approaches with full citations, the failure pattern worth avoiding, and sources to go deeper on your own.
Pictor uses this when you need to think it through.
Powerful questions that help you see what's really happening, generate your own alternatives, and commit to a specific action you'll actually follow through on. You find the answer — and own the outcome.
Most coaching ends when the conversation closes. pictor connects every session to your competency development across all eight dimensions of Lyssa Adkins' Agile Coaching Competency Framework — the gold standard the profession was built on.
Get unstuck right now. Expert answers, mentor guidance, or powerful coaching questions — whatever you need to move forward today.
Weekly competency analysis across all eight domains from Adkins' framework shows where you're growing and what to focus on next.
Turn insights into commitments. Track what matters. Build the habits that drive growth.
← Swipe to navigate between Insights and Actions →
Talk → Insights → Actions: Every conversation connects to your competency development and tracked commitments
Icons by Arief Mochjiyat and Kris.27 from Noun Project
Whether you're new to Agile or a seasoned expert, pictor adapts to your experience level and role.
Get clear answers about practices, ceremonies, and frameworks. Build confidence fast and start contributing from day one.
Get instant guidance on facilitation challenges, team dynamics, and ceremony design. Show up as the servant leader your team deserves.
Get proven patterns from experienced product leaders for the hard backlog decisions. Think through the stakeholder conflicts you can't discuss with your team.
Get a thinking partner for the complex cases you can't bring to a supervisor. The ones about people, politics, and organizational resistance.
Get practical guidance on engineering practices, technical debt, estimation, and team performance. Lead with confidence at the intersection of technology and people.
Deepen your practice, explore edge cases, and help others grow. Pictor meets you at your level. No basics, no hand-holding, just depth.
"As a Senior Engineering Manager, I was skeptical at first, but this actually feels useful. The Expert, Mentor, and Coach modes match real day to day needs, not just theory. It gives practical, grounded guidance that aligns with real delivery challenges, not textbook Agile. Overall, it feels like a solid thinking partner rather than just another chatbot."
"As someone responsible for scaling Agile practices across multiple teams, I found pictor to be incredibly helpful, very intuitive and surprisingly insightful. It standardizes best practices while still adapting to each team's context and needs. The insights and coaching prompts helped me stay aligned with Agile values and way of working without feeling prescriptive."
"I used pictor to obtain feedback on a new, improved agile process I plan to implement. The insights provided were clear, actionable, and highly relevant to my needs."
Start free. Scale when you're ready. All plans include adaptive coaching.
Test the waters
ChatGPT is a brilliant generalist. Pictor is purpose-built for Agile coaching with adaptive intelligence that automatically detects what you need—direct guidance, documented patterns, or powerful questions—and responds accordingly. No mode switching. Just natural, contextual coaching.
But the real difference goes beyond the conversation. Pictor tracks your growth over time. Every week, your sessions are analyzed across all eight dimensions of Lyssa Adkins' Agile Coaching Competency Framework, showing you where you're developing and what to focus on next. Every coaching session can end with a specific, time-bound action you've committed to — saved with context, tracked over time, feeding back into your weekly insights.
ChatGPT answers your question and moves on. Pictor remembers where you've been, shows you where you're growing, and helps you become the practitioner you want to be.
Think of tokens as your monthly coaching budget. A typical conversation uses roughly 10,000 to 20,000 tokens, depending on depth and complexity.
The Free tier (20k) gives you one or two coaching sessions to explore. Ripper (200k) supports 10–12 conversations a month — perfect for weekly coaching. Big Wave (500k) is built for daily use, entire teams, or ambitious practitioners navigating complex organizational challenges.
You always see your usage in real time. No surprises.
Expert gives you direct, precise answers you can apply today. Mentor shares documented patterns and principles drawn from the Agile canon, with citations from recognized thought leaders. Coach asks powerful questions to help you discover your own solutions — the kind that stick because they came from you.
Each mode is a distinct coaching methodology, not just a different tone. Pictor automatically adapts its approach based on your needs—seamlessly shifting from teaching to exploring to questioning as the conversation evolves.
Pictor reads the intent behind your message and automatically adapts its coaching approach. No mode selector. No manual switching. Just natural conversation.
Ask "How do I run sprint planning?" and Pictor detects you need direct guidance (Expert). Share "I'm struggling with team dynamics" and it recognizes you need deep exploration (Coach). Wonder "Why do some teams resist change?" and it knows to share patterns and wisdom (Mentor).
The adaptation is seamless and transparent—you'll see which approach Pictor is using and why, but you never have to think about it. The conversation flows naturally, just like working with a human coach who knows when to teach, when to share stories, and when to ask powerful questions.
Pictor is framework-agnostic. Whether you're working with a single-team Scrum setup, a scaled delivery model, a Kanban system, or your own hybrid approach, Pictor draws from documented patterns across the Agile landscape — with verified citations from thought leaders and practitioners. You bring your context. Pictor meets you there.
Yes. Your conversations are encrypted in transit and at rest, never sold, and never used to train AI models. Only you can access your own data. Full stop.
Yes. Pictor is fully mobile-optimized with touch-friendly controls. Whether you're on a phone between meetings, a tablet in a workshop, or a desktop at your desk — your coaching sessions are always accessible and always in sync.
Sign up free and ask your question—Pictor automatically adapts its coaching approach to match your needs. No credit card needed. Setup takes about 30 seconds.
Not sure what to ask? Start with a real challenge you're facing right now. Pictor will detect what kind of help you need and respond accordingly. You'll get a feel for adaptive coaching immediately.
Your tokens reset monthly on your billing anniversary. You can see your usage in real time in the dashboard — no surprises, no guessing.
If you need more before the reset, upgrade anytime. The change is instant. The new tokens are available immediately.
And if you're consistently running low, that's a signal. It means Pictor is working for you. Move up a tier and keep the momentum going.
Absolutely. Individual practitioners use Pictor to develop their own skills, while teams and organizations use it as a shared coaching resource—everyone learning, everyone growing, all from the same foundation of Agile wisdom.
Each person has their own account with private conversations and personalized insights. Your growth tracking is yours alone. For teams looking for shared resources or coordinated development, reach out to discuss custom arrangements.
No — and it's not trying to. Pictor is what happens between your coaching conversations. It's available at 11pm when you're preparing for a difficult retro, at 7am when you need to think through a team dynamic, in the moment when you need a framework or a fresh perspective and your coach isn't there.
Human coaches bring relationships, intuition, and organizational presence that no AI replicates. Pictor brings availability, consistency, and a memory of your growth that makes every human coaching conversation more valuable.
Use both.
Have more questions? info@yourpaths.eu
Get Agile insights and Pictor updates delivered to your inbox
No spam. Unsubscribe anytime.